X48 Rampage Formula Preview.

Quote:

---

Originally Posted by JohnZS

Glad to see you got the microcode sorted in the end.
You may find that slightly less vcore is required with the new microcode as apparently GTL improvements for QX9650 C0 was one of the fixes. I found this :)
Anyway with regards to the MSR issues I know that there are some people who believe that errors are expected.
Well I have done this test today on a DELL at work.

Both pass with flying colours.
If Dell can do this, why can't ASUS?
John

---

Because they don't want to. You should buy a new ASUS motherboard and maybe* than they are going to fix some BIOS issues for you.


* There's no guarantee that they are going to fix them and there's no guarantee that you ever going to see a BIOS with out issues.


@SoLoR

Did you build this R3 from scratch?

I mean did you also replace the Option ROM again in your last R3 build because I see a major improvement to mount my HDD in Ubuntu. With R2 it took a few seconds before the HDD was mounted.

Quote:

---

Originally Posted by Alien Grey

Did you build this R3 from scratch?

I mean did you also replace the Option ROM again in your last R3 build because I see a major improvement to mount my HDD in Ubuntu. With R2 it took a few seconds before the HDD was mounted.

---

no R3 is R2+microcodes.

Quote:

---

Originally Posted by SoLoR

no R3 is R2+microcodes.

---

I've also found another major improvement. The SMI latency dropped by 4 us with this BIOS. Going from 511 us to 507 us.:rofl:

I think that I discovered the most important fix that was ever done in the ASUS Rampage Formula BIOS history. I still can't believe it and I want someone else that also has this issue to try it out and confirm it.:yepp:

Halleluja!! Praise the Lord! Loadline Calibration is fixed with 1002B-R3.:eek:

Quote:

---

Originally Posted by Alien Grey

I think that I discovered the most important fix that was ever done in the ASUS Rampage Formula BIOS history. I still can't believe it and I want someone else that also has this issue to try it out and confirm it.:yepp:

Halleluja!! Praise the Lord! Loadline Calibration is fixed with 1002B-R3.:eek:

---

I used to have this issue, however only with certain combination of settings (and this was totaly random)... at the end i found certain combination that worked fine for my overclock... anyway i didnt pay any attention to this since then and to check it i would again need to go play with overclock settings and do testings and im not sure if im up for it... its summer and its hot, dont want to torture my computer more then its neccessery :)

Quote:

---

Originally Posted by SoLoR

I used to have this issue, however only with certain combination of settings (and this was totaly random)... at the end i found certain combination that worked fine for my overclock... anyway i didnt pay any attention to this since then and to check it i would again need to go play with overclock settings and do testings and im not sure if im up for it... its summer and its hot, dont want to torture my computer more then its neccessery :)

---

It's working but it doesn't mean that I can use it. There's still the 0x124 BSOD issue and now it's only a matter of time before one gets triggered if I enable LLC. But someone should try it out that doesn't have this 0x124 BSOD issue with his board.

Quote:

---

Originally Posted by JohnZS

BTW have you had any luck on your MSR quest Alien?
John

---

Maybe there's a way to find out if it's necessary to have the MSR Fails fixed in the BIOS. There's a utility, called Read & Write Utility, that should make it possible to fix the MSR in Windows. This utility can be downloaded here: http://jacky5488.myweb.hinet.net/

That is a great find Alien
The problem is I do not have a clue how to use the program. I can find the MSR section and display data, however I am not sure of what it means and what needs to be changed.
Perhaps now you have located the tool and posted it maybe some of the experts here and chip in some advice?

