Why didin't use just use a pen drive and EZ Flash? It's a cakewalk.Quote:
Originally Posted by WeeMaan
Printable View
Why didin't use just use a pen drive and EZ Flash? It's a cakewalk.Quote:
Originally Posted by WeeMaan
http://img32.imageshack.us/img32/323...tablealfin.jpg
oc for 24/7 ... dangerous??
Temps:
idle 44º
works mediums, games 60º
Full all cores at 100% only with stres programs 80º
can not get minor vcore stable with Intel burnTest or Linx .. :(
This BETA bios is :banana::banana::banana::banana:ing rulez!!!!
I run stable 1h prime95 at 4200mhz with only 1.225vcore!
Before i have to use 1.248 to get stable this clocks...
=)
Another test... now testing the limits of this board >=D
http://img521.imageshack.us/img521/8...ck4763mhzc.png
What? Does that work for the v2 to?Quote:
Originally Posted by Classic Satch
I was under the impression it did'nt work? :confused:
I'll try that later.
I don't see why it wouldn't. It's a basic feature and couldn't be easier to use.Quote:
Originally Posted by WeeMaan
in bios set the "USB Legacy" to EnabledQuote:
Any BIOS newer than 1206 won't let initialize my USB keyboard (Logitech G15) during POST so that I cannot enter the BIOS settings...
this way i haven't any troubles with my G15 on Deluxe and P6T WS
vas have troubles early with P5E64 WS PRO... (year ago). but the keyboard initialized if i press RESET or if i press keys on it before and during the post...
on P6* series i haven't this trouble - all works fine. My G15 is the first blue led revision.
Yeah it doesn't work. "ROM ID in the file is incompatible with existing bios."Quote:
Originally Posted by Classic Satch
Any other suggestions in how to get the keyboard working in dos?
I really want that 0006 bios. :up:
WeeMaan
buy cheap PS/2 keyboard - just for "backup" and any such situations ))really helps ;)
I have plenty of them, the problem is that I just moved into a apartment (in another country) and still have them in my house along with all other old PC junk.Quote:
Originally Posted by Gre4ka
If there is no fix then I'll jsut have to buy some random PS/2 keyboard, but I rather not (since I already have ton of them).
Wow men, this batch of my its simply rulez!
4200mhz with only 1.224 Vcore! :shocked:
I think i gonna try more lower vcore :yepp:
http://img266.imageshack.us/img266/2...rei7920420.png
Feel like selling me that one? :p: It takes 1.37v to hit 4.2Ghz on my C0.Quote:
Originally Posted by SHAFT Brazil
What are your other settings? PLL, QPI, NB etc?Quote:
Originally Posted by SHAFT Brazil
Okay, I got the keyboard working. But the command does not work?Quote:
Originally Posted by WeeMaan
I wrote: Afudos /i0006.rom /pbnc /n
I got the Afudos ES and the 0006.rom on the cd that I made with nero, what could the problem be?
It was the A: parameter before but my CD drive is on E:, could that be the problem?
When I type E: it does not find it.
(I'm not an expert on dos as you see, so be gentle on me. :))
Weeman,Quote:
Originally Posted by WeeMaan
you have to use the cd command to enter the path where your afudos.exe tool is located. Either that or both the BIOS filename and the flasher have to have the full path in them. For example:
a:\flasher\afudos /i ....
or:
c:\ a:
a:\ cd flasher
a:\ afudos /i0007.bin /pbnc /n
DOS can hardly guess where in the hierarchy your tool is after all :cool:
And yes, if your optical drive is on E:, you would have to replace the A with an E. But keep in mind that drive letters can change when booting DOS, also due to DOS not recognizing NTFS partitions. See below.
A: and B: usually refer to floppy drives, C: and beyond can be HDs or optical drives. You can certainly put your flasher and BIOS files on your harddrive but this HD partition MUST be FAT 32 formatted. DOS does not support NTFS! Floppies as a medium are stupid nowadays, and CDs or DVDs are stupid too since they're not writable under DOS. Another option would be a USB stick with a bootable DOS to hold the flasher and all possible BIOSses...just in case. Whatever it is, keep the drive letter in mind when changing pathes. In case you want to know which subdirectories there are on your current drive, use the dir command.
To all:
On a side note, I am running BIOS 0007 on my V2 board. But I can't tell if the throttling is disabled, it is a matter of principles to me to have errors straightened out even tho my system might not be affected.
I am currently running my C0 920 at 3.8 GHz, unable to get to 4 GHz despite disabling power saving options.
VCore: 1.26 (200x19, all power saving options enabled!), Vqpi: 1.375, Vpll: 1.80, IOH: 1.34V (Feels faster than 1.26, so I assume that the chipset feels better with more juice)
DRAM: 1.6V, 1200 MHz, 7-7-7-18 Corsair XMS3 sticks. Better than 1600 at CL9 and 1.86V!
Just a quick summary. Maybe it's the most economical spot there at 3.8 and power savings on.
Thanks for taking some time to explain! :up:Quote:
Originally Posted by Amurtigress
Alltough I didn't quite understand it, but I did manage to launch afudos from my NTFS harddrive (some how?) and a fat32 formatted usb drive.
Wich leads to the next problem. ;)
When it's about to flash it comes up 2 warnings that says: "Warning! Out of memory".
Why is that? How do we solve it?
And one more thing, I tryed to switch to the CD by typing "E:" but it says invalid drive, only when I connected my USB drive it worked but I guess the usb drive was on E: then?
I really want the 0006 bios, I've been spending several hours today trying to make it work. :shrug:
Edit: I missed the part where it said ntfs drives wont come up in dos, in that case I launched afudos from CD and USB drive.
Anyway, the only problem now is the "end of memory" warning.
oh no no no :p:Quote:
Originally Posted by Classic Satch
With 1.37 i can run stable at 4500mhz :D
PPL - 1.80Quote:
Originally Posted by WeeMaan
QPI (VTT) 1.268
IOH - 1.18
DRAM - 1.64
Looks nice for you friend? :)
Looks really nice, you got a killer chip there! :up:Quote:
Originally Posted by SHAFT Brazil
very nice.:up::up:Quote:
Originally Posted by SHAFT Brazil
I can only guess what it is. Open the config.sys file (may be hidden) of your boot device (CD, DVD or USB stick) and check for any lines containing himem.sys or emm386.exe. Those twoa re there to enable usage of memory above 1 MB. We are talking about a 8/16 bit OS here that is basically limited to 640 MB of RAM, and despite giving you more memory total, himem and emm386 reduce the available memory below 1 MB. They use it to ahve a "window" of memory that's mapped to RAM above that limit.Quote:
Originally Posted by WeeMaan
Make sure to hold down CTRL just when the OS is booting and it'll give you a menu. Just load DOS without config.sys and autoexec.bat to keep the memory free.
AFUDOS cannot run with any of those memory extensions. Flashers in general can't.
That does not help either. :( I'm short of any plausible explanation what this could be.Quote:
in bios set the "USB Legacy" to Enabled
Should try to write to ASUS tech support, may be they have smth to suggest.
Anyway, thx for the effort. :)
I also had problems with flashing the V1 bios on my V2. I created to and booted to the flash drive properly and using the dir command I could see that I was in the right drive. My problem was that I kept getting an "unrecognized command" error when I tried the afudos /i0006.rom .......
My solution was to type the following:
AFU236U.exe /i0006.rom /pbnc /n
Please note that changed the name of rom to 0006.rom before copying over to the flash drive. I only did this for simplicity so I didn't make a typing mistake with the longer original name.
Hope this works for you!
Ugh, folks... you HAVE to type afu236u , not Afudos. That was so obvious to me that I did not even mention it.Quote:
Originally Posted by grogthegreat
<g> Sorry, I've been into DOS for more than twenty years.
You don't have to type the command extension. You can only execute .exe, .com and .bat files. Which means, type their name with or without the suffix. Other commands like CD and dir are internal commands of DOS and don't appear in any directory.
Hell yeah men!Quote:
Originally Posted by WeeMaan
Im just imprecive with my core i7, i got OCCT stable for 1h with only 1.216vcore @ 4200mhz
:shocked: :cool:
God dammit i love my ci7 :p:
Yes, that was not my problem. I did type whatever I've named it to.Quote:
Originally Posted by grogthegreat
But thanks for sharing.
I will try Amurtigress solution later on today.
Edit: There is no config.sys file on the cd, and holding ctrl during boot doesn't work either.
Got any other suggestions? :)
Shaft, your english is very very fu***** bad! Why don't u use the translator? At least they can understand you by doing that...
Shaft:
Shaft, teu ingles eh ruim pra kct... tenta usar o tradutor antes de postar... os caras devem ficar rindo de ti! KKKK
:rofl::ROTF:Quote:
Originally Posted by McBacker
@ SHAFT Brazil
Indeed a sweet CPU you have :up: could you share the batch number on that?
That's why he asked my i7 batch before buying his one... he was after a chip with the same batch like mine, 3845A687 :DQuote:
Originally Posted by NBF
Like u Backer? :rofl: hahaha its just fine man...be coolQuote:
Originally Posted by McBacker
Still need help with the P6T little noob? :rolleyes::rofl:
Thanks NBF :DQuote:
Originally Posted by NBF
My batch is 3845A687
...Did i know u? :ROTF: KKKK
Does any one here gets more than 229 bblock on this board? :confused:
Thats right!Quote:
Originally Posted by japamd
I was impressed when i see your overclock test with this batch :cool:
Luck of mine get on of those :D
Can someone please tell me exactly how you did to flash the 0006 and I'll try to start from the beginning.
How come no one else but me has had the "Warning - Out of memory" issue?
I really want the 0006 bios but I'm about to give up, been spending way to many hours on this now. :shrug:
Edit: Fixed!
I now have 0006 up and running, I have not noticed any overclocking improvements becides the turbo issue resolved (which is good).
I have a rather annoying issue, I can't use speedstep, C1E or C-State when I'm using the 21x multi and 4+ ghz.
With the v2 bios 0504 (and all previous) it gave me a BSOD when the Windows logo came up, now with the 0006 bios it freezes when the logo comes up.
If I turn of the powersaving feautures it is rock stable.
Anyone had simular problems? Can it be fixed?
Edit 2: Okay, I'm ditching the 0006 bios after all. I get BSOD "system_service_exception" on settings that have been stable before.
The turbo throttling issue did not go away either, it drops to 18-19x once in a while.
Sorry to hear that you ran into so much problems WeeMaan. I just flashed my board to 0006 and it went really smoth. I'll post later on about throtteling results.
Yeah, it's a shame when I spent several hours trying to make it work.Quote:
Originally Posted by JoBu
But atleast I'm one experience richer, now i know.
The multi even drops down to 15 sometimes now, don't now if it's because of the 0006 bios or not.
You think itäs worth trying the 0007 bios or is it about the same?
Might be worth a try. What CPU are you using?
Since I flashed to 0006 i got mem and qpu-ratio settings added to my BIOS. According to funkypunk I will lose these settings again if i flash to 0007 but maybe it will help with the throtteling issue. Anyhow will do some OC first to try 0006 out.
I'm using a i7 920 D0, I have not noticed any other change in the bios except for the SAS option.Quote:
Originally Posted by JoBu
I'll give it a try, if it doesn't work then I go back to 0504.
That has nothing to do with turbo throttling. If your multiplier is dropping at idle and you don't like that then make sure your Control Panel -> Power Options -> Minimum processor state is set to 100%. That might help. On some boards, turning off EIST in the bios doesn't actually turn EIST off. i7 Turbo will report the true state of EIST.Quote:
WeeMaan: The turbo throttling issue did not go away either, it drops to 18-19x once in a while.
Without a stable system and without some proper testing, I think it's a little early to jump to the conclusion that 0006 doesn't work. It has been proven to work for many happy users here. When you change to this bios version, it's not unusual to need some slightly different settings including more vcore.
It does not give me that option in Win7 build 7600 when I have speedstep (eist), C1E and C-State off.Quote:
Originally Posted by unclewebb
And it is 10h Prime stable now, alltough the multiplier jumps between 15 and 22 once in a while.
And just to clearify, I am not saying 0006 doesn't work! Obviously it does work for many users here, just not for me. ;)
Edit: And it is ofcourse in 100% load that it drops.
The reported multiplier can get a little jumpy on some motherboards when running monitoring software that samples a lot of voltages. HW Monitor and Everest sometimes cause problems.
I know ben805 had to raise his core voltage with bios 0006. When the turbo was throttling and dropping down to 20X at full load, it obviously didn't need as much core voltage to remain stable. With bios 0006, his multiplier was now steady at 21X at full load so extra core voltage was necessary to remain stable.
I think EIST has to be enabled to get the Minimum processor state option available in the Power Options. If you can't boot up with that set then I understand that's not an option for you.
Yes I know som other software can cause misreadings, I read alot in this and the i7 turbo throttling page where you explained this.Quote:
Originally Posted by unclewebb
So I have only prime, realtemp, cpu-z and turbo v8 or the other turbo software you made on when I am monitoring.
But it looks like it din't need a voltage bump after all, if I reduce QPI / Dram voltage with .025v then it works out OK.
Infact, I am testing now with slightly lower vcore (with the reduce in qpi voltage aswell) and Prime has managed 1½ hour now.
So perhaps the bios wasn't that bad afterall. :up:
But are you saying that the turbo throttling issue can be because I have speedstep off, and because of that can't change the powersaving settings? :confused:
I have always assumed that the setting is not there because you can't turn it on when speedstep is disabled.
Lower vcore is a good thing. What MHz are you testing at?
Post a piece of the i7 Turbo log file if there are any multiplier drop outs observed.
Post a screen shot of i7 Turbo V8 at idle. With EIST turned off in the bios and no way to adjust the Minimum processor state, I'm not sure what this is actually set to by default. It might be different from one board to the next. Some boards need EIST enabled for turbo mode to work correctly. Now that your combo is running more stable you might be able to enable EIST in the bios so that you can have some control over your Minimum processor state.
I'm going to take a wild guess and say the turbo v8 isn't really working correctly.Quote:
Originally Posted by unclewebb
Or is this common?
http://pici.se/pictures/YPDsXjMAE.jpg
Edit: This picture is taken only seconds after I started the v8 program, so no throttling has yet occured.
Will take pic of that later together with the log.
I hope it's not common. :(Quote:
I'm going to take a wild guess and say the turbo v8 isn't really working correctly.
Or is this common?
Looks like a big bug to me. At least 3 of your 4 cores look correct.
Maybe I can blame this on Windows 7. :)
On most motherboards at full load, the results are very consistent. PM me a big chunk of your i7 Turbo log file so I can have a closer look. If you copy and paste it into a message just use the code html tags before and after the data enclosed in square brackets [] like this:
[codeX]
paste data in here
[/codeX]
Remove the X in the html code tags. This will make it easier for me to have a look.
You can also upload the log file to somewhere like SendSpace and send me the link.
Edit: I made a quick update to i7 Turbo V8. It should show up as version 6.3.
http://www.fileden.com/files/2008/3/3/1794507/Turbo.zip
Hopefully this tool can show you if your multiplier is steady at 21 or not.
One random value can be ignored but continuous multiplier values below 21 is a good sign of turbo throttling. If there is a problem, I like looking at the log file to get a more accurate picture of what's going on. If you continue to get random values then try turning off CPU-Z and see if that makes a difference. I haven't had any feedback yet on the newest version (1.52) of CPU-Z and how it effects i7 Turbo.
I got some data for you.Quote:
Originally Posted by unclewebb
This log is done with 4.2ghz @ 1.3v cpu, 1.3v qpi. Speedstep ON in bios (it worked some how), minumim state set at 100%.
I'm using Win7 build 7600 (RTM), the only programs that are on is realtemp, prime95 and turbo v8 6.3.
http://www.sendspace.com/file/rvm1nj
Here is a old one with about the same except speedstep OFF in bios, + cpu-z running and Turbo v8 6.2.
http://www.sendspace.com/file/w2gt2r
If you need any more then let me know what settings etc you want me to use.
And by the way, perhaps it would be good to att an option for showing all 4 cores in the log just like in the program itself?
Thanks WeeMaan. I've had a close look at your data from i7 Turbo 6.3 and I think I understand where those occasional glitches are coming from.
First of all, there are absolutely no signs of turbo throttling. Your multiplier is rock steady at 21.000 at full load like it should be.
As much as I hate to admit it, I believe the glitches are being caused by RealTemp 3.00. If you use RealTemp 3.30 instead then I think your i7 Turbo V8 multiplier results will be 100% steady.
http://www.fileden.com/files/2008/3/...alTempBeta.zip
What i7 Turbo is doing is it is comparing two high performance timers within your CPU. When Turbo is engaged on your system, one timer should be running at 4200 MHz and the second reference timer should be running at 4000 MHz. If you divide those two you get a ratio of 1.05. The default 20X multi multiplied by that ratio (1.05) equals your turbo ratio of 21.0.
The problem is that Intel cheaped out a little bit and these timers are only 40 bits wide compared to most timers within a CPU that are 64 bits wide. A 64 bit timer can count continuously for over 100 years but a 40 bit timer running at 4200 MHz will overflow and wrap around about every 4 and a half minutes. I had a look at the frequency of your glitches and they correspond very closely to when these timers overflow.
Since version 3.00 came out 6 months ago, I've changed how RealTemp handles timer overflow so I hope with version 3.30 you can monitor your temperatures and your multiplier and get excellent results with each program.
Thanks for your help with this and your suggestion to add all multiplier data to the log file. I usually look at the standard deviation column. During actual turbo throttling, this number tends to be very low, usually less than 0.005, which shows that all multipliers are reporting pretty much the same thing. All of your glitches showed a very high standard deviation which was a sign that one or more multis were out to lunch, and they were.
Your overclock is looking great now. :up:
Edit: Here's a i7 Turbo V8 log file from rge's i7-950.
http://www.sendspace.com/file/zup4gn
No glitches during 4 hours of testing at full load. As long as no crappy programs like RealTemp 3.00 are screwing up your readings, the Calculated Multi should be very consistent.
Hi folks,
I was wondering a few days ago if it would be possible to use something I saw on my previous P45/Q9550 E0 setup to our present i7 systems. Back then people had, and still have, to mess with the GTL references to avoid errors on an analog level of the aging AGTL+ bus of the CPU.
The thread on the workings of the GTL bus ehre on xtremesystems came to the conclusion at some point that it was actually possible to see indirectly how well the system was doing, beyond just the foggy testing when the system got unstable and then put the GTL reference setting in the middle between both unstables.
One indirect indicator of how "well" your setup felt was to see if Intel Burntest/LinX was showing increasing or decreasing fluctuations of the GFLOPs performance. IMHO this can be an indicator for excessive self-correction algorithms at work in the chipset. Also for overshoot and undershoot problems on GTL; but that's not an issue for us i7 users. Hail QPI bus!
To make the story a bit shorter.
I ran a series of tests on Windows Server x64 here on my i7 that showed that the IOH voltage is having a visible, but small, influence on the performance. Ideal seems to be 1.26 or 1.28 volts as it was to be expected. 1.22V led to a significant drop from 45.8 GFlops average to 40 GFlops. The QPI voltage was fine at 1.30 V and higher.
What was most interesting was seeing that my C0 920 was losinga quite big amount of performance if the voltage was just a bit off. 1.25V were dropping to 40 GFlops, 1.2625V and 1.275 were fine at 46.6 GFlops, and 1.30V gave the same weird dropping effect to 40 GFlops.
I was running LinX 1.5.8 using 2048 MB RAM. P6T Del. V2, xflashed to BIOS 0007. Win2003 Server x64. i7 920 C0 Batch 3839A499, BCLK200x19.
It might be possible that those here who try to run their CPUs at as low as possible VCore are losing performance as I do (assuming it's not just a kink of IBT/LinX) while being at the verge of instability without knowing.
Any comments on this? :)
Amurtigress
imho use newer versions of LinX
0.6.1 current now and it use linpack ver.10.2
there was a problems with i7 (HT also) with earlier versions.
i don't see any perfomance fluctuations - if system is stable to run and pass linpack and the temperatures below 100C.
Which voltage I should add is USB is flaky (just a little bit) and I want the USB to be a bit more stable.
Hi,Quote:
Originally Posted by Gre4ka
thanks for the hint at the update. 0.6.1 gave me some insights, however, the performance dropping effect still persists. Here's a table:
Linpack 0.5.8
vcore
1.250 perf drop
1.275 stable
1.300 perf drop
Linpack 0.6.1
vcore
1.250 cold reboot/LinX error
1.275 perf drop
1.300 stable
(perf drop: GFLops result drops from 45.7 to about 40 for several or all passes)
(stable: GFlops stay around 45.7-46.3 GFlops at 19x200)
This looks to me as if the older linpack code did not work well on i7s, per chance not being able to put the i7 chips to their limits as needed. Apparently i have had a latent instability that never caused me a problem, since my setup only gets under seriously high load when benchmarking.
I still think tho this 15% drop in the floating point performance might be a good thing to keep an eye on when testing stability/looking for sufficient voltages for certain clock rates.
Interesting read there.
im trying to get 920 stable at 4.0ghz (200 x 20)
i can get into windows at 1.18v, but even at 1.234v
its not stable (reboots after 3 hours of prime 95)
i left everything auto except for qpi (1.35), c1e and intel speed something.
should i try to mess around with other voltages?
i thought id get it stable upping only cpu voltage, then mess with
others to get the lowest cpu voltage possible.
or should i try 191 x 21?
if i go with this, i can only select 1533?mhz for my memory.
is this ok? i already ran memtest for several hours at 1600mhz
any suggestion would be helpful.
thx.
I would try 191X21. In some cases the 20X multiplier can be alot more fickle then 19 or 21. (Someone correct me if I am wrong on this.) Perhaps set the DRAM voltage to 1.66 and CPU/PLL to 1.88 and keep the QPI @ 1.35. I am still learning as well, so if someone has better advice please chime in. :)
since yesterday, the board hangs at boot up trying to detect sata hard
drives. i have 3 sata drives. 150gb, 1tb, 1tb. i am not running them in
raid or anything.
if i disconnect 2 1tb drives, everything is fine.
also if i disconnect one of 1tb drives, everything is fine.
but if try to boot with all 3 drives connected, the board
fails to recognize 2 1tb drives, and hangs at boot up.
its kinda random, sometimes it recognizes all 3 drives, sometimes it only detects
150gb drive and hangs at boot up.
i did enable & disable marvell controller numerous times, but does not seem to work.
this board is giving me nothing but problems.
i doubt its the power supply or the cables as i was using the same ones until 2 weeks ago.
on p5e3 board. i read somewhere overclocking failure could cause this. but it happens at default clock as well.
would reinstalling windows help?
can someone help?
i reinstalled windows and everything seems fine now.
i didnt even install marvell sata driver, just ich10 chipset.
trying to get it stable at 4.0 as i write this.
just hope it doesnt happen again
Errrm, you're having me totally confused. You are talking about the Marvell controller. That one is a SAS controller, assuming you have the P6T deluxe V1 board. You did not mention which one...Else, the other marvell chip on the board is the eSATA/IDE chip.Quote:
Originally Posted by sodina
If that one is having issues with your SATA drives, try them on the ICH SATA ports, and vice versa.
Try increasing the ICH voltage by 0.1V if nothing else helps.
ive been trying to get it stable at 3.8ghz for a while now.
but ive been getting some weird errors when running prime95.
for example, i would pass prime large mode at 1.2v but fail blend mode.
so i up the vcore bit more, only this time pass blend mode but fail large mode.
what is wrong here? how can i fail in large mode with higher vcore when i alreday
passed the large mode with previous lower vcore?
i believe 1.2v should be enough for 3.8ghz because i can boot into windows
at 4.0ghz (200x20) with the 1.18v.
i suspected memory. but im only running it at 1603mhz (pass memtest 5 hours),
which is pretty much the default setting.
anyone wanna shed some light on the situation here?
http://thumbnails4.imagebam.com/4411/5ff81d44109084.gif http://thumbnails13.imagebam.com/441...8c44109086.gif
Hi there,
I think you should have read a bit more of this thread.
The i7 920 requires roughly 1.25-1.3V at 3.8 GHz. That is for a C0 die revision, D0s require tendentially less. My C0 takes 1.375V at 4 GHz (19x211), but would get 100C hot running any flavor of Linpack.
IOH voltage: 1.26V. Less than 1.22 won't work at that speed.
Disable C states in the CPU config submenu.
That should get you in the right direction
upping ioh seems like working.
currently testing 200 x 19 and looks like its stable.
passed prime95 large, blend mode for 6 hours.
cpu - 1.176-1.18
cpu pll - 1.82
ioh - 1.20
qpi - 1.35
dram - 1.66
intel speed step - disable
c1e support - disable
everything else auto
temps are bit high, but its middle of summer and
i am on top floor unit with no ac on. so i dont
think is all that bad.
http://thumbnails18.imagebam.com/442...ae44248597.gif
Sodina,
apparently you're not reading my posts closely, and you are not giving some important information on your CPU, so I'll stop helping here.
Next time be so kind and read the thread before approaching people with quizzical posts.
Bye
i have no idea what you mean.
what more information on cpu? stepping?
it is 920 d0 + p6t deluxe v2
and yes, i did read about last 20 pages of this thread before
i asked a question. there was not much info on bios setting.
it was all about how 21 multiplier getting throttled town to 20
and the modified bios to fix it.
your help? ioh 1.26v is way too high for 3.8ghz.
most of 920 d0 chip achieve 3.6~3.8 with just upping vocre and qpi.
one question guys
can you use the 2 sata ports behind the white pcie slot when using 2xgtx 285 or 295??
does an gtx 285/295 fit in white slot when the psu is installed in the bottom of the case??
pls help
I don't have that kind of card here, but as I see it, those two SATAs were put right next, but left of that PCIe slot to avoid interfering with long cards in a SLI configuration. Hence also the four/six angled SATA connectors at the front of the board. ASUS had an eye on such problems when designing the board.Quote:
Originally Posted by Fire4Wire
5087 MHZ VALIDATE: http://valid.canardpc.com/show_oc.php?id=584665
Very very nice...21x242.33 on a P6T Deluxe!!
Quote:
Originally Posted by EXPANDER
How come the vcore is blanked out.? If you have some ridiculous high vcore and you cant use it 24/7 then it doesnt mean much imo.
It's doen automatically, try it yaself... there's never ever a Vcore indication in a CPU-Z Validation screenshot... sorry to say but almost everyone understands that a 5Ghz validation is not a 24/7 speed... no idea why you even made that comment...Quote:
Originally Posted by Buggalugs
Good work Expander on that P6T , top job !
Well im just making the point that for me unless you can run it 24/7 its pointless. Sure its a good effort to validate at that speed but i dont see the point if you cant actually use the computer for what its designed to do.Quote:
Originally Posted by Leeghoofd
But yeh i dont usually come here for that reason, most of this thread is crying about 21X multiplyer dropping at over 4 ghz and people saying asus sucks because their 2.66Ghz CPU will only run normal up to 4ghz.
I just like to keep an eye out for new bioses or any discovery about the board.
OMFG! :shocked:Quote:
Originally Posted by EXPANDER
Great job!!! :up:
Can you post your voltagens in bios to get this bblock clock? :D
1.48 Vcore Vapochil Ls Modified - 30c:up:
http://img199.imageshack.us/img199/3...lovvoltage.jpg
Have any of you removed the "top" of the NB heatsink to add another waterblock / heatsink?
If so, what where your results?
Like this:
http://www.xtremesystems.org/forums/...d.php?t=207977
I did a quick test with some freeze spray to cool things down and my finger to heat them up. So far as I am able to determine, the motherboard temperature of the ASUS P6T Deluxe V2 motherboard is actually the temperature of the Winbond chip itself. It is not an ambient temperature. Due to its location, it is also highly affected by the cooling layout of the first video card in the system.
In this picture of a P6T Deluxe V2 motherboard, I have outlined the Winbond chip with a green rectangle:
http://members.cox.net/danco/WinBond.jpg
Can anyone either confirm or deny that this is indeed where the motherboard temperature sensor is located, inside the Winbond chip?
.
I have not added a water block to mine, but I have removed the heatsink and replaced the thermal pad found there with well spread out MX-2. I have also added the supplied standoffs and a 40mm fan to the heatsink as specified in the motherboard manual.Quote:
Originally Posted by WeeMaan
Bare heatsink:
http://members.cox.net/danco/BareHeatsink.jpg
Fan on heatsink:
http://members.cox.net/danco/FanOnHeatsink.jpg
nice work's:clap::clap::clap::up:Quote:
Originally Posted by EXPANDER
I know I am off topic by not talking about the 21x multiplier. What do you think about the new P6TD Deluxe?
Intel Matrix Storage Console - 8.9.0.1023
Intel Chipset inf - 9.1.1.1015
Yukon Ethernet - 10.70.6.3 - 8/14/09
What's the difference between the P6T Deluxe V2 and the P6TD Deluxe?Quote:
Originally Posted by chuckbam
Intresting, did you noticed any improvements in overclocking or stability?Quote:
Originally Posted by astrodanco
Or perhaps it wont get so hot that it's a problem even without fan.
It's aluminium right?
The black fins part that screws to the underlying chipset heat sink is aluminum. I think the underlying chipset heat sink is a copper plated aluminum slab. Hard to imagine ASUS paying for solid copper. The 40mm fan is obviously plastic.Quote:
Originally Posted by WeeMaan
Back when I was on air cooling I was not using the ASUS fan and the 40mm fan. I also wasn't using the stock Intel cpu heat sink and fan. I was using just a Mugen-2 with a Scythe fan blowing through it rearward. So I'm not sure how much air either the MOSFETs or the chipset heat sink were getting when I was on air. Probably not much. On air I was running 3.2 GHZ 24/7.
When I switched to water cooling I added both the ASUS fan on the rear MOSFET heat sink and the 40mm fan on the chipset heat sink. I never actually even tried water cooling with out them. On water I'm running 4.0 GHZ 24/7.
I have not noticed any differences between having the fans there or not there, but then I haven't looked for any either. I've been told that the motherboard life would be shortened without either them (or something else to accomplish the same thing).
I'd certainly be willing to add an inexpensive water block to the underlying chipset heat sink instead of using the black fins and the 40mm fan. That would likely cool better than the black fins and 40mm fan do. I may do that. But I suspect it wouldn't make any difference, so I'm currently operating in "why bother?" mode.
What I'm not willing to do is to buy a full cover motherboard chipset water block AND two MOSFET blocks. For the price and inconvenience of adding all of those, I could more easily buy and swap in a new motherboard when/if mine eventually fails!
All I can see is 2 additional copper plates on the back of the board.Quote:
Originally Posted by astrodanco
-
http://chuckbam.com/Post2/P6TD.PNG
P6TD Deluxe is 16+3 phase design while P6T Deluxe V2 is 16+2 I believe.
Also ASUS Fanless Design: Stack Cool 3+ (more copper) afaik.
Nope it has 16+2 Phase Power DesignQuote:
Originally Posted by zalbard
Stack Cool 3+, Two copper plates (like I said)
http://usa.asus.com/products.aspx?l1...76&modelmenu=2
I don't understand why they bother with such minor a difference unless this is intended to supersede the P6T Deluxe V2.
What they should have done is add another RAID controller where the SAS was and include some eSATA adapters. And change 1394a ports to 1394bQuote:
Originally Posted by astrodanco
2 copper plates :)
I bet it will supersede the P6T Deluxe V2.
The V2 is for Version 2 less SATA ports.
--------
Intel Matrix Storage Console - 8.9.0.1023
Intel Chipset inf - 9.1.1.1015
Yukon Ethernet - 10.70.6.3 - 8/14/09
no newer p6t deluxe v2 bios as 0504
if you have some newer bios pn me
thx
Only the 0007 and the 0006. illuminatiASUS said new bios' are in the works for the P6T series, but did not give a time frame. I myself do not expect any. I am moving on to other brands of motherboards.
I plan to keep this board for a good while. But, this will probably be my last ASUS for my #1 system. The chassis fan headers stopped powering. They sent me an advanced replacement that would not boot to 12GBs. I sent it back and purchased 4-pin connectors and some controllers. I hope nothing else goes. The CPU and Power Fan headers work fine.Quote:
Originally Posted by r1rhyder
I used to only buy GIGABYTE. look at this baby! But, I think it only has 2oz of copper :)
http://chuckbam.com/Post2/13-128-362-06.jpg
Does anyone know if the P6TD Deluxe has the new b3 x58 chip?
What's the difference about this B3 rev?Quote:
Originally Posted by MetalRacer
Have someone notice when you plug a more power video card, the overclock become more hard to get estable overclock at the same settings when using a basic video card?
Here i can get nice and stable 4200@1.224 with 8400GS, but when i put my GX2 for example, for the same clock speed i have to push a litte more voltages on de cpu (1.248) and the board... is that normal? :confused:
how did he get that all those voltages monitoring? :eek: :mad:Quote:
Originally Posted by icecpu
My new P6T Deluxe V2/P6TD Deluxe:up:
http://img198.imageshack.us/img198/8238/p6td.jpg
your point is the P6TD bios'es is no longer have "multiplier throttling bug" ? am i correct?Quote:
Originally Posted by angelreaper
but, i have interesting question thoug. Are you using P6TD or you just "crossflashing" P6T v2 with P6TD bios??
angelreaper is only at 3150 MHz so far. He's just getting warmed up.
Welcome to Asus angelreaper. :)
He won't be able to tell if there are any turbo throttling issues until he gets up to 4000 MHz and beyond.
Those core temperatures are pretty bad. I'd recommend water cooling...
oh..i see..:cool:Quote:
Originally Posted by unclewebb
it appear i have been mistaken by thinking that this particular throttling problem is triggered by high cpu temp.
i also been thinking (w/ extreme prejudice :rofl:) :
If (later) P6TD bios is proven to have "turbo trhottling" bug fixed, meanwhile the "old" P6T DLX/V2 will never get this "bug" fixed (the 0006/0007 is forbidden right?). I think asus is trying to setup a massive "exodus" from P6T DLX/v2 to P6TD DLX...bad,bad asus :D. i just hope my "prejudice" will only be "prejudice" not the "reality" :D:D
Lots of users have successfully cross flashed their P6T Deluxe v2 board with the special v1 0006 bios without any problems.
Asus just released another special bios yesterday for the P6T6 WS (0001) and JJ asked me what board should be next. I told him to flip a coin.
Lots of v2 owners but the serious users are already using 0006 so I thought a special bios for P6T7 WS might be more important. Go back a page or two in this thread and find JJ and tell him what you think. Place your vote for a special v2 bios if you think that's important.
Turbo throttling is caused by all 3; high core temperatures, high current and high power consumption. Minimize all 3 of those and the higher you will be able to overclock without hitting the throttling wall.
Much easier to just cross flash to bios 0006 and solve all your problems with one quick fix.
I cross-flash my P6T Deluxe V2 to P6TD Deluxe:)Quote:
Originally Posted by E-CRUSH
This is my work machine with box cooler. But soon I test with good processor and cooler:up:Quote:
Originally Posted by unclewebb
For now not multiplier throttling.
:D:D:DQuote:
Originally Posted by unclewebb
may i ask you, i have 1 (noobies) question :D:D :
what is the difference between 0007 and 0006 bios if i using P6T DLX OC PALM w/ i7 920 D0?
all i know is the 0006 bios fixed some issues w/ c0/c1 steeping. Is there any detail i might have overlooked?
so it's possible!!! :up:Quote:
Originally Posted by angelreaper
that make me to draw a conclusion that P6TD just P6T DLX V2 with more ounce of cooper and new chipset (SLGMX / X58 B3) (CMIIW).
and...that gave me more than enough reason to cancel :ROTF: my "exodus" plan :ROTF: from P6T DLX V1 (oc palm) to P6TD.
( admittedly some of asus marketing mumbo-jumbo has nail me :D:D:D )
My results with the Ci7 920 @ 4200mhz are now stable at 1.208v :D
I will try to get more oc from the processor now :D
http://img34.imageshack.us/img34/668...108vstable.png
Bios for P6TD Deluxe - 0106 no turbo throttling but no full support for Xeon:down:
But bios 0006 is great:
http://img195.imageshack.us/img195/4982/4621b.jpg
http://valid.canardpc.com/cache/banner/668291.png
http://img19.imageshack.us/img19/8408/44unrar.jpg
To date, my system has been ROCK SOLID at 4.40Ghz 24/7 ever since I crossflashed to the 0006 BIOS on my V2 board when that BIOS was made available. I have not run into any issue whatsoever......there isn't anything new to report that's why I haven't post much lately. LOL :D
I assume that is your daily setting...nonetheless,still it is an excellent result you have there..:clap:Quote:
Originally Posted by angelreaper
Just out of curiosity, the 0106 (P6TD) bios fixed the turbo throttling by "cheating" ( slashing TDP reading ) or by *ehmm..* "superior design" :D, like asus'es claim on ROG series mobos.
I just got me new P6T Deluxe V2 but i need some help with a problem.
Im missing the QPI link settings and the uncore setting in the AI Tweaker menu:censored:
Im using the latest 0504 bios but i cant finde the two settings they are just gone:eh:
Cross-flash to 0006 bios:up:Quote:
Originally Posted by Rasmus66
Bios 0006 is very good:
http://img35.imageshack.us/img35/2908/superpi2.jpg
http://img35.imageshack.us/img35/9131/superpi1s.th.jpg