Tweet
Oh, it may well be network-related...most BSODs are caused by corrupted files, followed closely by bad drivers or incorrect driver settings, and then applications - very few apps nowadays are able to actually cause a BSOD.
If you've saved a DMP file you will need Symbols to view them in a debugger, but that's not going to help you now. Download the Microsoft utility uptime.exe and run it on your PC with the /S switch... If you have a BSOD error, the Stop code will be viewable there.
In the Event Viewer look for a System entry: "The computer has rebooted from a bugcheck." It will also give you an idea of what is going wrong.
The fact that it is not logging the BSOD in the usual places is a little troubling; check this reg key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\CrashControl]
Value Name: LogEvent
Data Type: REG_DWORD (DWORD Value)
Value Data: 1 (enabled)
Exit your registry, you may need to restart or log out of Windows for the change to take effect.
If you've saved a DMP file you will need Symbols to view them in a debugger, but that's not going to help you now. Download the Microsoft utility uptime.exe and run it on your PC with the /S switch... If you have a BSOD error, the Stop code will be viewable there.
In the Event Viewer look for a System entry: "The computer has rebooted from a bugcheck." It will also give you an idea of what is going wrong.
The fact that it is not logging the BSOD in the usual places is a little troubling; check this reg key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\CrashControl]
Value Name: LogEvent
Data Type: REG_DWORD (DWORD Value)
Value Data: 1 (enabled)
Exit your registry, you may need to restart or log out of Windows for the change to take effect.
Comment