SoLoR please could you PM me details of how you are able to extract the new Option ROM as I can only seem to extract option ROMs from the DX58SO2 and fail miserably with the Z68 based BIOS :(
I think I need a new tool :(
Thanks
John

I have LLC ON all the time from early bioses. 0x124 seems not to be related to LLC at least for my case, unless this has been broken in latest bioses.
But funny thing is that lately all my 0x124 will only happen minutes after boot and not after more than 4 hours of playing.

Quote:

---

Originally Posted by JohnZS

SoLoR please could you PM me details of how you are able to extract the new Option ROM as I can only seem to extract option ROMs from the DX58SO2 and fail miserably with the Z68 based BIOS :(
I think I need a new tool :(

---

i did not try to extract any option rom from efi bioses for a while, because there is always someone that does it before me so i dont need to... but i was doing this with phoenixtool...

Quote:

---

Originally Posted by Spyrus

I have LLC ON all the time from early bioses. 0x124 seems not to be related to LLC at least for my case, unless this has been broken in latest bioses.
But funny thing is that lately all my 0x124 will only happen minutes after boot and not after more than 4 hours of playing.

---

I know that it doesn't have to do anything with LLC. The problem is that if I enable LLC I always run in to a 0x124 BSOD no matter if it's at full load or Idle. With LLC disabled I can at least have it stable running and the 0x124 BSOD onlu happens under full load with Prime95 or LinX. I also know that it isn't the CPU that is faulty. I'm almost 100% sure that it's a BIOS bug because before updating the Microcode it was almost impossible to boot in to Windows 7 with LLC enabled.

How long are these Microcodes already available?

I think long enough to say that ASUS doesn't care if you've got issues with there board.

@Spyrus

Use BIOS 1002b-R3 and try with DRAM CLK Skew on Channel A and B Delay 50ps. This seems to stop the 0x124 BSOD on my board with CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps with LLC Enabled. I need some more testing to see if it's really stable.

I now know for sure that it's the BIOS causing these BSOD and instabilities. I tried to run LinX and it didn't BSOD but Windows gave me a warning if I wanted to stop running LinX to prevent damage, data corruption. I cancelled it and gues what happened...

Nothing at all. LinX didn't stop or crash and everything stayed stable. I think that now is the time to fix those MSR fails in BIOS 0001 for us ASUS.;)

This is an older site and may not fully be applicable to newer AIM bios roms(or other bios Mnf.), but i am finding it very useful to read through the BIOS workshop guide. In general it is covering a lot of the stuff we would want to adjust in our bios for this board.

Even bits about how might be able to get around AIMBCP save corruption.

http://www.rebelshavenforum.com/sis-...ubb=forum;f=52



What version of AMIBCP/ MMtool is being used?

I have 3.47, and 3.26 respectively.

I know that there are newer versions out, ie 4.06 and beyond. Among other tools needed for version 8 BIOSes.


To outline what we all are looking to resolve:

Update Microcode cpu patch to latest revision(SoloR and Alien Gray did this)

Update Intel OptionROM to latest stable version(SoloR did this? version: 11.xx)

Adjust bit values that cause IBI Test Suit MSR failures(unresolved)

Add adjustable ODT item/values(SHOW), or at minimum edit per ROM build(unresolved)

What else?

This is what it should be.

1. Intel BIOS Implementation Test Suite MSR Fails.
2. Individual DRAM CLK Skew (A1-A2-B1-B2).
3. Adjustable MCH Read ODT (8T-9T-10T-11T-12T).
4. Adjustable DRAM Read ODT (3T-4T-5T).*
5. Adjustable DRAM Write ODT (6T-7T-8T).*

* I don't know if it's really necessary to have these available in the BIOS.

That's a good find Commander_HK47, so it looks like it could be possible to add in the options we want assuming we know the assembly code necessary to perform the function.

I find it ridiculous we have to program the BIOS ourselves to get it stable :shakes:

So who's up for learning BIOS coding??

I just wanted to thank you guys for this thread, especially Alien Grey, SoLoR, JohnZS, Neo_rtr & greg.m! I've been following this for at least the past year. Thanks to you guys I have a fast, stable, quiet machine with a respectable 24/7 overclock. I have learned an awful lot here! Thank you, guys!

Quote:

---

Originally Posted by leo27

That's a good find Commander_HK47, so it looks like it could be possible to add in the options we want assuming we know the assembly code necessary to perform the function.

I find it ridiculous we have to program the BIOS ourselves to get it stable :shakes:

So who's up for learning BIOS coding??

---

In all the time that I've been posting here in this thread, I don't think that I've ever seen someone posting from ASUS. If ASUS wants me to buy one of their boards for my next build they are going to have to do a lot better than what they are doing now. It's time that they realize that I'm not a fool and that I won't help them sell their boards by posting on the forums if it's to much asked to do something back when it's necessary.

So, is it ridiculous that we've got to fix the BIOS our selves? - No, it isn't... It's hilarious.

It's so hilarious that even the moderator from the ASUS forum thinks that maybe it's better to try your luck with an other company in the future.

Quote:

---

Originally Posted by jaytee

I just wanted to thank you guys for this thread, especially Alien Grey, SoLoR, JohnZS, Neo_rtr & greg.m! I've been following this for at least the past year. Thanks to you guys I have a fast, stable, quiet machine with a respectable 24/7 overclock. I have learned an awful lot here! Thank you, guys!

---

You're welcome.

Quote:

---

Originally Posted by leo27

That's a good find Commander_HK47, so it looks like it could be possible to add in the options we want assuming we know the assembly code necessary to perform the function.

I find it ridiculous we have to program the BIOS ourselves to get it stable :shakes:

So who's up for learning BIOS coding??

---

Well that guide mainly pertains to Award BIOSes, AIM bios are a bit different. They are a bit more complex, non modular, and less open ended.
Seems like Adding option ROMS and patching CPU micro codes is the easy/trivial stuff for AIM BIOSes when compared to everything else there after. It becomes that much more difficult as you have to recompile(first you have to decompile it...)to add new features it seems.


Here is a post that contains a link to a write up that covers AIM BIOS reverse engineering circa 2005:

http://www.rebelshavenforum.com/sis-...;f=52;t=000144

Direct link to the doc:
http://sites.google.com/site/pinczak...-engineering-1

Seems like one would need to know x86 assembly language, and Hardware codding, ect to be able to tackle these problems.


I am still looking around for more current information on this matter.
I currently have a hobby level interest in learning about this stuff and bettering my self with it :) But by no means am i a programer :(

Quote:

---

Originally Posted by Alien Grey

In all the time that I've been posting here in this thread, I don't think that I've ever seen someone posting from ASUS. If ASUS wants me to buy one of their boards for my next build they are going to have to do a lot better than what they are doing now. It's time that they realize that I'm not a fool and that I won't help them sell their boards by posting on the forums if it's to much asked to do something back when it's necessary.

So, is it ridiculous that we've got to fix the BIOS our selves? - No, it isn't... It's hilarious.

It's so hilarious that even the administrator from the ASUS forum thinks that maybe it's better to try your luck with an other company in the future.

---

I wont be buying "ASS out of US" board come socket R build time... In terms of my over all experience with it, i would say that its been ok, but for the price i payed for the first one i got at lunch Hindsight seems like i could have done better. I sure feel like we got burned in terms of Asus dragging their feet on providing updates to fix things like this, and then using product EOL as an excuses to wipe their hands all together.

There was a time when ASUS fixed BIOSes of boards that were two years out of production already. Not anymore it ssems. I bought an ASUS P5A mainboard in 1998 and ASUS provided an ACPI fix for Windows XP with a new BIOS revision in 2002. EOL was in 2000. This was somewhat unexpected by me but very welcome :clap:

Seems that company is not that dedicated to their own products anymore as they were in the past.

I think it's better to leave Loadline Calibration disabled. If I would want it to run stable with Loadline Calibration enabled it's going to need more voltage across the board to keep it stable and question is if it would still be possible to use the same clock skews. It's what I think the reason why it's so difficult to keep it stable running.

My conclusion is that Loadline Calibration disabled improves stability. Enabling Loadline Calibration results in kernel panics :eek: and it never did that with Loadline calibration Disabled at 100% load. Maybe when I've got the time to do it I'll try to find stability with Loadline Calibration to actually see the differences between enabled and disabled.

@JohnZS

Download the Intel® 64 and IA-32 Architectures Software Developer's Manual
Combined Volumes 3A and 3B: System Programming Guide, Parts 1 and 2

Look at Appendix Model-Specific Registers (MSR). Chapters B.1,B.2 and B.3. You'll find the MSR's that fail consistency and you'll also notice that at least one of them has to do with the L2 cache. This explains the 0x124 BSOD's and it also means that ASUS is responsible for the issues with the BIOS. These MSR fails should be fixed and it's ASUS job to do that.

Do you have a reference board where BITS doesn't fail on MSR tests? Then I could easily take the microcode patches out from there. As for your requests the easy way is this: http://www.rebelshavenforum.com/sis-...132;p=1#000006
Add a new menu (which is real to do) and then write an optional ROM that will set registers the same way you do with your tools (MCHbaredit analogs from what I've seen) but integrated in BIOS. So it'll apply settings after POST but before Windows. The hard way is to disassemble the main BIOS module and write what you want there. I'm not a programmer so I can't help with this one definitely.

Quote:

---

Originally Posted by Antinomy

Do you have a reference board where BITS doesn't fail on MSR tests? Then I could easily take the microcode patches out from there. As for your requests the easy way is this: http://www.rebelshavenforum.com/sis-...132;p=1#000006
Add a new menu (which is real to do) and then write an optional ROM that will set registers the same way you do with your tools (MCHbaredit analogs from what I've seen) but integrated in BIOS. So it'll apply settings after POST but before Windows. The hard way is to disassemble the main BIOS module and write what you want there. I'm not a programmer so I can't help with this one definitely.

---

Maybe the Intel DX48BT2 if it's possible to edit the BIOS file?:shrug:

Adding a new menu and apply settings before OS load should be fine.

Did you ever wonder why everything always ends up in failure? :confused:


MSR Fail 0x2a

Quote:

---

Processor Hard Power-On Configuration.
(R/W)
Enables and disables processor features; (R)
indicates current processor configuration.

---

MSR Fail 0x40

Quote:

---

Last Branch Record 0 From IP. (R/W)
One of four pairs of last branch record
registers on the last branch record stack. This
part of the stack contains pointers to the
source instruction for one of the last four
branches, exceptions, or interrupts taken by
the processor. See also:
• Last Branch Record Stack TOS at 1C9H
• Section 16.10, “Last Branch, Interrupt, and
Exception Recording (Pentium M
Processors).”

---

MSR Fail 0x118

Quote:

---

Data ECC register D[7:0]: used to write ECC and
read ECC to/from L2

---

MSR Fail 0x19e

Quote:

---

???

---

MSR Fail 0x400

Quote:

---

See Section 15.3.2.1, “IA32_MCi_CTL MSRs.”

---

Quote:

---

MACHINE-CHECK ARCHITECTURE

The IA32_MCi_CTL MSR controls error reporting for errors produced by a particular
hardware unit (or group of hardware units). Each of the 64 flags (EEj) represents a
potential error. Setting an EEj flag enables reporting of the associated error and
clearing it disables reporting of the error. The processor does not write changes to
bits that are not implemented.


NOTE

For P6 family processors, processors based on Intel Core microarchi-
tecture (excluding those on which on which CPUID reports
DisplayFamily_DisplayModel as 06H_1AH and onward): the operating
system or executive software must not modify the contents of the
IA32_MC0_CTL MSR. This MSR is internally aliased to the
EBL_CR_POWERON MSR and controls platform-specific error
handling features. System specific firmware (the BIOS) is responsible
for the appropriate initialization of the IA32_MC0_CTL MSR. P6 family
processors only allow the writing of all 1s or all 0s to the
IA32_MCi_CTL MSR.

---

Now you know why it always ends up in failure. :D

Excuse me,
I need help, few days ago with the 1002b-R1 bios my motherboard (P5E) stops rebooting. I can only start my pc from completely off and, i.e., if I restart it from windows it stays in a limbo with all lights and fans on but no signal from the video card and from hd. Same thing if I reboot from bios or linux, even from the reset button.

EDIT: Solved with a correct clear cmos: remove power cord, remove battery, clrtc swith enabled, disabled, insert battery.

By the way, could you give me some raccomended bios settings to achieve 4GHZ with an E8400 C0 and corsair ddr2 800mhz TWIN2X4096-6400C4DHX ram.
I have a p5e motherboard with the latest solor's 1002b-R3 bios.
Thank you

Quote:

---

Originally Posted by Giaki

By the way, could you give me some raccomended bios settings to achieve 4gb with an E8400 (first model), and ddr2 ram.
I have a p5e motherboard with the latest solor's 1002b-R3 bios.
Thank you

---

I don't know exactly what you mean with that. You can find lots of Overclocking Profiles in the thread. I'm using DRAM CLK Skew on Channel A and B delay 50ps with the 1002B-R3. Everything else is the same.

I use for Delay in DRAM, CPU and NB the normal since i think that when back to 0902 where no such settings, by default normal seems to me fine.
I might change them to AUTO or use delay 50/50/100/200? BTW 0902 has also blue screen 0x124 so apparently these 4 bios options are not relative (and i have not Quad)

Quote:

---

Originally Posted by Spyrus

I use for Delay in DRAM, CPU and NB the normal since i think that when back to 0902 where no such settings, by default normal seems to me fine.
I might change them to AUTO or use delay 50/50/100/200? BTW 0902 has also blue screen 0x124 so apparently these 4 bios options are not relative (and i have not Quad)

---

Look at the MSR fails and than you know who's responsible for these BSOD issues. ;)

Noob here ... with the MSR Fails ... you mean run the tool some tried here? Or read your post that said that for MSR Fail 0x400 (which i will probably found also in my PC),
bios coding is responsible so nothing we can do? Did you also said that only bios 1001 and beyond have these MSR fails or also older ? I might give a try to 0803 then ...
But users with no overclocking have blue screens?

You should run the tool to know if there are also MSR fails with a Dual. This has been done some time a go but the results weren't accurate with that version of BITS.

I'm not surprised that one of them has to do with the L2 cache and the other with the MACHINE-CHECK ARCHITECTURE. It's typical for a 0x124 and MACHINE_CHECK_EXCEPTION BSOD.

All BIOS versions have these MSR fails and all versions also have these BSOD's.

I don't know if users with BIOS defaults have these BSOD's. All I can say is that I already had to ask 2 times to RMA my CPU. The first time for my Q9450 and the second time for my Q9650. Both CPU's where replaced and I think that both CPU's have been tested. I've asked this to my retailer because I saw that they've been used before and he answered me that I didn't have to worry about that and that he knew that these where good CPU's. Both CPU's are running fine but the BSOD's continued. I also tried different memory but that doesn't help either.

I've been asking ASUS to fix these BSOD's for as long as I've got this board and that's more than 3 years a go. I've also asked them a few times to fix the Loadline Calibration. They probably laughed at me and thought that it was user error. Now it's my time to laugh with them because LLC is fixed with a Microcode update and the MSR fails are terrible. :rofl: The only reason that they probably don't want to fix them is because they're pissed that they where wrong. :shrug:

With doing that they screw us but they also screw Intel because the CPU RMA's will continue with these MSR fails. I'm starting to think to make the switch to AMD when it's time to upgrade. Why pay so much money for something that never is going to be good enough. ;)

Quote:

---

Originally Posted by Alien Grey

I don't know exactly what you mean with that. You can find lots of Overclocking Profiles in the thread. I'm using DRAM CLK Skew on Channel A and B delay 50ps with the 1002B-R3. Everything else is the same.

---

Thank you Alien Grey, I found the Overclocking Profiles in the thread and started ocking from that settings (yours last with 450x9).
Let me introduce the initial situation of my config. The last few years it was with 3,64ghz (403*9) and ram at 968 mhz with FSB Strap 333mhz (ratio 6:5). My bios voltages settings were: Cpu 1,23125, CpuPLL 1,5, FsbVTT 1,34, Ram 1,94, NB 1,31, SB 1,05 and 1,5.
Now I'd like to squeeze some more from the E8400 and Ram too. Actually I'm quite stable (still testing) with this settings: 444*9=3995MHz with fsb strap to 333 and ram to 1066mhz.
The voltages from aida64 are:
Attachment 118921

I'd like to know if 3,6 to 4ghz worth the consistent increase in the cpu voltage and if 333mhz strap is a good choice or if is better a 400mhz like I've seen in most of your overclocking profiles.

Quote:

---

Originally Posted by Giaki

I'd like to know if 3,6 to 4ghz worth the consistent increase in the cpu voltage and if 333mhz strap is a good choice or if is better a 400mhz like I've seen in most of your overclocking profiles.

---

If you use it for gaming on a 64 bit OS, it's worth to run it at 4GHz. The reason that I'm using the 400MHz strap is to run my memory at 1200MHz with tRD 6 to increase the memory bandwidth.

MSR Fail 0x118

The importance of CPU L2 cache ECC checking.


Where's the BIOS setting to enable it in our BIOS? :shrug:


I can understand that ASUS tries to squeeze as much performance as they can with BIOS defaults, but I can't understand that if they disable features in the BIOS that there isn't a BIOS setting to revert them. :shakes:

Quote:

---

Please note that the presence of this feature in the BIOS does not necessarily mean that your processor's L2 cache actually supports ECC checking. Many processors do not ship with ECC-capable L2 cache. In such cases, you can still enable this feature in the BIOS but it will have no effect.

---

Is there a list of processors that support this function to cross check if this feature is supported on our chips end?

Quote:

---

Originally Posted by Commander_HK47

Is there a list of processors that support this function to cross check if this feature is supported on our chips end?

---

The processors support the L2 cache ECC check. Here's prove that it does support it.

Quote:

---

Errata

AV17. Address Reported by Machine-Check Architecture (MCA) on Single-bit
L2 ECC Errors May be Incorrect

Problem: When correctable Single-bit ECC errors occur in the L2 cache, the address is
logged in the MCA address register (MCi_ADDR). Under some scenarios, the
address reported may be incorrect.

Implication: Software should not rely on the value reported in MCi_ADDR, for Single-bit L2
ECC errors.

Workaround: None identified.

---

Source: Intel® Core™2 Extreme Processor QX9000Δ and Intel® Core™2 Quad Processor Q9000Δ Series Datasheet Specification Update

This might interest you guys:

http://news.softpedia.com/news/Windo...s-217745.shtml

Quote:

---

KB 2493989 offers what Microsoft refers to as a microcode update for Intel processors. “This update improves the reliability of x64-based versions of Windows that uses certain Intel processors. This update fixes an issue in which the operating system might function incorrectly,” the company noted.

---

Apparently Windows 7 x64 is unstable for certain Intel processors, go figure.

Did anyone find the setting in BIOS 1002B-R3 to make your CPU fail LinX? :D

I've tried every CPU GTL and they all work stable. All issues with the BIOS seems to be resolved except the CPU Voltage 0x124 BSOD. This BSOD also happens when I enable LLC and Ubuntu fails to load because of somekind of synchronisation issue.

The 1002B-R3 link is down can someone reupload it? Thanks

My BIOS 1002-R3 - No More BSOD - Overclock Profile

Code:

---

*Extreme Tweaker*
Ai Overclock Tuner              [Manual]
OC From CPU Level Up            [Auto]
CPU Ratio Setting                [09.0]
FSB Strap to North Bridge        [400]
FSB Frequency                    [450]
PCIE Frequency                  [110]

DRAM Frequency                  [DDR2-1199MHz]
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      [Advance 50ps]
DRAM CLK Skew on Channal B      [Advance 50ps]

DRAM Timing Control              [Manual]
 1st Information
  CAS# Latency                  [5]       
  RAS# to CAS# Delay            [5]       
  RAS# PRE Time                  [5]       
  RAS# ACT Time                  [15]       
  RAS# to RAS# Delay            [3]
  REF Cycle Time                [Auto (52)]
  WRITE Recovery Time            [6]       
  READ to PRE Time              [3]
 2nd Information
  READ to WRITE Delay (S/D)      [8]
  WRITE to READ Delay (S)        [3]
  WRITE to READ Delay (D)        [5]
  READ to READ Delay (S)        [4]
  READ to READ Delay (D)        [6]
  WRITE to WRITE Delay (S)      [4]
  WRITE to WRITE Delay (D)      [6]
 3rd Information
  WRITE to PRE Delay            [14]       
  READ to PRE Delay              [5]       
  PRE to PRE Delay              [1]       
  ALL PRE to ACT Delay          [6]       
  ALL PRE to REF Delay          [6]
  Refresh Period                [16120T]

DRAM Static Read Control        [Disabled]
Ai Clock Twister                [Lighter]
Ai Transaction Booster          [06]               
Pull-in of CHA PH1                [Disabled]       
Pull-in of CHA PH2                [Disabled]       
Pull-in of CHA PH3                [Disabled]       
Pull-in of CHB PH1                [Disabled]       
Pull-in of CHB PH2                [Disabled]       
Pull-in of CHB PH3                [Disabled]       

CPU Voltage                      [1.31250v]
CPU PLL Voltage                  [1.50v]
North Bridge Voltage            [1.27v]
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      [DDR2_REF -10mv]
DRAM Channel A Voltage REF      [DDR2_REF -30mv]
DRAM Channel B Voltage REF      [DDR2_REF -30mv]

CPU LED Selection                [CPU Voltage]
NB LED Selection                [North Bridge Voltage]
SB LED Selection                [South Bridge Voltage]
Voltiminder LED                  [Enabled]

CPU Spread Spectrum              [Disabled]
PCIE Spred Spectrum              [Disabled]
Cpu Clock Skew                        [Delay 300ps]
NB Clock Skew                        [Delay 200ps]

*CPU Settings*

CPU Ratio Settings                [09.0]
C1E Support                        [Disabled]
CPU TM Function                        [Enabled]
Vanderpool Technology            [Disabled]
Execute Disabled Bit                [Enabled]
Max CPUID Value Limit            [Disabled]

---

Note: With CPU Clock Skew Delay 300ps and NB Clock Skew Delay 200ps the BSOD is gone if you use to low CPU Voltage. The DRAM Controller and Channel REF Voltages have been tested up to 1250MHz. Use the CPU GTL Voltage Reference that gives you the best stability/performance. They all seem to work stable with my Q9650.




Stress Testing


Unreal Tournament and Prime95 Blend together to stress everything. Room temperature 25° Celsius (Opt1=Coolant Temperature). Duration 3 hours.


http://i431.photobucket.com/albums/q...IOS1002-R3.jpg


Note: The Prime95 start time is wrong because I didn't change the time in the BIOS after a Clear CMOS.




LinX to stress the CPU and view it's performance. Room temperature 24° Celsius.


http://i431.photobucket.com/albums/q...BIOS1002R3.jpg


Note: The highest GFlops at 4.05GHz with 3475 MB memory that I've seen with my Q9650.




AIDA64 Cache & Memory Benchmark.


http://i431.photobucket.com/albums/q...BIOS1002R3.jpg




The BIOS has it all. Improved stability and improved CPU performance. I don't think that we're going to need individual DRAM CLK Skews anymore because if you make a 50ps difference between the channels it isn't stable anymore. Time will tell if we're still going to need MCH Read ODT. ;)

Hey A-grey, what made you use a PCIE Freq of 110??

Also what happens if you use the default DRAM Reference voltages??

Quote:

---

Originally Posted by Weebeast

The 1002B-R3 link is down can someone reupload it? Thanks

---

server is down because of irene... no power :)

Quote:

---

Originally Posted by leo27

Hey A-grey, what made you use a PCIE Freq of 110??

Also what happens if you use the default DRAM Reference voltages??

---

Because it works stable with PCIe 110MHz and I wanted to know if it could pass the stress test at that frequency.

Nothing happens if you use the default DRAM REF Voltages. It's only better at higher frequency with my memory.

Quote:

---

Originally Posted by SoLoR

server is down because of irene... no power :)

---

Thanks for the info and the bios!

@Alien Grey thanks for the temporary download link!

Gonna flash my mobo now

Alien Grey, what ram are you using? Is it the G. Skill Pi pc9600 rev. 1 sticks?

Quote:

---

Originally Posted by Commander_HK47

Alien Grey, what ram are you using? Is it the G. Skill Pi pc9600 rev. 1 sticks?

---

It's the G.SKILL F2-9600CL5D-4GBPI but I don't know what revision it is. I can't find it anywhere. Not on the box, memory or any program in Windows. They've got the grey metallic heatspreaders.

That is revision 1. I have the same set as well.
Here is what revision 2 looks like:
http://www.newegg.com/Product/Produc...82E16820231201

Quote:

---

Originally Posted by Alien Grey

My BIOS 1002-R3 - No More BSOD - Overclock Profile

Note: With CPU Clock Skew Delay 300ps and NB Clock Skew Delay 200ps the BSOD is gone if you use to low CPU Voltage. The DRAM Controller and Channel REF Voltages have been tested up to 1250MHz. Use the CPU GTL Voltage Reference that gives you the best stability/performance. They all seem to work stable with my Q9650.

The BIOS has it all. Improved stability and improved CPU performance. I don't think that we're going to need individual DRAM CLK Skews anymore because if you make a 50ps difference between the channels it isn't stable anymore. Time will tell if we're still going to need MCH Read ODT. ;)

---

What you had before in this settings? I remember i have to raise CPU Voltage in order to Disable LLC

Quote:

---

Originally Posted by Spyrus

What you had before in this settings? I remember i have to raise CPU Voltage in order to Disable LLC

---

I was using CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps with every other BIOS revision. I've tried it with CPU Clock Skew Delay 300ps and NB Clock Skew Delay 200ps but it didn't stay stable with a room temperature around 20° Celsius. Now I'm using CPU Voltage 1.3000V, like I did with BIOS 1002-R2, to have my full load voltage between 1.22V and 1.23V and it stays stable with CPU Clock Skew 300ps and NB Clock Skew Delay 200ps.

This is with LLC disabled. With LLC enabled it still gives me the 0X124 BSOD after a couple of minutes.

So, you suggest in order to overcome 0x124 to LLC Disable and use Clock Skew? Have voltage 1.325 to be 1.30 real with LLC enable.
Now, what i need to set as Voltage with LLC Disabled and Skew?

Let me first say thanks for all of the help and support I have received from this thread. I bought my board based on this thread. I tried 1002b-r3 after first having 0001 and for me there is a difference of not being able to boot with a drive attatched to my sil3132 controller. I works fine with 0001. It hangs at checking nvram with 1002-r3. Any idea if this could be fixed? I wouldn't know where to start. Thanks for any help.

Quote:

---

Originally Posted by boxer9999

Let me first say thanks for all of the help and support I have received from this thread. I bought my board based on this thread. I tried 1002b-r3 after first having 0001 and for me there is a difference of not being able to boot with a drive attatched to my sil3132 controller. I works fine with 0001. It hangs at checking nvram with 1002-r3. Any idea if this could be fixed? I wouldn't know where to start. Thanks for any help.

---

My guess new jmb or intel option rom doesnt go along with sil3132 controler. One thing is to do bios reset with removed battery (remove battery for ~10min), that would clear nvram settings. If this doesnt work nothing you can do about it, except trying to figure out exactly which option rom breaks it and which is last version of that option rom that works...

Quote:

---

Originally Posted by Spyrus

So, you suggest in order to overcome 0x124 to LLC Disable and use Clock Skew? Have voltage 1.325 to be 1.30 real with LLC enable.
Now, what i need to set as Voltage with LLC Disabled and Skew?

---

Yes, I do. Look at this article that Anandtech wrote about Loadline Calibration and power consumption.

Anyone runs any SSDs on this board and are they are working fine? Thinking about buying Crucial m4 128GB for OS+programs....

Running Intel X-25M 2nd Generation with Trim 80GB

No issues with my OCZ Vertex 3 120GB. I've tried every firmware version and I never had a BSOD or freeze with my OCZ Vertex 3 and my board. I've never used a BIOS without the updated Option ROMS with my OCZ Vertex 3 so I can't say if there aren't any issues with the SSD and board if you use an official ASUS Rampage Formula BIOS and I'm never going to try it.

Thanks for info... obviously i dont intend to use original intel option rom as well... however im not sure, i think if you have sata controler in RAID mode (as i have) you lose TRIM....

Quote:

---

Originally Posted by SoLoR

Thanks for info... obviously i dont intend to use original intel option rom as well... however im not sure, i think if you have sata controler in RAID mode (as i have) you lose TRIM....

---

I'm not sure either but I think that you only lose TRIM if you use a RAID controller card.

Hello everyone i'm currently trying to get my E7400 core 2 duo stable at 3,6ghz any suggestions for settings in bios?

Memory: Ocz blade series ddr2 8500 2x2 GB : OCZ2B10662G
Cpu cooler: Zalman CNPS-9900 MAX
Chassi Full tower 3 120mm - 2 on sides and 1 back, 1 200mm top

Following volts in picture is what i use and settings rest that you need info on is under picture.

http://imageshack.us/photo/my-images/33/foto0280l.jpg/

FSB Frequency [400MHz]
FSB Strap to North Bridge [400]
CPU Ratio Setting [9.0]
DRAM Frequency [1066MHz]
DRAM Command Rate [2N]
DRAM Static Read Control [Enabled]
Ai Clock Twister [Light]
CPU Spread Spectrum [Disabled]
PCIE Spread Spectrum [Disabled]
CPU Clock Skew [Auto]
NB Clock Skew [Auto]

C1E Support [Disabled]
CPU TM Function [Auto]
Execute Disable Bit [Disabled]
Max CPUID Value Limit [Disabled]
Intel(R) SpeedStep (TM) Tech. [Disabled]-> Not available anymore when CPU Ratio Setting is locked.

Managed to pass memtest 84+ without any problems with thoese settings but now i dont manage to come in windows it just reboots right when loading windows screen.

Without cpu gtl volt and nb gtl volt it wouldnt let me pass memtest84+ always rebooted around 21-22% now questions is are thoese cpu gtl,nb gtl volt most optimal in picture or should i change it to different values if yes then wich.

would be glad if anyone had similar setup or know wich settings i should go with and work from there lowering volt etc. And wich ones i should be focusing on.

also the new bios that you guys managed to do if it is a big improvement for me i would be glad if you could upload it ofc if its stable and safe with improvements on it.

This should be use for a 24/7 gaming setup that's why i'm gonna push it to 3,6ghz maybe 3,8 after i achieved 3,6

Alien Grey we talked in asus forums really thankfull for the help you gave me there and now i am back and i'm ready to overclock, why i'm here asking for help it doesnt seem to work out to well.

link when you helped me -> http://vip.asus.com/forum/view.aspx?...Language=en-us

Thanks in advance

OK, I'm posting here because I need a bit of hw troubleshoot before i reinstall windows.

Yesterday I replaced my gtx570 with a gts450 (brand new) and moved the 570 to the new rig. The drivers installed were the solid 270.61. In the past moving from an nvidia card to another has been absolutely smooth. But not this time. i dont seem able to install the drivers.
The only other hardware changes I did were to remove the x-fi fatality pci and put the supreme fx in the first pcie slot. After a bit of cleaning the audio drivers did install and work, but the gfx seem to have a conflict of some sort.

nvidia drivers (i'm trying only whql)- older versions up to 266.77 says that I have no compatible hardware.
MS driver from windows update installs fine, but after reboot at login screen, the monitor blanks twice and then it reverts to vga standard!
I'm thinking of some hardware conflict...
NOTHING in the event logs...

Any ideas before i reinstall windows (WITHOUT the fcking sp1)?

Try latest WHQL (280.26) and they have option "preform clean install" that should remove all traces of old drivers... otherwise format :)

Hmm i thought i replied... anyway i said that i tried all whql version of drivers, cleaned registry and all like recommended on nvidia forums but nothing. no go.
Tomorrow i reinstall windows and i put the drivers before the service pack and any update.

Should i remove the supreme fx card before?

Quote:

---

Originally Posted by RealTelstar

Hmm i thought i replied... anyway i said that i tried all whql version of drivers, cleaned registry and all like recommended on nvidia forums but nothing. no go.
Tomorrow i reinstall windows and i put the drivers before the service pack and any update.

Should i remove the supreme fx card before?

---

no need to do that... there are 2 possible issues with your inability to install drivers, OS is totally screwed up or graphic card is (doesnt matter if its new) also you might try other pcie slot...

Quote:

---

Originally Posted by SoLoR

no need to do that... there are 2 possible issues with your inability to install drivers, OS is totally screwed up or graphic card is (doesnt matter if its new) also you might try other pcie slot...

---

OS is old and messy, so I'm reinstalling today. If the card is broken (i really hope not), I have to return or rma it, a replacement should be in order, first 30 days from purchase we have complete warranty from seller, and it was a reputable shop.
Anyway if it's the card, Zotac lost a customer forever. I did plug it to the new PC to check if it wasnt DOA, and I get double trouble instead?

Other pci-e slot, why? There was the 570 in the same slot, do u think I could have ruined it when mounting the new card (it would be the first time ever to damage a pci/pci-x/pci-e slot)?
Edit: I'm not moving the raid controller from the second pci-e slot sry.

Quote:

---

Originally Posted by xcr

Hello everyone i'm currently trying to get my E7400 core 2 duo stable at 3,6ghz any suggestions for settings in bios?

Memory: Ocz blade series ddr2 8500 2x2 GB : OCZ2B10662G
Cpu cooler: Zalman CNPS-9900 MAX
Chassi Full tower 3 120mm - 2 on sides and 1 back, 1 200mm top

Following volts in picture is what i use and settings rest that you need info on is under picture.

http://imageshack.us/photo/my-images/33/foto0280l.jpg/

FSB Frequency [400MHz]
FSB Strap to North Bridge [400]
CPU Ratio Setting [9.0]
DRAM Frequency [1066MHz]
DRAM Command Rate [2N]
DRAM Static Read Control [Enabled]
Ai Clock Twister [Light]
CPU Spread Spectrum [Disabled]
PCIE Spread Spectrum [Disabled]
CPU Clock Skew [Auto]
NB Clock Skew [Auto]

C1E Support [Disabled]
CPU TM Function [Auto]
Execute Disable Bit [Disabled]
Max CPUID Value Limit [Disabled]
Intel(R) SpeedStep (TM) Tech. [Disabled]-> Not available anymore when CPU Ratio Setting is locked.

Managed to pass memtest 84+ without any problems with thoese settings but now i dont manage to come in windows it just reboots right when loading windows screen.

Without cpu gtl volt and nb gtl volt it wouldnt let me pass memtest84+ always rebooted around 21-22% now questions is are thoese cpu gtl,nb gtl volt most optimal in picture or should i change it to different values if yes then wich.

would be glad if anyone had similar setup or know wich settings i should go with and work from there lowering volt etc. And wich ones i should be focusing on.

also the new bios that you guys managed to do if it is a big improvement for me i would be glad if you could upload it ofc if its stable and safe with improvements on it.

This should be use for a 24/7 gaming setup that's why i'm gonna push it to 3,6ghz maybe 3,8 after i achieved 3,6

Alien Grey we talked in asus forums really thankfull for the help you gave me there and now i am back and i'm ready to overclock, why i'm here asking for help it doesnt seem to work out to well.

link when you helped me -> http://vip.asus.com/forum/view.aspx?...Language=en-us

Thanks in advance

---

Try with NB Voltage 1.27V. The DRAM Clock Fine Delays should change. Check it with AIDA64 or EVEREST.
CPU Clock Skew Delay 300ps and NB Clock Skew Delay 200ps. AI Clock Twister Lighter and DRAM Static Read Disabled.
I keep NB GTL Voltage Reference at 0.67X but if you say that you've got more luck with 0.63X than leave it like that.

If you still can't get it to load Windows without rebooting/BSOD, up the CPU Voltage.

Check the CPU Microcode version with AIDA64 or EVEREST. Download BIOS 1002B-R3 and flash your board with it. Look if the CPU Microcode has been updated for your CPU. If there's an update for your CPU than never bother to flash it back with an official BIOS. Before flashing it do a Clear CMOS and load Setup Defaults. After flashing also Clear CMOS and Load Setup Defaults but this time also disable the power from the PSU and remove the battery for a few minutes.

Quote:

---

Originally Posted by RealTelstar

OS is old and messy, so I'm reinstalling today.

---

Happy news: it was windows to be borked. :)

Quote:

---

Originally Posted by Alien Grey

Try with NB Voltage 1.27V. The DRAM Clock Fine Delays should change. Check it with AIDA64 or EVEREST.
CPU Clock Skew Delay 300ps and NB Clock Skew Delay 200ps. AI Clock Twister Lighter and DRAM Static Read Disabled.
I keep NB GTL Voltage Reference at 0.67X but if you say that you've got more luck with 0.63X than leave it like that.

If you still can't get it to load Windows without rebooting/BSOD, up the CPU Voltage.

Check the CPU Microcode version with AIDA64 or EVEREST. Download BIOS 1002B-R3 and flash your board with it. Look if the CPU Microcode has been updated for your CPU. If there's an update for your CPU than never bother to flash it back with an official BIOS. Before flashing it do a Clear CMOS and load Setup Defaults. After flashing also Clear CMOS and Load Setup Defaults but this time also disable the power from the PSU and remove the battery for a few minutes.

---

Thanks alien i will test it out soon and post how it goes.

Edit:
ok ran memtest 86+ stable with somewhere around 2,8-2,9 cpu volt, with cpu and nb ref volts auto and rest on minimum.
Memtest windows gave me error after 100 % 1 single error, i ran 2 instances 1 at 500% and 1 at 280%.

Gonna try upper nb volt 1 stepp see how it goes.

and yes i got microcode update atleast it changed in aid64.

Quote:

---

Originally Posted by xcr

Thanks alien i will test it out soon and post how it goes.

Edit:
hmm tried the new bios with my previous settings i couldnt get screen, i putted cpu voltage to auto guess what it booted but with 3,5 voltage on 2,8ghz with new bios something is strange gonna test more.

---

Something isn't right. Did you load your old Overclock Profile?

If you did load your old Overclock profile, it won't work because the BIOS has DRAM Refresh Period added in the Extreme Tweaker menu. If you try to load an old Overclock Profile from a BIOS without DRAM Refresh Period everything is going to be screwed up.

If you didn't load an old Overclock Profile, try to flash it again with BIOS 1002B-R3.

Thanks i will try that, btw cpu microcode updated so maybe that's the reason dunno. 25 passes on linx stable so far with max temp of 61C gonna test memtest windows again soon to make sure it dont give me any errors. And i will try to reflash bios, i didnt load any old profiles, i wrote my old settings down and i putted them in bios manually that's why i feelt something where strange becouse they where 100% stable the ones i used before.

Edit 2: reflashed still same, seems it have something to do with fsb strap to northbridge at 400 and fsb freq 400 but i could use the lowest voltage on 2,8ghz with nb volt 1.27 with the other bios, seems like when you push the fsb strap to nb and fsb it forces you to go for higher volts with this new bios, tried cpu gtl ref volt, and nb ref volt same didnt want to post any ideas becouse i think now when i put a volt and it starts to boot its alot more stable then before it means like at that volt it boots at 3,6ghz i also get in windows with that volt but i dont know if that good or not up to you to decide or if you got any ideas.

testing further with new settings.

I think it's a lot better if you can get it to boot Windows at 3.6GHz with the 1002-R3 BIOS. Try with CPU Clock Skew Delay 300ps and NB Clock Skew 200ps, DRAM Clk Skew on Channel A and B Advance 50ps, Ai ClockTwister Lighter (Anything else won't give you better performance)and Perfomance Level 6.

