BSOD BCCode: 124

[Kuzan]

Here the problem


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800427A8F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1



Files that help describe the problem:
C:\Windows\Minidump\091912-17222-01.dmp
C:\Users\Redel\AppData\Local\Temp\WER-44943-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Attach here is the Dump file






Hoping for your reply

 

[Arc]

Hello Kuzan!

Stop 124 is totally a hardware crash. It may be any component of your hardware, and so it is to check various parts thoroughly.

The best way, I would suggest you, to follow the steps suggested by H2SO4:
http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696 .

Follow it, step by step. I hope you will be able to point out the problematic part of the hardware.

 

[Vir Gnarus]

Error details:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, [COLOR=Green]fffffa800427a8f8[/COLOR], 0, 0}

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
---------

1: kd> !errrec [COLOR=Green]fffffa800427a8f8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800427a8f8
-------------------------------------------------------------------------------
Record Id     : 01cd9638e619e4a4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/19/2012 7:32:23 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=Red]Error Type    : Cache error
Operation     : Data Read[/COLOR]
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : a7 06 02 00 00 08 10 00 - 9f e3 ba 0d 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  @ fffffa800427ab10

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

[COLOR=Red]Error         : DCACHEL2_DRD_ERR (Proc 0 Bank 5)[/COLOR]
  Status      : 0xee20000000041136
  Address     : 0x000000007b903e80
  Misc.       : 0x00000030e0000086

L2 Cache suffered an error when attempting to read data from it. From the article, you want to specifically go for updating drivers related to your Mobo, and that also includes your BIOS. The only additional thing I can mention outside of the article's scope is motherboard software. If you have software installed that came with your motherboard, uninstall them all. They are buggy messes that have been known to produce 0x124 bugchecks which can be very misleading to people. Driver Sweeper is a free app that's able to clean em off completely, so you may need to give that a go after you uninstall them through the usual manner. The only things left behind should be drivers specifically designed to make your motherboard components work. Any "enhancement", monitoring or other utilities or so-called drivers should be avoided.

For hardware tests related to this, Memtest for your memory (run overnight), and Prime95 for CPU. For Prime95, set to Torture Test at Blend first (run overnight), and then after that test do another on Large FFTs instead of Blend (again, run overnight). If it bugs out on Blend but not Large FFTs, it's most likely an issue with crosstalk between RAM and CPU. If it bugs out on Large FFTs and not Blend, it's an issue with the CPU's internal cache. If it bugs out on both, then it's most certainly the CPU that's failing.

 

[Kuzan]

Thank sir Vir Gnarus

Are those details mine ??extracted from my dump file??

Can i have the name of those test software

 

[Kuzan]

What would the driver Sweeper do?Would it uninstall all my driver or just search for leftovers error?

 

[Vir Gnarus]

The software I use is not 'test' software. It's a kernel debugger called Windbg, and is designed for professional use. It comes with the WDK (Windows Development Kit), and there's a number of tutorials on this website to get you started with it. I also have some articles here for a bit more advanced approaches, including dealing with 0x124 bugchecks like yours.

As for Driver Sweeper, it is designed to target drivers for certain hardware and remove them. You can select which drivers you want it to uninstall.

It's been two days now, have you managed to run any of the hardware tests?

 

[Kuzan]

I did not have much time recently cause i had a lot of project and A THESIS goin on..i plan to focus on it after this semester

Thank you for your answers

 

[Kuzan]

Sir Vir Gnarus goodday.about the test to be run to fix my problem can you suggest some..i have enough time now to do it now.

 

[Vir Gnarus]

Follow the instructions mentioned in my first post. They have links to the applications you'll want to run and specific instructions on how you should run them.

 

[Kuzan]

Is Memtest fine with a 64bits system?

 

[Vir Gnarus]

Yes, it is ok with either x86 or x64. It is updated frequently. The only compatibility issues you may have is if you have very old hardware and old type of RAM, which then you'll use the older Memtest for that. Yours, however, is new enough to use the newest Memtest86+