HIDCLASS.sys, CRITICAL PROCESS DIED, PFN List Corrupt, and KMODE EXCEPTION NOT HANDLED BSOD.

304FV

Reputable
Jan 10, 2016
15
0
4,510
I have a Dell Latitude E7440 Laptop Ultrabook, i've had a lot of problems with it because a lot of BSOD.

Tried:
-Slim Drivers
-Slim Cleaner
-RegClean Pro
-Advanced System Optimizer

Used windows functions like chkdsk /F /R and verifier.

The next problem is: When I go to dell's website and try to install the detected chipset. Can't do it because of an unexpected error.

BSOD:
-HIDCLASS.sys while running verifier.exe
-CRITICAL PROCESS DIED when it wants
-PFN List Corrupt when it wants
-KMODE EXCEPTION NOT HANDLED when it wants

Help please...
 
Solution
Well firt off I know two of the programs you listed are just junk (Reg Clean Pro and Advanced System Optimizer).

Second, HIDclass.sys is a driver for Human Interface Devices, i.e. mice or keyboards normally, and is what is causing the problem. Some interface device you have plugged in via USB is causing the crashes. Try a new mouse, keyboard and remove any other USB devices you might have plugged in.
Well firt off I know two of the programs you listed are just junk (Reg Clean Pro and Advanced System Optimizer).

Second, HIDclass.sys is a driver for Human Interface Devices, i.e. mice or keyboards normally, and is what is causing the problem. Some interface device you have plugged in via USB is causing the crashes. Try a new mouse, keyboard and remove any other USB devices you might have plugged in.
 
Solution
usb devices are a special case, when you update to windows 10, generic USB drivers will be installed. These drivers may also require that you update the BIOS because usb support starts with the BIOS, then you have to update the USB drivers for your motherboard. You will also want to update the drivers for your actual USB device. There were changes in what a driver is allowed to do when you go to newer versions of windows.

if all else fails, you can change your memory dump type to kernel rather than minidump and put the file c:\windows\memory.dmp on a server like Microsoft onedrive, share the file with the public and post a link. The kernel memory dump will save info on that will indicate what USB device is failing and why.