Sporadic crashes on boot / wake, need to reset

sd522527 · May 7, 2024

Hi,

I have a computer that I recently built and everything is going great, except every now and then my computer will fail to wake from sleep, and I have to press the reset button on the case. This also sometimes happens when I power the machine on after being shutdown for a few days. In all cases, there are critical errors in the Event Viewer (I attached a V2 log to this post).

When the computer is failing to start/wake, the fans are spinning, but the monitor does not wake and there is no power to the keyboard or mouse (based on the numlock light not being turned on). I'm not really sure what is happening; I've run every benchmarking tool I could find and have had no errors, nor have I had an actual BSOD.

Thanks in Advance,
Steve

zbook · May 7, 2024

There were four BSOD during the past 30 days.

Had you configured the settings to only use the Nvidia dGPU?

The AMD GPU was disabled when the V2 log collector ran on 05/06/2024.

Was the AMD iGPU disabled on 04/07 and / or 05/06 during the unexpected shutdowns and restarts?

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) The BIOS Version/Date American Megatrends International, LLC. 2.02, 11/17/2023

Upgrade the BIOS: 2.02 > 2.10 (most up to date non-beta BIOS)

ASRock B650M Pro RS WiFi

Supports AMD Socket AM5 Ryzen™ 8000 and 7000 Series Processors; 8+2+1 Power Phase, Dr.MOS; 4 x DDR5 DIMMs, Supports Dual Channel, up to 7200+ (OC); 1 PCIe 4.0 x16, 1 PCIe 3.0 x16; Graphics Output Options: HDMI, DisplayPort; Realtek ALC897 7.1 CH HD Audio Codec, Nahimic Audio; 4 SATA3, 1 Blazing...

www.asrock.com

3) If the AMD GPU was disabled on 04/07 and / or 05/06 then uninstall the Nvidia GPU drivers nvlddmkm.sys using DDU.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

www.nvidia.com

4) Read this tutorial on Windows Driver Verifier:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Code:

Name    NVIDIA GeForce RTX 4080
PNP Device ID    PCI\VEN_10DE&DEV_2704&SUBSYS_13BB196E&REV_A1\4&D0BDF66&0&0009
Adapter Type    NVIDIA GeForce RTX 4080, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 4080
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll
Driver Version    31.0.15.5212
INF File    oem31.inf (Section081 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_268E85175AA9E991\NVLDDMKM.SYS (31.0.15.5212, 57.26 MB (60,044,320 bytes), 4/7/2024 8:19 PM)

sd522527 · May 7, 2024

zbook said:
There were four BSOD during the past 30 days.

Had you configured the settings to only use the Nvidia dGPU?

The AMD GPU was disabled when the V2 log collector ran on 05/06/2024.

Was the AMD iGPU disabled on 04/07 and / or 05/06 during the unexpected shutdowns and restarts?

I believe after the last time this happened (04/07 sounds about right) I went into the Bios and disabled the AMD iGPU, because the EventViewer Bug codes were pointing at a VIDEO_CARD memory issue IIRC.

zbook said:
Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) The BIOS Version/Date American Megatrends International, LLC. 2.02, 11/17/2023

Upgrade the BIOS: 2.02 > 2.10 (most up to date non-beta BIOS)

ASRock B650M Pro RS WiFi

Supports AMD Socket AM5 Ryzen™ 8000 and 7000 Series Processors; 8+2+1 Power Phase, Dr.MOS; 4 x DDR5 DIMMs, Supports Dual Channel, up to 7200+ (OC); 1 PCIe 4.0 x16, 1 PCIe 3.0 x16; Graphics Output Options: HDMI, DisplayPort; Realtek ALC897 7.1 CH HD Audio Codec, Nahimic Audio; 4 SATA3, 1 Blazing...

www.asrock.com

3) If the AMD GPU was disabled on 04/07 and / or 05/06 then uninstall the Nvidia GPU drivers nvlddmkm.sys using DDU.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

Download the latest official NVIDIA drivers

www.nvidia.com

