Windows 10: Consistent BSODs after waking from sleep

Since installing Windows 10 Pro 64bit a couple of weeks ago, I've gotten consistent BSODs when waking desktop pc from sleep. Mostly store_exceptions and kernal_data_inpage errors... but others hv occurred as well.

The one common factor is that the BSOD ALWAYS occurs when resuming from sleep.

I also included a WinDBG output file since it returned an error almost immediately.

:)

 

Custom keyboard shortcuts slow to execute

The one consistent replication of the problem of delayed custom shortcut keys (for me) is the waking from sleep. Even after items that linger when closed (calculator, search, etc.) doesn't slow shortcuts consistently; just sleep.

Note that I have hybrid sleep off which solved a few things in Win 7, but not Win 10. Desktop clicks of these same shortcuts run normal before/after wake. Do a restart, speed returns to that of Win 7.

 

Blue Screen die (BSOD), Windows 10 Professional Laptop Machine

I can confirm that this problem would occur every time I wake the computer up from sleep mode.

After a few seconds waking up from sleep mode, the computer will freeze and then BSOD occurs

Very annoying.

 

Hi lp009,

Is the Realtek LAN driver from Realtek directly? In any way install the drivers ASUS provides for your motherboard.
Your Realtek LAN driver has been flagged.
M5A99FX PRO R2.0 | Motherboards | ASUS Global

Code: 0: kd> lmvm rt640x64 Browse full module list start end module name fffff801`6eb80000 fffff801`6ec66000 rt640x64 T (no symbols) Loaded symbol image file: rt640x64.sys Image path: \SystemRoot\System32\drivers\rt640x64.sys Image name: rt640x64.sys Browse all global symbols functions data Timestamp: Fri Mar 11 06:57:50 2016 (56E25E5E) CheckSum: 000EE0F5 ImageSize: 000E6000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Thx for the reply Axe0..

Yes, the drivers are from Realtek. I originally used the Asus version from their site. But after hv'ing read that installing the latest drivers was paramount in fixing BSODs, I searched for updated versions for all hardware components: sound card, network, chipset, video etc.. I only installed those that I found that were rated for windows 10.

I will uninstall and use the drivers from ASUS.

 

I'm still having issues.. have installed ASUS' realtek lan drivers. Today, while resuming from sleep, "critical process died" BSOD. <br><br>Are there any other problems that you see in the dump files? Or should I upload the latest crash files?

 

Definitely upload the latest, just re-run DM_Log_collector and upload the zip file.

 

I've uninstalled and reinstalled each of the driver packages I've gotten from Asus (for my mobo model) and from the Realtek site. I've found that when using the drivers from ASUS, my pc BSODs more frequently than when using the latest drivers from Realtek. But regardless of which I use, I still get BSODs. Of course, I'm not certain that the drivers are the sole culprit. Is there anything else in the logs that I should be looking at? Or maybe another (older?) version of the LAN drivers that might work? Any thoughts or suggestions would be greatly appreciated.

 

There is more than enough to let us think the file system may be corrupted.






Diagnostics Test

HDD TEST
*Arrow Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

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 says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\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.

