Windows 10: Frequent BSOD/Lockups Bugcheck 0x0000009c

Over the last few days my computer would lock up and checking the EventViewer I'd see a Bugcheck 0x0000009c error. Here's what I've done: At first I figured it was time to nuke Windows anyway so I formatted my boot drive and installed Windows 10. When that didn't work I figured well the SSD was getting kind of old anyway so I installed Windows 10 on a newer SSD.When that didn't work I made sure all my drivers were up to date. I removed a slight overclock that I'd done previously. I ran memtest for a few hours with zero errors. Usually happens within 30 minutes of Windows being running.

Any help is appreciated.

:)

 

BSOD pnp_detected_fatal_error

That is a very unusual bugcheck-probably I saw it for the first time.

Is this a one off BSOD or does it happen frequently?

Can you access the USB disk on another computer?

 

Windows 10 bugcheck every few hours with event id 1001

Unfortunately, I have now had a further two bugcheck reboots with event id 1001.

The event text is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x0000000000000000, 0xffffd0006a879760, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 092615-4281-01.

I have saved the MEMORY.DMP file on onedrive here: http://1drv.ms/1KBbXmO

On both occasions I was running VMWare Workstation 12.

Please can someone with the necessary tools inspect the MEMORY.DMP to find out what is going on?

Thanks,

Paul

 

Hi there,

The intelppm.sys is a driver for intel processor.
Please check at Drivers & Software for driver update compatible with windows 10.
Your CPUID: "Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz"

Also, i would advise after updating to run driver verifier. A tutorial can be found at : Enable and Disable Driver Verifier in Windows 10

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

Goodluck

 

Enabled Driver Verifier as per the instructions. Upon logging into windows after reboot I would instantly BSOD. Log files from C:\Windows\Minidump from this morning (Which is where I've been lead to believe Driver Verifier stores logs)

 

Well, those two are pointing towards Probably caused by : IOMap64.sys

This is according to the DRT Driver Reference Table

ASUS Kernel Mode Driver ?Asus Smart Doctor/iTracker 2 Asus GPU Tweak and GPU Tweak Streaming

So i would download the latest video drivers for your GPU AMD Radeon (TM) R9 390 Series.
After that i would remove all videodrivers with DDU (driver display uninstaller) to remove ALL previous drivers (do this in safemode)
I would also remove all OC software like GPU Tweak and other ASUS related software.

Then reinstall the latest drivers (without GPU tweak), test it and see how it runs.

 

Did that and PC was stable for awhile, just received a few BSODs in a row. Here are the new dump files.

 

There is only one of the two DMP-files that were readable for me.
In that one that i could read, the issue seems to be with the following driver :

Driver Reference Table (Creative OS Services Driver)

Software of some soundblaster or some sort of headset software? Try to delete that software and see if that helps.
If you go to the control panel -> programs and features -> look for something that has "creative os" in its name, delete it, reboot and see what happens.

 

The issue still persists and it's gotten even weirder. I went ahead and manually updated everything through my mobo manufacturer's website, removed my sound card in case the drivers for that were causing issues, etc. What I ended up with were Hardware Machine Check BSODs that pointed to hal.dll and a lot of googling suggested a processor issue.

I removed the cooler, removed and reapplied thermal paste, reapplied the cooler, and I didn't have a BSOD for a week. Now they're back and I have no idea what is causing them. Sometimes I'll get an actual bluescreen and a memory dump is generated, sometimes it will just lock up and no dump is generated. Using the program WhoCrashed this is what I see:

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/19/2017 3:01:06 AM your computer crashed
crash dump file: C:\Windows\Minidump\011917-115812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xA (0x17FFFFFFEF0, 0xFF, 0xA, 0xFFFFF803E1BE8E55)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/19/2017 3:01:06 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x17FFFFFFEF0, 0xFF, 0xA, 0xFFFFF803E1BE8E55)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/19/2017 2:57:26 AM your computer crashed
crash dump file: C:\Windows\Minidump\011917-103046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/19/2017 2:39:42 AM your computer crashed
crash dump file: C:\Windows\Minidump\011917-5515-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8039F4A4FF6)
Bugcheck code: 0x50 (0xFFFFB7B44BC00030, 0x2, 0xFFFFF8039F4A4FF6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


I've run Memtest86 overnight with no errors, I've run Prime95 and Furmark for hours with no lock ups. I'm not sure what to think really. If it does turn out to be a processor issue, I've had this one for just over a year, does anyone have any experience with Intel's three year warranty?

 

Update - I contacted Intel to start the RMA process rolling in the event that it turns out to be the processor. The gentleman on the phone told me that my RAM frequency was too high. My mobo supports 2400hz but according to this gentleman my processor does NOT. So I've put in some 2133hz sticks which supposedly will work, and I'll see if the issue persists.

EDIT: Haha nevermind ... less than 30 seconds after posting that, computer locked up.

Another update: Intel's rep told me that they'd replace my processor for free, so I took them up on that. He also told me that the problem was my 2400Mhz ram, and that the maximum speed a 6600k supports is 2133Mhz.

This doesn't really make sense to me because I see a lot of people on the internet recommending 2400Mhz RAM or even 3000MHz RAM to people in combination with my processor and motherboard. Are they just assuming that the user will be overclocking and that's why this is okay? Do I need to buy new RAM? Or can I just underclock my current RAM for compatibility so this doesn't happen again? I've been putting my own PCs together for almost 15 years now and I've never been this confused.