Can you say more about what I should do here? Once I uninstall the Nvidia drivers, I reinstall the latest ones. Should I do something about the AMD iGPU? Should I install PhysX and GeForce Experience (they're currently installed)? After I uninstall the drivers, do I need to connect my monitor to the HDMI port of the motherboard, or will my Nvidia card still work?

I'm asking because I built this computer in kind of a weird way, because the secondary drive is seated under the GPU on the motherboard. So I installed Windows 11 with only one drive connected, then powered down, and connected both the second drive and the GPU. I'm wondering if that messed things up. But also I remember having to be connected to the motherboard's HDMI until I installed the Nvidia drivers.

zbook said:

4) Read this tutorial on Windows Driver Verifier:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Code:

Name    NVIDIA GeForce RTX 4080
PNP Device ID    PCI\VEN_10DE&DEV_2704&SUBSYS_13BB196E&REV_A1\4&D0BDF66&0&0009
Adapter Type    NVIDIA GeForce RTX 4080, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 4080
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_268e85175aa9e991\nvldumdx.dll
Driver Version    31.0.15.5212
INF File    oem31.inf (Section081 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_268E85175AA9E991\NVLDDMKM.SYS (31.0.15.5212, 57.26 MB (60,044,320 bytes), 4/7/2024 8:19 PM)

I read through the Driver Verifier link, but I'm not sure what to do about the CODE section you have here? Should I be using it somewhere?[/CODE]

sd522527 · May 7, 2024

zbook said:
There were four BSOD during the past 30 days.

Had you configured the settings to only use the Nvidia dGPU?

The AMD GPU was disabled when the V2 log collector ran on 05/06/2024.

Was the AMD iGPU disabled on 04/07 and / or 05/06 during the unexpected shutdowns and restarts?

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Tuneup files attached.

zbook · May 7, 2024

[/CODE] is a website menu feature

Code:

is a website menu feature

Several Nvidia drivers will be tried as needed to see if alternative drivers can fix the unexpected shutdowns and restarts including BSOD and the video idle time out.

When reinstalling the Nvidia GPU drivers please reinstall physx.

Don't reinstall GeForce Experience at this time.

The AMD iGPU will be turned on at a later time for testing purposes.

With the disabled iGPU plan to connect the monitor to the HDMI port of the motherboard.

After replacing the Nvidia dGPU drivers plan to stress test all non-Windows drivers.

When using WDV:

1) Create a new restore point

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

2) Learn the methods to recover from WDV BSOD by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

3) Only use system restore if both of above administrative command prompt commands fail to turn off the tool

4) Test all non-Microsoft drivers

5) Test no Microsoft drivers

6) Start WDV with the 3 customized test in the TF tutorial

7) Plan to use various customized tests during approximately 48 hours of testing

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

verifier /querysettings

Post a share link.

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

Tuneup plus results were good.

sd522527 · Monday at 3:09 PM

OK I have used DDU to uninstall then reinstall the latest NVIDIA drivers. I have had Driver Verifier running for about 1.5 days now, with these settings:

Code:

C:\Users\steph>verifier /querysettings

Verifier Flags: 0x00100610

  Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Verified Drivers:

    amdpsp.sys
    rtf64x64.sys
    ctiio64.sys
    amdsafd.sys
    mtkwl6ex.sys
    rt640x64.sys
    amdgpio2.sys
    amd3dvcache.sys
    amdgpio3.sys
    amdfendrmgr.sys
    amdfendr.sys
    rtkvhd64.sys
    atihdwt6.sys
    mtkbtfilterx.sys
    mt7612us.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    amdryzenmasterdriver.sys
    nvlddmkm.sys
    nvhda64v.sys

