Windows 10: BSOD on sleep, intelppm.sys

My laptop can't sleep. After I try and make it sleep it's like someone removes the battery. No visible BSOD, just shuts off.

Attachment 50214

:)

 

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.

 

BSOD Error, DRIVER_IRQL_NOT_LESS_OR_EQUAL (intelppm.sys)

Hi,

Thank you for responding and apologize for the delay in response to your issue.

I would like to inform that there can be many events which might have resulted in the system files errors. An incomplete installation, in incomplete uninstall, improper deletion of applications or hardware.

I suggest you to perform a Reset on your computer and check if it helps.

I would like to inform that when you perform reset/ refresh on your computer by selecting
keep my files, it works as below:

• Reinstalls Windows 10 and keeps your personal files.
• Removes apps and drivers you installed.
• Removes changes you made to settings.
• Removes any apps your PC manufacturer installed. (If your PC came with Windows 10, apps from your PC manufacturer will be reinstalled.)

Note: While performing reset on your PC, I suggest you to choose "Keep my files" as this will not affect the user data (files and folders) on your computer.

Follow the below:

• Press Windows + R keys from the keyboard, type
  Control and press Enter.
• Click on Recovery, click on
  If you're having problems with your PC, go to Settings and try resetting it.
• Click on Get started under
  Reset this PC, click on Keep my files and follow onscreen instructions.

Refer: Recovery options in Windows 10

As the installed applications and updates will be removed, you will have to re-install all those after performing the reset on your computer.

Hope it helps. Kindly update the status of the issue, we will be happy to help you.

 

