TechSpot

Win XP reboots at Random

By LiqLight
Mar 28, 2007
  1. Just installed a clean PC. New Hardware and a new Win XP installation.
    But my PC keeps restarting at random.

    This is my minidumpfile


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini032807-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) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Mar 28 19:38:51.578 2007 (GMT+2)
    System Uptime: 0 days 0:03:05.265
    *********************************************************************
    * 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
    ........................
    Unable to load image SYMEVENT.SYS, Win32 error 2
    *** WARNING: Unable to verify timestamp for SYMEVENT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 804eff5b, 981dc940, 0}

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

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

    Probably caused by : SYMEVENT.SYS ( SYMEVENT+b388 )

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

    1: kd> analyze -v
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *** WARNING: Unable to verify timestamp for kmixer.sys
    *** ERROR: Module load completed but symbols could not be loaded for kmixer.sys
    *** WARNING: Unable to verify timestamp for naveng.sys
    *** ERROR: Module load completed but symbols could not be loaded for naveng.sys
    *** WARNING: Unable to verify timestamp for navex15.sys
    *** ERROR: Module load completed but symbols could not be loaded for navex15.sys
    *** WARNING: Unable to verify timestamp for HTTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for HTTP.sys
    *** WARNING: Unable to verify timestamp for EraserUtilDrvI1.sys
    *** ERROR: Module load completed but symbols could not be loaded for EraserUtilDrvI1.sys
    *** WARNING: Unable to verify timestamp for srv.sys
    *** ERROR: Module load completed but symbols could not be loaded for srv.sys

    etc.
     

    Attached Files:

  2. chamillitarysk8

    chamillitarysk8 TS Booster Posts: 128

    if windows is brand new non pirated then it shouldnt do that form that i say that it looks like windows is corrupted so run checkdisk and see what it says but if you just installed windows it might be your harddrive thats damaged
     
  3. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    You've got one bit memory corruption. Test your memory with Memtest.

    BugCheck 1000008E, {c0000005, 804eff5b, 981dc940, 0}
    Probably caused by : memory_corruption

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    804eff55 - nt!IoSetThreadHardErrorMode+b
    1 error : !nt (804eff55)

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
     
  4. LiqLight

    LiqLight TS Rookie Topic Starter

    although the reply's seem verry helpfull i still have the same situation.

    Memtest and dskchk found no failure. Still my system keeps restarting...
     
  5. chamillitarysk8

    chamillitarysk8 TS Booster Posts: 128

    well i suggest you reinstall windows if the programs reported no problems
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...