IF DV crashes before you get into your desktop, you must have applied it improperly.
Disable it in safe mode. Then boot normally and enable it again, make it sure that you are not checking any drivers provided by microsoft.
Do it slowly, following all the steps of the tutorial very properly. Otherwise DV will not come in any help
No, I applied it properly(and very slowly) I turned it off then back on again(this time making absolute sure that no windows or Microsoft drivers were selected and it still wont boot without blue screening(the error that come up is driver is trying to access memory after it has been freed, or something like that)
Found in Problem Devices:
1. CDC Serial USB\VID_04E8&PID_6860&MI_01\6&8B945D1&0&0001 The drivers for this device are not installed.
2. SAMSUNG_Android_SGH-T999 USB\VID_04E8&PID_6860&MI_03\6&8B945D1&0&0003 The drivers for this device are not installed.
3. Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.
Install the drivers for these devices - Keep us Posted
Well, there is a different set of instructions, you may try it:
Using Driver Verifier to identify issues with Drivers
It's actually the same instructions, just from the command line..... Also, I went to the driver verifier thread, posted the BSOD i'm getting, and told them you said I was doing something wrong.... The reply I got from Vir Gnarus was as follows:
"I'm not understanding why they're saying that. Driver Verifier is designed to cause BSODs by adding extra driver checks in Windows, making it more paranoid to possible bugs. The bugcheck code I see in that bluescreen snapshot you made does show a 0xC5 crash, which was made by Driver Verifier, meaning it found a driver doing something erroneous and it crashed the system in response. Often it may do this at startup when the driver loads because when the driver loads up it may already have a bug in the works, which DV will detect and respond. You'll want to go to the thread you made and post the resulting crashdumps from the crashes that DV made. Those DV-created crashdumps are more reliable than regular ones."
I would be more than happy to post the crash dumps for this BSOD again as long as you are going to help me with my problem instead of telling me i'm doing something wrong when the program is doing exactly what it's supposed to do...
Quote