Quote:

---

Originally Posted by Alien Grey

I think it's a lot better if you can get it to boot Windows at 3.6GHz with the 1002-R3 BIOS. Try with CPU Clock Skew Delay 300ps and NB Clock Skew 200ps, DRAM Clk Skew on Channel A and B Advance 50ps, Ai ClockTwister Lighter (Anything else won't give you better performance)and Perfomance Level 6.

---

right now i have fsb 400 strap 400 multi 9.0 , cpu volt 12875, nb volt 1.27, dram volt 1,80, performance level 6, linx stable 25 passes, memtest windows stable 228% on both without errors i just upped nb volt from 1,25 -> 1.27. Gonna test prime95 soon and let it to run for like 12 hours.

Also 1 more thing i noted pull-in of cha pha a1 and b1, i where just curious before to try to boot with them with performance level 6, but i need to up the nb to like around 1.30 to get it pass around 50% memtest86+ but then the errors started to show up this is not something i think of right now first i wanna have my cpu stable.

if you got something i could start improving to get better reads or speeds etc, great if thoese settings would be mentioned as i will post back in about 12 hours and see how it did go with prime95.

Edit: 12 hour stable prime95 blend test

edit2: btw http://vip.asus.com/forum/view.aspx?...Language=en-us

Look all the way down last post trolling?
he provide rampage extreme bios for rampage formula?

