BSOD showing 0x00000124 error code

Hi guys,

I have been getting this error message recently. The computer would automatically restart after showing the BSOD. I am new to debugging anf don't know much details of debugging etc. Your help is required plz.

Basic system info:

Sony Vaio VPCCW2PFX/R
OS: Windows 7 Home Premium x64 SP1 (Reinstalled in Jan 2012)
Make: OEM installed Windows (Genuine registered copy)
System (hardware) is almost 2 years old

I have also attached the dump files.

Please let me know if any clarification is required.

Regards ... Irfan

Majority of your crashes are 0x124 bugchecks, yes. These are caused by WHEA (Windows Hardware Error Architecture) triggering due to a hardware fault. If you wanna know how to interpret them, you'll need to grab Debugging Tools for Windows (aka WinDBG, from the Windows WDK) and then run the !errrec command followed by the memory address mentioned in the second argument for the bugcheck. The 4 numbers after the crash error code (0x124) are the 4 arguments. Doing that will bring all the results from the WHEA error structure telling you details on what went wrong. Example below:

Code:

...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80058a6028, be000000, 800400}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : GenuineIntel

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

0: kd> !errrec fffffa80058a6028
===============================================================================
Common Platform Error Record @ fffffa80058a6028
-------------------------------------------------------------------------------
Record Id     : 01cd1754552d5b65
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/10/2012 20:01:49 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80058a60a8
Section       @ fffffa80058a6180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x0000000000020652
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80058a60f0
Section       @ fffffa80058a6240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 52 06 02 00 00 08 10 00 - bd e3 98 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80058a6240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80058a6138
Section       @ fffffa80058a62c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 5)
  Status      : 0xbe00000000800400
  Address     : 0x000007fef6d51519
  Misc.       : 0x0000000000000000

Every 0x124 crash I've found from you are the same issue. An internal CPU timer failed. While almost every time it's during Processor 0 (that's the first - and primary - CPU core) activity, every time it's also using the same CPU cache bank (Bank 5). Very consistent behavior.

Before we start blaming the CPU on this, first you should go to the Sony website and download and update both your BIOS and any and all drivers for your motherboard. Typically they show up as chipset or CPU drivers. If none of that fixes the problem, then we will have to believe that the CPU has failed and you will have to replace the laptop or get it serviced if it's still under warranty.