new graphics card causing overheating and bsod while gaming.

Belmonte

Reputable
Jun 10, 2015
3
0
4,510
hey guys i just ordered a r9 270x and replaced my older gtx 650 and now when i start playing counterstrike my CPU overheats and causes my computer to bsod and shut off the message in the blue screen of death just says that its shutting down to prevent damage. at first i thought it was the twin frozr blowing hot air into my case causing my cpu to overheat so i went out and bought a system blower and 3 new fans so i went from 3 active fans to 9. is it a fualty card or is my proccessor too weak for this new card need help fast! my team is getting pissed at me :( specs
cpu=amd fx 4130 zambezi 3.8 ghz 4 core
motherboard= random biostar
8 gigs ram g.skill 1600 mhz
gpu= r9 270x
 
what kind of heat sink do you have on your processor? do you suppose it is loose? is it full of dust? that Processor is more than powerful enough and a single R9270X does not put out enough heat to make that kind of change. Do you think it got knocked loose or shifted when you put in the new GPU? have you considered fresh thermal paste for it also? you may want to get a better than stock heat sink if that is all you have.
 
your old GPU took less power than your new one.
http://www.realhardtechx.com/index_archivos/Page362.htm

new one requires at least a 500 W power supply, old one required 400W power supply.
(new GPU has 2 (six pin connectors at 75 watts each + the PCI/e bus at 75 watts)

you will want to check to make sure your power is correctly rated.
(any GPU overclocking will cause the GPU to use extra power so remove any overclock utilities )

Note: generally you will get a bugcheck 0x124 if your GPU pulls too much power from the PCI/E bus. you will get bugcheck 0x116 or 0x117 i don't recall the code but it is a video timeout if your system is marginal. You can also just get hangs in the graphic drivers.

 
I did not see a temperature of the CPU mentioned so I am not sure if it is a fact or an assumption.
Sometimes people get a bugcheck 0x124, look it up and assume a overheated CPU when in fact they have a GPU power problem that caused power fluctuations to the CPU.

I guess it would be better to just look at the memory dump to determine the cause.


 

Belmonte

Reputable
Jun 10, 2015
3
0
4,510
heatsink is fine i actually got an aftermarket coolmaster fan and threw it on there to replace the stock one because it was very loud. The temps were fine when i was monitoring it with speedfan. 53c was my max under load with my old graphics card. the heatsink is not loose by any means but now that i think of it the thermal paste was kind of thin. but anyway i already sent the graphics card back to the manufacturer and i am actually planning on snagging an r9 280. also i decided to upgrade my whole pc as i ordered a xeon e3 1231v3 processor and a h97 gaming 3 mobo from MSI :) very excited but now i am worried about the powersupply. i think my proccessor temps were reaching 65c+ with the 270x but maybe it was the power consumption like John said it might have been. is there anyway to test my psu to see if it is capable of putting out enough power for my new 280? i went onto pcpartpicker and my psu should be able to handle the load quite well if it is putting out the correct power so please let me know if you guys know of a way for me to check my power rates and see if maybe it was my psu fluctuating power and giving me the bsod. thanks for thehelp guys very apreciated!
 
if you want to know if your power is the cause of the bugchekc 0x124, look at the memory dump
specifically the system uptime shown by the debugger. if it is under 15 seconds or so, your CPU was reset. if the uptime is longer, say more than 15 mins then look for overheating issues. don't assume that just because you were playing a game for hours that your uptime will be hours. Lots of people describe palying a game and then getting bugcheck 0x124 and don't realize their machine rebooted on them and bugchecked on startup.
put the memory dump file on a server and post a link. often there is some useful info even in a panic CPU shutdown of the system (bugcheck 0x124)