thanks in advance.

At FSB 400MHz and DDR 1066MHz there should be some room left to use a few of the Phase Pull-Ins to increase performance. I don't know if it's possible to keep that stable because at FSB 450MHz and DDR 1200MHz it doesn't seem to work. You can change the Refresh Period to 16120T or whatever value you like in the BIOS to increase bandwidth. This should be possible to keep that stable.

Quote:

---

Originally Posted by xcr

Look all the way down last post trolling?
he provide rampage extreme bios for rampage formula?

---

This reminds me of something in the past. :D

Refresh period higher number = more bandwidth or is it lower = higher bandwith?

thanks in advance :D

Quote:

---

Originally Posted by xcr

Refresh period higher number = more bandwidth or is it lower = higher bandwith?

thanks in advance :D

---

Longer timing or higher number improves bandwidth. A Refresh Period of 16120T is possible 24/7.

Enabling all or some of the Phase Pull-Ins at FSB 450MHz with DDR 1200MHz and tRD 6 doesn't work at all.

Revert back to 1001 official, 0x124 is less often with same settings. I am convinced that i have to go back to 0803, because 0902 introduced latest microcode and so 0x124 programmable errors.

I'm also selling my mobo, it has been 3,5 years now that i have it:D. I'm gonna try a other brand i think.

