BSOD BCCode: 124

Page 1 of 2 12 LastLast

  1. Posts : 14
    Windows 7 proffesional 32 bit
       #1

    BSOD BCCode: 124


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


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    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:
    Stop 0x124 - what it means and what to try .

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


  3. Posts : 1,314
    Windows 7 64-bit
       #3

    Error details:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800427a8f8, 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 fffffa800427a8f8
    ===============================================================================
    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
    Error Type    : Cache error
    Operation     : Data Read
    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
    
    Error         : DCACHEL2_DRD_ERR (Proc 0 Bank 5)
      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.
      My Computer


  4. Posts : 14
    Windows 7 proffesional 32 bit
    Thread Starter
       #4

    Thank sir Vir Gnarus

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

    Can i have the name of those test software
      My Computer


  5. Posts : 14
    Windows 7 proffesional 32 bit
    Thread Starter
       #5

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


  6. Posts : 1,314
    Windows 7 64-bit
       #6

    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?
      My Computer


  7. Posts : 14
    Windows 7 proffesional 32 bit
    Thread Starter
       #7

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


  8. Posts : 14
    Windows 7 proffesional 32 bit
    Thread Starter
       #8

    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.
      My Computer


  9. Posts : 1,314
    Windows 7 64-bit
       #9

    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.
      My Computer


  10. Posts : 14
    Windows 7 proffesional 32 bit
    Thread Starter
       #10

    Is Memtest fine with a 64bits system?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 21:05.
Find Us