Bsod error code bc124 help please

orico99

Honorable
Sep 4, 2013
5
0
10,510
Random Blue screens- over last few weeks i am getting, seemingly at random strange shutdowns, doesnt matter what im doing, can just be surfing, games or on apps.
But screen freezes, goes black and shuts down and restarts, sometimes doesnt do it for a couple of days, sometimes does it more, happened 3 times last night then was good rest of evening, just done it now while playing wordament on windows apps.
I have ran memtest/scanned disks/virus scanned/ set everyting back to default and still does it, all drivers up to date as far as i know, temps running fine, cpu about 40-50 under testing, just cannot seem to solve it.
this is what i get from whocrashed on the latest one, but they are all the same


On Wed 04/09/2013 17:59:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090413-23353-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x52EBC9)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8009A778F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

and from windows dbg


ADDITIONAL_DEBUG_TEXT:


FAULTING_MODULE: fffff803bf881000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031a8530 fffffa80`09b0a000 : 00000000`00000000 fffffa80`09a778f8 00000000`0000000a fffffa80`09a778f8 : nt+0x52ebc9
fffff880`031a8538 00000000`00000000 : fffffa80`09a778f8 00000000`0000000a fffffa80`09a778f8 00000000`00000000 : 0xfffffa80`09b0a000


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

BUCKET_ID: WRONG_SYMBOLS

anyone any ideas at all as it has got my head scratching??

 
It appears to be a hardware issue, possibly your graphics card.

Hardware troubleshooting:
0. Ensure CPU/Memory at default settings (not overclocked)
1. Swap video card (or try your video card in a different PC if possible)
2. Swap RAM (I know Memtest passed. This is a last resort as Memtest is good but not 100%.)

Software Troubleshooting:
1. If you have a SPARE DRIVE, unhook all other drives and install Windows, drivers etc to it to see if crashing still exists...

2. Load earlier RESTORE POINT (System Restore).

Summary:
There's a few things it could be, both software and hardware. My first guess is the video card and the EASIEST test there is to run it in a different system (with adequate Power Supply). Since the other system is known to be working, if the card has no issues then the card is fine and it's something ELSE.

If the card fails on the new system, initiate RMA with the manufacturer for a replacement.
 

orico99

Honorable
Sep 4, 2013
5
0
10,510
I dont have another system to test on, could i run from onboard graphics, would that give me an idea?

have got cpu at standard, it has turbo core on it-its an fx-6300, but i have tried with that disabled and enabled and still get crashes
the drive i could do if needed but i would have to borrow one, ive got a partitioned 2tb drive at mo
I have been leaning to gfx card and gonna see about another next week, got a gtx560ti currently which is about 3yrs old
 

orico99

Honorable
Sep 4, 2013
5
0
10,510
it was overclocked, have set back to default and turned turbo mode off and still does it,memtest ran through night and day, no errors.
just trying a driver clean and reinstall on some stuff at moment to see if it affects ought
 


Did you make any changes within a week prior to the failure?
GPU overclock does seem to point in the direction of the graphics card being the issue.

Can you test with just onboard iGPU?
Not sure what that would prove. I guess if your system didn't crash it would suggest the graphics card was defective, though it could also be a driver issue with that card. Too bad you can't borrow another system.

Really the best thing is to do a CLEAN INSTALL if you have a spare drive. If you do NOT have a spare drive, make sure you backup your data etc.
*If you DO reinstall Windows do NOT ACTIVATE unless you are sure that you will stay with that. There's a limited number of re-activations (not sure what they are, or if Microsoft actually enforce it.)

It's really hard to troubleshoot hardware without SPARE PARTS.
 

orico99

Honorable
Sep 4, 2013
5
0
10,510
I know, ive got odds and sods about but its from an old agp computer with ide drives, so fairly useless, havent made any changes, i bought the cpu about 6 months ago, and been fine, only installed games over last few weeks, run cccleaner every week and virus scans, this is just something weird thats happened over last couple of weeks, i am looking to upgrade the card anyway to a 760 next month so i can check that bit then.
Ive ran the stress test on msi afterburner and not crashed, this has really got me puzzled..
Strangely its mainly happened when just surfing or on desktop, or a few times on metro interface and apps , when playing games i think its done it once maybe twice tops, as they are more intense i would have thought would cause it to happen more.
Only thing i can even possibly think happened is i was playing arkham city a few weeks ago, and it crashed to desktop and wouldnt start, said was a gfx issue, had to reinstall game as it wouldnt start again, clutching at straws probably but cant think of anything else thats happened, keep looking at reliability monitor for clues lol
 

orico99

Honorable
Sep 4, 2013
5
0
10,510
LOoking through my reliability report, as mentioned i had batman game crash on me a bit back, it come up as fatal video hardware error, could that have caused problems to start?