I wanted to ask if the rampage formula got shipped in a antistatic bag or not. I can't find the antistatic bag so i think that the mobo never had 1 when i buyed it:D

Could someone please confirm it?

Quote:

---

Originally Posted by Weebeast

I'm also selling my mobo, it has been 3,5 years now that i have it:D. I'm gonna try a other brand i think.

I wanted to ask if the rampage formula got shipped in a antistatic bag or not. I can't find the antistatic bag so i think that the mobo never had 1 when i buyed it:D

Could someone please confirm it?

---

Mine did not come with a antistatic bag

Yes was only plastic cage cover it.

Thanks guys, good that i don't need to buy 1:D

Mine is still going strong


tough boards theses !!!

@SoLoR

What's new in BIOS 1002b-R4 ?

There's a new Intel RST driver and a new Intel Chipset Software installation Utility available that fixes the issues that I had with the previous versions.

Just wanted to post to say how awesome this motheboard is. I'm still using it for 3,5 years and never failed, just had to replace battery once and lost all my settings xD

I'm changing platform soon and will try other brand, but this x48 is the bomb :).

BTW, never updated the BIOS, never had issues so didn't want to mess with that :yepp:

Quote:

---

Originally Posted by Alien Grey

@SoLoR

What's new in BIOS 1002b-R4 ?

