No, I'm done with messing with this board
Printable View
No, I'm done with messing with this board
I tried nothing spectacular, heck the 1407 doesn't do well for me either. I have to use the 1403 when I want to bench @450-455FSB. I use 1305 otherwise.
Ok so it seems 1305 is still a better bios to use.
Quote:
Originally Posted by virtualrain
I have not really had an issue with any bios since 801. After it, I used 1101, and now 1402. No speciffic reason, just to try them. I am not a good "reviewer" of these bios because I do not really dig into each to see what I can and cannot do. They all (that I have tried) have done what I wanted. Others may get into more detailed comparisons of each, not me. If I can boot, and make it run fast, and give no troubles, good enough for me.
I did have a prob for while getting memory errors with memtest and bios 1402, but it turned out it was my fault due to playing with settings :) ( big thanks go out to RyderOCZ from OCZ for setting me straight on that one ). I had put vmch back on auto (doh). vmch needs to be juiced up to be stable at high Mhz. I am using 1.65 vmch
I have a pic of 4 hours Orthos, vcore set at 1.575 in bios, and asus probe showing 1.52 at load. Yeah, vdroop sucks.
Core temp shows one core at 58c, other at 60c while asus probe says cpu is 46c and mobo 35c
hmmm, maybe I should try 1305 for the heck of it.
1101 & 1305 have been best for me on my 1.85v mch boards. No bios after 1403 will let me post above 440 X 9. I can't run memory @ 9 X 400 DDR2 1000 either but I bought some Crucial Ballistix's DDR2-800 to see if they will do it. My G. Skills do DDR2-1000 @ 2.3v 4-4-4-12 using the 2:3 divider but I have to set the FSB to 334 with is only 3 ghz. Max FSB 1mb Pi stable with no mods is 455 so far. Changing southbridge & northbridge chipsets tomorrow.
Quote:
Originally Posted by The Nemesis
lol you are still going hard at it eh :) Is this with the new 69MOAG and B series Conroe? I quit messing with mine like a couple weeks now. Just been enjoying it more hehe :D
Please let me know if you find any improvements or issues! Thanks again Tallman!Quote:
Originally Posted by Tallman
Well I tried 1502 bios, just to see if the boot issue was gone, it isn't gone completely but the pc (at least mine does) seems to restart smoother, all fans and stuff spin up at a slower rpm to get at normal speed a few secs after. I think Asus is focusing on that. the E6400 with 400x 8 still runs happily on 1.4125 bios volt. Previously I could get it workingand bench it at 445 x 8 , will try that later today. Anyone else experiencing a different bootup then before. I also had with 1405 bios in case I used alower multiplier some weird readings with benchprogs. Eg Bios set to 7 x 400, CPU Z detects 2800mhz, Everest home 3456mhz, 3dmark 3456mhz,... will try that 2.
Keep it up Asus !!!
well did some testing, max benchable FSB is 438 Mhz :( (have max 1.65 MCH voltage) Also the multiplier software bug is still present with me ( not that it annoys me just seems weird ) Everest home and other seem to detect the fsb wrong 457Mhz all the time if set to 400mhz. Only CPU-Z seems to detect it correctly.
In Everest Read timing improved from 8351 to 8769
The Write timings dropped form 2642 to 2132
Latency dropped from 50.5 to 49.7
All by all this shaved 1 sec of from my SuperPI score 1Mb test now 17 secs flat. doing other SuperPi tests and they all seem to improve by a small margin ...
Just to clear up, there's no added memory timings?
I could use a little diagnosis here.
DH Deluxe (version capped @ 1.65V MCH), Arctic Cooling Freezer 7 Pro, 2048MB Corsair TWIN2X2048-6400C4 RAM, CoolerMaster Real POwer 550W PSU, GeForce 7300 GS video.
SEEMED stable for a few days @ 410 FSB, RAM @ 4-4-4-12 1:1. 1.65V MCH, 2.10V Vmem, Vcore on AUTO was working fine, FSB 1.50V, ICH AUTO. HyperPath 3 disabled. CPU heat not excessive: as low as 43C at idle and 51C during Orthos stressing, and higher if I use a pre-selected Vcore instead of AUTO, but it was worse before I cut a hole in my case for a 120MM fan to blow on the MB.
Then I 'upset' it by testing why the 1407 BIOS locked up on me. Reverted to 1305, including CMOS reset just for luck (didn't NEED it). Now it runs for a while and locks up at random. An attempt to leave it on overnight yesterday doing nothing died at 1:32AM per the clock. Retart this morning was delayed when the hard drives went AWOL. Two power-offs still didn't bring them back, so I cracked the case and patted down the related wires, power and data. Nothing budged, but the drives came right back so maybe it NEEDED a timeout with no power. Only stayed running for maybe 35 minutes though, and then the mouse, keyboard, and clock all stopped.
Now, I've been hearing something just before the lockups when I'm there, like this time, and I've been calling it a kind of 'relay click'. Two quick clicks, followed eventually but not instantly by the whole system siezing up. It reminds me of what I hear when I'm shutting down, but slightly more subtle. No sign there was a full shutdown attempted, though.
I guess the PSU is causing the clicks (correct me if I'm wrong), but is that because the MB initiated a shutdown/cutback due to overheat of something? Is there some monitoring BIOS option I should turn off since I THINK things are OK? Some other heat-checking program (I use Core Temp for the CPU) to tell me what's going on that's not OK?
Thanks...
Does anyone have issues with this board on a reboot where it fails to initizalise the usb controller and hangs. I then press reset switch and it slow boots and throws a weird config disk entry in the raid list of disks on the ICH raid screen.
Config is 3 Raptors on raid 0
System not overclocked
Help appreciated
Topboy
Nope..:)Quote:
Originally Posted by lawrywild
got my e6400 @ 3.2ghz using 1.412 vcore and 1.65 vmch
can't even boot 410 fsb on this vcore thou, but it's rock stable at 400, ran orthos for 24 hours and other benchies fine, ran a few hours of fear and bf2 also and works fine
it's a week 28, do i have a dud? (I'm on a p5w, so i guess with vdroop it's actually lower than 1.412?)
it definitely needs that voltage, just think it's a bit too much for that clock. also temps are high... around 65 at max load ...and that's with a scythe infinity and some as5 (possibly bad contact?)
any suggestions/comments? full system specs below
thanks all ;)
600w GameXstream OCZ PSU
2GB DDR2 800 Crucial Ballistix @ 4-4-4-12
E6400 @ 3.2 ghz 1.412 vcore
Sapphire X1900XT 512MB
ASUS P5w DH
WD 250GB SATA II HDD
20" Widescreen Viewsonic Monitor
5413 3dmark06 at stock e6400 speeds
6098 3dmark06 e6400 @3.2ghz.
no OC on the video card yet (i dunno how to )
First off I need to knock on wood, mainly because I guess I've been blessed because so far I haven't had any major issues with my settup. Maybe it's a combinatior or hardware or may it's just plain luck. I haven't tried BIOS 1502, mainly because I've been busy but I'll give it a go this weekend. My first mobo (1.65 vmch) was good to me it did 400x9 and better tried anything like my current setup because they hadn't released the unluck multi BIOS yet so I never got around to try 450x8, my current one (1.85vmch) is doing well as you can on my sig. I recently acquired a Rev 1.03G which I'll be testing this weekend to see if I get better OC. As far as added memory timing I kinda like not having to worry about more settings to mess around with, then again this is just me.
I have some issues with my PATA drives in this mobo..
I first tried to use the black jmircon IDE slot for the 2 PATA HDDs (and used a longer cable since the one from ASUS couldn't reach the distance from the HDDs to the black slot) and left the blue IDE slot for the optical drives. Drives worked fine both but both HDDs were impossible to be recognized from the black IDE.
Then I used black IDE slot for optical drives and used the blue one for HDDs. I managed to make the HDDs be recognized but the system becomes slow at loading and transfer (This is happening because of the one of the 2 PATA drives). If I remove the particular one the other PATA HDD works fine and my system works fine. The one drive that slows down the system works fine in another computer and I can't understand why it slows down things in this mobo..
What's happening here? Making my 2 PATA drives to work simulteanously has become a pain in the a$$ why is this happening can anyone help?
P.S : Now every time I start Windows I get a "Jmicron raid controller error" but I checked at the device manager and the device is working properly. I'm so confused..
Two quiet clicks....that sounds like a hard drive head dying...could be wrong, though....(a head dying and freezing can cause the entire system to freeze).Quote:
Originally Posted by mikepaul
Is the HDD LED light on when this happens?
jumper the drives properly. Cable select ain't gonna cut it.Quote:
Originally Posted by Orbitech
I am using jumpers properly.. :) Hell I used all teh possible combinations to make sure I was correct..Quote:
Originally Posted by cadaveca
I mentioned that BOTH PATA HDDs ARE RECOGNIZED CORRECTLY. But I have slower transfer times and windows are taking forever to load.. If I remove one of the 2 PATA HDDs(the one that creates the problem for a strange reason since it works just fine on another pc) the other PATA will work fine and the system as well..
Anyone guys? Too fvckin weird :mad:
Seagate drives, by chance?
Nope.. 2 old WD 7200rpm one 80GB and one 40GB.Quote:
Originally Posted by cadaveca
Yeh I get that weird Config disk every now and againQuote:
Originally Posted by topboy
So, it's not me with these weird stability problems...
FWIW, the "disk" resulting from a RAID0 or RAID1 on the EZ-BACKUP ports identifies itself as "Config" something.Quote:
Originally Posted by lawrywild
umm, I don't use ezraid at all
Can't say if the HD light was on more than normal: the case is on its side with the access opening up, so the light faces away from me.Quote:
Originally Posted by Falkentyne
The boot drive is 'new', a RMA replacement WD 160GB that was fortunately around when I overheated and killed my old drive while defragmenting, and it hasn't had any problems that have been brought to my attention. It now lives in an Antec HD cooler at maybe 34C per the LED display. The WD 80GB data drive has seen better days, since I've had to reformat three partitions recently to get around Ghost 10 not being able to back them up. One of the partitions is where I keep the swapfile and it has needed a CHKDSK a few times due to these crashes and also what seemed like normal shutdowns. I guess the click sound could be coming from that general area, since it's almost the same level in the case as the PSU.
I can keep this idea in mind if having the non-boot (but swapfile) drive act funny can cause these kind of crashes, and put a new drive on the shopping list. Would moving the swapfile back to the C: drive for a while limit the impact crash-wise of any head issues on this secondary drive? One day, when I have 8GB of RAM and a version of Windows that can use it, I want to do away with the swapfile anyway...
Quote:
Originally Posted by topboy
I get that rubbish too sometimes. It stalls for a moment when trying to find IDE4 then it displays that junk (--------------) in the Intel RAID section. I've got 2 Raptors in Raid 0. I don't know what happens if the PC actually boots, because when I see it I normally reset the PC because it worries me that it might corrupt the data on my hard drives if I let it boot.
Same here..:(Quote:
Originally Posted by pee4
I just let it boot when it happens, it does nothing, don't worry about it
can't even boot 410 fsb on this vcore thou, but it's rock stable at 400, ran orthos for 24 hours and other benchies fine, ran a few hours of fear and bf2 also and works fine
Max FSB I got with 1405 was 445 and with 1502 now it's less :( But the reboot seems different. Thoush stil noa added mem timings like with P5B Bios
it definitely needs that voltage, just think it's a bit too much for that clock. also temps are high... around 65 at max load ...and that's with a scythe infinity and some as5 (possibly bad contact?)
I need to put 1.4125 or 1.4250, the latter gives me less choppyness in games but the rig is rockstable on 1.4125 ( real just below 1.4 volts in bios) but he games tend to lag so I give the cpu some more voltage. I think you better reseat the cooler. In Orthos (so Dual prime) I get 52-50°c in Coretemp with my Ultra 120, The previous Zalman was 4-5 degrees hotter than the Thermalright. Everest Home gives for the CPU under load 44°C which is fine for me and the rig runs like this 24/7
These are my settings here in the link :
http://users.pandora.be/OAP/ALT.doc
Also here's a piccie of the cooling setup, I removed the covers of the bridges, a small old CPU fan on the northbridge and a beefy 120mm fan giving some cool air to my X2 card and the southbridge
http://users.pandora.be/OAP/Ultra120.jpg
You Asus guys have too many hits!, 165,000...us Gigabyte folks are launching a campaign to beat y'all.
:-)
Hi guys!
Is in the new 1502 bios anything concerning memory subtimings (tRD, tRFC)configuration?
Somebody did try it? And what about memory divider? Are They working better with this new bios?
Thanks in advance
Apparently not :(Quote:
Originally Posted by v_parrello
haha.. you can try :DQuote:
Originally Posted by Richard Dower
I thought it might come in handy to pass this url : it`s the newest version of the Asus update utilty v 7.07.06 to update the bios of all asus boards in windows xp without leaving windows xp :
http://drivers.softpedia.com/get/Oth...ty-70706.shtml
I finally get around to testing my Conroe 6400 and P5W DH, I install the board and the stock cooler as usual to test temps on stock, and then go to power-up the system and nothing?
So I check all connections blah blah, and try the obvious removing the conroe and installing a Pentium 930, still the system won't power-up?
So I pull the board out of the case set it up on the box on Anti-static bag to elinimate Case grounding problems etc. as an option. I use a jumper to power up the board and it works! So I pop the front off the NZXT Zero case to see where the short might be in the wiring and it's fine? Then I realize I was freaking trying to power on the system using the DAM Reset button Doh!!!!
I've decided to remove the "savant" from my nickname Idiot-Savant. Anyway I rei-install Conroe she boots but it says 6300 running at 1.60GHz? So I raised the FSB to 333 as I thought this was supposed to be the Conroe's FSB speed anyway and this raise the memory to ddr2-1000 ehifch it is, and the chip to it's dfeault speed of 2.13GHz> Then the system won't boot? When the BIOS (0801) comes up again (at 1.60GHz) I notice the CPU temp is 65C? I try lowering the Vcore which was on Auto but I figure maybe there's something wrong, and this does nothing. Now I know with stock cooling 65C is insane since my room is at 18C and the case is open and near an open patio door letting cold air in. SO 65C is impossible. Well not with a Pentium 930 and a stock cooler overclocked but on a Conroe running under it's speed? PLAESE HELP
Does the bIOS 0801 report CPU temps wrong?
I'm sure I seated the cooler correctly although to be honest I hate these freaking new pop-pins they drive me nuts because they just don't work right half the time. You push two pin across from each other so one side doesn't seat unevenly and what happens only one goes in anyway. Anyway I need help or a handgun..... :(
The BIOS will correctly report which CPU you have, regardless of the operating speed. So, if it's reporting that you have a E6300, that's exactly what you have. Stock FSB for conroe is 266. Your temps suggest that the cooler is NOT properly secured to the mobo. I would suggest removing and reseating the CPU (Take the opportunity to read the fine print on the heatspreader, which tells you the default operating frequency. This will help you determine what chip you have.) and reinstalling the HSF.
-phil
my new asus p5w dh deluxe straight out of the box manage to run my E6400 @ 3.2ghz with vcore @ default, vfsb up 1 notch, vmch @ 1.65, vdimm @ 1.9.
orthos stable @ 6hrs, but i'm using stock intel hsf. Coretemp reported core temp @ 80c .. :D
80c? :eek:Quote:
Originally Posted by irenic
I thought mine was bad at 60c load, at 3ghz.
Well screw it then, Im going back to 3ghz. :D
i dunno how accurate it was.. my room temp was at 24c and my GTO also cooled down to 35c .. i touched intel hsf and i could feel the cold. but coretemp showed 80c.
my cpu is ok, not concave bcoz last time with big typhoon VX, even at 1.5vcore temp never goes above 65c.
Core temps of ~60C at load (TaT, Orthos Small FFTs) are well within the safe zone. I would certainly be very much uncomfortable with 80C, though.Quote:
Originally Posted by Jimbo
-phil
Where did it say 1.6 GHZ? If in windows it could be the cpu throttling down to save power. If when you set the FSB to 333, you left vcore on auto, the board will possibly set the vcore very high, thusly given you high temps. And if you try and read the vcore with cpuid it will read low.....Quote:
Originally Posted by Liquid3D
Just a bunch of maybes.....
That sound could also be from a hard drive starved for power.Quote:
Originally Posted by Falkentyne
When I had another failure to boot due to no hard drives found, I checked and noticed the plug into the slave drive (the one with recent troubles) wasn't on solidly. Sure, I had shoved it on until it clicked, but it still rattled like the pins inside weren't attached solidly. Another plug had already proven to be unreliable so it's not like I wasn't warned.
So I demoted that plug to powering a fan and put another one on the HD, then still moved the swapfile to C:, and the machine ran all night. I may still splurge for another PSU with attachable cables so I can cut back on splitters. Meanwhile I may need to figure out if they sell kits to rebuild these plugs. This was the PSU I got via RMA when the first one seemed bad.
Thanks...
That's good to know. Thanks.Quote:
Originally Posted by lawrywild
Np, afaik it's supposed to show up every once in a while.
I have a big problem. The second core on my 6600 stops working after I leave my pc on for a while. When I reboot, it goes back to normal. It'll then work fine for a few hours or maybe several days straight, but eventually it happens again. I'll run something multithreaded and the first core will be maxed out and the second core will be virtually unused. I tried a fresh install with xp pro and home and same problem with both. I ran Othos the last time it happened and got the following error message: Affinity Mask: Process: 0x1 Sys: 0x3. Anyone have any ideas on what's going on?
I just found a post about someone wanting to use just one core and doing this: run,msconfig,boot.ini tab,boot.ini advanced options, /numproc (set to number of cores to 1). So I did that but set it to 2 to see if it helps. It was blank by default. Hopefully, this'll do the trick. For some reason, I'm not that hopeful that it will.
LOL, keep posting in this thread please and see if you beat this one.Quote:
Originally Posted by Richard Dower
MXtra - sounds like a bad cpu maybe?? you could try a full socket reseat.. blow the socket off when the cpu is out also.. good luck!
Well, I tried 1305, and for me at least, 1402 is better. More stable.Quote:
Originally Posted by virtualrain
With 1305, when I boot at 390 fsb, I cannot bench and it shuts down after about 30 seconds with 1.7 vcore.
Same vcore and fsb of 390 with 1402 and I can bench and stays running.
So it is 1402 for me all the way.
Sounds like a software problem to me. I'd think if one core really became dead/comatose it would cause nasty things to happen.Quote:
Originally Posted by Mxtra
That's what I was thinking too, so I was suprised that a fresh install didn't change things. I use a program called svcd2dvd for encoding and it's multithreaded. The last time I found only one core was being used I closed it and ran Orthos. Same thing happened for Orthos, only one core got stressed. This sux cuz there's virtually no help online for such a problem. Not enough people have dual core pc's.
Quote:
Originally Posted by NghtShd
:rofl:Quote:
Originally Posted by Tallman
Ok... thanks again for your insights... you are going to save me a lot of time!Quote:
Originally Posted by Tallman
On the subject of BIOS... What's the verdict on the latest 1502 bios people?
Or... POST stop after memory check.
For me, the problem I discovered was actually the PWR_FAN1, or the use of both PWR_FAN2 and PWR_FAN1 to power my case fan and the optional fan. So now I just plug the case fan into PWR_FAN2, forgo of the optional fan. ASUS manual should have highlighted "Installing the optional fan with an active CPU cooler ]<i.e. a fan> will interfere with the airflow and destabilize the system." THey're quite right, I only wish they made it be known better.
Other than that, my P5W DH runs like a dream.
In your experince is 1305 better than 1407?
No issues with 1502 (mild OC)
- P5WDH BIOS: 1502
- E6700 WK: 26
- FSB: 300; 3:4; PC-800
- OCZ OCZ2G8002GK; vDIMM=2.10vdc
- 5-6-6-18; BW: 6290/6279
- memtest86; 8 passes OK
DRIVES:
- 3 on ICH7 (AHCI mode)
- 2 on EzBackUp SI 4723 (RAID 0)
- 1 on JMicron [SATA RAID1]
IDLE: (SpeedStep and C1E enabled)
- CPU: 25c/77f
- MEM: 31c/87.8f
- AMB TEMP: 20.5c/69f
LOAD: (Orthos 4+ hrs)
- CPU: 48c/118.4f
- MEM: 39.5c/130.1f
- AMB TEMP: 22c/72f
LOAD: (SuperPI Single 32M)
- CPU: 40c/104f
- AMB TEMP: 22c/71.6f
LOAD: (SuperPrime 1E8)
- CPU: 45.5c/114f
- AMB TEMP: 23c/73.4f
LINK to build pix/mods/benches:
http://www.esnips.com/web/ConroeReady
The "optional fan" that they talk about here is the extra fan that came with the mobo and it mounts on top of the heatsink that is between the cpu cooler and the back of your case (covering mosfets).Quote:
Originally Posted by SpaceCadet0
I have a fan connected to both PWR_FAN1 and 2 with out any problems
infact, I have 4 fans connected to mobo besides the cpu fan(actually 5 if you count the one on the splitter)
Using PWR_FAN1, PWR_FAN2 and CHA_FAN1 with no boot/post delays or issues.
- (not using PWM aware HSF or ASUS MOSFET fan)
- BIOS fan controls all set to DISABLE (1502)
- Zalman CNPS-7000 AlCu with 478 to 775 bracket
i just installed my wc and my temp drop 40c during full load!
with same room temp (25c) and same oc setting (400x8) orthos showed intel stock fan full load @ 80c while my new wc setup only 41c! :D
i'm so happy..
i installed ASUS mosfet fan and connect it to pWR_fan2 without any problem..
Hello!
I would like to thank everyone who posted in this thread for providing great information. I've been reading this thread all week, and finally finished reading it all. I am new to overclocking, and have managed to get a nice and stable 3.2GHz on my E6600 with air cooling (400*8 - FSB:RAM = 1:1).
Here's a link to my Orthos test: http://img170.imageshack.us/img170/8...testit6.th.jpg
My only consern now is my Geil ram. It is rated 4-4-4-12 @ 800MHz, but the board won't POST if I set the STD timings to manual :mad: . This means I'm stuck with 5-6-6-18 timings. From what I've read here, this is because the board is setting too low tRFC.
Is there nothing I can do to fix this besides waiting for a new bios? It seems like a lot of people are having the same problem...
Have you disabled hyperpath in bios?Quote:
Originally Posted by Pluppo
Hey guys, I'm going to be overclocking my buddy's rig tomorrow with this Mobo... We are replacing the stock HSF with a XP120 and Scythe S-FLEX fan. My question is, how do you connect a normal 3-pin fan to the CPU 4-pin Mobo PWM header correctly? Do you just connect the fan to the three left pins and leave the "CPU FAN PWM" pin unconnected?
Please reference the pins as mentioned in the manual (See attached pic).
Also do you recommend having the fan speed controlled via BIOS and if so, what settings? If not, we can use Speefan... is that recommended or not?
Thanks!
Assuming its a standard three-pin fan connector with tab relief....
- line-up tab dentent on fan 3-pin plug with tab on motherboard connector
- personal preference, I don't use BIOS fan controls, all disabled in BIOS
- old Zalman CNPS-7000 AlCu with 478 to 775 bracket is quiet at full volts/speed for me
- other fans are large, low-speed, low noise types, with ample CFM
now i am running orthos blend @ 4hrs+ with 413x8, vcore auto, vmch 1.65, vfsb up 1 notch, vdimm 1.9 @ 5-5-5-15.
:D
Yes it's disabled.Quote:
Originally Posted by ROCKSOLID
No matter what memory timings I try at 400MHz FSB, the board won't POST. I I managed to set the memory to 4-4-4-12 @ 800MHz when the FSB was 266, but what's the point of that? This is very annoying, because I could have bought a cheaper ram with high latency instead of this one.
Here are my settings using a template from an eariler post:
ASUS P5WDH Dlx Overclock Settings
CPU : E6600
DDR2 : Geil 2x1Gb PC2-6400 800MHz DDR2 CAS 4-4-4-12
Bios : 1407
VGA : Asus EAX1900XT
HDD : Seagate Barracuda 7200.10 250GB 16MB Cache
PSU : Mist ATX.2.2 600W (same as Coolmax CU 600W)
OS : Windows XP Pro SP2
OVERCLOCK (MHz) = 3.2Ghz
BIOS SETTINGS
JumperFree Configuration
AI Overclocking set to MANUAL
CPU Frequency : 400
DRAMM Frequency : 800
Performance Mode : Turbo
PCI Express Frequency : 105
PCI Clock Sync Mode : 33.33
Memory Voltage : 2.1V
CPU Vcore Voltage : 1.375V
FSB Termination V : 1.3V
MCH Chipset V : 1.65V
ICH Chipset V : 1.2V
--------------------------------------------------------
CPU Configuration
Microcode Update : Enabled
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 : Enabled
Hyper Path 3 : Disabled
DRAM Throttling : Disabled
@ Pluppo,you could try setting ICH V to auto,FSB V to auto,performance mode to auto and bump the memory voltage to 2.2/2.25v.Also,why not bump the vcore a little,run the 9 multi and go for some clockspeed ?
I tried setting ICH, FSB and perfomance mode to auto, 2,3v on the memory, and I still can't boot with manual SDP timings. As for the multi, I get too high temperatures in the cpu in full load when the vcore is higher, and I want to run this overclock 24/7.
Here is someone else having exactly the same problem as me:
AndQuote:
Originally Posted by kevsta112003
And here's what lawrywild says about the issue:Quote:
Originally Posted by suio
Quote:
Originally Posted by lawrywild
i still think you'd be better off on the 9x,even if you dont increase vcore,but thats just me,and each to his own eh?.If it is the trfc,just for testing you can boot as high as you can with manual timings,then memset and clockgen your way higher in windows,just to prove the theory.Also if you cant run more than 3.2ghz or 1.375v without overheating,then something is wrong.
What happen when you set a lower FSB like 366 or 333Mhz? Can You set manual timings? You could determinate the manual/auto breakpoint FSB.Quote:
Originally Posted by Pluppo
I have never been able to boot with the FSB > 400Mhz.
My best stable 24/7 OC follows Lawrywild's efforts, but I found that I had to increase vCore to 1.6125v:
-------------------------------------------------------
BIOS 1305
BIOS SETTINGS
JumperFree Configuration
AI Overclocking set to: MANUAL
CPU Frequency : 390MhZ
DRAMM Frequency :780Mhz
Performance Mode :Standard
PCI Express Frequency : 110Mhz
PCI Clock Sync Mode : 33.33Mhz
Memory Voltage : 2.20v
CPU Vcore Voltage : 1.6125v
FSB Termination V : 1.50v
MCH Chipset V : 1.65V
ICH Chipset V : 1.20v
--------------------------------------------------------
CPU Configuration
****Default CPU Ratio : Disabled
****Ratio CMOS Setting: [9]
Microcode Update : Enabled
Max CPUID Value Limit : Disabled
Execute Disable Function : Disabled
CPU Internal Thermal Control : Disabled
Virtualization Technology : Disabled
Intel SpeedStep Technology : Disabled
--------------------------------------------------------
*Advanced Chipset Settings
*Configure DRAM Timing By SPD : AUTO
*DRAM CAS Latency : 5
*DRAM RAS Precharge : 6
*DRAM RAS To CAS Delay : 6
*DRAM RAS Activate to Precharge Delay : 18
*DRAM Write Recovery Time :24
Hyper Path 3 : Disabled
DRAM Throttling : Disabled
--------------------------------------------------------
boot @3514/390
windows logon ok
TAT temps 54/52
ambient72F
-------------------------------------------------------
I have the E6600 and Corsair RAM PC8500.
My best manual memory timings 4-4-4-12 were achieved at 370 FSB (3333MHz)
Ambient temps in the acreage office have been cool, so the TAT and Coretemp beta processor temps have been acceptable, even though I run on air.
I made a couple of changes to your settings, they are in BOLD. See if you can it now, also do you know what IC hips your memory has? One last thing, vcore might be too low but if you say it's stable for you then I guess it is what it is.
Just to let you guys know that I've gotten another Week27 and it cannot do 450x8 @ 1.5125 like my other Week27, however it can do 400x9 @ 1.5125 no problem and it is able to do 450x8 but @ 1.600vcore. Which makes me think that each CPU has a FSB wall. I'm still testing away.Quote:
Originally Posted by Pluppo
Here are my settings that might help some one. Below you'll see the 450x8 and 400x9 settings (The only diffirent value is the one in (), everything else remains the same). Rock Solid Stabled.
-------------------------------------------------------
BIOS 1407
BIOS SETTINGS
JumperFree Configuration
AI Overclocking set to: MANUAL
CPU Frequency : 450MhZ (400MhZ)
DRAMM Frequency :900Mhz (1000MhZ)
Performance Mode :Standard
PCI Express Frequency : 110Mhz
PCI Clock Sync Mode : 33.33Mhz
Memory Voltage : 2.40v
CPU Vcore Voltage : 1.5125v
FSB Termination V : 1.50v
MCH Chipset V : 1.75V (I have the 1.85vmch version)
ICH Chipset V : 1.20v
--------------------------------------------------------
CPU Configuration
****Default CPU Ratio : Disabled
****Ratio CMOS Setting: [8] ([9])
Microcode Update : Enabled
Max CPUID Value Limit : Disabled
Execute Disable Function : Disabled
CPU Internal Thermal Control : Disabled
Virtualization Technology : Enabled
Intel SpeedStep Technology : Disabled
--------------------------------------------------------
*Advanced Chipset Settings
*Configure DRAM Timing By SPD : Disabled
*DRAM CAS Latency : 4
*DRAM RAS Precharge : 4
*DRAM RAS To CAS Delay : 4
*DRAM RAS Activate to Precharge Delay : 4
*DRAM Write Recovery Time :4
Hyper Path 3 : Disabled
DRAM Throttling : Disabled
CPUZ question>>
I am using 1.36 CPUZ and have ram at SPD for the moment.
Any idea as to why Trc is reported as "1" and then sometimes "24" which should be correct?
TIA
sparx
Why you do´nt update CPU-Z to 1.37?
Does anyone know of any programs that can get SMART data off the Intel ICH7R RAID0? Normally I use SpeedFan but it comes up empty with my 2x320g 7200.10 RAID.
Hi all, im new and been reading here for a long time. I built my new system and everything seemed to work fine. Boots up and posts all information. My problem is getting my RAID 0 to work on the Intel matrix ich7r! Ive grabbed the RAID drivers off the Asus cd and put them on a floppy. Ive made the Matrix array and set up my Bios for it. Also disabled the 1394 firewire and jmicron in Bios. ive hooked my HD's to Sata1 (red) and Sata3 (black) connectors using the RED sata cables. When everything boots up , I hit F6, and install the RAID driver (intel 82801GR/GH SATA Raid Controller Desktop ICH7R/DH ). IT all loads up fine and then proceeds to start loading windows. Gets as far as saying "Starting Windows", hangs for 2 seconds and then gives me the BSOD !. Ive tried Moving the SATA connectors to Sata 4 and other configurations. Still BSOD everytime.
When i use the Orange sata cables onto the Ez-raid ports, Config the Bios for ez-raid 0 and the jumpers, it will load windows and all is good.
I want the better performance out of the Martix Raid 0 instead of the ez-raid0 .
My system specs are:
E6700 L629a434
P5W DH Deluxe Bios 1305
Gskill 6400 2GBHZ
7900 GTO
3 SeaGate 320gb 7200.10 - want raid 0 on 2 and 3rd for storage
Zippy GSM-6600p (G1)
Any help would be appreciated. Right now im going to Reinstall my OS (xp home sp2) on the ez-raid sata ports just to get this up and running for now untill i can figure this martix raid 0 stuff out.
Thanks!
I had a lot of problems with my ocz ddr 6400 xtc ram. My board does 400fsb easy so i wanted to run ram @1:1 since it speced for that. Using default volt was not good. Ruined my os install 2 times :(one i had for a year)
Then i uped volt to 2.05(giving 2.1) and running it@350 stable for memtest and prime. Tried with stock settings(4-5-4-15)if i remember right. Gave me errors after a while. Trired more volt and i reported errors faster, tried less and got lockups. Then i tried 2v and it was perfectly stable@4-4-4-10. Strange board ram combo. Was almost giving up running this ram at stock. Happy now :D
Will now try to max my cpu, using 400x6 now for stock speed when i am testing. Will try 8x400 to see if that is stable.
Thanks, didn't know about 1.37.Quote:
Originally Posted by BulldogPO
I will do that.
jim
Quote:
Originally Posted by ArneJohansen
same here.
Quote:
Originally Posted by Delta
*BUMP* sorry for this, just wondering if anyone has any ideas.... Is it possible for me to run the ich7r raid 0 with one drive on the RED boot sata connector and another one on one of the easy raid (orange) sata ports ??
Thanks!
Your setup is almost identical to mine. E6600, 2x7200.10 on RAID 0 using the Intel ICH7R raid, 7900GTO. I used the ASUS CD to create the driver floppy disc, did F6 upon installing WinXP, and used it. Perhaps you should hold off installing the 3rd hard drive til your raid setup is going. Oh, and how did you setup your drives in the Intel Matrix Bios (Ctrl+I)?Quote:
Originally Posted by Delta
Might be a bad WinXP CD. Can't think of much else that would cause that, despite running into that issue a few times. I did use N-Lite to create a slipstream install of WinXP w/ SP2 and a few other options but there's nothing specific about that, that would fix your problems.
with 2 drives you can use either the red and one black or the red and one orange port. Both should work.Quote:
Originally Posted by Delta
No idea why you're having problems, should just work, however, get the latest floppy create program from the intel site instead of using the asus cd, the intel drivers are a lot newer and give higher performance.
Don't make the raid floppy in windows. Some of the drivers Asus CD's are actually ich8r when you need Ich7r. Either use the asus CD to boot and make a disc in dos or (better) download the correct ones from intel direct.Quote:
Originally Posted by Delta
Hey, thanks for the infromation. I will get the drivers from Intel site and see what happens tomorrrow. I did hit (ctrl+i) and set it all up. Boot screen did show the 2 drives in Matrix Raid 0. I bet its my copy of XP ( dell reinstallation cd with cd key, xp home edition sp2). Its been great for the last 2 yrs. Ive been too lazy to get another operating system, since this one has worked. Maybe i should get a copy of XP pro sp2.
I'll update tomorrow!
Thanks!
It's fine to do it in windows.Quote:
Originally Posted by Ic3man
You just have to remember, that when you press F6, it only shows the first 4 but there are actually more that are not being shown below, you can use your arrow keys to scroll down and find ICH7R Desktop RAID :)
I sent a technical inquiry to Asus, and here is the reply I got:Quote:
Originally Posted by Pluppo
I just hope "probobly" means "yeah we're working on it and it will be out soon" :DQuote:
Dear Valued Customer
We will probobly release new BIOS versions to this MB.
Best Regards
David Hammer
Asus Nordic TSD Support
Any idea when / if they'll release a P5W DH BIOS that stops that horrible shutdown on reboot issue? They fixed it for the P5B D and many others, why not the P5W?
And while their at it… they could fix the IDE detection time or what ever the stupid thing doing when computer boots up:mad: .
I’ve tried everything? And I’m all out of ideas.
Just now! http://www.xtremesystems.org/forums/...23#post1792623 <- go get the Rebootbugfree BIOS 1503 there!Quote:
Originally Posted by Brahmzy
Now i need only 1 thing Asus to do:
enable VcoreConfiguration with C1E/EIST enabled! PLZ!
iLL
hi all, i hade a great news for you P5W-DH users.
There is a new bios out and it solfs really the rebootbug, it has the number 1503.
Please note, that this news will brought to you by the forumdeluxx.de
Works well just installed it :) no more cold boots :toast:
owh got people tried already..anyway since i just bought this board and never flash bios yet, so i wonder whether flash bios from USB thumbdrive is safe or not?
thx!
I have been using thumbdrives for flashing without problems for the past few years, done a few times on the P5W too. Going to flash mine soon cos I can't stand the way reboot is power cycling the harddisks with the older BIOS.
and the OC still over 400mhz , my 1502 locked up at 430 about 15mhz less then before (1305 bios) ? glad they got something going now good job Asus engineers keep it up and bring us more speed !!!!
Flashed and yes, it fixed the power cycling for my 1.85v mobo too.
It's no Problem to use the Asus Update tool under running OS.
I did it many times now and have no problem with the usage.
You just update from a file ( one of the options ) and let the programm do the rest.
1503 BIOS Flashdrive Update Oddness
- flash via BIOS utility and thumbdrive failed
* normal process checking file, erasing, etc.
* begin writing to EEPROM, stopped at "2nd block"
- BIOS recovery normal with renamed 1502 to p5wdh.rom on flashdrive
- successfully installed 1503 via AFUDOS and floppy
This is an early board.
- EEPROM markings: WDH06-0401-7ED5-GS V06
Will have to investigate why later.....
- first time this has happened using ASUS flashdrive method
TIP: (for those with early boards, just in case BIOS recovery is needed)
- copy AFUDOS.exe and your last good BIOS, renamed to "P5WDH.ROM" to floppy
Used the update tool at lunch time. Very easy indeed.Quote:
Originally Posted by TheMaster
Put in 1503 and confirmed it does eliminate the annoying cold reboot.
I missed a fan setting (passive cooling) so I had to press the F1 key when I booted the first time (and the second). Dang. :nono: I'd better document those BIOS settings better.
I'll run it a while before updating my sig. . .:)
flashed the bios and so far it is better than my board default bios (1407)!
with 1407, i cant boot my E6400 at 425x8 @ 1.35vcore, 1.3vfsb, 1.65vmch.. it just stucked before windows login.
I know it's not my processor max because i can did exactly the same setting with biostar 965p deluxe and gigabyte ds3 rev c2..
But now with this 1503 beta bios, it works with flying colors. Passed super PI 1m and right now i'm running orthos blend (by the time i write this orthos @ 7mins).
I know this is 975 board but i hope i can achieve orthos stable near what i got with 965 boards (430x8 @ 1.375vcore)
tRFC? tRFC? tRFC??? :rolleyes: