LinX error

setter

setter

setter

Caporegime
Joined
14 Dec 2005
Posts
28,067
Location
armoy, n. ireland
Been running LinX on my oc'd i7, with all ram selected, (4206), problem size 23428, first i was running the following.

21x193
1547 mhz ddr3
pcie freq, 101
cas 7-7-7-24
uclk, 3095 mhz
qpi link, 6965 mt/s
1.2750 vcore
1.312500 qpi
1.66 vdimm
1.84 pll
ioh, 1.2
ioh pcie, auto
ich, 1.2
ich pcie, auto

Tried today with 20x200, vcore raised to 1.28125, ram at 1600mhz, 7-7-7-24

uclk, 2208 mhz
qpi link, 7218 mt/s

All other voltages as above, ive ran LinX/IBT on the first settings, (21x193) in the past, however though i had a lesser amount of ram selected.

Previous passed ss.
linx40-Copy.jpg


Failed ss
linxfail.jpg
linxfail2.jpg


Cpuz cpu + ram settings.
cpuz20x200.jpg


Thanks for any advice/input.:)
 
Last edited:
The first set (21 x 193) were tested for 5 hrs ono error free with blend. Just a few mins ago i tried LinX again with memory lowered to 4096, same error.

EDIT: Ran blend on the 20x200 settings, worker thread 5 error after 3 minutes, ram voltage is set at 1.66v, which should be ok, will try another bump on qpi voltage. Increased qpi voltage from 1.312500 to 1.31875, blend running error free so far. Scratch that, worker thread 8 failed after 9 mins.:( Raised qpi to 1.32500, failed on thread 4 after 7 minutes.
 
Last edited:
Could this be a case of more qpi? The 1.2750 vcore settings at 21x193 have been tested for 8 hours stable with p95 small fft and various passes of IBT/LinX a while back. Currently trying 20x200, small fft, 1.28125 vcore, running almost an hour error free.
 
Id say it may be a mix of both vcore and qpi, can't see why a stable clock all of a sudden starts acting up really, but yeh maybe a bumb in vcore may help
 
Thanks, currently running vcore at 1.28125, qpi at 1.32500, small fft is fine so far on theese settings, decided to start running at 20 x 200 so as to get a little more from my ram, hence the testing, blend fails on every attempt so far.
 
Or Fold on the cpu, if there are no freezes, lock ups, crashes, BSOD's when doing that then its 100% stable, even more so then prime lol.

Hope the testing goes well though setter, i know from experience how annoying it can be, i had a 24 hour prime stable clock that used to now and then freeze when folding, notch up on qpi and vcore sorted that for me.
 
I'll also add that the 20 multi might be causing the issues.
I found going from 21x191 to 20x200 needed a fair bit more vcore.

I would also try lower ram speed or loosen the timings just to test to confirm that its ram related.
 
Yep, ill have another mess about with it tomorrow. Tbh, it's stable enough in anything im using it for, mainly gaming and a bit of video encoding. The only crashes/freezes etc ive ever had are caused by my rubbish usb wireless adapter, what is the max reccomended on qpi for 24/7 use?

@game4it, im currently running the ram at 1.66v, 1T, 7-7-7-24, what should i slacken timings to? Thanks guys.
 
Last edited:
setter said:
Yep, ill have another mess about with it tomorrow. Tbh, it's stable enough in anything im using it for, mainly gaming and a bit of video encoding. The only crashes/freezes etc ive ever had are caused by my rubbish usb wireless adapter, what is the max reccomended on qpi for 24/7 use?

@game4it, im currently running the ram at 1.66v, 1T, 7-7-7-24, what should i slacken timings to? Thanks guys.
Click to expand...

I think max qpi/vtt is 1.375v or 1.35v for the 920's but i'm sure the guys here will comnfirm that its right or wrong ;)

As for ram i would try 9-9-9-27-2t or lower the ram multi and run test.
If it passes you know that the 20x200 is fine and dosen't need tweaking.
If not then you need to tweak other settings.
I find its best to get cpu overclock stable first then bring ram up to speed and tighten timings.

So if you pass tests and cpu OC is fine you will need more qpi.Your ram volt are high enough as is.
 
Thanks, the 20x200 settings ran ok for an hour and a half with small fft before i stopped it, bit of a short run i know, will have to let it run a bit longer. Ill also have a play about with the ram timings etc.
 
Bit of an update. Finally found time to have a tweak with settings. Upped vcore to 1.28750, slackened the ram to 9-9-9-27, (previously at 7-7-7-24), 1.66 vdimm, 1.325 qpi. Running prime blend for almost 2 hours error free so far.

prime95bl.jpg


Gonna let it run for another few hours, if all's well ill attempt to lower the ram timings again.
 
Thats next on the agenda, providing of course that blend runs for a minimum of 8 hours, havent had any bsods when previously running p95 blend, just individual worker threads failing after a certain amount of time, anything from 2 - 10 minutes.
 
setter said:
Thats next on the agenda, providing of course that blend runs for a minimum of 8 hours, havent had any bsods when previously running p95 blend, just individual worker threads failing after a certain amount of time, anything from 2 - 10 minutes.
Click to expand...

Then your overclock isn't stable if it is failing some of the threads.
 
Thankfully so far this evening it's running a lot longer than its ever done, (2hrs 30 mins and counting), used to run the cpu at 21x193, ram downclocked to 1547mhz, recently changed to 20x200, with ram at 1600 mhz, (ocz reaper c7).
 
Scratch that one, failed on thread 7 after 5 hours.:(

prime95blf.jpg


FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
 
Last edited:
Unstable.

Trust me, Linpack (Linx/Intel Burn Test) will find instability in minutes, not hours. Gives you more time to tweak.

Can't help you diagnose the BSOD I'm afraid - not my vintage :)
 
You must log in or register to reply here.
Back
Top Bottom