General discussion
April 22, 2005 at 01:49 PM
canderson

Computer reboot due to bugcheck

by canderson . Updated 21 years, 5 months ago

I have a computer that will randomly reboot, it is usually when the user is in word or excel. I have downloaded the Windows debugger program and pulled up a minidump log, but I don’t see anything that will help me figure out what is going on. I would really appreciate it if someone could help me out!! I don’t know anything about coding. Here is one of the minidumps. Thank you!!

Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Minidump\Mini041105-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Mon Apr 11 09:53:02.203 2005 (GMT-5)
System Uptime: not available
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Bugcheck code 00000BAD
Arguments fdaf2b60 81385c40 c0000005 b5b45514

ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
b5b45a94 00000bad fdaf2b60 81385c40 c0000005 0xb764ef82

WaitForEvent failed

This discussion is locked

All Comments