BSOD Need help!

JLuzier40

Reputable
Apr 24, 2015
2
0
4,510
Hello

I've updated my graphics card about a month ago from an ATI Radeon HD 5770 1024 MB to an R9 290X 8GB. I also ordered a new PSU (Corsair 750M) to go with it. I hooked them in and installed drivers, etc. My games would crash after about half an hour. I couldn't solve it so I took it to my local computer repair store. They said my mobo/processor were messed up and reccomended I just switch out all my components. Here are my current specs:

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name GATEWAY-DESKTOP
System Manufacturer MSI
System Model MS-7641
System Type x64-based PC
Processor AMD FX(tm)-8350 Eight-Core Processor, 4000 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. V25.0, 5/28/2013
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 6.72 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 14.7 GB
Page File Space 8.00
GPU Sapphire R9 290X 8GB

I bluescreen a few seconds after all the startup processes finish, and if not then, a few minutes after playing my games. Here is the bluescreen information. It's the same information every bsod.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800851F8F8
BCP3: 0000000000000000
BCP4: 0000000000000000
 


Thanks for the reply. I'm looking at the contents of Minidump right now, what do you want me to do with them?
 
common overclocking bugcheck called by the CPU because of a internal error detected. Most often the error is detected by the cpu cache memory controller. Most often cause will be overclocking, overheating or too low voltage applied to the CPU because of lack of proper power to the GPU.

if you have a memory .dmp the system uptime is a useful indicator as to the cause of the CPU bugcheck.
A short system uptime of less than 15 seconds indicates a power problem (voltage to cpu went too low and the CPU reset) A longer uptime is often a overheating issue.

generally, to fix, reset the BIOS to defaults or update, remove any overclocking software (cpu and GPU)
if you have a debugger you can use the command
!errrec on the WHEA_ERROR_RECORD address (parameter 2 in the bugcheck)
most likely a internal CPU cache memory or bus error.
sometimes on older systems it will be something directly connected to the CPU that is overheating.