Solved BSOD after configuring WDV (CRITICAL_PROCESS_DIED)

jbcarreon123 · Jan 31, 2022

Hi, If you want to see the configuration, see this thread:

Not your normal BSOD post

Is it just me or does 11 seem to have less crashes than 10? I havent had one in 10 or 11 in years, knock on wood, but does 11 behave a little better? Less user base yet making it seem less? If this should be somewhere else, feel free to move :)

www.elevenforum.com

I created this thread because I'm not the OP of that thread.

jbcarreon123 · Jan 31, 2022

zbook · Jan 31, 2022

The last BSOD dump file collected was from 1/25.

Please continue with WDV testing.

jbcarreon123 · Jan 31, 2022

zbook said:
The last BSOD dump file collected was from 1/25.

Please continue with WDV testing.

It may be because of the system restore.

I will replicate this but with /bootmode resetonbootfail later.

zbook · Jan 31, 2022

The files often disappear with system restore so whenever possible run the reset and resetonbootfail commands.

zbook · Jan 31, 2022

Restart with only the two DDI customized tests.

0x00020000 DDI compliance checking
0x00080000 DDI compliance checking (additional)

jbcarreon123 · Jan 31, 2022

zbook said:
The files often disappear with system restore so whenever possible run the reset and resetonbootfail commands.

How do I run the verifier /reset on a Windows 11 install media (WinRE)
It shows No settings were changed.

zbook · Jan 31, 2022

See:

Option One:
Disable Driver Verifier via Command Prompt

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

jbcarreon123 · Jan 31, 2022

Hi. I replicated the problem, and this is the V2 logs.

It looks like the fault is osfdisk.sys, Uninstalled OSFMount, and configured WDV again.

zbook · Jan 31, 2022

Please run:
Gather_additional_dump_files.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.

The last BSOD dump file was from 1/25.
The last livekernel dump file was from 1/24.

So no new files yet.

Please continue with the various customized tests.

When planning to sleep run Memtest86+ version 5.31b

Memtest86+ | The Open-Source Memory Testing Tool

Memtest86+ is an advanced, free, open-source, stand-alone memory tester for 32- and 64-bit computers (UEFI & BIOS supported)

www.memtest.org

Run one test for greater than eight passes.
Please post both images or share links into this thread.

jbcarreon123 · Jan 31, 2022

I run the WDV customized test, and you guessed again, BSOD!

Today, it leaves a dump file. I will provide V2 logs as soon as possible.

jbcarreon123 · Jan 31, 2022

zbook · Jan 31, 2022

Please uninstall Vbox and continue WDV testing.

Add more customized tests.

Once WDV testing is completed you can reinstall Vbox.

If you absolutely need it you can install it before the completion of WDV testing.

If there are no performance problems or very slow boot then add:

Code:

    [ ] 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.

jbcarreon123 · Feb 2, 2022

zbook said:
Please uninstall Vbox and continue WDV testing.

Add more customized tests.

Once WDV testing is completed you can reinstall Vbox.

If you absolutely need it you can install it before the completion of WDV testing.

If there are no performance problems or very slow boot then add:

Code:

[ ] 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.

Code:

C:\Users\jbcarreon123>verifier /querysettings

Verifier Flags: 0x001fe610

  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.
    [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).
    [ ] 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:

    Resetonbootfail

  Rules:

    All rules are explicitly disabled.

  Extensions:

    wdm: rules.all

    Options: logging

  Verified Drivers:

    osfdisk.sys
    igdkmd64.sys
    athw8x.sys
    rt640x64.sys
    vbaudio_vmvaio64_win10.sys
    vbaudio_vmauxvaio64_win10.sys
    vbaudio_cable64_win7.sys
    rtkvhd64.sys
    dump_diskdump.sys
    dump_storahci.sys
    dump_dumpfve.sys
    sbiedrv.sys
    semav6msr64.sys

C:\Users\jbcarreon123>

Already tested beyond 3 hours. I can disable it or add other ones?
I enabled it yesterday before shutdown (not Fast Startup), and because it used as a youtube machine, and YouTube 720p (not 60fps) does not affect PCs performance.

zbook · Feb 2, 2022

Please test for an additional 36 hours using:

Code:

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

If there are no BSOD with the above tests running in the background then that will complete the troubleshooting.

jbcarreon123 · Feb 2, 2022

zbook said:
Please test for an additional 36 hours using:

Code:

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

If there are no BSOD with the above tests running in the background then that will complete the troubleshooting.

already running beyond 5 hours.

ShamrockRig · Feb 2, 2022

zbook said:
Please test for an additional 36 hours using:

Code:

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

If there are no BSOD with the above tests running in the background then that will complete the troubleshooting.

36 hours holy crap on a cracker, Full pc stress tests take less than this xD
I do trust you're info though and im sure theres a reason, But what could possibly happen in 36hrs that wouldnt happen in say 24hrs? From an info point not poking at youre methods, I just like to learn

zbook · Feb 3, 2022

If there are no performance problems and very slow boot please reinstall Vbox if needed and restart WDV with these customized tests:

Code:

    [ ] 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.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

zbook · Feb 3, 2022

Devlin1888 said:
36 hours holy crap on a cracker, Full pc stress tests take less than this xD
I do trust you're info though and im sure theres a reason, But what could possibly happen in 36hrs that wouldnt happen in say 24hrs? From an info point not poking at youre methods, I just like to learn

Most often problems are detected with short runs but at times misbehaving drivers can be missed.

The longer the continuous use the better the testing environment as the end user may use different software.

If there are no performance problems then WDV can run for long periods of time in the background.

Almost always using 48 hours of varied customized tests followed by 36 hours continuous run completely rules out misbehaving drivers.

jbcarreon123 · Feb 3, 2022

Another BSOD!
I will provide (again in the third time) a V2 log so you can look with it

Solved BSOD after configuring WDV (CRITICAL_PROCESS_DIED)

Well-known member

My Computer

Well-known member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

R H Semi Erin Go Bragh

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Similar threads