well, looks like no luck for me on the 430 fsb wall with 0701. I got no where with 450 so I tried 440fsb. turns out the same voltage I'm using prime stable at 430 (1.5vfsb, 1.8vnb) wouldn't boot at 440 and after trying different things, I got the windows screen to load by jacking up the pci-x frequency, sb and sb core voltage. Still no luck getting it into windows though.
It's just amazing to me that 10mhz can make such a difference. 430 no problem, 440 no way. I'm starting to think this board just doesn't have it in it.
You know what? The only thing I haven't tried yet is changing the cpu pll. Zucker2k reccomended I lock it at 1.5v. Any reason I shoudln;t raise it? Can that harm the CPU or could it help the fsb issue?
Feel free to change it. It works for some people, has only created instability for me, but that may be due to other factors. I've shown you overclocks of 8x450 easy with everything at the lowest possible setting. My bet is you're overlooking something, all those voltages you mentioned are just too high. The 4.25ghz priming action you see in the screenie is done with 1.650v VNB @ 500 FSB! It was just a guesstimate so I think I can get it even lower when I find time to play with the overclock again.
This is a note to all; TO BE SURE A PARTICULAR OVERCLOCK ISN'T WORKING, AFTER YOU REBOOT, GO BACK INTO BIOS (IF YOU'RE NOT DUAL-BOOTING), TURN THE SYSTEM OFF. UNPLUG IT FROM THE WALL. WAIT 30 SECONDS AND TURN IT BACK ON.
THIS IS TRUE FOR BOTH MAXIMUS AND RAMPAGE FORMULA. I DON'T KNOW WHY, PROBABLY A BUG.
Last edited by Zucker2k; 12-12-2008 at 07:55 PM.
maybe I'll hang out at 430 for a bit then, install the NB block I received today and see how low I can get the voltages. There are enough settings on this board that I do not truly understand that I'm sure you could be right in that I'm just overlooking something.
Just installed my new QX6850 (old tech I know, but good price) and testing @ 4GHz without breaking a sweat.
Will post some screenies in a bit.
Also, updated to 0701, liking it and not noticing much difference between that and 0308.
Bios 0701 is giving me the infamous Asus Termination Voltage bug, where it jumps from 1.2v to 2v...
Will the CPU be ok @ 2v vFSBT for 20seconds? Saw it in bios, fixed it, save and reboot.
So, I have posted a few times here in the past and check in on this thread every so often. I am personally at wit's end with this board today, the longer I own it the quirkier and more faulty it apparently is becoming.
I bought my Maximus Formula in early October last year when it first hit the market if memory serves correctly, I had paired the system with a Corsair Dominator 4x1GB DDR2-1066 kit. In the beginning, it was possible to install one module, boot to BIOS (0401) and up the voltage (kit uses 2.2v by default, and I've been running them on 2.35v) to the required level. I could then install the other 3 modules and get the entire kit to boot.
Each time I made a change that kit did not like, it required to me to go through the process of reseting the CMOS and installing one module, upping the voltage, and installing the other modules. I upgraded to BIOS 0505 but it had no impact on the memory booting (DET DRAM) issue. I had setup the system to run a modest 320x9 (Q6600 B3) with DDR2-1067 memory divider in play. If I was lucky enough to get the system to boot up, I would leave it turned on for months at a time on a UPS. The overall system is apparently very stable and reliable, but the DET DRAM issue plagues me if I ever have to do a cold startup or snags the occasional reboot.
Fast forward to October 2008, I have to shut down the system one day to move some furniture around, but now the system does not let my old trick of installing one of the modules and booting to change BIOS settings. With a single module installed it would still display DET DRAM after a full BIOS reset. Since memory prices had dropped, I picked up a 512mb DDR2-667 module for $8 at newegg and was able to boot the system and up the voltage, and install the Dominator DDR2-1066 4x1GB kit. After this fiasco, I upgraded the BIOS to 1207 from 0505 hoping it might address these issues, but nothing appears to have addressed the DET DRAM issue.
So jump ahead to this week, after a spontaneous reboot the system restarted and then froze during the nightly backup the next day. After shutting it down, and using the DDR2-667 module to perform the same usual tricks, I can only get one of the DDR2-1066 modules at a time to boot with the new BIOS settings. Switching out 2 or more of the DDR2-1066 kit modules causes the system to hang at DET DRAM. I tried upgrading the BIOS again to the available beta 1302 version, but it appears to not to address the DET DRAM issue.
I should note this latest fit of interoperability is being attempted under the lightest of settings, full auto and default clock settings, DDR2-667 for the DDR2-667 diagnostic module and the DDR2-1066 Dominator kit. I have tried using the 333/400 straps with transaction booster disabled and relax 0/1. No combination of settings appears to address the issue, nor have any of the BIOS updates since the time this board came available. To say it's frustrating is an understatement, I'm ready just to toss the system in dumpster.
Any thoughts? Anyone have a Maximus Formula SE with Corsair Dominator DDR2-1066 4x1GB kit who can post their BIOS version and settings for me? I'm not a happy customer at the moment.
Last edited by Budious; 12-13-2008 at 11:39 AM.
OK, so you have RAM that does not work at the default settings that the motherboard operates at, and you are angry at the BOARD?
Obviously, since the board works fine with the 667 stick, this isn't an issue with the board.
Perhaps now you've developed a bad DIMM?
I would agree, one would test each stick independantly with memtest at stock speed / volts,
DET DRAM is a incorrect PL setting, set your ram strap and FSB then set the correct PL level, DET DRAM will no longer happen to you.
I run Corsair Dominators on my MAX X38 SE and have since the day I bought it (Novemeber 07), best ram ever hands down. I find they play very nice with the board and do anything I ask from them.
![]()
All the modules are good as far as I know. Like I have said, this system has months upon months of uptime on it, the issues I'm having are at the boot level and detection of the memory. Once the system gets up and running it can stay up for months on end without problems. Windows applications run flawlessly, I frequently run multiple virtual machines and games simultaneously. Tools such as OCCT and Super Pi operate flawlessly. I think the freeze the other night was heat built-up from me neglecting to knock the dust out of the heat sinks as of late.
I tried the modules separately and in different slots, but the system won't boot any one of them installed separately in any slot with the BIOS set to defaults. I'll try setting the memory timings manually and see if will help me get all four modules swapped out and up and running, but as I said, it's a problem with the BIOS not detecting any of the modules with BIOS set at defaults. Whether or not I should be blaming the board or the memory is subjective, I'm just angry because of spending so much time with it and not finding a solution.
I know what you mean bud. My Ballistix did 1113Mhz; they were 667's, but, I had no issues booting with them at stock voltage.
My current 'el cheapo grande Kingston DIMM's likely won't OC much, so I haven't pushed them at all, as I'm sure you can tell from my sig.
I have not experienced the problem you are experiencing, but if you had better luck with an earlier BIOS, perhaps flashing back would be a good idea.
Of course not.
Random freezes and reboots are usually bad ram
His reply is "All the modules are good as far as I know" so no he has not tested them, untill he does there is no point in speculating anything
Plus his sig state's he's running bios 505 and wonders why there is issues
Last edited by Grnfinger; 12-13-2008 at 02:57 PM.
Hi there
I can boot to windows, but Adobe Lightroom and every game crashes the pc
any thoghts?
My bios is on page 300I did try lower and higher voltages with no sukcess
thx
I think I'll give also this 701 a try![]()
OS: Windows XP Pro PL SP3 / WIndows Vista x64 ULTIMATE pl / Mac Os X 10.5.5 - Ideneb v1.3 x86 project
Processor: Intel Core2 Quad Q9550 'C1' - VID 1200v @ 3.68ghz on 1.304v 433x8,5 (air noctua NH-U12F)
Mobo: ASUS Maximus Formula BIOS Rev. 1302
Memory: 4GB Geil Black Dragon DDR2 800 (1.8v) @ DDR2 866 5-5-5-18 on 2.0.1v
Monitor: Lg 227wt 22" lcd
Video Card: Gigabyte Geforce GTX260 OC 896mb @ 690/1240
Storage: 2x 250GB seagate 10 - RAID 0 + 500GB 32mb seagate 11 + 320GB seagate 11
PSU: Enermax Infiniti 650W
Case: Antec P182
3dmark Vantage: 11940 and will be morea bit
I don't post here often, so I didn't update my signature. But your post makes me wonder if you even read my post as I posted my BIOS upgrade path, which was 0401 -> 0505 -> 1207 -> 1302 and I said that I've experienced similar problems under all BIOS. Also, I did not specifically mention testing each module individually, but I have in the past when I was still having these issues. I used Windows Memory Diagnostic (including extended suite) and have used Super Pi (which is a good indicator of memory stability) under Windows with an instance on each core doing a 32M calculations. So, yeah "I'm pretty sure it's not the modules" and I'll stand by that statement.
Signature updated and bolded just for you...
Likewise: I should point out your signature indicates:
G.Skill F2-8500CLD5-4GBPK @ 1130MHz
G.Skill F2-8800CLD5-4GBPI @1142MHz
So where's those Dominators you claim to be running?
Last edited by Budious; 12-13-2008 at 03:45 PM.
Because I can swap out the lower spec'd module for one module of the kit at a time and the system still boots. All the modules are good and will boot to Windows and pass Super Pi or pass Windows Memory Diagnostic bootable cd test suites. But none of the modules will boot from BIOS defaults on their own, nor can I use the set BIOS settings with lower spec'd module and swap out two or more of the four modules of the kit. This problem is not new, I have had it since day one in one capacity or another, but it's getting worse and not better. The modules have always worked fine once they get past the DET DRAM stage of the post process.
Also, you can see my last post in this thread before today was related to this issue as well:
http://www.xtremesystems.org/forums/...postcount=3503
The difference was back then, it would not reboot immediately reboot without displaying DET DRAM but if I left it off for a period of time and tried it later, it would boot. This is part of the "getting worse" description of the problem, as I just wish that leaving it off for a while would still work.![]()
Last edited by Budious; 12-13-2008 at 04:01 PM.
Memtest86+ pass?
Tried flashing back to the previous BIOS?
Hey OverKill,
Can I get the details of your BIOS settings?
Thanks
ASUS Maximus Formula Special Edition / SE X38 RAMPAGE 0803 BIOS
Q6700
Lapped TRUE
G.Skill 8500 2x2GB
9600DT 512MB
X-Fi Extreme Music.
Samsung 1TB & 2 WD 200GB (trying to RAID)
PC Power & Cooling 750 (Black)
Row Refresh Cycle Time??? Is that the tRFC? And 52 is what I want for 1066?
ASUS Maximus Formula Special Edition / SE X38 RAMPAGE 0803 BIOS
Q6700
Lapped TRUE
G.Skill 8500 2x2GB
9600DT 512MB
X-Fi Extreme Music.
Samsung 1TB & 2 WD 200GB (trying to RAID)
PC Power & Cooling 750 (Black)
2x1GB Crucials fried? How about what you could suggest for my Q6700 and 4X1GB Crucials 6400 (the new 2.0V versions)
Thanks
ASUS Maximus Formula Special Edition / SE X38 RAMPAGE 0803 BIOS
Q6700
Lapped TRUE
G.Skill 8500 2x2GB
9600DT 512MB
X-Fi Extreme Music.
Samsung 1TB & 2 WD 200GB (trying to RAID)
PC Power & Cooling 750 (Black)
Bookmarks