Windows 10: bugcheck and verifier detected violation at win10 startup

Hello again, turns out my problem wasn't fixed by updating my BIOS and chipset. Bugcheck was happening randomly, sometimes a dozen hours later.Using Verifier I cannot access win10, but I can reach safemode to disable it.Here are all the things I collected: minidump, memory dump, msinfo32, and driverview:https://drive.google.com/drive/folders/1BQWu66qSHMkcjbOuttCasMa-Mh22rUWr?usp=sharingCan you tell me what driver/s cause this problem? Thanks a lot for your help.

:)

 

Unable to start Win10 - 0xc000021, also "Driver Verifier Detected Violation"

OK, I started having a problem booting win10, getting a 0xc000021 error and the only way I could out of that was using the bootup/troubleshooting menu/advanced options/startup settings option 7 "Disable driver signature enforcement".

When I was finally in windows (logged on as Administrator) I ran "Verifier" and select all drivers (except Microsoft drivers) to try to find out whether there was a bad driver and then rebooted the PC (it's a home-build with ASUS 990x motherboard (I think)
and AMD 6-core cpu).

Now it fails to load Win10 with "Driver verifier detected violation" immediately on reboot and there is nothing I can do to make windows load up. I tried going into the command prompt from the troubleshooting menu and running "verifier /reset" and also running
verifier to get the verifier window then selecting to remove all settings, and still I can't start up. If I try to use the "Disable driver signature enforcement" method it fails with the "Driver verifier detected violation" error even though I tried to reset
it in command prompt, and if I try to start in safe mode I get 0xc000021.

NOTE: when I use the command prompt option, it puts me in directory tree "X:\windows\system32", which seems weird.

Is there any way I can get verifier to stop detecting violations - or, why is verifier still deteting violations even though I've tried to reset it?

I am absolutely NOT interested in any option that involves resetting windows as there are a LOT of files and apps I really don't want to lose.

HELP!

 

Driver verifier detected violation

Hi Ridhwan,

We suggest you check out ZigZag3143's recommendations from the following links:

Driver Overran Stack Buffer

Driver Verifier Detected Violation

You may also check out the link to
Troubleshoot blue screen errors to address the problem.

Let us know how it goes so we can further assist you.

Regards.

 

Driver verifier detects a violation in win32kbase.sys

In driver verifier with all of the "Standard" tests enabled, my F1A75-M motherboard & A8-3850 cpu based system bluescreens with stopcode DRIVER_VERIFIER_DETECTED_VIOLATION (0xC4) in win32kbase.sys. Winver is Windows 10 1803 17134.48.

With slightly more blue screen info enabled, it writes at the top left:

Code:

0x00000000000020000xFFFF82107C888F630x00000000000000000x00000000616C6947
Bugcheck [url='https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xc4--driver-verifier-detected-violation']
Parameter 1 = 0x2000 in this context[/url] is supposed to mean there is a problem with StorPortInitialize in the storage miniport driver. Of which I only have Microsoft's own storahci.sys loaded. No dumpfile is written, which seems normal if the storage driver
 is keeling over.

With win32kbase.sys unchecked in driver verifier (same standard tests), my system boots fine.

I have 4 third party drivers on my system:

• AMD's usbfilter.sys (up to date)
• Nvidia HDMI audio: nvhda64v.sys
• Nvidia Graphics: nvlddmkm.sys
• network driver: L1C63x64.sys

How do I go about debugging this? I'll be running SFC and DISM.