MMM
Results 1 to 25 of 727

Thread: Foxconn Quantum Force Black Ops X48 OC Guide (56k Warning)

Threaded View

  1. #11
    Xtreme Addict
    Join Date
    Mar 2008
    Location
    UK
    Posts
    1,083
    Hi gmcg.

    I actually got this system from a gaming pc company here in the uk, i don't have the WC know how or time right now to do an elaborate build myself, but this WC system is i guess you could say 'professionally' done.

    I can tell you the following specs: D-Tek Fuzion CPU Block, Thermochill Triple Radiator (i thought it was a 320mm rad but i take it that is the same as a 120mm tripple rad), Laing DDC 12v with Modded Plexitop, 6 x 120mm Xilence Fans, 2.5 Metres of Tygon 1/2" Tubing. They also machined a new top for the NB block, it's delrin. Sorry if this isn't enough info.

    What would make you think i have a temp problem though? My temps don't actually change (noticably) between 1.39v 3.8ghz and when i'm testing 1.44v 4ghz - i idle at 32c and load generally at 55-58c, it peaked at 61c during prime yesterday and it was a very hot day! I've read of people running this chip safely in the 60s and even 70s so i was thinking these temps were not bad.

    Also not sure i completely understand 'controlling' my temps during the test, if you just mean what do i use to monitor, i use Realtemp for the cores and Everest for the NB, which peaks at 44/45, 46/47 on a hot day (on 1.5-1.6v)

    I've been continuing GTL tests, here are my results from yesterday, continuing from the last one i done which was +2 +2 +2 +9 - core 3 and 4 fail both in 34 mins:

    +2 +2 +3 +10 - core 3 fails in 10 mins

    +2 +2 +1 +10 - core 4 fails in 31 mins

    At this point i wondered if tweaking core 2 might affect core 4 because of the way they are on the die, so i tried changing that

    +2 -3 +1 +10 - core 4 fails in 18 mins

    +2 +1 +1 +10 - core 4 fails in 31 mins

    It did change the time to fail, didn't fix the problem though

    +2 +1 +1 +11 - core 4 fails in 20 mins

    +2 +1 +1 +13 - core 4 fails in 32 mins, core 1 fails in 34 mins

    +2 +2 +1 +14 - core 3 fails in 32 mins, core 4 fail 34 mins

    +2 +2 default +15 - core 4 fails in 17 mins, others stable for 1 hour+

    +2 +2 default +16 - core 4 fails in 20 mins, core 1 fails in 34 mins

    default +2 default +17 - core 4 fails in 32 mins

    default +2 default +18 - core 4 fails in 9 minutes

    default +2 default default - core 4 fails in 32 mins, core 1 fails in 2 hours

    +3 +2 default -1 - core 4 fails in 17 mins, core 1 fails in 34 mins

    +1 +2 default -2 - core 4 fails in 18 mins

    And the run i started before i went to work today:

    +1 +2 default -3 - core 4 fail 22 mins, other cores stable 8 hours+

    So as you have noticed the 'successful' runs have all had steady fail rates at 32-35mins, i don't know what to make of that though, i'm out of my depth here i just hope the recording can help someone come up with a theory!

    Thanks again.

    :update:

    My runs this evening:

    +1 +2 default -4 - core 4 fails in 1 min

    +1 +2 default -5 - core 4 fails in 5 mins

    +1 +2 default -6 - core 4 fails in 33 mins

    +1 +2 default -7 - BSOD after 20-25 mins, INTERUPT_EXCEPTION_NOT_HANDLED

    +1 +2 default -8 - core 4 fails in 18 mins, core 1 fails in 37 mins

    As you can see, core 1 was stable for over 8 hours on +1 +2 default -3, yet it failed in 37 mins on +1 +2 default -8, and it had the same GTL value both times. I guess this means that adjusting the GTL value for one core can affect other cores, and if that's true this could take years

    :further update:

    Well i caved in and started upping my core voltage.

    Changes:

    vcore from 1.456(1.44 actual) to 1.467(1.458 actual)

    default default default default - core 4 fails after 32 mins

    +10 +5 +10 +10 - core 4 fails after 33 mins

    vcore from 1.467(1.458 actual) to 1.487(1.47 actual)

    default default default default - core 4 fails after 2hr 42 min, others stable 8hr+

    Finally some progress i thought, but isn't it rather insane that i can get a completely stable 3.8ghz at a mere 1.39v, and for simply 200mhz more i'm having to go above 1.47v?

    I upped it once again from 1.487(1.47 actual) to 1.5 (1.48 actual). I hope someone will answer my question from before:

    Quote Originally Posted by Xello View Post
    If temperatures are fine with those voltages [ like the 1.48 i'm at ], is it safe to be there? Or is it possible for your temperatures to be great but for that voltage to kill your cpu anyway.
    At 1.48v My idle temperatures are still 32-35c, and load is still between 50 and 55, peaking at 60 today.

    Basically, what do you go by for judging the safety - the temps or purely the voltage?

    Take at look at this too:

    http://img.photobucket.com/albums/v4...estar/2334.jpg

    I noticed that cpu-z is reporting my core voltage approx nearly 0.4v lower than it actually is. It's version 1.46, is it just an error in the program or do i have a more serious problem? HWmonitor also reports 1v~. Also, might be worth mentioning that core 4 is always 5-10 degrees lower than the other cores. I'm sure it has always been like that, so i didn't see it as a problem - seen as core 4 is the one dropping out all the time though is this maybe something to do with that?

    Thanks.
    Last edited by Xello; 08-07-2008 at 01:40 PM.
    TJ07 | Corsair HX1000W | Gigabyte EX58 Extreme | i7 930 @ 4ghz | Ek Supreme | Thermochill PA 120.3 | Laing DDC 12v w/ mod plexi top | 3x2gb Corsair 1600mhz | GTX 680 | Raid 0 300gb Velociraptor x 2 | Razer Lachesis & Lycosa | Win7 HP x64 | fluffy dice.

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •