is my amd fx 6300 going out? getting bsods, bbccode 124

Toggle sidebar Toggle sidebar
V

visualcmos

Reputable
Jan 9, 2016
6
0
4,510
So I have a little custom build that is a cpl years old, specs are:
CPU: AMD FX(tm)-6300 (Vishera) six-core (3515.87 MHz) Turbo 4.1
Memory: 8175 MB (single)
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Graphics Card: EVGA GeForce GTX 650 Ti BOOST/PCIe/SSE2
MB: ASUS M5A78L -M LX PLUS

So lately while playing one of my games (H1z1) I have started getting bsod's after about 30-40 minutes of playing. I have checked temps and haven't noticed any overheating. When I scim through the minidump's I mostly notice bbcode 124 and I think their pointing towards my cpu. Any insight or help would highly be appreciated. I'm not really sure how to pinpoint the problem or try trouble shooting it, I've ran sfc/scan now and had a couple errors but fixed and ran it a few more times with no more errors. Also I have ran memtest with no errors, prime95 with no error, and I also haven't gotten the bsod or any other crashes playing any other games, like gta 5, crossfire, witcher 3, or nba2k15. Just in h1z1. What's the best way to post my last minidump on here? Oh also there is no overclock all stock. Also I have tried turning off the turbo core with amd overdrive and it still bsod'd, same code.
 
Solution
O
Have you tried replacing the thermal paste (If it's not under warranty) or getting the manufacturer to do so? Also, try keeping the GPU fan at 100 and using headphones. Make sure it's 100 % and not 100 degrees.
Sort by date Sort by votes
V

visualcmos

Reputable
Jan 9, 2016
6
0
4,510
WHEA_UNCORRECTABLE_ERROR (124)
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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80081d34a8, 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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:
fffff880`031a25b0 fffff800`0351dcb9 : fffffa80`081d3480 fffffa80`067aa550 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a2ad0 fffff800`033fcc07 : fffffa80`081d3480 fffff800`034772d8 fffffa80`067aa550 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a2b00 fffff800`03363c55 : fffff800`034d9ba0 00000000`00000001 fffffa80`08107110 fffffa80`067aa550 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a2b40 fffff800`032d6b69 : fffff880`00c5ae00 fffff800`03363c30 fffffa80`067aa500 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a2b70 fffff800`03566b86 : 00000000`00000000 fffffa80`067aa550 00000000`00000080 fffffa80`066e9b10 : nt!ExpWorkerThread+0x111
fffff880`031a2c00 fffff800`032be0e6 : fffff880`009b3180 fffffa80`067aa550 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a2c40 00000000`00000000 : fffff880`031a3000 fffff880`0319d000 fffff880`031a1c50 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH: {78c2f422-5335-4ef3-5cef-a28518da5023}

Followup: MachineOwner
 
Upvote 0 Downvote
V

visualcmos

Reputable
Jan 9, 2016
6
0
4,510
well crap, It finally got over the 124 error and gave me another one, this time pointing towards my gpu. I also noticed after running furmark again that my gpu temps were hitting 100c. heres the minidump for that one:
BugCheck 117, {fffffa800b58a010, fffff880111cae80, 0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+15ee80 )

Followup: MachineOwner
---------

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa800b58a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880111cae80, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
nvlddmkm+15ee80
fffff880`111cae80 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:
fffff880`029df4f0 fffff880`040fa72b : fffffa80`0b58a010 fffff880`041470cc fffffa80`0b58a010 fffff880`040c8807 : watchdog!WdDbgReportRecreate+0xa3
fffff880`029dfa10 fffff880`040fb3f0 : fffff8a0`03564850 fffff8a0`03564850 00000000`00000080 fffffa80`0b58a010 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`029dfa60 fffff880`040cf6b3 : 00000000`00000001 fffffa80`096ca000 00000000`00000000 fffff880`0000005e : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`029dfa90 fffff880`040fbf43 : 00000000`0000000f ffffffff`fffe7960 fffffa80`0b58a010 fffff880`041cbf3c : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`029dfb40 fffff880`041cc03d : fffffa80`0b449480 00000000`00000080 00000000`00000000 fffffa80`096b3410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`029dfbc0 fffff800`0356cb86 : 00000000`03bcf2eb fffffa80`096f3060 fffffa80`066dab10 fffffa80`096f3060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`029dfc00 fffff800`032c40e6 : fffff800`03452e80 fffffa80`096f3060 fffff800`03460cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`029dfc40 00000000`00000000 : fffff880`029e0000 fffff880`029da000 fffff880`0c347d40 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15ee80
fffff880`111cae80 ?? ???

SYMBOL_NAME: nvlddmkm+15ee80

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5671716e

FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x117_image_nvlddmkm.sys

FAILURE_ID_HASH: {c306f7be-ced2-9b11-9b10-d0239a4fd800}



All the drivers have been and are up to date, I even tried goin back to a couple older ones, still same.What I dont understand now is why does it only overheat with h1z1 game? not gta 5, not witcher 3, crossfire, or any other game I play. I also pulled out the card blew some air to clean her off, looked her over and everything seemed okay, fan doesnt run hard or loud, but even if i crank it up to max or so with evga percision x it doesnt help much. Is it time for a new gpu? xD
 
Upvote 0 Downvote
V

visualcmos

Reputable
Jan 9, 2016
6
0
4,510
tried that, didn't work still over heating, gpu running 49-70 idle and now getting up to 90s and crashes at 100 in a couple games now, not just h1z1. so i', assuming the gpu is going out. any other ideas or thoughts would help though before I get a new one. ;D I tried underclocking it and jacking the gpu fan up to 70 but still overheated ;(
 
Upvote 0 Downvote
O

OldAmazingBrain

Reputable
Dec 1, 2015
142
0
4,710
Have you tried replacing the thermal paste (If it's not under warranty) or getting the manufacturer to do so? Also, try keeping the GPU fan at 100 and using headphones. Make sure it's 100 % and not 100 degrees.
 
Upvote 0 Downvote
Solution
V

visualcmos

Reputable
Jan 9, 2016
6
0
4,510
Okay so I took out the gpu and took her apart, and yea the old thermal paste was ugly, I cleaned it all up and put some new on, ran furmark for an hour with no errors and she never got over 72 c. So I fired up ol h1z1 and so far so good, It hasn't got much higher than 60s c so far. @OldAmazingBrain ty for the input and I'll post back if any more probs occur, ty again ;P
 
Upvote 1 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom