• 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 problems continued

C

crazyjx

n00b
Joined
Jul 11, 2011
Messages
12
This is the first thread I made about my blue screen problem.

At first I suspected my cpu to be the problem because after I oc'ed it started bsoding, but some people said it was the psu, but I bought a new one and it still bsods. It's highly unlikely it's the cpu, but I'll have to take a wild guess and say it's the cpu.

Is there anyone who can give some insight on this problem?
 
I skimmed it (super skimmed), but it could just be drivers? Got a flakey wireless card? Audio driver? Reinstall your OS perhaps?
 
I replaced every part including the hard drive but not the graphics card which I have confirmed is not the problem and drivers are definitely not the problem. I'm plugged in with an ethernet cord.
 
I had the same problem with my MSI board, seems to be that if you OC on an MSI board you have to bump the CPU voltage up manually alittle.
I started by replaced my VC, MB, cables. Then one day I did an obscure search and found someone mention bumping my CPU voltage on an i7 2600k running at 4ghz to 1.225v. Apparently it was running at 1.17v when it was set to AUTO...too low! I also have DRAM voltage now manually set at 1.65. No more random BSODs.
 
OP:
You were asked twice to supply the BSOD error you were getting, but instead of doing that, you ignored *everyone* and then ran out and bought a new power supply, which didn't help you, and you wound up wasting money. If you don't want help, and you want to ignore us, what's the point of even posting here?

So I guess I'll ask the 4th time: what is the BSOD code error you were getting? If you got more than one, list it.

And yes, try setting your CPU vcore manually to 1.25v-1.30v, maybe with a little Loadline Calibration (may be called "Vdroop control" on that board).
 
Falkentyne said:
OP:
You were asked twice to supply the BSOD error you were getting, but instead of doing that, you ignored *everyone* and then ran out and bought a new power supply, which didn't help you, and you wound up wasting money. If you don't want help, and you want to ignore us, what's the point of even posting here?

So I guess I'll ask the 4th time: what is the BSOD code error you were getting? If you got more than one, list it.

And yes, try setting your CPU vcore manually to 1.25v-1.30v, maybe with a little Loadline Calibration (may be called "Vdroop control" on that board).
Click to expand...

+1

OP: Do as the man says above!
 
I'm at stock speeds so I don't think voltage is the problem. The power supply wasn't for fixing it I wanted to crossfire and I originally had a 650.

Everytime the bsod happens it's because of ntoskrnl.exe Is this how I tell the bsod error? or do I have to take a picture when it happens? I'm using bluescreenview.
 
There is usually a hexadecimal code to the bluescreen. The kernal file is just the windows core, but we want the code to the BSOD. Usually its something like STOP 0x000101 or STOP 0x00000124 or 0x0000007f or 0x00008e; I think those are the most common ones. Usually it's unrecoverable hardware error, which the 101's and 124's are, which tend to be directly CPU related, while other errors can be caused by a variety of things. IRQL_not_less_or_equal, or bad_pool_header tend to be driver related, although in the past, unstable cpus could cause these too, as well as RAM issues.

You most definitely should NOT be getting them at stock speeds. This might point directly to a memory issue, unless the CPU's IMC is dead ...
 
up the voltage, that ought to help with the 124 error. Either vccio or vcore. Most probaby vcore
 
Yup, for Sandy Bridge processors, 124 is vcore related. Doesn't matter if your clocks are stock or not, if it's not getting enough voltage you'll get BSOD's. Some chips require more voltage than others.
 
Sounds unstable. I'm guessing you have had unstable system over clocks and have corrupted the OS. I like to run memtest86+ from USB flash drive for stability before booting into OS. If your OC is unstable and you boot into windows you can screw up your OS. Try going into Windows restore mode to check and fix problems with Windows.

All system speeds, voltages and temps have to set correctly for your system to not crash during operation.

I would load safe BIOS settings at stock speeds with CPU and re-install OS and not mess with it. See if it will operate stable with those settings. If not I'd RMA the MB. MB is more likely to be the problem at stock settings. RAM can be a problem as well. Some memory will run fine at stock system settings but with over clocks it fails. I doubt the CPU is the problem.
 
I agree with this. was the os reinstalled with the overcolocked settings?? That has happened to me before and it ended up being corrupted. ah how we learn lol.

Can someone merge these two threads together?
 
You must log in or register to reply here.
Back
Top