Windows 10: Driver Verifier Detected Violation: WUDFRd.sys failed

Hello,


I have been having some blue screens on my computer when is has been idling for a bit.

I have tried tracking it down my self but have not had much luck.


I have ran the Driver Verifier and it blue screened on start up (after BIOS screen but before Windows screen).

Said driver was WEDFRd.sys.


In the Linc to the folder below I have included the zip of the past 3 minidump files, first 2 were normal crashes after leaving computer for a while, and the 3rd is with the Driver Verifer.

Also include is the MSinfo and the system specs.


https://drive.google.com/drive/folders/1mc3tWabK6dCVLU_cD1MpnFcv1wOLkCND?usp=sharing


Thank you,


Michael

:)

 

DRIVER VERIFIER DETECTED VIOLATION (FSPFltd2.sys)

When i reset my lap without backup then. DRIVER VERIFIER DETECTED VIOLATION (FSPFltd2.sys)

It continuously showing when i power on my lap

I tried all the things but i don't get my solution

Please help me to solve

**Post moved by the moderator to the appropriate forum category.**

 

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.