New
#11
EDITED: Double post by mistake...
EDITED: Double post by mistake...
System are now Specs Updated!
Driver Verifier is coming back with a bluescreen on dgmbx2fu.sys Looks like my M-Audio interface is the culprit... However, now I am stuck in a boot loop and I have tried everything in the instructions to disable Driver Verifier. Nothing is working
Fixed the bootloop by just restoring back to my restore point. I will uninstall my mbox and then try to re-verify. Still need to figure out whats causing the memory management bsod.
Got to windows login. when logging in got BSOD for IOmap64.sys (verifier is turned on)
Please run the DM log collector and upload a new zip.
Please don't yet disable verifier, in case there are more drivers.
Since I'm in Verifier mode, I cant run the DM log collector because it bluescreens everytime i try to log in. I have no option to boot to safe mode... The only thing i am able to do right now reboot with recovery media (usb) and get into the setup and recovery menu, however i cant restore to a previous point because it keeps asking me to specify what installation of windows i am restoring to, and it never lets me choose.... I have also tried to turn off verifier mode so i can boot into windows and it will not turn off. I'm literally stuck unless i wipe my computer it seems.
Have you tried?
It is not really clear to me what you mean with 'verifier mode'.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
I have tried that and it will not turn off Verifier. I have tried:
verifier /bootmode resetonbootfail
verifier /reset
I have also tried going into startup settings and turning of driver verification in safe mode. Nothing works.
It just keeps failing on IOMap64.sys under the driver verification BSOD. I cant turn the driver verification off.
The only thing left for me to try is a system restore. But that would not leave the logs from the BSOD for me to upload.