Make a photo of SFC and post it.


Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: ffffc00137d2e990, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000000e, error status (normally i/o status code) Arg3: 00000001f07cc860, current process (virtual address for lock type 3, or PTE) Arg4: fffff801d2b1e5e0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !volmgrx 244 errors : !volmgrx (fffff800d03c1000-fffff800d03c10ff) fffff800d03c1000 *00 *40 *00 *00 *88 *3f *00 *00 *08 *40 *00 *00 *00 *00 *00 *00 .@...?...@...... fffff800d03c1010 *95 *8d *2b *16 *3e *00 *00 00 *54 *00 *00 *00 *00 *00 *00 *00 ..+.>...T....... fffff800d03c1020 *20 *00 *5e *cb *01 *e0 *ff *ff *05 *00 *10 *00 *03 *00 *00 *00 .^............. fffff800d03c1030 *88 *3f *00 *00 *20 *00 *00 *00 *38 *90 *a0 *d3 *01 *e0 *ff *ff .?.. ...8....... fffff800d03c1040 *38 *20 *72 *ce *01 *e0 *ff *ff *02 *01 *13 *c0 *01 *00 *00 *00 8 r............. fffff800d03c1050 *3c *02 *00 *00 *04 *00 *00 *00 *dc *89 *2b *16 *3e 00 *00 *00 <.........+.>... fffff800d03c1060 *3a *3b *1c *33 *05 *20 *c2 *44 *ac *5e *77 *22 *0c *37 *d6 *b4 :;.3. .D.^w".7.. fffff800d03c1070 *07 *00 *01 *10 *04 *01 *27 *00 *08 *00 *00 *00 *00 00 00 *40 ......'........@ fffff800d03c1080 *01 *00 *00 *00 00 *00 *00 *00 00 *00 *00 *00 *00 *00 *00 *00 ................ fffff800d03c1090 *00 *00 *00 *00 *00 *00 *00 00 *20 00 *0c *00 *00 *00 *16 *00 ........ ....... fffff800d03c10a0 *16 *00 *00 *13 00 *01 *1a *73 *50 *4f *cf *89 *82 *47 *b3 *e0 .......sPO...G.. fffff800d03c10b0 *dc *e8 *c9 *04 *76 *ba *00 *00 *a0 *c6 *ef *d0 *01 *e0 *ff *ff ....v........... fffff800d03c10c0 *01 *00 *00 *00 *02 *e0 *fa *01 *cc *01 *e0 *ff *ff *3d *00 *50 .............=.P fffff800d03c10d0 *00 *43 *00 *49 *00 *5c *00 *56 *00 *45 *00 *4e 00 *5f 00 *31 .C.I.\.V.E.N._.1 fffff800d03c10e0 *00 *30 *00 *44 *00 *45 00 *26 *00 *44 *00 *45 *00 *56 *00 *5f .0.D.E.&.D.E.V._ fffff800d03c10f0 *00 *31 *00 *32 *00 *34 *00 *34 *00 *26 *00 *53 *00 *55 *00 *42 .1.2.4.4.&.S.U.B THREAD_SHA1_HASH_MOD_FUNC: f64ca59882dfb043fa6c72b6a260cbda6fefe6ce THREAD_SHA1_HASH_MOD_FUNC_OFFSET: cd56dadc77aa96d20fdc939f246f18b900867cee THREAD_SHA1_HASH_MOD: ef0b9811d1c3c2b0b400d0c8a17067df59efd56d FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware_disk IMAGE_NAME: hardware_disk DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: 0x154_c0000006_c00000c0_IMAGE_hardware_disk BUCKET_ID: 0x154_c0000006_c00000c0_IMAGE_hardware_disk PRIMARY_PROBLEM_CLASS: 0x154_c0000006_c00000c0_IMAGE_hardware_disk TARGET_TIME: 2016-06-12T19:29:44.000Z OSBUILD: 10586 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !spaceport fffff80120e44001-fffff80120e44026 38 bytes - spaceport! ?? ::FNODOBFM::`string'+4a61 [ 00 48 8d 15 3f af 01 00:90 a2 00 00 00 00 00 20 ] fffff80120e44029-fffff80120e44033 11 bytes - spaceport! ?? ::FNODOBFM::`string'+4a89 (+0x28) [ 90 e9 7d 63 ff ff cc 8b:00 00 00 00 00 00 00 00 ] fffff80120e44035-fffff80120e44038 4 bytes - spaceport! ?? ::FNODOBFM::`string'+4a95 (+0x0c) [ ff ff ff 3d:00 00 00 00 ] fffff80120e4403a-fffff80120e44062 41 bytes - spaceport! ?? ::FNODOBFM::`string'+4a9a (+0x05) [ 4e 43 52 0f 85 88 64 ff:00 00 00 00 00 00 c4 13 ] fffff80120e44064-fffff80120e44099 54 bytes - spaceport! ?? ::FNODOBFM::`string'+4ac4 (+0x2a) [ 4c 8b c0 4c 8d 4d 18 0f:00 00 00 00 00 00 00 00 ] fffff80120e4409c-fffff80120e440a3 8 bytes - spaceport! ?? ::FNODOBFM::`string'+4afc (+0x38) [ 90 e9 6f 64 ff ff 3d 11:00 00 00 00 00 00 00 00 ] fffff80120e440a6-fffff80120e440aa 5 bytes - spaceport! ?? ::FNODOBFM::`string'+4b06 (+0x0a) [ 80 0f 85 22 01:00 00 00 00 00 ] fffff80120e440ad-fffff80120e440ea 62 bytes - spaceport! ?? ::FNODOBFM::`string'+4b0d (+0x07) [ 66 c7 43 03 04 18 e9 2e:00 00 00 00 00 00 00 00 ] fffff80120e440ec-fffff80120e440ff 20 bytes - spaceport! ?? ::FNODOBFM::`string'+4b4c (+0x3f) [ 88 45 d2 e9 f2 65 ff ff:00 00 00 00 00 00 00 00 ] fffff80120e44e44-fffff80120e44e4a 7 bytes - spaceport! ?? ::FNODOBFM::`string'+58a4 (+0xd58) [ 48 8b cf e8 68 51 05:00 00 00 00 00 00 00 ] fffff80120e44e4c-fffff80120e44e58 13 bytes - spaceport! ?? ::FNODOBFM::`string'+58ac (+0x08) [ 90 e9 6e 69 ff ff 48 8b:00 00 00 00 00 00 00 00 ] fffff80120e44e5a-fffff80120e44e61 8 bytes - spaceport! ?? ::FNODOBFM::`string'+58ba (+0x0e) [ 90 e9 60 69 ff ff b9 03:00 00 00 00 00 00 00 00 ] fffff80120e44e65-fffff80120e44e69 5 bytes - spaceport! ?? ::FNODOBFM::`string'+58c5 (+0x0b) [ 89 0d 85 42 02:00 00 00 00 00 ] fffff80120e44e6b-fffff80120e44e86 28 bytes - spaceport! ?? ::FNODOBFM::`string'+58cb (+0x06) [ e9 02 6a ff ff 41 0f b6:00 00 00 00 00 00 00 00 ] fffff80120e44e88-fffff80120e44e89 2 bytes - spaceport! ?? ::FNODOBFM::`string'+58e8 (+0x1d) [ ba 23:00 00 ] fffff80120e44e8d-fffff80120e44e93 7 bytes - spaceport! ?? ::FNODOBFM::`string'+58ed (+0x05) [ 89 5c 24 20 e8 1a 1d:00 00 00 00 00 00 00 ] fffff80120e44e96-fffff80120e44eaf 26 bytes - spaceport! ?? ::FNODOBFM::`string'+58f6 (+0x09) [ 90 e9 88 69 ff ff 80 79:00 00 00 00 00 00 00 00 ] fffff80120e44eb1-fffff80120e44eb2 2 bytes - spaceport! ?? ::FNODOBFM::`string'+5911 (+0x1b) [ ba 53:00 00 ] fffff80120e44eb6-fffff80120e44eb8 3 bytes - spaceport! ?? ::FNODOBFM::`string'+5916 (+0x05) [ e8 51 26:00 00 00 ] fffff80120e44ebb-fffff80120e44ec2 8 bytes - spaceport! ?? ::FNODOBFM::`string'+591b (+0x05) [ 90 e9 70 6a ff ff bb 04:00 00 00 00 00 00 00 00 ] fffff80120e44ec5-fffff80120e44ede 26 bytes - spaceport! ?? ::FNODOBFM::`string'+5925 (+0x0a) [ c0 e9 c1 6b ff ff 80 79:00 00 00 00 00 00 00 00 ] fffff80120e44ee2-fffff80120e44ef0 15 bytes - spaceport! ?? ::FNODOBFM::`string'+5942 (+0x1d) [ 48 89 44 24 20 4c 8d 4d:00 00 00 00 00 00 00 00 ] fffff80120e44ef2-fffff80120e44ef4 3 bytes - spaceport! ?? ::FNODOBFM::`string'+5952 (+0x10) [ e8 71 26:00 00 00 ] fffff80120e44ef7-fffff80120e44efe 8 bytes - spaceport! ?? ::FNODOBFM::`string'+5957 (+0x05) [ 90 e9 85 6a ff ff bb 23:00 00 00 00 00 00 00 00 ] fffff80120e44f01-fffff80120e44f05 5 bytes - spaceport! ?? ::FNODOBFM::`string'+5961 (+0x0a) [ c0 eb 05 bb 30:00 00 00 00 00 ] fffff80120e44f07-fffff80120e44f0b 5 bytes - spaceport! ?? ::FNODOBFM::`string'+5967 (+0x06) [ 38 c0 41 bd 05:00 00 00 00 00 ] fffff80120e44f0e-fffff80120e44f40 51 bytes - spaceport! ?? ::FNODOBFM::`string'+596e (+0x07) [ 80 e9 78 6b ff ff 0f 10:00 00 00 00 00 00 00 00 ] fffff80120e44f43 - spaceport! ?? ::FNODOBFM::`string'+59a3 (+0x35) [ 8b:00 ] 466 errors : !spaceport (fffff80120e44001-fffff80120e44f43) THREAD_SHA1_HASH_MOD_FUNC: c3645e90816e0fe9682b272f9f80fa11fc64443d THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 66c5ed23e2b1e97cfd6c2f278486fbc2af637773 THREAD_SHA1_HASH_MOD: 18de883f0f7a44ee1c6adccce64512484d76eb74 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware_disk IMAGE_NAME: hardware_disk DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: 0x154_c0000006_c000000e_IMAGE_hardware_disk BUCKET_ID: 0x154_c0000006_c000000e_IMAGE_hardware_disk PRIMARY_PROBLEM_CLASS: 0x154_c0000006_c000000e_IMAGE_hardware_disk TARGET_TIME: 2016-06-15T02:42:06.000Z OSBUILD: 10586[/quote]

 

