Second power source for the chillblast?
Printable View
Second power source for the chillblast?
The problem is when the P5W cold boot, it's also power down the PSU which feeding the ChillControl. What I did is I hooked up the ChillControl to a different PSU and power them up separately while O/Cing from Bios.
-Asus should have given the endusers the option to disable the cold boot in the Bios if we don't want that option.
If I know this cold boot effect my Vapo, I would NOT buy this board.
Quote:
Originally Posted by Brahmzy
me 3 ;) ...350FSB no problem 365 a little problem, stuck at 375....dont want to fry it.
2 quickies...
1. What is FSB termination voltage..and what to choose ?
2. vmch 1,65v safe ...changed paste and have a little 50mm fan above NB....
Some new "errors"
1.
Asus has quite ALOT of vdroop on vcore
2.
Asus has HUGH, vdroop on vdimm - its more than 0,3v :shocked:
3.
Error with Sis Sandra scores when hitting above 8GB/s, it will just stock, but everything else will still increase (SPI etc.)
WD150 Raptor Drives not working properly!!!
These drives worked 100% fine on DFI Expert in raid0.
I initially had the same issues with running these drives on this mobo, but somehow, not sure what changed, they worked. The were running really well for the last week, no problems at all.
Earlier I had tried both the intel and silicon image controller, both with varied results. But now as I have had the system up and running on the intel controller, I dont wont to change it. I dont wont to re-install, or loose my data if possible.
Anyone got any ideas? I have logged a call with ASUS, maybe they can recommend something or a bios fix could fix it?
It's wierd that I did have it working. Anyone recommend a bios setting or something that I may have missed?
My issues with the bios not picking up my 2 WD 150 Raptors is back! I was running bios v801, all was working fine, then I upgraded to 1201, and got my disk problem again, so I rolled back to 801, and I still have the disk problem!
It is driving me insane!!!
The bios does not detect the hard drives properly. I have 2 WD 150 Raptor drives, 1 plugged into Sata1 and the other plugged into Sata2. I have configured the Intel controller to be in RAID mode, and plan on running the drives in a RAID0 array No other drives are connected to the system. I have tried multiple bios versions.
The system at one stage was working fine and detecting the drives properly, I was able to create a raid array, and install XP etc. But it stopped working after a bios upgrade. I have also tried to reset the cmos to factory defaults - removed power, removed batter, and changed cmos clear jumper, but that did not help.
The WD 150 Drives work 100% in an AMD NF4 based system. I can use 2 WD 500GB SataII 16mb cache drives and create a raid array etc with no problems. The only problem is with the Raptor high speed drives.
I have tried multiple power supplies with the same results. I have 2 power supplies:-
Antec NeoHE 550W
Silverstone ST60F 600w
I get varied results, with the bios detecting the drives.
Sometimes it comes up with the following:-
----------------------------------------------------------------------------------------------
Auto-Detecting 3rd Master..IDE Hard disk
Auto-Detecting 3rd Slave...Not detected
Auto-Detecting 4th Master..Not detected
Auto-Detecting 4th Master..Not detected
3rd Master .0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 19.06P.0
Auto-detecting USB Mass Storage Devices ..
00 USB mass storage devices found and configured
3rd Master Hard Disk Error
Press F1 to Resume
------------------------------------------------------------------------------------------------
sometime I get this:-
----------------------------------------------------------------------------------------------
Auto-Detecting 3rd Master..IDE Hard disk
Auto-Detecting 3rd Slave...IDE Hard disk
Auto-Detecting 4th Master..Not detected
Auto-Detecting 4th Master..Not detected
3rd Slave: WDC WD1500ADFD-00NLR0 19.06P19
3rd Slave Hard DiskError
Press F1 to Resume
------------------------------------------------------------------------------------------------
Other times it goes past the initial bios screen and shows the "Intel Matrix Storage Manager" RAID Bios. This is still with only the 2 WD 150GB Raptor drives.
and shows that the raid0 status has failed, and the physical disks are as follows:-
Port Drive Model Serial# Size Type/Status
0 ? Bz? Bz? Bz? Bz Bz?Bz?Bz?Bz?Bz? 511.0GB Non-raid disk
2 WDC WD1500ADFD-0 WD-WMAP41062308 139.7GB Member Disk(0)
-------------------------------------------------------------------------------------------------------
What is going on?
Anyone have any ideas?
Cheers
I got a reply from an Asus contact about the auto power down:
Quote:
This behaviour is caused by system's limitation. For over-clocking, the
internal PLL of NB would not lock on the high clock right away, so that means
system could not hold on the clock frequency immediately after reset. That's
why we add a auto-power down scheme to fix this issue. Of course, this
behaviour only occurs at over-clocking scenario.
0.3v? Are you sure you're measuring the right spot?Quote:
Originally Posted by M.Beier
I doubt it. The vmodders surely would have said something about this!!!
Found another thing:
If I enable auto on after power loss the board won't initialize the video card for me.
BIOS - 1101
MSI 7900GT
Hi, I am having some very strange problems.
Water-cooling my p5wdh (just processor for now, chipset has a zalman passive sink on it and is running at 35C, processor doesnt go above 25c at full dual prime load).
I haven’t started over clocking but I am having random crashes. I can run dual prime95 for hours on end (without an error), run 3dmark fine, run burin tests on every part fine. But if I try to just do regular computing it locks up (I.e. I could after 8 hours of no errors in prime click on the start menu and it would completely lock). I tried booting a ubuntu disk but it wont load (not sure if it relates to the fact that I am using a sata DVD drive), I havent reinstalled windows yet but I am running out of ideas on what else to try. Any suggestions would be appreciated (running bios 1101, thinking of going back). I have tried clearing the cmos and even left the battery out for hours (after putting it back I haven’t been able to get it to remember settings as every time I unplug it looses everything).
ive got a problem with the P5W DH DELUXE when using a PCI-E videocard.
when i use an old PCI videocard (ATI rage pro 8mb) then i have no problems overclocking my motherboard with 450FSB and 1.65vMCH. then it boots fine (cold boot ocourse) and no problems when restarting it.
BUT when i use x1900xt or x800GT with 1,5V MCH and 400FSB then after the restart it does the cold boot, but after the cold boot it powers on for like 2 seconds and then it shuts down. and if i power on the PC then it boots at default clocks and with an error message "overclocking or overvoltage failed".
im using fortron bluestorm 500W and tried the chieftec 400W (with chieftec the problem seemed to have gone away for sometime, but reappeared again). my friend who used almost the same setup as i did (same mem, same motherboard, conroe not allendale, seasonic 430W) has no problems. could it really be my PSU, should i buy the seasonic?
Is the southbridge temp...Quote:
Originally Posted by i||uSi0n^
At first I had the 48°C you mentioned.
So I lapped the stupid ASUS-sink and applied AS5...
This gave me a 43°C reading.
I glued a 50mm-fan on top of it.
This keeps the temp around 32°C...
Quote:
Originally Posted by jkresh
put a fan on the NB!
The temp you see is SB, the northbridge gets quite hot and gives the locking problem you describe!
I have a fan over the original NB heatsink, running D820 at 4GHz the northbridge will get to 65-70degC during load still! Vcore is 1.6, vdim is 2.2.
Works nearly 24/7 stable, but without the fan i get locks like you describe.
OneyedK: ok thnx i will try to place fan on it and see if it helps...Quote:
Originally Posted by OneyedK
jkresh: its 1101 bios that is causing random crash,i had get same problem...went back to 0901 and no more crash...
i||uSi0n^
I am running bios 1301. Seems to bring a bit more stability for me X6800. Went from 336 to 340 and dropped voltage .01
interesting :DQuote:
Originally Posted by MnM
>jkresh: its 1101 bios that is causing random crash,i had get same problem...went back to 0901 and no more crash...
running almost 24/7 and no stability problem on 1101 but S3 resumes tend to occasionally lose USB2 speeds on the onboard USB hub, didn't notice this on earlier BIOS versions.
FOUND A SOLUTION TO WD 150 RAPTOR ISSUES!!!!!!!!!!!!!!!!!!!
I was playing around in the bios, and if you set the "PCI Express Frequency" to anything but "AUTO" ie 100 or 101 then the bios picks up the drives perfectly 100% of the time.
I am so relieved! :banana: :toast: :woot:
never mind.
1.Quote:
Originally Posted by M.Beier
My board had about 0.03V
2.
0.3V:p: (2.3V to 2.0V) :rolleyes:
My board have 0.00V without any mods
Thanks for this POST. Now I know, still don't like it, but now I know. :)Quote:
Originally Posted by eva2000
1. AUTOQuote:
Originally Posted by [G.N.U.]Fragman
2. 1.50 - you shouldn't need any VMCH increase at the low FSB speeds. VMCH only comes into play @ 400FSB+ or higher.
Playing with VMCH has made no difference whatsoever on my 3.2GHz/3.4GHz OC's. Don't run it hot if you have to.
What are your temprature on the chipset on Asus p5w dh?
Mine is 56c now...
Case is closed, cpu is water cooled.
Yes Im 100% positive, I got vdimm and vmch mod on my board, none pencil style, but wires.. :)
They're made from pictures from Kyosen, so I have no doubt its 100% correct..
The sad thing is... Its not just 2.3->2.0v, would be to deal with..
But when using 2.85v, it can JUMP up to 3.1v during boot and during load in dualprime or dual 32M, go all the way down to 2.75v - and its not just with high voltage, have same issue at 2.3v
The 3.1v causes instant computer reboot... - I have to wait 2 get into windows and then turn up vdimm for benching.
Someone who is using Bios 1201, pls confirm that the Bios fix the cold boot on this board? thanks.
Somebody on another forum said so,
I am using the Vapo, this is very important to me
I'm using 1201. There's no visible difference as far as I can see.
What do you guys have on:
Memory Voltage:
CPU Core Voltage:
FSB Termination Voltage:
MCH Chipset Voltage:
ICH Chipset Voltage:
copy'n paste!
i got:
Memory Voltage: 2.30
CPU Core Voltage: 1.550
FSB Termination Voltage: Auto
MCH Chipset Voltage: 1.65
ICH Chipset Voltage: Auto
Can changing the ICH and the FSB termination voltage help go overclock more?
Memory Voltage: 2.3Quote:
Originally Posted by Cornel
CPU Core Voltage: 1.575
FSB Termination Voltage: auto
MCH Chipset Voltage: auto (but manually set to 1.65v - modded board, allows HIGH volt for 1.65v in bios :fact: )
ICH Chipset Voltage: auto
Those of you hitting 3.6ghz or 400 FSB on this board, do you have the onboard wireless removed? I don't see a way to disable it other than within windows. Just wondering if this would help my OC.
Nope, I got it attached and running, yesterday I started a wifi network at home. I am using even the IR remote as well.:)Quote:
Originally Posted by The Nemesis
Hi, I'm not sure if this is a common problem or not, but frequently when trying to overclock, once I get above about 385 FSB I can post fine, but WinXP x64 often reports NTLDR missing, or occasionally starts up but blue screens after the login. Is there any simple solution for this, or am I just hitting the limit on something in my hardware setup? Thanks for any advice.
hi guys.. i just bought this mobo.. its the new rev flashes with 1101 from factory(with the yellow sticker bios 1101) and my mch can reach as high as 1.85..(no i didnt do any mod) think it because of the new rev(hardware changes) as my fren tried to flash his mobo to 1101 and cant set to 1.85(no option).. hmm i was wondering wats the safest volt for mch and cpu if i am using the default heatpipe and gigabyte lcs for my cpu??
I switched back to 801 and am having the same issues so it doenst appear that its the bios and my northbridge heatsink is cool to the touch (also I have 7 fans each outputting 100+cfm in the case I doubt an extra fan on the north or south bridge could possibly be necessary). Have been running memtest for the last 11 hours without an error and I am stumped.
There s a thread somewhere about this - most probably a new revision :p:Quote:
Originally Posted by moonSymph
of the MB .
1,6 to 1,65 maximum on air
I have, but makes no diff.. Only reason I have is that I use 100mbit LAN for all my computers except the laptops & mac - which suits me well :)Quote:
Originally Posted by The Nemesis
So the Cold Boot still there with Bios 1201? thanksQuote:
Originally Posted by miochza
So does anyone else feel that 1.6vcore is safe? I have entry level water and can get 3.2ghz with 1.5vcore set in bios for a 1.46-1.48vcore during orthos. I think I can ge more out of my cpu as I've completed 3DMark06 @ 3.6ghz but I had to have 1.65 set in bios. I thought the whole point of the 65nm process was to require less voltage to acheive same high clocks as previous generation thus running cooler etc. Most of us stopped around 1.55-1.6vcore for our opterons so maybe thats why I'm a bit hesitant.Quote:
Originally Posted by famich
Famich, I noticed you only require 1.48vcore for your 3.6ghz to be orthos stable. Thats awesome!
THX , Nemesis , I think this chip is good -and it s OEM :) week 24:)
-some people here stated that OEMs and week 24 particularly are not good chips. I dont know, but if it IS some kind of rule, sure s got its exeptions :)
I do not know anything about your WC setup, but 1.6 V Core should be no problem for you then . If you were able to complete 3DM06-you re on your way:D
Have you tried the 3DM06 loop ? If you d be able to run that loop / without a sound / for 2-3 hours, you can play games and you re good to go.
Me and my friends use this loop as additional means of testing stability.
PS As I m writing this , Orthos large FFTs runs in the background
for 3H -and the temps of CPU are 46.47C MB 47 C / Everest reading /
:clap:
Yes, it's unlikely it'll ever be fixed by a bios update..Quote:
Originally Posted by dragonhunter
i just changed to radiical chipset water block on my P5W DH and put a thermal probe on top of my chipset waterblock too.. at 1.85v mch even the top of chipset block gets hot ~40.3C under load heheQuote:
Originally Posted by Cornel
Crap....tried different things today, has serious issues with it..hyperpath 3 is no-go here at 375FSB....will try turning down the volt for NB if it wont do anything less stable
Hello,
I bought this motherboard for my E6600 set up and i have been having major problems with my DVD rom and DVDRW drives being forced into PIO mode regardless of what i set it to in the bios or device manager.
This causes MAJOR slowdown whenever my disk drives are in use. For example, it took me 10 minutes to burn a CDR, it takes my old sempron 2-4 mins to do the same job, and my mouse is jittering all over the place. 1 of my cores will be @ 100% load while the other fluctuates ...... this is unbearable.
My system specs are as follows
E6600
P5W DH
2gigs OCZ GOLD XTC ddr2 800mhz ram
320gb SATA Seagate 7200.10 hdd
Lite on DVDRW
LG DVDROM
BFG 7600GT
OCZ Modstream 450w
I have used the main IDE port (blue one) and the one that is controlled by the Jmicron chip. The Jmicron only picks up my drives as SCSI and i cant seem to get anything installed when using that. And the intel controller continuously switches my 2 dvd drives into PIO mode regardless of what i try.
I have tried uninstalling and reinstalling my IDE channels and disk drives through device manager, and that switches the drives to DMA mode but its pointless because as soon as i pu a disk into either drive, that drive will revert to PIO mode.
I have both drives set to DMA if available, i have them set to DMA mode in bios. Basically i have tried everything i could think of aswell as what i have been told by people over @ anandtech, but regardless of what i try nothing works.
I have also tried using different ide cables, my older disk drives etc etc.
My disk drives arent bad because i have hooked them up to my older computer and they are recognized properly and put into DMA mode, they are both brand new drives aswell.
I have also used my older drives in the new Core2 system and same thing happens.
This is my last attempt at solving this problem before i return this board.
Thanks.
where are you guys getting your P5W bios updates? the one on the Asus site has the 801 there, and that is all.
kpamir, your problems do sound unusual since you say the burners cannot be set to UDMA. Maybe go thru' this checklist and see if it helps,
1. Intel chipset drivers installed?
2. JMicron drivers installed? Needed for proper UDMA & S3 support.
3. deselect ALPE/ASP in BIOS?
anybody has had this problem?Quote:
Originally Posted by heikis
I have had it happen a few times with sys in sign.Quote:
Originally Posted by heikis
turned out my problems related to a couple of bad sata cables. Now running dual prime at 3.4 (1.5v actual) with maximum load temp at 37C (full load with folding at home is under 30). I wonder how high I will be able to go at 1.5 and if 1.6 or a little higher will be safe (stability is realy important, but temps should be fine!)
Is there any difference between the DH version and the non-DH version overclocking-wise? I only need 1 PCI-E 16x slot
I'm not sure if I should push my cpu volt higher, currently its set at 1.45v but it shows only 1.4v in these progs. Aibooster is giving me irregular readings, it shows my cpu underclock, even though I disable a majority of features in bios. I follow the guide that was posted. My cpu at stock speed has a core temp of 29/24 C, I am using Thermaright SI-128 but I have my case flat on the ground sideways with the motherboard facing down. I want to push it farther but I'm not sure what celisus temp is safe with just aircooling??
Memory Voltage: 2.1
CPU Core Voltage: 1.45
FSB Termination Voltage: auto
MCH Chipset Voltage: auto
ICH Chipset Voltage: auto
http://img245.imageshack.us/img245/515/e6600ri1.png
Thanks for the link, but are you sure those bios updates are stable? Is that site even remotely connected with ASUS? Why do they have all those Bios versions and the official Asus site has almost nothing there.Quote:
Originally Posted by m0da
New Bios .. 1305 http://p5wdh.de/downloads/asus/bios/p5wdh1305.zip
Any changelog or? So what Bios versions are you people running most?Quote:
Originally Posted by M3kk
Quick question: how do I change my FBS in the BIOS? I can't seem to be able to change it in jumper free settings.
Runnin 1305 as we speak...still no booting past 370FSB without SPD timings on auto. Furthermore noticed some cosmetic changes...thats all.
Set Jumperfree to manual then use the + - keys on your keypad to increase or decrease the FSB. You can also type the desired value using the number keys. Keep an eye on the memory speed, as it will be automatically adjusted along wih the FSB. However, you adjust the mem speed without it affecting the FSB setting.Quote:
Originally Posted by Mr.X
-phil
Been using 1301 since the day it was released. Have had no issues. I did try 1201 :nono: , which surfaced after 1301, only to have get a blue screen the second I tried monitoring core temps. Odd. Went back to 1301 and have not had that BSoD again. Anomaly? Perhaps.Quote:
Originally Posted by AnjinSan1966
Will flash to 1305 tonght. I'm a hopeless early-adopter. :slapass:
-phil
It strange , I was able to boot 410*9 using manual mem timingsQuote:
Originally Posted by Ibinco
5.5.5.15 but changed teh perform. mode from TURBO to STANDARD.
V Core 1.525V Anyone ?;)
Just ordered another 6600 from the egg. Gotta love their free ground that gets to me in two days. Hoping to get a better batch# because mine requires 1.5vcore set in bios to do a measely 3.2ghz 12hours orthos stable. I want 3.6ghz I'd settle for 3.4ghz, but I don't want to have to put 1.5vcore on the cpu for either. I determined that the cpu was holding me back because the MSI board faired no better. It did however have less vdroop. Gonna give it a couple of more weeks and order another p5w dh too. Unless someone can point me to someplace thats selling the board with the new 1.85v chipset available. I think asus will make a bios for this board that's as good as the p5 model. Sli is a must for me & I don't think the P5 model can do sli witht he modified drivers. Come on ASUS get that stable overclocking bios out!:D
Someone has money to burn. :clap:
-phil
Thanks.Quote:
Originally Posted by phile
I am so tempted to do the same. I ordered up a P5B Deluxe...shoulda just grabbed another E6600. You can always feeBay them if they suck arse.Quote:
Originally Posted by The Nemesis
Anybody else try 1305?
Ya, no better for me..
Being a cautious n00b to the world of overclocking I have a quesition. In my system I have the following components (that are relevant to this matter):
Intel Core 2 Duo E6600 (currently with the FSB set to 333mhz to get a 3ghz stable speed)
Asus P5W DH Deluxe (with the BIOS at 1305)
2GB (2x1GB) PC6400 (DDR2-800) 4-4-4-12 Corsair XMS2 C4 memory (currently running at DDR2-833 speeds with timings at 5-5-5-12)
Arctic Cooling Freezer 7 Pro CPU Cooler
Tagan TG480-U01 PSU
I also have a couple of akasa 80mm fans directly behind the CPU cooler running at 1800ish rpm sucking air out of the case and one on the side window of the case above the graphics card area. I would say the internals are kept reasonable cool at the moment (the cpu is currently 28c at 3ghz idle).
Given this sort of setup how high can I realistically go without shortening the product life of the components (if possible)? Ideally I would like to set my memory to 4-4-4-12 but I have not yet been able to do so without the power cutting out.
Again I realise I am a total n00b here but I have to ask this - can the product lives of products like the CPU be shortened quite drastically by this sort of overclocking? I tend to keep my components for between two and three years at a time so I'd like them to last that long at least (and much longer ideally).
it can, if you are going too far....too much voltace e.g.
If it was left as it is just now (i.e. 3ghz and 5-5-5-12) then may it be reasonably inferred that it should in theory last three years min without any problems?Quote:
Originally Posted by [G.N.U.]Fragman
no guarantee but if your volts arnt to high then it should be fineQuote:
Originally Posted by DarthVader
What volts are you puting on your cpu core, chipsets & ram?
After doing some more meddling I have reduced the memory timings to 4-4-4-12 by increasing the memory voltage to 2.00V (I believe my modules can take up to 2.10V fine) and as of yet the PC has not shut down on me. As for the other voltages they have been left on auto (even though the FSB is currently at 333mhz and consequently the ddr is apparently at "DDR2-833").
If your volts for everything except ram are on auto chances are your not overvolting or even slighty pushing the envelope. You should loop a few instances of 3DMark or run some prime benchmarks to see if you're stable @ those settings. Not many of us are getting 3ghz out of our 6600's @ stock volts. If you are then you have nothing to worry about. As for you ram, since you went with corsair you have nothing to be concerned with. They have the absolute best warranty replacement policy in the business. I've used it three times myself and have always received new sticks within a week:DQuote:
Originally Posted by DarthVader
That's very reassuring to know. :toast:Quote:
Originally Posted by The Nemesis
On an entirely different matter (although concerning the Asus P5W DH Deluxe post v1301 BIOS) I have noticed something odd about the motherboard. I should point out this was happening before I even started my overclocking attempts. It was happening with v1301 and continues with v1305. If one saves changes in the BIOS and exits then the computer powers off for a moment but then restarts itself as normal. Secondly the same thing happens if I restart (obviously using the restart button) in Windows XP Pro x64. Is this normal?
I am currently using v1305 of the BIOS.
For this board yes.Quote:
Originally Posted by DarthVader
My E6600/P5W DH will not run stable at 333 FSB (3GHz) with anything less than 1.35 vcore. I can go as high as 320 FSB with vcore on auto. I'm not going to bother pushing any further. There isn't a justifiable return in performane for the hot temps I would get, on air. Hey, it's like I have a X6800 running at stock, for 1/3 the price! :woot:
-phil
That's normal behavior when the systen is overclocked, but you're the first person I have seen experiencing that at stock. Maybe, it's something to do with XP64. Have you tried resetting BIOS to default setting and rebooting?Quote:
Originally Posted by DarthVader
-phil
I'd go for 3.2GHz @ 1.45. I consider 200Mhz to be a worthy gain.
My full-load core temps already peak in the 70s at 1.35v. I don't even want to try 1.45v. :nono:Quote:
Originally Posted by Brahmzy
-phil
Guys, what are all these weird settings in the bios for the memory?
i have 2 Corsair CM2X1024-6400C3 sticks, and the timings for them are:
3-4-3-9 (CL-RCD-RP-RAS) tRC 22T CR 2T and Write Recovery Time(tWR) 6T
when i go into the Asus p5w bios, and i try to match these values i get a damn listing of the following, (I have no clue where each value should go, you'd think they would keep the words consistant so that someone like me could just match the words and numbers together:
Cas latency ? 3
Ras precharge? 3
Ras to Cas Delay? 4
Ras Active to Precharge? 9
Write Recovery? 6
The above is what imy guess should read in my bios, but could someone confirm if the values above match the memory stick timings i have listed at the top of this post? God how things have changed, i guess i should upgrade my computer more often, used to be sooooooo damn easy. lol
MEMORY divider problem FIXED!, after flashing 1305 BIOS i can finally set up my memory in others dividers than 1:1! Before 1305 was my best setting 400FSB, CPU 3.6GHz, mem 800@8-3-3-3, NOW - 400FSB, CPU 3.6GHz, mem 1000@14-4-4-4 ! WOW the best BIOS for this MoBo i here...
Hi guys
i have for a 14days my new ASUS P5W DH.And cannot solve problem with slow POST.I have tried all available BIOSes and without succes.Now i running on 1301.If i not overclock anything MoBo bootup quick and POST is about 3sec max.When i overclock then POST is about 30sec up to 5minutes!I tried disable Quick FAn but still same, only FANs start running on max speed.I have OC E6600 to 3,14GHZ,Core V 1,4125 rest is auto.If i change anything this not affect speed os POST.Sometimes MB says FAN CPU error press F1 to resume(ArcticFreezer).I tried everithing what is here posted but my problem is still same.On stock speeds POST is fast as hell,when i OC even to one MHZ then POST is 30sec up to 5minutes:-(Can someone help?
currently have my e6600 at 3.45 with 1.55 volts (1.52 actual), acording to asus my prime95 load is 38c, thinking of upping the voltage a little. (801 bios)
edit: Oops dividers not spd.. :slap:Quote:
Originally Posted by OBR
Looks to me like you have correctly configured your mem timings in the BIOS. A pox on the house of ASUS for not listing the individual timings in the standard order. :slapass:Quote:
Originally Posted by Artmic
-phil
I am not talking about SPD or timings man. Read carefully, with old BIOS i can not to reach anything above 950MHz at any voltages and timing. With FSB 400 i had only one option MEM:FSB - 1:1, other dividers -freeze. NOW i can set anzthing and it is working ..., for me is the biggest problem of this MoBo solved ...Quote:
Originally Posted by lawrywild
Strange...this bios dindnt solve those issues for me. Can u post your full specs on how u achieved this?Quote:
Originally Posted by OBR
Na I doubt it is x64 that is causing it because it does it when leaving the BIOS too. However, it did start doing this before I began overclocking when I flashed it to 1301. Although in saying that I obviously had the memory set to DDR2-800 and 4-4-4-12 at that point anyway.Quote:
Originally Posted by phile
I presume this switching off won't cause any damage?
EDIT - I did get this response in another forum though (apparently from the Asus techies):
Quote:
This behaviour is caused by system's limitation. For over-clocking, the
internal PLL of NB would not lock on the high clock right away, so that means
system could not hold on the clock frequency immediately after reset. That's
why we add a auto-power down scheme to fix this issue. Of course, this
behaviour only occurs at over-clocking scenario.
Actually i think i did this:Quote:
Originally Posted by phile
Cas latency 3
Ras precharge 9
Ras to Cas Delay 4
Ras Active to Precharge 3
Write Recovery 6
The asus bios is not in the 3-4-3-9 format i think. i don't think the Ras Active to Precharge should be set to 9 that is too much, so the only option was that i had to switch the two precharge values.
I dont understand why my system is acting so weird. (p5w-dh-del, e6400)
when using PCI videocard + 400FSB + 1,65V MCH then everything is ok.
when using PCI-E videocard + 400FSB + 1,5V MCH then randomly after the
restart it powers off, then powers on for 2 seconds and powers off again. then by powering it on manually it boots with stock settings loaded and reports "overclocking or overvoltage failed". the problem occurs only when using a PCI-E videocard. ive tried different memories, different PSU-s, different videocards, different BIOS setting, different BIOS-s. im 100% sure these are fine. that leaves me motherboard or CPU. as everything is ok with a PCI videocard then i suggest its the fault of the motherboard. anybody has a solution or advice`?
Quote:
Originally Posted by heikis
have you tried booting in with 1.65 mch with the pci-e card in? maybe im reading your post wrong but id think thats where Id start. @ 400fsb your probably going to need more than 1.5
Well it definitely is not doing the power down thing at stock settings - this could become a nuisance.
Incidentally I found that the motherboard temp appeared to go up when I reverted back to stock, which is slightly odd. Maybe it is just the progression of the day that has caused the temp to go up slightly instead.
it's possible the p5wdh is really better with an E6600 than the p5bdeluxe ?
Just wondering as I have a quite similar setup how you gotten 3.1GHz out of the E6300. I have the following stuff:Quote:
Originally Posted by OBR
- Intel Core 2 Duo E6300 @ 2.8GHz
- Asus P5W-DH DeLuxe - BIOS 1101 / 1201
- 2GB Crucial PC2-8000
Could you details me which settings you used to get to 3.1GHz? As I can even get to 2.9GHz. Thanks... ;)
Well, my P5W DH´s LAN keeps disconnectin with those new drivers also but not as badly than with original drivers from mobos CD.
when uTorrent DL´s over 250kB/s network just freezes.
I have tried both ports, same thing.
Now everything works well cos I disabled Marvel Yukon and installed really old 3Com 10/100 Fast Etherlin XL PCI card.
Should I try some really old drivers for Yukon?
Anyone else having those LAN problems?
Can't say that I am.Quote:
Originally Posted by BulldogPO
Quote:
Originally Posted by OBR
Where do u find all this bios???
when i search asus homepage i only find one bios
Hey it's good to know that this BIOS provides more FSB/DRAM ratios.Quote:
Originally Posted by OBR
But, isn't 3-3-3-8 @ 800 actually faster than 4-4-4-14 @ 1000?
3 cycles at 800 MT (400 MHz) is 7.5 ns, but 4 cycles at 1000 MT is 8 ns. :confused:
Thanks lawrywild for putting together this list. I've been lurking for a while now, finally read to post.
First, a new problem: after the system has been up for a couple of days, Probe 2 and SpeedFan start reporting the CPU temperature as 128C. This goes away after a while. In this state, Probe alternates between 128 and 256, and Speedfan stays at 128. Everest reports the temperature correctly (~40).
Second, in your initial summary, the Probe 256 problem is blamed on CPU-Z. That is not my experience: it happens anytime Probe is running regardless of what else is running. Neither SpeedFan nor Everest report 256 ever.
Third, the "FSB wall" issue could use a clearer explanation. The issue is that the P5W DH normally overclocks the 975X NB by changing its strapping from 1066 to 800. This gives better benchmarks at stock speeds, but limits the FSB speed. This feature is controlled by the "Hyper Path 3" BIOS switch; disabling this forces the 1066 strap and allows much higher FSB speeds without overvolting the NB.
Fourth, people continue to be confused about the CPU and MB temperatures. Perhaps you could edit the summary to state that the CPU temperature reported by Probe 2 and SpeedFan is a thermistor on the board near the CPU, and that to see the actual (core) CPU temperature you need to run Everest or Core Temp. Also, it might help to clarify that the MB temperature is the ICH7 SB, not the 975X NB.
Couldent agree with you more :)Quote:
Originally Posted by cmthomson
No problem, refresh my first post in about 10 minutes.Quote:
Originally Posted by cmthomson