New
#1
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
BSOD on sleep, intelppm.sys
-
-
New #2
It seems there is a little more going on then just a driver problem.
This means a hard drive related problem
The CPU driver seems to be corrupted.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)
Please check your manufacturer for driver updates for your CPUCode: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)
Please test your hard drive.
Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html
NoteDo 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.
-
New #3
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?
-
New #4
Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums
NoteIf you're overclocking anything, please stop it and set everything back to default while troubleshooting
WarningYour CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
-
-
New #6
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.
-
-
New #8
Well I ran CHKDSK again and it found and fixed some errors but I still can't enter sleep mode.
Ran it again after and it found nothing and my computer is faster (20 mb/s faster according to crystal disk mark).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.
-
-
New #9
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.
-
New #10
Here is what it found: Attachment 50691
Quote
Related Discussions
