Printable View
Can't totally blame them if they have other mobos which unlinks Vcore from EIST/C1E, even Asus own 965 mobos have unlinked options.
Are all 975 mobos from other brands doomed to behaving likewise ie. a chipset limitation? Or are the Asus P5W BIOS writers...
In BIOS 1901 EIST/C1E is not linked with Vcore.Quote:
Originally Posted by MacClipper
Hi, looks like in your sig you have an e6600 with 1.50vcore to hit your 3ghz, which is 333 fsb. What are your temperatures like on your cores in windows using CoreTemp at idle? How about with orthos or prime?Quote:
Originally Posted by AHolland
I had a similar problem with my e6600, but under water, I could push 1.60+vcore and get up to my sig's speeds. You want to stay under 70c at the cores under full load. Anything more, and you're slowly killing your proc. 85c and your thermal junction between the cores will melt.
I believe lawrywild has a similar issue with speeds, and part of why he started this thread, and why he is getting a quad g0. ;)
Hi, I can hit 3.0 with 333 FSB on STOCK voltage but if i go to more fsb even if multiplier on 8 to make it 2.7 i still cant get in. So is it possible that i need higher vcore to break 335fsb wall? I tried 1.3 but no luck, should i go as high as 1.5 to see if vcore effects fsb? Dont want to fry my e6600, revision b2 stepping 6.
Ok since it was just mentioned about the "cores" temp. I use the everest sidebar in Vista to monitor all my temps. It shows me the individual cores and then the overall CPU temp. When we speak of thermal limitaitons are the engineers measureing overall CPU temp or the individual cores?
Thanks to the people that responded to my question.
To answer, I have disabled everything that I could, including the hyperpath, etc. I hae also tried core voltages up to 1.5 with no luck. I did notice that the board does not seem to recognise my 320gb drive. I boot off of a raptor 150gb. I also have a couple of 500GB's in a mirror raid config. The SATA2 connector is not there so I have the 320gb drive connected to one of the other sata connectors.
My board is the 1.02 version but I have full control of the MCH up to 1.85, vcore control, etc. Is there some issue with the board 1.02 version.
And on the OE issue. Can someone lay down a quick paragraph on what this discussion is about?
Lawrywild could you append your first post to include some of these issues? It would make an easy point to point people to who are asking these same questions. Over time it would (and is already) be a go to point rather than having people like me asking the same questions over an over again. We can be told to read the forums, but with 225+ pages it becomes a lot to go through.
Thanks guys
Here is also a quick one. Where the heck is the motherboards serial number. I may send this board back to the manufacturer, but because I bought 2 at the same time from 2 different vendors, I have to figure out which bill to use.
In short, I made up a board from a friend and the local vendors only had one in stock at each of the stores so I had to run around getting two of them.
Thanks
Bro please try upgrading your bios to 2004. My board came with the 1901 and it was not nearly as stable as it is now with my current OC settings... I really believe the newer bios do a better job but that is just IMHO....Quote:
Originally Posted by AHolland
http://www.xtremesystems.org/forums/...postcount=5413Quote:
Originally Posted by AHolland
Okay, for arguments sake I ramped up and tested the system on some of the highest voltage settings.
If I put the vcore voltage to 1.6 volts the system blue screens. If I bring it back down again it's happy. In testing voltages between 1.3 - 1.5 there is absolutly no difference. I ahd previously tested these settings overnight and found them all stable up until passsing the 333SB level. It's interesting to see that the system became unstable if the voltages went too high.
I also tried putting up the voltages such as MCH to their highest levels (1.85). Again the system is okay until 333 FSB and then unstable past that.
I'm just going to have to accept that either the motherboard or the CPU is limiting the overclock. I have worked in the electronics world (design and manufacture of PCB's, robotic board manufacture etc.) for 15 years. It is extremely unlikely that a chip will work to a specific level and then completely not work at a very fine different level. There is always a grey area in between when chips get flakey. My system is telling me that there is some other outside influence making the 333 - 334FSB limitation. I just wish I could figure out what it is. I've checked and rechecked that all the components are properly soldered, seated, etc. There just can't be something about my board that would not show up on other peoples boards to make this specific limitation.
I forgot to add that the temps under load were in the low 50's
Arrghh
My system was never stable with 1.85 MCH. 1.75 is ok but again my mobo does not even like that but raising my FSB to 395 I have to run it there or it will not post... I like to keep it @ 1.65 and that gives me the most stability....Quote:
Originally Posted by AHolland
I used P5wdh and TRU 120 cooler, I want replace a new NB cooler, any body know how to remove bronze box in NB chipset?
Check out the link in my signature (P5W DH mod guide) or hereQuote:
Originally Posted by Zray
thx, I'm a newbie in this 4rum so I forgot search :D
Asus P5W DH Help
Im removed wrong jumper and now...
Chassis Intruded !
Fatal Error... System Halted!
And i can't do anything, no access to the bios, nothing. I read the manual,
but the Chassis Intrusion jumper is in default. Already claered cmos, but the same.:(
I don't now what to do.
Any ideas?
I can flash by holding F2+Alt
Tested Bios:
P5W-DH-ASUS-Deluxe-0065
P5W-DH-ASUS-Deluxe-160x
P5W-DH-ASUS-Deluxe-2004
P5W-DH-ASUS-Deluxe-2004-G0-45nm-Edition
P5W-DH-ASUS-Deluxe-2206
P5W64-WS-ASUS-PRO-0802
I have try, attempt and search in 3 day's
http://www.google.se/search?q=P5W+DH...&start=10&sa=N
http://www.xtremesystems.org/forums/...d.php?t=111129Quote:
Originally Posted by simri
hope this helps, read that post it seems the other folk had this problem and it is correctable....Quote:
Originally Posted by speks
Doesnt work :(
Tested with:
Flash Chip 1 P5W-DH-ASUS-Deluxe-2206
Flash Chip 2 P5W64-WS-ASUS-PRO-0802
how are you flashing??
Use a USB stick or floppy and make sure you use the pbnc switch??
so:
afudos \ip5wdh.rom \pbnc \n
Ctrl+Page UP
Boot block .........
Is the only thing i can do to flash
(USB Device)
P5WDH.ROM
not sure man, anyone else can chime in with any advise to help this dear fella...
I know many on this board have more than 1 rig but I was just wondering, I use this board because it has been my rock stable machine for 6 months now. Yet, when I check out the boards, especially with the Q6600 it seems like the P5W DH is a mediocre, mabe even poor overclocker. FSB of 333 vs. reported values closer to 400FSB on 965x and P35 boards. Any thoughts on why people stick with this? Cost? I have to admit that the thing that keeps me from moving to another is the hassle of moving my Windows platform. I like my machine the way it is now and reinstalling Windows plus working out all the bugs on a new board gives me a headache.
I guess the devil you know is better that the one you don't.
Why do you stick with this board?
Quote:
Originally Posted by simri
Did a quick Google and found this article about "loose/bent pin" chassis intrusion jumper:Quote:
Originally Posted by MarcusTaz
http://blogs.ittoolbox.com/windows/a...n-system-15608
If the jumper is not "loose" and verified it's over the correct pins: (see attached pic)
- unplug AC power
- CAREFULLY double-check intrusion jumper and pins for "tightness"
- check PCB mounting for odd shorts
- disconnect all USB devices, especially powered HUBs (in case of a "sneak-circuit" supplying +5sbvdc to intrusion circuit)
- clear BIOS with jumper (10sec)
- connect only keyboard and USB port if needed for flashdrive, else floppy
- reconnect AC power and pray
If all fails, guess its time to request replacement BIOS chip from ASUS Support?
Best of luck to you!
EDIT: just found more stuff using Google "ASUS intrusion" search term
http://www.digit-life.com/forum/0003/000387.html
clipped from above thread:
Dr Fat Chick - Junior Member
I had this problem with my brand new A7v333 and fixed it successfully:
If you look on the Asus web site you can find the fix tucked away in a faq - it suggests removing the existing jumper, rebooting (yes, you'll get the error but now correctly because the chassis alert pins are bare).
Now jump the pins with a NEW jumper cap (should ship with the board) and....huzzah!! immediate boot....at least that fixed mine.
It's still a bit worrying that this problem crops up on so many Asus boards though.
You can generally live with 333 max FSB, even if it is limited to 333 MHz, if you have one ofQuote:
Originally Posted by nrs250
- X CPU with unlocked multiplier
- 800 MHz FSB CPU
- x10 or higher multiplier 1067 MHz CPU
- overclock only in the "not much more Vcore" regions
What I found more annoying is that the max FSB dropped some more with 8 GB of RAM and Asus' BIOS antics. The board worked fine but as a battering ram it isn't that great. By 965p DS3 didn't do much better with 8 GB, BTW.
Is the audio bug fixed in larry's bios??Quote:
Originally Posted by miochza
or do you have to reset at every reboot?
Can someone post how to flash using AFUDOS211 and Lawrywilds 2004 bios..
I have not flashed using dos in many years..
I kmow I have to put AFUDOS211 on usb key then put bios on aswell..
Then what?
reboot then do what to get it to flash properly?
Thanks