Had voltage at vcore 1.40 for 460MHz... mch at .2v, fsb at .2v and memory at +.4v (2.2v)... no go.Quote:
Originally Posted by Bromptoners
Printable View
Had voltage at vcore 1.40 for 460MHz... mch at .2v, fsb at .2v and memory at +.4v (2.2v)... no go.Quote:
Originally Posted by Bromptoners
I have a new option in this BIOS called HPET support, what the hell is this and do I want to disable it or keep it enabled? My options for the are 32bit mode, 64bit mode, or just disabled.. Thanks
This has been debated previously. As usual opinions split. It was thought that using a USB mouse or keyboard caused hitting the OC wall and the solution was to try a PS/2 mouse and keyboard to see if it makes a difference.Quote:
Originally Posted by davidos
Maybe worth a try
cheers
I'm using a USB wireless Microsoft mouse and I can hit 3.4 with my 6300 so it's not that. I am using a PS2 keyboard. This is with the F7 bios.
You can disable it.Quote:
Originally Posted by newls1
here is some info on it if you care..
http://softwareforums.intel.com/ISN/.../30225022.aspx
Short version: Although one-millisecond resolution and aperiodic functionality are theoretically possible using todays timer hardware, achieving this level of granularity and taking advantage of this functionality while maintaining reasonable system performance is not possible in reality. To make this level of resolution and functionality realistically possible, a new timer is needed that replaces the legacy timers used currently. The new High Precision Event Timer (HPET) was designed to have very fine-grained resolution, fast access times, and support for aperiodic behavior.
A Very good read on it is at MS.
http://www.microsoft.com/whdc/system/CEC/mm-timer.mspx
Short version:
The High Precision Event Timer
The High Precision Event Timer (HPET) was developed jointly by Intel and Microsoft to meet the timing requirements of multimedia and other time-sensitive applications. Originally, the HPET was called the Multimedia Timer (MM Timer), but the name was later changed to avoid confusion with a Microsoft DirectX timer, and to better describe the timer.
Benefits of the HPET
Experiments on prototype HPET hardware by Microsoft Test Engineers have shown that, in addition to extending the capabilities and precision of a system, the HPET also improved system performance.
In a test that compared the performance of the HPET to that of the PM clock, a function that called the usermode QueryPerformanceCounter() API 1000 times was executed and timed. To ensure the results were comparable, the test was run multiple times on a single system. A similar test was run using the kernel mode KeQueryPerformanceCounter() API on the same hardware to identify the kernel mode benefits of the new timer. Table 1 shows the results of these two experiments.
Table 1 Comparison between HPET and PM Clock Performance
Benchmark1000 consecutive [K]QPC calls PM Clock[calls/ms][µs / call] HPET[calls/ms][µs / call] Perf Increase using the HPET
QueryPerformanceCounter()
6301.59
7841.27
24%
KeQueryPerformanceCounter()
11940.84
19200.59
61%
This data shows that reading the timestamp from the HPET is more efficient and faster than with legacy timers. However, because of the fine level of resolution needed for measurement, the actual performance benefits of the HPET and their implications on applications are impossible to quantify.
Quote:
Originally Posted by Bromptoners
NO do not do that.
+6 and +7 is 2.4v and 2.5v vdimm and that is stupid.
unless you know for a fact your ram can handle it. and only with a fan blowing over them
Thank you for the quick reply.. Ok so your saying disable it right? I read what you wrote, but still dont understand it. Would you disable it? or would you leave it enabled? Could this affect my OC at all?Quote:
Originally Posted by markopoleo
You can disable it, i would. It is one of those "useless but could be good in the future" options they added. I don't think it effects OC ability, but you can try with on or off to test if you want :P
nevermind.Quote:
Originally Posted by ferds
I do not know yet, trying to get some user inputs on the BIOS now. So far I have hit anywhere from 485~510 with it depending on the CPU type. It appears the Allendales are clocking under the Conroes now so additional tuning is needed but the goal is to get everyone to 490FSB with the BIOS before addressing any further issues.Quote:
Originally Posted by markopoleo
I just had a new experience!:eek:
I flashed to F8i and tried to up my fsb using my 805 and ocz memory. My choice of fsb caused my computer to go into a continuing restart with the message on the screen that it was looking for bios on hard drive and trying to recover. Eventually it recovered to F6 (my previous bios was F7) and I was able to flash to F8i again.
In about 10 hours I'll install my E6400 and D9 memory and see what happens.
Bingo...any beta for the DQ6?, because F7 sucks lemons.
When I get a chance to try the bios on my S3 tonight when I get home in about an hour I'll let you know how the Allendale works with some OCZ D9 ram. Hopefully I'll get past this 450 wall. :)Quote:
Originally Posted by bingo13
Update: Tried the F8i bios, jumper reset the bios. Went reset all my settings, tried to go past 450, still can't. Same wall. 475 causes it to shut down and reset itself like 3 times, 460 just resets the bios.
Gigabyte just sent me the F8E bios for DS3 will try this one and the F8I when i get home from work later
The memory module I'm currently using is Corsair DDR2 800 , 1GB module.. I'd pumped it up the vdimm to +0.6v (2.4v) no additional fan blowing over on it.. still working fine.. The only difference is the CPU, I'm using E6700.. it's that the reason why I can reach such high freq??Quote:
Originally Posted by Lestat
the f8i bios did indeed help me. i just flashed it and in order to test if the d9 problems were fixed, or at least improved on, set the 2.5x divider and lowered fsb to 400, just for testing. previously, i was not able to post at ddr2-1000 (crappy timings, but still, better than not posting with crappy timings) but now i'm running memtest. so far i't sbin a minute without errors.
i'll report back with more results. i really need to lap this cpu :( 55-60c idle with water. the base of the wb is barely warm.
UPDATE
2.5*450 done! unstable, 5-5-5-11, 2.3v. ddr2 1125, e64@3600, superpi1m=16.0s
currently testing stability at 450*8 with ddr2 at 900 with 4-4-4-10 2.1v
Helped me ...
Yeah they're doing something right.
I just flashed to the F8i bios and can get my OCZ gold ram up to 402 right now, thats just the first fsb i put in. I couldnt evev POST above 360 with this ram on any other BIOS. Does anyone know what mem chips are in the gold sticks of OCZ?????
Hmm, tested F8i BIOS, its is a little bit better than F6 for S3, flashed S3 with DS3 F8i BIOS and all works fine as it looks :D With F6 I was able to do 480 x 6 SuperPi 32M stable, but now I can do 490 x 6 SuperPi stable, hope I will be able to do 486FSB for 24/7 setings, it would be nice to have E6300 @ 486 x 7 = 3402 or a little bit more :banana:
And I realy like, that its posible to add +0.7v for DDR2, so its posible to get 2.5v without vmods :)
I cant really OC better, but the damn XF-i bug is gone
It seems as though this new BIOS dropped my AQ3 score 1200 points:mad: . I cant understand why. Anyone else have this issue?
Would it not be safe to run my Gskill HZ ram @ 2.3Vdimm (+5 setting) im thinking if I could run it at that Vdimm, I might be able to scale higher keeping 4/4/4 timings.
I hope there will be more new bioses for DS3 and S3 boards wich can overclock even more, I like F8i, here is my first result with Team PC5300 D9GMH @ 2.2v DDR972 4-4-4-12 and E6300 Allendale @ 3.4Ghz with BOX air SuperPi 32M stable :D Now I will try to lover vcore, but 1.4v in BIOS is ok I think for 3,4Ghz. Boots fine with 490FSB from BIOS, but looks like no more :(
http://foto.apollo.lv/files/Kashelz/large/318746.jpg
And cliffy - maybe we can get F8E bios for DS3 too? Really want to test it, not far from 500FSB at the moment :p: What else we can do to get higher FSB? Maybe some hardmod?
Sorry if I missed it in a previous post, but how are you measuring temps? because there's like a 10 degree difference between what the motherboard reports for CPU temp and what the CPU's internal sensors report, I think Intel would be recommending ~60c as read by the mobo and not the latter... see screenshot (max temp @ max CPU load, stock speeds)Quote:
Originally Posted by markopoleo
http://i12.photobucket.com/albums/a2...stock-load.gif
i also like this new F8i bios. i can now boot with 490fsb unlike before 485fsb using f7 bios.