I read somewhere that the firmware on certain hard drives had to be updated to work with some raid controllers. Might give that a try.
Printable View
I read somewhere that the firmware on certain hard drives had to be updated to work with some raid controllers. Might give that a try.
Funny thing - the HDs do work with the mobo RAID - just not the external RAID controller (which is fairly new, as well).
Worth a shot, if there's any firmware update for WDs
No firmware updates on these HDs. The EX8350 is going for RMA, tried it in another board, and no POST even.
You might wanna get as much cooling into the passive cooling cuz mine runs really hot. Although my average mobo temp is like 38C temp on the heat pipe is about 50C.Quote:
Originally Posted by Nocturnal
I fixed my passive cooling a bit. I didn't realize i had the K8>NB going at like 1500. So I reduced the multiplier to 4 and the temps went down. I also ripped off the asus logos to get more air in the heat sinks.
I think most people who have high temps probably have their K8>NB going too high.
I have problem with my A8N32 SLI DX and my memory Corsair 2x1GB DDR500MHz. This memory are very unstable on my mobo. WHY? I Tried lot of setings a Tried 2,7-2,85V (memory are very hot:-(
Have anybody same memory and mobo? I need your BIOS screen or screen A64 tweaker program.
THX
Your not the only one, I have issues with my Mushkin ddr500, the board is just not a great board, its very picky.Quote:
Originally Posted by Neller
The board looks really good
Yea I have major problems tweaking my ram too. But that's probably cuz I'm not quite sure wut I'm doing.
But, what I do now? Can new BIOS helps me? or I must buy other memory?Quote:
Originally Posted by Pinnacle
I also had problems with Mushkin Redline UTT.Quote:
Originally Posted by Pinnacle
By the way, I've noticed a cpu temp decrease with bios 1205. I had around 39-40ºC idle at 2.2GHz 1.25V, now 35ºC at 2.6GHz 1.325V :)
Would be nice if that's the case, however I had memtest failures on anything above 1109 BIOS, regardless of the memory timings, so please do run memtest, and let us know if it's just my bad luck or a general BIOS 1205 problem.
Quote:
Originally Posted by dsl
I had errors at Memtest's test #6, but i can run Memtest for Windows flawlessly.
Exactly. 1205 is very complicated and flawed BIOS release - head over to ASUS forum, you'll see all known problems.
BTW, temp decreases are usually attributed due to Cool n' Quiet being Enabled by default in 1205 as opposed to earlier releases.
Quote:
Originally Posted by dsl
Yeah, I've considered all those issues reported on Asus forum before flashing to 1205. With Silicon Sata Controller disabled, I have no major problems with this bios so far, except AiBooster reading some crazy clocks often (showing 3150 or 2042MHz when real clock is 2600MHz).
Btw, I'm not sure but I think C'n'Q was disabled by default. Guess the temp decrease is something about sensor calibration..
No need to overvolt high density modules try lower mem volts and differents tref if wanna keep em stable at speed.
Quite interesting, AIBooster is part of CnQ ;-)
Re-check it, mate, and don't let MemTest #6 fail, it's not as harmless as one thinks.
Quote:
Originally Posted by dsl
Hello all;
I am having a problem OC'ing my system I am hoping you can help with. I have the A8N32-SLI Deluxe, an X2 4400, 2x1GB of the Corsair 3500 LL PRO, an ATI All-In-Wonder x1800XL, Creative X-Fi music sound card, and a Silverstone Zeus 600 W PSU. Cooling is a Zalman 9500, My system runs Prime95 stable at default settings. I am using BIOS 1103.
I decided a good place to start was Cisco's guide, which suggests an initial OC of FSB 250, Multiplier x10, K8>NB 4x, Memclock 166, Memory Command rate 1T, all other memory settings auto, Cool 'n' Quiet disabled, PEG link disabled, SB>NB freq 200, SB>NB multiplier 5x, K8>NB and SB>NB linkwidth both 16x/16x, PCIe freq 100, all overvolts off, and the VCore at 1.35.
At these settings, the machine boots, and core 1 runs Prime95 stable for hours with CPU temps of 47-48. The problem is that I can't get core 0 stable at all. I have boosted the Vcore in increments to 1.435. Core 1 runs Prime95 stable for at least 6 hours, but Core 0 fails within seconds if I am testing both cores simultaneously (sp?). Interestingly, I ran Core 0 by itself, and it failed Prime95 after 2 hours. One observation...when I made the last adjustment in Vcore (from 1.4275 > 1.435), the Vcore as reported by AI booster and CPU-Z actually seemed to go DOWN. I was getting a reading of 1.42 from both. Also, my VCore seems to fluctuate a bit (according to CPU-Z) from 1.408 to 1.424 from moment to moment.
Here is my thinking. I am new to this, so bear with me if I say something stupid. Since Core 1 seems stable, the problems with core 0 cannot be attributed to any of the memory or bus settings. My initial impression was that Core 0 just needed a bit more VCore to function than Core 1, and it does run longer before failing with a higher VCore. I cannot fathom why Core 0 fails within seconds while I am testing both cores, but runs for 2 hours if I test it alone, unless there is a problem with power to the CPU.
Am I right in suspecting that either my PSU or the MB is bad? My understanding of these things is limited, but I do know that the MB takes care of distributing power to the CPU, right? My PSU should be more than adequate for my system, as far as I know. Or I just have a bad CPU for overclocking? Probably the best thing I could do as far as isolating the problem is to drop my CPU into a different MB and see if it works at 250 x 10, but I don't have one available.
Any help you guys could provide would be greatly appreciated.
Mark
For all those with memory tweaking problems... try the "black" set of DIMM slots.... I have Corsair DDR400 cl2 2GB Kit and had rough time getting it stable @266MHz 3.0-3-3-5-1T in the blue slots without a success... moved them to the black ones and voila - it's stable :)
@mhorgel: I think your PSU is up to the job. I suspect you have a bad clockin' CPU, unfortunately :(
@TodB: I will try those black slots, thanks for the tip :)
Quote:
Originally Posted by TodB
^^^Ditto
@mhorgel Yea I have the exact same problem with my core 0.
It MIGHT be because of the cpu but for some reason core 0 just seems TOO weak to be true. My core 1 overclocks very well and primes for hours while the other core fails in a few seconds. I try booting the vcore to 1.6v but it still is unstable. I haven't figured out what's wrong yet. I might get another cpu soon to test it on but that won't be for a few weeks.
Have you tried eneabling the overvolt option (+0.2v)? If not then set your vcore to 1.25 and then enable the vcore ovevolt to get 1.45v. For some reason the board will not go above 1.42 without the overvolt option enabled(mentioned elsewhere in this very thread).
You can then increase vcore in small increments (with overvolt enabled) to help stabalize core 0, I wouldn't personally go above 1.55 on air. Aslong as your cpu dosn't hit 60c+ on full load then you will be fine. It sounds as though core 0 is failing due to not enough vcore being supplied to it.
If that dosn't work then relax your timings to say 3-3-3-8 instead of the spec 2-3-2-6. Or even put it onto a 133 divider.
You want might to use the mem tweaking guide. Its memory related. THe link is couple of pages back.
That explains why my reported voltage from both AI booster and CPU-Z does not seem to increase when I increase VCore. I had forgotten that peculiarity of this board...Quote:
Originally Posted by Ic3man
I decreased the FSB to 245 and both cores seem stable at 1.42v. Temps are 52-53 C during torture testing. I have an Asetek WaterChill kit on order, though it will take me a while to set aside enough time to install it...looks like a weekend project, hafta strip the system, remove the mb, and do some minor case mods.
I will probably stay at 2.45 Ghz for a while, until the watercooling is in place, and I will try gently pushing the VCore after that.
About the memory divider, I was thinking of trying 183, as my memory is PC3500, which can go as fast as 216, and 245/200*183=224, so I was thinking it should work.
Thanks again to everyone who responded to my query!
Mark