It seems there is a little more going on then just a driver problem.
This means a hard drive related problem
Code: KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: ffffc001ee379968, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000000e, error status (normally i/o status code) Arg3: 00000003a9047860, current process (virtual address for lock type 3, or PTE) Arg4: fffff8008956354c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)[/quote] The CPU driver seems to be corrupted.
Code: CHKIMG_EXTENSION: !chkimg -lo 50 -d !intelppm fffff80089563000-fffff80089563065 102 bytes - intelppm!InitAcpiIdleDomain+30 [ 00 48 8b 74 24 38 8b c3:c0 04 78 3f 18 8c 01 e0 ] fffff80089563067-fffff80089563087 33 bytes - intelppm!ValidateAcpi_PSD_TSD+3 (+0x67) [ 75 32 83 79 04 05 75 2c:e0 c0 04 78 3f 18 8c 01 ] fffff80089563089-fffff800895631be 310 bytes - intelppm!ValidateAcpi_PSD_TSD+25 (+0x22) [ 3d 80 02 00 00 77 08 f7:04 78 3f 18 8c 01 e0 c0 ] fffff800895631c0-fffff80089563201 66 bytes - intelppm!InitAcpiPerfStates+11c (+0x137) [ ff ff 48 8b 5c 24 48 8b:c0 04 78 3f 18 8c 01 e0 ] fffff80089563203-fffff8008956322f 45 bytes - intelppm!ValidateAcpi2PStates+23 (+0x43) [ 3d 48 8b cf e8 40 00 00:3f 18 8c 01 e0 c0 04 78 ] fffff80089563231-fffff8008956326d 61 bytes - intelppm!ValidateAcpi2PStates+51 (+0x2e) [ 48 8b 5c 24 30 48 8b 74:04 78 3f 18 8c 01 e0 c0 ] fffff8008956326f-fffff80089563285 23 bytes - intelppm!Validate_PCT_PTC+23 (+0x3e) [ 75 f6 eb e5 cc 48 89 5c:e0 c0 04 78 3f 18 8c 01 ] fffff80089563287-fffff800895632cb 69 bytes - intelppm!ValidatePssCore+13 (+0x18) [ 76 3a 44 8b c2 4c 8d 49:e0 c0 04 78 3f 18 8c 01 ] fffff800895632cd-fffff800895632fb 47 bytes - intelppm!ValidatePssCore+59 (+0x46) [ 00 00 c0 eb f1 ba 01 00:8c 01 e0 c0 04 78 3f 18 ] fffff800895632fd-fffff80089563317 27 bytes - intelppm!InitAcpiThrottleStates+21 (+0x30) [ 5f 7e ff ff 48 8b 80 c8:8c 01 e0 c0 04 78 3f 18 ] fffff80089563319-fffff80089563325 13 bytes - intelppm!InitAcpiThrottleStates+3d (+0x1c) [ 48 a9 00 00 00 03 74 1d:04 78 3f 18 8c 01 e0 c0 ] fffff80089563327-fffff80089563357 49 bytes - intelppm!InitAcpiThrottleStates+4b (+0x0e) [ 00 00 8b f8 85 c0 0f 89:e0 c0 04 78 3f 18 8c 01 ] fffff80089563359-fffff80089563440 232 bytes - intelppm!InitAcpiThrottleStates+7d (+0x32) [ 0f 89 a1 44 00 00 48 81:04 78 3f 18 8c 01 e0 c0 ] fffff80089563442-fffff8008956347d 60 bytes - intelppm!IsValidAcpiGenericAddress+1e (+0xe9) [ a9 00 00 ff ff 75 20 85:78 3f 18 8c 01 e0 c0 04 ] fffff8008956347f-fffff80089563497 25 bytes - intelppm!InitAcpi3ThrottleStates+f (+0x3d) [ 00 00 ba 5f 50 54 43 48:e0 c0 04 78 3f 18 8c 01 ] fffff80089563499-fffff8008956352b 147 bytes - intelppm!InitAcpi3ThrottleStates+29 (+0x1a) [ 48 8b cf 0f 48 d8 e8 00:04 78 3f 18 8c 01 e0 c0 ] fffff8008956352d-fffff80089563563 55 bytes - intelppm!InitAcpiCStates+75 (+0x94) [ 2f 7c ff ff 48 8b 80 d0:8c 01 e0 c0 04 78 3f 18 ] fffff80089563565-fffff8008956356b 7 bytes - intelppm!InitAcpi2CStates+19 (+0x38) [ 00 4c 8b f2 48 8d 50:8c 01 e0 c0 04 78 3f ] fffff8008956356d-fffff80089563577 11 bytes - intelppm!InitAcpi2CStates+21 (+0x08) [ 48 8b f9 e8 f7 02 00 00:8c 01 e0 c0 04 78 3f 18 ] fffff80089563579-fffff8008956363f 199 bytes - intelppm!InitAcpi2CStates+2d (+0x0c) [ 78 27 48 8b 74 24 40 48:04 78 3f 18 8c 01 e0 c0 ] fffff80089563641-fffff8008956375f 287 bytes - intelppm!ValidateAcpiCStates+85 (+0xc8) [ eb ef cc 48 89 5c 24 20:04 78 3f 18 8c 01 e0 c0 ] fffff80089563761-fffff8008956390d 429 bytes - intelppm!AcpiEval_PSD_TSD+11d (+0x120) [ 0f 84 d1 42 00 00 ff c8:04 78 3f 18 8c 01 e0 c0 ] fffff8008956390f-fffff80089563947 57 bytes - intelppm!AcpiEval_CST+a3 (+0x1ae) [ 00 00 10 00 48 89 4d 0f:e0 c0 04 78 3f 18 8c 01 ] fffff80089563949-fffff80089563a20 216 bytes - intelppm!AcpiEval_CST+dd (+0x3a) [ 0f 88 ac 01 00 00 41 8b:04 78 3f 18 8c 01 e0 c0 ] fffff80089563a22-fffff80089563a30 15 bytes - intelppm!AcpiEval_CST+1b6 (+0xd9) [ 4a 8d 04 a0 c7 44 24 28:78 3f 18 8c 01 e0 c0 04 ] fffff80089563a32-fffff80089563b25 244 bytes - intelppm!AcpiEval_CST+1c6 (+0x10) [ 48 89 44 24 20 48 8d 4d:78 3f 18 8c 01 e0 c0 04 ] fffff80089563b27-fffff80089563b3f 25 bytes - intelppm!AcpiEval_CST+2bb (+0xf5) [ 00 00 48 81 c4 d0 00 00:e0 c0 04 78 3f 18 8c 01 ] fffff80089563b41-fffff80089563c98 344 bytes - intelppm!AcpiEval_CST+2d5 (+0x1a) [ eb af cc 48 89 5c 24 18:04 78 3f 18 8c 01 e0 c0 ] fffff80089563c9a-fffff80089563ce8 79 bytes - intelppm!AcpiEval_PSS+156 (+0x159) [ 83 c1 38 44 8b f1 8b d1:78 3f 18 8c 01 e0 c0 04 ] fffff80089563cea-fffff80089563e20 311 bytes - intelppm!AcpiEval_PSS+1a6 (+0x50) [ 45 0f b7 4e 02 ba 06 00:78 3f 18 8c 01 e0 c0 04 ] fffff80089563e22-fffff80089563e67 70 bytes - intelppm!AcpiParseCore+96 (+0x138) [ 48 8b ce 44 8b 44 24 78:78 3f 18 8c 01 e0 c0 04 ] fffff80089563e69-fffff80089563feb 387 bytes - intelppm!AcpiParseCore+dd (+0x47) [ 25 0b 00 14 c0 48 8b 5c:04 78 3f 18 8c 01 e0 c0 ] fffff80089563fed-fffff80089563fff 19 bytes - intelppm!AcpiEval_CSD+5 (+0x184) [ 55 56 57 41 54 41 55 41:8c 01 e0 c0 04 78 3f 18 ] 4064 errors : !intelppm (fffff80089563000-fffff80089563fff)[/quote] Please check your manufacturer for driver updates for your CPU
Please test your hard drive.





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html



