v2 registry patch suppose to erase more things :) anyway good that it worked out...
Printable View
v2 registry patch suppose to erase more things :) anyway good that it worked out...
The modus switch is available in the Creative folder but if you try to run it you've got to select an other sound card.
Could it be that it's a feature that they locked for the SB X-Fi MB and that can be unlocked if you would add it to the supported sound cards?
I've found a X-Fi Mode Changer but I didn't try it yet.
It wont work... X-Fi MB have locked functions and have only one "mode" that operates on... There is no Game/Entrataiment mode like on "real" X-Fis.
Good work SoLoR i'll have to try the new drivers. BTW how's 6610 looking cause if there looking good i'll hold off on 6600
I had them working, but find out they are unstable... they are crashing creative audioprocessing objects that where made for 6600 drivers... so they can work for a while but then just randomly you lose all effects... I did however sended inquiry to asus asking them about new drivers... but didnt get any answer yet..Quote:
Originally Posted by leo27
You're going to have more luck if you open a new thread about the SoundMAX drivers on the ASUS Rampage Formula forum.Quote:
Originally Posted by SoLoR
You'll be surprised how many users are having problems with their official SoundMAX BETA WHQL :confused: drivers.
well i cant talk about moded drivers and unlicensed x-fi software there :) what i did was, i found real serial number of rampage II gene on the internet and gene II boards have x-fi software officaly avilable and soundmax 1989B chip and said i have problems with sound on gene boards and if they intend to release new drivers :DQuote:
Originally Posted by Alien Grey
You don't have to talk about the SB X-Fi MB software. It doesn't matter if you mod the drivers and use the Creative X-Fi software if they release a new driver for the ASUS Rampage Formula to replace the BETA driver that works well then you can MOD it again. ;)Quote:
Originally Posted by SoLoR
Or is this driver not good enough to use with the Creative X-Fi software?
Well thing is, Rampage Formula drivers comes with SonicFocus APO dlls and when you mod them with creative dlls there might be incompatibility (crashing), like in case of 6610 driver from Intel DQ45CB mobo. Also considering II Extreme, II Gene, Crosshair III Formula are all much newer mobos that all use same drivers (Soundmax with Creative APO), there is bigger chance we get new drivers for that :) Thing is... not sure why but ALL drivers should be "refreshed" at least every 6 months, but we know how Asus works...Quote:
Originally Posted by Alien Grey
I see what you mean. It's a lot easier to MOD the driver that is already using the Creative X-Fi software.Quote:
Originally Posted by SoLoR
SoloR lost somehow, can you post again the final upgrade procedure from 6590 soundmax to 6600, with updated links?
Well honestly not sure, because i cleaned registry manualy and then later i made that registry patch :) But this is how it "should" work, uninstall 6590 drivers, reboot, run cleanup6590-v2 registry patch, go to system32&syswow64 and remove ctapo*.dll, daisywrp.dll and ppchain.dll if they are still there, install 6600 and hope for the best ;) and again 6590 are just one big of a mess, should get rid of them as soon as possible... all later updates (if there will be any), will be easly upgradable without all that cleaning mess... Also i think this cleanup is only needed on x64 systems...Quote:
Originally Posted by Spyrus
K installed with no problem. Nice :)
Nice job SoLor! I just replaced my old Soundblaster Audigy LE PCI with the SupremeFX II, which i never used before because of the crappy Soundmax-drivers. The sound is impressive with the modded drivers!
Hello...
I was away for a while and now I' m reading about those x-fi modded drivers for the Rampage onboard soundcard. I've a real X-fi so I'm really not interested in it, but I was wondering if you managed to enable the DTS-DD Encoding / Decoding. I found a fix on another forum to re-enable the driver DTS-DD Decoder only, but I didn't find anything for the DTS-DD Encoder.
Was anyone luckier than me?
;)
Cheers!!
P.S.
Alien Grey, any news about a newer BIOS better than 0001 ?
:rolleyes:
No news from ASUS about a new BIOS.Quote:
Originally Posted by Antineutrino
I did my first stress test with BIOS 0001 and Windows 7 at 4.05GHz and I'm also testing the Creative X-Fi software. I'll post some screen-shots later.
Where did you find for DTS-DD decoder? :) I tryed to integrate creative DTS & DDL encoder but it does not work, even tho that license maker creates licenses for this as well, its disabled for some reason, maybe hdaudio chips are just not enough to handle this.Quote:
Originally Posted by Antineutrino
Also i removed couple of applications from software pack (crap like Karaoke player and Wave editor...) if anyone wants any of this back i can add it, but just seems useless...
Better performance needs more voltage so I had to bump the NB Voltage from 1.27V to 1.29V in the BIOS or from 1.25V to 1.26V real. :D
http://i431.photobucket.com/albums/q...RD6-tREF-6.jpg
The question is does EAX actually work with the MOD drivers and the Creative X-Fi software. :yepp:
So I installed a game with EAX Advanced HD and fired up Alchemy.
http://i431.photobucket.com/albums/q...medetected.jpg
Added it to have EAX Advanced HD enabled.
http://i431.photobucket.com/albums/q.../GameAdded.jpg
Started the game and went to the Audio options.
http://i431.photobucket.com/albums/q...Detected-1.jpg
EAX Advanced HD detected and fully working. :cool:
Funny :) same Voltage here...Quote:
Originally Posted by Alien Grey
But i lowered (!) the voltage from 1.31v in Bios to 1.29v (1.26v real) and now iīm finally stable with tREF 16120!!
>4h Prime Custom:
http://www.abload.de/img/q96504.05ghz-1.192v_60hh35.jpg
Everest:
http://www.abload.de/img/4.05ghz-everestwewd.jpg
The funniest thing is that if I use 1.27V or 1.25V real it fails Prime95 within a few minutes and a bump of 0.01V real is enough to have it completely stable. :D
same here... the difficulty is, to find the right combination of VTT and vNB.
Here's the DD-DTS Decoder FIXQuote:
Originally Posted by SoLoR
http://rapidshare.com/files/35796840...D_DTS_FIX_.rar
By the way here you can find a LOT of information and a VERY BIG repository about Unofficial drivers for Creative soundcads...
http://www.hardwareboard.eu/threads/...FCber-die-X-Fi
Cheers!!!
:D:D:D
a ye back in the days (2 years ago) i was using that board for unoffical encoder fixes for my x-fi, but kinda forgot about it :) thanks for remind me... ill check tomorrow, after ill think about anything more then "where can i get next beer". :)Quote:
Originally Posted by Antineutrino
Some new results with my new EK Supreme HF CPU Waterblock:Quote:
Originally Posted by OLDcomer
9x500 - 14 successful passes, but the system freezed at pass No 15
http://img594.imageshack.us/img594/5...1819411.th.jpg
@OLDcomer
Looking good. :up:
@SoLoR
The SoundMAX driver 6600 crashed after 4 hours of Prime95 Blend and UT2004. :shakes:
how did it crash? and dunno i didnt have any issues personaly, maybe just some wierd random isssue... or better, blame soundmax drivers being updated once/year... i so wish i had a realtek or via, since they have drivers every month :)Quote:
Originally Posted by Alien Grey
BSOD resulting in broken SoundMAX driver. Maybe the 6600 aren't good for the Supreme FX II and I should try the 6590 again to see if they are stable.Quote:
Originally Posted by SoLoR
I thought this thread was for overclocking, not for sound drivers :p:
q9650@4500MHz(9x500) 1.45V LinX Stable
http://img99.imageshack.us/img99/557...xstable.th.jpg
It's for everything except defaults. :rofl:Quote:
Originally Posted by OLDcomer
Congrats mate with your 4.5GHz LinX stable overclock. :up:
OMG...Quote:
Originally Posted by OLDcomer
You MADE it!
:clap::clap::clap::clap:
Can you share with us your BIOS setting?
Thanks!
Cheers!
ASUS Rampage Formula BIOS 0802 9x500 Template
*Extreme Tweaker*
Ai Overclock Tuner [Manual]
CPU Ratio Setting [9]
FSB Strap to North Bridge [333Mhz]
FSB Frequency [500]
PCIE Frequency [100]
DRAM Frequency [DDR2-1202MHz]
DRAM Command Rate [2N]
DRAM CMD Skew on Channal A [Greyed Out]
DRAM CMD Skew on Channal B [Greyed Out]
DRAM CLK Skew on Channal A [Auto]
DRAM CLK Skew on Channal B [Auto]
DRAM Timing Control [Auto]
DRAM Static Read Control [Disabled]
Ai Clock Twister [Lighter]
Ai Transation Booster [Manual]
Common Performance Booster [7]
Pull-In of CHA PH1 [Disabled]
Pull-In of CHA PH2 [Disabled]
Pull-In of CHA PH3 [Disabled]
Pull-In of CHA PH4 [Disabled]
Pull-In of CHA PH5 [Disabled]
Pull-In of CHA PH6 [Disabled]
Pull-In of CHB PH1 [Disabled]
Pull-In of CHB PH2 [Disabled]
Pull-In of CHB PH3 [Disabled]
Pull-In of CHB PH4 [Disabled]
Pull-In of CHB PH5 [Disabled]
Pull-In of CHB PH6 [Disabled]
CPU Voltage [1.475] Vdrop pencil moded
CPU PLL Voltage [1.50]
North Bridge Voltage [1.73]
DRAM Voltage [1.80]
FSB Termination Voltage [1.46]
South Bridge Voltage [AUTO]
SB 1,5V Voltage [AUTO]
Loadline Calibration [Disabled]
CPU GTL Voltage Reference [AUTO]
NB GTL Voltage Reference [0.67x]
DRAM Controller Voltage REF [AUTO]
DRAM Channel A Voltage REF [AUTO]
DRAM Channel B Voltage REF [AUTO]
CPU LED Selection [CPU Voltage]
NB LED Selection [North Bridge Voltage]
SB LED Selection [South Bridge Voltage]
Voltiminder LED [DISABLED]
CPU Spread Spectrum [Disabled]
PCIE Spred Spectrum [Disabled]
CPU Clock Skew [Delay 100ps]
NB Clock Skew [Normal]
*Advanced settings*
CPU Ratio Setting [9]
C1E Support [Disabled]
CPU TM Function [Disabled]
Vanderpool Technology [Disabled]
Execute Disable Bit [Disabled]
Max CPUID Value Limit [Disabled]
Intel(R) SpeedStep (TM) Tech. [Disabled]
I've just got around to testing the 6600 drivers and i occasionally get random pops when playing music (with cmss etc all disabled), i got this with 6590 as well but not with the 6585 official drivers.
Does anyone else get this or am i the only one (btw i ccleaned and looked for the dll's SoLoR said to delete but didn't find them after uninstal)??
I've also got pops with 6610 drivers. I uninstalled 6610 and installed 6585, then pops cleared away ;)
Then I installed 6590 modded drivers which is provided by SoLoR. Now there is no problem with the sound.
I don't have pops with the 6600 drivers but what I do know is that theres a lot of stuff in the registry that can be cleaned with the TuneUp Utilities registry cleaner.
I cleaned it after removing the 6590 drivers and after the installation of the 6600 drivers. I didn't look what it was but I know that it's something in the registry that can be removed and Ccleaner doesn't do it.
And I don't use the headphone setting but leave it on 2 speakers to use a headphone because the sound with the headphone setting is horrible.
I had this with 6590 drivers, but for me 6600 are fine.Quote:
Originally Posted by leo27
I had a lot of difficulties running stable with Prime95 and UT2004 together with Windows 7 Ultimate X64.
First there was the BSOD problem with the 6600 drivers and X-Fi software. I think I fixed that with changing from AC97 to HD Audio in the BIOS and using the openal.dll from the Creative X-Fi software and not the one from UT2004.
It was a lot longer stable with changing to HD Audio but not BSOD free. If you're still using AC97 with the SoundMAX 6600 driver and the X-Fi software make the switch but remember to remove the SoundMAX driver and the X-Fi software before doing it.
Disabling the Sound Driver in UT2004 so it would use the openal.dll in the windows/system32 folder that came with the Creative X-Fi software fixed the BSOD or I didn't have it anymore but I've got more problems than that.
With the settings that I was using it failed Prime95 after a few hours on one core running Prime95 and UT2004 together. Not a big deal but it isn't good enough for me so I wanted to fix that.
I've flashed my board with the 0001 MOD BIOS from SoLoR in the hope that the updated option ROMs would fix it and I also updated the Intel Chipset Device Software to the latest official version but it still failed Prime95 after 4 hours. I've flashed it to the MOD BIOS in the hope that I could run it with the DRAM Clock Fine Delays back at 9-8-9-8 but they didn't change from 10-8-10-8 like they did in Windows XP 64 bit with lowering the NB Voltage. :(
But I did find a way to have them back at 9-8-9-8 with the 0001 MOD BIOS. Changing the CPU Clock Skew Delay from 300ps to 400ps and the NB Clock Skew Delay from 200ps to 300ps did the trick. :)
Maybe try to raise VTT a little, i think 1.10v is to low... these fine-delays are very tricky, looks like they change every reboot..
I made a succesfull run with 9x465Mhz, Memory 1240Mhz, PL6, tREF 16120 finally :)
http://www.abload.de/img/q96504.185ghz-1.256v_6egqy.jpg
http://www.abload.de/img/4.185ghz-everestwgz6.jpg
It's strange that they aren't the same in Windows 7 Ultimate 64 bit like in Windows XP 64 bit. :confused:
Changing the clock skews didn't help. It freezes after some time. :(
A-Grey
I think you may need to raise vNB and or vTT some.
And btw Are you LinX stable atm, or is it only P95+UT2004 thats failing??
I always wondered why myself and many others who were testing settings on vista x64 (Win7 x64 needs the same voltages as vista x64 btw) were needing a lot higher voltages than you, it looks like xp x64 may be the culprit.
@SoLoR
Have you had any luck implementing the DTS & DDL encoder fix that Antineutrino posted??
Nah thats what i tryed to implement before i saw that post... he just said decoder so i tought its something new :) I tryed to implement THX TruStudio software, but until soundmax makes driver (like never?) it probably impossible. THX TruStudio gives you EAX 5.0 and 128 hadrware channels.Quote:
Originally Posted by leo27
It's only Prime95 and UT2004 together that fails so I'm really close and I'm going to try it again with FSB termination Voltage 1.22V or 1.12V real.Quote:
Originally Posted by leo27
The problem is that something changes when you use Windows 7 and maybe Windows Vista. It must be a combination of BIOS and Intel Chipset Device Software. :shrug:
Is that actually possible having EAX 5.0 and 128 hardware channels with the Supreme FX II card? Isn't it also a hardware limitation?Quote:
Originally Posted by SoLoR
in that case EAX gets is processed by CPU.. so ye its possible. However atm only "offical" way of having this is using msi x-fi syren (similar to supreme-fx x-fi i guess, just "msi") or having realtek 889 (i think) hdaudio chip. However i know its possible to unlock this on all hdaudio cards, i just dont know how and the one that does know, dont want to reveal anything since he already had some problems with creative back in the days, but his "offical" stand is "until creative releases x-fi mb2 its not possible".Quote:
Originally Posted by Alien Grey
edit: btw i made "all you need" for mobo repository here, drivers all bioses, moded bioses etc etc.
6600 works ok for me , no issues with 6590 either.
Does anyone know what causes a PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 BSOD ???
cause i just had one
Memory.
thanks kuebk, i guess going from vista x64 to win7 x64 without running a memory test was infact not a good idea :D.
I think that Windows 7 Ultimate X64 and BIOS 0001 with updated option ROMs is the way to go.
With the original 0001 BIOS there's a BSOD wit error code 0x00000124 at 4 hours running Prime95 Blend. This could be to low voltage or bad driver or bad hardware in Windows 7 Ultimate X64. The 0x00000124 BSOD is probably the same as the MACHINE_CHECK_EXCEPTION BSOD in Windows XP X64.
With the 0001 BIOS with updated option ROMs it doesn't BSOD at four hours but it gives me a rounding error at 4 hours in Prime95 in Windows 7 Ultimate X64. This happens a lot faster in Ubuntu 64 bit and happens on more than one core too.
What I'm trying to do know is up the NB Voltage to 1.31V in the BIOS or 1.28V real to try to have it stable for more than 4 hours Prme95 Blend in Windows 7 Ultimate X64 with the 0001 BIOS and the updated option ROMs. If I can run it stable for more than 4 hours I'll try it again in Ubuntu 64 bit to see if it's also stable with a little higher NB voltage and the 0001 BIOS with updated option ROMs.
Guys, I have an Asus Rampage Formula mobo, I did have a X3350 quad in it, but I went and put it in my Asus P5Q-E.
The question I want to ask is, would the Asus Rampage Formula be better for clocking the X3350 quad compared to my Asus P5Q-E?
Thanks
Will.
Just an idea: try it with higher voltage for the memory. Even if the memory-test runs fine for hours, it looks like in Win7 X64 the memory needs more voltage with tREF 16120. In my case i got stability again with 0001-mod Bios, 1.14v VTT and NB 1.29v (Bios, 1.26-1.28v real), memory 1.86v instead of 1.84v.Quote:
Originally Posted by Alien Grey
The reason that I'm thinking that it's the NB Voltage is because it fails Prime95 Blend in Ubuntu 64 bit with the updated option ROMs and it doesn't do that with the original one but the original one gives me a BSOD in Windows 7 Ultimate X64.Quote:
Originally Posted by Trust13
Over 4 hours Prime95 Blend stable with Wine in Ubuntu 64 bit. :)
http://i431.photobucket.com/albums/q...ODBIOS0001.jpg
So it was vNB then??
Ubuntu is happy with vNB 1.28V and the MOD BIOS 0001. I'm going to try Windows 7 Ultimate X64 and hope I can pass the 4 hours also without problems.Quote:
Originally Posted by leo27
It looks like the updated option ROMs are going to fix the BSOD. No need to bump the vCore higher than necessary to make it go away. That was the solution to fix the MACHINE_CHECK_EXCEPTION BSOD in Windows XP X64 and it would probably be the same with the original 0001 BIOS and Windows 7 Ultimate X64 to fix the 0x00000124 BSOD.
Maybe now with the updated option ROMs it's going to be possible to use lower vCore. :shrug:
Succesfully passed the 4 hours with MOD BIOS 0001.
Forget about lower vCore. Windows 7 Ultimate X64 needs more. :D
http://i431.photobucket.com/albums/q...RD6-tREF-7.jpg
Oh you got my attention, as I am running Win7 X64 as well.
so A-Grey did any other voltages need to be raised other than vCore??
No, only the NB Voltage and CPU Voltage.Quote:
Originally Posted by leo27
I already knew that it would need a little more NB Voltage than with with the original 0001 BIOS when I saw the change in the DRAM Clock Fine Delays.
The CPU Voltage also needed a little bit more to push it over the 4 hours without making an error in Prime95.
My BIOS settings:
Code:Ai Overclock Tuner [Manual]
CPU Ratio Setting [9.0]
FSB Strap to North Bridge [400MHz]
FSB Frequency [450MHz]
PCIE Frequency [100MHz]
DRAM Frequency [1199MHz]
DRAM Command Rate [2N]
DRAM CLK Skew on Channel A/B [Auto]
DRAM Timing Control [Manual]
Refresh Period [16120]
DRAM Static Read Control [Disabled]
Ai Clock Twister [Lighter]
Ai Transaction Booster [Manual]
Common Performance Level [06]
Pull-In of CH A/B all disabled
CPU Voltage [1.31250V]
CPU PLL Voltage [1.50V]
North Bridge Voltage [1.31V]
DRAM Voltage [1.80V]
FSB Termination Voltage [1.20V]
South Bridge Voltage [1.05V]
SB 1.5V Voltage [1.50V]
Loadline Calibration [Disabled]
CPU GTL Voltage Reference [0.63X]
NB GTL Voltage Reference [0.67X]
DRAM Controller Voltage REF [Auto]
DRAM Channel A/B Voltage REF [Auto]
CPU Spread Spectrum [Disabled]
PCIE Spread Spectrum [Disabled]
CPU Clock Skew [Delay 300ps]
NB Clock Skew [Delay 200ps]
Any chance you could post your 0001 modded bios? :)
http://solor.windowsdream.com/Asus.R...mula/BIOS/MOD/Quote:
Originally Posted by Darkstormz
1002bMOD = 0001 MOD, just changed some strings to get some version consistancy and IF 0001 ever becomes offical im sure it will be in 11XX range because of new feature. So calling this 1002 does not hurt anything.
ahh thanks alot :up:Quote:
Originally Posted by SoLoR
@SoLoR
Euhmm... did you just fix the most annoying bug in the BIOS for ASUS. It's still early to call it 100% stable but I'm making progress being MemTest For Windows stable. :rofl:
http://i431.photobucket.com/albums/q...D6-tREF161.jpg
if i did something i did not do intentionaly.... i can try to break it again ;)Quote:
Originally Posted by Alien Grey
I think it's going to be possible to have it stable running at 9 X 470MHz and DDR 1253MHz with tRD 6 and tREF 16120T.
SoLoR fixed it for us without knowing it. :rofl: We really need the updated option ROMs. This is the key to have it running stable with DDR +1200MHz. If ASUS took the time to try them out they would have found this a long time a go but they didn't so they couldn't fix it for us.
An other thing that I've found thanks to Trust13 and OLDcomer is to use CPU GTL Voltage Reference 0.67X when using Ai Clock Twister Lighter. It isn't the FSB termination Voltage that let you run it stable with lower CPU Voltage it's the CPU GTL Voltage Reference. At 0.63X it was impossible to have the CPU stable at 4.23GHz and using more FSB Termination Voltage and CPU Voltage couldn't make it more stable. At 4.23GHz it likes to run with low FSB Termination Voltage and CPU GTL Voltage Reference 0.67X with lower CPU Voltage than I was expecting to have to use.
The downside is that you need more NB Voltage to run it stable with the updated option ROMs but I don't think that this is a big problem if we can run stable at higher speeds. :yepp:
The higher NB voltage is probably because the DRAM Clock Fine Delays increase with 1T with the higher NB Voltage. Maybe delaying the DRAM CLK Skew on Channel A/B is going to fix that but I didn't try it yet. It has to run stable before I can try that.
sounds like good progress, i wish we new the import of newer option roms months ago though :D
Well... im kinda moding bios since i learned how to do it more then a year ago around bios 0803. I however dont want to promote them, because i dont want to be responsible if something breaks and/or dont work... Until i break only my mobo because of bad bios flash (happened once), its ok. If i would break someone elses, then it wouldnt be that ok :) Also main issue was i never tought it could improve OC ability, because honestly it doesnt do anything for me... im "locked" on 8x451mhz (3608) and cant get even mhz more 100% stable (stoped trying last summer and just accepted this fact), why... beats me, but i guess its just bad cpu.Quote:
Originally Posted by leo27
There's definitely progress. It's like a thought you've got to delay the DRAM CLK Skew on Channel A/B to lower the NB Voltage and stabilize the board at these speeds. :up:
SoLoR do not know if previous 6590 or original 6685 had the same problem:Quote:
Originally Posted by Spyrus
When moving scroll bar of Firefox i see the CPU Usage to increase for firefox.exe.
That is ok, have seen it also on my laptop,
but i can see also some crackling noise coming from a game
that is running in background (alt+tab in firefox while playing and
immediately start scrolling).
Can you confirm this behaviour? I would try with Media player for example
and see if there occurs too, but i am at work again (all thoughts come up here :rofl: )
didnt notice anything like this... this might be dpc latency issues people randomly reports while playing sound... For example you have some sound playing (in your case game) and then you use some program that causes cpu usage spikes (using lots of interrupts) and sound starts to crackle. This sound crackling issue is (almost) always because of dpc latency spikes and cant be caused by lots of things like drivers, applications etc etc. I personaly have absolutly no issues with onboard soundcard, but its also true i dont play games much, only BC2 and WoW once in a while but didnt notice anything... Im still wating on some new drivers... slack soundmax and drivers form a year ago :< i couldnt make THX TruSound work with it yet as well, but in all honesty i gave up quickly...Quote:
Originally Posted by Spyrus
'dpc latency spikes' i googled it to investigate further. I will do some test and report back.
Edit: Used the dpc checker ... no spikes found.
I noticed, that some of you(especially Alien Grey) are using CPU/NB Skews with 100ps difference, but with values like 300ps/200ps. Since 100ps/none was the key reason to be able to do more than 460FSB, does higher value skews, but with 100ps difference, do any better compared to 100ps/none?
Yes but it depends on what voltage you need to keep it stable.Quote:
Originally Posted by spoof
CPU Clock Skew Delay 300ps and NB Clock Skew Delay 200ps for really low voltage. NB Voltage of 1.25V to +/-1.35V.
CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps for NB Voltage +/-1.35V to +/-1.45V.
It isn't always a voltage issue like what I'm experiencing now trying to run stable at 9 X 470MHz and DDR 1253MHz. I've tried really hard but it keeps failing Prime95 Blend. The longest I can keep it stable is an hour so now I'm going to try to find out how much lower I have to go to keep it stable.
I think I'm not going to try to run LinX for a very long time. It doesn't make sense at high CPU speed.
I'm trying to run LinX for 25 passes stable at 4.22GHz and everything is just fine but it's BSOD 0X00000124 again so I add more CPU Voltage and everything is fine but at some point it's BSOD 0X00000124 again so I add more CPU voltage and more and more... What the :banana::banana::banana::banana: is wrong. :mad:
But then I realize that if you add more voltage you have more heat so the water temperature starts to climb up and the CPU becomes unstable and needs more voltage but then the temperature starts to climb again and the CPU becomes unstable again. Whatever I do it's always BSOD 0X00000124 after some time. :confused:
So I'm thinking that running LinX for a very long time at very high CPU speed isn't a good stability check and now I'm running Prime95 Small FFT's again to check the stability of the CPU.
What do you guys think of that?
Well i always did only 15-20 passes of lynx for "quick" check and then i was runing prime for hours (15+) if it passed that i considered it stable :) Runing lynx for very long time is also probably not healthy for CPU :) for me it reaches INSANE temperatures (~85-90 so maximum of maximum that its still considered "safe").
and on another note, i updated x-fi software pack today. You dont really need to update it, since it doesnt change any functionality but it does have updated host openal and audiocp... but you might want to download it to install it on next format :) Also i still didnt have any luck with geting EAX5 to work :(
Thanks I'll try the new X-Fi pack later. I'm trying to get my Q9650 stable at 4.22GHz with DDR 1250MHz. :D
I still have no luck with this...Quote:
Originally Posted by Alien Grey
About stability test: i always use Prime95 custom with FFTīs in place. I think itīs more reliable then "only" to test Prime95 blend, because it stresses the CPU more.
I think I've got it all running stable now. I'm going to run some tests tomorrow.
If you want to run your G.SKILL F2-96000CLD-4GBPI memory at 1250MHz try with DRAM CLK Skew on Channel A/B Delay 50ps and DRAM Controller Voltage REF -10mV.
CPU PLL Voltage at 1.52V if your voltage fluctuates from 1.53V to 1.56 and CPU GTL Voltage Reference 0.65X with FSB termination Voltage 1.22V real to have your Q9650 running at 4.22GHz.
q9650@4563 (9x507) Prime95 SmallFFT 1-2 hour test for fun:
http://img257.imageshack.us/img257/1...prime95.th.jpg
I'm done with trying to get it stable at 9 X 469MHz and DDR 1250MHz. It isn't stable and I don't think it's because of the memory at DDR 1250MHz.
It wasn't a complete waste of time and I've found some interesting things.
My CPU likes the CPU GTL Voltage Reference 0.65X and I've got to use CPU PLL Voltage 1.52V int the BIOS. The longest stable MemTest86+ Test 5 was 19 passes stable before it starts to fail with DRAM CLK Skew on Channel A Delay 50ps and DRAM CLK Skew on Channel B Advance 100ps.
If you compare the original BIOS to the MOD BIOS than you know that ASUS did some work on the option ROMs and made the DRAM CLK Skew on Channel A Delay 100ps and DRAM CLK Skew on Channel B Advance 100ps the default for the original BIOS but didn't fix the stability problem. :rolleyes:
Managing option roms is not Asus job... they just intergrate what manufactures provides to them. I personaly think that option rom changing VITAL things like memory timings is a fluke (or design flaw) in the long run... option roms should have one function only, and that is to provide support and compatiblity for certain integrated hardware and not change functions that you might not want to be changed... :) But since this could be design flaw (and mobo manufacutes knows about it), this might be a reason asus is so reluctlant to update them, because they know it might effect stability. Funny thing is, all mobo manufacuters that actualy updates option roms every once in a while have award or efi bios. Dont think i ever saw mobo with AMI bios that manufacture also updates option roms... coincidence? could be... or not :<Quote:
Originally Posted by Alien Grey
Let's say that if they would like to update them it's going to be more work for them than just aading them to the BIOS. It's a bit sad that we still don't have a BIOS with the Special 133 Mode.Quote:
Originally Posted by SoLoR
I've spend a lot of hours trying to get it stable at 9 X 470-469MHz and DDR 1253-1250Mhz and I know it isn't the memory that makes it unstable. If ti was the memory you can never run MemTest86+ Test 5 stable for such a long time before it starts to fail.
This is the reason why I don't believe in ASUS products anymore. If you want something for benching than it doesn't matter that much but if you want it to run stable than... well you better look for something else. :D
I know that 4.05GHz 24/7 stable isn't bad but if you've got that stable with the lowest voltages than something is seriously wrong. :shakes:
Nice find A-Grey about the original clock skews in the unmodded bios, that'll be usefull to know when i get time to flash to the modded 0001.
And I envy you that you can run at lowest voltages while i'm stuck at 1.42 vNB for 425 fsb :shakes:
You need DDR 1133MHz to run it at FSB/DRAM 3/4 and AI Clock Twister Lighter.Quote:
Originally Posted by leo27
I tried CPU GTL Voltage Reference 0.67X and FSB termination Voltage 1.10V and it looks like I'm going to have it stable with lower CPU Voltage but I need to to test it. I think that if we could use a higher GTL than 0.67X with FSB 450MHz or lower we would be able to use less CPU Voltage to run it stable and see it fail from to low CPU Voltage like with a C1 stepping and not a BSOD.
The problem with ASUS is that you can run an E0 stepping CPU but they didn't optimize the BIOS for it. They only made it compatible and that sucks.
MOD BIOS 0001 with DRAM CLK Skew on Channel A Delay 50ps and DRAM CLK Skew on Channel B Advance 100ps.
I think the Skew is more important than what you see as DRAM Clock Fine Delays in EVEREST.
http://i431.photobucket.com/albums/q...RD6-tREF-9.jpg
No luck here too with 9x469Mhz. Last thing i tried was 9x467 (4.2Ghz), memory at 1245Mhz. With DRAM CLK Skew on Channel A/B Delay 50ps I thought i had found the right setting. Prime Large passed, but Small (8k) failed. So I raised the CPU voltage, 8/10k passed then failed on 768k. Next try with higher vNB, 8k failed again wtf....
So the best stable setting i could get is 9x465Mhz with memory at 1240Mhz. This without changing DRAM CLK Skews.
About the CPU-GTLs: it would be nice if itīs possible to change them for every Core, like itīs in the Extreme-Bios...
I'm not sure why they offer individual GTL tuning per core in the extreme and not in the formula when they use identical hardware, i guess it's just asus screwing us over yet again
I've flashed it back to the original BIOS 001 to try it again at 9 x 469MHz and I can get it MemTest86+ stable with DRAM CLK Skew on Channel A Normal and DRAM CLK Skew on Channel B Advance 50ps but it still fails 4 threads of MemTest For Windows. :(Quote:
Originally Posted by Trust13
I wish someone could successfully mod the ASUS Rampage Extreme BIOS 0002 so it could work on our ASUS Rampage Formula board.Quote:
Originally Posted by leo27
Yes please...Quote:
Originally Posted by Alien Grey
;););):D
Can anyone make a recommendation for a 8GB set of memory that will work on the Formula?
Either 4X2 or 2X4?
I know there was issues with getting 4 sticks to run.
G.Skill Pi Series are fine.
Last wednesday i woke at 03:30 from the firealarm in my house. Panicattacked i looked arround the house to see where was the fire and my nose pointed me to guess what.....:
http://img195.imageshack.us/img195/5499/dsc00263ek.jpg
http://img15.imageshack.us/img15/5225/dsc00264kq.jpg
http://img252.imageshack.us/img252/604/dsc00262qp.jpg
http://img249.imageshack.us/img249/8486/dsc00261xb.jpg
That was the end for my rampage story :):(
The good news are that im alive:D but... probably the damaged parts are "our" rampage formula ofcourse, psu (mayby) and (i hope not) my lovely 5900, everything else seems to be allright.
WTF time to move on....;)
That sucks. :shakes: I bet you never thought it would die from a burned PCIe X1 slot. That's where the fire started isn't it?
That realy sucks mate:mad:Quote:
Originally Posted by Alien Grey
Yes i think that fire started on the mobo beside pciex1 slot. The good thing is that my insurance covers me but im thinking if ishould contact with asus also because that kind of accidents are very weird and dangerous. Then again im wondering what could cause that...:confused:
Yes, you should contact them. Maybe they are going to replace it if it's still in warranty because it looks like it was the slot that caught fire because of bad contact that started to heat it up.:shrug:
Now i need some help about which mobo is best to go. It would be nice with usb3/sata3 and (very)good overclocking ability - all that on a x58 motherboard....:)
If you look in the Intel 4.5GHz LinX stable Club the Gigabyte X58A-UD7 hasn't been beaten yet by any other board. But of course you can buy an ASUS again and wait for a good overclocking BIOS. :rofl:
So, 1001 it's official on Asus Support site. Any difference since 0803 that affect CPU overclock?
No, BIOS 1001 is exactly the same as BIOS 0902. It doesn't have the Refresh Delay (tREF) as in BIOS 0001. No need to update if you don't press the button for to long. :rofl:Quote:
Originally Posted by spoof
Like I said before. Trying to have it stable at 9 X 470MHz and DDR 1199MHz with tRD 6 and tREF 16120T wasn't a complete waste of time.
I know now that the BSOD 0x00000124 has something to do with the memory on the ASUS Rampage Formula board. It doesn't allow me to lower the CPU Voltage without triggering the BSOD.
It's possible to use a little bit less CPU voltage when you use the DRAM CLK Skew on Channel A/B.
This is with DRAM CLK Skew on Channel A Delay 50ps and DRAM CLK Skew on Channel B Normal. I could lower the CPU Voltage from 1.31250 to 1.30000 in the BIOS and keep it stable but I have to use CPU GTL Voltage Reference 0.65X.
http://i431.photobucket.com/albums/q...D6-tREF-10.jpg
To have it complete stable you should try to find a NB Voltage that let you run it with a difference of 1T between Channel A and Channel B. It's possible that you don't have to delay Channel A with 50ps and Channel B normal but keep Channel A on Normal and advance Channel B with 50ps.
My BIOS settings:
Code:Ai Overclock Tuner [Manual]
CPU Ratio Setting [9.0]
FSB Strap to North Bridge [400MHz]
FSB Frequency [450MHz]
PCIE Frequency [100MHz]
DRAM Frequency [1199MHz]
DRAM Command Rate [2N]
DRAM CLK Skew on Channel A [Delay 50ps]
DRAM CLK Skew on Channel B [Normal]
DRAM Timing Control [Manual]
Refresh Period [16120]
DRAM Static Read Control [Disabled]
Ai Clock Twister [Lighter]
Ai Transaction Booster [Manual]
Common Performance Level [06]
Pull-In of CH A/B all disabled
CPU Voltage [1.30000V]
CPU PLL Voltage [1.50V]
North Bridge Voltage [1.29V]
DRAM Voltage [1.80V]
FSB Termination Voltage [1.20V]
South Bridge Voltage [1.05V]
SB 1.5V Voltage [1.50V]
Loadline Calibration [Disabled]
CPU GTL Voltage Reference [0.65X]
NB GTL Voltage Reference [0.67X]
DRAM Controller Voltage REF [Auto]
DRAM Channel A/B Voltage REF [Auto]
CPU Spread Spectrum [Disabled]
PCIE Spread Spectrum [Disabled]
CPU Clock Skew [Delay 200ps]
NB Clock Skew [Delay 100ps]
It was LinX stable with the NB Voltage at 1.27V in the BIOS but I have to use 1.29V to have a difference of 1T between Channel A and B as you can see in the EVEREST screenshot.
http://i431.photobucket.com/albums/q...D6-tREF-11.jpg
Now it's complete stable with CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps with less voltage. ;)
http://i431.photobucket.com/albums/q...mTestForWi.jpg
The question is how can I make it stable now at 9 X 470MHz and DDR 1253MHz with tRD 6 and tREF 16120T? :shrug: