Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 [FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views
     
syyang85
post Oct 11 2006, 01:59 AM

Enthusiast
*****
Senior Member
982 posts

Joined: May 2005
QUOTE
Microsoft ® Windows Debugger  Version 6.3.0017.0
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini101106-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.060411-1541
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805534a0
Debug session time: Wed Oct 11 01:21:10 2006
System Uptime: 0 days 0:51:52.218
Loading Kernel Symbols
................................................................................................................................
Loading unloaded module list
.........
Loading User Symbols
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {4, 805462f0, b2000000, 70f0f}

*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Probably caused by : hardware

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

kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
Arguments:
Arg1: 00000004
Arg2: 805462f0
Arg3: b2000000
Arg4: 00070f0f

Debugging Details:
------------------


BUGCHECK_STR:  0x9C_IA32_AuthenticAMD

MODULE_NAME:  hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

LAST_CONTROL_TRANSFER:  from 806d38d7 to 804f8c07

STACK_TEXT: 
805462c8 806d38d7 0000009c 00000004 805462f0 nt!KeBugCheckEx+0x1b
WARNING: Stack unwind information not available. Following frames may be wrong.
805463f4 806cec2e 80042000 00000000 00000000 hal+0x58d7
00000000 00000000 00000000 00000000 00000000 hal+0xc2e


FOLLOWUP_NAME:  MachineOwner

STACK_COMMAND:  kb

BUCKET_ID:  0x9C_IA32_AuthenticAMD

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



What is wrong?
syyang85
post Oct 12 2006, 12:07 AM

Enthusiast
*****
Senior Member
982 posts

Joined: May 2005
I took my hardisk and brought it to my frens house to copy some movies.
After that, i came back installed my harddisk back to my computer.
And i get an error x9c BSOD.

Then i took out the problematic harddisk and install it into my housemates computer. Amazingly, it can be read and there was no BSOD, but only the old files i previously had in my harddisk. The new files that had been copied cannot be read.

How do i solve this?
I'm using western digital 80gig HD

 

Change to:
| Lo-Fi Version
0.0588sec    0.33    7 queries    GZIP Disabled
Time is now: 2nd December 2025 - 12:03 AM