Windows 10: Keep receiving Driver Verifier BSOD every month or so

Hello,I've been receiving the same error for about a year now. It only happens when I play games and maybe it crashes my PC once a month.I can tell when its about to happen as normally my USB devices start to malfunction. Any help would be appreciatedDRIVER_VERIFIER_DMA_VIOLATION e6An illegal DMA operation was attempted by a driver being verified.Arguments:Arg1: 0000000000000026, IOMMU detected DMA violation.Arg2: 0000000000000000, Device Object of faulting device.Arg3: 00000000408349e7, Faulting information usually faulting physical address.Arg4: 0000000000000004,

:)

 

BSOD at least twice a month - uncertain cause

I have run driver verifier with the below settings for >48 hours. There have been no BSOD. Please advise on next steps

• I/O verification
• Force pending I/O requests
• IRP logging

 

BSOD hidclass with driver verifier

Hi Doc_Samson,



Thank you for writing to Microsoft Community Forums.



I understand that you receive Blue Screen error with hidclass.sys. In order to get to the root cause of the issue, we will need the Dump files, so that we can analyze them and assist you accordingly. I have sent a private message to you, please share
the Dump files over the private message.



To access Private Message click on your Profile on the top right corner, then click on the ellipses, and select
View Private Messages.



However, the hidclass.sys is a driver file for Human Interface Devices, which are basically, keyboard/mouse or gaming controllers. I would suggest you to disconnect all the external devices and see if that helps.



I would suggest you to refer the steps mentioned below and see if that helps:



Method 1: Update drivers



I suggest you to update the drivers on the computer, to make sure that all the drivers are up to date including Keyboard, Mouse, USB and HID Drivers. In addition, you may also update the chipset drivers from the computer manufacturer’s websites. Kindly
refer the article
Update drivers in Windows 10.



Method 2: Check hard disk for errors



I would suggest you to run chkdsk utility to check any errors in the hard drive. Refer the steps mentioned below:

1. Type command prompt in the search bar on the
   Taskbar.
   
2. Right click on the command prompt icon and select
   Run as administrator.
   
3. Now, paste the following command and hit Enter: chkdsk/f C:
   
4. Select Yes and restart the computer.
   

Note: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost



Method 3: Windows Memory Diagnostic



You can also run Memory Diagnostic on the computer to check for any memory corruption errors. Follow the steps mentioned below:

1. Press Windows key + R, to open
   Run dialog box.
   
2. Type mdsched and click on
   OK.
   
3. Click on Restart now and check for problems.
   

You may want to refer the troubleshooting steps mentioned in the article

Troubleshoot blue screen errors.



You can also refer the suggestions provided by auggy replied on May 15, 2018 in the thread

BSOD Hidclass.sys.



Let us know how it goes.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Driver Verifier BSOD on Start Up DRIVER_VERIFIER_DETECTED_VIOLATION

OK I'm going to keep this thread updated as I go through troubleshooting this issue.

As I have received no help with my minidumps, I am going through the process of learning to do it myself.

This seems
like a good guide to learn the very basics.

What has happened so far:

• New computer build, unstable windows install, slowly degrades to where the computer is unusable. Happens on multiple clean installs.

• Continuous error and critical messages in Event Viewer, some events of note are:
  • Event 219 Kernel-PnP, failed to load driver
  • Event 7031 service control manager (dozens on start up)

• First crash will happen on start up and it eventually degrades with below events.
  • Event 5 kernel general
  • Event 2 kernel-event-tracing
  • Event 3 kernel-event-tracing
  • Event 29 kernel-boot

• Tested hardware - no faults found

• Ran Driver Verifier and Windows will keep crashing with DRIVER_VERIFIER_DETECTED_VIOLATION until Driver Verifier is reset in safe mode

• Started this thread, PC became too unstable and had to do a system restore, restore had minimal changes (see above)
• Have not installed the applications and drivers removed after system restore.
• PC is heading down same road again, BSOD now appearing on startup.
• Ran Driver Verifier again - same resuslts
• Installed WinDBG to start analyzing new dumps from crashes that have been happening on startup.
  • dump 1 - pool_corruption
  • dump 2 - memory_corruption
  • dump 3 - memory_corruption
  • dump 4 - ntkrnlmp.exe

From the limited knowledge I got from the guide the only information I can get from WinDBG is shown above.

So that's where I am at the moment. My next step is to run Driver Verifier again and see what I can find.