Yes I 2nd that opinion, and what's with all the dust? Seems it needs a good blow-out.
Printable View
First off..is there a stable bios that does not enable the hd audio on a reboot?
Second how to flash to an earlier bios, I am using 2006 I tried to go back to earlier 2004 or 2005 tried 2103 It won't let me says it's older than the 1 I'm using..using ez-flash
I wantedto try Larrywild's 2004 bios but it won't let me..
Third, I was using Vista 64bit but started having major issues with programs crashing randomly, working fine 10min earlier then not starting up, windows error reporting poping up all the time..
I was using 4G ram Q6600 see sig.
So I have since reinstalled Vista Business 32bit and was having the same issue again, so I took out 2G ram and while doing that I was reading that by using all 4 dimms/4G I had to run ram at 667 only..What should the default voltage be for Q6600 1.24 and how high is safe? also my Corsair Voltage what is the default voltage for that 1.8-2.0 or higher and how high is safe?
It's Corsair XMS2 6400 timings of 5-5-5-12
I was forcing them to run 800 all the time before, and I swear they were working fine before at 800, but now not..
So right now everything is running perfect, Vista 32bit 2G ram running 800, Q6600 and bios 2006 except the HD audio bug..on reboot.
and my default stock score of 3dmark06 is now 11000, before I only get 9200-9400..??Vista64bit and 4Gram.
Also did a bit of case modding last weekend..
Bought an Antec Nine Hundred case..nice case except it has piss poor cable management, so I took my dremel to the back of it and made some exit holes to hide wires..cut a hole in the bottom of it to mount the PS the right way..
Now motherboard temps are 31 degrees and cpu shows 23 according to Everest..
memory stuff
already been suggested the drives are defenitly in dma mode, or its been reported wrong, althoughit was acting like pio mode it isnt the case.
I have noticed tho that when not using ahci or raid it just uses the slow microsoft drivers I guess intel dont deem it worthy developing drivers for the normal ide mode. I plan to test it on multiboot to see if the stuttering is gone in ahci with eist disabled.
So, should I update to bios version 2206, or not?
Well, I don't expect ASUS to replace my mb, since I already voided the warranty by putting on the nb cooler. However, I'm crossing my fingers with Intel.
Yes, I guess I did put a bit of a glob of as5, but when I took the chip out of the socket, there was no paste on the bottom of it.
And like I mentioned, I got it to post and begin starting up, but it got too hot with my pump dead, not moving the water, so I had to shut it down. The CPU *may* be ok if I can clean off the oxidation properly.
I'll still be trying to rma it tho.
I'll update with progress as it comes.
Can someone please remind me what the really good, huge, air cpu cooler was that people got close to watercooled temps and overclockability with?
Was it the Thermaltake CL-P0114: http://www.newegg.com/Product/Produc...82E16835106061
Or Zalman CNPS9500: http://www.newegg.com/Product/Produc...82E16835118223
Or the Tuniq Tower 120: http://www.newegg.com/Product/Produc...82E16835154001
K, found someone with the Thermaltake, lapped, getting REALLY low temps. Gonna get that. http://www.xtremesystems.org/forums/...d.php?t=152722
Tuniq Tower 120
Thermalright Ultra-120 Extreme
Fornowagain, the IFX-14 was a big disappointment and is inferior to the Ultra-120 Extreme... (which is cheaper and smaller)
PS: I still haven't got a refund from Eclipse.... :/
URL says Thermaltake :)
I ordered that + Gigabyte p35 dq6 motherboard. After checking a lot of reviews and a bunch of threads on here, much of the highest clocks were on that board. It sucks that ddr3 isn't backwards compatible with ddr2, so you have to pick one or the other when you're looking into new boards.
With the price of ddr3 now, (559$ for 2gb), I think i'm gonna stick with ddr2 for now.
I contacted the company I bought the cpu from, and they're going to ship me a new one, and I have to send mine back to them after I receive it. So I figure I will try to get the rest of the oxidation or scorch marks, or whatever they are off of the chip before I ship it back. Hopefully they won't make a fuss about it!
@fornowagain - lol that's intense heh.
I know the link says thermaltake but the thermalright ultra-120 extreme is much much better than any thermaltake heatsink.
for you patato salad take the 2004 mod by larrywild or beta bios 2103 the others is not running so great and i just flash it with my usb pen in dos no problems back and forward with afudos 221...
or use a floppy good luck
Just got my Q6600 G0 L24A760 in, testing it at stock volts currently, at 3.0 ghz prime stable 10 min so far. My VID is 1.2875 and my load volts are bouncing between 1.25-1.26. 2206 bios.
Water, load temps are ~38 C, 38 C, 43 C, 43 C at 21 C ambient
Can you try 400 FSB x9 for a 3.6Ghz and let me know if that proc will do it?
Hey, i have a huge problem with my p5w. Im hitting fsb wall of 335 and its unstable that high. Currently im at 330x9 so my e6600 is around 3.0. I tried everything and i cant solve the problem. My bios is 1901, is updating it gonna help it anyway? I didnt get around updating bios because im out of floppys. My cpu stepping is 6 revision b2 vcore at 1.280.
Ram gskill 1gbhz at ddr 1000 4-4-4-12. Mobo revision is c0. Did i get unlucky on my mobo or something is wrong with it?
Well I am expecting my Q6600 G0 in 4 days.
I upgraded to BIOS 2204. All is well.
Anyone have a Q6600 G0 running at stock stable on 2204? (not the modded flavor).
Should I go to the mod because why (someone help with this point)???
I have a question about the BIOS flash utility:
1) I used a Win98 boot disk on a USB floppy (set BIOS up right to boot from it) and then inserted a second floppy with AFUDOS 2.11 on it (second floppy be so I made sure room was not an issue). I was able to type:
AFUDOS /oOLDBIOS1.rom
as per page 4-6 in the manual and it worked as expected.
Next:
I tried using a USB stick formatted in WinXP as an MSDOS boot disk (not the 98 version I describe above), I then put AFUDOS on it and repeated the procedure. It would not work. The USB key was a Sandisk 2GB U3 key. No go. I kept getting drive "write errors" on the AFUDOS /oOLDBIOS1.rom command after the flash was read. It seems to have an issue writing to the USB stick.
I even used this to prep the key and used Sandisk's U3 uninstall utility to make sure the key is clean and free of the U3 crap that Sandisk loads on it.
Can anyone tell me how you went about
1) getting a USB key to work with AFUDOS
2) what key did you use (if it even matters)
3) how you prepped or formatted the key.
4) what Windows boot disk you used (98, XP etc)
I will save the rant that we have a damn QUAD CORE processor and we are using 1990 floppies to flash mobos in 2007.
P5WDH; Rev 1.02g; 66M0AG; 1.65MCH; BIOS: 2206; Purchased: Jul 29, 2006
- setup for testing only
- VCore set to 1.25vdc
- C1E and EIST both disabled
- CPU-Z v1.40.9b (cpuz.ini - Sensor=OFF to show Core VID)
- reboot and BIOS pix taken
No problems with VCore or any other settings with any BIOS
- maybe the newer revs are the ones affected?
Where I can see what rev is my P5WDH?
Not sure if you understood correctly but I think he meant the Vcore can't be changed if C1E and EIST is both enabled.
It happens on mine as well, only BIOS up to 1602 I believe didn't have this bug/issue.
Even if I reboot, I can't change Vcore unless I disable C1E & EIST.
Yeah, I kinda wish I would have looked at your post before I clicked the trigger, lawry. But that's ok. As long as I don't have fitment issues (which should be ok), then I'll be happy with this Thermaltake when it arrives on Tuesday.
Unfortunately, I can't. I cut the heatpipe when I removed the stock NB block, and after a week or two of running the Spirit 2 NB cooler, one of the two hooks that's holding it in pulled out from the mb. Thankfully it was the bottomright one, nearby the memory, and I was able to stretch the mounting legs and pull it to the hole that the motherboard gets mounted in.
It's okay though. This motherboard has done me proud, and done me well in the 8 months I've owned it. It will rest in piece(s), and will always have a spot in the back of my mind, since it was my first attempt at watercooling. :)
Glad to know that stock volts can do so well with the g0's! I can't wait to get my new board and chip and begin playing around again. :)
Not looking good... I can post at 400 x 9 with vMCH maxed (only 1.65) but it crashes when it starts loading windows. I tested in 100 mhz increments (from 3.6 down to 3.2). It's the same (posting but no windows load) all the way down until 356 x 9 (3.2 ghz). At 3.2, windows will load but gives me a BSOD about memory management. Clearly 975X is a failure when it comes to quads. I'm sure the 1.85 vMCH will help for those who have the option, but unfortunately it looks like its ~3.0 for me, until I get a new x38 board.
what are your bios settings? Have you tried my settings?:
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
I can hit 395 FSB and boot into windows vista @ 3.55 ghz but I have to pump in 1.6vcore which really yields me 1.55 vcore and run FSB termination of 1.5 and MCH of 1.65 but my temps are way high and even though it is stable surfing www, it is not stable with orthos and unpredictable in gaming. 400FSB I can boot in with same voltage settings but it is just to unstable.
Please try these setting if you can and let me know...
This is a quad core? I'll test out those settings, all the voltages are similar so I'm doubtful that it will change much...
EDIT: Wouldn't boot windows at your settings.
Ah man that is a shame.. Can you try of 1.75 on you MCH??? Or you have an older rev?
Well I bought it from www.frys.com and they have a 30 day refund policy so I am gonna get the G0 see what it can do and if it will not run 400FSB 3.6Ghz and if it does not perform better then my current B3, then I will keep the B3. Thanks for trying my settings...
BTW, just flashed my BIOS to the lawrywild 2004 modded one. Works fine with my Q6600 G0.
happ, I personally haven't had the problems you've described on BIOS 2206. But also, lawry's 2004 G0 bios is working great for me. So, I would say, try out lawry's 2004 BIOS if 2206 gives you trouble.
Unfortunately, it isn't much better than 2206 for me. I still can't get windows stable at 3.2 ghz. I was thinking about pencil modding for higher vMCH, but my multimeter's tips are too big to measure the required resistor with any accuracy and I really don't want to do it blindly.
Hi Again,
I posted some questions regarding overclocking back in the mid 180 pages but never really got an answer I was looking for. I'm trying again in case something new has popped up since then. Here is my issue.
I can overclock from a FSB of 266 up to 333 with no issues. One fsb above that and my machine locks up. I've tried jumping past that with dozens of different FSB up to 375 with no success. I did that as some boards seem to have a hole at one spot where they are unstable.
I can play with different memory timings with no problem, but raise that FSB above 333 and the system dies hard. I really was expecting a zone of flakeyness before the hard die. I've tried a number of differnt bios's from 16-20 and settled on 17 for no real reason.
I just don't know why everyone is getting reasonable overclock..3.2-3.6 GHz but I can only get to 3.0. Yes, I could have a wimpy cpu, but I am really worried that I am missing something. Voltage changes on the cpu makes no difference at all. It's that damn 333 vs 334 wall.
Anything that you guys think I can try?
Thanks in advance.
wtf?
- you mean you hayseeds are expecting/complaining about VCore adjustments with C1E/EIST enabled?
- clearly states that C1E and EIST must be disabled before VCore can be adjusted (see attached clips)
- and here I thought ya'll were :banana::banana::banana::banana::banana:ing about AUTO with C1E/EIST disabled..... LOL!
- ahh, OK
- will try with Q6700 G0, IF it ever gets delivered
- (been waiting for almost 3 weeks from supplier....)
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...
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?
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
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
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 here
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=111129
hope this helps, read that post it seems the other folk had this problem and it is correctable....
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?
Did a quick Google and found this article about "loose/bent pin" chassis intrusion jumper:
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 of
- 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.
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
Have you made the usb drive bootable?
This is my favourite guide: http://www.weethet.nl/english/hardwa...omusbstick.php
Once you made it bootable, put afudos.exe and 2004.rom on the drive.
In bios change the usb drive in usb configuration to "FORCED FDD"
Then save changes, tap f8 on POST and select to boot from usb drive.
Once dos is loaded, type:
afudos /i2004.rom /p /b /n /c /reboot
note the i after the /
Hi guys, I've been playing with my OC settings now that I have my watercooling kit installed, but I've been hampered by this damn 360 FSB wall. I've tried putting my RAM on SPD settings, but that doesn't help. (Strangely, when I tried the SPD setting at a lower FSB speed that worked, it didn't boot at SPD, but at the speed that was selected right beneath the FSB setting.) So, anyways, I've turned off all the extra memory options, the CPU options, etc. I've gotten my system to boot and run two Orthos instances for 10 minutes with no problems at FSB 350, RAM at 875mhz 4-4-4-12 with 1.325 vcore and 1.65mch, but upping the voltages to get higher FSB aren't working at all. I've tried doing all the things I could find in this thread and elsewhere, but nothing has helped. All I want is 400 FSB. That's it. I'm not trying to break records, I just want to run 1:1 with tighter RAM timings at DDR2-800. I'm using the 2004 BIOS, by the way. Was I a lucky winner in the "let's see who gets a poor overclocker" sweepstakes?
I miss the days when heat was your only enemy. Just throw good enough cooling at it and it'll go. Not anymore it seems.
Two more possible "intrusion detected" solutions:
- not specific to P5WDH, but worth a try
- from ASUS FAQs
Server will show Chassis intruded! Fatal error message:
Server will show Chassis intruded! Fatal error message
The error message will appear due to chassis intrusion sensor detects the server chassis has been opened. When user encountered this issue, they can eliminate the error message by following the steps below:
1. Shut down the system, close the top or sider cover properly and secure the screws of the cover if available.
2. Power on the system and the error message will show again. Please press the Reset button on front panel.
2. The error message will show persistently after system restarts. Please press the Reset button on front panel again
3. Upon restarting for 2nd time, the error message will be eliminated and the server will boot properly then.
*************
System goes directly to BIOS utility with error message:
Due to the fact that system detects chassis is opening during boot up, if you would like to disable this function, please refer to the user manual to find out the location of chassis alarm lead (4-1 pin). This lead is designed for hassis with intrusion detection feature. Please power off the system and use a jumper cap to short the pins labeled "Chassis Signal" and "Ground".
After power on for the first time, the system will go to BIOS utility directly and warn user with message stating "chassis opened" previously. Please go to [Exit] menu and select [Exit Saving Changes]. After reboot, the system will enter boot sequence successfully.
By the way, you also can also choose to close the chassis so the message won't show after second reboot.
*****************
ASUS SUPPORT
Search Terms: intrusion, answer
http://support.asus.com/faq/faq.aspx?SLanguage=en-us
Not even now this work :shakes:
Im can not RMA for that reason i placed AS5 on NB and SB and removed the asus label on NB,SB and Silicon Image SI4723.
simri it sounds like you have managed to corrupt your bios chip. Call Asus and ask for the bios department and they will send you a new one 502-995-0883.
With this board there is no need to pull the jumper!!! if you OC to far and it won't move just hold down the power on switch til it goes off, when things stop spinning hit it again . you will get an over clock error and it will tell you to hit F1 to boot .This will take you back to the bios to try again. Again there is no need to pull the JUMPER. In the future make sure of what you are removing before you remove it! I have built 13 systems on these boards they have all been perfect!!!
Don't try to tell me I just happen to get 13 great boards and 13 great cpus and hell even 13 sets of great memory. It isn't luck. Too many of you overthink this. It is not rocket science. (which is not really hard either)
Too many of you know too little and should just leave the damn side covers alone. If there were a shred of decency in this world this miserable thread would be deleted. People don't search it, they just want to re-ask the same ?'s for god knows how many times. very few really want to research and understand anything most just want some killer OC and they want it now!!! I have been running these boards for over a year now. Starting back
with a Presler 950es which was great cuz it would just kick the hell out of an FX-60 so it made my day. Then I moved to the e6400, again it was just unreal fast but, this board works best with the 6600 and higher due to the need for higher multipliers to work with. These boards have been great to me.
WZ
See, this is the kind of stuff I see that gets me pissed off:
http://forums.vr-zone.com/showpost.p...80&postcount=2
I lowered my RAM to 720mhz and upped my FSB to 365, yay, but I'm afraid putting my RAM up to 800 is gonna mess things up. All I want is 8 or 9x400 on the lowest vcore possible. That guy did it at 1.3! Why would my RAM be holding me back? It's frickin' Dominator 8500, easily capable of DDR2-800 at 4-4-4 timings!
you are not really losing that much, try my bios settings, they are a few pages back. Just run the FSB @ 395 to give you 3.5GHZ and leave your mem where it is @, one click below 800... The bios should still say you are at PC-6400 at boot....
So far I can't get past 375, though my RAM is at 750 with 4-4-4-12 timings. In order to do it I had to set my vcore to 1.45. I'll look at your BIOS settings to see what you did. This isn't too bad, really, I just wish my parts would OC as well as others'. I mean, 9x400 at 1.3x? That's nuts. I guess we'll see how stable this OC is when Orthos has had its way. :) Thanks for the help.
I guess it's just a matter of luck. Could be the board, your CPU, maybe your RAM. Some people have had crazy good luck, others have not. :\
My Vcore is bumped to 1.5 in my bios, just bump the vcore up and keep and eye on temps. I have no mods on this board at all, it is bone stock and that goes for cooling too just my cpu is water cooled. So even though I have vcore set to 1.5 now it reads 1.45-1.47 under Everest.. bump that Vcore and leave the MCH @ 1.65 no more no less and set the term voltage to 1.4 no higer no less
Does someone have problems with Overclocking to some limit, lets say from 266 to 280 it works good, but when you try 290 Vista sometimes shows black screen on welcome screen. its like instead of opening pretty, it shows black when only the password box shows first and than everything becomes visible.
i have no idea what the problem is, i tired voltages , timings. very very anoying, its like something is wrong, and prime 95 25.24 passed blend 6hr.
Seems my stuttering video is related to page faults and a windows registry tweak setting system pages to the maximum possible number just about removes the stuttering even with speedstep enabled, havent tested this alongside ahci/raid yet but will as soon as possible on dual boot.
How do I get the Lawrywilds 2004 bios? and what is different on it? thanks.
--edit-- I see added to 1st post in this thread.
Here's a few screenshots of my setup. This is the best I've gotten out of it. So far, it's passed two instances of Orthos (RAM and CPU tests) for about 15 minutes, a 32M superpi, two full runs of 3DMark06 (just the gaming benches, not the other stuff) and I played Counter-Strike: Source with 11 bots for about an hour with all the settings maxed. It's pretty stable, at least for what I do with it. I'll probably do more rigorous testing in the future. Here's the screens:
Bios1
Bios2
Bios3
CPUZ + Temp
http://valid.x86-secret.com/show_oc.php?id=229340
Hope this helps. Keep in mind, your machine may boot slower, so wait an extra 30 seconds or so before shutting it off to try again. See below.
Is there any way to "fix" the stall when booting when you've overclocked a lot? My machine takes an extra 15 to 20 seconds to get to the POST beep. I'm glad I waited, otherwise I would've never known this thing was actually capable of booting at these speeds.
@Polynikes,
Pretty similar rig, even got the same psu! (look sig.)
You should get a lot more out of that x6800. Tried higher multiplier? (got the same stepping also :) )
Mine oc easy above 4G on this board, mind if you have 1.85Vmch avalible..
Think fsb 370 was about max with a 1.65Vmch revison board I had earlier.
btw, your biossettings looks ok by me.
http://valid.x86-secret.com/show_oc.php?id=131012
I haven't tried a higher multiplier, I'm more interested in 400FSB. I'm curious if it can handle 10 or 11, perhaps I'll mess with it later. I'd also rather not push too much voltage through my NB since I have stock cooling and just finished installing my watercooling kit. The idea of taking it all apart and removing the mobo to put new TIM/reseat and/or install a different cooling solution sounds depressing. :P What voltage settings (all of them) are you using to get it to 410 there? How far is it safe to go with the mch on stock cooling? I do have the 250mm fan on the side of my case blowing directly on the mobo and NB, is that enough to keep it relatively cool? My radiator's two 120mm fans are in the front of the case blowing at full speed (~78 CFM each) towards the mobo as well.
Was hoping to find a concise list of bios settings in this thread but so large!!! any ideas where i can find list. Iv just got a p5w and have managed to get to 3.7 with e6750 though not orthos stable so really need settings have updated to latest bios anyone with any suggestions ta
Assembly /deassebly is half the fun :cool:
My voltage was pretty much maxed out, unless Vcore at 1,58V (1.55V DMM measured) to reach 4G.
I agree - you should be a bit careful with Vmch with stock cooling on it, at least you should change the termal paste on it if haven't already.
My 24/7 (rock stable) is 11 x 325 (water on NB) at Vcore 1.50V set i bios (real 1.48V). Coretemp about 55 C under full load. Probably stable at about 3,8 - 3,9, but haven't tested yet.
@aledsav1,
Take a look at Polynikes settings, they are a good start.
Look at my post above for bios screenshots that will probably help. vMCH is going to need to be raised a bit to help, and depending on how far you want to go, your vcore will, too.
Wow, I was running at 333*10 for the longest time at stock voltage and it was rock solid. My load temp on water wouldn't go past 48 C. Does the extra multi really make that big a difference for you?
Someday when I'm feeling more adventurous and want more out of my system, I'll probably change my NB cooling. Maybe I'll integrate it into my loop, maybe not.