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

Jacky Deschepper

• SERVER-wo_26_08_2015_230415,60.zip (253.0 KB, 1 views)

Hi Jacky De,

Welcome to the 10blog.

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

Jacky Deschepper

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

Jacky Deschepper

• SERVER-zo_13_09_2015_140729,49.zip (314.9 KB, 2 views)

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
Jacky Deschepper

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 tutorialto 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

Jacky Deschepper

Hi Jacky De,

Do you have any result of driver verifier?