Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Machine_check_exception (9c)


24 Jan 2011   #1

Windows 7 Professional x64
 
 
Machine_check_exception (9c)

I turned on my computer this morning. Opened a pdf I had created the night before, opened a firefox window. Then my mouse stopped moving. Within a couple seconds this changed to a BSoD.
I have an HP e9150t with an i7-950


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50
Debug session time: Mon Jan 24 08:50:35.614 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:49.660
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880009bac70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

4: 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
AMD64 Processors
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
Arguments:
Arg1: 0000000000000000
Arg2: fffff880009bac70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x9C_GenuineIntel

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff800035f86e0 to fffff8000307a740

STACK_TEXT:
fffff880`009bac38 fffff800`035f86e0 : 00000000`0000009c 00000000`00000000 fffff880`009bac70 00000000`00000000 : nt!KeBugCheckEx
fffff880`009bac40 fffff800`035f7e1f : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`009bad90 fffff800`035ebe88 : 00000000`d372b300 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`009badc0 fffff800`03078fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009badf0 fffff800`03078e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009baf30 fffff800`03088600 : 25300001`00000000 00000000`00000001 00000000`00000000 fffff781`00000004 : nt!KiMcheckAbort+0x153
fffff880`037e7860 fffff800`0308e770 : 00000000`00003743 00000000`00000001 00000000`00000002 00000000`00003719 : nt!KeFlushMultipleRangeTb+0x250
fffff880`037e7930 fffff800`030fca5e : fffff800`03206b40 fffff880`00000001 00000000`00000001 fffff880`037e7bb0 : nt!MiAgeWorkingSet+0x651
fffff880`037e7ae0 fffff800`0308eee2 : 00000000`0000037a 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`037e7b80 fffff800`0308f173 : 00000000`00000008 fffff880`037e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`037e7bd0 fffff800`0331ec06 : fffffa80`06a376a0 00000000`00000080 fffffa80`06a11890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`037e7d40 fffff800`03058c26 : fffff880`009b2180 fffffa80`06a376a0 fffff880`009bd0c0 5d5e99f6`d2c1e338 : nt!PspSystemThreadStartup+0x5a
fffff880`037e7d80 00000000`00000000 : fffff880`037e8000 fffff880`037e2000 fffff880`037e77e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxMcheckAbort+6c
fffff800`03078fec 488d8c2400010000 lea rcx,[rsp+100h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!KxMcheckAbort+6c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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


My System SpecsSystem Spec
.

24 Jan 2011   #2

Microsoft Window 7 Professional 32 bit
 
 

Hi Renko and welcome to SF!
Please follow the instruction below:
http://www.sevenforums.com/crashes-d...tructions.html

We are all happy to help you with your problem
Regard,

Tuan
My System SpecsSystem Spec
Reply

 Machine_check_exception (9c)




Thread Tools



Similar help and support threads for2: Machine_check_exception (9c)
Thread Forum
Solved BSOD - Machine_Check_Exception BSOD Help and Support
BSOD Machine_Check_Exception BSOD Help and Support
BSOD Machine_Check_Exception BSOD Help and Support
Machine_check_exception (9c) BSOD Help and Support
BSOD Machine_Check_Exception + Reboots BSOD Help and Support
Machine_Check_Exception - Stop 0x9c BSOD Help and Support
Machine_check_exception BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:48 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33