Windows 7 Please help BSOD BCCODE 124

jamiehend · Jan 8, 2013

Hi all I'm new to the forum and wanted to know if anyone could help me with this BSOD. I am nearly in tears!

It has been happening for a few months now and its doing my head in. It happens when under load be it playing games or running handbrake. Ran tourture test with prime95 twice and it happend between 15 mins to an hour in. Very rarely it will occur in idle.

Have run memtest86 through 10 passes with no errors. System is not overclocked. idle temp of around 30C and full load of about 60C. Stripped the machine out and cleaned then reassembled. All driver up to date as is bios. Have done clean install of windows a while ago with no change!

Confused and angry!

Heres my system specs:
Windows 7 x64 ultimate service pack 1
AMD Phenom II X4 965 Black edition
Arctic Cooling Freezer 7 Pro rev 2
Asus M4A87TD/USB3
2x4GB G-Skill Ripjaws DDR3 1600Mhz
Sapphire HD 6870 1GB
Corsair 120GB Force 3 SSD (OS and Programs)
Samsung 1TB HDD (storage)
Samsung SH-B123L Optical Drive
3x 120mm Case fans
700W PSU. Can't remember the PSU make and model will pull it out if this info will help.

Attached is all the info from CPU-Z, RAMMon and W7F Tool. Only 3 miniDumps in there has I Ran CCleaner the otherday and it cleaned them!

I appreciate the time taken to read and look at this and hope that someone can help.

Thanks
Jamiehend

usasma · Jan 9, 2013

Prime95 errors are suggestive of RAM, CPU Cache, or memory controller issues. You can pass Memtest and still get errors in Prime95 from your RAM (2 different tests)

60ºC is a bit warm for a CPU - but not excessively so if it's truly under full load (and it's only 60 - not 61/62/63 etc)
It's way too warm for a mobo, RAM or HDD. It's a bit cool for a GPU - which I generally let get into the 70's before becoming concerned.

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

It is unusual to have these drivers present in a system as updated as yours:
amdsata.sys Wed Oct 7 16:13:09 2009 (4ACCF655)
amdxata.sys Wed Oct 7 16:13:10 2009 (4ACCF656)

I'd suggest updating your chipset drivers from the AMD website - Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

There are drivers from Avast and AVG on your system. Please un-install the AVG. If you uninstalled it after a previous BSOD, don't worry about it.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

000.fcl Fri Sep 26 09:11:22 2008 (48DCDF7A)
CyberLink FCL Driver
http://www.carrona.org/drivers/driver.php?id=000.fcl

AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)
ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)
http://www.carrona.org/drivers/driver.php?id=AtiPcie.sys

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys

nusb3xhc.sys Thu Dec 9 23:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys

nusb3hub.sys Thu Dec 9 23:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys

Must be removed:
AODDriver2.sys Thu Apr 5 05:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys

