Windows 10: KMODE_EXCEPTION_NOT_HANDLED (intelppm.sys)

Edit: Solved by updating firmware on the motherboard.


I recently installed Fallout 4 and when playing that game I suddenly get a BSOD with the message saying:

This is my first BSOD in Windows 10 and I've had it since launch. My version of Windows 10 is an updated one from Windows 7.

After Fallout 4 provoked this error I have also had it without running the game, but so far only after a restart.

There are some other threads on a similar issue on this site, and others, which gave me some ideas on things to try.

What I have done so far:

• Installed latest Windows 10 updates.
• Installed latest Nvidia Drivers (graphics)
• Installed Latest Realtek Drivers (sound)
• Rerolled last update for Windows 10.
• Reset Windows 10, but I kept the files
• Ran Windows memory diagnostics tool - no errors.
• I tried to update Intel drivers by using their tool for it, but it found nothing to update.
• Checked temperature: Max has been 65 degrees Celsius (149 F)

I am at a loss and I turn to you. Perhaps someone here can understand the output of the attached file?

Thank you very much in advance!

Attachment 52339

:)

 

Windows 10 Clean Install - Microsoft-Windows-Kernel-Power Event ID: 41 BugcheckCode 30

Memtest passed without error.

I tried nirsoft BlueScreenView and it showed some interesting things:

- Most recent crash caused by driver: intelppm.sys (as well as one earlier crash)

- DRIVER_VERIFIER_DETECTED_VIOLATION: atikmdag.sys

- Two other KMODE_EXCEPTION_NOT_HANDLED: Wdf01000.sys

What would you recommend as a next step?

 

Sudden increase in Windows 10 BSODs after updates around 9/7/2017

It doesn't seem to be crashing in safe mode, but I can't do most of the stuff I'd do normally in safe mode.

For now, I've gotten 2 more BSODs today. One was after the usual exiting a game scenario (this time the Runescape client) with a KMODE_EXCEPTION_NOT_HANDLED related to intelppm.sys. The second was when I woke up my monitors after they'd turned off due to inactivity,
but my PC had not yet gone to sleep. That generated an IRQL_LESS_THAN_OR_EQUAL stop code. I have no peripherals to speak of aside from a USB hub and my mouse and keyboard. I've removed the hub and will see if I get errors now.

Another KMODE_EXCEPTION_NOT_HANDLED related to intelppm.sys BSOD. This is happening pretty reliably when I exit the Runescape client. I have now had a restart without the hub connected, so I'm assuming the drivers are fully unloaded. Will now see if I get another
BSOD after exiting a game.

Just got another KMODE_EXCEPTION_NOT_HANDLED, but this time it didn't say that intelppm.sys was what failed. It just had the stop code, no other information. This was with my USB hub disconnected. This BSOD was delayed by a minute or two after exiting a game.

I'm now up to 4 more BSODs in the span of about an hour. Sometimes they're delayed, like this most recent one, but other times they're immediately after exiting a game. More perplexing is that there was a period where I started and exited Overwatch and Runescape
about two dozen times, but no BSOD occurred after exiting, or even after a delay.

Edit: And now I've had another IRQL BSOD while playing a game, not after exiting.

 

Checked RAM following the tutorial for memtest86+ twice. Did 9 and 11 passes, no errors.

 

Please update the Realtek network driver
Driver Reference Table - rt640x64.sys
Code: ffffd000`45c1a8d0 fffff801`e9164850Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x4850 1: kd> lmvm rt640x64 start end module name fffff801`e9160000 fffff801`e91f3000 rt640x64 T (no symbols) Loaded symbol image file: rt640x64.sys Image path: \SystemRoot\System32\drivers\rt640x64.sys Image name: rt640x64.sys Timestamp: Wed Apr 01 16:34:31 2015 (551C01F7) CheckSum: 0009D4EA ImageSize: 00093000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Hi axe0,

Thanks! I will do so promptly.

It seems the problem was solved by updating the motherboard firmware. At least I got through a few hours of gameplay yesterday without problems, compared to the usual 15 minutes I had before.

I will report back if I have further issues.

 

Glad to hear that *Smile