X48 Rampage Formula Preview.

[OLDcomer]

Is there any possibility to mod 802 bios so by default it would be setting the highest possible tREF (16k) instead of 3120?

+ 1

[Alien Grey]

We definitely need someone that can MOD the BIOS and add some more fun stuff to the BIOS.

[OLDcomer]

These boards have significant potential but need bios to unleash their power.

[Alien Grey]

I'm having a hard time getting it stable at 4.05GHz, DDR 1199 and tRD 6 with Prime95 and UT2004 together.

Everything runs fine, not a single sign of instability. The problem is that just before it's running for four hours it becomes totally unstable and reboots like someone is pushing the reset button.

I tried with giving it more FSB Termination Voltage but it didn't help. I tried with a little more NB Voltage but still the same. I tried with changing tREF to 4680T or changing the CPU and NB GTL Voltage Reference but it doesn't help.

I can run 100 passes of LinX stable and my memory is 1000% MemTest for Windows stable.

The only thing I didn't try is changing the PCIE Frequency. I'll give it a try with 110MHz to see if that fixes something.

The only thing that I find odd is that if I start a 3D application (UT2004) my memory frequency starts to fluctuate between 588MHz and 602MHz in MemSet.

Did anyone else have this problem when running a 3D application?

[kuebk]

A-Grey - try the highest possible tREF. About memtest I would rather prefer to use dos version instead.

[Alien Grey]

A-Grey - try the highest possible tREF. About memtest I would rather prefer to use dos version instead.

I'll try that tomorrow. Changing the PCIE Frequency didn't help.

I also use MemTest86+. I know it's stable with MemTest86+ but I did test it with MemTest for Windows to be really sure that my memory is running stable.

[kuebk]

MemTest86+ can test much more memory than memtest.

Anyway I found out that with the highest possible tREF my ram is more stable and faster - too bad that you can't set it in bios so you could test ram using memtest86+.

[leo27]

I'm curious to see if changing the tREF to max has any impact on stability as well. I was under the impression that setting the tREF to max was only used to give lower latency whilst benchmarking and not generally used in everyday use. Out of curiosity what are you using to change the tREF memset or bar_edit?

[kuebk]

Memset.

[Alien Grey]

Something is seriously wrong. I've been testing with Prime95 in custom mode to change the test times to 3 minutes and I can't run it for more than an hour.

It doesn't fail in Prime95 it just crashes. With FSB termination Voltage at 1.14V it just crashes Prime95. With higher FSB termination Voltage it crashes earlier and not just Prime95 it crashes and reboots.

I've tested my memory with tREF at 16383T and it's stable.

Now I'm going to try to run Prime95 and UT2004 together with tREF at 16383T to see if that fixes the problem.

[Alien Grey]

I think that I've found the solution for my problems.

Prime95 V25.11 64 bit is buggy and causes these crashes.

It's running fine with Prime95 V25.9 64 bit.

[kuebk]

So changing tREF gave you nothing?

[Alien Grey]

So changing tREF gave you nothing?

No, it didn't fix the problem.

[leo27]

that's odd the P95 is the problem because the stress test i ran with UT2004 was with 25.11 and it worked perfectly fine.

[Alien Grey]

that's odd the P95 is the problem because the stress test i ran with UT2004 was with 25.11 and it worked perfectly fine.

You're right Prime95 V25.09 ended up with a crash too but only later.

I'm going to try with Intel Chipset Version 9.0.0.1008. I've updated them recently to the latest version and maybe this wasn't a good idea.

[Roger_D25]

Hey Guys - I've recently switched to Vista 64-Bit from Windows XP 32-Bit and I'm having some issues when I run certain benchmarks (in particular SuperPI and Prime95 (Windows 64 v25.9 build 4). When I used to run these benchmarks in Windows XP and got an error the program itself would show an error message of some sort, (in SuperPI it would say something like "there was a rounding error" and in Prime95 it would show that one or more cores failed). Well in Vista 64-Bit I'm getting messages from the operating system saying that the program needs to close (even though there are no messages from the programs themselves)? Windows shows these errors as being "APPCRASH" and gives me the option to either "Close the Program" or "Connect To Internet for Possible Solutions To the Problem". Is this simply the way these benchmarks work in Vista 64-bit if/when there is a stability issue? In any case guys thanks very much for any and all help you can give (I have indeed searched for help on this problem both here at XS Forums and on Google with very little luck)?

[leo27]

I use vista x64 as well. Usually when there is an error P95 will say a core has failed. If your system is really unstable you could get the occassional BSOD or restart. i remember having a similar problem with P95 that you are describing and i think i fixed it be downloading a different version of P95. Try P95 x64 25.11 and see if that helps.

[Roger_D25]

Thanks Leo27 for taking the time to reply, in hindsight I should have known to try a different version first (before posting my question)! I just finished completely re-installing Vista 64-bit and I'm gonna try Prime95 25.11 and hope for the best. Thanks again!

[leo27]

no problem let us know how it goes

also A-Grey
I'm using Intel Inf 9.0.0.1011 and havn't had any problems on XP or Vista x64. In fact a device called ATK0110 ACPI Utility only showed up with this version of the intel inf. I know that this is related to an ASUS feature but the point is this is the only inf i've used that found this device.

[Alien Grey]

no problem let us know how it goes

also A-Grey
I'm using Intel Inf 9.0.0.1011 and havn't had any problems on XP or Vista x64. In fact a device called ATK0110 ACPI Utility only showed up with this version of the intel inf. I know that this is related to an ASUS feature but the point is this is the only inf i've used that found this device.

I'm currently using Intel Chipset V9.0.0.1008. I was looking for V9.0.0.1011 in a zip file but I can't find it.

-------------------

Executing the Intel Chipset Driver V9.0.0.1011 from the Command Prompt with this command -OVERALL should do the trick to update from V9.0.0.1008 to V9.0.0.1011.

[Alien Grey]

You can find the Intel Chipset Driver V9.0.0.1011 at X-drivers.com.

The funny thing is that Intel Chipset V9.0.0.1008 isn't mentioned in the X-drivers.com X48 section and it's the only version that you can download from Intel's official downloadpage.

[leo27]

It is a bit wierd that it can't be found on intel's website but 9.0.0.1011 works so i don't question it.

[SoLoR]

9.1.1.1015 are latest from station-drivers.

[Alien Grey]

Finally stable at 4.05GHz and DDR 1199 with tRD 6.

This is with Intel Chipset Version 9.0.0.1011 and tREF at 16383T.

[Armored_Kech1]

Very nice! (read with borat accent)