I let my computer go to sleep overnight, and just tried to wake it. The screen stayed black but the computer woke (similar to what's been happening). I switched my monitor to the HDMI port on the motherboard, and the computer instantly restarted. Looking in the event viewer, I see the following critical error:

Code:

Kernel-Power 41(63)
EventData

  BugcheckCode 270
  BugcheckParameter1 0x33
  BugcheckParameter2 0x0
  BugcheckParameter3 0x0
  BugcheckParameter4 0x0
  SleepInProgress 0
  PowerButtonTimestamp 0
  BootAppStatus 0
  Checkpoint 16
  ConnectedStandbyInProgress true
  SystemSleepTransitionsToOn 2
  CsEntryScenarioInstanceId 13
  BugcheckInfoFromEFI true
  CheckpointStatus 0
  CsEntryScenarioInstanceIdV2 13
  LongPowerButtonPressDetected false
  LidReliability false
  InputSuppressionState 0
  PowerButtonSuppressionState 0
  LidState 3

I also see the following volmgr error at exactly the same time as the above critical error:

Code:

volmgr 161
EventData

   \Device\HarddiskVolume5
   000000000100000000000000A10004C081000200010000C000000000000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00000000 00000001 00000000 C00400A1
0010: 00020081 C0000001 00000000 00000000
0020: 00000000 00000000   


In Bytes

0000: 00 00 00 00 01 00 00 00   ........
0008: 00 00 00 00 A1 00 04 C0   ....¡..À
0010: 81 00 02 00 01 00 00 C0   ......À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

There is also one driver error from when the computer was restarting:

Code:

   amd3dvcacheSvc
   CreateHelperUserProcess - WTSQueryUserToken Failed failed with 1008

There's also an error about not having Secure Boot enabled, which happened after the critical error above.

I never actually got a BSOD, so I'm not sure how to tell what's going wrong. Driver Verifier is still running, and I see no events related to it in Event Viewer.

Questions:

Should I enable Secure Boot?
Should I be worried about the amd3dvcachesvc error?
Could this volmgr error be related to the kernel-power error?

zbook · Monday at 3:13 PM

Please post a new V2 share link into the newest post

sd522527 · Monday at 3:21 PM

Whoops, sorry, attached to this post.

zbook · Monday at 4:08 PM

Please restart WDV with these customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00080000 DDI compliance checking (additional).

Test all non-Microsoft drivers

Test no Microsoft drivers

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

verifier /querysettings

Post a share link.

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

sd522527 · Monday at 4:18 PM

Sorry, can you confirm I should have those items checked or leave them unchecked?

sd522527 · Monday at 4:31 PM

OK I opened driver verifier and set those options. On rebooting, I got a BSOD for PAGE_FAULT_IN_NONPAGED_AREA. Attached is the V2 logs.

I also noticed that my previous settings for Driver Verifier were still set. So I will now disable Driver Verifier, then re-enable with only those settings in the above post.

Code:

C:\Users\steph>verifier /querysettings

Verifier Flags: 0x001a0fbb

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [X] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.all

  Verified Drivers:

    amdpsp.sys
    rtf64x64.sys
    ctiio64.sys
    amdsafd.sys
    nvlddmkm.sys
    mtkwl6ex.sys
    rt640x64.sys
    amdgpio2.sys
    amd3dvcache.sys
    amdgpio3.sys
    amdfendrmgr.sys
    amdfendr.sys
    nvhda64v.sys
    atihdwt6.sys
    rtkvhd64.sys
    mtkbtfilterx.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    mt7612us.sys
    amdryzenmasterdriver.sys

sd522527 · Monday at 4:41 PM

On disabling Driver Verifier, I got another BSOD on restart. On setting the values below, I did not get a BSOD on restart.

Code:

C:\Users\steph>verifier /querysettings

Verifier Flags: 0x001a09ab

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [X] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.all

  Verified Drivers:

    amdpsp.sys
    rtf64x64.sys
    ctiio64.sys
    amdsafd.sys
    nvlddmkm.sys
    mtkwl6ex.sys
    rt640x64.sys
    amdgpio2.sys
    amd3dvcache.sys
    amdgpio3.sys
    amdfendrmgr.sys
    amdfendr.sys
    nvhda64v.sys
    rtkvhd64.sys
    atihdwt6.sys
    mtkbtfilterx.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    mt7612us.sys
    amdryzenmasterdriver.sys

zbook · Monday at 5:53 PM

Uninstall and reinstall:

mtkbtfilterx64 MTK BT Filter Driver c:\windows\system32\drivers\mtkbtfilterx.sys

Restart WDV with the same settings.

sd522527 · Monday at 6:35 PM

OK I uninstalled the BT device from Device Manager, and removed the driver(s). Then reinstalled from the ASRock website.

Have now turned on Driver Verifier and restarted, no BSOD:

Code:

C:\Users\steph>verifier /querysettings

Verifier Flags: 0x001a09ab

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [X] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.all

  Verified Drivers:

    amdpsp.sys
    rtf64x64.sys
    ctiio64.sys
    amdsafd.sys
    nvlddmkm.sys
    mtkwl6ex.sys
    rt640x64.sys
    amdgpio2.sys
    amd3dvcache.sys
    amdgpio3.sys
    amdfendrmgr.sys
    amdfendr.sys
    nvhda64v.sys
    rtkvhd64.sys
    atihdwt6.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    mt7612us.sys
    amdryzenmasterdriver.sys
    mtkbtfilterx.sys

zbook · Monday at 6:45 PM

Please restart WDV with these customized tests:

Code:

    [ ] 0x00000010 I/O verification.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

sd522527 · Monday at 6:56 PM

OK, restarted Driver Verifier. No BSOD yet, will let it run for a while and attempt to wake my PC later tonight. Thanks for the help so far!

zbook · Monday at 8:58 PM

Please post a new querysettings share link.

Restart WDV with all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.

For no immediate BSOD post a new querysettings share link.

For any BSOD post a new V2 share link.

Run WDV for approximately 12 - 24 hours.

Make sure that the tool is off by running querysettings.

If there are no new BSOD then that will complete the troubleshooting.

sd522527 · Wednesday at 9:51 AM

Here is my current querysettings:

Code:

C:\Users\steph>verifier /querysettings

Verifier Flags: 0x03b5e010

  Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [X] 0x00002000 Invariant MDL checking for stack.
    [X] 0x00004000 Invariant MDL checking for driver.
    [X] 0x00008000 Power framework delay fuzzing.
    [X] 0x00010000 Port/miniport interface checking.
    [X] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [X] 0x00200000 NDIS/WIFI verification.
    [X] 0x00800000 Kernel synchronization delay fuzzing.
    [X] 0x01000000 VM switch verification.
    [X] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    ndis: rules.default

  Verified Drivers:

    amdpsp.sys
    rtf64x64.sys
    ctiio64.sys
    amdsafd.sys
    nvlddmkm.sys
    mtkwl6ex.sys
    rt640x64.sys
    amdgpio2.sys
    amd3dvcache.sys
    amdgpio3.sys
    amdfendrmgr.sys
    amdfendr.sys
    nvhda64v.sys
    atihdwt6.sys
    rtkvhd64.sys
    mtkbtfilterx.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    mt7612us.sys
    amdryzenmasterdriver.sys
    ndis.sys
    netadaptercx.sys
    mbbcx.sys
    wificx.sys
    wdiwifi.sys

Now going to run it with everything but Randomized low resources simulation.

sd522527 · Friday at 1:20 AM

I was going to come here and post how I haven't had a BSOD at all, but as I woke my computer to make that post, the screen stayed black and I had to reset again

I've posted the V2 logs attached.

Here are my current WDV settings:

Code:

C:\Users\steph>verifier /querysettings

Verifier Flags: 0x03bfefbb

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [X] 0x00002000 Invariant MDL checking for stack.
    [X] 0x00004000 Invariant MDL checking for driver.
    [X] 0x00008000 Power framework delay fuzzing.
    [X] 0x00010000 Port/miniport interface checking.
    [X] 0x00040000 Systematic low resources simulation.
    [X] 0x00080000 DDI compliance checking (additional).
    [X] 0x00200000 NDIS/WIFI verification.
    [X] 0x00800000 Kernel synchronization delay fuzzing.
    [X] 0x01000000 VM switch verification.
    [X] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.all
    ndis: rules.default

  Verified Drivers:

    amdpsp.sys
    rtf64x64.sys
    ctiio64.sys
    amdsafd.sys
    nvlddmkm.sys
    mtkwl6ex.sys
    rt640x64.sys
    amdgpio2.sys
    amd3dvcache.sys
    amdgpio3.sys
    amdfendrmgr.sys
    amdfendr.sys
    nvhda64v.sys
    rtkvhd64.sys
    atihdwt6.sys
    mtkbtfilterx.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    amdryzenmasterdriver.sys
    mt7612us.sys
    ndis.sys
    netadaptercx.sys
    mbbcx.sys
    wificx.sys
    wdiwifi.sys