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:
Printable View
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.:)