Windows 10: BSOD Driver verifier detected violation

recent problems with bsods forced reinstallation of Win10. Similar problem this morning with System Service Exception ( no specific file). Then it changed to Driver verified violation but still rebooted. Ran DISM and sfc, no errors. Checked device manager for errors and drivers for updates. Created restore point and opened Driver Verifier. Followed your reccomendations for use but when I restarted Windows it wouldn't open. Through Advance Options I tried to 'restore' but recent restore points didn't work.

How can I restart? How can I access dump log files? Will Verifier still be 'on', if so how can I turn it off?

:)

 

BSOD - DRIVER VERIFIER DETECTED VIOLATION - AsusPTPFilter.Sys

Hello

I have an Asus ROG GL553VE , after the last windows 10 update 1803 I started to get the computer completely frozen seconds after loading to the actual gameplay of the games sometimes with a static noise and/or image starting to get white or parts of the
screen going static. Here it is what i tried so far :

• Rollback NVIDIA graphic drivers - Didn't work
• Rollback Windows 10 to 1703 - Didn't Work

What I have seen in some cases is that online games I get the screen frozen and the only to get out of it is to hard shut down on the power button of the laptop, in offline games I got the following BSOD:

• page_fault_in_nonpaged_area
• system_thread_exception_not_handled

After some searches on the Web I decided to try the built in Driver verifier of Windows 10 , the BSOD that I get is the following :

• BSOD - DRIVER VERIFIER DETECTED VIOLATION - AsusPTPFilter.Sys

Can you please advise on what to do in this situation ? are these issues related or should I run Memtest?

Thanks.

 

Driver Verifier shows BSOD with "Driver Verifier Detected Violation" but doesn't create dump file

Hello,

I wanted to have my Windows stable so I run Driver Verifier to check if everything is ok (I had some BSODs from time to time). After first Verifier run I had kl1.sys BSOD which is related to kaspersky. So I removed the software and made a second run on Verifier.
This time however it shows BSOD before entering desktop and "Driver Verifier Detected Violation" is written, without any file or anything. However there is percentage moving up to 100% and then my PC restarts.

The problem is, no dump file is created when I use verifier and I don't know why :-( When kl1.sys BSOD came out I was at least able to see the file on BSOD, but when I don't get any file name except "Driver Verifier Detected Violation", I don't know what
I should search for...

When I had BSOD before using Verifier, it created dump file, but when checking with verifier, it doesn't.

What can I do with that? I would be glad if you guys help me, because I want to feel stable on my PC

 

Driver verifier detects violation in every driver, 3rd party and system.

Long story short - my System started to get random BSODs.

Tried to find the cause with Driver verifier and it always crashes system before I'm able to log in.

1. Driver verifier detected violation on each 3rd party driver, including intel, nvidia, antivirus etc.. I was removing associated soft and drivers one by one until there was no 3rd party soft and drivers left.

2 Driver verifier started to detect violation on random microsoft and system drivers.

At this point it is obvious that any driver will be detected as violating so driver verifier can't point me in the right direction anymore.

The pattern is always the same - DRIVER_VERIFIER_DETECTED_VIOLATION -> BSOD -> Dump file analysis shows random "driver.sys" violation, then ntoskrnl.exe crash

Windows is up to date, bios, all drivers are newest versions.

SFC/scannow - no errors

Dism /restorehealth - no errors

memtested each ram module - no errors

removed videocard - no changes

removed every peripheral except system ssd - same result

Wiped and reformatted ssd, installed OS back - no effect

I'm puzzled by the result to be honest.

At this point I have only 3 suspects left:

1. Faulty cpu

2. Faulty motherboard

3. Faulty psu.

Any suggestions? I'm struggling for 4 days now.