I built this PC about two or three weeks ago, and it consistently crashes to a blue screen roughly five hours and 32 minutes after starting it. We replaced the RAM, but that didn't solve the problem. We also cleaned up and reinstalled potentially outdated or corrupted drivers, including the network and graphics drivers. The graphics driver was removed in Safe Mode with DDU before reinstalling it.
Event Viewer has shown different bug-check results, but the last few crashes reported SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E), with win32kfull.sys and Wdf01000.sys mentioned. The system uses an X870 Wi-Fi 6 motherboard, a Ryzen 7 7800X3D processor, and a Radeon RX 9070 XT graphics card. We have collected several minidump files and are considering updating the BIOS. What would be the best next steps for identifying the faulty component or driver?
3 Answers
The minidumps are the most useful evidence here, since Event Viewer often only shows a symptom rather than the actual cause. Analyze several dumps together with a debugger and check whether they consistently point to the same third-party driver. If Windows is not creating dumps reliably, make sure small memory dumps are enabled and that the system drive has a paging file.
Also check temperatures and power stability while the system is under load. Monitor CPU, GPU, hotspot, and motherboard temperatures, and run separate tests for memory, CPU, and graphics rather than stressing everything at once. If crashes continue at completely stock settings, reseat the RAM and graphics card, verify all power connections, and test with minimal peripherals. The files named win32kfull.sys and Wdf01000.sys are Windows components, so they may be getting blamed because another driver or unstable hardware caused the crash.
Because this is a brand-new AM5 system, update the motherboard BIOS and install the current AMD chipset drivers from the motherboard or AMD support page. Then load BIOS defaults before testing. Avoid enabling EXPO, PBO, undervolting, or other overclocking features until the machine is stable, since memory-controller or firmware instability can look like random driver crashes.
We have not found one consistent driver in Event Viewer, so we’ll try the BIOS and chipset updates with everything set to stock first.