SkyNetRising
Titan
Why do you insist on using sleep, if it causes crashes all the time?it only happens when I wake from sleep after like 2-3 weeks time
but this time i can confirm it was on sleep for over 12hours
Disable and don't use sleep.
Why do you insist on using sleep, if it causes crashes all the time?it only happens when I wake from sleep after like 2-3 weeks time
but this time i can confirm it was on sleep for over 12hours
nah i never turn it off i just put it to sleep every daymaybe i am misunderstanding this but are you telling me that you left your laptop on sleep mode for 2-3 weeks lol?
A good pc shouldnt crashWhy do you insist on using sleep, if it causes crashes all the time?
Disable and don't use sleep.
Even on best PC - bad device drivers can cause crash.A good pc shouldnt crash
38f08e78 fffff800
65f94f6e : 0000000000000154 ffff8d0c
4ac89000 ffffe60438f08f30 00000000
00000002 : nt!KeBugCheckEx38f08e80 fffff800
65e10f83 : ffff8d0c4ac89000 ffffe604
38f08f30 ffffe60400000002 ffffe604
38f08fe0 : nt!SMKM_STORE::SmStUnhandledExceptionFilter+0x7e38f08ed0 fffff800
65dcd0ff : fffff80000000002 fffff800
65ad4838 ffffe60438f04000 ffffe604
38f0b000 : nt!SMKM_STORE::SmStDirectReadIssue'::
1'::filt$0+0x2238f08f00 fffff800
65e004df : fffff80065ad4838 ffffe604
38f094e0 fffff80065dcd060 00000000
00000000 : nt!_C_specific_handler+0x9f38f08f70 fffff800
65ce6f97 : ffffe60438f094e0 00000000
00000000 ffffe60438f0a3c0 fffff800
65d056e9 : nt!RtlpExecuteHandlerForException+0xf38f08fa0 fffff800
65ce5b96 : ffffe60438f09eb8 ffffe604
38f09bf0 ffffe60438f09eb8 00000158
6b78e900 : nt!RtlDispatchException+0x29738f096c0 fffff800
65e096ac : ffff8d0c4ac8b780 fffff800
65cf8276 0000000000010000 ffffe604
38f09f60 : nt!KiDispatchException+0x18638f09d80 fffff800
65e05843 : 0000004800000000 ffffd603
f8b31d40 0000000000000000 01d8469b
573497d4 : nt!KiExceptionDispatch+0x12c38f09f60 fffff800
65d317f0 : ffffc381a32ed000 ffff8d0c
4ac89050 fffff80065d06660 ffffc381
a32ed000 : nt!KiPageFault+0x44338f0a0f8 fffff800
65d06660 : ffffc381a32ed000 ffffc381
a32ed000 0000000000000002 00000158
6b78e900 : nt!RtlDecompressBufferXpressLz+0x5038f0a110 fffff800
65d063a8 : ffffe60400000001 00000000
00000000 0000000000000000 02000000
00000000 : nt!RtlDecompressBufferEx+0x6038f0a160 fffff800
65d06235 : 0000000000000004 fffff800
65d05d9e 0000000000000000 00000000
00000001 : nt!ST_STORE::StDmSinglePageCopy+0x15038f0a220 fffff800
65d05a6c : 0000000000000001 00000000
0001e900 ffff8d0c4ac89000 ffff8d0c
00003000 : nt!ST_STORE::StDmSinglePageTransfer+0xa538f0a270 fffff800
65d0589c : 00000000ffffffff ffff8d0c
722f4000 ffffe60438f0a350 ffff8d0c
70fa0290 : nt!ST_STORE::StDmpSinglePageRetrieve+0x18038f0a310 fffff800
65d056e9 : ffffc3819b3c8730 00000000
00000001 0000000000000000 00000000
00000000 : nt!ST_STORE::StDmPageRetrieve+0xc838f0a3c0 fffff800
65d055a1 : ffff8d0c4ac89000 ffff8d0c
70fa0290 ffff8d0c722f4000 ffff8d0c
4ac8a9c0 : nt!SMKM_STORE::SmStDirectReadIssue+0x8538f0a440 fffff800
65cf8618 : ffff8d0c72421080 ffff8d0c
4ac89000 0000000000000000 ffff8d0c
776031f0 : nt!SMKM_STORE::SmStDirectReadCallout+0x2138f0a470 fffff800
65d030ff : fffff80065d05580 ffffe604
38f0a510 0000000000000003 00000000
00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x7838f0a4e0 fffff800
65cd0fc4 : ffffe60438f0a5e0 00000000
31526d73 00000000000003ff fffff800
667229c0 : nt!SMKM_STORE::SmStDirectRead+0xc738f0a5b0 fffff800
65cd09f8 : 000000000000000c 00000000
000003ff ffffe60438f0a660 fffff800
667229c0 : nt!SMKM_STORE::SmStWorkItemQueue+0x1ac38f0a600 fffff800
65d03b87 : 000000000000000c 00000000
00000003 ffff8d0c70fa0290 ffff8d0c
776031f0 : nt!SMKM_STORE_MGR::SmIoCtxQueueWork+0xc038f0a690 fffff800
65d5afcb : ffff8d0c00000003 ffff8d0c
776032b0 0000000000000000 ffff8d0c
4ac89000 : nt!SMKM_STORE_MGR::SmPageRead+0x16738f0a700 fffff800
65c5df30 : 0000007f00000100 00000000
00000000 ffffe60438f0a958 fffff800
65c5be80 : nt!SmPageRead+0x3338f0a750 fffff800
65c5b9dd : 0000000000000002 ffffe604
38f0a7e0 ffffe60438f0a958 ffff8d0c
776031a0 : nt!MiIssueHardFaultIo+0x10c38f0a7a0 fffff800
65c9f5b8 : 00000000c0033333 00000000
00000001 0000000001cebf98 00000000
00000000 : nt!MiIssueHardFault+0x29d38f0a860 fffff800
65e0575e : ffff8d0c72421000 ffff8d0c
00000000 ffffe60438f0aa80 00007ffe
02c23a10 : nt!MmAccessFault+0x46838f0aa00 00000000
010d94de : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : nt!KiPageFault+0x35esorry for late reply I went to sleep so it saysHave 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 fffff800
65f94f6e : 0000000000000154 ffff8d0c
4ac89000 ffffe60438f08f30 00000000
00000002 : nt!KeBugCheckEx
ffffe60438f08e80 fffff800
65e10f83 : ffff8d0c4ac89000 ffffe604
38f08f30 ffffe60400000002 ffffe604
38f08fe0 : nt!SMKM_STORE::SmStUnhandledExceptionFilter+0x7e
ffffe60438f08ed0 fffff800
65dcd0ff : fffff80000000002 fffff800
65ad4838 ffffe60438f04000 ffffe604
38f0b000 : nt!SMKM_STORE::SmStDirectReadIssue'::
1'::filt$0+0x22
ffffe60438f08f00 fffff800
65e004df : fffff80065ad4838 ffffe604
38f094e0 fffff80065dcd060 00000000
00000000 : nt!_C_specific_handler+0x9f
ffffe60438f08f70 fffff800
65ce6f97 : ffffe60438f094e0 00000000
00000000 ffffe60438f0a3c0 fffff800
65d056e9 : nt!RtlpExecuteHandlerForException+0xf
ffffe60438f08fa0 fffff800
65ce5b96 : ffffe60438f09eb8 ffffe604
38f09bf0 ffffe60438f09eb8 00000158
6b78e900 : nt!RtlDispatchException+0x297
ffffe60438f096c0 fffff800
65e096ac : ffff8d0c4ac8b780 fffff800
65cf8276 0000000000010000 ffffe604
38f09f60 : nt!KiDispatchException+0x186
ffffe60438f09d80 fffff800
65e05843 : 0000004800000000 ffffd603
f8b31d40 0000000000000000 01d8469b
573497d4 : nt!KiExceptionDispatch+0x12c
ffffe60438f09f60 fffff800
65d317f0 : ffffc381a32ed000 ffff8d0c
4ac89050 fffff80065d06660 ffffc381
a32ed000 : nt!KiPageFault+0x443
ffffe60438f0a0f8 fffff800
65d06660 : ffffc381a32ed000 ffffc381
a32ed000 0000000000000002 00000158
6b78e900 : nt!RtlDecompressBufferXpressLz+0x50
ffffe60438f0a110 fffff800
65d063a8 : ffffe60400000001 00000000
00000000 0000000000000000 02000000
00000000 : nt!RtlDecompressBufferEx+0x60
ffffe60438f0a160 fffff800
65d06235 : 0000000000000004 fffff800
65d05d9e 0000000000000000 00000000
00000001 : nt!ST_STORE::StDmSinglePageCopy+0x150
ffffe60438f0a220 fffff800
65d05a6c : 0000000000000001 00000000
0001e900 ffff8d0c4ac89000 ffff8d0c
00003000 : nt!ST_STORE::StDmSinglePageTransfer+0xa5
ffffe60438f0a270 fffff800
65d0589c : 00000000ffffffff ffff8d0c
722f4000 ffffe60438f0a350 ffff8d0c
70fa0290 : nt!ST_STORE::StDmpSinglePageRetrieve+0x180
ffffe60438f0a310 fffff800
65d056e9 : ffffc3819b3c8730 00000000
00000001 0000000000000000 00000000
00000000 : nt!ST_STORE::StDmPageRetrieve+0xc8
ffffe60438f0a3c0 fffff800
65d055a1 : ffff8d0c4ac89000 ffff8d0c
70fa0290 ffff8d0c722f4000 ffff8d0c
4ac8a9c0 : nt!SMKM_STORE::SmStDirectReadIssue+0x85
ffffe60438f0a440 fffff800
65cf8618 : ffff8d0c72421080 ffff8d0c
4ac89000 0000000000000000 ffff8d0c
776031f0 : nt!SMKM_STORE::SmStDirectReadCallout+0x21
ffffe60438f0a470 fffff800
65d030ff : fffff80065d05580 ffffe604
38f0a510 0000000000000003 00000000
00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffe60438f0a4e0 fffff800
65cd0fc4 : ffffe60438f0a5e0 00000000
31526d73 00000000000003ff fffff800
667229c0 : nt!SMKM_STORE::SmStDirectRead+0xc7
ffffe60438f0a5b0 fffff800
65cd09f8 : 000000000000000c 00000000
000003ff ffffe60438f0a660 fffff800
667229c0 : nt!SMKM_STORE::SmStWorkItemQueue+0x1ac
ffffe60438f0a600 fffff800
65d03b87 : 000000000000000c 00000000
00000003 ffff8d0c70fa0290 ffff8d0c
776031f0 : nt!SMKM_STORE_MGR::SmIoCtxQueueWork+0xc0
ffffe60438f0a690 fffff800
65d5afcb : ffff8d0c00000003 ffff8d0c
776032b0 0000000000000000 ffff8d0c
4ac89000 : nt!SMKM_STORE_MGR::SmPageRead+0x167
ffffe60438f0a700 fffff800
65c5df30 : 0000007f00000100 00000000
00000000 ffffe60438f0a958 fffff800
65c5be80 : nt!SmPageRead+0x33
ffffe60438f0a750 fffff800
65c5b9dd : 0000000000000002 ffffe604
38f0a7e0 ffffe60438f0a958 ffff8d0c
776031a0 : nt!MiIssueHardFaultIo+0x10c
ffffe60438f0a7a0 fffff800
65c9f5b8 : 00000000c0033333 00000000
00000001 0000000001cebf98 00000000
00000000 : nt!MiIssueHardFault+0x29d
ffffe60438f0a860 fffff800
65e0575e : ffff8d0c72421000 ffff8d0c
00000000 ffffe60438f0aa80 00007ffe
02c23a10 : nt!MmAccessFault+0x468
ffffe60438f0aa00 00000000
010d94de : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : 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?
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 :/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![]()
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.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?
If i restart the computer once a week though we wont know if the problem is solvedboth 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.
yeah alright let's wait then I hope it's fixed because the last crash made me lose some unsaved work really pissed me offI 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 i updated too. lets see if this helps.Shame as if he updated to it, I would have a pool of 2 Acer trying same fix.
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.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