• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

i5 2500k problem?

C

crazyjx

n00b
Joined
Jul 11, 2011
Messages
12
My computer has been bsoding for a while and I have no clue what is wrong.

At first I thought it was my ram and it turned out one of my ram sticks had failed so I sent it in to RMA and when I got it back my computer still bsod every once in a while. I RMA my hard drive next and same it still bsod. And that's where I'm stuck at. I don't think it's my GPU. I'd have to guess it's my cpu? Does anybody have any information that could help me?
 
Have you tried reverting to factory settings in the BIOS? Also, if you're concerned there's something wrong with the CPU I would try running Prime 95.
 
I forgot to mention I ran occt on cpu for an hour and it didn't crash. So does that mean it can't be my cpu?
 
before you go blaming hardware for BSOD's perhaps you should try reinstalling the OS or running a different one. BSOD's can be caused by many things and an OS that has been mucked up with too much software and/or malware/viruses can be the source just as much as hardware. what you should do is write down or take a picture of the BSOD when it happens and then go on the net and google the error and that will help lead you to the source of the BSOD. blindly replacing and blaming hardware without testing it properly is not the way to go ;)

generally speaking computer hardware does not just up and fail one day when its pretty new. in my 16+ years of experience with PC's most hardware failures are a result of the end user doing something stupid or not keeping their PC clean on the inside and cool. DOA hardware is another story but if it works for the first month i've never had hardware die within 2-3 years after that with the exception of some crappy hard drives but thats why i try to use enterprise drives now because they are much more reliable not to mention faster. one of my current 15k RPM SAS drives has been on for 936 days and has 1,272,128 Tb worth of lifetime writes to it!
 
Last edited:
I'm on a fresh windows right now. It's on my RMA'd hard drive. I reformatted shortly after the bsods started occuring so I'm sure it's hardware.

I should have mentioned that the bsods happened shortly I overclocked. I didn't insanely overclock it though. I was running 3.5 on stock cpu cooler until I got my h60 and then I jumped to 4.0. It didn't bsod right after i booted, but it happened twice so I went back to stock setting. I tried resetting my bios.
 
crazyjx said:
I'm on a fresh windows right now. It's on my RMA'd hard drive. I reformatted shortly after the bsods started occuring so I'm sure it's hardware.

I should have mentioned that the bsods happened shortly I overclocked. I didn't insanely overclock it though. I was running 3.5 on stock cpu cooler until I got my h60 and then I jumped to 4.0. It didn't bsod right after i booted, but it happened twice so I went back to stock setting. I tried resetting my bios.
Click to expand...

you play with voltages when you overclocked? 4ghz is pretty easy for a 2500k to get to though so you shouldn't have needed to do much if any voltage increase. can you tell us what the BSOD error is ? does it change (ie its random?) nobody is going to tell you that yep its you CPU and honestly unless you cranked the voltages up too high on your CPU for no reason your CPU is not likely to be the problem, i would blame the motherboard first :)

what i would do if this was my PC and i was certain it was a hardware issue is i would tear out any hardware i did not need to make it run. bare bones. then start swaping parts that i have spares of (video card, ram, hard drives etc.) as you do this you can rule out each of those parts and if you do then your left with the mobo and the CPU and i have seen alot more dead or failing motherboards than i have seen CPU's
 
also what is your motherboard? i don't see it listed in your sig.
 
Frito said:
you play with voltages when you overclocked? 4ghz is pretty easy for a 2500k to get to though so you shouldn't have needed to do much if any voltage increase. can you tell us what the BSOD error is ? does it change (ie its random?) nobody is going to tell you that yep its you CPU and honestly unless you cranked the voltages up too high on your CPU for no reason your CPU is not likely to be the problem, i would blame the motherboard first :)

what i would do if this was my PC and i was certain it was a hardware issue is i would tear out any hardware i did not need to make it run. bare bones. then start swaping parts that i have spares of (video card, ram, hard drives etc.) as you do this you can rule out each of those parts and if you do then your left with the mobo and the CPU and i have seen alot more dead or failing motherboards than i have seen CPU's
Click to expand...

Great post.

Yeah, even minor issues with voltages can cause a BSOD. I'd agree that it's highly unlikely that the CPU is bad. They rarely fail. I've run across three that have actually failed in my years of working on computers. For hardware I would suspect the PSU or the MOBO next to be honest. And a yeah, a zero config is always a good idea.

I do have some questions though as well. Had the system been running fine since you built it? It was only until you over clocked that it started? Also, you made sure that your memory is compatible with the MOBO and that the voltages match up with the processor?
 
I did forget to put my mobo. It's a MSI Z68 Z68MA-ED55 (B3) and I never increased voltage oh and if it matters my power supply is a 650 watt antec truepower

EDIT: My computer is pretty new. It's very close to being a year old.


PolygonGTC said:
I do have some questions though as well. Had the system been running fine since you built it? It was only until you over clocked that it started? Also, you made sure that your memory is compatible with the MOBO and that the voltages match up with the processor?
Click to expand...

