Windows 7 Random BSOD error code 0x0124

[Wooshna]

Hello,

I am having random BSOD's it happens at all times doesn't matter what i am doing or if i am doing anything i usually get atleast 1 a day. All my hardware is in my profile nothing is overclocked since its pointless if the system is not stable yet. I did purchase all parts and built it myself. Memtest showed no errors after 500% run on stock settings prime95 last more than 8 hours after that i stop testing. attached are all files that are necessary. View attachment 22811View attachment 22812View attachment 22813

 

[usasma]

The reports are incomplete. Please let the data collection app run for at least 15 minutes (or until it tells you that it's done).

While waiting for a reply, please try these free diagnostics: Hardware Diagnostics

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Wed Mar 20 17:56:39.495 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032013-16317-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:00:04.634[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa800d55c8f8, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800d55c8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar 19 19:49:42.635 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031913-16645-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:00:04.775[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa800d5828f8, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800d5828f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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.

[font=lucida console]**************************Wed Mar 20 17:56:39.495 2013 (UTC - 4:00)**************************
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
amd_sata.sys        Fri Mar  4 15:45:41 2011 (4D714F75)
amd_xata.sys        Fri Mar  4 15:45:44 2011 (4D714F78)
jraid.sys           Thu May 19 03:55:18 2011 (4DD4CCE6)
avgrkx64.sys        Thu Sep 13 20:41:40 2012 (50527D44)
avgloga.sys         Thu Sep 20 21:23:51 2012 (505BC1A7)
avgidsha.sys        Sun Oct 14 21:22:54 2012 (507B656E)
avgmfx64.sys        Thu Nov 15 17:03:50 2012 (50A566C6)
[/font]

http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=jraid.sys
http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=avgloga.sys
http://www.carrona.org/drivers/driver.php?id=avgidsha.sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys

 

[Wooshna]

sorry about that I did not realize that it was incomplete here is the complete scan. Did i need to update those drivers or get rid of them?

View attachment 22818

 

[usasma]

No need to do anything with the drivers. Just start with the hardware diagnostics (skip the one's that you've already run) and this....

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). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- 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
....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.
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
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
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.

Lot's of APPCRASH's in the WER section of MSINFO32. Most relate to Fuel.Service.exe - a component of your AMD video driviers. I also have to wonder if this is possibly related to a hardware problem with your video card. Please do this to remove all AMD stuff: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums If the BSOD's remain, be sure to run the different video tests at the hardware diagnostics link that I gave earlier ( Hardware Diagnostics )

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems. Please un-install it immediately!

 

[Wooshna]

Ok I have updated my jmicron controllers and my amd drivers. I also completely uninstalled my amd catalyst and did a fresh install. I do seem to notice that sometimes the catalyst control wants to open but then it just stops. Like if I right click my desktop and try to open ccc it will look like its trying to open then nothing happens. I tried updating my ssd but currently crucial is having issues with their updater recognizing uefi bios systems. Good news is that my system ran prime95 full blend for 18 hours and there was no bsod. Im going to stress my video card now to see if it Is the video card.

 

[BIGBEARJEDI]

Hi Wooshna: looks like things are improving on taming your BSOD problems. Was just curious as to why you made your boot C: drive the SSD drive and the 500GB platter drive showing up as you E: drive in your uploaded specs on this thread. I'm certainly not convinced that SSD technology is stable enough to use as a boot drive yet. If your BSOD's come back, you might consider swapping your 2 drives, and making your 500GB SATA platter drive the boot C: drive, and using the 150GB SSD2 drive as your secondary internal drive. I was wondering if you chose that SSD drive just for boot up speed or your reasoning there. Personally, I would choose stability and reliability in a boot drive versus performance/speed. I've had multiple issues with SSD drives, especially in netbooks that give me cause for making that statement--random drive failures etc.

Best of luck with the new system!

BIGBEARJEDI

 

[Wooshna]

View attachment 23030View attachment 23031View attachment 23032

Thanks bigbearjedi after stressing my card with furmark for 4 hours there was no bsod but now my bsods have come back. I am usually doing nothing on the pc just watching videos or surfing the web and i would get a bsod. I have a new list of them here but now i am thinking of just switching my operating system to my 500g hard drive and just use the ssd for other programs. If you could please take a look at the new set of bsods and see if something else is causing the issue.

Update: I updated my ssd to the latest firmware now its 070h and seems to be pretty stable. no bsod for today so after saturday i'll start stressing my system on sunday to see if it was an ssd issue.