BSOD stop code 124 after replacing HHD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by acasualgamer, Sep 10, 2013.

  1. acasualgamer

    acasualgamer New Member

    Joined:
    Sep 10, 2013
    Messages:
    2
    Likes Received:
    0
    I recently bought and installed a new HDD in my desktop. The HDD is a Western Digital 1TB Caviar Blue 64MB 7200RPM drive. After installing this new HDD and reformatting my computer I am continuously running into a BSOD. I myself am not extremely tech savvy, my computer knowledge is limited to about just putting together the parts required to build a desktop.

    I have attached my dump files and any help would be greatly appreciated.
     

    Attached Files:

  2. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    I'm conflicted. The crashes are almost all saying that an issue occurred with an attempt to read an instruction in the CPU's L1 cache. As in the CPU has a problem. However it just seems so coincidental that this has all just started happening when you installed a hard drive, which I would assume the drive is as fault just because the only thing that changed in the environment is the HDD.

    Are you using this new HDD as a replacement for an older system drive you used to run Windows on? Also, have you made any other changes at all during the installation of this hard drive?

    Btw, if you have your system overclocked in any way whatsoever, please reset to factory defaults. In fact, go into your BIOS and make sure that your BIOS is set to safe default settings, not normal (if safe options are available). Also, ensure that all your fans in your system are running properly, and that your CPU isn't getting overheated. Perhaps you may have dislodged a cable somewhere or something or a fan is getting stuck and preventing the CPU from cooling down. Make sure to check your system cooling.

    Overall, I'm inclined by the data to have to believe we have CPU failure of some sort, notably either voltage issues, overheating issues, or some other related CPU failure. The motherboard and power supply can also be suspect here, but because this is an internal CPU failure code, I'm leaning more on the CPU itself.

    Analysts:

    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80055af028, b0800000, 40151}
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    6: kd> !errrec fffffa80055af028
    ===============================================================================
    Common Platform Error Record @ fffffa80055af028
    -------------------------------------------------------------------------------
    Record Id  : 01ceae7229172ae9
    Severity  : Fatal (1)
    Length  : 928
    Creator  : Microsoft
    Notify Type  : Machine Check Exception
    Timestamp  : 9/10/2013 22:09:46 (UTC)
    Flags  : 0x00000000
    
    ===============================================================================
    Section 0  : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor  @ fffffa80055af0a8
    Section  @ fffffa80055af180
    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  : 1
    CPU Version  : 0x0000000000600f20
    Processor ID  : 0x0000000000000006
    
    ===============================================================================
    Section 1  : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor  @ fffffa80055af0f0
    Section  @ fffffa80055af240
    Offset  : 536
    Length  : 128
    Flags  : 0x00000000
    Severity  : Fatal
    
    Local APIC Id : 0x0000000000000006
    CPU Id  : 20 0f 60 00 00 08 08 06 - 0b 32 98 36 ff fb 8b 17
      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  @ fffffa80055af240
    
    ===============================================================================
    Section 2  : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor  @ fffffa80055af138
    Section  @ fffffa80055af2c0
    Offset  : 664
    Length  : 264
    Flags  : 0x00000000
    Severity  : Fatal
    
    Error  : ICACHEL1_IRD_ERR (Proc 6 Bank 1)
      Status  : 0xb080000000040151
    
     
  3. acasualgamer

    acasualgamer New Member

    Joined:
    Sep 10, 2013
    Messages:
    2
    Likes Received:
    0
    Hey thanks for the reply man, I followed the advice you gave me with regards to double checking the cables. Afterwards I also re-seated all the components to make sure nothing was loose. I then reset the BIOS to default (as I was unable to find a safe mode). With regards to the fans and heat that shouldn't be the problem because according to the BIOS the CPU averages about 43 degrees Celsius.

    Thankfully i was able to solve this issue over the weekend. After doing all those steps I was really hoping it wasn't the CPU but I began to despair.

    What fixed it was that since I have basically confirmed that it wasn't a hardware problem (unless it's the CPU) I decided to check to see maybe if it was a software problem since I had to re-install all the drivers and whatnot after changing the HDD.

    I created a disc image of my previous HDD with Paragon Backup & Security 2013 and then used it to "restore" my new HDD. That seemed to have done the trick as I haven't experienced a BSOD stop 124 error in the past 2 days.

    Thanks for reading up on my post and helping out! Really appreciate the effort =D
     
  4. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    We'll see how this goes for now. I do know that on rare cases software installed for motherboards have bugs inherent in them that can trigger odd WHEA bugchecks like what you were experiencing. That's why I usually recommend to anyone that any software that came with their motherboard should be uninstalled and avoided. Only device drivers designed to get parts of the mobo working should be installed. I've also seen that certain Windows updates will fix issues like these because of fixes on bugs in their kernel and HAL code. Perhaps your new Windows installation lacked the update it needed to fix this.

    In any case, glad to hear it's ok so far.
     

Share This Page

Loading...