Question Blue screen of death when waking up from sleep (BSOD)

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Colif

Win 11 Master
Moderator
Jun 12, 2015
55,526
4,335
160,590
10,082
Have you crashed since updating RST? I believe the dump results Gardenman showed last were from before the update?

if its not cause, you both have same problem. Your last dump is almost identical to his last crash. I don't normally see the same report results on 2 different machines (and yet its happened twice this week)

same actions: CPU looked for info in ram, didn't find it so it looked on the page file, actioned it and then crashed when it accessed ram next.
So its likely its following driver instructions as all of these steps below (see spoiler) which are in FILO order (First In, Last Out - the bottom actions were first in order of operation, the last ones were PC calling error) are exactly the same in your crash as they are his.

Page fault, This is a normal operation of windows. It happens when CPU has to access ram
Hardfault - This is a normal operation of windows. It happens when CPU has to access Page file
I won't explain it all (as I don't know it all) but all the ST_Store lines are in virtual memory
the bolded line is where I think it all started to fall apart

STACK_TEXT:
ffffe60438f08e78 fffff80065f94f6e : 0000000000000154 ffff8d0c4ac89000 ffffe60438f08f30 0000000000000002 : nt!KeBugCheckEx
ffffe60438f08e80 fffff80065e10f83 : ffff8d0c4ac89000 ffffe60438f08f30 ffffe60400000002 ffffe60438f08fe0 : nt!SMKM_STORE::SmStUnhandledExceptionFilter+0x7e
ffffe60438f08ed0 fffff80065dcd0ff : fffff80000000002 fffff80065ad4838 ffffe60438f04000 ffffe60438f0b000 : nt!SMKM_STORE::SmStDirectReadIssue'::1'::filt$0+0x22
ffffe60438f08f00 fffff80065e004df : fffff80065ad4838 ffffe60438f094e0 fffff80065dcd060 0000000000000000 : nt!_C_specific_handler+0x9f
ffffe60438f08f70 fffff80065ce6f97 : ffffe60438f094e0 0000000000000000 ffffe60438f0a3c0 fffff80065d056e9 : nt!RtlpExecuteHandlerForException+0xf
ffffe60438f08fa0 fffff80065ce5b96 : ffffe60438f09eb8 ffffe60438f09bf0 ffffe60438f09eb8 000001586b78e900 : nt!RtlDispatchException+0x297
ffffe60438f096c0 fffff80065e096ac : ffff8d0c4ac8b780 fffff80065cf8276 0000000000010000 ffffe60438f09f60 : nt!KiDispatchException+0x186
ffffe60438f09d80 fffff80065e05843 : 0000004800000000 ffffd603f8b31d40 0000000000000000 01d8469b573497d4 : nt!KiExceptionDispatch+0x12c
ffffe60438f09f60 fffff80065d317f0 : ffffc381a32ed000 ffff8d0c4ac89050 fffff80065d06660 ffffc381a32ed000 : nt!KiPageFault+0x443
ffffe60438f0a0f8 fffff80065d06660 : ffffc381a32ed000 ffffc381a32ed000 0000000000000002 000001586b78e900 : nt!RtlDecompressBufferXpressLz+0x50
ffffe60438f0a110 fffff80065d063a8 : ffffe60400000001 0000000000000000 0000000000000000 0200000000000000 : nt!RtlDecompressBufferEx+0x60
ffffe60438f0a160 fffff80065d06235 : 0000000000000004 fffff80065d05d9e 0000000000000000 0000000000000001 : nt!ST_STORE::StDmSinglePageCopy+0x150
ffffe60438f0a220 fffff80065d05a6c : 0000000000000001 000000000001e900 ffff8d0c4ac89000 ffff8d0c00003000 : nt!ST_STORE::StDmSinglePageTransfer+0xa5
ffffe60438f0a270 fffff80065d0589c : 00000000ffffffff ffff8d0c722f4000 ffffe60438f0a350 ffff8d0c70fa0290 : nt!ST_STORE::StDmpSinglePageRetrieve+0x180
ffffe60438f0a310 fffff80065d056e9 : ffffc3819b3c8730 0000000000000001 0000000000000000 0000000000000000 : nt!ST_STORE::StDmPageRetrieve+0xc8
ffffe60438f0a3c0 fffff80065d055a1 : ffff8d0c4ac89000 ffff8d0c70fa0290 ffff8d0c722f4000 ffff8d0c4ac8a9c0 : nt!SMKM_STORE::SmStDirectReadIssue+0x85
ffffe60438f0a440 fffff80065cf8618 : ffff8d0c72421080 ffff8d0c4ac89000 0000000000000000 ffff8d0c776031f0 : nt!SMKM_STORE::SmStDirectReadCallout+0x21
ffffe60438f0a470 fffff80065d030ff : fffff80065d05580 ffffe60438f0a510 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffe60438f0a4e0 fffff80065cd0fc4 : ffffe60438f0a5e0 0000000031526d73 00000000000003ff fffff800667229c0 : nt!SMKM_STORE::SmStDirectRead+0xc7
ffffe60438f0a5b0 fffff80065cd09f8 : 000000000000000c 00000000000003ff ffffe60438f0a660 fffff800667229c0 : nt!SMKM_STORE::SmStWorkItemQueue+0x1ac
ffffe60438f0a600 fffff80065d03b87 : 000000000000000c 0000000000000003 ffff8d0c70fa0290 ffff8d0c776031f0 : nt!SMKM_STORE_MGR::SmIoCtxQueueWork+0xc0
ffffe60438f0a690 fffff80065d5afcb : ffff8d0c00000003 ffff8d0c776032b0 0000000000000000 ffff8d0c4ac89000 : nt!SMKM_STORE_MGR::SmPageRead+0x167
ffffe60438f0a700 fffff80065c5df30 : 0000007f00000100 0000000000000000 ffffe60438f0a958 fffff80065c5be80 : nt!SmPageRead+0x33
ffffe60438f0a750 fffff80065c5b9dd : 0000000000000002 ffffe60438f0a7e0 ffffe60438f0a958 ffff8d0c776031a0 : nt!MiIssueHardFaultIo+0x10c
ffffe60438f0a7a0 fffff80065c9f5b8 : 00000000c0033333 0000000000000001 0000000001cebf98 0000000000000000 : nt!MiIssueHardFault+0x29d
ffffe60438f0a860 fffff80065e0575e : ffff8d0c72421000 ffff8d0c00000000 ffffe60438f0aa80 00007ffe02c23a10 : nt!MmAccessFault+0x468
ffffe60438f0aa00 00000000010d94de : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e