If you still have BSOD's after all of the above, please run these free hardware diagnostics: Hardware Diagnostics

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Tue Jan  8 10:23:37.051 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010813-12027-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:50:51.190[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa8007cd9028, f6002000, ed000136}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007cd9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6002000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000ed000136, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME: [B]prime95.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  7 17:43:44.347 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010713-12168-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:25:18.487[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa8007cf6028, b6002000, ed000136}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007cf6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6002000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000ed000136, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME: [B]prime95.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  7 10:30:51.363 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010713-11902-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:52:05.909[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa8007d23028, f6002000, ed000136}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007d23028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6002000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000ed000136, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME: [B]HandBrakeCLI.e[/B]
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[FONT=lucida console]**************************Tue Jan  8 10:23:37.051 2013 (UTC - 5:00)**************************
[COLOR=RED][B]000.fcl                     Fri Sep 26 09:11:22 2008 (48DCDF7A)[/B][/COLOR]
[COLOR=RED][B]AtiPcie.sys                 Tue May  5 11:00:22 2009 (4A005486)[/B][/COLOR]
[COLOR=RED][B]AsUpIO.sys                  Sun Jul  5 22:21:38 2009 (4A515FB2)[/B][/COLOR]
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
CLBUDF.SYS                  Wed Oct  7 02:42:23 2009 (4ACC384F)
CLBStor.sys                 Wed Oct  7 02:42:27 2009 (4ACC3853)
amdsata.sys                 Wed Oct  7 16:13:09 2009 (4ACCF655)
amdxata.sys                 Wed Oct  7 16:13:10 2009 (4ACCF656)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
rikvm_9EC60124.sys          Tue Oct  5 21:27:35 2010 (4CABD087)
[COLOR=RED][B]nusb3xhc.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)[/B][/COLOR]
[COLOR=RED][B]nusb3hub.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)[/B][/COLOR]
ElbyCDIO.sys                Thu Dec 16 17:58:13 2010 (4D0A9985)
VClone.sys                  Sat Jan 15 11:21:04 2011 (4D31C970)
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
Rt64win7.sys                Thu Jul 14 02:18:47 2011 (4E1E8A47)
[COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
RtHDMIVX.sys                Tue Jun  5 01:45:14 2012 (4FCD9CEA)
point64.sys                 Tue Sep 18 06:18:08 2012 (50584A60)
atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
aswrdr2.sys                 Mon Oct  8 04:23:43 2012 (50728D8F)
viahduaa.sys                Mon Oct 22 04:11:15 2012 (5084FFA3)
aswFsBlk.SYS                Tue Oct 30 18:43:04 2012 (509057F8)
aswMonFlt.sys               Tue Oct 30 18:43:09 2012 (509057FD)
aswTdi.SYS                  Tue Oct 30 18:43:16 2012 (50905804)
aswSP.SYS                   Tue Oct 30 18:44:06 2012 (50905836)
aswSnx.SYS                  Tue Oct 30 18:44:08 2012 (50905838)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  7 10:30:51.363 2013 (UTC - 5:00)**************************
avgtpx64.sys                Tue Aug 21 10:16:24 2012 (50339838)
[/FONT]

jamiehend · Jan 9, 2013

Hi first off thankyou very much for the response and advice massively appreciated.

Before I got your reply I moved my machine and ran prime95 again still Blue screened on me after about an hour but load temps maxed out at 50C so was obviously not getting enough airflow.

I then slowed ram to 1066Mhz and ran prime95 again this ran for 6 hours with no blue screen or errors, looking promising.

I stopped prime to read your response, I have gone through updated SSD firmware, updated all drivers I could find, removed all graphics bits and just installed driver, removed AAODdriver AOODriver 4.01 and AODDriver2 as suggested.

As I said from inital test this morning all is looking good, will run another test tomorrow morn and hopefully system will remain stable. Will let you know after.

Again thankyou for the help

jamiehend

Vir Gnarus · Jan 10, 2013

Just to append info along with Usasma's post to fellow analysts:

Analysts:

All crashdumps same WHEA error:

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, [COLOR=#008000]fffffa8007d23028[/COLOR], f6002000, ed000136}

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

0: kd> [COLOR=#0000cd]!errrec[/COLOR] [COLOR=#008000]fffffa8007d23028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8007d23028
-------------------------------------------------------------------------------
Record Id     : 01cdeccb8de74449
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/7/2013 15:30:51 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007d230a8
Section       @ fffffa8007d23180
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   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 00 00 00 00 00 00 - 00 00 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  @ fffffa8007d23240

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

Error         : [COLOR=#ff0000]DCACHEL2_DRD_ERR[/COLOR] (Proc 0 Bank 0)
  Status      : 0xf6002000ed000136
  Address     : 0x000000010b4aca80
  Misc.       : 0x0000000000000000

As Usasma pointed out, the AOD driver can be very well responsible for this, regardless of the fact it's a WHEA error. Otherwise, if removing AOD does not fix it, then this most likely is an internal CPU failure. Error message states CPU's L2 data cache suffered a generic error when performing a read on said cache. This is same on all crashes, and the same bank is reported as well as the CPU core responsible for the request.

Windows 7 Please help BSOD BCCODE 124

jamiehend

New Member

Attachments

usasma

Fantastic Member

jamiehend

New Member

Vir Gnarus

Active Member

Similar threads