Errors BEFORE OC - Prime95: Expected less than 0.5

[joeb361]

Posted here, wasn't too sure which section it goes under. Normally I see this error related to overclocking, so here it goes

I recently got a new custom build (put together by a friend).
It is:
i5 2500k - CPU
Gigabyte UD5H - Mobo
MSI GTX 670 - GPU
Corsair Vengeance 2x4GB 1600mhz - RAM
Noctua NHu9b - CPU cooler
CM Storm scout - Case
CM silent pro 700w - PSU

If you need to know anything else, just ask.
I planned on overclocking, and started preparing by downloading all required software. (prime 95, monitoring programs etc)

I ran Prime95, and instantly got: Fatal error: rounding was 0.5, expected less than 0.4
If I run:
Small FFTs - No errors
In-place Large FFTs- no errors
Blend - Fatal error
Within a couple of minute each 'worker' will usually fail from that error, in a random order.

I have changed NO settings, this build is barely a few weeks old.
No changes in the BIOS, but there is a later version out, would it be worth downloading that?
Everything I have read so far indicates it is a problem with the CPU or RAM.

I read it could be a RAM issue, and try to increasing the voltage. (stock is 1.500)
Changed voltage of RAM to 1.550
Booted, ran prime95.
Within 10 seconds the error popped up, I went to close it but then it blue screened.
Changed voltage back to 1.500, and booted fine again. This led me to think it was a RAM error, so I ran memtest.

I ran 6 passes of memtest, all fine.
http://img62.imageshack.us/img62/6617/img0793nj.jpg
I did notice the BIOS had set my RAM automatically to 1333mhz, so I changed it to 1600, but this didn't fix anything.

I got told to try Intel burn test, so ran that. Passed on normal, got an error on high.
http://img833.imageshack.us/img833/4495/intelburntest.jpg


Picture of the error on prime95 with temps up:
http://img708.imageshack.us/img708/7466/prime95.jpg

Prime95 error with CPU-Z up:
(Core voltage jumped around by around 0.1)
http://img543.imageshack.us/img543/6226/prime952.jpg

Would this be safe to carry on and overclock? Or is it even stable if it receives these errors, as I'm not actually sure what they mean.
I understand this is quite a complicated problem, but any help would be much appreciated

 

[Pinhedd]

Looks like a memory IO problem. Try performing a firmware update

 

[joeb361]

I'm quite new to this, and have no idea what that means xD
Could you go into more detail or direct me to a guide? Thanks

 

[Pinhedd]

The latest firmware revision is version F8 released May 31st

you can download it here

http://www.gigabyte.com/products/product-page.aspx?pid=4139#bios

Download Type -> BIOS

It's an easy process, may already be up to date.

 

[joeb361]

Oh ok thanks.
Im currently on F4
Another update: If I run 'In-place large FTS' (all cpu, some ram) I get the error in about 10 minutes.
If I run it on blend (max everything) I get it in about 10 seconds.
On small FFTs (not much ram) I don't get an error. I dont think so, but i've ran it for 3 hours without an error.
Thats why I think it would be a memory problem, but memtest says otherwise :S

I will trying updating the BIOS now

 

[Pinhedd]

Small-FFTs will only test the ram if it needs to. It tries to fit as much of the data in the cache as humanly possible but this is largely outside of Prime95's control

 

[joeb361]

Ok, successfully updated to F8, however still getting the errors on prime 95 :/
Could it possibly be a setting in the bios? Something limiting voltage etc

 

[Pinhedd]

Ok, successfully updated to F8, however still getting the errors on prime 95 :/
Could it possibly be a setting in the bios? Something limiting voltage etc

Unlikely. There's a lemon in there somewhere, time to find it.

Take out one of the 4GB sticks and test it, then repeat with the other one.

Memtest tests your ram for errors, not stability. That's what Prime is for

 

[joeb361]

OK, I will try that.
Thanks for the help
Wouldn't it be an error in the RAM which causes it to be unstable?
I asked for help from other people, and they have all been stumped :/
Not tried individual RAM though, and memtest was when it was at 1333mhz (it should be 1600)

 

[Pinhedd]