Drivers can bring a good PC to its knees. Its as simple as having a memory leak, taking memory from the system and not giving it back each time you finished but instead asking for more. Or if they old and are sending instructions that have been changed in the bios since their writing, or just being corrupt and telling CPU to look in the wrong locations in ram for information.


Another thing I noticed, your BIOS isn't reporting correctly,
its not telling the dump what BIOS you have. The same applies for the other guy.

so the question is, which one do you have now
search windows for System Information app
in the right hand column, next to BIOS Version/Date... what is it showing?
 
Last edited:

supremekaiqc

Reputable
Feb 11, 2018
79
1
4,530
0
Have you crashed since updating RST? I believe the dump results Gardenman showed last were from before the update?

if its not cause, you both have same problem. Your last dump is almost identical to his last crash. I don't normally see the same report results on 2 different machines (and yet its happened twice this week)

same actions: CPU looked for info in ram, didn't find it so it looked on the page file, actioned it and then crashed when it accessed ram next.
So its likely its following driver instructions as all of these steps below (see spoiler) which are in FILO order (First In, Last Out - the bottom actions were first in order of operation, the last ones were PC calling error) are exactly the same in your crash as they are his.

Page fault, This is a normal operation of windows. It happens when CPU has to access ram
Hardfault - This is a normal operation of windows. It happens when CPU has to access Page file
I won't explain it all (as I don't know it all) but all the ST_Store lines are in virtual memory
the bolded line is where I think it all started to fall apart

