all voltages were kept at default value afaikQuote:
Originally Posted by monza1412
Printable View
all voltages were kept at default value afaikQuote:
Originally Posted by monza1412
Can't wait for 2103 to be made official, with a changelog of "support for new CPU." :lol:
E6850 here I come!!Quote:
Originally Posted by miochza
Quote:
Originally Posted by monza1412
At 400FSB you should be able to leave the chipset voltage on Auto or 1.65V this depends on the memory speed. If the memory speed is 1000MHz or greater (which will be very hard) 1.75 ~ 1.85V will be needed. You'll have to raise all the volatges to MAX (ICH etc.) at 445FSB with memory running on the 800strap or at 890MHz for 445FSB, I also raised the Vcore on my E6400 to 1.40V at that speed, but not because it needed it....
Now here's the weird thing. If I left the memory strap at 533FSB and overclocked as high as 440FSB, Vcore for my E6400 could be left at default? I was using the PCPower&Cooling silencer 750W so it had nothing to do with the PSU, BUT what I did mention in the review was the P/4-pin power connector?
For the 975X chipset this should be an 8-pin connector and I believe a major issue with this board may be the power cricuitry isn't given current in the correct configuration, even though it seems robust enough regarless with an 8-phase stage and the mosfett coolers. Asus may have thought Conroe wouldn't clock that high off the 975, at 445FSB the chip is running 150W. I'm sure this is taxing the power circuitry and then affects the NB MCH requiring more voltage.
Nice article/review Liquid3D. I have built 14 systems on this board all have worked perfectly. All are set at 400fsb except for 2 one is set at 413,his cooling threshold and mine is set at 413 right now also As I am playing with 4 sticks of G.Skill 6400HZ running 1:1 timings set at 4-3-3-4. I have had this board for 1 year now and it is a great board. Clock for clock it will run with anything and out run most. My system resides in a case and functions 24/7.
I did not set out to build a bench machine, just an extremely fast stable benchable machine to earn it's keep in my room. It has done that every day since I bought it. First with a 950ES Presler running daily at 4800mhz to a 6400 Allendale running daily @3400 to my e6600 running daily at 3825mhz. All 3 systems were and are just smooth and flawless. I will be keeping my board for a long time to come. The bench numbers in my sig let you know it's fast but more importantly it is also rock steady. I love the damn thing.
WZ
Does anyone know where the thread is about making the P5W ready for overclocking?
It was called 'preparing for the beast' or such, but can't find it...
Is this what you're looking for?
lol - it's in my sig too :)
@~aoe~: indeed that one :p
@WeldZilla: have you done mods on your motherboard, or just stock.
Has anyone managed fsb 400 or over with 4x1GB sticks? With two sticks it's primestable 406 fsb (vfsb 1.40V,MCH max(1.65V),ICH Auto), but with 4 sticks cannot get primestable even 400. I'm using 1707 bios.
Can anyone recommend a good heatsink to replace the stock one on the NB of the DH Deluxe? I'm using a Big Typhoon for my CPU, and it has pretty good clearance. I don't need anything too amazing, just wanna be able to raise the vMCH a little without having to worry about it.
I like the Zalman ZM-NBF47, but I'm not sure if it will properly mount on my board, or if it will even make a significant improvement over the stock HS.
Also, can I simply cut the heatpipe that goes from the stock HS to the HS on top of the MOSFETs? Or is there some more elaborate way that I need to separate them?
I'm using the Thermaltake Extreme Spirit II as suggested by Lawrywild.
I tried the Thermalright HR-05, which is a superior heatsink, but the retaining bracket provided isn't suitable for this board.
Note that the Thermaltake Extreme Spirit II isn't really suitable for the SB if you're considering that - I found that the retaining screws were too high and prevented correct seating of the graphics card. HR-05 SLi works fine though (excessive for the SB i know...).
I think that my s. bridge is overheating, I've used some very complicated high-tech equipment (my finger), to measure the temp of the heat sink, and I've found that it's untouchable. Though, I can't find any software that measures the temp of the s. bridge. Does anyone know of one (that is preferably free)?
I need to be sure that it's overheating before I send it back because I've only had the board for two days and had to buy XP for it. If I get a replacement then I get to buy a new XP license. *yay*
SpeedFan 4.32 reports a number of temps from all the chips/sensors that it is able to read. On this board, it shows 3 temp readings from the Winbond W83627DHG chip, namely CPU, AUX and System.Quote:
Originally Posted by LordXenu
Now, I could be totally wrong here, but I sort of assumed that the System temp referred to the SB.
I have noticed that the AUX sensor temp increases under load, whilst the System temp remains stable. That made me think that the AUX sensor was maybe the NB, and the System the SB.
I'm happy to be corrected if my assumptions are incorrect...
I asked the same question a couple of weeks ago :)Quote:
Originally Posted by cbell
It is as simple as cutting the heatpipe. There should be a small amount of liquid in the pipes (most likely water), but nothing to worry about.
The inside of the pipes also contained a copper-coloured crystalline solid - not sure what it was (more copper maybe?). In order to avoid the risk of anything dropping onto the board from inside the pipe after installation, I chose to remount the MOSFET heatsink the opposite way round, so that the open ends were facing up (tower case).
Anyone able to flash back to a older bios, I experimented with bios 2004and I want to switch back to 1601 (unlocked multi) and everytime I try to flash back, it says older bios detected, please download latest file from ASUS website.
HALP!
I don't believe that is correct. The temp reading for the system is low, no where near the temp of the heat sink.Quote:
Originally Posted by ~aoe~
Better way is too place the chipset cooling assembly onto stove burner @ 75% heat for about 10 minutes. While hot, gently twist the mosfet part and it should come loose from heatpipe. then you are left with empty mosfet cooler, and intact heatpipe, should you decide to restore stock cooling!Quote:
Originally Posted by ~aoe~
Quote:
Originally Posted by Luis_GT
You, my friend, must flash using a floppy, and afudos. using the proper switches, you can force the flash.
Telling me the switches would be helpfull,Quote:
Originally Posted by cadaveca
What I've used so far Afudos /iP5WDH.Rom /pbnc /n and still won't work, yes, I renamed my Bios to P5WDH just to try the Alt + f2 Flashing.
Just use afudos 2.17 like the other people who asked this question about a billion times..
Thats the thing... I am using Afudos, I tried EZflash, I've tryed Alt + F2, non of them work. Hell, I'm even using FCG's Flash.bat and it won't work. Just a few months ago I flashed back from 1707 to 1601 with no problmes... I'm stumptQuote:
Originally Posted by lawrywild
Ok, I finally flashed back, 2.21 and 2.17 didn't work, but I found Afudos 2.07 and that one worked.
FYI:Quote:
Originally Posted by ~aoe~
- System/Motherboard temp sensor is NOT inside either of the bridges:
http://www.xtremesystems.org/forums/...54#post2052854
- don't know when LawryPooPooHead is going to fix his "first page" - LOL!
Mine run 8 x 400 with four memory sticks. Prime and TAT stable. But not Orthos...
Quote:
Originally Posted by Family man 72
No mods on any of the boards I have built on. The boards are fine. I have replaced the dry crap under the NB heatsink with AS-5 that's it.
Hey cadaveca contrary to popular belief you can go home again...Think about it.......
WZ
how can I make the esata working with my seagate esata hard drive? I have been unable to do it it works fine with usb 2.0. Thanks
I needed to push vMCH to 1.75v on my mobo to keep Orthos happy with 4 x 1GB at 800 4-4-4-8.Quote:
Originally Posted by Family man 72
now then people, i am having a problem upping my pcie bus above 120mhz. if i go to even 121 then the boot process misses out the hard drives and dvdwriter and then instead of the dual boot menu i have a message telling me to select a propper boot device in bios. this happened when i was only using 1 os also. the pci bus is locked of course and would just like to know what the motherboard is doing or not doing. i may then be able to figure out a work around. i have two hd2900xt's and they love the extra banwidth. the 3dmark06 world record was done using 167mhz on the pci express bus....
ok i worked it out, i think the sata-2 drives are on or connected to the pci-e bus and thats why they arnt recognised at boot. if anyone has any info please let me know... i've searched every link on google so far...
I love this thread... responses are fast and it fills up with new information so quickly.
Thanks, I'll try this for my NB. I'm not overly concerned about my SB; I replaced the thermalpaste with AS5 and took off that weird metal cover over the heatsink.Quote:
Originally Posted by ~aoe~
Quote:
Originally Posted by ~aoe~
Thanks, sounds easy enough. Would you guys recommend that I upgrade my cooling if I only plan on upping the vMCH to 1.65? Or would stock cooling with AS5 be sufficient? I have my overclock turned off for the summer, so I'm planning ahead for fall right now.Quote:
Originally Posted by cadaveca
I'm surprised nobody responded before now to your many posts about mounting the HR-05 on the north bridge.Quote:
Originally Posted by ~aoe~
It's actually fairly simple: after removing the stock NB heat sink, pry its clip from the HS (it's held in place with friction by some folded metal), then use that clip on the HR-05.
Or, you can do what I did before realizing this trick: bend the s**t out of the supplied HR-05 clip so it slips under the hoops of the P5W, which are of course on the opposite corners to what Thermalright designed for...
I've just seen a bunch of news about BIOS updates including microcode fixes for some Intel Core 2 Duo CPUs, including the E6600. Does anyone know how to tell?Quote:
Originally Posted by miochza
been looking thru the pages but can't seem to find much info on vMCH required for 400MHz FSB oc?
my 1.03G requires 1.65V to achieve 400MHz stable (default of 1.55V results in auto-reboot during loading of Windows).
wonder if the 1.04G can do it at 1.55V since it is using a 'newer' 975X?
how much volts did u require for this (i'm thinking of going 4GB too)? and rev number of your board is? :)Quote:
Originally Posted by psy4fun
mine wont boot when i plug my psu
the onboard green LED (SB_PWR) is blinking
is my mainboard faulty?
Here is a link to simple pencil mods to increase all your voltages if you need to.Quote:
Originally Posted by TWY
http://sg.vr-zone.com/?i=3876. I have a later revision but need MCH=1.65v for stability with FSB400 running memory 1:1 . Search the thread for more on 4x1GB setups.
CC, if you have 4Gb of main memory, only a 64 bit OS will allow you to change the BIOS setting which will address all 4Gb. If you are running 32 bit, most people are (doesn't matter if it's XP or Vista), you can only address the 2688 Gb.Quote:
Originally Posted by -:[CC]:-
Upgrade to a 64 bit OS (XP and Vista have 64 bit versions) and then you can safely change the BIOS option allowing your OS to see all 4Gb.
Hey guys. I can't install 64 bit operating systems with this board's Intel ICH7R/Matrix RAID enabled. It's always "setup cannot copy the file: iastor.sys". The drivers won't really install. Of course I have no problem running 32 bit OS's. Is there some BIOS setting I'm missing?
I'm running:
Intel e6600
2 GB of Super Talent RAM running 4-4-3-8
A variety of sata hdd's, especially two 150GB Raptors I'd like in RAID 0
I have tried:
Installing AHCI style and converting to RAID with utility
Multiple matrix drivers
Removing all non-vital hardware
Different versions of the BIOS
Different RAM
1 GB RAM
A wide variety of bios settings
Much more
A barrel roll
Again, if I pretend the drives are IDE, the installation works. However, I'm determined to have RAID 0.
I'm at my wits end. Any ideas? :shrug:
You downloaded the correct 64bit floppy drivers yeh?
http://downloadcenter.intel.com/Deta...%2064&lang=eng
If it's Vista x64, then it already comes with drivers on the DVD so no need to use floppy.
Hi, my system is :
Case : Thermaltake Soprano DX, 12cm Front Fan , 14cm Rear Fan, 9cm Side Fan Scythe
Power Supply : Thermaltake 650 W
Mobo : ASUS P5W DH Deluxe WiFi, ASUS 6cm HeatSink Fan 6cm, BIOS 2004
CPU : Intel Core Duo E6700 with Thermaltake CL-P0371 TMG I1
RAM : 2 X 1 Gb Kingston DDR2 PC6400 533 5-5-5-15
Graphics Card: ASUS 8800 GTS 320 Mb HTDP
HD : 1X 150 Gb WD Raptor SATA, 3X 500 Gb WD SATA
Sound Card : Creative Sound blaster X-fi Platinum Fatl1ty Champion Series
OS : Vista Ultimate Greek
I tried to OC but I only get 3,06 Ghz with the 15% AI OC predefined profile.
With all the other auto options (30 % etc) I had no luck.
With 30 % (3,2 Ghz) after 5mins under ORTHOS priority 9 the pc freezes.
With some other options doesn't boot or windows doesn't start and after restart (sometimes) get bios message about high
voltage.
In CoreTemp I get at Idle 40-42 and at full load 49-51 C.
Can someone please give me a safe starting point for manual oc (voltage,timing etc) and any other options on BIOS setup
('cause I see much higher speeds than mine) ?
If any other infos needed,please let me know.
TIA
If you want to manually overclock you do not use AI. Follow this guide http://forumz.tomshardware.com/hardw...ict197995.html and read the first page of this thread. You can search this thread for answers to most problems you may encounter on the way.Quote:
Originally Posted by vladimirus
Sesdave thanks.Quote:
Originally Posted by sesdave
I'll try these settings and see what happens.
Regards for all the members.
Here is my question :
Finally is there a practical way to unlock the multiplier for a P5W DH Deluxe bios ?
I installed 2004 version, for a QX6700. I read that 2103 new bios also is locked to 6-10 limits (very similar to 2004 bios) and I don’t want to downgrade to 1601 or 1506 versions.
I find “a modded bios“ but I don’t know what exactly "modded bios" is. Have a look at http://forums.mydigitallife.info/sho...postcount=3515
I think that is very difficult for such modded bios to unlock the multiplier but really don’t know.
Also I couldn’t find a way to do this, from lawrywild’s post http://www.xtremesystems.org/forums/...10193&page=198 , #4945
with AMI Tools. Very useful tools but not for unlocking the multi I think.
I also read the relative post http://www.xtremesystems.org/forums/...24#post2227324 , #4984
Also I haven't tried the CPUID software and i 'm wondering if anybody succeeded to change the multi using this software to a quad or if anyone has tested RMClock 2.25 utility for that purpose ?
Finally do you have any recommendations about these “modded bios” use ?
Guys...something that I think is very odd just happend to me 5 min ago. I have not posted here for a very long time because I gave up on this board about 4 months ago. I just dusted off my old p5wdh mobo and started to build a second rig because I had some extra parts. I installed a E6600, a cheao nvidia pci graphics card, seagate 160gb hd, And a very good pair of ocz alpha vx1000 2gb kit. After installing vista 64bit i started to mess around and overclock. On default nb volts This thing is stable at 360x9 mem at 1080mhz:eek: I remember why i stopped using this board 4 months ago it was because of terrible memory overclocking. This board is rev 1.02g so its old one. I can post screens if its a special mem overclock. If it is not then sorry for this post i just foud it wierd. thanx
My overclock now.:eek: Stock Nb volts vdimm set to 2.25 in bios.
Those modded bioses are to make the board appear to windows like an oem system, so you can activate certain versions of windows.Quote:
Originally Posted by chessman
I decided to install an MCW20-K on the northbridge pumping 10c water through it and its much more stable now. I will let it run over night. Some pics of my ghetto rig i put together tonight:D
Quote:
Originally Posted by chessman
Why don't you want to use 1601... other than the bios misreading the temp, theres basically no difference.
@lawrywild : Thank you for the answer. Also for this very useful thread.Quote:
Originally Posted by lawrywild
@Luis_GT : Bios 2004 is very stable for my rig. I ‘m afraid about “growing pains” with 1601 or others. Do you use 1601 with your qx6700 ? What about the multiplier ?Quote:
Originally Posted by Luis_GT
Yep, I have 1601 and run a 12x multi just fine, I can get it up to 20.
What "growing pains" are you talking about exactly... I've had zero issues with it and I can oc my memory upwards of 1000mhz, which I could'nt before... oh and 2004 killed my bios chip for some reason, Did a few benchmarks under that bios, failed a OC and it never booted up again... and a hot flash didn't work.
Quote:
Originally Posted by Luis_GT
Thank you very much for the answer.:)
I think I will give a try to 1601.
i am using p5wdh deluxe + e6400 2.13 ghz .......
i have installed vista ultimate .. and my bios version is 1305...
i am thinking to upgrade it...
please tell me.. which version is the best and also WHETHER there are any RISKS involved in bios updation ?
thanks in advance....
Anyone running with G.skill 4GB (2x2GB) 6400c5 PQ - if so how do they perform. I cant find a decent review of them. I have just dual installed Vista x64 with winxp pro
and have ordered these sticks instead of 4x1gb ballistix 8500C5. I though they would be easier on the board memory controller from what I have read but I might regret it if they they wont run decent timings.
Edit 06/07 - Answer my own question. I got these sticks and found I could only post and boot to winxp pro with SPD enabled. Vista x64 hung on black screen after logo - I know there is a hot fix for 4GB problems but I think this is more board compatibility. I trired reducing to rated settings of 5,5,5,15 with memset and the system froze. This was running on my current settings for 3.6ghz. - fsb400 and ddr800 FSb=1.3v,MCH=1.65,ICH=1,2v. I tried memory at 1.8-2.0v and with MCH=1.75 with no joy . I also flashed to BIOS2103 in case there was a memory compatibility issue I had missed but no joy so I am going to change them for 4x1GB ballistx 8500C5's and see how I get on with them.
I am running mutli boot winxp pro and vista x64 and have been running no problems with 1707 and dont see anything that makes me want a later version - not really much differences with later versions apart from support for other CPU's and so called memory compatibility. Search the thread or comments on each version and take your pick! You can always reflash older bios using afudos 2.11 or earlier and renaming the bios to be installed as P5WDH.ROM. Check the thread for more detail - there was a recent post on BIOS 2103. I and others have posted the detail numerous times.Quote:
Originally Posted by phoenix.bits
well im hoping asus gives us a update so we can run the new go steppings chips
Apparently 2103 includes the updates for running G0 stepping cpus
I hope this includes e6750/e6850..
thanks lawry i do to im waiting for price cuts. 1901 update the 1333 fsb so guess we will seeQuote:
Originally Posted by lawrywild
OK, here's my tip to the "extremely slow booting" problem. I was also left staring at the POST screen for 40-50 seconds, and this is what helped:
If you don't have a fan, change it's BIOS setting to "Ignore". If it set to N/A, the mobo will search for it. N/A doesn't mean it's not there, just that the mobo can't find it, but it will look for it...
Useful tip ! Thanks bern_viking :up:Quote:
Originally Posted by bern_viking
mainly i came here because i found this in the official FTP
ftp://ftp.asus.com.tw/pub/ASUS/mb/so...eluxe/2205.zip
BIOS2205!
I really wish that ASUS would add changelog into their ZIPfiles like other Vendors...
Can any 6600-B2 User confirm Multichanges to 10+ with 1601BIOS?
iLL
2205 bios allow to go up and down with the multiplier of the Core 2 Extreme (at least for my QX6800)!!
No more need of 1601.
I 'm waiting every day for a new bios. I will try it.Quote:
Originally Posted by SKiLL3D
In any case Thanks a lot SKiLL3D !
Regards from Athens !
Peanuts, is there any new option about tRFC, tRD etc ?Quote:
Originally Posted by Peanuts
What about cpu temperature indication ?
edit : I saw ! No tRFC, no tRD, only change multiplier 6 - 20 (and cpu temp).
Rapid Mirror as usual:
http://rapidshare.com/files/41961174...eluxe-2205.rar
i can also concur with peanuts higher up that the 2205 bios allows multiplier changes on extreme chips i have a qx6700 and it works well, also first time ever ai booster shows the right cpu frequency
2205 is the worst bios ever for me
EIST does not work unless you turn C1E on too, multis screw around on my E6600, disabling onboard devices doesnt work, windows is telling me it's finding new devices.. 2103 f*cked up my rig, i have no idea how but it's unstable as f**k now, even after flashing back (too coincidental to NOT be 2103, after i just flashed to it 10 minutes earlier) and now 2205 is just SH*T.
WTF
sorry to hear that Lawrywild. I dont upgrade bios since 1707. In this motherboard, unless you have a new cpu I think its pointless. At this time, TRD and TRFC its only a geeks wet dream. :shakes:
I know, I just wish I didn't upgrade bios from 2004 now :(
Is there really a chance that a new BIOS flash can permanently affect the MB, even after flashing back?Quote:
Originally Posted by lawrywild
While I'm at 1707 now, I tried some newer ones but kept being beaten back by the requirement that I hit F1 to accept defaults when it refused to correctly save my new settings. No amount of CMOS resets ever helped, like my revision of the MB isn't quite up to the specs of the ones around which they now design the BIOS...
I'm pretty sure there is yeh, I have two theories;
1. The bios itself fed too much voltage on first boot, or just had some dodgy setting or something that's damaged my ballistix or chipset (pretty sure cpu is fine).
2. There are still remains of the old bios that even afudos /pbnc /n won't flash over when flashing an old bios.
The second theory I thought about a long time ago, remember how everyone said they'd noticed a decrease in overclocks over time, well we were also all updating ours bioses too.
Some people experienced better overclocks with 2004 (I didn't) but it shows that the bioses can affect overclockability and hence my theories are a possibility (imo) :p:
Id, there is something wrong with this bios. I just flashed to 2205, immediately after reboot, when I entered windows, it said: "Found new PCI-Device" - I was like "wtf?". I took me a while before i recognized it was one setting in bios that wouldn't be saved; more exactly "Disable onboard sound device". This is freakin' irritating, since I have X-Fi and don't want to use the onboard, it keeps popping up on every reboot. I haven't had any problems with anything else though, but this problem is extremely enoying.Quote:
2205 is the worst bios ever for me
EIST does not work unless you turn C1E on too, multis screw around on my E6600, disabling onboard devices doesnt work, windows is telling me it's finding new devices.. 2103 f*cked up my rig, i have no idea how but it's unstable as f**k now, even after flashing back (too coincidental to NOT be 2103, after i just flashed to it 10 minutes earlier) and now 2205 is just SH*T.
WTF
I'm forced to just "disable" the yellow "?"(PCI-Device) in Device manager to keep it from popping up on every reboot. It helps, but I hate to have yellow "?" in my Device manager.
I have tried to revert back to 2004 - but I haven't figured out how to do it. When I try to flash back with Asus Update Utility(even with "Bios downgradable" enabled), It says: Warning! Bios date is older etc etc. Please use ASUS DOS. And when I use the Asus Ez Flash utility, it says the same; "Bios is older than current version" - and program ends back to main menu.
I really would like to flash back with AFUDOS, in DOS mode; however here comes my problem: How can I flash with a bootable floppy when the bios file is too large to fit on a floppy? I mean, I made a bootable floppy disc and copied AFUDOS on it - but the bios file is over 1 mb large, so there's no space for it?
If anyone could explain it for me, I would appreciate it - and surely try to revert back to 2004.
Hope someone is able to help =)
Not all the hidden files on the bootable diskette are necessary. Delete from the floppy the file named somewhat like “ Drvspace.bin” it’s about 68 Kb.Quote:
Originally Posted by tentp0le
Use afudos 2.17 or 2.11. These versions doesn't check the date or/and the version of the bios, so you will be able to downgrade with the command “afudos /p5wdh.rom /pbnc /n“
Yes, and also for me it found pci modem (i assume the gigabit controller) which I had disabled in the bios. Just a seriously badly coded bios, nice one asus :clap:Quote:
Originally Posted by tentp0le
edit: (as well as the onboard audio)
Seems that this crappy little bugger has made it official..(Asus Web site).
Found this at Asus forums: (pay attention to the last paragraph!)
Link: http://vip.asus.com/forum/view.aspx?...Language=en-usQuote:
My system: E6600, 8800GTX, 4GB Corsair (dual), 640 Gb HDD, P5W DH Deluxe. Vista Ultimate.
I flashed 2103 several days ago and problems started. The system became totally unstable! PC hangs up even when I try to open file manager. In my E6600 core 1 is loaded for 5 - 7% and core2 - for 100%.
So it's no way to reboot or shut down the computer. Explorer stops responding completely
The rollback to bios 2004 does not help to solve the problem!
I've tried to tune the bios up in different ways - no chance to fix the bug!
BTW, Asus had already removed 2103 from ftp. I asked the support of Asus in my country about the problem but until now - no response.
Now I flashed 2205. Loading the defaults after flash procedure to apply the new bios was a problem - the defaults did not apply from the first time - I had to repeat it 3 times to make changes!!!
So - DO NOT FLASH to 2103!
Next thing:
How to get rid of existing 2205 bios.
Method 1.
Under Windows start AsusUpdate utility (from the original support CD)
Start flashing 2205 procedure. Straight after "Erase ROM" part is finished - kill the process with Task Manager or Process Explorer. That's it. You don't have any bloody bios at all.
Insert original motherboard CD to drive. Reboot. The system will start to recover bios from the CD. In my case I obtained finally bios ver. 0801.
Method 2.
Do the same without windows. Start AFUDOS.exe. Start flashing 2205. After it deletes the current ROM - just unplug the power from the outlet. The rest - is the same as above. Insert CD. Recover...
Wow, so I'm not the only one, I'm seriously pissed off about this. That's a dodgy way to correct the issue, but I will probably end up trying it if I can get my rig stable again. Strange thing is, my pc goes through 18 hours orthos, 8 hours memtest and then crashes on MSN minesweeper and some media center service in the background.. :banana::banana::banana::banana:ing asus!
O.O that sounds risky, isn't there any other way to revert back to an older bios?Quote:
Next thing:
How to get rid of existing 2205 bios.
Method 1.
Under Windows start AsusUpdate utility (from the original support CD)
Start flashing 2205 procedure. Straight after "Erase ROM" part is finished - kill the process with Task Manager or Process Explorer. That's it. You don't have any bloody bios at all.
Insert original motherboard CD to drive. Reboot. The system will start to recover bios from the CD. In my case I obtained finally bios ver. 0801.
Method 2.
Do the same without windows. Start AFUDOS.exe. Start flashing 2205. After it deletes the current ROM - just unplug the power from the outlet. The rest - is the same as above. Insert CD. Recover...
CONFIRMED!Quote:
Quote:
Next thing:
How to get rid of existing 2205 bios.
Method 1.
Under Windows start AsusUpdate utility (from the original support CD)
Start flashing 2205 procedure. Straight after "Erase ROM" part is finished - kill the process with Task Manager or Process Explorer. That's it. You don't have any bloody bios at all.
Insert original motherboard CD to drive. Reboot. The system will start to recover bios from the CD. In my case I obtained finally bios ver. 0801.
Method 2.
Do the same without windows. Start AFUDOS.exe. Start flashing 2205. After it deletes the current ROM - just unplug the power from the outlet. The rest - is the same as above. Insert CD. Recover...
O.O that sounds risky, isn't there any other way to revert back to an older bios?
First I want to thank roger_h99.nor for sharing this with us.
I decided to try this solution #1, and can confirm it worked - I'm now at bios 2004 again (thank god), and everything is working 100%. I have rebooted, shut down the PC to check that everything is OK.
Just a little heads up!
I tried it because I have another PC next to me, I can do things on if my main rig fails; and in this situation I'm glad I had another PC.
My steps where as follows:
(Before I started, I made sure my boot priority where as follows: 1. CD/DVD-rom, 2. HDD)
-Started ASUS Update Utility (v.7.10.03), and loaded bios 2205 (from this site) In task manager it recognized it as "Update.exe", when you load the bios "from file" and push "flash", it changes to "WinFlash.exe" <- This is the task you need to kill after it's done with "Erase EPPROM"
-Loaded ASUS Recovery CD. When it rebooted it started "Bios recovery" immediately, however it couldn't find "P5WDH.ROM" as a valid file on the CD. I checked it on my other computer, and the file on my CD was named "P5WDHD.ROM", so first it wouldn't recover from CD. The bios recovery process goes in a loop between; "USB, CD-rom and floppy" until it finds the proper bios file on one of these units. Therefore I renamed bios 2004 to "P5WDH.ROM" (on my other computer) and copied it on a fresh floppy.
-Loaded the floppy to my main rig, and voíla - bios recovery flashed back to 2004.
Conclusion, before you do this, you should be prepared with the issues at hand, and make sure you got everything at hand. This worked great for me, and I'm thanking lord vader for that I have bios 2004 back again. My problem with "PCI-Device" popping up, and a bios that wouldn't save settings are history.
I will not be responsible for any damage done to your rig, by using my method - but I surely hope that it works for you that have had problems with bios 2103 and 2205.
Next time I will read a lot more about the bios before I flash again.
dont know if this helps any but im using bios 2103 no problems at all but i dont have a core 2 duo as im waiting for price using a 650 3.4. think that may make since. :confused:
Sooo...why are these bioses still in the startpost? :confused:
Because I have my own pc to sort out, that's why
I did the crashfree bios method by crashing afudos. Crashfree bios did not work reading P5WDH.ROM from a usb drive, it gave me 2 beeps, then 5 more beeps. I copied the asus cd to a folder, replaced P5WDH.ROM with 1707 named the same and burnt to a disc labelled 'P5W DH Deluxe' in iso format. This worked straight away.
However, I don't know if this fixed my issues or not yet. We'll see I guess (since stress tests were passing before, even with the issues).
Quote:
So - DO NOT FLASH to 2103!
Running BIOS 2103 for a week now and no problems to report whatsoever. Nothing different from 2004 either. :rolleyes:
I'll give 2205 a miss though! ;)
OH ONE MORE THING;
Are the people having the stability issues all using 4GB of ram? I am, and the dude on asus forums is, but no one else has sigs.
2 gb of memory here
2x1GB or 4x512?
I have 4x1GB, flashed back to 2004 after 2103 stability issues.
Running BIOS 2205 for 2 days here and no problems to report !
I have 4 x 1 Gb (as in the signature)
Upgraded from bios 2004 with afudos 2.11
Edit : I installed "Intel Microcode update" before a month at bios 2004
no problems with 2103 since release, about 2.5 weeks ago.
- P5WDH; Rev 1.02g, 66M0A
- QX6700 @ 3.0g; B3
- OCZ OCZ2G11002GK @ 500mhz, 3:5, 2 or 4gB RAM, depending on which OS, XP SP2 Pro or Vista Ult 64b
- Microsoft KB936357 Microcode update installed: http://support.microsoft.com/?kbid=936357
- no "new devices" issues, except the occasional "config" device appearing, which past BIOS'es have also done
will try 2205 and report back later this evening....
FYI:
- have been researching correlation between recent new BIOS'es and Intel/Microsoft microcode release
- only reference is comparing dates, so far
- assuming "CPU Patch" includes a microcode update and not just new processor ID/VID codes
- also assuming corrective microcode was released to manufactures weeks ahead of press date, April 10, 2007
- all guesses and nothing verified, but seems like 2103 and 2205 are likely candidates
- from AMI "MM TOOL" under "CPU Patch"
NO. uCODE ID PLATFORM CPUID UPDATE REV DATE SIZE
2004 - June 19, 2007
18 0016F982 01 06F9 82 2006/09/03 00001000
19 00166115 01 0661 15 2006/11/08 00001000
2103 - June 23, 2007
20 00166115 01 06FB B3 2007/03/14 00001000
21 0106FBB3 10 06Fb B3 2007/03/14 00001000
22 01067106 10 0671 06 2007/03/29 00001000
23 01067106 10 0671 06 2007/03/29 00001000
2205 - June 29, 2007
24 00167106 01 0671 06 2007/03/29 00001000
NOTES:
A microcode reliability update is available that improves the reliability of systems that use Intel processors
Article ID : 936357
Release Date : June 11, 2007
Last Review : July 9, 2007
Revision : 2.0
http://support.microsoft.com/?kbid=936357
Frequently asked questions:
Q: What issues are fixed by the microcode reliability update?
A: The microcode reliability update fixes the following issues:
• A possible Intel processor marginality.
• A potential source of unpredictable system behavior.
Q: How do you know if the system needs the microcode reliability update?
A: Although these issues are uncommon, you may receive a Stop error, or you may experience unpredictable system behavior.
Q: What errors occur?
A: You may receive a Stop error, or you may experience unpredictable system behavior.
Q: Which Intel processors are affected?
A: Although these issues are uncommon, the following Intel processors may be affected:
• Mobile: Intel Core 2 Duo mobile processor.
• Desktop: Intel Core 2 Duo desktop processor, Intel Core 2 Quad desktop processor, and Intel Core 2 Extreme processor.
• Server: Intel Xeon processors 3000, 3200, 5100, and 5300 series.
Q: If you install the microcode reliability update, do you still require the latest BIOS update?
A: If you install the microcode reliability update, you do not require the latest BIOS update.
Q: Does the microcode reliability update have to be proactively installed?
A: Affected Intel processor users must use the microcode reliability update.
****************
Around April 10th, 2007, Intel released a microcode update (BIOS flash to the rest of us) so resolve several major issues with how Intel
Core 2 series processors operate. Intel has provided a microcode update as a critical software fix. This Intel microcode update addresses an improper Translation Lookaside Buffer (TLB) invalidation that may result in unpredictable system behavior such as system hangs or incorrect data. OEM's are making available a system BIOS upgrade that integrates a new version of this Intel microcode to address this potential but extremely rare issue. While the occurrence of this issue is extremely rare, OEM's strongly recommends upgrading the system BIOS to an updated version. Intel has indicated that the microcode update has no known measurable performance impact and provides a complete and comprehensive resolution to this issue.
The issues can affect any workstation that uses Intel Core2 Duo desktop processor E4000 and E6000 sequences, Intel Core2 Quad desktop
processor Q6600 and Intel Core2 Extreme processors X6800 and QX6700 processors. While the implications of the issue are difficult to quantify, any of the following symptoms can occur:
* The system may stop responding to keyboard or mouse input.
* A system operating in a Microsoft Windows environment may generate a blue screen.
* A system operating in a Linux environment may generate a kernel panic.
i have installed a qx6700 cpu and it wont let me set the multiplyer past 10?
bios version 2004
Can't be that microsoft release. I actually installed that after I started getting the problems.
re bios 2205 , same issues here as other people , if bios entered cpu volts reverts to auto, and pci modem and on board sound enabled even though disabled in bios , was stable enough though and allowed multiplier adjustment worked on my qx6700 but i am back to the old faithful 1601 bios and its back to normal
2x1 GB | Corsair Dominator TWIN2X8500C5DF 2048MBQuote:
2x1GB or 4x512?
Interesting, a new entry showed up in the P5W DH Del CPU support chart:
I ran 2103 & now 2205 w/o any problems :/ 1st gen P5W & E6600, 2x1GB GeILQuote:
Core 2 Duo E6550 (2.33GHz,1333FSB,L2:4MB,rev.G0) ALL 2104
I have the 1st gen P5WDH, too. E6600, DDR2-800 2x1gig Patriot PDC22G6400LLK . Installed 2103 and 2205 without any problems.Quote:
Originally Posted by Grendel66
Also tried on P4 650, 2x1gig StarRAM 533 + 2x512mb Geil 533 kits. No problem on both BIOS.
I never do any overclocking though - because I'm sooo lame LOLz!
I also have installed 2103 and 2205 and I don't appear to have any problems. From reading the posts of people that do have problems they seem to have disabled devices in the BIOS, but aren't disabled because Windows is discovering the new devices.
The amount of memory I'm not sure about, but I have 1 GB 2x512MB DDR2800
Well atleast that's some good news, but shame I can't even use that bios. I hope they release a good working bios (for everyone) for the e6850 before july22.Quote:
Core 2 Duo E6850 (3.00GHz,1333FSB,L2:4MB,rev.G0) ALL 2103
I can't get S3 to work with this MB and Vista Home Premium. Has anyone else had any luck?
please delete this duplicate.
No problem w/S3 here
Vista Ultimate
2205 installed without issues, from 2103 (early P5WDH; Rev 1.02g; 66MOAG)
- imaged XP SP2 OS drive, precautionary measure
- prepped AFUDOS v2.17 with 2004, renamed to "p5wdh.rom" on floppy, precautionary measure
- note: Microsoft KB936357 update is installed
- flashed with EZFlash 2 from USB thumbdrive
- cleared BIOS with jumper (10sec)
- set BIOS settings and rebooted
- no new "devices" appeared, except the usual "config" device
- no problems with onboard sound staying at "disabled"
- tested 4gB (4x1gB sticks), no issues
- memory speed, temps, OCCT v1.1.1-b4, etc., all nominal
- did not test "multi" capability
- did not test Vista Ultimate 64b
I was having stability problems before 2205. Now all seems gravy.:)