There's a new Intel RST driver and a new Intel Chipset Software installation Utility available that fixes the issues that I had with the previous versions.

---

Hey A-Grey what version of the RST driver and Chipset Utility are you using btw?

Quote:

---

Originally Posted by leo27

Hey A-Grey what version of the RST driver and Chipset Utility are you using btw?

---

Intel RST driver 10.8.0.1003 and INF Update Utility 9.2.3.1022.

Uninstall the old Intel RST driver. Update the INF Update Utility to version 9.2.3.1022 with the -OVERALL command. Install the Intel RST driver version 10.8.0.1003.

Cheers A-Grey, what problems did they solve??

And SoLoR i take it BIOS R4 has an updated rapid storage ROM?

Quote:

---

Originally Posted by leo27

Cheers A-Grey, what problems did they solve??

And SoLoR i take it BIOS R4 has an updated rapid storage ROM?

---

SATA issue. The installation process didn't complete.

Quote:

---

Originally Posted by leo27

And SoLoR i take it BIOS R4 has an updated rapid storage ROM?

---

yes... v11.5.0.1111.

Guys, I have this kind of problem:
After installation of Solor's BIOS software 1002b-R3 and R4, my BIOS stops recognizing DVD-drive. But in Windows I see my optical drive and it works normally. Reverting back to 1002b-R2 changes situation back to normal. I shuffled between those three versions twice to be sure. Request your feedback on this one.

