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