In the past few months, my Toshiba Satellite L675-S7048, began to reboot on its own. No BSOD at all. After looking at a few postings on the subject and looking at my machine, I determined that it was a kernel power event. I turned on logging, waited for another crash and have collected the log files from the Seven Forum Diagnostic Tool. Any help would be greatly appreciated.
medtner, have a look here, some information obtained from your crash dump .....
Description here: Driver Reference Table - SYMNETS.SYSCode:fffff880`0c16d678 fffff880`013b5a91Unable to load image \SystemRoot\System32\Drivers\N360x64\0502020.003\SYMNETS.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for SYMNETS.SYS *** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS SYMNETS+0x5ca91
And again ....
Description here: Driver Reference Table - SYMEVENT64x86.SYSCode:fffff880`0c16d508 fffff880`018b09b0Unable to load image \??\C:\windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS SYMEVENT64x86+0x269b0
And yet again .....
Description here : Driver Reference Table - BHDrvx64.sysCode:fffff880`0c16d4a8 fffff880`031dd2e0Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_5.0.0.125\Definitions\BASHDefs\20121130.005\BHDrvx64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for BHDrvx64.sys *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys BHDrvx64+0x1372e0
Still coming .....
Description here: Driver Reference Table - EraserUtilRebootDrv.sysCode:fffff880`0c16d168 fffff880`049c2ab8Unable to load image \??\C:\Program Files (x86)\Common Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for EraserUtilRebootDrv.sys *** ERROR: Module load completed but symbols could not be loaded for EraserUtilRebootDrv.sys EraserUtilRebootDrv+0x2ab8
If you follow the description links, you will see that all the crashing elements are belonging to Symentec. Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
Let us know the results.
Thanks very much for the quick response. Before I heard from you, I tried something a bit drastic (for me at least). I thought about it and realized that the fan had been a bit noisier than usual, so... I decided to open up the machine and see what the dust situation was like. Well... there was an enormous blob of compressed dust at the heat sink near the fan. Since removal, the machine has not crashed in the same way and it much quieter (though I now have an occasional blue screen of death on booting up; even after removing my virus program and replacing it).
Let us see the new crash dumps? If those crashes havent created a crash dump, upload your MSINFO32.nfo file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
Quote