Occasional BSOD

fobose · 5 Jun 2016 at 00:26

Hi all,

I have been posting in the memory section (although my post appears to have disappeared now).

Basically, every now and then, and I mean like every 6-8 weeks I will get an occasional BSOD. This has happened since I built the rig in sig. The BSOD's are normally memory management or IRQ not equal to or less etc. Anyway, I thought this was a RAM issue so I have slowly been increasing my DDR3 RAM voltage from the recommended 1.65V to 1.7V (been running with XMP enabled, but issues also occured without the XMP profile enabled).

I can game all day without any issues, and yet the random odd time I am surfing (between 6-8 weeks) I will get the random BSOD. I recently replaced my Intel 520 180GB SSD (Win 8.1) and upgraded to a Samsung 850 EVO 500GB (upgraded to Win10 too) so I don't think it is a software issue (I did a fresh install).

Last night I ran memtest and left it running for 19 hours, 10 minute. So that it could complete 8 of 8 passes, which it did without errors. I am left thinking wtf..

So if any one else can suggest anything that would be great! The last BSOD message was: Error code: 0xc0000017

*edit*

Rroff · 5 Jun 2016 at 00:41

Try increasing the vcore and vtt/imc (might be vccsa) voltages 1 notch (keep vtt below 1.2v).

fobose · 5 Jun 2016 at 07:25

Hi Rroff,

Thanks for the reply. I am a bit of a newb when it comes to those settings. I have found the vcore and increased it from 1.130V to 1.135V, is that a worthy increase?

I couldn't find the other setting you mention, should it be in the same location? I did look through the other menus. Maybe it only appears when something is set to manual?

*edit*

Just noticed that the 'CPU System Agent Voltage' mentions it controls the IMC on the description. What should I increase this by? I am also not sure where the VTT setting is.

Stealthploit · 5 Jun 2016 at 17:03

im sure it would would be fine with 1.135V does the BSOD occur under load ? if os yes that might solve your problem

Rroff · 5 Jun 2016 at 17:13

You are manually setting/limiting voltage to 1.135V there - the 1.130V figure may be just the CPU nominal voltage and not what it needs to run stable under load. You may be better off using offset voltage to increase it slightly but that would take a bit more explaining.

System agent usually controls VTT and IMC on boards setup that way but without knowing what its running at I'm not sure how much to add with a positive offset :S

fobose · 5 Jun 2016 at 18:43

Stealthploit said:
im sure it would would be fine with 1.135V does the BSOD occur under load ? if os yes that might solve your problem

Nope, never had a BSOD under load. I can play games all day long (10+ hours) without any issues at all. It will always do it when I am surfing, or sometimes when I reboot. In the last 11 months I have only had about 6 of these BSODS.

Rroff said:
You are manually setting/limiting voltage to 1.135V there - the 1.130V figure may be just the CPU nominal voltage and not what it needs to run stable under load. You may be better off using offset voltage to increase it slightly but that would take a bit more explaining.

System agent usually controls VTT and IMC on boards setup that way but without knowing what its running at I'm not sure how much to add with a positive offset :S

Ok thanks for that. I have removed my manual setting for now then. My offset voltages don't let me adjust them (greyed out). Is there a way I can find out what the system agent is running at? HW monitor lists 'System ageny offset' which is 0.000V but doesn't actually say what its using.

Rroff · 5 Jun 2016 at 20:05

When you change the vcore setting it should have something like Auto, Normal (or Offset) then a range of voltages, when you choose the 2nd setting (Normal) it should unlock the offset entry which will generally start at minus voltages so you'd have to scroll through a bit until you find the low + values - be careful with it as it is easy to mis-read/mix up voltage ranges and put a lot of extra offset voltage through the CPU which ain't good - usually just edging it up a couple of notches can be enough.

fobose · 5 Jun 2016 at 22:08

Ok thanks Rroff. I will give that a go tomorrow after work. I presume I need to be a + voltage though and not a - right?

*edit*

I have done it now instead of waiting till tomorrow after work. I have set the vcore to normal, and the vcore offset to +0.010V.

fobose · 6 Jun 2016 at 06:25

After I logged in to my PC this morning, I noticed a few things didn't feel 'right'. The login sequence hanged for a start, and then Chrome kept having a hissy fit and closing itself. I also tried opening CPUZ and HW monitor and that gave me an error. I rebooted, turned the voltage settings back to Auto and everything seems ok again.

Did a do something wrong or forget to do something? Maybe the 'normal' mode locked the Vcore to 0.734V (the idle voltage)?