Windows 10: BSOD hidclass.syss with verifier enabled

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

//win10 version 1903

Hello

i have enabled "verifier" to check my PC behaviour; well at the start of the system it gives me Always this bsod.

I have tried to:

- unplug all usb things
- sfc /scannow and chkdsk
- reinstall in place of Windows

No results.

Thanks in advance of all your replies.

Cheers

:)

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

BSOD kernel security check failure


Why is driver verifier enabled? You can't simply enable driver verifier unless instructed by an analyst as it may cause your system to become unbootable.
Please disable driver verifier

• Open an admin command prompt
• Enter "verifier/reset" (without quotes)

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

 

[SOLVED] Multiple random BSODs, all pointing to the kernel


No BSODs yet but I haven't been playing World of Warcraft which I suspect to be a possible cause.

Was the driver verifier step necessary or just a suggestion?