im currently using a modded bios which have been changed to a rampage formula bios ver 0219.....
im currently using a modded bios which have been changed to a rampage formula bios ver 0219.....
Should I enable DRAM Static Read Control or disable it? I have always had it on enabled without a problem.
Morning #1
After a 8 hours I am happy to report that the computer does in fact properly cold boot with my PC8500 ram at 1066MHz. It appears that having the north bridge voltage at 1.55V instead of 1.43V is working so far.
Side note:
Enabling DRAM Static Read Control increases the memory controller performance level; disabling it decreases it. If you disable it you may experience lower performance from your ram. If it's stable with it enabled keep it there unless you are experiencing other non critical OS, program or gaming problems like stuttering, hitching, pausing, programs closing do to errors, etc.
Can somebody tell me one thing because I'm clueless.
I recently put 4x1 GB of ram (planing to move on 64bit win) and bios shows that I have only 3328MB. I know that 32bit win doesn't show above that but shouldn't bios show 4GB? :confused:
Thanks in advance
New sudden instability with this board...again. I tried a higher overclock, it wasn't stable so I backed down again. Now the old 110% stable (literally over a month 100% load 24/7 Folding Dual SMP Clients) is as flakey as :banana::banana::banana::banana:...
I can't wait until I have the money for a DFI board and to get away from this Asus POS. :(
i've tested 6 E8400's on my MaxForSE and each one i was able to just pop it in and set the FSB to 450x9 vcore 1.3, ram 1:1 at 900 and run 100% stable in windows.
i can't get past 450fsb though. other mobo's i can go way higher.
===================================
on a separate note: how the effing sh do you get the thermal crap off the back of the stock blocks? i've tried everything, nothing dissolves that crap. what is it? cement?
well i got another coolermaster 850w psu and i got the same results... I then put a 300w cheap psu in and it worked no fans at 100% with no post it just booted up straight away. Its funny as the psu worked fine on the p35 and 680i chipsets but not the x38 and x48. I guess its time to get a good psu and not a £136 piece of c++p....
Not sure if any of you have read this, but check out this AnandTech article about tRD and command level (CL). I'm currently running CL7 in the 333 strap at 6:5 and 1.49 vNB, but it turns out the same is possible at CL6.
ARTICLE
This really unlocks the potential of this rampage hack.
ir1z;
try disabling load-line calibration.
I'm having to retest my overclock with the 0219 bios. After trying a faster overclock it proved to be unstable so I backed down to my 110% stable settings...apparently they're unstable too now! :(
Nope. The problem is an odd one. The FSB is stable if the CPU is clocked lower, and the CPU is stable if the FSB is clocked lower and the multi increased to compensate, but both together and it starts to randomly reboot again.
It just baffles me. I'm testing the FSB again, and then I'll do the CPU once more...
Yes, I made adjustments. Everything tighter than tRD 7 at sigged results in DET RAM for me, even 450FSB which they say will work with 1.6 vNB. I haven't pulled any DIMMs, though. I'm still 4x1. Maybe this weekend I'll mess around with that.
It was a really good article, and it really helped me understand what's going on, though. Now it makes perfect sense that running tRD of 8 with all the phases pulled-in resulted in the same bandwidth.
I've been trying around with Rampage BIOS and I think it's quite okay. The only error I've encountered is that the BIOS shows me pull ins for 10 cores at my current FSB. On a single q6600, nice eh? :)
Anyway, I think the q6600 I bought is a volt pig. First some volts and temps loaded with FAH (CPU PLL is set to Auto, I hope that helps getting the box stable):
http://bandwidth.se/imgs/101/227/everest.jpg
Near 8hrs OCCT RAM (stopped that myself, I'm guessing it would have done just fine..):
http://bandwidth.se/imgs/101/227/over7hrsocctram.jpg
And some 17hrs p95:
http://bandwidth.se/imgs/101/227/primescreen.jpg
Now I'll just wait a few days to see if it's craps out on me again. To gain only 100 Mhz over these values, be it on 8x or 9x the chip needs over 1.5 vcore. Amazing, huh? :shrug:
Stupid thing is that it doesn't like more FSBT, in fact it either destabilises it or has no effect whatsoever. If I'm going water later this year I think I'll beat the chip with some more of this sweet vcore. :devil:
I recommend reading the article I linked on the previous page. It will explain where the number of pull-ins is dependent upon which NB strap you're in. It looks like you're 6:5 in 333 (like I am). The 333 strap has 5 pull-ins per channel, or ten total. This can be easily verified by changing the strap in BIOS (no need to save or restart).
Thanks for sharing your screenies! What is your desktop background? It looks cool.
I have set PL7 and disabled pull-ins, I find it give a slight increase in bandwidth, I hae also tried 6 and cant get the :banana::banana::banana::banana::banana: to boot.
Adjusting timings and strap now to get a bootable pl6 and see if its worth the headache.
I have Rampage bios 215 , going to test it tonight aswell
Heh, thank you, I bookmarked that link for further reading tomorrow. Too sleepy now for reading it.
And for that wallpaper, it's from AnimePaper.com, a very nice community, you'll have to register and earn (be it own wallpapers or comments or whatever) your wallpapers through active participation though.. :up:
Here is another excellent article regarding tRD and other things that I wish I could understand better.
http://www.anandtech.com/cpuchipsets...spx?i=3184&p=8
edro
hook us up with 215!