Hi ! My system crashes randomly, last time when I was copying files from my remote computer using Explorer. It has happend before using different tools. Would be grateful if someone could help me! My dumpfile generated this message: rosoft (R) Windows Debugger Version 6.2.0013.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini110503-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 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530 Debug session time: Wed Nov 05 22:09:10 2003 System Uptime: 0 days 1:27:07.435 ********************************************************************* * 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 unloaded module list ......................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c000001d, b2f41c17, 80539144, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image netbt.sys, Win32 error 2 *** ERROR: Module load completed but symbols could not be loaded for netbt.sys Unable to load image tcpip.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys Unable to load image NDIS.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for NDIS.sys *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys Unable to load image psched.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for psched.sys *** ERROR: Module load completed but symbols could not be loaded for psched.sys Unable to load image RTL8139.SYS, Win32 error 2 *** WARNING: Unable to verify timestamp for RTL8139.SYS *** ERROR: Module load completed but symbols could not be loaded for RTL8139.SYS Probably caused by : Unknown_Image ( netbt+c17 ) Followup: MachineOwner --------- best regards, Peter

If you can boot up, fire up your xp disk in the cd rom go to start run type cmd at the prompt type in exactly with the space sfc /scannow If that does not do it then you will need to do a repair installation

This is an indication that you have severe corruption in the OS. There is a very good chance that the only cure will be a reinstall of the OS.

I did the "scannow" about an hour ago.(I saw it in another post from you Robbie), but it just did the check and then nothing happend. fredf: The thing is that I just reinstalled it.:) Its very annoying, I also got a "VPU" problem with my graphic card, which made my system to crash. Dont know if it has something to do with it. /Peter

It definitely could.. maybe the drivers are incompatible. What video card do you have and what drivers are you using? And did you install all of your chipset drivers from the motherboard?

I have a ATI Radeon 9800 Pro with the latest catalyst driver downloaded from ati.com. version: 6.14.10.6396, 2003-09-30 (wxp-w2k-catalyst-7-95-031028m-011774c.exe) And I did install all the drivers for mymotherboard that came along. I have a Soltek SL-86SPE with integrated audio chip AC'97.

I have got the exact same problem. The system crashes about five / ten times a day while running 24h. Most of the time when system is active (there are no problems when system is idle). I tried a lot of things: reinstall OS, different hardware changes (all the hardware except for mobo&processor&cooler), even installed W2000 (same problem) instead of XP. It seems to be a hardware problem to me. My guess would be a mobo-problem. I tried benchmarks and other tests: no results yet though.