Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: X64_0x124 possible fix

19 Jul 2013   #1

Windows 7 65 bit
X64_0x124 possible fix

Hello every one, i signed up and i feel like posting this could help some one out there who are going insane trying to fix their bsod or random reboots caused by the FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

I'm not sure if this is the right section to post this i hope it is if not forgive me.

*My short story on my problem*
Since may 22 i have been having super random blue screens of death some times i didn't get any blue screens it was a quick freeze reboot. Of course i asked people on the web.

I ended up buying a new PSU , New motherboard, tested ram with memtest86 still no fix. My GTX 560 SE seemed fine? of course i tested it it didn't give me issues gaming it wasn't over heating. So i took my GTX 560 SE out swapped for a low end card a EVGA GT 430 my computer has been on since 1:30 pm 7/18/2013 it is now 8:08 AM 7 /19/2013 and my pc has not froze or reboot.

That being said "just because you're GPU isn't acting funny or is having the symptoms of most failing cards. really it had 0 problems gaming I have already RMA my EVGA GTX 560 SE back to see if it is in fact the card at the moment it's looking like i was right.

Here's the list of things i tried before i tried the GPU.

1. Swapped out my corsair 500 watt for a brand new xfx pro 550 watt.
2. Swapped mother boards with the same board but a brand new one, didn't fix the issue so i put the old one back in.
3. Tested 8 gigs worth of ram using memtest86 and other memory tools.
4.Prime95 everything checked out fine.
5. Clean install of windows 7, manual download on all gpu/bio updates ect.
6.Heavens bench mark test, despite my card running it fine and having no issues makes it weird that the card was the issue. So just be aware it can be you're card even if it is running fine. Try to swap out for a lower end card that you know will work.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\071713-15334-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03092e50
Debug session time: Wed Jul 17 18:45:51.660 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:08.626
Loading Kernel Symbols
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80079d18f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner

2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80079d18f8, 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.

Debugging Details:

BUGCHECK_STR:  0x124_AuthenticAMD





fffff880`02fc46f0 fffff800`0310fa89 : fffffa80`079d18d0 fffffa80`06a38680 00000000`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc4c10 fffff800`02ff1547 : fffffa80`079d18d0 fffff800`0306a5f8 fffffa80`06a38680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc4c40 fffff800`02f59b95 : fffff800`030cc360 fffffa80`07982828 fffffa80`07982820 fffffa80`06a38680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc4c80 fffff800`02ed4161 : fffff880`00dd9e00 fffff800`02f59b70 fffffa80`06a38680 fffffa80`06a38680 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc4cb0 fffff800`0316a166 : 00000560`00000000 fffffa80`06a38680 00000000`00000080 fffffa80`069abb30 : nt!ExpWorkerThread+0x111
fffff880`02fc4d40 fffff800`02ea5486 : fffff880`02d64180 fffffa80`06a38680 fffff880`02d6efc0 00000560`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc4d80 00000000`00000000 : fffff880`02fc5000 fffff880`02fbf000 fffff880`035b93b0 00000000`00000000 : nt!KiStartSystemThread+0x16


FOLLOWUP_NAME:  MachineOwner






Followup: MachineOwner
This isn't a 100% fix and you're issue maybe something els.
Now i'm not saying it's your GPU doing this for sure to anyone who is having this issue. But keep in mind i told everyone oh my card works fine! it runs games no problems no heat issues ect turns out it must have been the card, in the end all i had left to test was Hard Drive, CPU.

I hope this post will be helpful to some one who used google for days weeks trying to find a fix or possible causes. I wish i would have swapped out my GPU before spending all that money on a new psu and mother board. I guess it was the fact it seemed it was working fine but i guess it wasn't! i didn't have to post this but i really feel that it could help some one out if their in the same boat i was in.

"*also take note, this was my problem i understand this code can mean anything failing, but this is just a heads up to people who think just cause their GPU is running games fine or isn't over heating the card still uses RAM and in my case also it provided me with audio.*"

*Edit Update" 7/19/2013 1:04 PM*
My pc is still running, it's been over 24 hours now. No BSOD, No Freezing, No random reboots. Everything is going smooth. I think i can confirm that it was the Graphic Card even though i have not got the test results back yet. I will reboot my pc once at 6:00 pm and let it run over night once more use it as i normally do to make sure 100% so far it's looking good.

My System SpecsSystem Spec
20 Jul 2013   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

A stop 0x124 is generally a hardware error; but the overall computing environment have the bearing on it.

Not only the GPU but the RAM, CPU, PSU and the USB/PCI/PCIe PnP devices, but also the motherboard may cause this bugcheck. It is also found that heat, dust accumulation within the computer, dried thermal compound, not-properly-seated devices and cards, and even a missing service pack may cause this particular bugcheck.

If you need more info, see the following threads ....
If any help is needed at any point of time, let us know :)
My System SpecsSystem Spec

 X64_0x124 possible fix

Thread Tools

Our Sites

Site Links

About Us

Find 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 14:51.
Twitter Facebook Google+