Computer freezes after loading CLASSPNP.sys

I'm not entirely sure where to post this, but windows seems to be treating it as a BSOD (Shows me the "Unexpected shutdown" summary when I boot it in safe mode, creates a kernel dump) so I'll post it here.

My mom's computer has started to hang on boot. It will reboot, attempt to do a startup repair, and then fail to boot again. If I boot into safe mode, I see that it gets stuck after CLASSPNP.sys, and then eventually loads into safe mode and gives me a crash report. I thought it was the hard drive because I thought I heard clicking, so we bought a new SSD and reinstalled. After installing the intel graphics driver from the CD, it experiences the same crash as before.

I've removed everything connected to the motherboard except the SSD (including keyboard and mouse), and it still crashes. I've tried each stick of RAM by itself, still crashes. I've exhausted my arsenal on this problem, and I hope somebody here can help me figure out what's going on and how I can fix it.

Specs:
CPU: i5-2400
Mobo: H67M-GE
RAM: 8GB DDR-1600 (Not sure of brand or model #)
SSD: Samsung 840 EVO 240GB

Your Intel graphics driver is being flagged, and it's outdated.
Update it here.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+ba34d )

Code:

fffff880`04827000 fffff880`053db700   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Jan 27 16:57:05 2011 (4D41A3E1)
    CheckSum:         00BC2892
    ImageSize:        00BB4700
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Updated driver from Intel's website, same problem. New report attached.

Hmm, still getting the blame.


Can you also enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no points, make a System Restore Point Manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

So I should enable DV in safe mode, let it restart my computer into normal start, let it crash, then boot back into safe mode to disable it and collect the results?

Yep, exactly.

I'm pretty sure you only need the crash dump but I've attached the whole thing again just to be sure.

Right, we aren't getting much from this.

Stress test your CPU with Intel Burn In test
Watch your temperatures.

If it passes fine then I think Kernel Memory Dumps might be necessary as I can't see much that stands out with these dumps, the problem I'm having is that it's pointing to your Intel Graphics driver.
You've updated it but no such luck.
I see this as 2 main possibilities, something is conflicting with your Intel Graphics driver and it's getting the blame, or your CPU is faulty.

To change to Kernel Memory Dumps you need to go here and look how to do it from these instructions.

Dump Files - Configure Windows to Create on BSOD

Then once a dump file has been created here: C:/Windows/memory.dmp copy the dump file to the desktop, then upload it to OneDrive then post that link.

There's literally nothing that could be conflicting. This is a fresh install of Windows with nothing connected or installed, and it was working with the this same hardware last week. Seems like it's best to not waste any more time and just replace the CPU, right?

I don't want to ignore your expertise but it just seems like this is all pointing towards a bad CPU and I've spent enough of my weekend on this as it is.

I would still test your CPU with Intel Burn In test.
For the reason is that I don't want you to make the mistake I nearly did.

Let me tell you something, my PC has had so many problems in the past...
I got it March 2013 and it had problems all the way until around last month when I finally fixed the problem.
It has had so many different bugchecks including 0x124 errors which indicates a fatal hardware error has occurred, now I bought my PC from a local PC shop who buys his computers from a manufacturer.
I had been going back to the PC shop where I bought it from telling him I have had X, Y and Z problems (BSODs) and he'd say "Leave it with me for a few days and I'll have it fixed by -day", now when I got it back it worked for a bit then it started to BSOD again.
I then rang up the manufacturer who he buys the PCs from and told them the situation, I sent it off and they did some testing and found nothing, they did actually upgrade my graphics card and power supply a bit (for free which is nice).
Now even thought lots of stress testing had taken place and it came up clean I had still gotten a few 0x124 errors.
At this point I decided I'll join a forum and ask for help, I got a lot of advice but I ignorantly took no notice and looks for videos and the local PC shop which got me nowhere.
Oh and the other thing is that I had formatted by PC and re-installed windows at least 6 times and was still getting BSODs and deadlocks, this is what made me think it's time to replace hardware, but if you keep installing the same software then the same error will come back...
Anyway, I thought I'd do something about it myself, although at the time I knew absolutely nothing about computers but going on Seven Forums and helping a few people out by posting a few tutorials then downloading Windbg and learning stuff on that, then learning by reading Windows Internals and other technical books I managed to do some debugging and I've fixed my computer.
The point of this story is that I thought replacing components without making sure would end well but it doesn't, you could just replace your CPU tomorrow and you could still have issues then you've wasted quite a bit of money which is not what I want you to do.

If you run Intel Burn In test and it works fine then there's no need to replace the CPU as it's working fine, although there can be small possibilities that it passes the test but it's actually faulty.