Windows 10: intelppm.sys causes BSOD KMODE_EXCEPTION_NOT_HANDLED 0x0000001e

Hi,

I'm running on a clean install of windows 10 64 bit. I installed each day several programs without any problems. Everything seems ok, but tonight I had a BSOD. Can someone analyse the attached dump please

grz

schepper

:)

 

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.

 

win10 BSOD

Hi I just got another BSOD again..

this time it says "

[*]STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED – igdkmd64.sysand the computer reboots

the event viewer says the following

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000094, 0xfffff8015b409bab, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1f0be5f2-4abc-48ca-92c6-a498e0ce50b3.

minidump file :103016-8250-01.rar

 

Hi Jacky De,

Welcome to the 10forums.

The intelppm.sys is a driver for your intel processor.
Please check here for driver update compatible with windows 10.

 

Hi,

The intel driver update utility is not usefull because the most recent drivers are for windows 8.1. I think Intel wil not release any drivers for my motherboard DH67BL (4 years old), I upgraded from windows 7 SP1. So I just installed manually the most recent drivers (for windows 8 or 8.1).

Let's hope this solves the problem. I'll keep you informed

grz

schepper

 

Please check windows updates for driver updates.
Mostly those driver updates are causing problems.

I wouldn't recommend a driver update program, because driver update programs are known to cause problems.

 

Hi,

Haven't had the BSOD since 26/08/2015. Today, without a reason suddenly the same BSOD. Windows 10 64 bit is working excellent. Nog new programs installed. Alle drivers are up to date. can someone analyse both dump files to establish what causes this BSOD (I know it's probably a part of my motherboard Intel DH67BL that causes these BSOD but I don't know what). I updated al my drivers for this motherboard after my first BSOD

grz

schepper

 

Hi Jacky De,

I see you have DriverMax.
Programs that claim to update your drivers give problems regarding installing corrupted drivers or the wrong drivers.
Please remove this program with every driver that this program has installed and install the drivers from the manufacturer and companies only.

 

Hi Axe0,

I haven't downloaded any driver with drivermax. I just installed the program after the last BSOD to look which drivers could be old. I only download drivers from the website of the manufacturer.

grz
schepper

 

Alright,
Because this is a windows driver, windows drivers are very rarely the real cause, we need to stress the drivers to find the cause.
In a lot of cases the real driver that causes the problem 'hides' so windows drivers are being blamed (something has to be blamed)





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

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

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

thanks,

Give me a few days to run this diagnostic test with driver verifier. I'll come back with the results

grz

schepper

 

Hi Jacky De,

Do you have any result of driver verifier?

 

Hi,

No result. No BSOD. Today I noticed that I couldn't play any mp3 anymore. So I dit a repair install of windows 10 with an In-place Upgrade. MP3 are ok now with any app. Is this problem caused by Driver verifier ?
I'll have to wait till the next BSOD. I'll keep you noticed when the same BSOD occurs

grz

schepper

 

Driver verifier only stresses the drivers, this could only cause the system to behave laggy.

 

I know. So driver verifier did not create any BSOD. Does driver verifier creates a log if no BSOD occurs.

schepper