I've been playing around with my OC again recently, working on tweaking things with LLC off in the hopes of getting rid of the random 0x124 BSODs... Anyhow my question is this: What the heck is up with this board? I'll run LinX and everything will pass, but I can come back the next day and run it on the exact same settings and it will fail on the first or second pass, then the next day it passes again.... I'm not really sure whats going on here. I ran several passes of memtest with no errors so I don't think its related to that. I'm seeing the same issues at 3.2 GHz so I don't think its the CPU being pushed to the edges of its capability, and 400FSB should be no where near a wall - I mean, this board supposedly supports 1600FSB. RAM is 1:1 @ DDR2-800 4-4-4-12. CPU temps @ 3.6 [9x400] are 70C max in LinX, @3.2 [8x400] they are 55C so I don't think temps are causing the problems either (CPU and push/pull washermod TRUE both lapped... so I'm out pretty much out of ways to improve the cooling except gong to water... and if I could afford that, I could afford a new sandy bridge cpu/mobo/ram). Running BIOS 0902 still.

If it doesn't appear to be a CPU or RAM problem, it would have to be something mobo related, right? Any thoughts? I haven't had any crashes playing games since this latest round of tweaks, just LinX weirdness.

oh man... this thread brings back some serious memories. I remember the day that I made this thread.

