Hey, I was forced to reformat ny system just yesterday because of this same issue....it seemed to go away untill it just happened agian an hour os so ago......Just out of the blue my pc us force restarted by a blue error screen The is the techinical information from windows error report C:\DOCUME~1\Owner\LOCALS~1\Temp\WEReb6b.dir00\Mini100104-02.dmp C:\DOCUME~1\Owner\LOCALS~1\Temp\WEReb6b.dir00\sysdata.xml Dose anyone have any odea what might be causeing this

Damn....i think i figured it out....i bet it's the new nortons i installed

try reseating the ram, take one stick out to try finding faulty one

Ok...nortons wasent the problem.....i restored this pc to befor i installed nortons and it jus crashed agian.....any ideas why?

Ok...i took my oldest stick out.....well try thsi and see what happens....thanks for the reply.

You must diagnostic your problem logically. The Blue screen has a lot of useful diagnostic information. Such as the bugcheck code and its parameter list. Usually 80% of blue screen is related to software. 10% related to virus and 10% is related to hardware. You never mention what is the bugcheck code that you encounter. Check the system event log and look for record id 1001 (ie sysdump). Zoom in and copy the content of the sysdump event record. Base upon the bugcheck code, you can look up the explanation and suggestion from Mircosoft WebSite. If your PC encounter bugcheck code 0A, 1E, 40, 8E or D1 which is usually software error at one of the device driver. If you still know the problem, download the windbg from mircosoft and process the minidump ( ie Mini100104-02.dmp) Hope it can help you Albert

This is what i got from Mini100104-02.dmp is says probably cause by ntoskrnl.exe Microsoft (R) Windows Debugger Version 6.3.0017.0 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini100104-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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20 Debug session time: Fri Oct 01 22:36:31 2004 System Uptime: 0 days 0:00:18.626 ********************************************************************* * 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, {c0000005, 8054b909, ba81f82c, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ntoskrnl.exe ( nt+74909 ) Followup: MachineOwner ---------