Hi i keep getting this BSOD MACHINE_CHECK_EXCEPTION (0x9C).When I look in the event viewer the error is sytem error, category (102, event 1003. I have also looked at the mindump and it comes up with: Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini071806-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 <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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Tue Jul 18 13:12:10.015 2006 (GMT+1) System Uptime: 0 days 1:33:56.613 ********************************************************************* * 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 ............ *** 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, 80545ff0, b2000000, 70f0f} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner Please someone help me
You could very well have a bad RAM chip. Event 1003 is usually related to RAM. If you have multiple chips, only use one and try to boot. If the problem is gone, then shutdown and add another one. Keep going until you have isolated a bad stick. If all the sticks do the same thing, then we'll start to look elsewhere. Make sure you test all the sticks independantly first. If they all have the same result, there is a bigger issue. ~Rich Edit: Here is a link. http://support.microsoft.com/?kbid=329284&sd=RMVP