Thank you all for making this thread such a wealth of information.

Guys, do you have any ideas?

Quote:

---

Originally Posted by 3lfk1ng

oh man... this thread brings back some serious memories. I remember the day that I made this thread.

Thank you all for making this thread such a wealth of information.

---

yeah this thread has been extremely helpful. I'm glad everyone has contributed to it this much.

Quote:

---

Originally Posted by SoLoR

yes... v11.5.0.1111.

---

I tried downloading your latest bios and found I did not have access? Is there someplace I could get it? Thanks for everything you have done for us.

Quote:

---

Originally Posted by MaynardX

Guys, do you have any ideas?

---

IDE or SATA DVD?

Quote:

---

Originally Posted by boxer

I tried downloading your latest bios and found I did not have access? Is there someplace I could get it? Thanks for everything you have done for us.

---

yesterday server was moving... maybe because of that... try again, i just tryed and its working for me....

Unfortunately IDE dvd-drive, it's connected to the MB via blue IDE connector. I read few posts ago you've had answered to someone that it's possible new Intel option rom doesn't support sil3132 controller. Am I correct?

Quote:

---

Originally Posted by MaynardX

Unfortunately IDE dvd-drive, it's connected to the MB via blue IDE connector. I read few posts ago you've had answered to someone that it's possible new Intel option rom doesn't support sil3132 controller. Am I correct?

---

yes its possible they are not compatible with... thing is i rarely test jmb rom, because i dont use any IDE device, i have some old IDE DVD in the closet and thats about it :)

Copy that. So I should stick to 1002-b2 rather then trying newest ones?

Little offtopic. I assume new optical drives use sata connections. If I decide to change my dvd-drive (to be able to use newest bios in pursuit of the stability), which one you suggest to head for? Right now I'm considering use a ide-sata adapter.

Quote:

---

Originally Posted by MaynardX

Copy that. So I should stick to 1002-b2 rather then trying newest ones?

Little offtopic. I assume new optical drives use sata connections. If I decide to change my dvd-drive (to be able to use newest bios in pursuit of the stability), which one you suggest to head for? Right now I'm considering use a ide-sata adapter.

---

Im not using any specific DVD drive... I have SATA optiarc DVD recorder and thats all... in all honesty even if i wouldnt have it i wouldnt miss it. That odd once/year DVD that i put in...