[SOLVED] BSOD 0x124 need help

D

Damke

Member
Joined
Jun 12, 2012
Posts
21
Location
Bosnia and Herzegovina
Hello,

I have a problem with a laptop Toshiba Satellite L500 1XZ (PSLJHE). Problem is BSOD 0x124 which happens frequently, even on a fresh installed Windows 7 OS.I changed hdd, memory, motherboard, and the problem is still there.This output is from freshly installed Windows 7 Ultimate x64, without installed drivers and OS updates.I installed just net framework 4 for debugging purposes (I wanted to install Win SDK but i didnt manage).Any help would be appreciated...
 

Attachments

Hello and welcome to Sysnative!

All dumps attached are of the x124 WHEA_UNCORRECTABLE_ERROR bugcheck. This bugcheck indicates that a fatal hardware error has occurred. This bugcheck uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

First off, if the CPU is overclocked, please return it to stock settings. If it's not, I'd go as far to say since you replaced everything but the CPU, that's your issue. That's not to say the CPU itself is the issue, but it could also be for example heat related, so be sure to check that you have a proper amount of TIM (thermal compound / thermal paste) and a good application method to ensure your temperatures, especially for the CPU, are at a comfortable level.

I would also at this point recommend updating if you have not already to the latest BIOS version.
 
It looks to me like the CPU is reporting an internal fault:
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, [COLOR="#FF0000"]fffffa8004de5028[/COLOR], b2000000, 175}

[B]Probably caused by : GenuineIntel[/B]

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

