Windows 10: BSOD hidclass with driver verifier

memory. dmp


hi I have tried to enable driver verifier to check the stability of my computer, and every time I have got this bsod correlated to "hidclass.sys".

Some help?


Thanks a lot

:)

 

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 BSOD diagnosis opinions?

I used the link provided and selected the option that says the BSOD occurred while using my PC. The link suggests checking for updates and disconnecting hardware. My software is already up to date, and rather than disconnecting random hardware, I was under
the impression from that by uploading the dump files from the Driver Verifier program that from

this post, there might be some clues as to what specific driver is causing the crashes. Is that possible to determine?

 

Windows Driver Verifier BSOD


I took the WinTV card out of my computer and ran driver verifier again but didn't have it check dfx12x64.sys. Still got an immediate BSOD which BlueScreenView reported as being caused by wdcsam64.sys. Ran driver verifier again and didn't have it check either of those two, this time I got a BSOD that BlueScreenView reported as being caused by rtwlanu.sys (I've included that crash dump - the previous one got deleted when I had to use system restore to disable driver verifier). Ran driver verifier again and excluded all 3 of those from the list of drivers to check and finally didn't get a BSOD. So what the heck does that mean? Driver verifier's given me BSODs for 5 different drivers now. I'm about to just give up and go back to Windows 7.