Ok.. I've finished the tests/diagnostics requested. The only test that produced any errors was the "sfc/scannow" tests.

I did all of the seatools tests.. but only made screen shot of the Long Generic, which is included. Forgot to do such for ShortDriveSelfTest and Short Generic, but ALL of the SeaTools tests produced NO ERRORS.

Included in the zip file "6300 system tests and diag":
- SeaTools Long Generic screenshot (as stated above, No other SEATOOLS screenshots are included but all tests were error-free)
- chkdsk log
- HDTUNE Benchmark/Error Scan/Health requested screenshots for each of the four harddrives: WDC 320, WDC 640, ST 2000, PNY SSD (boot)
- CBS.log

 

What command did you use with chkdsk?

The CBS error is nothing to worry about, it is a bug that Microsoft is trying to fix.

 

just as requested... sfc/scannow.. I'm running it again... now... as I see that I was supposed to post a screenshot of the output.. but other than "Windows Resource Protection found corrupt files but was unable to fix some of them" msg.. I don't remember there being any other output.

Which is why I'm running it again..

sorry.. disregard.. you asked about chkdsk... lack of sleep is playing with my mind. *Confused

Windows 10 didn't present any option but scan..
Attachment 85599

Truthfully, didn't even realize that the other options were missing (no longer available??) as I've only used this command a few times since installing W10.

 

Please open command prompt as administrator, search cmd > right click and choose 'run as administrator'
Enter following command
Code: chkdsk C: /r[/quote] The partition needs to be not in use, so you have to reboot for it, enter Y to schedule the command on next reboot and restart your system.
Please note that this may take a while and it may look like it is frozen, let it finish as it could suddenly finish from 11% to 100% after hours.
Please do NOT interrupt it, interrupting may lead to boot problems as it is possible that this command runs every reboot when interrupting. The only way to fix such boot problems is by pressing any key at the right time what can be difficult sometimes.

Change C to the partition letter the next time you run it, it is better to run this command for each partition.

 

Thank you *Smile

The logs look good, let us know in case of any BSOD occurs again.