incompatibility problem with windows defender offline and windows driver verifier

Z

zbook

Member
Joined
Oct 2, 2015
Posts
919
I currently have two computers that have blue screened that I cannot move into the advanced troubleshooting for safe mode with administrative command prompt after using two Microsoft windows software programs. Can someone check to see whether they experience the same incompatibility. If you do find the same incompatibility please indicate how you might be able to prevent the blue screen triggers and loop. Also please indicate how you return to your desktop after the incompatibility loop.

The two windows programs are:
1)Windows driver verifier
2)Windows defender offline

The first computer had its internal hard drive sanitized. The bios was changed from legacy to UEFI native without CSM. The windows 10 professional operating system was freshly installed. Drivers were freshly installed too. Using Microsoft windows driver verifier the new os and drivers blue screened with stop code driver verifier detected violation. Having a newly installed os and drivers followed by a driver verifier detected violation I checked many other computers and all computers using windows driver verifier produced blue screens.

To return from windows driver verifier produced blue screens to the windows desk top the advanced troubleshooting menu was used. Using start up options then safe mode with command prompt verifier /reset turned the windows verifier off. This was followed by shutdown -r. The wall paper or lock screen moved to the log on screen and then to the desktop. This so far was normal windows driver verifier processing.

While looking up the multiple stop codes the computers had Microsoft windows defender full scans. Once the full scans completed the computers had windows defender offline scans. In the windows defender settings menu is the option to click on offline scan. The offline scan is supposed to run once. It requires a reboot. There is no setting to repeat the windows defender offline scan. This so far was normal for windows defender offline.

The windows driver verifier was then used again to recheck the drivers. I had planned to use control panel to remove problematic drivers and then download new drivers from the HP web site.

Once windows driver verifier was used after windows defender offline the computer went into a loop. There was no option to break the loop by going into advanced troubleshooting. Windows defender offline appears to be incompatible with any computer that has a blue screen produced by windows driver verifier. The windows defender offline and the windows driver verifier both interact during the reboot. The windows defender was not supposed to be active after it completed the first offline scan. Somehow though the windows driver verifier triggers the running of the windows defender offline. Thus the incompatible loop is created.

A power off from a blue screen followed by power on went to a display with a HP icon followed by a display with a windows icon and preparing automatic repair followed by a flash on the screen with a box or rectangle then a windows defender offline load with a moving green bar followed by a windows defender offline scan. The typical windows offline scan on this computer took approximately 2 minutes. The first windows defender offline scan in the video was cancelled. Then it moved to a display with the hp icon and then to a display with the windows icon with preparing automatic repair. Then it displayed the windows driver verifier produced blue screen with stop code driver verifier detected violation.

Then power off and power on led to a a display with a HP icon followed by a display with a windows icon and preparing automatic repair. This was followed by a flash on the screen with a box or rectangle then a windows defender offline load and then scan. This scan was completed and took approximately 2 minutes. Then another blue screen with the windows driver produced blue screen with stop code driver verifier detected violation.

Then a power off and on led to a display with a hP icon then a display with a windows icon and preparing automatic repair. The display with windows icon and automatic repair always moved to the screen flash with a box or rectangle followed by a windows defender offline scan load and then windows defender offline scan. When the scan was completed or canceled it always went to the driver verifier produced blue screen with stop code driver verifier detected violation.

The typical method that I had used to turn off driver verifier before the incompatibility was in this sequence of displays: preparing automatic repair to diagnosing your PC to automatic repair windows couldn't load correctly, the option cancel was selected, and this was followed by the windows icon with automatic repair, then automatic repair couldn't repair your PC with log file at C:\windows\system32\logfiles\srt\srttrail.txt, then advanced options, then troubleshoot, then advanced options, then start up options, then restart, then choosing number 6, then safe mode with command prompt, then entered verifier /reset, then entered shutdown -r

All of my computers had blue screens with driver verifier. And each computer that later had a run of windows defender offline went into a blue screen/windows defender offline loop if windows driver verifier was run after a windows defender offline scan. If the first run of windows driver verifier does not produce a blue screen I don't know if there is an incompatibility problem after running a windows defender offline. It has only happened with computers that blue screen with windows driver verifier.

If you can please check to see whether you find an incompatibility problem with windows driver verifier and windows defender offline.

