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: Random BSOD 0x0124

10 Mar 2014   #1
pmoradi2002

Windows 7 x64
 
 
Random BSOD 0x0124

I recently purchased a new Lenovo Y510P, however upon turning it on it bluescreened within minutes with WHEA_UNCORRECTABLE_ERROR

The bluescreen always happens at random, sometimes when I'm transferring files or on YT watching a video

Per Lenovo, I reinstalled 8.1 via recovery however I still faced the same issue

Went ahead and installed Windows 7 and now I get the 0x0124 code.

I have ran memtest with no issues, I'd prefer not to send it in for service as I'd be out of a laptop for 2 weeks


My System SpecsSystem Spec
.
11 Mar 2014   #2
peebee

Windows 7 x64
 
 

Here's what happened.

Code:
 
===============================================================================
Common Platform Error Record @ fffffa800f185028 <-- WHEA record
-------------------------------------------------------------------------------
Record Id     : 01cf3bf2de6d6f46
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/10/2014 0:13:47 (UTC)
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f1850a8
Section       @ fffffa800f185180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f1850f0
Section       @ fffffa800f185240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb da 7f 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
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_XPF_PROCESSOR_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
Proc. Info 0  @ fffffa800f185240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f185138
Section       @ fffffa800f1852c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
Error         : ICACHEL2_IRD_ERR (Proc 2 Bank 8) <-- Whoops... crashed in cache
  Status      : 0xbe00000000081152
  Address     : 0x000000040f4e4940
  Misc.       : 0x000000302202c086
Your processor (or motherboard BIOS) isn't treating you kindly. I would update your BIOS first and see if that helps. If you're overclocking your system, stop. Overclocking is one of the most common reasons for cache errors (you're pushing the CPU too hard).

If you're not overclocking and a BIOS update doesn't fix the problem then you've likely got a bad CPU and should RMA it (or the entire machine).
My System SpecsSystem Spec
Reply

 Random BSOD 0x0124




Thread Tools




Similar help and support threads
Thread Forum
Random BSOD error 0x0124
Hello, for quite some time I have problem of almost random BSOD crashes. They usually happen while I watch online videos, play games or simply browse internet, but it happens while idle too. I checked cpu and gpu for temperature and other errors, RAM for errors, I think I run some HDD test also,...
BSOD Help and Support
Random 0x0124 BSOD when gaming or watching youtube/twitch
I get random 0x00124 bsod when gaming or watching youtube/twitch. This started after I upgraded to windows 10 (I also bought a new GPU, but had no issue for a month before I started getting theses BSOD), but I tried downgrading to windows 7 to no avail (fresh install). If anyone has any clue on...
BSOD Help and Support
Recent random BSOD with 0x0124 and hal.dll
Hello, I have been getting the same BSOD with 0x124 and hal.dll but it doesn't seem to be triggered by anything specific like playing video games or having multiple programs up and running. For example today I was just watching a streamer on twitch.tv and had 2 or 3 taps open and I got it. I...
BSOD Help and Support
0x0124 BSOD
I got a random bsod last month and today. I used a bsod tool to check .dmp and it seems like both of them were caused by the same thing. The first bsod was the one last month. It occured a little time after I installed an SSD and put two identical seagate 2tb harddrives into raid 1. One of the...
BSOD Help and Support
BSOD 0x0124
Hi. Lately I have been trying to solve this BSOD problem, but after some research on google, I saw that it could be many things. Changed my power supply, changed the sockets my memory sticks were and cleaned the PC but the problem still persisted. The BSOD 0x0124 ALWAYS happens while I'm playing...
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 09:15.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App