New
#1
BSOD & crashes overnight when returning from sleep?
HI
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
Kevin
Quote