TechSpot

Random Restart/Long loading/Blue Screen

By kniteshift
Nov 6, 2006
  1. A load of problems.

    1) There are rolling random restarts. I tried to do the chkdsk and it even restarted for that during 97% of stage four, and the second time I attempted it restarted at 67% of stage four. Sometimes when I'm trying to use I.E., or just listening to music.

    2) If I shutdown my laptop, and then attempt to turn it on there will be a long blank screen maybe 5-10 minutes before BIOS will load up, and etc., My computer lights are on, DVD ROM and everything else does not respond, I just wait it out. My current BIOS are up to date, and etc.,

    3) Ugly blue screens, mentions win32k.sys. Not sure.

    Code:
    Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\WINDOWS\Minidump\Mini110606-08.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 = 0x8055a420
    Debug session time: Mon Nov  6 13:56:48.640 2006 (GMT-8)
    System Uptime: 0 days 0:04:12.190
    *********************************************************************
    * 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 win32k.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, bf830a10, f7083484, 0}
    
    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    Probably caused by : hardware ( win32k+30a10 )
    
    Followup: MachineOwner
    ---------
    So I'm not sure if i'm doing the minidump right, I've never done it before. So any help will be useful, thanks in advance.

    - Alan
     
  2. xxdanielxx

    xxdanielxx TS Rookie Posts: 1,069

    can u upload tha file it looks like u dont have a sysmbol loaded
     
  3. kniteshift

    kniteshift TS Rookie Topic Starter

    ^
    okay, here it is.
     

    Attached Files:

  4. xxdanielxx

    xxdanielxx TS Rookie Posts: 1,069

    your computer crashed due to hardware issues it says COMMON_SYSTEM_FAULT if you get a few more upload them and ill try to help u is there anything that u upgraded

    open your winDbg and under file open symbol path then in there put this

    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

    this will put add symbol.

    The bugcheck show an IP_MISALIGNED. Informations from here states that a IP_MISALIGNED is a crash that happens when CPU’s instruction pointer fails to point to the beginning of a valid instruction. Instead, it points into the middle of an instruction. This is believed to be a hardware problem, possibly caused by over-clocking, over-heating, or power supply problem.
     
  5. kniteshift

    kniteshift TS Rookie Topic Starter

    what can i do about all this?
     
  6. xxdanielxx

    xxdanielxx TS Rookie Posts: 1,069

    up load more minidumps
     
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...