Random crash and reboot with new PC build

Please run:

a) Sea Tools for Windows Long Generic test > post images or share links




b) HD Sentinel (trial version)
Post images or share links for results on these tabs:
a) Overview
b) Temperature
c) SMART

Here's the results from Seatools and HD Sentinel

Please read this tutorial on Windows Driver Verifier (WDV):





Do not use the tool until comments are posted into his thread.

Please indicate whether the installed RAM is or is not on the Qualified Vendor List (QVL).

CMK32GX5M2B5600C36
DDR5 16GB 5600
13th Gen Intel(R) Core(TM) i5-13600K


If the installed RAM is not on the QVL then for testing purposes test RAM displayed on the QVL.





From the Ten Forums tutorial in the prior post learn the methods to recover from WDV crashes by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail


Plan to run WDV with various customized test settings for approximately 48 hrs.

Make a new restore point.

Start the testing with these settings:

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers
c) Start with the 3 customized tests displayed in the Ten Forums tutorial


If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

For any BSOD post a new V2 share link into the newest post.

Yes, the RAM is on the QVL for my motherboard (see attached pic)

I'm still reading up on Driver Verifier, does the PC need to be running for the full duration that WDV is enabled? I don't usually keep my PC running overnight, that's the reason I'm asking.

WDV can be used in the background during regular use.

It can be turned off with the verifier /reset command before sleep.

The goal is to stress test drivers with various customized tests.

While using the tool if there are major performance problems including very slow boot please comment into this thread.

Most often the BSOD crashes occur shortly after starting the tool.

For the misbehaving drivers that don't immediately crash the stress testing is continued for 24 to 48 and sometimes longer to find the misbehaving drivers.

PLEASE take a System Restore point, or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar), BEFORE you enable Driver Verifier. When Driver Verifier identifies a misbehaving driver it BSODs. If a driver loaded at boot time is misbehaving then you'll be stuck in a boot-BSOD loop. In that event you can either boot the Windows installation media and use System Restore from there to restore to the restore point you took, or you can restore the disk image you took. These are the only ways out of a Driver Verifier boot-BSOD loop.