BSOD's occurring frequently, mostly error 0x00000124

[Crayo]

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

 

[x BlueRobot]

[COLOR="Red"]BugCheck 124[/COLOR], {[COLOR="Blue"]0[/COLOR], [COLOR="SeaGreen"]fffffa80079cb8f8[/COLOR], 0, 0}

Probably caused by : AuthenticAMD

0: kd> [COLOR="SeaGreen"]!errrec fffffa80079cb8f8[/COLOR]
===============================================================================
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    : [COLOR="Red"]Cache error[/COLOR]
Operation     : [COLOR="Red"]Data Read[/COLOR]
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      : [COLOR="Red"]Fatal[/COLOR]

Error         : [COLOR="Red"][COLOR="Red"]D[/COLOR]CACHE[COLOR="Blue"]L1[/COLOR]_DRD_[COLOR="SeaGreen"]ERR[/COLOR] (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.

0: kd> [COLOR="SeaGreen"]!prcb[/COLOR]
PRCB for Processor 0 at [COLOR="Red"]fffff780ffff0000[/COLOR]:
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

0: kd> [COLOR="SeaGreen"]dt nt!_KPRCB fffff780ffff0000[/COLOR]
   +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              : [COLOR="Red"]0xd48[/COLOR]

0: kd>[COLOR="SeaGreen"] ? 0xd48[/COLOR]
Evaluate expression: [COLOR="Red"]3400[/COLOR] = 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.

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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

 

[Crayo]

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!

 

[x BlueRobot]

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

 

[Crayo]

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?

 

[x BlueRobot]

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:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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

 

[Crayo]

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?

 

[x BlueRobot]

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.

2: kd> [COLOR="SeaGreen"]!errrec fffffa800673f028[/COLOR]
===============================================================================
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         : [COLOR="Red"]DCACHEL1_DRD_ERR (Proc 2 Bank 0)[/COLOR] <<< 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?

2: kd> [COLOR="SeaGreen"]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=2442]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 0704   
BiosReleaseDate = [COLOR="Red"]11/25/2009[/COLOR]
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 = [COLOR="Red"]M4A79XTD EVO[/COLOR]
BaseBoardVersion = Rev X.0X

 

[Crayo]

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?

 

[Crayo]

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.

 

[x BlueRobot]

The latest driver update will contain all the previous fixes.

 

[x BlueRobot]

[COLOR=Red]BugCheck D1[/COLOR], {0, b, 8, 0}

Probably caused by : [COLOR=Red]atikmdag.sys[/COLOR] ( atikmdag+f2ec7 )

2: kd> [COLOR=SeaGreen]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`04800000 fffff880`05134000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Wed Apr 20 02:53:29 2011[/COLOR] (4DAE3C99)
    CheckSum:         008E91DD
    ImageSize:        00934000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update to the latest WHQL AMD graphics card driver, it seems to have used a NULL instruction pointer.

http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

 

[Crayo]

I've updated both my BIOS and AMD driver as you requested and I'm still unfortunately having the crashes.
I've had a single bluescreen since then as the rest are complete freezes (screen locks up requires hard reset, screen goes black as if PC has been turned off despite system remaining on requiring hard reset). I'll upload the bluescreen that occurred yesterday.

Two of the crashes today forced the sound in my headset to crackle whenever sound from anything was heard and forced all the applications I had opened to not respond and close themselves. Not sure if this is to do with the new changes I've made with the driver and BIOS updates.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 4E[/COLOR], {[COLOR="Blue"]99[/COLOR], 0, 0, 0}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiBadShareCount+4c )

This bugcheck is caused by a corrupt PFN or PTE, as a result of a Bad Share Count, the Share Count is the number of PTEs which point to a physical page, Working Set Trimming will typically reduce the Share Count, as well as, the freeing of virtual memory.

2: kd> [COLOR="SeaGreen"]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`033fb1d8 fffff800`02d1847c nt!KeBugCheckEx
01 fffff880`033fb1e0 fffff800`02cfa49b nt!MiBadShareCount+0x4c
02 fffff880`033fb220 fffff800`02d002a1 nt! ?? ::FNODOBFM::`string'+0x31b67
03 fffff880`033fb2a0 fffff800`02cc946e nt! ?? ::FNODOBFM::`string'+0x3806d
04 fffff880`033fbb30 fffff800`02c87ad3 nt!NtFreeVirtualMemory+0x2de
05 fffff880`033fbc20 00000000`770af89a nt!KiSystemServiceCopyEnd+0x13
06 00000000`02dee118 00000000`00000000 0x770af89a

I would run Driver Verifier again, and also test the RAM for any possible issues too:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Crayo]

Hey, I've ran the memtests once again, this time until 10 passes. The results turned out to be the same as my original test with the fourth piece proving faulty. I decided to terminate the test for the fourth piece during pass 5 when it was clear it was the piece of RAM and not the slots which showed 0 errors for the other 3 pieces.

I've tried to boot up the PC using a known working piece of ram in a tested slot, but I received the same freezes that have been bothering me for the past 3 weeks. I've yet to attempt driver verifier again because I don't occasionally receive blue screens and rather just hard locks or the screen shutting down with the computer remaining on. I'll be sure to attempt to use it sometime this week and try to run it for 24 hours to see if any problems are shown to me.

I just wanted to ask what are the chances of the HDD causing such freezes? I failed to mention before that I suffered from these problems with this PC 2 years ago and a technician told me it was a problem with my harddrive. I'm not sure what he did to fix the problem 2 years ago, but I've tried to reformat, delete etc without any luck. This is the same HDD I had when those problems occurred last time.

EDIT: 11/12/2013

After constant crashes I encountered three BSOD's over the past 2 days. Hopefully these will reveal more information about my problems like the previous one.

 

[Crayo]

I apologise for again double posting, but it's been a week since I received my last bit of advice for my problem. Are there any other recommended procedures for me to figure out my problem?

Thanks.