• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Win XP crash every day

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

BlitzPuppet

Member
Joined
Feb 8, 2006
Location
Texas
I have windows xp home edition with all the updates and SP2 and such, rest of my machine info is in my sig here is the Dump file:


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


Loading Dump File [e:\123.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: symbolpath
Executable search path is: imagepath
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 Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Dec 18 10:53:58.468 2006 (GMT-6)
System Uptime: 0 days 12:57:28.164
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
..................................................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {4, 8054d5f0, b2000000, 70f0f}

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

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

Probably caused by : ntoskrnl.exe ( nt+22d1b )

Followup: MachineOwner
 
STOP 0x09C is a machine check exception, a hardware-level exception raised when something is grossly wrong with, well, your hardware. I have found it to be a warning of impending, massive hardware failure, although that's just my experience.

If you are overclocked, drop to stock and see if the problem persists. This includes memory or other system components.

Download and run a memory tester program (memtest86 can be found here) to verify as best as is possible the integrity of your system RAM.

If you changed anything, change it back.

HTH, good luck.
 
Back