Tag Archives: bsod

BSOD 0x124 WHEA_UNCORRECTABLE_ERROR

So what is going to happen if you have installed everything, you are really happy about your setup and you think: “hey tomorrow i will even do a backup! Because it is really worth to preserve this!” Quite simple:

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

Loading Dump File [G:\Minidump52910-45333-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols;

Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82a0f000 PsLoadedModuleList = 0x82b57810
Debug session time: Sat May 29 08:13:07.914 2010 (UTC + 2:00)
System Uptime: 0 days 0:08:03.802
Loading Kernel Symbols
………………………………………………………
……………………………………………………….
……………………………………..
Loading User Symbols
Loading unloaded module list
……
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 00000000, Machine Check Exception
Arg2: 85d51024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6608000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
——————

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1f

STACK_TEXT:
82b32d2c 82e2df3f 00000124 00000000 85d51024 nt!KeBugCheckEx+0x1e
82b32d68 82addf04 85d425c9 85d51024 82a774d0 hal!HalBugCheckSystem+0xab
82b32d98 82e2e1f1 85d51ea8 82e3be40 00000000 nt!WheaReportHwError+0x230
82b32eac 82e2e2e3 85d51ea8 85d51ef8 00000000 hal!HalpMcaReportError+0x3b
82b32ed0 82e2e54f 00000000 85d51ef8 82b32ff0 hal!HalpMceHandler+0x8b
82b32ee0 82e245f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
82b32ff0 82e21261 0000001c 801df000 00000000 hal!HalpMcaExceptionHandler+0x87
82b32ff0 00000000 0000001c 801df000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
———

So what happened my ASROCK HDready MB with AMD 3800 X2 worked fine with Windows XP, but after some time i decided to upgrade to Windows 7 :). After doing the setup (more or less 10 hours of work, vpn – firewall – vmware – bla bla bla … ) windows 7 started to surprise with BSOD.

After contacting the Asrock support i got Bios 2.19 for testing, this even killed my XP, which was still working perfectly in parallel :). After downgrading back to 1.20 i was still facing BSOD (minidump analyse shown above).

So what was may solution:

– installing cpu-z info tool checking core voltage and memory timing

– increasing core voltage to 1.30 (from auto to 1.30v)

– correcting memory timings from (auto to given values from cpu-z info tool)

up to now i am happy again, no BSOD anymore. 🙂

*CROSSINGFINGERS*

bye. Continue reading

Advertisements
Posted in Setup | Tagged | Leave a comment