Intel to AMD, MBR to GPT, Secure Boot Windows UEFI + CSM Disabled BSOD

zbook said:

Please keep secure boot off so that you can boot using the MCT > RE > command prompt > verifier /reset

Click to expand...

zbook said:

Please keep secure boot off so that you can boot using the MCT > RE > command prompt > verifier /reset

Click to expand...

frenzy said:

For some reason I was unable to actually cancel verifier via "verifier /reset" by using the MCT created.

Click to expand...

frenzy said:

The command prompt window I would open kept telling me there were no drivers being verified when I tried the query command. Nor did it stop running driver verifier when I attempted to reset.

I had to reset by bluescreening my PC 3 times in a row and then enter safe mode and then disable it that way.

Click to expand...

frenzy said:

The bluescreen error I would get on startup would always be "System Thread Exception not.."

Click to expand...

zbook said:

verifier /reset and / or verifier /bootmode resetonbootfail are used to turn off WDV

If these fail to turn off the tool then system restore.

If all three fail to turn off the tool then restore a backup image.



This is the hard boot method to get into safe mode per the tutorial.




For any BSOD post a V2 share link.

Click to expand...

zbook said:

Please post a new V2 share link into the newest post:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

Click to expand...

zbook said:

1) Identify any Logitech hardware.



2) If available, temporarily use alternative hardware.



3) Uninstall or uninstall and reinstall:

logi_joy_vir_hid Logitech G HUB Virtual HID Device Driver c:\windows\system32\drivers\logi_joy_vir_hid.sys



4) If possible, uninstall all Logitech drivers.



5) 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

6) Create a new restore point.



7) 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).

Click to expand...

zbook said:

1) Identify any Logitech hardware.



2) If available, temporarily use alternative hardware.



3) Uninstall or uninstall and reinstall:

logi_joy_vir_hid Logitech G HUB Virtual HID Device Driver c:\windows\system32\drivers\logi_joy_vir_hid.sys

logi_joy_bus_enum Logitech G HUB Virtual Bus Enumerator Driver c:\windows\system32\drivers\logi_joy_bus_enum.sys



4) If possible, uninstall all Logitech drivers.



5) 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

6) Create a new restore point.



7) 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).

Click to expand...

zbook said:

All of the test settings are customized for each run.


See part 2:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Click to expand...

zbook said:

How did you run it the first time?


The computer user launches the WDV tool then checks boxes for:
a) drivers
b) tests


These are various tests:

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.

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

For the next run of WDV check the boxes for 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).

Click to expand...

zbook said:

The tool is most frequently used by Graphical User Interface (GUI).
It can run using command prompt too.

Click to expand...