Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If a Windows 10 blue screen names win32kfull.sys, that does not prove the file is damaged: Windows may have detected a failure there after a driver, memory, storage, or system-file problem. Photograph the screen and note the exact STOP code, then back up important files and work through recent changes, drivers, Windows repair tools, and hardware checks. Windows 10’s ordinary support ended October 14, 2025, so plan a supported upgrade as well as a crash fix.
What does win32kfull.sys mean?
win32kfull.sys is a Windows component associated with the Win32 and desktop graphics subsystem. It normally resides at C:WindowsSystem32win32kfull.sys. When a crash screen or dump-analysis tool names it, Windows has identified the module involved when the failure was detected; that alone does not establish the original cause. A third-party driver, incompatible graphics or input software, faulty RAM, damaged Windows files, a storage problem, or another kernel-level component may be responsible. Microsoft’s stop-code guidance treats the named module as a clue to investigate, not proof of fault.
Do not delete the file or download a replacement from a system-file repository. Use Windows repair tools or recovery options instead. A stop code gives more useful direction than the filename alone. Examples include SYSTEM_SERVICE_EXCEPTION (commonly bug check 0x3B), PAGE_FAULT_IN_NONPAGED_AREA (0x50), MEMORY_MANAGEMENT (0x1A), KMODE_EXCEPTION_NOT_HANDLED (commonly 0x1E), IRQL_NOT_LESS_OR_EQUAL (0xA), and VIDEO_TDR_FAILURE (commonly 0x116 or a related graphics timeout). These codes narrow the investigation; none by itself proves which part needs replacing.
Recommended Free Tools
Record the crash and protect your files
- Photograph the blue screen before the PC restarts. Record the STOP code, any “What failed” filename, the time, and whether it restarts immediately.
- Note what was happening: startup, gaming, video playback, sleep or wake, printing, remote desktop, or ordinary desktop use. Record recent driver or Windows updates, new apps, peripherals, BIOS changes, and memory overclock or tuning changes.
- If Windows starts, check the edition and version at Settings > System > About. Review Settings > Update & Security > Windows Update and open Event Viewer > Windows Logs > System to inspect events around the crash.
- For recurring crashes, look in
C:WindowsMinidumpand, if present,C:WindowsMEMORY.DMP. A pattern across several dumps is more useful than a single filename; a dump can show where corrupted memory was detected rather than which component corrupted it.
Back up important files before resetting Windows, replacing hardware, or attempting intensive recovery. If the drive is unstable or reports read errors, copy irreplaceable files first. Avoid registry cleaners and generic driver-updater utilities: they can install the wrong driver or make the cause harder to isolate.
#1 Best Overall
Start with recent changes, updates, and peripherals
If the crashes began after a specific change, undo or isolate it before making several unrelated changes at once. Disconnect newly added peripherals and temporarily remove recently installed software that interacts with graphics, input, or the desktop, such as GPU overlays or tuning tools, virtual-display and remote-control software, tablet or printer utilities, shell customization, or third-party security software. Do not remove a Microsoft system driver just because an analyzer lists it.
For an older driver on a previously stable system, use Windows Update or the support page for the exact PC, motherboard, or graphics-card model. Prefer the computer maker’s driver on laptops and branded PCs, particularly for chipset, storage, touchpad, and firmware components. Do not use a generic download site. If trouble began immediately after a driver change, rollback is more appropriate than installing another driver at random.
- For Windows updates, open Start > Settings > Update & Security > Windows Update, choose Check for updates, install applicable updates, and restart. Labels can vary slightly by Windows 10 release.
- For a changed device driver, open Device Manager, expand the relevant category, right-click the device, and select Properties > Driver. Choose Roll Back Driver if available. If rollback is unavailable, use the device maker’s instructions to install the correct model-specific driver.
- If the crash began after a Windows quality update rather than a device driver, consider uninstalling that recent update through Windows recovery or update history. Make one change at a time so you can tell whether the timing matches the result.
For gaming or video crashes, investigate the graphics driver, overlays, GPU overclock or undervolt, chipset and BIOS updates, RAM stability, temperature, and power. Graphics activity can expose several kinds of instability; it does not by itself prove the GPU is faulty. For crashes during printing, tablet use, or desktop interaction, prioritize the related printer, pen, touchpad, HID, remote-access, virtual-display, or customization software.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
Use Safe Mode to narrow down third-party software
Safe Mode loads a reduced set of drivers and services. If the crashes stop there, a third-party driver, startup app, security product, overlay, or hardware-related driver becomes more suspect, but Safe Mode does not identify the exact culprit. If the crash continues in Safe Mode, increase attention to RAM, storage, firmware, core Windows corruption, or a low-level driver that still loads.
- If Windows starts, hold Shift while selecting Restart.
- Choose Troubleshoot > Advanced options > Startup Settings > Restart.
- After restart, press
4for Safe Mode or5for Safe Mode with Networking.
When Safe Mode is stable, remove or roll back the most recently changed relevant driver or app first. If there is no clear recent change, use a controlled clean boot or disable recently added startup services in small groups; avoid removing unrelated system components.
Repair Windows system files with DISM and SFC
Run these built-in tools when Windows may have corrupted or missing protected files. Open Command Prompt as administrator and run DISM first, then SFC:
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannowDISM repairs the Windows component store that SFC may rely on. SFC checks protected system files and repairs corruption where possible. Let each command finish, then restart. Microsoft documents these tools in its System File Checker guidance. If SFC says it could not repair some files, do not assume the crash is fixed; try Safe Mode, System Restore, or a repair installation as appropriate. If SFC finds no integrity problem, that still does not rule out faulty hardware or third-party drivers.
Test RAM and memory settings
- Press the Windows key, type Windows Memory Diagnostic, and choose Restart now and check for problems. Let the test complete.
- After Windows starts, check Event Viewer > Windows Logs > System for
MemoryDiagnostics-Results. - If crashes continue or the test is inconclusive, return BIOS/UEFI memory settings to defaults. Remove overclocking, undervolting, XMP-style memory profiles, and non-default timings while troubleshooting.
- If the machine has removable RAM, test one module at a time only if you are comfortable doing so; otherwise use the PC or motherboard maker’s diagnostics or seek service.
A clean Windows Memory Diagnostic result does not guarantee that RAM is stable under every workload. Microsoft’s guidance for bug check 0x50 includes physical memory among the possible causes.
Check the Windows drive
Start with a scan that does not request repair:
chkdsk C: /scanIf Windows reports file-system errors, or the problem persists, schedule a repair:
Rank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
chkdsk C: /fThe /f repair may require a restart when C: is the Windows volume. Do not start with /r on a drive that may be failing: it can take a long time and requires extensive reads. If the drive disappears, makes unusual noises, shows SMART warnings, or returns read errors, prioritize backup and drive diagnosis over repeated repair attempts. A file-system scan cannot repair a physically failing drive.
Use dump files and Driver Verifier only for advanced diagnosis
Read recurring crash dumps
Advanced users can inspect dump files with Microsoft WinDbg and the command !analyze -v. Consider the call stack and third-party modules alongside the stop code, recent changes, and patterns across dumps. A named Microsoft module may be where Windows detected corrupted memory, not the driver that first caused it.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use Driver Verifier cautiously
Driver Verifier deliberately stresses drivers to expose violations; it can also make Windows unstable or prevent normal startup. It is not a first-line fix. Create a restore point, save work, and select only suspicious, recently updated, third-party, or unsigned drivers rather than verifying every driver. Do not leave Verifier enabled indefinitely. Microsoft’s stop-error instructions warn about careful driver selection and recovery.
If enabling Verifier causes startup crashes, enter Safe Mode, open an elevated Command Prompt, and run:
verifier /resetRestart normally. Driver Verifier cannot run in Safe Mode; Safe Mode is useful here to disable it.
If Windows will not boot
Use Windows Recovery Environment (WinRE), which may appear after repeated failed starts, or boot from Windows installation media and select the repair option. Microsoft outlines recovery paths in its Windows boot issues guidance. From Troubleshoot > Advanced options, try the option that matches the timing of the problem:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Startup Repair for startup failures.
- Startup Settings to reach Safe Mode and undo a driver or software change.
- System Restore if the problem began after a change and a restore point exists.
- Uninstall Updates if a recent Windows update appears to have triggered the boot failure.
If Verifier caused the loop, use Safe Mode and verifier /reset as described above. Do not repeatedly interrupt power as the main recovery strategy. In WinRE, drive letters may differ from their normal Windows assignments; before running offline repair commands, identify the volume containing the Windows folder rather than assuming it is C:. If you cannot identify it safely, use the recovery interface or get technical help.
When to restore, repair, reset, or replace hardware
- System Restore: Use an available restore point if crashes began after a driver, application, or update and simpler rollback did not resolve them.
- In-place repair installation: Consider this when Windows remains repairable but system corruption persists. Whether apps and files can be retained depends on the installation media, edition, and selected option.
- Reset this PC: Consider it after a verified backup when software causes remain likely and earlier repairs failed. Resetting can remove apps and data depending on the option selected, and it will not fix defective RAM, a failing SSD, overheating, unstable firmware settings, or a faulty graphics card.
- Hardware service or replacement: Favor diagnosis when crashes continue in Safe Mode, storage or memory tests report faults, the drive shows failure signs, or instability persists at default firmware settings. Ask for specific RAM/SSD testing and a written diagnosis rather than a vague optimization service.
- Windows 11 upgrade: If the device meets requirements and you do not need to remain on Windows 10, plan an upgrade after backing up and addressing suspected hardware faults. An OS upgrade does not repair failing hardware.
Windows 10 support status
Microsoft ended ordinary Windows 10 support on October 14, 2025. Eligible personal devices running Windows 10 version 22H2 can use the consumer Extended Security Updates program through October 13, 2026; this provides security coverage, not a fix for a BSOD. Eligibility and enrollment options vary by region. See Microsoft’s Windows end-of-support information for current terms. If the PC is compatible, moving to Windows 11 is the more durable supported-platform plan; otherwise, investigate replacement or a supported alternative rather than treating Windows 10 as fully supported long term. Microsoft’s Windows 11 page has upgrade information.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
