Printable View
A friend started having issues with their laptop today, error report as above - I said I'd throw it over to you guys as that exact 'crash caused by driver' code hasn't shown up on searching. The issue started with several freezes ie no mouse pointer but not a BSOD. They system-restored to a couple of days ago prior to the last couple of windows updates, restarted, and did experience BSOD shortly after. No obvious event to cause this as far as they know.
Thanks.
Not much to work with there, might be a TDR 116/117, maybe a utility driver/remnant AV driver. Check Reliability history: https://www.sysnative.com/forums/win...8-7-vista.html
0x117/117 troubleshooting steps: https://www.sysnative.com/forums/bso...116-0x117.html
Autoruns should enable you to check for odd/remnant drivers, get an autoruns.arn zipped and emailed to attach? https://technet.microsoft.com/en-us/.../bb963902.aspx
Or follow the BSOD steps to get dumps and other useful info: https://www.sysnative.com/forums/bso...8-7-vista.html
They had a look at reliability history but there is nothing to report although there was previously apparently (owing to System Restore)? Should they allow the system to crash in order to obtain current info? Have to say this is mostly above my (& their) head but will do my best to follow your advice, thanks.
Also they have followed your last link, generated the 2 zip files, but having gone on to run perfmon /report have encountered Error - system cannot find the path specified.
Will get them to bring the machine over later & look at your info with it in front of me.
The error code in first post they got from BlueScreenView, is there anything more helpful I can post from there?
Thanks a lot for your reply.
That's not enough to find the type of BSOD or the driver, I doubt that the Windows kernel was faulty, most likely *something else*, maybe on a different thread, was behind it.
See if you can replicate whatever they were doing, it might help figure out which subsystem was affected. If you can trigger a crash or two, that would be useful. Also ask about recent updates, Windows or 3rd party software.
Will do & report back. So assuming it crashes - run the synastive.com bsod dump app again? Is not being able to run perfmon /report going to hamper things?
Yes, just collect with the BSOD app., don't fret over Perfmon, I can rarely pick out anything useful from that :)
Sorry to not tie this up before; marking as resolved as problem failed to re-occur, so they have just been keeping an eye on things in the interim & rather than diagnose any further for diagnosing's sake will come back to it if necessary. Ta again.
No worries, odd BSOD occurrences can be almost impossible to replicate, Watchdog freezes (no BSOD) similar.
Even if there was a dump (singular) available for debugging, it would still be very difficult to pinpoint a cause.