BSOD's occurring frequently, mostly error 0x00000124

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Home Premium 64bit
       #1

    BSOD's occurring frequently, mostly error 0x00000124


    Hey, I've been having serious problems with my computer over the past week. When running my computer, I get frequent crashes, black screens and BSOD's. These crashes occur randomly, but strangely enough when I'm not playing games. Usually when I exit the game a crash will occur shortly after and other times they occur when I'm simply browsing the internet or watching something. I unknowingly had AMD overdrive activated, so I turned that off and also re installed my GPU's drivers, which seemed to allow the computer to run for longer duration without a crash, blackscreen or BSOD, but the problem still persists.

    I've gathered a collection of minidump reports and the main culprits are ntoskrnl.exe and hal.dll, but I'm unsure why. I've attempted to to google the crash addresses, but have found no luck in solutions provided by other people. Right now my computer is only stable and free without crashes when in a max power save mode, using the EPU-4 Engine which came with my motherboard, so I'm getting pretty desperate on finding solutions.

    I've attached a .rar file containing my collection of minidump files and would appreciate any assistance anybody could provide me in clearing up my problems.

    Thanks in advance.

    System Specs:

    Windows 7 Home Premium 64bit
    AMD Phenom™ II x4 965 processer 3.40 GHz
    M4A79XTD EVO motherboard
    8GB RAM
    ATI 5850 Graphics card
      My Computer

  2.    #2

    Code:
    BugCheck 124, {0, fffffa80079cb8f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    Code:
    0: kd> !errrec fffffa80079cb8f8
    ===============================================================================
    Common Platform Error Record @ fffffa80079cb8f8
    -------------------------------------------------------------------------------
    Record Id     : 01cee484a17c1a23
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 11/18/2013 17:36:00 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80079cb978
    Section       @ fffffa80079cba50
    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         : 1
    CPU Version   : 0x0000000000100f42
    Processor ID  : 0x0000000000000002
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80079cb9c0
    Section       @ fffffa80079cbb10
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000002
    CPU Id        : 42 0f 10 00 00 08 04 02 - 09 20 80 00 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  @ fffffa80079cbb10
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80079cba08
    Section       @ fffffa80079cbb90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : [COLOR="Red"]DCACHEL1_DRD_ERR (Proc 2 Bank 0)
      Status      : 0xf669c00000000135
      Address     : 0x000000018b591450
      Misc.       : 0x0000000000000000
    With these kind of errors, the most important thing is to check the CPU mnemonics. The first field (TT) which is Transaction Type, indicates that the type of transaction was a Data type. The TT field is two bits.

    The next field is the (LL), Level Encoding or Memory Hierarchy indicates where the error took place, and in this case it was the Level 1 Cache. Again, this is also a two bit field.

    The last field of interest, is the (RRRR) request field which indicates the type of action desired. This is 4 bits long. This type simply shows a generic error.

    Code:
    0: kd> !prcb
    PRCB for Processor 0 at fffff780ffff0000:
    Current IRQL -- 0
    Threads--  Current fffffa8006ae2040 Next 0000000000000000 Idle fffff80003219cc0
    Processor Index 0 Number (0, 0) GroupSetMember 1
    Interrupt Count -- 00000942
    Times -- Dpc    00000007 Interrupt 00000000 
             Kernel 000001ed User      00000000
    Code:
    0: kd> dt nt!_KPRCB fffff780ffff0000
       +0x000 MxCsr            : 0x1f80
       +0x004 LegacyNumber     : 0 ''
       +0x005 ReservedMustBeZero : 0 ''
       +0x006 InterruptRequest : 0 ''
       +0x007 IdleHalt         : 0 ''
       +0x008 CurrentThread    : 0xfffffa80`06ae2040 _KTHREAD
       +0x010 NextThread       : (null) 
       +0x018 IdleThread       : 0xfffff800`03219cc0 _KTHREAD
       +0x020 NestingLevel     : 0 ''
       +0x021 PrcbPad00        : [3]  ""
       +0x024 Number           : 0
       +0x028 RspBase          : 0xfffff880`031b6db0
       +0x030 PrcbLock         : 0
       +0x038 PrcbPad01        : 0
       +0x040 ProcessorState   : _KPROCESSOR_STATE
       +0x5f0 CpuType          : 16 ''
       +0x5f1 CpuID            : 1 ''
       +0x5f2 CpuStep          : 0x402
       +0x5f2 CpuStepping      : 0x2 ''
       +0x5f3 CpuModel         : 0x4 ''
       +0x5f4 MHz              : 0xd48
    Code:
    0: kd> ? 0xd48
    Evaluate expression: 3400 = 00000000`00000d48
    You don't seem to be overclocking which is good.

    Run the Small FFT's, Large FFT's and Blend Test for a few hours each. Do not the temperature exceed 80*C.

    Enable "Round off checking" before the test (see first post below tutorial).
      My Computer


  3. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Thank you for your response.
    I'll run the stress tests very soon and post my results. Is there anything in particular I should be looking out for during these tests?

    Thanks again for your reply!
      My Computer

  4.    #4

    If the program crashes or BSODs when running, and also the log file of the program will be saved in the Prime95 program folder.
      My Computer


  5. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    I managed to run Prime95.exe for 2 hours and my CPU's temp ranged from 47-49. About a minute after stopping it my PC locked up/froze and required a reset (a frequent problem next to the BSOD's). I had to switch my PC into a power save mode for me to be able to use it again as it kept on crashing upon loading the desktop.

    The results seemed perfectly fine as I kept an eye on the test to monitor the temp, but no logs were saved because I had no prime95 folder (I extracted to desktop). Do you have any suggestions on what I should do from this point on?
      My Computer

  6.    #6

    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

       Information

    Check for any problematic drivers, they could be possibly writing bad data into the cache.
      My Computer


  7. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Hey, it's been a week since my last post and I'm at my wits end with the constant crashing! I attempted the driver verifier, but the majority of my crashes consist of freezes (sound stop, screen locks up etc) or black screening whilst the system is still on. Both require a hard reset before I can use my computer again, so I'm unable to force a bluescreen unless it randomly occurs.

    Since my last post, I've tried many different suggestions I read up on when researching my problem.

    I've tried memtest and tested for each stick of ram individually which discovered one error on pass 2, test 8 (tested the same piece 3 times and got the error each time) on my first stick. I removed the stick, but the crashes resumed (I've still not put it back in).

    I was told to up the voltage of my RAM to 1.64 from 1.60, but crashes still occurred. I've still not changed the voltage back to the original 1.60.

    Fresh installation of Windows 7 64 bit.

    The Fresh installation on top of the RAM voltage adjustment gave me a single crash then began to work as it had a few weeks ago and I was able to use it without problems for two days before the crashes began to frequently occur again.

    I've had a single BSOD on top of my other crashes and will upload the report. Using bluescreen viewer I noticed that it was the same drivers that were giving me problems before the fresh Windows installation. I was browsing the internet and watching videos using Youtube when the BSOD occured.

    I've been told that the crashes could be caused by my HDD, is that a possibility?
      My Computer

  8.    #8

    This Stop 0x124 seems to be more conclusive, it seems to have occurred as a result of a Data Read from the Level 1 Cache. It's also the same Processor Number and Memory Bank as before too.

    Code:
    2: kd> !errrec fffffa800673f028
    ===============================================================================
    Common Platform Error Record @ fffffa800673f028
    -------------------------------------------------------------------------------
    Record Id     : 01ceeab5196f4da5
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 11/27/2013 0:58:28 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800673f0a8
    Section       @ fffffa800673f180
    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         : 1
    CPU Version   : 0x0000000000100f42
    Processor ID  : 0x0000000000000002
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800673f0f0
    Section       @ fffffa800673f240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000002
    CPU Id        : 42 0f 10 00 00 08 04 02 - 09 20 80 00 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  @ fffffa800673f240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800673f138
    Section       @ fffffa800673f2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL1_DRD_ERR (Proc 2 Bank 0) <<< Error
      Status      : 0xb6004000d3000135
      Address     : 0x0000000155701990
      Misc.       : 0x0000000000000000
    Before, we conclude that the processor may be faulty, then I would suggest checking for any chipset updates, and have you checked for a BIOS update?

    Code:
    2: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=2442]
    BiosMajorRelease = 8
    BiosMinorRelease = 15
    BiosVendor = American Megatrends Inc.
    BiosVersion = 0704   
    BiosReleaseDate = 11/25/2009
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    SystemFamily = To Be Filled By O.E.M.
    SystemVersion = System Version
    SystemSKU = To Be Filled By O.E.M.
    BaseBoardManufacturer = ASUSTeK Computer INC.
    BaseBoardProduct = M4A79XTD EVO
    BaseBoardVersion = Rev X.0X
      My Computer


  9. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    I've never attempted to update my BIOS as it was out of my comfort zone, but searching for drivers today, I noticed there are many updates available for my motherboard. I'm not sure which updates I should go for as there are 10 alone in the BIOS category. Would I have to install each one individually or would the latest of the drivers include the previous fixes?
      My Computer


  10. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    Sorry for double post, but it wouldn't let me edit my previous one. Just wanted to upload another BSOD .dmp file as you said the last one showed more information. Hopefully this one will also assist.
      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 04:06.
Find Us