Windows 10 Driver Verifier BSOD loop.. how to get out of it?

Hi,

I realize that you are facing issues with BSOD loop. Sorry for the inconvenience this has caused.

Troubleshoot blue screen errors:

http://windows.microsoft.com/en-in/windows-10/troubleshoot-blue-screen-errors

Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION

https://msdn.microsoft.com/en-us/library/windows/hardware/ff560187(v=vs.85).aspx?ppud=4

You may follow the below methods and check.

Method 1: Unplug all external devices like flash drive, printer, scanner etc., connected to the laptop and restart the system to check if you are able to get to the desktop screen.

Method 2: If you are not able to get to the desktop screen, I suggest you to run Startup repair from Advance boot option.

It may ask you to insert the Installation DVD/USB while doing startup repair.

If you don’t have an installation media, you have to create an installation media for that.

You may download an ISO from the below link:

https://www.microsoft.com/en-us/software-download/windows10

Once your media is ready follow the steps.

• After you boot your computer using Windows 10 CD/ DVD or System Repair Disc, a black screen appears with gray text "Press any key to boot from CD or DVD". Press any key.

• Select the correct time and Keyboard type.

• Click on Repair your computer in the lower left corner.

• Select Troubleshoot from Choose an option screen.

• Click on Advanced options in Troubleshoot screen.

• Click on Automatic Repair from Advanced Options screen.

• Next, choose the operating system by clicking on its button.

• Windows 10 will look for problems on hard drive(s) and verify that all required files are intact.

You may try the given suggestions and check if it helps.

Thank you.

HI Deepak

thanks for the reply.

on running startup repairs, after a minute or so it gives me dialog box error

StartRep.exe - Application Error

the instruction at 0x00007FF84AC17C5C referenced memory at 0x00000000008. The memory could not be read.

click ok to terminate the program.

and then it goes back to troubleshoot

I ran Chkdsk /f /r and it fixed some errors in free space but didnt change the startup repair above.

SFC /Scannow gave me a 'windows resource protection could not perform the requested operation'

Then I ran sfc /scannow /offbootdir=c:\ /offwindir=c:\windows it gave the result Windows resource protection did not find any integrity violations.

Also i went into command prompt and tried verifier /bootmode resetonbootfail

it asked me to reboot but still ran verifier as if nothing has changed

Hi,

Sorry for the delayed response.

You may try the below steps to rebuild BCD (boot configuration data) and check if it helps.

1. Insert the Windows 10 DVD and restart your computer
2. Boot from the DVD.
3. Choose your language and click Next.
4. Click Repair Your Computer and then select Command Prompt and try the following commands:
bootrec /fixMBR
bootrec /fixBoot
bootrec /rebuildBCD

Restart the computer.

Disclaimer: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.      

You may try the given suggestion and get back with the results.

Thank you.

Though I also was stuck in a Verifier BSOD loop, in my case I had to log in before an unavoidable BSOD occurred.  (The boot drive is a SSD with legacy BIOS, not UEFI, but  I also could not break the loop using function keys.)  However, after two successive failures, on the third try the ongoing problem was detected by Windows, and I was offered alternatives - one of which was to change startup options, which, after reboot, allowed me to select Safe Mode.  I was then able to "run" "Verifier" and select the option to delete all current settings. This stopped the Verifier itself from producing BSOD and broke the loop, allowing a normal reboot.  I am now attempting to see whether the driver the Verifier failed on is what was causing problems.  If Microsoft has no correction to Verifier application forthcoming, they may still be able to change the default settings behind the scenes in the visual menu to run Verifier only one time.  This is an option in the command line version.

I just got back to windows in safemode with Network and deaktivated verifier again.