Windows 10: Driver verifier detected violation BSOD

https://1drv.ms/u/s!AjyfBDZNZqa8sTBssgAbKoCKChGa?e=Oxf9BxHi, please review the uploaded files for a continuing driver crash issue with my PC. Any help would be appreciated.Kind regards,Rhys

:)

 

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 detected violation without the name of the driver

I was intermittently getting BSOD with stop code Memory_ Mangement, so I decided to run Driver Verifier to check if there's a driver causing the problem. While I was able to succesfully get the "driver verifier detected violation loop", it did not specify
any driver. How do I find which driver was causing BSOD?>

 

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