Help understanding minidump........

[maverick777]

My computer is rebooting every now and then for no reason. Here is the minidump file in full. I can't seem to figure out what is causing the reboots even after looking through the minidumps.

Thanks in advance for the help.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini040607-02.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 <symbol_path> 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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Apr 6 13:57:24.843 2007 (GMT-5)
System Uptime: 0 days 12:55:33.544
*********************************************************************
* 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 <symbol_path> 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
Loading Kernel Symbols
............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000006, bf8be449, a0ea6b68, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for dump_WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for dump_WMILIB.SYS
Probably caused by : dump_WMILIB.SYS ( dump_WMILIB+d00 )

Followup: MachineOwner
---------

 

[dot_Zen]

Good luck, when you find someone to explain to you the debugging tools, and not just read them to you. Or even point you to understandable and to the point reference material regrading minidump files; I'll pay them.

 

[plasma]

What about that 2nd to last line "Probably caused by : dump_WMILIB.SYS ( dump_WMILIB+d00 )" ?

I googled WMILIB.SYS and it looks like a winbond sound card driver. Have you tried reinstalling the sound card drivers?

 

[maverick777]

Thanks for the help. I re-installed my built-in sound drivers and disabled the device since I'm using my x-fi card. That fixed the problem. At least I think it did since the BSOD's haven't come back. I'll cross my fingers

But who knows, it is windows afterall....