MultiHub Forum

Full Version: What is the best diagnostic plan for random BSODs after Nvidia driver update?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I've been getting random blue screen errors on my custom-built gaming PC for the past two weeks, and the stop codes seem to vary each time, making blue screen troubleshooting incredibly frustrating. The system was stable for over a year, but the crashes started shortly after I updated my Nvidia graphics drivers and installed a new Windows security patch. I've tried running the Windows Memory Diagnostic tool, which found no errors, and I've reseated my RAM and GPU, but the problem persists intermittently, often during gaming or heavy multitasking. For others who have solved similar elusive BSOD issues, what was your systematic diagnostic process? Should I focus next on testing the SSD with CrystalDiskInfo, rolling back the graphics driver with DDU, or stress-testing the CPU and RAM with something like Prime95 and MemTest86? I'm worried it might be a failing power supply or a motherboard issue, but I don't have spare parts to swap for testing.
Good plan. Start by collecting the minidump files and any crash logs so you can identify the STOP code and implicated module. On Windows, enable memory dumps (small/complete) under System settings, reproduce the crash if possible, then use WinDbg or BlueScreenView to read the dump and see which driver or kernel module triggered it. Also check Event Viewer System/Application around the crash time for clues.
Monitors: install HWInfo or Open Hardware Monitor to watch temps, Vcore, and GPU/PCIe voltages during load. If you see PSU rails dipping or unstable spikes when gaming, that points to power supply or motherboard VRM. In absence of spare parts, you can try a stress test that pushes CPU/GPU but keep an eye on temps; throttle to protect hardware. If you suspect the PSU, a local shop can test it with a known-good meter or you can temporarily swap with a known good unit.
Disk health: run CrystalDiskInfo to check SMART values; look for reallocated sectors, pending sectors, or long drive power-on hours. Run CHKDSK /R, and consider a firmware update if available. Since Windows updates and drivers can touch storage routines, log the state before each change and if a crash occurs after a patch, it’s a clue. Also test by moving heavy I/O tasks to another drive to see if issues persist.
Drivers: roll back NVIDIA driver using Display Driver Uninstaller (DDU) in safe mode to the previous version that was stable. Boot with clean boot and test; avoid beta drivers; consider a system restore or clean install if the issue seems tied to a patch. Verify BIOS/driver version compat with your motherboard and PCIe lane config; disable any XMP memory profiles during testing.
Systematic diagnostic plan you can follow quickly: 1) capture minidump, 2) run safe mode, 3) test RAM via MemTest86 overnight, 4) check disk health, 5) run a CPU/GPU stress test with temperature monitoring, 6) reseat power connectors and check for sagging rails, 7) simplify the system by removing non-essential peripherals, 8) check for overclock, 9) update BIOS if needed. If instability continues, consider suspect hardware like motherboard VRMs or the PSU; since you don’t have spares, a professional diagnostic might be cheaper than guessing.