Sign in with
Sign up | Sign in
Your question

Prime 95 ERROR:rounding was 0.5 less than 0.4 and hardware failure det

Last response: in Overclocking
Share
January 29, 2013 1:28:37 PM

Hey, Iv recently strated running prime 95 to try and pass it at the 24 hour mark but it always stops and sais "rounding was 0.5 less than 0.4" and sometimes itll even say "hardware failure detected consult stress.txt file" now, iv run memetest successfully foe 25 hours with both my 4 gig sticks in. Iv heard that you should bump up your vcore if it fails which i did up to 1.240v (and i believe the max 'safe' voltage for the i5-2500k is 1.35) but if i keep raising my vcore wont prime 95 keep detecting and error? some advice would be greatly appreciated



Build:
i5-2500k
2x4gig corsair vengeance lp 1600 ram
hyper 212 evo cpu cooler
gigabyte z68xp-ud3p motherboard
gtx 660ti gpu
850watt corsait psu
February 7, 2013 6:25:33 PM

I can't say for sure as I am also a newb to Overclocking but as I posted in my post this afternoon (http://www.tomshardware.com/forum/283440-29-3750k-5ghz-stable-advice-opinions) I achieved 5ghz on a i5 3570k with some high end components and good Watercooling kit.

Now just yesterday I got an error similar to yours while running Prime95 at the 5 hour mark saying "FATAL ERROR: Rounding was 0.4965515137, expected less than 0.4
Hardware failure detected, consult stress.txt file." on my 3rd core.

I then proceeded to up the vcore 0.005 volts. then ran Prime95 again for 12 hours and got no error at all. So I have a feeling your missing a bit of voltage on vcore. It could be because of something else also.. really I don't know I'm still an OC noob. But my friend who has OCed 5-6 rigs already said to bump the vcore a bit, so I did and now it's fine.
February 8, 2013 12:41:38 PM

it just means that your overclock unstable ;p reduce multiplier or increase volts ;p
Related resources
February 10, 2013 2:17:11 PM

krang said:
I can't say for sure as I am also a newb to Overclocking but as I posted in my post this afternoon (http://www.tomshardware.com/forum/283440-29-3750k-5ghz-stable-advice-opinions) I achieved 5ghz on a i5 3570k with some high end components and good Watercooling kit.

Now just yesterday I got an error similar to yours while running Prime95 at the 5 hour mark saying "FATAL ERROR: Rounding was 0.4965515137, expected less than 0.4
Hardware failure detected, consult stress.txt file." on my 3rd core.

I then proceeded to up the vcore 0.005 volts. then ran Prime95 again for 12 hours and got no error at all. So I have a feeling your missing a bit of voltage on vcore. It could be because of something else also.. really I don't know I'm still an OC noob. But my friend who has OCed 5-6 rigs already said to bump the vcore a bit, so I did and now it's fine.


Thanks for the reply, iv been doing bumping up the vcore by 0.010 every time it fails (im at 1.280) so i just gonna keep doing that for a bit and hope for the best, if only my first build could have gone more smooth :ange:  :ange: 
February 10, 2013 2:18:12 PM

amateur1337 said:
it just means that your overclock unstable ;p reduce multiplier or increase volts ;p


im working on it! :sol: 
May 4, 2013 5:35:13 AM

krang said:
I can't say for sure as I am also a newb to Overclocking but as I posted in my post this afternoon (http://www.tomshardware.com/forum/283440-29-3750k-5ghz-stable-advice-opinions) I achieved 5ghz on a i5 3570k with some high end components and good Watercooling kit.

Now just yesterday I got an error similar to yours while running Prime95 at the 5 hour mark saying "FATAL ERROR: Rounding was 0.4965515137, expected less than 0.4
Hardware failure detected, consult stress.txt file." on my 3rd core.

I then proceeded to up the vcore 0.005 volts. then ran Prime95 again for 12 hours and got no error at all. So I have a feeling your missing a bit of voltage on vcore. It could be because of something else also.. really I don't know I'm still an OC noob. But my friend who has OCed 5-6 rigs already said to bump the vcore a bit, so I did and now it's fine.


Thanks for the reply, and ya i get that same error as yours as well sometime, and iv also had my vcore up to 1.4 with the same result :/ 

!