Three System BSODs ?
Three System BSODs ?
Please download the SysnativeBSODCollectionApp and place it on your Desktop. After running it, upload the generated zip file to a cloud service using the provided link. This tool compiles all troubleshooting information we typically require. It does not gather any personal data. It is utilized by several well-known Windows help forums, including this one. As a senior BSOD analyst on the Sysnative forum where it originated, I can confirm its safety.
You may review the contents of the zip file before uploading, as most files are text documents. Avoid modifying or removing anything. For a detailed explanation of each file, refer to the information available here.
The Sysnative ZIP archive contains the WD Blue HDD file excluded.
https://www.mediafire.com/file/2zm7axggo...9.zip/file
Those three BSOD occurrences might all stem from RAM issues. You mentioned a previous unstable stick—are you absolutely confident the other one is stable? Consider running Memtest86 on it once more to confirm.
Additionally, I observe in one of the dumps that it failed when exiting the idle state.
Code:
8: kd> k
# Child-SP RetAddr Call Site
00 ffffbb8a`3c6d1278 fffff800`25a2af29 nt!KeBugCheckEx
01 ffffbb8a`3c6d1280 fffff800`25a26389 nt!KiBugCheckDispatch+0x69
02 ffffbb8a`3c6d13c0 fffff800`259b1909 nt!KiPageFault+0x489
03 ffffbb8a`3c6d1550 fffff800`258376dd nt!PpmIdleSelectStates+0x289
04 ffffbb8a`3c6d1a50 fffff800`25a19f64 nt!PoIdle+0x26d
05 ffffbb8a`3c6d1c40 00000000`00000000 nt!KiIdleLoop+0x54
Your analysis of the stack trace, read from top to bottom. You notice the processor begins in idle mode (nt!KiIdleLoop), gets activated by the power manager (PPM) shifting from low-power idle to active state, and then immediately encounters a page fault followed by a BSOD.
I’ve encountered similar issues on other CPUs, especially AMD models, where the transition between idle and active states can be slow—this could be the root cause here. There’s no permanent solution, but a workaround exists...
Visit your BIOS settings and adjust the CPU C-States control. Turn off all C-States for every processor. This will stop the CPU from entering low-power idle when inactive, preventing the need for a power-up transition when it becomes active again. Test this change to see if it resolves the problem.
The main drawback is that the CPU may run slightly hotter during idle periods, though a good cooler should manage it. It will also consume a bit more power while idle, but this is unlikely to impact performance noticeably.
I previously executed Memtest86 once more, and the device showed no issues.
I started using the system after turning off C-States and faced a BSOD. After two days of smooth operation, I had to restart because the GPU driver entered safe mode an hour after the second boot. The driver still crashes during idle or when running non-3D programs. When playing a PC game, the GPU temperature rises from 35°C to between 45°C and 60°C without triggering crashes. How can I stop the GPU driver from crashing while the system is idle? I’ll share the GPU-Z logs soon.
I own a Ryzen 5 air cooler paired with a 500W power supply unit.