Run HDTune to scan for errors, health and benchmark.
Let me know what the results are, prefered screenshots.

 

Thank you for your help but sadly doing those things was my first step to diagnosing this issue. I reinstalled the drivers from Dells website (in fact I reinstalled all drivers after CPU and SATA didn't work). I also ran chkdsk (no errors) and Crystaldisk says the HDD is fine.

Should I clean install?

 

Diagnostic Test

CPU TEST


Run Prime95 - Stress Test Your CPU - Windows 10 Forums



Note If you're overclocking anything, please stop it and set everything back to default while troubleshooting


Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

Prime95 isn't returning any errors.

 

Interestingly enough I just tried to get another minidump file by going to sleep mode and it did crash but not in the normal way as no minidump file was created. Onedrive has lost it's settings and Chrome profile is corrupted as happens many times with these crashes but no minidump was made.

 

A crash doesn't say anything, because there are 3 different crashes..

 

Well I ran CHKDSK again and it found and fixed some errors but I still can't enter sleep mode.

Code: Checking file system on C: The type of the file system is NTFS. Volume label is OS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 451328 file records processed. File verification completed. 15558 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 592906 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 50 unused index entries from index $SII of file 0x9. Cleaning up 50 unused index entries from index $SDH of file 0x9. Cleaning up 50 unused security descriptors. CHKDSK is compacting the security descriptor stream Security descriptor verification completed. 70790 data files processed. CHKDSK is verifying Usn Journal... 40613880 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 451312 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 131803768 free clusters processed. Free space verification is complete. Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. No further action is required. 964113501 KB total disk space. 436076288 KB in 346351 files. 230096 KB in 70793 indexes. 0 KB in bad sectors. 592041 KB in use by the system. 65536 KB occupied by the log file. 527215076 KB available on disk. 4096 bytes in each allocation unit. 241028375 total allocation units on disk. 131803769 allocation units available on disk. Internal Info: 00 e3 06 00 2e 57 06 00 2e 39 0c 00 00 00 00 00 .....W...9...... 4b 12 00 00 20 59 00 00 00 00 00 00 00 00 00 00 K... Y.......... Windows has finished checking your disk. Please wait while your computer restarts.[/quote] Ran it again after and it found nothing and my computer is faster (20 mb/s faster according to crystal disk mark).

 

Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

Here is what it found: Attachment 50691

 

Code: 2015-11-26 22:34:41, Info CSI 00005183 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-26 22:34:41, Info CSI 00005184 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys" 2015-11-26 22:34:41, Info CSI 00005185 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" : Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-11-26 22:34:41, Info CSI 00005186 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" : Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-11-26 22:34:41, Info CSI 00005187 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted[/quote] Please try following command in admin command prompt
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

 

I ran the commands and it found and fixed errors. Ran it again and no errors.
Ran SFC scannow again and it found and fixed all errors: Attachment 50775

Sadly I still can't go to sleep mode but the computer is much faster so that's good.

 

Try booting in safe mode and see if the problem still persist