OK, I will try that.
Thanks for the help
Wouldn't it be an error in the RAM which causes it to be unstable?
I asked for help from other people, and they have all been stumped :/
Not tried individual RAM though, and memtest was when it was at 1333mhz (it should be 1600)

Ah fun. Try Prime at 1333. It's rare for Intel chips and motherboards to have a hard time at 1600 but it is technically overclocking

 

[tiptonsr]

I actually had an error message similiar to that a few hours ago OC'ing my I5 2500k I increased the voltage a click or two and it worked fine afterwards. I know you said you haven't tweaked it yet but you might try increasing cpu voltage to 1.31v if it is lower and try. if its already at 1.31 or 1.32 then DO NOT INCREASE. Not sure if this is the issue but worth a shot. Also might check to make sure your ram voltage is at recommended settings probably 1.5v but check to be sure.

 

[joeb361]

My ram is supposed to be 1600mhz, so I can't see that being a problem?
I did a lot of tests on 1333mhz, some of those screenshots were (I didn't realise until someone pointed it out xD)
I'll put my vcore to 1.245, but i'll try 1.31 then.
If that doesn't solve, i'll memtest each individual stick and get back to you

 

[Pinhedd]

My ram is supposed to be 1600mhz, so I can't see that being a problem?
I did a lot of tests on 1333mhz, some of those screenshots were (I didn't realise until someone pointed it out xD)
I'll put my vcore to 1.245, but i'll try 1.31 then.
If that doesn't solve, i'll memtest each individual stick and get back to you

The 2500K only has native support for up to DDR3-1333. Going above this point to 1600 is trivial but it is technically overclocking and sometimes this can cause stability problems. For a very small number of chips the XMP profile alone won't work, additional voltage may be required

 

[joeb361]

Should I enable XMP?
I didn't know 1600mhz wasn't officially supported, that sucks.
Should I change voltage to ram? Last time I tried 1.55 instead of 1.5, and it blue screened

 

[joeb361]

Upped vcore to 1.32, still got the errors

 

[Pinhedd]

Should I enable XMP?
I didn't know 1600mhz wasn't officially supported, that sucks.
Should I change voltage to ram? Last time I tried 1.55 instead of 1.5, and it blue screened

Use the XMP profile!

 

[joeb361]

Am I supposed to?
Not sure really what it does, its auto set to enable.
Should I use it at 1333mhz or 1600mhz?

 

[Pinhedd]

Am I supposed to?
Not sure really what it does, its auto set to enable.
Should I use it at 1333mhz or 1600mhz?

The XMP profiles automatically configure the voltages and timings

 

[joeb361]

Loaded optimised defaults, then enabled XMP (which set it at 1600mhz)
Booted and ran prime 95, still errors :/
Time for memtest on each individual stick?

 

[Pinhedd]

yup, time to test each stick

 

[theconsolegamer]

Yes, and run them on all slots one stick at a time and in dual mode on both channels now that you're at it.

 

[joeb361]

All slots?
So, one stick in all 4, then repeat for the other one, then dual mode in the 2 spaces.
For how many passes?
This might take a long time :O Takes me about 1 hour 30 mins for each pass

 

[joeb361]

Just got another bluescreen. It said 'MEMORY MANAGEMENT'
Is this to do with ram? I was doing a disk defrag, so it could be talking about a hard drive? xD
This was on just casual computer use, not started the memtest yet

 

[Pinhedd]

Just got another bluescreen. It said 'MEMORY MANAGEMENT'
Is this to do with ram? I was doing a disk defrag, so it could be talking about a hard drive? xD
This was on just casual computer use, not started the memtest yet

Yeah memory management is memory related

 

[theconsolegamer]

Download OCCT software from here http://www.ocbase.com/index.php/software/20-occt

Install OCCT then shut down your PC. Don't forget to turn off the PSU switch to off ( or O from I) and then take the cable off the PSU.

Don't forget to discharge yourself BEFORE touching any RAM sticks.

Grab just one stick of RAM put it in the first slot from left to right, go into windows and run Linpack with the custom 90% of memory and let it run for 10 minutes. If there's no problem then go with the same stick on the next DIMM slot and repeat the process on all slots with just that stick if all goes right then do the same with the other stick all over again. Don't complain just do it.