Windows 10: BSOD & crashes overnight when returning from sleep? Solved

  1.    03 Dec 2017 #1

    BSOD & crashes overnight when returning from sleep?


    This is my first post so apologies if I do something wrong or unhelpful!

    Every night I put my Toshiba laptop to sleep and in the morning when I tried to wake it up it was giving a BSOD. During the day with short sleep times it behaved as expected. In the day it is on mains power but overnight it is switched off at the mains and left asleep on the battery - in the morning it boots from the battery or mains with the same result, so, I don't think the battery is bad?

    More recently, over the last week or two, it now takes ages to boot up sitting hanging with a plain black screen (approx 5 - 10 mins) and then decides to restart itself. Although I don't see a BSOD now in the event viewer I see the same critical errors relating to power but nothing that helps me identify the underlying cause.

    My problem has me completely bemused and confused.......I have spent hours googling and found numerous suggestions but nothing that has solved it yet. I have tried the usual sfc /scannow which showed nothing wrong, changed the internal battery, tinkered with the internal clock because I thought perhaps the system/hardware clocks were conflicting, various suggested sleep settings and more. To be honest I now feel that I have passed the limit of my knowledge and comfort zone and am probably in danger of doing more harm than good on my own!

    I have been trying for days to get an error log but whilst I thought I had it all set up correctly I still haven't got a Memory.dmp file and I'm not sure that I would know what it said anyway.

    I have a feature update to windows 10 version 1709 of 2.59gb that has failed to install at least 12 times for an unknown reason..........this may hold an update to my problem??

    I live rurally with limited broadband (only 40gb per mth) which means doing a restore and then downloading all the updates every time something goes wrong isn't really an option.

    I know I have a relatively old machine and some older drivers but it was working fine until early November. I suspect a dodgy driver but can't definitively identify the culprit - device manager says everything is ok, the windows troubleshooting utilities find nothing wrong, etc.

    My system restore points (15 Nov 2017 is earliest) possibly no longer go back to before the problem and I have used c10gb of data doing windows updates since so I am loathe to try without firm advice.

    I have considered a BIOS update but feel that I now need some professional direction as to what to do next.

    I have attached the zip file as requested and hope you can find something in their to guide me.

    I have also attached a driver view file. There are a load of Microsoft drivers that I don't understand that show as modified date of 2 Nov 2017 but created date of 21 Nov 2017 and wonder whether these are responsible?

    Many thanks

    BSOD & crashes overnight when returning from sleep? Attached Files
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       04 Dec 2017 #2

    Hi Kevin,

    Welcome to Tenforums :)

    There are no crash dump files to analyse (or records of them in the logfiles) so there is not a lot we can do to help at this stage. Make sure everything is set to record crash dump files according to the following tutorial. If the BSOD is happening during startup it is quite possible that the files never get written or the crash never gets recorded. In this case turning OFF automatic restart and taking a photo of the blue screen before manually restarting could help.

    Configure Windows 10 to Create Minidump on BSOD
      My ComputersSystem Spec

  3.    04 Dec 2017 #3

    Hi philc43 (!)
    Thanks for taking the time to reply. I have really struggled with getting dump files and as it only happens each morning on waking from sleep I have to wait a long time between each attempt!
    Anyway, I have now made a couple of corrections to my Minidump collection as per the link you posted, so, hopefully I'll get something useful next time it happens.
    The weird thing is this morning for the first time in 3 or 4 weeks my computer started up, albeit very slowly, without crashing .............I changed a couple of things yesterday including rolling back the Synaptics Driver which I could see had changed quite recently. So, maybe I found the problem "by accident"??
    I'll continue to monitor the situation and as long as I remember to I'll post back to say what happens.
    Thanks again for pointing me in the right direction - next time I'll know what to do.
      My ComputerSystem Spec

  4.    06 Dec 2017 #4

    Hi philc43

    After making a couple of corrections to my Minidump collection as per the link you posted I was hopeful that I'd get something useful from the next time it happened.

    Well after yesterdays success this morning I am back to having the same issue - a critical error but no dump file. I am pretty sure that the synaptics driver updated itself yesterday afternoon (after I tried to remove it entirely!) so I guess I'll roll it back again or try to disable it? It's just the laptop touchpad which I don't use as I prefer a mouse.

    Do you have any advice on how best to achieve this without it reinstalling?

    Can I also ask though - should I be getting dump files for a "critical error"................I don't actually see a BSOD anymore???
    I'll continue to monitor the situation and as long as I remember to I'll post back to say what happens.
    Thanks again for pointing me in the right direction.
    Last edited by Kenny2017; 06 Dec 2017 at 17:04. Reason: Didn't think my last post posted!!
      My ComputerSystem Spec

  5. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       06 Dec 2017 #5

    A critical error does not always trigger a BSOD. If you now do not see the blue screen then you will not be generating dump files :)
      My ComputersSystem Spec

  6.    17 Dec 2017 #6

    Fingers crossed this looks like my issue is finally sorted.

    I had to manually update to the Fall Creators Version 1709 as that particular update kept failing with no reason why. The Synaptics driver that I thought was causing the problem also updated itself and for the last three or four days everything has been playing nicely together although I have no doubt I will be back in the Forums when the next thing Windows 10 just like that for everyone!?!?!?

      My ComputerSystem Spec


Related Threads
I am getting the following error, any idea what could be the root cause: On Fri 1/6/2017 5:02:52 AM your computer crashed crash dump file: C:\WINDOWS\Minidump\010617-13140-01.dmp uptime: 21:52:13 This was probably caused by the following...
Hello. In my Toshiba Satellite I've recently noticed that my Windows Hello fingerprint authentication is disabled each time my laptop returns from sleep (it works fine during reboots or shutdowns and power on). If I want to use fingerprint...
not sure if this is something on nvidias end and they just havent fixed it yet, or if its something i can fix on my end. could you talk a look and help me out? please and thanks you!!!!!!!!!!!!
Hi all. I have a new Toshiba C55-C5241 Laptop, which came pre-loaded with Windows 10. (See Specs) I clean installed Windows 10 last weekend. All went very well. I just started loading programs this weekend. I started noticing the blue screen...
Hey guys, My Vostro is already in a bad condition but not physically. Some drivers do not work (e.g. webcam driver) properly. This Win10 is the fourth clean install on the PC (After 8 and 8.1), Windows Updates are enabled and installed...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:19.
Find Us