totally awsome m8, exacly what i needed :clap: :DQuote:
Originally Posted by lawrywild
Printable View
totally awsome m8, exacly what i needed :clap: :DQuote:
Originally Posted by lawrywild
after i saw your pic i found itQuote:
Originally Posted by bichi
thanks bichi
i could've swore that option wasn't there before :o
Hello chaps, I'm in a bit of a fix and wonder if you can help?
I've recently bought the P5WDH mobo - love it, although to say it has it's quirks is understating things somewhat. Anyway, I was running the 2205 bios which I found totally stable, except that it would disable the sound every time I rebooted.
Hoping that an update would fix this, I tried the 2206 beta that has been mentioned. Asus Update erased the eeprom but then refused to load any bios file, even the backup of the original I made before starting.
Now my PC won't boot - won't even post. I switch on the machine and it checks both cdroms but won't load anything (the board I got was an oem version and didn't come with a recovery cd - in fact, it didn't come with anything). I've tried making a CDrom with only the P5WDH.ROM file on it and switching on with it inserted, leaving it for half an hour, but it hasn't done the trick. Am I missing something? Does it look for a disk with a particular name or something?
Is there
a) anywhere I can download the recovery CD
or
b) some way I can make one
or
c) anything else I can do to try and get this board to reload a rom?
I have a C2D so I'm guessing that's a sticking point - someone mentioned sticking a Celeron or old P4 in there just to reflash the bios, but I don't have one and really hope there's another way.
Any help you can give a n00b on this would be much appreciated.
Try this:
http://www.overclock3d.net/news.php?...oe_bios_issues
You could modify the .iso with a newer bios yourself (with PowerISO). Rename 2004 to the same bios as on this image and replace it, then burn)
EDIT: actually you can't replace the bios on the image, seems the bios is in a hidden sector of the disc. Should do the trick 'as is' anyway.
Thanks lawry. :)Quote:
Originally Posted by lawrywild
I burnt the image to a disk and switched on with the disk in the drive, but it doesn't seem to have done anything, even though I left it for a good 20 minutes. Is there anything else I can try (I'm guessing I'm not the only person who has experienced this problem :( )
Maybe put the latest bios on a floppy or CDR(W).
The filename must be P5WDH.rom
When you power on the computer, press ALF+F2 several times.
That should trigger the EZ flash program.
Thanks Ragdd.Quote:
Originally Posted by Ragdd
I tried using both floppy and cdrom with P5WDH.ROM file in the root of each, but have no luck. I get no output on the screen whatsoever and if I press CAPS or NUM lock keys, no lights switch on on the keyboard. I do have a core2 processor installed - am I going to have to buy a cheap Celeron to be able to reflash this?
Forgive me for the noob question,
But will a QX6850 (g0) work on the p5wdh?
If so, will it work at full speed? I know this is a 1333 FSB CPU....
Should do, unless it's a really bad board. Chances of 333fsb will decrease with 4GB ram (4x1) but it's unlikely you won't be able to run 333fsb.
I should get a Q6600 G0 sometime next week, I will give your bios a try, but I'm currently using 2103 w/out problems but I can't remember if it's supported.
Quote:
Originally Posted by dddan
Bummer!Quote:
Originally Posted by dddan
- all the best luck!
PREP:
- rename selected BIOS file to "P5WDH.ROM" and copy to clean floppy
- if no floppy, then copy to flashdrive with BIOS file renamed to "P5WDH.ROM"
- (never personally tested CD-ROM method)
- use PS/2 keyboard, if available
PROCESS:
- power off system
- unplug all external USB, eSATA, LAN, RS-232, etc.
- remove cards, except graphics
- clear BIOS (jumper, 10sec)
- insert floppy with renamed "P5WDH.ROM"
- if no floppy, connect flashdrive with renamed "P5WDH.ROM"
- (not sure if process will access CD-ROM drive...)
- note: use only floppy or flashdrive, not both
- power up system and hold "ALT-F2"
- recovery screen should appear and begin to seach for "P5WDH.ROM" file (see attached pic)
If the "ALT-F2" screen does not appear in reasonable time, (few minutes), then a replacement
BIOS chip will have to be ordered from ASUS. (if USA, 510-739-3777, ask for BIOS department)
- cost is $1 USD, with expedite shipping extra
- old BIOS chip must be sent back to ASUS, or $20 USD will apply
- some shops have replacement BIOS chips or ability to re-write BIOS chips
- BADFLASH.com is another alternative: http://www.badflash.com/
ASUS AFUDOS:
http://support.asus.com/technicaldoc...Language=en-us
- if you are technically savvy, HOT-FLASH, but thats another discussion
- part number below, about $2.73 USD
WINBOND PART: W39V080FA (PLCC 32)
8mbit, 3.3vdc, 1Mx8bits
Yea, if you know someone else with this board, hotflash the chip. It's really not hard aslong as you're careful taking out the chip without damage.
http://img166.imageshack.us/img166/2620/08052007ky3.jpgQuote:
Originally Posted by lawrywild
^-- there's my box with the g0 q6700. I'll be trying out your bios and the CPU in a couple of days, lawry. I need to pick up some more as5 + remover + prepper, and find some time to do it. Always a pain to clean up your old cpu and mounting plate from as5!
I read this post:
I just updated the BIOS on my Asus p5w dh delux to the latest 2206 Version.
For some funny reason. when i disable the onboard sound in the BIOS. And save. It keeps enabling again. It wont let me disable it.
Has this been fixed with any BIOS version, reversion or mod, including P5W-DH-ASUS-Deluxe-2004-G0-45nm-Edition (Modified by lawrywild)?
Also is anyone running PC2-6400 at 800MHz with this chip (Q6600) and board.
I want to sell my E6400 (OC to 3.2 Ghz) on BIOS 1703, update the BIOS, buy the G0 Stepping Q6600, but am reluctant to move to this if the BIOS versions are so flaky on a fundamental level.
Same problem exists by me...check also speedstep...problem is here it stays disabled...I have the 2103 bios now on my p5wdh and the Q6600(65nm)...Works oke for me...2205 and 2206 give the problem with sound card and speedstep...I hope that asus will bring out a good bios update...
Are you saying that with BIOS 2103....
No Sound Card Problem..
No Memory Issue....
Oh... and the Speedstep issue- not a major feature for desktops I guess.. (posted by Lemmingsbeest above)
Anyone have a Q6600 45nm with a bulletproof BIOS revision on basic items like sound and memory?
Chip is $300. I would like to have a working sound card for $300 and be able to use my Corsair Dominator RAM as well. It would not be OK not to run memory at 800MHz at least. I would like memory to run at spec minimum... leave OC'ing alone for now.
I don't know why Asus would claim to support the Q6600 with a major issue like that. Its like saying.. this car works fine....just don't make right turns....
I am running 1503 BIOS because I have a stable 3.2 GHz OC on an E6400 on WC.. For every 10 revisions ASUS puts out there there is like 1 real improvement.
Quote:
Originally Posted by bichi
Thanks guys - in fact, thanks to everyone who has replied and tried to help me.Quote:
Originally Posted by lawrywild
I'd really be up for hotflashing, except my only other system (which does happen to have a PLCC32 chip) has it soldered to the board, so it isn't gonna happen.
I'm going to try a couple of the local PC stores, see if they can reprogram the chip for me. If not, I've found a UK-based supplier who can ship me a replacement flashed with the revision of my choice in a couple of days. (It's a bummer having your system out of action for any length of time, isn't it?)
Anyway - to the poster who asked if they can run the 1333FSB chips on this board - I can answer quite categorically YES, it is certainly supported in rev. 2205. I was running the E6850 quite happily with 4x1GB sticks of Geil PC-6400 until the BIOS mishap (I'll never use Asus Update ever again - Asus should be shot for releasing such shoddy code!) Only thing I had to do was set the RAM to 833MHz and up the voltage by 0.5V when I added in the extra two sticks and it worked fine. (Strangely enough, I didn't need to touch the voltage at all until I added the extra two sticks, but I guess that's just another of the board's quirks).
One question - I'm using the onboard sound, and 2205 kept disabling this in bios everytime I rebooted (hence why I tried to flash to 2206). Does anyone know if this bug is definitely fixed in rev. 2206? Does the onboard sound stay enabled, or is it just the same and I can stick with 2205, which ran fine except for helpfully (ahem!) disabling the onboard audio?
lawry has a modded 2004 bios that my work even better
Q6600 is 65nm not 45nm m8, use the lastest bios and disable the sound card from windows, it wont bother you after anymore.Quote:
Originally Posted by nrs250
Quote:
Originally Posted by dddan
Hey is there anyway to get a socket soldererd to the mobo and a new chip to avoid this in the future?
It is actually already socketed on the P5W.
Just wanted to say that I have just done the Vdroop pencil mod and have gone from a Vdroop of 0.06 to 0.02-1 and it has helped lower my vcore to 1.4875 from 1.5125 @3.6 and be 12hrs Orthos stable small ffts. Will try to lower it further tonight! Big thanks for the info in this thread!:)
I have a few questions I hope someone can answer.
1. Is there a general overall problem with the P5W DH and the Q6600 CPU (G0)? Because I have a Q6600 which I know can overclock to 3.2GHz on air on a P35 mobo, but I can only get 3GHz (333x9) with it on the P5W using water cooling. I'm using the 2206 BIOS.
2. On P35 boards using the Q6600 multiplier 6, 7, 8 & 9 are available, but on this board even when I select multiplier 6-9, it always defaults to 9. I take it the multiplier can't be changed when using the P5W DH with the Q6600?
3. I would like to try an older BIOS, but can't seem to because it tells me I CAN'T LOAD AN OLDER BIOS. I tried using a floppy and AFUDOS, with same result.
Help would be appreciated. :)
I'M ONLY GETTING 3.2GHZ on air at the moment. no matter what i do it wont clock any higher and be prime stable. i think there could be certain settings needed or conditions i have yet to find. strange as i could get 3.6 easily with the e6600 installed instead of the quad....
I see this presently on the Commando 1404 BIOS too but for that mobo, it is a misreporting of speed on POST. The set multiplier actually works as can be seen using CPU-Z in Windows.Quote:
2. On P35 boards using the Q6600 multiplier 6, 7, 8 & 9 are available, but on this board even when I select multiplier 6-9, it always defaults to 9. I take it the multiplier can't be changed when using the P5W DH with the Q6600?
Anyway, do give 9 x 356FSB a try if you are still going for 3.2GHz. I am not sure if the P5W can do 400FSB with quads. Haven't had the chance to try it out yet with my SLACR, still testing it on my Commando.
I have a similar situation, but can only get 3GHz (9x333).Quote:
Originally Posted by purecain
So you have a Q6660 and can mange to get 3.2GHz (356MHz x 9 I suspect?) with the P5W DH? Is so, please post your BIOS setting.
Oh what BIOS are you using?
Are you 100% sure the BIOS is reposting it incorrectly and it's not the software (CPUZ) that's reporting it incorrectly?Quote:
Originally Posted by MacClipper
I tried many clock settings and none will work above 333MHz x 9 for the Q6600 CPU. Interesting enough I had an E6400 at 3.2 (8x400MHz). So it has to be an Q6660 + P5W DH issue :(
I don't know why but with the quads, the P5W DH won't allow you a high FSB.Quote:
Originally Posted by 5OH
If I tough the northbridge it's very hot so that could be the reason (having to handle more I/O requests due to more cores).
It will do 333MHz though giving 1333MHz effective, even without bumping up the voltage.
Quote:
Originally Posted by 5OH
the B3 q6600 top out at about 350fsb if you are lucky on the p5w motherboard, not sure on the new G0 stepping ones, i had a qx6700 and thatr would only go to around 320fsb on the p5w
Quote:
Originally Posted by GFORCE100
I guess it's just a limit of the board when it comes to quad cores, which I kinda expected :(Quote:
Originally Posted by GLENBOY
Time to upgrade this system to a P35 mobo I guess.
Could ppl with problems with this combination please investigate the vdroop? (use Speedfan, I find this fairly accurate).
Problems reaching high fsb only during load, or also in idle?
Maybe the vcore circutry on this board is too weak for 4 cores.
Planning a quad on this board, but not until autumn.
Regards.
101% sure on Commando, not even 0.01% sure on the P5W. You've got to do your own investigations for now. :DQuote:
Originally Posted by 5OH
btw, you can't compare dual and quad core FSB o'cing even on the same mobo. Prob. going to test out the SLACR on the DFI P35 next so can't feedback the max. FSB on my P5W for a while yet.
I´m getting 3.2GHz Orthos stable and 3.36GHz SuperPi 8M Stable.
I can help with (3). Get yourself afudos 2.11Quote:
Originally Posted by 5OH
http://drivers.softpedia.com/get/Oth...ool-2-11.shtml
this seems to allow you to go back to earlier BIOS revisions - later versions won't.
BTW my replacement BIOS chip should be arriving tomorrow. I will never trust Asus Update ever again! Been without my main rig since Friday night and I feel like I lost my right arm!
Not bad, 8 x 400 or 9 x 356?Quote:
Originally Posted by BulldogPO
Respectfully disagree. I run my system everyday @ 378 FSB and I can run it @ 395 if I wanted but I have to put to much Vcore into it. Your talking maybe an average possibly? I have B3 currently and a G0 stepping on the way and then I will know for sure if I can run 3.6ghz stable I am oonly looking for 400fsb and PC 6400 on the nose. If I can get those numbers I will be very happy indeed!Quote:
Originally Posted by GLENBOY
thats quite impressive.Quote:
Originally Posted by BulldogPO
What volts are you using?
? Are you even running a quad core? Don't expect to get the same fsb on a quad as a dual.Quote:
Originally Posted by MarcusTaz
Are you using a Quad core CPU? If so, I for one would love to know your BIOS setting :)Quote:
Originally Posted by BulldogPO
Thanks. I will give it a try later :yepp:Quote:
Originally Posted by dddan
I bet you are:Quote:
Originally Posted by MarcusTaz
1) Not running a quad core
Or/And
2) Own a very recent version of the P5W DH using a 975X chipset revision that's newer than C1.
replacing my Q6600 b3 with a go..... it isnt even prime stable @3.2 anymore.... i'm sure the board isnt helping but i cant help but think the G0 will give me better results. i used to get 3.6ghz 24/7 on my e6600....
Yes running a Q6600...Quote:
Originally Posted by lawrywild
Bios Settings are as follows:
ASUS P5WDH Dlx Overclock Settings
CPU : Q6600 Bx
DDR2 : Crucial Ballistic 4GB (4 x 1GB)
Bios : 2004
VGA : 1 ATI HD 2900XT 1GB DDR4
HDD : WD Raptor 150gb 16mb
PSU : Antec 650w Tri Rail
OS : Win Vista X64
Sound: Creative XFI Fatality Pro
OVERCLOCK (MHz) = 3406Mhz
BIOS SETTINGS
JumperFree Configuration
AI Overclocking set to: MANUAL
CPU Frequency : 378MhZ
DRAMM Frequency :758Mhz (1:1 according to CPUZ)
Performance Mode :Turbo
PCI Express Frequency : 100Mhz
PCI Clock Sync Mode : 33.33Mhz
Memory Voltage : 2.2v
CPU Vcore Voltage : 1.5
FSB Termination V : 1.4
MCH Chipset V : 1.65
ICH Chipset V : 1.2
--------------------------------------------------------
CPU Configuration
Microcode Update : Disabled
Max CPUID Value Limit : Disabled
Execute Disable Function : Disabled
CPU Internal Thermal Control : Disabled
Virtualization Technology : Disabled
Intel SpeedStep Technology : Disabled
--------------------------------------------------------
Advanced Chipset Settings (DDR2)
Configure DRAM Timing By SPD : MANUAL
DRAM CAS Latency : 4
DRAM RAS Precharge : 4
DRAM RAS To CAS Delay : 4
DRAM RAS Activate to Precharge Delay : 12
DRAM Write Recovery Time : 4
Hyper Path 3 : Disabled
DRAM Throttling : Disabled
As far as revision of my mobo, I have just purchased this from newegg this very month so I am sure I got the latest rev. :clap:Quote:
Originally Posted by GFORCE100
Oh and if the G0 stepping is not any better I will gladly keep this B3 and just settle for the 3.4GHz... But that 400FSB 3.6GHZ and 800MHz even #s would be nice. I am just anal like that...
Is that my 2004 you're running (G0/45nm edition)? :D
Or official :(
Quote:
Originally Posted by lawrywild
No Larry you were not nice to me when I asked you a question. :shakes:
:p: I will give it a try after I get the G0 stepping...
I had this same problem once before. Only one of the options worked for me, and I can't recall which it was. Floppy, CDR, or usbstick. But for sure it worked!Quote:
Originally Posted by dddan
Run CPU-Z or Sandra and tell us what revision of 975X chipset you got. C2?Quote:
Originally Posted by MarcusTaz
Rev. C0Quote:
Originally Posted by GFORCE100
What are the differences, I guess I have the older Rev...
After trying to find info on a C2 stepping 975x I cannot. I only see a C2 stepping on a 965
It would be useful to know - if you ever remember, be sure to post about it.Quote:
Originally Posted by nickfd
I got no output whatsoever (although my proc. is a Core2 and I have rev. 1.02G board) so I wasn't sure if it would be able to boot an old bios with this processor anyway. It did check both cdroms when I switched the PC on, although when I tried it with P5WDH.ROM on the root of a cdrom it totally ignored it. It also ignored the same file when I loaded it on a floppy drive.
Oh well, new bios chip arriving tomorrow so hopefully will be sorted out with that.
UK posters (who cannot get Asus to supply a new chip) might find this place useful:
http://www.biosflashuk.com/html/contact_us.html
------------------------
Incidentally, I found this link on the web for AMIbios - it suggests using a different filename instead of P5WDH.ROM when trying to recover from floppy, CD etc. I'll post it here as I think you guys might find it useful.
http://www.ami.com/support/doc/AMIBI...epaper_v10.pdf
I'll try it with my old (ruined) BIOS and let you know if it works.
One guy that got my same batch of q6700 on a phasechange cooling setup got 360x10 with 1.4 vcore. Attached is pic.
That's a good sign if it requires that little voltage to hit such a high speed. g0 rocks!!
Quote:
Originally Posted by GFORCE100
Can you confirm there is even a C1 let alone a C2 975X? I see no revisions of steppings on the 975x
has anyone updated their 975x chipset drivers? It appears they have addressed the SMBus device not installing correctly. It's been a while but it's finally fixed.
http://www.xtremesystems.org/forums/...ighlight=smbus
http://www.xtremesystems.org/forums/...ighlight=smbus
http://www.xtremesystems.org/forums/...6&postcount=44
even the P4GD1 has this problem LOL
Well, even though the driver updated (have to do it manually) the irq conflict is still there.
Sidnote:
I have more success manually updating (using the zip version) then using the setup file. It's tedious but I checked each system device and ide ata/atapi controllers to see what will take and what didn't. You usually have to check the universal serial bus controllers but I already updated that. (found in device manager).
I will have to check whether CPU-Z reports C0 or C1 on mine. C2 sounds like a P965 indeed, sorry.Quote:
Originally Posted by MarcusTaz
Quote:
Originally Posted by GFORCE100
Cool you got me really nervous there. After searching Intels site and various other sites, I could not even find a C1...
SLACR@333FSB x 9, Vcore at AUTO with EIST/C1E activated - note the rather low Vcore on this mobo detected as by the onboard sensor, rather bad news for those like me who have to use AUTO Vcore for EIST/C1E. Thought someone did say 2206 gives 1.4V at AUTO (kindly confirm) which may make o'cing with EIST/C1E easier.
http://i173.photobucket.com/albums/w...48_OCCT_OK.jpg
http://i173.photobucket.com/albums/w...3h03-VCore.png
Mine here is C0Quote:
Originally Posted by MarcusTaz
Ah, found the 2206 1.4V reference here but sadly, the poster isn't using a quad.
http://vip.asus.com/forum/view.aspx?...Language=en-us
So is it true that with the 2004 bios update the P5W DH supports Intels 45nm?
Got my Q6600 G0 but I'm on baby duty (watching my daughter) so my wife can go take her test (College) and my daughter refuses to take a nap so I will not get a chance to play with it today. I go to bed early because I have to be @ work @ 4:30am -- so maybe tomorrow.
Please let me know how she OCs. I have my G0 on order and would love to know how it does compared to the BxQuote:
Originally Posted by nicepun
lawry has a 2004 bios that will work with the 45nm cpus and the go.sQuote:
Originally Posted by RangerXLT8
Not sure if you were looking for Q6600 G0 only, or just any quadQuote:
Originally Posted by MacClipper
- 2206 BIOS; C1 and EIST enabled
- QX6700 B3 @ 3g
- OCCT v1.1.1.b04 (short 10min test)
I tried the 2004 modded and regular and 2103 and for some damn reason all I get is Auto for vcore (I know to disable EIST and C1E).
Q6600 G0?
My bios works fine otherwise yeah? No microcode errors or anything.
No idea why it's doing that though. Did you load setup defaults first?
I'm reflashing through DOS with old Afudos 2.11 and the /pbnc /n switches.Quote:
Originally Posted by lawrywild
Edit: Just tried with 2103 and no go. I will try with the 2004 modded later or tomorrow.
Thank you very much for the info bichi, precisely what I wanted.
Tried out 2206 on my G0 Q6600 but too bad, Vcore values remained exactly the same as 2205 previously, varying between 1.15V idle and 1.25V load. So it looks like they upped the Vcore for B steppings only. Or perhaps diff. P5W revisions play a part, mine is the earliest 1.85V revision.
Enable it then need to disable Speed Step againQuote:
Originally Posted by nicepun
I was reading the documents before.Quote:
Originally Posted by nicepun
Flash with
Quote:
afudos /i2004.rom /p /b /n /c /reboot
Quote:
Options
The optional field used to supply more information for flashing BIOS ROM. Following lists the supported optional parameters and format:
�� /P Program main bios image
�� /B Program Boot Block
�� /N Program NVRAM
�� /C Destroy CMOS after update BIOS done
�� /E Program Embedded Controller block if present
�� /K Program all non-critical blocks
�� /Kn Program n’th non-critical block only (n=0 - 7)
�� /Q Quiet mode enable
�� /REBOOT Reboot after update BIOS done
�� /X Do not check ROM ID
�� /S Display current system’s BIOS ROM ID
�� /Ln Load CMOS default (n=0 - 1)
L0: Load current CMOS optimal settings
L1: Load current CMOS failsafe settings
L2: Load CMOS optimal settings from ROM file
L3: Load CMOS failsafe settings from ROM file
�� /M<MAC Address> Update BootBlock MAC address if exists
�� /R Preserve all SMBIOS structures during NVRAM
programming
�� /Rn Preserve specific SMBIOS structure during
NVRAM programming
Whatever you read is wrong. The bios reads the VID of the cpu under load and uses 1.1625v idle. These are the EIST values. P5WDH Bios revision never changes stock vcore. The cpu itself determines this via the VID, which can be read in coretemp or everest. And by the way, lower VID is generally better.Quote:
Originally Posted by MacClipper
... except when it comes to trying to o'c it higher cos this chip is confirmed stable at 3.2GHz at 1.30V on my Commando (lovely independent Vcore/EIST-C1E options).Quote:
Originally Posted by lawrywild
Nonetheless thanks for the consolation, lawry. :D
3GHz is enough, 3GHz is enough, 3GHz is enough... my new chant. lol
Coretemp with EIST/C1E, load vs no load
http://i173.photobucket.com/albums/w...R/Coretemp.jpghttp://i173.photobucket.com/albums/w...etemp_Idle.jpg
Dude, there are no exceptions... (EDIT: Oh nevermind, I understand you now, you were talking about the lower VID is better comment. The information below is still useful though, so I'll leave it)Quote:
Originally Posted by MacClipper
The change in vcore your getting from the VID is the result of Vdroop.
You can do what I did and Vcore mod the motherboard. Thus, I can run EIST but increase vcore above stock. (this also increases the EIST vcore by the same fraction too)
for example. The vcore mod provides a vcore 18/15 x Your VID.
So 18/15 x 1.300v = 1.56v under load (without vdroop)
EIST VID is 1.1625v so you will get 18/15 x 1.1625v in IDLE mode which = 1.395v
Did the Vdroop for my Commando test mobo (easy, works great) but the P5W is casing installed so kinda PITA to pencil it so willing to live with 3GHz for now. Waiting for the incoming X38 anyway.
:)
Not vdroop, vcore mod. Solder a pot on ;)
Lookie here:
http://img3.shareavenue.com/getimage...b97b7732aa7e21
FYI:
- whether P5WDH BIOS can override processor VID values is another story, assuming all manual
- tough to defeat/exceed PROCHOT# and Tj and override processor shutdown limit with BIOS, Vmods, in any case
- and QX6700 VID is higher than Q6600 B3 and appears to be even lower with Q6600 G0
From Intel Q6000 Series Datasheet, page 18:
3. Each processor is programmed with a maximum valid voltage identification value (VID), which is set at
manufacturing and can not be altered. Individual maximum VID values are calibrated during manufacturing such
that two processors at the same frequency may have different settings within the VID range. Note this differs
from the VID employed by the processor during a power management event (Thermal Monitor 2, Enhanced Intel
SpeedStep® Technology, or Extended HALT State).
REF LINK:
Intel® Core™2 Extreme Quad-Core Processor QX6000Δ Sequence and Intel® Core™2 Quad Processor Q6000Δ Sequence Datasheet
http://www.intel.com/design/processo...hts/315592.htm
Tried but luck.Quote:
Originally Posted by lawrywild
Tried but no luck.Quote:
Originally Posted by sbinh
I think this is where the problem lyes....:shrug: :shakes: Mine is an earlier version 1.85v Rev1.02g. Dammit I don't feel getting another mobo right now.Quote:
Originally Posted by MacClipper
Not sure what your point was, but P5WDH can not alter VID values and we are talking about AUTO setting in bios (EIST enabled).Quote:
Originally Posted by bichi
I don't get what you mean by qx6700 vid is higher than q6600 b3. VIDs are nothing to do with steppings. VIDs are assigned individually to each cpu depending on it's stability at what voltage at stock clocks. I.e. Not all q6600 b3 have the same vid, or qx6700 or whatever cpu.
Hmm, I have an even earlier 1.65v revision. No G0 yet but hopefully in a few weeks.Quote:
Originally Posted by nicepun
(I will be using Auto vcore anyway. EIST FTW! Vcore mod FTW! :D )
Hey everyone,
I haven't kept up with the 200+ pages of stuff there is here, but I've searched the internet High and low for a fix, and it seems I'm not the only one with the problem, but I have been having pretty heavy problems with the whole LAN portion of this board, from both the 2 Marvell Gb NICs and the Realtek Wireless Adapter. I have sudden and short disconnects at random intervals, be it in games, applications, or simply browsing the web. I have tried many different driver versions for both the WLAN NIC and the 2 Wired NICs, even though evidence points to something other than drivers since the problem applies to both network components. My own personal (uneducated, even though I'm an IT graduate, I'm not really into hardware) guess is that the Chipset falls out of sync, but that's most probably a wrong guess.
Here's hoping someone knows something about this and would like to share :D
Specs:
Core 2 Duo E6600
P5W DH Deluxe (obviously) with the most recent drivers from Intel for the 975X chipset
2x1024Mb Corsair RAM (I can't remember the whole product number and stuff, and unless it's really useful I can't be bothered to dig up the exact name)
ASUS GeForce 8800 GTS (up to date drivers, forceware from week of July 22th)
Running Windows XP SP2 somewhat up to date (mid-june)
Stock Fans (but no temp problems whatsoever)
Everything is at stock speeds/memory rates/etc. No OC at all, and no intention to do so.
Thanks for reading and don't hesitate to ask for more info, I'm soooo eager to rid myself and most probably a few of us of this problem.
Cheers,
Chlikaflok
Max OC E6600
ASUS P5W DH Deluxe
http://members.chello.cz/dj_studio/p...cpuid_3726.jpg
CPU Watercooled
Hyperpatch 3 - Disabled;Memory Voltage 2.20V;Chipset 1.55V;PCI Clock 33.33MHz
does anyone have answer as to why speedstep is causing sound and video stuttering problems for me? this also occurs at stock speeds so isnt a result of too low voltage (I think).
Is it possible that whilst the cpu is jumping between clock speeds it causes a stutter.
no, EIST shouldn't do that. Check the DMA status on your host drive instead.
Hi all.. So last night I took out my e6600, cleaned off the AS5, and installed the g0 q6700 that arrived. Prior to doing this, I had installed lawry's g0 200(4/6?) modified bios on the mb, and was content with it working OK.
So when I booted the box, I went into the bios and started looking at the hardware monitor page. I think it was like 1.21 or 1.23vcore by default, and temperature was 24-25c at idle on my water. I started by mildly overclocking, and got it to post at 333mhz*10 at 1.45vcore. I didn't go into the OS at all, just sticking in the bios.
Then I upped the vcore and went up to 366x10. Still posted fine. Then did 400x10, and did 1.50vcore. Black screen, no post. After several hours of clearing the CMOS many, many times, and doing so without the battery in the mb, I finally got my bios back. I decided to go back to 333x10 and see if my os worked, testing the OS for the first time.
Bad news, nope. It would start booting, give the windows xp splash screen, then bluescreen immediately, and reboot. I couldn't tell what the msg was, since it rebooted so fast. Safe mode did the same thing. Then I tried Vista Ultimate 64bit, which I had on the same hd in a dualboot scenario. Same thing.. It would die shortly after splashscreen.
I was thinking worst case scenario.. something happened in the hd, and it corrupted the OS. K, so I formatted (reluctantly, since there was some stuff I didn't have backed up), and went to install XP SP2. It would finish installing the console/text portion of the OS, and when you reboot to have it go into the GUI, it would reboot constantly. Broke.
Testing the memory with memtest86 showed that there was no errors after an hour of crunching, back at normal 2.66ghz, with auto vcore. I tried upping the voltage to the cpu and it still made no difference. I also upgraded the mb bios from lawry custom to 2206, which had no impact or change on functionality, or lack thereof.
So I'm kinda stumped. I'm going to take out the q6700 tonite and pop my e6600 back in to see if it works. I don't know if the problem is the mb or the cpu may be a lemon, or got messed up while I was testing for higher oc? Either way, i'm frustrated.
I'm happy that other people posted pics with their g0's working on our mb, so at least I know mine SHOULD work. But I don't understand why it's not.
Yeah I had the scenario you're having with my QX6700 at 10x333. It would work at 11x300 but not 10x333. The same situation with Windows XP not loading and rebooting at one point during start-up (though I'm sure the latter is because I had the restart after BSOD option enabled in device manager).Quote:
Originally Posted by nickfd
Finally I figured out one had to disable EIST and C1E for it to work, this was with the 1506 BIOS. Since then I just disable both regardless what BIOS I'm using when overclocking the QX6700.
So am I the only one with a P5W DH and a Q6600 G0?? Anyone else having problem with vcore value staying "Auto" no matter what BIOS version and settings you use? Thanks, it looks like I'll have to go with a P5K Premium.
Well, I can't get into any OS to disable the autoreboot, and now after format and start of xp install, the gui part of the install doesn't work.Quote:
Originally Posted by GFORCE100
My CPU settings are:
Microcode Update : Enabled
Max CPUID Value Limit : Disabled
Execute Disable Function : Disabled
CPU Internal Thermal Control : Disabled
Virtualization Technology : Enabled
Intel SpeedStep Technology : Disabled
^- all the same stuff I had on my e6600 that worked an hour before I took it out and popped in the q6700.
And also remember that even when not overclocking, I can't get an OS either. So like I said, I think it must be the CPU that's messed up, or my frankenstien p5w dh deluxe that finally threw in the towel. If that's the case, Im gonna get a p35. :) I'll update after I put the e6600 back in tonight after work.
So the question still stands can* the P5W DH work with Intel 45nm?
I know the badaxe 2 does,,,,,,,,
Quote:
Originally Posted by nicepun
I assume you mean G0? I am waiting on www.frys.com to sell out their old stock before they can ship me a G0, then I will be able to let you know if I experiance the same issue. Did you try Larry's modded bios?
I know what you mean. I had that problem with the wireless. I couldn't fix it so I just bought an abit airpace pci-e x1 card and it's perfect. (also bought a huge aerial which gets 100% signal constantly)Quote:
Originally Posted by Chlikaflok
No problem on my rig, I can change the Vcore once C1E/EIST is disabled - tried with both 2205 and 2206. However, I am using Auto cos I love C1E/EIST power/heat reduction. Have you tried clearing the CMOS by removing the battery for a few mins.? Have personally seen weird disappearing options with corrupted CMOS settings.Quote:
Originally Posted by nicepun
@nickfd - have u tried the FAQ advice to disable all the unnecessary onboard devices eg. 1394, audio etc.. while installing yet?Quote:
the gui part of the install doesn't work
Yep. Ive been a user on this thread since page 145 or so, when I bought it and got my e6600. Audio, 1394, and bottom nics are disabled. jmicron is disabled as well. All the basic debugging is done, and all that's left is swapping the q6700 with the e6600 to cross out motherboard or cpu.Quote:
Originally Posted by MacClipper
What I don't understand is why memtest86 works fine when I boot it, and also the text based installer, but not when the graphical part of the OS wants to start.
Hmm i really hope my 8800gtx isnt going.
What rev is your mobo? I cleared the CMOS but not by removing the battery, I used the jumper. I will give it a try by removing the battery.Quote:
Originally Posted by MacClipper
Additional Comments: NO GO!! I'm still getting the same "Auto" value regardless. I haven't tried 2205 but if 2206 doesn't do it I doubt 2205 will make a difference.
nicepun, the manual has the correct way to completely clear cmos.
:shakes::down: No go my friend. :shrug:Quote:
Originally Posted by lawrywild
nickfd
So does the P5W DH work with your E6600 or is Windows XP doing the same thing?
Sounds very odd, as if some capacitor was broken off.
I've got a P5W-DH, but my IDE pioneer burner gets detected on boot up, but then after some time it just disappears from the list in My Computer.
What could be the problem?
Also a few months back, i attempted to boot up my computer and i heard something pop and smoke was coming out of a chip. It is circled in red in the picture.
http://img410.imageshack.us/img410/2743/1198law4.jpg
The things i have discovered from the pop, is that the 2 fan connectors next to the chip don't work...
What is that chip supposed to do?
IC Regulator or power output transistor. Call Asus and setup an RMA, if you want a crossship so you do not have any downtime you can arange that with them if the mobo is a current model... Always worked for me...
That's a mosfet; http://en.wikipedia.org/wiki/Power_MOSFET
Well, I took off the cpu, and was shocked to see what happened. It looks like there are ~25 charred pads on the CPU, and the corresponding pads on the MB are charred as well.
I was able to clean it up a little bit, and some of the substance came off as well when I scraped at it with a knife. However, it leaves little marks where I scrape, so I don't want to do that.
I'm figuring when I was cleaning the board, some as5 cleaner made its way between the chip + mb, and oxidized the connections when the board supplied it with power. I don't know for sure, cause I've never seen anything like this before.
I took the chip slightly better than what you see in the pics, and put it on the board and put my waterblock on the cpu. I was able to actually see the board+cpu POST, but due to my absolutely WONDERFUL luck, the pump on my water reservoir decided to die on me.
Being too afraid to see if it worked, cause I went into the HW Monitor and saw the temperature just rising without stopping, I shut it down. As you guys with watercooling solutions know, the cpu block is very small, and isn't designed to run very well without any kind of flow.
So I guess my plan now is to toss the motherboard, get a p35 (any suggestions?), and go air cooling for a little while. I don't have the extra cash to spare now to get a whole new water solution, which i desperately need, cause the pump going is just the latest of problems that have been plaguing my crap boxset water solution.
If the CPU still causes me problems when I get the new mb, I'll cross my fingers and HOPE that intel takes the chip in for warranty. I just don't know how to even approach them about what I see on the cpu without having them void my warranty for misuse or something.
Sigh. Stuff like this always happens at the worst times. I leave on a cross continental vacation in less than a week, and I really need this time to research plans, options, and things to do. GRRRRRR. </rant>
pics:
http://img530.imageshack.us/img530/1...2007275dt6.jpg
^- look at the bottom pins, which lined up to the left pins on the image below (mb)
http://img528.imageshack.us/img528/3...2007276sr1.jpg
^- look at the left part of the board.
Judging by the INSANE amount of thermal grease I see on the underside of the socket mounting clip, I think we know what your problem is.
You put too much thermal paste on there, and when the CPU was clamped down it oozed into the socket.
This is user error, and both Intel and ASUS are going to say sorry, no warranty.
A little dab will do ya.. literally.