Jump to content
HWBOT Community Forums

TerraRaptor

Members
  • Posts

    1959
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by TerraRaptor

  1. Haven't tested. The only way to minimise an impact is setting sensor polling interval to higher value (i use 9 sec interval for sensor readings).
  2. Almost impossible, taking @Luumi's score of 10.45.781 being best 4G run as of now:)
  3. Analyzing first 15 subs give 4 subs with C0 and 11 submissions with E0. So E0 should be better - just keep in mind that you likely miss best cpu if you will only bench it for 32m stability - E0 has higher range of semi-stable fsb clocks. P45 is having cooling issues imho due to open die - stock coolers are of sub-par quality and may not sit tightly on die. I had DFI P45 that wasn't able to accept anything over 1.45v - then I glued IHS on NB and it became way better. So cold NB seems to be the key for P45. I have also run into strange issues with 32m stability with ddr2 boards - they won't do over 618-620mhz 32m 1:2 (I have tested Rampage Formula and DFI P45-T2RS). Pretty strange both boards hit the same wall (and cpu was definitely not the limit - at least 630mhz with 6-7 ddr3 boards). Probably something needs tweaking in mchbar (use baredit etc). Just my experience - my best board is capable of running large waza (3-4GB) @666mhz. But even 1M goes bluescreen/"not exact in round". I think that it is cpu issue if board is capable of waza but fails tests stressing cpu-nb link.
  4. 1. Hi. Normally, VTT won't give you any noticable gain - one cpu will do FSB 650 in 32m with 1.44-1.49v vtt, another one will hit the wall at 630 with same voltage and raising vtt to 1.7v won't break that wall. Also, some cpus have a very narrow range between full stability (pi 32m run) and valid - just 10-15mhz, others may have that range extended - like 640mhz 32m and 690mhz barely stable to validate (but yet 50 mhz difference). I would say C1 stepping is first category, E0 is second category. CPUs are also extremely sensitive to GTLs. So I would bin cpus for fsb validation if that is the goal. I had just a couple of good cpus that would break 690mhz, both were trying to post with air cooling @670mhz. Very important thing to consider - push Vcore for fsb. I needed >1.7v to get 700mhz although core clock was 4.2ghz. 2. Biostar t-power p45, giga ep45t-extreme, rampage exteme (8x serials). There is a chance with P5e3 x48, p5e64 evo. DFI is really annoying, ate all my patience yesterday - so I won't recommend it (though board is still worth mentioning here). 3. Boards run into a kind of wall with fsb, I wouldn't count Vnb as important factor - while it scales, who cares of volts? My safe limits are 1.82v and 45C idle temps. 4. VTT - normally every cpu has a sweetspot, 1.45-1.55v. Vref (aka GTL) should be 0.61-0.65 of VTT, depends on cpu. Vpll - keep it low, high values are killers for 45nm anyway. I have an impression that Vcore should be higher than vtt with a margin of 0.15-0.2v all the time. NB vref is a kind of unknown for me yet, but looks like p45 needs it to be x0.58 of vtt, x48 will need higher values (0.63-0.65).
  5. Epic is 666, hope to see it from you 500x8 is interesting yet we have many of these.
  6. https://hwbot.org/benchmark/pyprime_-_2b_with_benchmate/ Can be downloaded at https://benchmate.org/ - Offline installation
×
×
  • Create New...