I still can't get these thing stable, i got it stable for abit, but it destabilized again.
Printable View
I still can't get these thing stable, i got it stable for abit, but it destabilized again.
Hey guys, just wanted to say thanks for all the great info posted. I've been lurking here since the 2nd page of this thread. :p: I purchased the board about a week after. It just sat while I was waiting for parts. I still don't have everything I want but a leak in the Asus Deluxe build forced a tear down. I decided to do a temp build with the Maximus just to make sure everything worked before redoing the W/C. This thread has reminded me sooo much of the ICFX3200 T2R/G board's thread. :( So many problems and unhappy people. :confused: Fortunately despite using 4GB of Ballistix 8500 things went well for the most part. I had no luck with raid 0 and XP x64 despite the latest drivers. Vista 64 installed Raid 0 without a hitch. The failure rate of the Ballistix ram is troubling and I can't help but think people aren't paying attention to the overvolting of the ram. I set the bios for 2.0 and got 2.1 in Everest and 2.3 in AI suite. :shocked: I backed down to 1.9 and now Everest reads 2.0 and AI 2.05. This is running stock 1066 speed. It's been folding stable for a week. My NB was running 45C despite chilly 65F ambients so I decided to reseat the NB and SB. Whoa! They used mega amounts of adhesive. NB was completely covered and SB almost.It took at least 30 minutes and felt like 45 to remove the block and HS with extreme care. Check out the pix. With 4 screws and a back plate why on earth did they feel adhesive was necessary???? I probably won't have this rig back up with my W/C and be ready to OC till next weekend. By then maybe bios 902 will be up. :) And I won't have my 3870s in crossfire till about the 12th. :)
http://img407.imageshack.us/img407/7452/p1010016ku2.jpg
http://img260.imageshack.us/img260/1585/p1010018ek8.jpg
Edit: I have an active ram cooler coming for the Ballistix. Even on the my Asus deluxe they could burn you running at the rated 2.2v. That ain't right.
Hi. I just purchased Asus Maximus Formula and this awesome board fried my memory.It worked before, now it doesn't.
I have some questions...maybe I get an answer:
1. The revision of the board is written somewhere on the PCB, sticker, box,etc or you are supposed to have a hunch when you hold the MB in your hand?I spent 30 minutes trying to find any hint and I failed
2.Is there any 4 GB kit that WORKS with this board without errors in memtest 86? I understood 4x1 GB is more problematic that 2x2 gb.
3. The errors from memtest are motheboard's fault or memory's fault?Is it possible that the memory is affected by higher voltage , as Asus Probe shows? In my case bios says 2.2v, Asus Probe 2.29 and Asus AI suite over 2.55 v on a Vista-64 bit os
Should I RMA this board, since I can not run anything only with 1 dimm-is it defective...what the hell...300$ and a set of 4gb memory with errors which goes back to Mushkin.
Sorry, I know...too many question. But I bought the MB 7 days ago and can still return it. I am thinking taking the Gigabyte instead, too many problems with this board.
Please advice...Thank you
1.There is only 1 version of the Formula SE. 1.02G. It's between The PCI-E slots in the lower right hand corner of the Maximus Formula. :)
2. Somwhere in this thread it was stated memtest 86 does not work with the X38 chipset. Don't use it. How does the computer run at stock settings? Does it show any signs of memory errors in normal use? Is it Prime or OCCT stable?
3. If you had read any of this thread, you would know the MB overvolts ram by at least .1 and you should adjust for that in the bios so you don't fry it. At 2.0 in the bios AI suite said I was 2.3. Everest said 2.1. I tend to believe Everest but... many have lost ram on this board. :shrug:
4. I'd say ignore memtest and see how it performs doing what you usually do. If it's locking up or exhibiting intolerable behavior RMA it. Especially if the ram is know good from another rig. If the ram is new and unused... you may really have bad ram. I've had more issues with new ram than new motherboards. HTH. :)
Well, I'm running now with the following settings, but my Idle temp is reporting as 60C!! (it was 42C with my 680i @ 3.6GHz)
Ratio 9 Freq 400 (3.6GHz - originally 2.4GHz)
CPU 1.5
CPU PLL 1.6
NB 1.49
DRAM 2.2
FSB Term 1.4
SB 1.15
SV 1.5 1.6
... why on earth is this burning so hot - especially with my liquid cooled system?
Idle @ 2.4GHz was ~28-30C...
What BIOS? Try using CoreTemp.
I have 4 * 1 GB Kingston DDR2 HyperX PC9600 CL5-5-5-5. They are rated for 2.3-2.35v, but I run them at 2.2v ( 2.09 in bios ), and they don't get hot.
They are able to run CL3-3-3-6 @ DDR 833MHz on the maximus.
Haven't experienced any problems with them at all! I Love them!
They are cheap, and they deffently deserve more attention!
Yep, hence why it's better to test many programs for benching. I'll try to give you some situations showing that necessity, and limitations of every program
OCCT in RAM mode proved to be the more stressing and revealing errors on NB-RAM combo. Do remember, that even an error code 4 (CPU) can be due to a NB or RAM error (vNB, vDDR, RAM timings, STRAP...). If the NB and RAM return erronous values to the CPU, than OCCT and any other program will have a round off error check and read it as a CPU error, so be careful interpreting the results... (Sine I changed my RAM to Hyperx 9600 and used a 4:5 multiplier to get 974MHz on them, I need 1.55v on my NB instead of 1.45 for 1:1, otherwise OCCT in RAM mode will return me an error code 4). The more you OC your RAM, the more you need to volt your NB too, even if the FSB is unchanged
Also, OCCT in CPU mode should be as effective as Prime95 small FFT in testing CPU stability. On the other side, to check cooling limits of the CPU, small FFT is better as it generates more heat. Do remember, that no program will generate as much heat as small FFT (if we exclude the crazy intel TAT).
Finally, a F@H for some hours should be a necessary check, as it is a real program that can much stress the CPU-NB-RAM all together.
As a Prime95 Blend test uses more RAM than OCCT, it can reveal more hardware defects in RAM than OCCT, like Memtest would do. Also, Blend test will heat the CPU more than OCCT in RAM mode, thus unveiling an unsufficient CPU cooling. But definetely, OCCT in RAM mode, will stress your RAM an NB much much more than Prime Blend.
Hope my explanations show you why you need many programs to test your OC stability.
The final test, will be every day use to see if you have reboots, BSOD or random strange program or memory access violation errors
With my ADVICE - this "intervention" takes 30-40 sec. :)
Interesting, I've been using V3.3 since I got the board and as far as I can tell it works fine. When Vista was telling me I was having memory problems I fired up Memtest and found which sticks were faulty. I've also used it to figure out my sub timmings prior to running OCCT and I've been completely stable because of it.
For not working, it has been doing a pretty good job for me.
I wonder if most people are using Memtest86+ v1.7? Or Classic Memtest86 v3.3? Because the chap above me who uses 3.3 and has no issues could be on to something... I know I've only tried 1.7v '+' version?
anyone stable with 430x9 with a Q6600?
I use these settings:
get stable only 20min /OCCT
Vcore=1.45
FSBT=1.65
NB=1.68
SB2=1.65
SB=1.10
DRAM=2.2
all other settings (auto)
maybe anyone has a suggest
I was a week ago, but I've been so many problems lately, I think these board hates my Cheap 680W power supply, So I'm waiting till I get my Antec 850W back from RMA to see if its that, If its not, then either the memory controller on the X38 is dying or my Memory is dying, I can't say for sure right now.
deleted - reposted down below
The strange thing is that with a pair it works with memory in single-channel, in blue and white slots but when I stick it in dual-channel it is stuck and won't boot at "checking dram" or something similar. Does it mean the board is defective or it's a memory issue?(the other pair is stuck from the beginning, wouldn't ever boot)
I'm using OCCT 1.1.1, and don't see an sliders and when it fails, it just says, "Crashed", no hints... What version are you guys using?