STACK_TEXT:
ffffe60438f08e78 fffff80065f94f6e : 0000000000000154 ffff8d0c4ac89000 ffffe60438f08f30 0000000000000002 : nt!KeBugCheckEx
ffffe60438f08e80 fffff80065e10f83 : ffff8d0c4ac89000 ffffe60438f08f30 ffffe60400000002 ffffe60438f08fe0 : nt!SMKM_STORE::SmStUnhandledExceptionFilter+0x7e
ffffe60438f08ed0 fffff80065dcd0ff : fffff80000000002 fffff80065ad4838 ffffe60438f04000 ffffe60438f0b000 : nt!SMKM_STORE::SmStDirectReadIssue'::1'::filt$0+0x22
ffffe60438f08f00 fffff80065e004df : fffff80065ad4838 ffffe60438f094e0 fffff80065dcd060 0000000000000000 : nt!_C_specific_handler+0x9f
ffffe60438f08f70 fffff80065ce6f97 : ffffe60438f094e0 0000000000000000 ffffe60438f0a3c0 fffff80065d056e9 : nt!RtlpExecuteHandlerForException+0xf
ffffe60438f08fa0 fffff80065ce5b96 : ffffe60438f09eb8 ffffe60438f09bf0 ffffe60438f09eb8 000001586b78e900 : nt!RtlDispatchException+0x297
ffffe60438f096c0 fffff80065e096ac : ffff8d0c4ac8b780 fffff80065cf8276 0000000000010000 ffffe60438f09f60 : nt!KiDispatchException+0x186
ffffe60438f09d80 fffff80065e05843 : 0000004800000000 ffffd603f8b31d40 0000000000000000 01d8469b573497d4 : nt!KiExceptionDispatch+0x12c
ffffe60438f09f60 fffff80065d317f0 : ffffc381a32ed000 ffff8d0c4ac89050 fffff80065d06660 ffffc381a32ed000 : nt!KiPageFault+0x443
ffffe60438f0a0f8 fffff80065d06660 : ffffc381a32ed000 ffffc381a32ed000 0000000000000002 000001586b78e900 : nt!RtlDecompressBufferXpressLz+0x50
ffffe60438f0a110 fffff80065d063a8 : ffffe60400000001 0000000000000000 0000000000000000 0200000000000000 : nt!RtlDecompressBufferEx+0x60
ffffe60438f0a160 fffff80065d06235 : 0000000000000004 fffff80065d05d9e 0000000000000000 0000000000000001 : nt!ST_STORE::StDmSinglePageCopy+0x150
ffffe60438f0a220 fffff80065d05a6c : 0000000000000001 000000000001e900 ffff8d0c4ac89000 ffff8d0c00003000 : nt!ST_STORE::StDmSinglePageTransfer+0xa5
ffffe60438f0a270 fffff80065d0589c : 00000000ffffffff ffff8d0c722f4000 ffffe60438f0a350 ffff8d0c70fa0290 : nt!ST_STORE::StDmpSinglePageRetrieve+0x180
ffffe60438f0a310 fffff80065d056e9 : ffffc3819b3c8730 0000000000000001 0000000000000000 0000000000000000 : nt!ST_STORE::StDmPageRetrieve+0xc8
ffffe60438f0a3c0 fffff80065d055a1 : ffff8d0c4ac89000 ffff8d0c70fa0290 ffff8d0c722f4000 ffff8d0c4ac8a9c0 : nt!SMKM_STORE::SmStDirectReadIssue+0x85
ffffe60438f0a440 fffff80065cf8618 : ffff8d0c72421080 ffff8d0c4ac89000 0000000000000000 ffff8d0c776031f0 : nt!SMKM_STORE::SmStDirectReadCallout+0x21
ffffe60438f0a470 fffff80065d030ff : fffff80065d05580 ffffe60438f0a510 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffe60438f0a4e0 fffff80065cd0fc4 : ffffe60438f0a5e0 0000000031526d73 00000000000003ff fffff800667229c0 : nt!SMKM_STORE::SmStDirectRead+0xc7
ffffe60438f0a5b0 fffff80065cd09f8 : 000000000000000c 00000000000003ff ffffe60438f0a660 fffff800667229c0 : nt!SMKM_STORE::SmStWorkItemQueue+0x1ac
ffffe60438f0a600 fffff80065d03b87 : 000000000000000c 0000000000000003 ffff8d0c70fa0290 ffff8d0c776031f0 : nt!SMKM_STORE_MGR::SmIoCtxQueueWork+0xc0
ffffe60438f0a690 fffff80065d5afcb : ffff8d0c00000003 ffff8d0c776032b0 0000000000000000 ffff8d0c4ac89000 : nt!SMKM_STORE_MGR::SmPageRead+0x167
ffffe60438f0a700 fffff80065c5df30 : 0000007f00000100 0000000000000000 ffffe60438f0a958 fffff80065c5be80 : nt!SmPageRead+0x33
ffffe60438f0a750 fffff80065c5b9dd : 0000000000000002 ffffe60438f0a7e0 ffffe60438f0a958 ffff8d0c776031a0 : nt!MiIssueHardFaultIo+0x10c
ffffe60438f0a7a0 fffff80065c9f5b8 : 00000000c0033333 0000000000000001 0000000001cebf98 0000000000000000 : nt!MiIssueHardFault+0x29d
ffffe60438f0a860 fffff80065e0575e : ffff8d0c72421000 ffff8d0c00000000 ffffe60438f0aa80 00007ffe02c23a10 : nt!MmAccessFault+0x468
ffffe60438f0aa00 00000000010d94de : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e