Yeah I actually overclocked it pretty early to 3.5ghz on stock cooler and I got a H60 I upped it to 4.0 and the following week one of my ram sticks failed. I know for sure one of the sticks failed because I tested it. On the plus side of RMAing my hard drive was that Western Digital sent a 750 gb caviar black, but now I'm doubting whether my hard drive was the case. Might as well say it here that I really like Western Digital advance RMA they send you a hard drive so you can back up all your stuff and then send the defective one back.
 
Last edited:
crazyjx said:
I did forget to put my mobo. It's a MSI Z68 Z68MA-ED55 (B3) and I never increased voltage oh and if it matters my power supply is a 650 watt antec truepower

EDIT: My computer is pretty new. It's very close to being a year old.




Yeah I actually overclocked it pretty early to 3.5ghz on stock cooler and I got a H60 I upped it to 4.0 and the following week one of my ram sticks failed. I know for sure one of the sticks failed because I tested it. On the plus side of RMAing my hard drive was that Western Digital sent a 750 gb caviar black, but now I'm doubting whether my hard drive was the case. Might as well say it here that I really like Western Digital advance RMA they send you a hard drive so you can back up all your stuff and then send the defective one back.
Click to expand...


WD makes pretty good stuff and are a good company.

i'm going to have to agree with Polygon that its likey the motherboard or your power supply. faulty/power supply that cannot output what the PC needs to run will result in random lockups and crashes, though usually only if the PC is under a load and pulling a lot of power. so i would try a PSU next and then if thats not it mobo. the small amount of overclocking you did will not damage the CPU. it could of however put too much stress on your PSU or motherboard and caused them to start failing.
 
as others have said... before randomly swapping more hardware


you might want to do some work to diagnose the BSOD


bluescreenview is a good tool that has helped me track down a few BSOD problems for me.

http://www.nirsoft.net/utils/blue_screen_view.html


pretty much for me it has usually been old drivers / drivers that for whatever reason didn't install properly.... it did also help me track down that a $12 trendnet Gigabit nic was a bad idea ;) replaced it with a intel Gigabit nic and life was good.
 
atarione said:
as others have said... before randomly swapping more hardware


you might want to do some work to diagnose the BSOD


bluescreenview is a good tool that has helped me track down a few BSOD problems for me.

http://www.nirsoft.net/utils/blue_screen_view.html


pretty much for me it has usually been old drivers / drivers that for whatever reason didn't install properly.... it did also help me track down that a $12 trendnet Gigabit nic was a bad idea ;) replaced it with a intel Gigabit nic and life was good.
Click to expand...

hes on a fresh install now so its not a software problem. looking into the BSOD error though could potentially help narrow down what part of your hardware is causing the error but then again its probably random as hardware induced BSOD often are.
 
fair enough.. but drivers can cause the bsod on fresh installs


especially if you are my dad and absolutely refuse to listen to reason and only install the drivers from the CD that came with new hardware :rolleyes: and will not be convinced that downloading the newest drivers off the web would be better... but i digress...
 
atarione said:
fair enough.. but drivers can cause the bsod on fresh installs


especially if you are my dad and absolutely refuse to listen to reason and only install the drivers from the CD that came with new hardware :rolleyes: and will not be convinced that downloading the newest drivers off the web would be better... but i digress...
Click to expand...

haha yeah i could see that happening but that would be some bad luck.
 
So I'm took out my graphics card and have been browsing the web for several hours. I know that isn't much time to determine what's wrong but I haven't bsoded and when I had my card in, it was random but happened within 30-40 minutes. Could graphic cards cause bsod?
 
crazyjx said:
So I'm took out my graphics card and have been browsing the web for several hours. I know that isn't much time to determine what's wrong but I haven't bsoded and when I had my card in, it was random but happened within 30-40 minutes. Could graphic cards cause bsod?
Click to expand...

sure it can cause BSOD's. i take it your using the onboard GPU on your CPU then? the reason why its not crashing could also be because without the extra power the discrete GPU takes even at idle is causing your PSU to fail to deliver the power required, assuming its going out.
 
Yeah I thought about that too. I was planning on switching out my PSU with another one, but the only one I have is a 430 watt enermax which wouldn't be able to run the GPU too so there was no point. I guess the only option is to wait for my RMA to come
 
IB S1155 is tick after the tock. Should be better than preceding tock. Tick is good.
 
Could taking power supply to a local shop for testing.There is usually a little bit of a charge to taste
 
crazyjx said:
I'm on a fresh windows right now. It's on my RMA'd hard drive. I reformatted shortly after the bsods started occuring so I'm sure it's hardware.

I should have mentioned that the bsods happened shortly I overclocked. I didn't insanely overclock it though. I was running 3.5 on stock cpu cooler until I got my h60 and then I jumped to 4.0. It didn't bsod right after i booted, but it happened twice so I went back to stock setting. I tried resetting my bios.
Click to expand...

Did this happen after your fresh install? A bad OC can definitely corrupt files/your OS.
 
You must log in or register to reply here.
Back
Top