BSOD...why?

moonbogg

Lifer
Jan 8, 2011
10,731
3,440
136
OK, so i'm at 4.5 @ 1.36-1.369 offset voltage. I get occasional BSODs playing BF3 after about 3 hours. Could this be not enough voltage or do you suspect VRMs overheating? I don't know crap about VRMs so I have no idea. I'll turn down the OC and reduce voltage if I have to.
 

dma0991

Platinum Member
Mar 17, 2011
2,723
1
0
Write down the BSOD codes on a piece of paper as it happens.
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
 

Joseph F

Diamond Member
Jul 12, 2010
3,522
2
0
If your VRMs were overheating, you'd probably be having worse issues than BSODs.
IMO, with the little information I have to go on, you probably have to back-off the frequency, a little bit.
(Or, you could try to increase the voltage, if your cooling, motherboard, and PSU can cope with it)
 

moonbogg

Lifer
Jan 8, 2011
10,731
3,440
136
Thanks for the awesome BSOD code reference. I will have to wait until it happens again to get the codes. I only have an H80, so I really can't increase Vcore anymore without getting really damn hot and I just don't have the stomach to fork out the cash for real watercooling, especially since I might ditch the whole damn rig for a haswell setup. I'll let you know how it goes, thanks.
 

JAG87

Diamond Member
Jan 3, 2006
3,921
3
76
Thanks for the awesome BSOD code reference. I will have to wait until it happens again to get the codes. I only have an H80, so I really can't increase Vcore anymore without getting really damn hot and I just don't have the stomach to fork out the cash for real watercooling, especially since I might ditch the whole damn rig for a haswell setup. I'll let you know how it goes, thanks.


You can just check the Event Viewer for the BSOD info.
 

2is

Diamond Member
Apr 8, 2012
4,281
131
106
Drop the multi by 1 if BSOD goes away you can keep it that way or bump voltage for 4.5
 

BonzaiDuck

Lifer
Jun 30, 2004
16,678
2,053
126
Drop the multi by 1 if BSOD goes away you can keep it that way or bump voltage for 4.5

Did he say that he had "Offset" at 1.36+ or that his load voltage for (whatever offset he was using) showed 1.36+? In other words, did he mean what he said, or am I just confused by an unfortunate choice of wording?

Nobody asked him which stress-tests he ran and for how long when he built the rig and before these BSODs happened. I've seen a Prime95 small-FFT test run for a good part of a whole day, only to get a "fail" after several hours with large-FFT.
 

2is

Diamond Member
Apr 8, 2012
4,281
131
106
Did he say that he had "Offset" at 1.36+ or that his load voltage for (whatever offset he was using) showed 1.36+? In other words, did he mean what he said, or am I just confused by an unfortunate choice of wording?

Nobody asked him which stress-tests he ran and for how long when he built the rig and before these BSODs happened. I've seen a Prime95 small-FFT test run for a good part of a whole day, only to get a "fail" after several hours with large-FFT.

Regardless, if he's getting a BSOD it's an unstable system. You can raise voltage or lower clocks to stabilize it (assuming the instability is due to OC)
 

moonbogg

Lifer
Jan 8, 2011
10,731
3,440
136
I did a bit more reading (not much, it hurts) and I saw that after 4.3ghz the required voltage for stabilization starts to climb fast and steep. I backed it down to 4.3 and left vcore on auto in offset mode. I turned off LLC to keep voltage low. So far, under load voltage is 1.288 and stable so far and temps are a good bit lower as well. I'll leave it like this until it crashes again, but so far so good. Not worth the headache to go for that extra 200mhz.
To clarify, before I was at 1.36v under load as reported in cpuz.
 

2is

Diamond Member
Apr 8, 2012
4,281
131
106
Yeah, that's an expensive CPU to force it to a speed you can tell it really doesn't want to do.
 

moonbogg

Lifer
Jan 8, 2011
10,731
3,440
136
Yeah, that's an expensive CPU to force it to a speed you can tell it really doesn't want to do.

Agreed. OK, so again, I am now happy with 4.3 and am now focusing on keeping voltage low. I turned all those power phase features to normal and CPU LLC is set to normal so it doesn't go too high. CPU hits about 1.288 under prime 95 load. Any reason why I would need LLC with an OC like this? If its working then no problem right?
 

coffeejunkee

Golden Member
Jul 31, 2010
1,153
0
0
I have a different cpu but had to disable C6 sleep state beyond 4.3GHz. Prime or Linx didn't catch this instability, but it was there causing crashes in games.

So try that, or just stick to 4.3GHz, it's not like it's slow or anything at that freq. And I see no reason for using llc either. Only use it when you have to.
 

2is

Diamond Member
Apr 8, 2012
4,281
131
106
If its stable without LLC then it's stable. Leave it disabled.