At one time I had sanitized an internal drive from the bios but dont remember what can or cannot be done to an internal SSD. On one computer with this incompatibility problem with windows defender offline and windows verifier the internal SSD drive could be formatted or overwritten and the windows 10 professional could be installed from a recovery disk. I was unable to find my usb drive windows iso but can purchase another flash drive and download the os onto the flash drive and then install the os.

The other computers are more critical as they have important files and all of them had windows defender offline scans. They have internal hard drives or SSD drives with files that have not yet been saved to another drive. What can be done with these computers so that I could use driver verifier again and fix the problematic drivers discovered by windows driver verifier? Does turning off real time protection prevent the incompatibility? And if they have incompatibility loops how can movement to advanced troubleshooting be made to turn off driver verifier and return to the desktop? If this becomes impossible what are the alternatives?
 
It's normal to see driver verifier bosd on Microsoft drivers, that is why we have op's exclude all MS drivers when running verifier.

The only way I know to quickly get it back to normal is by using a restore point which you should have created before starting verfier.
 
When the windows driver verifier was used all non-Microsoft drivers were checked and all Microsoft drivers were unchecked.

Every computer displayed an immediate blue screen.

The stop codes were:

driver verifier detected violation (alone, or no additional information provided about the violation)
driver verifier detected violation hpdskflt.sys
driver verifier detected violation sddtoki.sys
driver verifier detected violation soluto.sys

all of the above were on the driver list except sddtoki.sys

Some of the computers that produced blue screens with driver verifier did not update the mimidump or memory.dmp files
The sytem defaults were changed to see if this could more frequently record the blue screens. In startup and recovery settings small memory dump (256) was changed to automatic memory dump. Automatically restart was unchecked. The dump file was not changed and remained %systemroot%\memory.dmp.

Even with the above changes many of the driver verifier produced blue screens were not showing up in the memory.dmp file.

A few of the computers had whocrashed which provided additional information about the windows driver verifier stop code driver verifier detected violation that had no additional information. For this one whocrashed processed c:\windows\mindump and found cvirtualdrive.sys

For this problematic driver I could uninstall and reinstall cyberlink. The problem is that I cannot rerun windows driver verifier to see if there is a third driver on this computer or any additional drivers that need to be fixed. This computer and all the other computers had the windows defender offline scan. Using the windows driver verifier after using windows defender offline likely will go into the blue screen/windows defender offline loop and make the computer unusable.

There was some information about paging files and minidump or memory.dmp files that I did not understand. The computers have 8 to 32 gb of ram. The paging file size on the computers viewed varies from 1024 to 4864. The default settings have never been changed. Is this something that needs to be manually changed to increase the probability that minidump and memory.dmp files will be updated for each blue screen? If so what are the steps?

The computer in the initial post, the first computer is now in the Microsoft store. There were three restore points and none of them work. They were able to get to the restore points only by using a usb drive with windows iso. They said that they would save the files and reinstall the windows 10 professional operating system, drivers, files, office, etc

It appears that other people have been having problems with windows defender offline. This one was on Microsoftanswers: Windows 10 Defender Offline stuck in infinite restart loop - Microsoft Community

The second computer that is stuck in the windows driver verifier/windows defender offline incompatible loop has no important files. I have a windows 10 professional recovery disk and can insert it into the optical drive.

For all of the other computers I could attempt to fix the blue screen stop codes by deleting drivers. The problem is that I cannot check to see if it was effective as running windows driver verifier again is likely to put the computers into the incompatibility loop. The first computer above had three restore points that were created within one week of the incompatibility loop and none of them worked.

I wonder whether temporarily turning off windows defender may prevent the incompatibility loop?

If not I am seeking other options to be able to get back to a working computer.
 
The post that I made earlier had links within it that I did not read until just now.
One of the links calls it a boot loop.
The problems that I am having with multiple computers are related to using the windows driver verifier after the windows defender offline or WDO.
None of the advanced troubleshooting options were available with three boots.......each time it went to the WDO.
The microsoft store had a usb flash drive with windows iso as was unable to to use the repair options.
The second computer that is in the loop can be fixed by reinstalling the operating system with the recovery DVD.
The problems are all of the other computers that had WDO. They all had blue screens with windows driver verifier. One of them had already one driver uninstalled and a second problematic driver appeared with windows driver verifier.
So I am looking for a strategy to be able to do preventative maintenance with the windows driver verifier. Two computers had blue screens before all of the incompatibility loops.

This is the link within the earlier microsoftanswers link: Windows 10: Defender Offline Scan boot loop – Part 2 | Born's Tech and Windows World
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top