BSOD after Sleep

Thanks zbook. To late tonight to start this. I will also get a full macrium before I start.

I'm taking from this, and I saw one thread, that if turned on I may not be able to disable.

Is this because one can't get Windows started or because Verifier is buggy and just doesn't disengage?

I looked and I counted roughly 34 non MS drivers. Thinking maybe I do 12 at a time.

zbook, in post 10 of this thread you have a typo.

​


Could you edit/correct in case someone else follows these instructions.

Thanks

So I fired up verifier this morning. All 34 non MS drivers included - 3 tests enabled. Have a look. Not sure if I have this right as nothing seems very stressed ( CPU, Disk)

Code:

Microsoft Windows [Version 10.0.19044.1706]
(c) Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>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:


    iastorac.sys
    mvs91xx.sys
    mvxxmm.sys
    pwdrvio.sys
    cimfs.sys
    saskutil64.sys
    sasdifsv64.sys
    asio2.sys
    asupio.sys
    igdkmd64.sys
    teedriverw10x64.sys
    mv91cons.sys
    e1d68x64.sys
    corsairvbusdriver.sys
    intcdaud.sys
    leqdusb.sys
    lhideqd.sys
    lhidfilt.sys
    lmoufilt.sys
    dump_diskdump.sys
    dump_secnvme.sys
    dump_dumpfve.sys
    mbamchameleon.sys
    mbamswissarmy.sys
    mwac.sys
    farflt.sys
    mbae64.sys
    mbam.sys
    iomap64.sys
    mv_process.sys
    semav6msr64.sys
    corsairvhiddriver.sys
    corsairllaccess64.sys
    cpuz153_x64.sys


C:\WINDOWS\system32>

Just so I don't screw this up I want to review how I add tests.

Is it basically open the app again and run through process. I assume the three test I have enabled would show enabled and I would just checked off so many more.

Is there any preferred order to add or just start at top of list and pick 4-6?