[jdq]

I'd sure appreciate any help on this - I have been having issues with my system for the past several weeks - my computer will randomly restart. The screen will go blank, the tower will give a "click" and then the system will restart. I found another issue saying to check out the event viewer (never done that) and I ran across this:

"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x82ee3ac8, 0x82ee3ad8, 0x1a020001). A dump was saved in: C:\WINDOWS\Minidump\Mini033105-02.dmp."

I don't really know what this means or refers to - anyone got any ideas?

[Advertisements]

The autoreboot is normal - it's a response to some fatal error encountered by your system. The only time I've ever had an autoreboot to occur is due to hardware or memory problems. You can turn the autoreboot off, but I think at this point it will just BSOD whenever the problem occurs. I am not sure how to turn off the autoreboot without hacking the registry. About the problem causing the error - can you post the dump file, or is it too large?

[Kathryn]

The autoreboot is normal - it's a response to some fatal error encountered by your system. The only time I've ever had an autoreboot to occur is due to hardware or memory problems. You can turn the autoreboot off, but I think at this point it will just BSOD whenever the problem occurs. I am not sure how to turn off the autoreboot without hacking the registry. About the problem causing the error - can you post the dump file, or is it too large?

[jdq]

Not sure how to post the dump file - don't know how to access it.

[Kathryn]

It's the path that you posted earlier. That's where your minidump files are stored.

C:\WINDOWS\Minidump\Mini033105-02.dmp

[jdq]

I was viewing this information from computer management - event viewer - I can locate the dmp file, but cannot open it to read its contents. Can't seem to figure it out . . .

[jdq]

anyone have any idea how I can post this dump file? I'm still having issues, and would appreciate any help I can get. Thanks.

[Kathryn]

I use WinDBG to view my .dmp files. You can download the debugger from http://www.microsoft...installx86.mspx

[jdq]

This looks to be the information from the latest dmp file - not sure what to make of it:



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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Tue Apr 5 17:41:10.650 2005 (GMT-4)
System Uptime: 0 days 0:33:58.217

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 unloaded module list
.................................
Loading User Symbols
Unable to load image usbuhci.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for usbuhci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbuhci.sys

* Bugcheck Analysis *

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {3, 2, 0, f89710a2}

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

Unable to load image USBPORT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
Probably caused by : usbuhci.sys ( usbuhci+30a2 )

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

[Kathryn]

You need to install the symbols package to view it. I'll find it for you. Just out of curiosity - what have you been doing when it restarts? Did you install new memory around the time it started?

The symbols pack you can download from http://www.microsoft.../symbolpkg.mspx

[jdq]

well - I'm trying to add the symbols to the debugger - can't seem to set the system path - I thought I installed the symbols, but apparently I need to set the debugger to find the symbols - what all I've read about this seems rather foreign to me - so, any thoughts??

when the system restarts it is often when I try to open a new program, or to browse files - all of the icons will come up as generic placeholders and then they will refresh and appear as the specific programs. sometimes the screen will now just start flashing on and off at a regular interval of about 5-10 seconds and will keep flashing. sometimes the machine will just cut off and restart. i've unchecked the auto-restart option like other posts have suggested, but I get no bluescreen or error messages. now that I've installed the debugger, when the machine restarts i get some new notification saying "unable to load notes"??

I can't remember what all i've installed since this has started happening. i've recently added a liteon dvd burner to my system, and program called FreeRam XP pro, but the system will still restart even if I've exited the freeram program. I'd like to analyze the dmp file, but i'm just having trouble getting to the info.

again, any help would be appreciated.

thanks

[Kathryn]

This is a lot more detail - I will look up more information about this problem too - as far as the symbols go, you need to tell it where the symbols directory is. To do this:

1) Open WinDBG
2) Goto File --> Symbol File Path
3) Type in the path to your symbols directory whereever you installed them to. My symbols path is c:\windows\symbols to give you an idea.
4) If it prompts you to save workspace, go ahead and click yes
5) Select File --> Open crash dump and select the minidump file.

This should run the information you need. Lately I've been having problems with my debugger getting past the symbol files for the Symantec Firewall client. The last time this happened to me, it was because my ram was not installed correctly. If it's happening when you're opening programs at random, I wouldn't be surprised if it's a memory issue.

[jdq]

I've been away for a week - just came back - still hoping to try and fix this - I've directed the symbol path, but I think this post means it is still having some problem. Any thoughts??


kd> .restart

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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Apr 6 17:40:24.341 2005 (GMT-4)
System Uptime: 0 days 1:15:07.902
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
................................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
Unable to load image usbuhci.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for usbuhci.sys
Unable to load image USBPORT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {3, 10, 0, f8959fcd}

Unable to load image savrt.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for savrt.sys
*** ERROR: Module load completed but symbols could not be loaded for savrt.sys
Probably caused by : usbuhci.sys ( usbuhci!UhciInterruptService+a7 )

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

kd> .restart

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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Apr 6 17:40:24.341 2005 (GMT-4)
System Uptime: 0 days 1:15:07.902
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
................................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
Unable to load image usbuhci.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for usbuhci.sys
Unable to load image USBPORT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {3, 10, 0, f8959fcd}

Unable to load image savrt.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for savrt.sys
*** ERROR: Module load completed but symbols could not be loaded for savrt.sys
Probably caused by : usbuhci.sys ( usbuhci!UhciInterruptService+a7 )

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

[jdq]

I've checked the connections inside the case, and all seems to be in order. I'm discovering that my computer will begin flashing on and off even more frequently. I tried to play a CD and it will begin to flash and the program will need to close. When I open image files, sometimes the computer will have the same problem - if I open multiple programs, I will seem to "overload" the system. I'm wondering if it is a memory issue, but I don't know how to test it - I used a memory test program, and all seemed to pass through without any difficulties. Could this be Bios settings? Or Power Supply related? I'm not sure - thanks for the insights.

[riteshgautam]

hi,
DO u still have the same prob? .Also can u mail me the dump file so i can analysis it and tell u the exact cause.
pls send me the *.dmp file normally located in the %SystemRoot%\Minidump folder at [email protected]