Drivers can bring a good PC to its knees. Its as simple as having a memory leak, taking memory from the system and not giving it back each time you finished but instead asking for more. Or if they old and are sending instructions that have been changed in the bios since their writing, or just being corrupt and telling CPU to look in the wrong locations in ram for information.


Another thing I noticed, your BIOS isn't reporting correctly,
its not telling the dump what BIOS you have. The same applies for the other guy.

so the question is, which one do you have now
search windows for System Information app
in the right hand column, next to BIOS Version/Date... what is it showing?
sorry for late reply I went to sleep so it says
BIOS/DATE Insyde V1.06, 2020-11-25
 

supremekaiqc

Reputable
Feb 11, 2018
79
1
4,530
0
np, i went to sleep too.. its your thread. You reply when you want :)

You on an even older version of bios to the other guy.
But its also the latest for your laptop so thats not really an answer - https://www.acer.com/ac/en/US/content/support-product/8482?b=1

just thought I would check :)
its weird because I had a older gaming laptop it would get BSOD randomly so Acer gave me this one as replacement and it does BSOD too :/
 

supremekaiqc

Reputable
Feb 11, 2018
79
1
4,530
0
any BSOD since replacing driver yesterday?

could be it was refurbished and it wasn't fixed from what ever problem was... or was it new?
well no BSOD since i installed SetupRST but I only get Bsod waking from sleep and no other ways and it takes usually 2-3 weeks of sleeping everyday before i get one.

the PC was like new
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
55,526
4,335
160,590
10,082
both of you had same error after 18 days on.

So I should set a calendar for then?

If it keeps happening, I would restart PC occasionally and see if that puts the errors off

try a restart once a week, on same day. It beats crashing.
 

supremekaiqc

Reputable
Feb 11, 2018
79
1
4,530
0
both of you had same error after 18 days on.

So I should set a calendar for then?

If it keeps happening, I would restart PC occasionally and see if that puts the errors off

try a restart once a week, on same day. It beats crashing.
If i restart the computer once a week though we wont know if the problem is solved
 

supremekaiqc

Reputable
Feb 11, 2018
79
1
4,530
0
I did say if it keeps happening... I didn't say to do it now.

I mean, if in 3 weeks it does it again, starting once a week/fortnight sure beats crashing
yeah alright let's wait then I hope it's fixed because the last crash made me lose some unsaved work really pissed me off
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
55,526
4,335
160,590
10,082
so save work every day so you don't lose any. Its why shutting down once in a while is a good idea. It also flushes memory.

Problem with BSOD is often you don't know they fixed until they stop happening.

So only time your PC is off is during a windows update? You lucky you don't have a memory leak.

@nooblet0 might be waiting a while as well. He is waiting to see if this is answer as he has same driver version on his PC. Shame as if he updated to it, I would have a pool of 2 Acer trying same fix.
 

supremekaiqc

Reputable
Feb 11, 2018
79
1
4,530
0
I haven't came back on this thread since april 4 and today I am back just to say its been 1 month and two weeks since my last bsod and I feel like my problem has been fixed. I am beyond happy thanks everyone
 
Reactions: Colif

nooblet0

Reputable
Apr 14, 2019
29
1
4,535
0
I haven't came back on this thread since april 4 and today I am back just to say its been 1 month and two weeks since my last bsod and I feel like my problem has been fixed. I am beyond happy thanks everyone
Cheers. I haven't had any issues since updating either; but as far as the issue being resolved is concerned, the jury's still out on that; considering the fact that I had a gap of something like 4 months between my first and second BSOD lol. Here's hoping for the best.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
55,526
4,335
160,590
10,082
I have helped too many people with BSOD to ever be sure they gone. One month might be enough, depends how often they occured before. I have helped people where it only happened once a month so...

I do wish you luck, but I also hope this isn't a jinx :)
 

ASK THE COMMUNITY

TRENDING THREADS