Question:
What does this bluescreen mean?
2012-03-07 00:00:39 UTC
I have been getting this same bluescreen for 5 years. At one point it became so frequent I removed the Ram and put it back in. Then I reinstalled the entire operating system. The computer worked fine and then the bluescreens were back. They became more and more frequent until the computer could no longer start. At that point I removed 2 out of the 4 RAM in the computer. It worked fine with no bluescreens. After two days the blue screens are back with three of them so far. This is getting so annoying I cant stand it. Surfed the internet for answers and nothing. I am concluding the problem is hardware. What component is failing based on this information? ....



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


Loading Dump File [C:\Users\Chris\Desktop\New Folder\Mini103111-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Machine Name:
Kernel base = 0xfffff800`01c48000 PsLoadedModuleList = 0xfffff800`01e0cdd0
Debug session time: Mon Oct 31 15:28:37.318 2011 (UTC - 5:00)
System Uptime: 5 days 9:36:40.113
Loading Kernel Symbols

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005a11030, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000010, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010c0f, Low order 32-bits of the MCi_STATUS value.

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff800`02f03c18 fffff800`01c098ba : 00000000`00000124 00000000`00000000 fffffa80`05a11030 00000000`b2000010 : nt!KeBugCheckEx
fffff800`02f03c20 fffff800`01d68f53 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x12e
fffff800`02f03c90 fffff800`01c091bc : fffff800`00000c3e fffff800`02f03e70 fffff800`02f03ef0 00000000`00000000 : nt!WheaReportHwError+0x243
fffff800`02f03cf0 fffff800`01ca16f1 : 00000000`00000000 fffff800`02f03ef0 fffff800`01dbef00 00000000`00000000 : hal!HalpMcaExceptionHandler+0x114
fffff800`02f03d30 fffff800`01ca1535 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x71
fffff800`02f03e70 fffffa60`02212062 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
fffff800`02ef7cd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdk8!C1Halt+0x2


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN

BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN

Followup: MachineOwner
---------
Three answers:
Shiva
2012-03-10 06:12:11 UTC
its processor prob me too had this prob solved it by changing the processor hope urs is in warranty
exy
2016-10-15 14:58:01 UTC
that's reported as the "blue exhibit of dying", having experienced this i stumbled on it became extra like the "blue exhibit of restore". Our pc guru fastened it in the present day and without dropping counsel it became a sort of Trojan virus. This became over a three hundred and sixty 5 days in the past and we've had no issues considering that.
allmightypuffn
2012-03-09 06:08:50 UTC
all that info is crap. u need to lookup the number at the top of the screen that looks simular to this:

0000x00000000000000164



right under that will be the specifc fault

page irq less then or equal to



or something simular to that.


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...