2: kd> !errrec [COLOR="#FF0000"]fffffa8004de5028[/COLOR]
===============================================================================
Common Platform Error Record @ [COLOR="#FF0000"]fffffa8004de5028[/COLOR]
-------------------------------------------------------------------------------
Record Id     : 01cd52b130e8e9c4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/25/2012 9:05:18 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR="#FF0000"]Cache error[/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000020652
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : 52 06 02 00 00 08 10 04 - 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  @ fffffa8004de5240

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

[B]Error         : DCACHEL1_EVICT_ERR (Proc 2 Bank 3)
  Status      : 0xb200000000000175[/B]

2: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 2  6,37,2 GenuineIntel 2128 0000000800000000                   21193ffe
                      Cached Update Signature 0000000c00000000
                     Initial Update Signature 0000000800000000
2: 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: 0000000000000000, Machine Check Exception
Arg2: [COLOR="#FF0000"]fffffa8004de5028[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SDKSetup.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6ba58 fffff800`02814a3b : 00000000`00000124 00000000`00000000 fffffa80`04de5028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`02f6ba60 fffff800`029d87d3 : 00000000`00000001 fffffa80`04de6ea0 00000000`00000000 fffffa80`04de6ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6baa0 fffff800`02814700 : 00000000`00000728 fffffa80`04de6ea0 fffff880`02f6be30 fffff880`02f6be00 : nt!WheaReportHwError+0x263
fffff880`02f6bb00 fffff800`02814052 : fffffa80`04de6ea0 fffff880`02f6be30 fffffa80`04de6ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6bc50 fffff800`02813f0d : 00000000`00000004 00000000`00000001 fffff880`02f6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6bc90 fffff800`02807e88 : 00000000`1b32a628 00000000`00000400 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f6bcc0 fffff800`028c9f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6bcf0 fffff800`028c9d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6be30 000007fe`f153b2a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`001ddc00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f153b2a5


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------
 
Thank You for quick replay.
CPU is not overclocked, and I apply thermal compound on it and also on gpu.Vents are clear.Temps are between 50 and 60 C.(Its now to hot in Bosnia :cool3:).On this new motherboard, bios version is 2.00 and there is newer 2.10, but on the old one the bios version was 2.10 and same things where happening.
Once again thank You for replay.
 
Thank You for quick replay.
I managed to install win sdk and I have same results.(when I tried to install win sdk I have BSOD during the installation of net framwork 4). So it will be worth to try another cpu.
Thanks again...:thumbsup2:
 
I will forward this to an expert. My conclusion is that this is CPU related (faulty CPU), but in order to provide best service, let's make sure of that.

Hang tight.
 
satrow and E-peen are correct, this is most likely a faulting CPU. All 4 crashdumps display a failure when attempting to evict (remove) data from L1 cache of your CPU. In all cases it's consistently bank 3 of this cache, which kinda leads me to believe we're dealing with a bad CPU and not just instability or temp problems from overclocking.

Just to let you know, stupid motherboard software has a tendency to cause these WHEA errors. If you have any software installed that came with your motherboard, you'll want to uninstall all of it, they're all buggy. Only leave drivers specifically for motherboard components (except USB and other external ports, those are buggy too). If you can confirm that they're uninstalled (sometimes they won't uninstall cleanly and you may need to use something like Driver Sweeper to take em off) and the problems still occur, then replace the CPU.
 
Last edited:
Thank You for replay.
As I wrote in post, this time I installed fresh copy of Windows 7 Ultimate x64, and wanted to install win sdk to troubleshoot this problem.So before installing any driver or motherboard software, I started installing net framework 4 which is required for win sdk, and Windows blue screaned.There are no drivers or any software installed, just trying to install required net framework.In last month bsod 124 happens more frequently and I can't use laptop anymore.BSOD happens even in safe mode when I want, for example, to uninstall driver.
 
No at this time.But before few days same on bsod was happening,(on another Windows installation) for example, when I attempt to install a graphic card driver, and during instalation of Windows update, and even in a safe mode, when I started Driver Sweeper.
 
Damke said:
Thank You for replay.
As I wrote in post, this time I installed fresh copy of Windows 7 Ultimate x64, and wanted to install win sdk to troubleshoot this problem.So before installing any driver or motherboard software, I started installing net framework 4 which is required for win sdk, and Windows blue screaned.There are no drivers or any software installed, just trying to install required net framework.In last month bsod 124 happens more frequently and I can't use laptop anymore.BSOD happens even in safe mode when I want, for example, to uninstall driver.
Click to expand...

Are there any dump files from these BSODs?

I think it's likely this will be the result -

Vir Gnarus said:
satrow and E-peen are correct, this is most likely a faulting CPU. All 4 crashdumps display a failure when attempting to evict (remove) data from lv1 cache of your CPU. In all cases it's consistently bank 3 of this cache, which kinda leads me to believe we're dealing with a bad CPU and not just instability or temp problems from overclocking.

Just to let you know, stupid motherboard software has a tendency to cause these WHEA errors. If you have any software installed that came with your motherboard, you'll want to uninstall all of it, they're all buggy. Only leave drivers specifically for motherboard components (except USB and other external ports, those are buggy too). If you can confirm that they're uninstalled (sometimes they won't uninstall cleanly and you may need to use something like Driver Sweeper to take em off) and the problems still occur, then replace the CPU.
Click to expand...

​
 
Dump files I uploaded was from latest installation of Windows (when I attempted to install net framework 4 on cleanly installed Windows, without any drivers or software).To have more info on this, laptop was in local Toshiba service, and tested with their low level testing software for more than 10 hours and passed!!!I will post a test as soon as possible...
 
I'm not familiar with that program for testing, and ~15 minutes to test for errors on all components like that seems sort of sketchy. Unless of course that's 15 HOURS and I am reading it wrong :P

Going off of the dumps we have seen earlier, and including the new provided information of the system BSOD'ing even in Safe Mode (MS signed drivers only) this definitely seems to be CPU related.

Regards,

E-Peen
 
I think that this error is one that is reported by the CPU itself, if that's correct, it's not something that can easily be worked around and if testing doesn't pick it up, it's because those tests are incapable of doing so.
 
I think that also.It so hard to work around this problem.Laptop was in toshiba service 3 or 4 times.Last time they replaced motherboard but problem was still there.They did a low level diagnostics and always passed.I'll be very happy if we are in right about faulty cpu.
Many thanks for all of You.
Best Regards
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top