Originally Posted by
Newms118
Ok smart guys, i have a very VERY strange problem that happened last night. i believe its RAM related because it happened after i changed my 2 Gb Crucial Ballistix Tracer 1066 DDR2 (double sided so not the revision) from 800 Mhz to 1066.
the problem started when i did the above change because the RAM is rated for that speed and i wanted to run it that level. I can notice the comp is more speedy at that speed then at 800, however its just slight. RAM is at 2.13V actual too. Windows boots up fine and reading websites and what not and i decide to make sure the system is stable at this speed, just to be sure. I load up Prime95, start blend test and my Q6600 on begins running 2 cores, the other two report an error "cannot initialise small fft, error code 1005." So i turn off the test and restart it, same thing, but different cores are working and different ones are turned off. I try again and only one core runs. I looked on the web and found that this occurred before on Orthos, so i loaded that up, ran blend, and same thing, same error, AND the motherboard starting BEEPING every 5-7 seconds, along with the LCD poster saying "RESERVED" Note that the beeping is a different tone than the initial beeps you get during start up, if that has any significance. I cant find anything on what the hell RESERVED means, and after i changed the RAM speed back to 800 i was able to run the blend tests fine with no beeping or RESERVED message
Keep in mind that i can run both small fft and large fft in prime95 just find, just not the blend. I can even run Memtest and prime95 small or large fft and let it go for 8+ hours with no errors. so what the HELL is this? im debating calling ASUS tech support because the error seems so unique.
I have my board on 0907 bios, with these settings:
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 400
FSB Strap to North Bridge : auto
PCI-E Frequency: 100
DRAM Frequency: DDR2- 800
DRAM Command Rate : auto
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : auto
Row Refresh Cycle Time : auto
Write Recovery Time : auto
Read to Precharge Time : auto
Read to Write Delay (S/D) : auto
Write to Read Delay (S) : auto
Write to Read Delay (D) : auto
Read to Read Delay (S) : auto
Read to Read Delay (D) : auto
Write to Write Delay (S) : auto
Write to Write Delay (D) : auto
DRAM Static Read Control: auto
Ai Clock Twister : auto
Transaction Booster : auto
CPU Voltage : set = 1.36 actual = 1.35
CPU PLL Voltage : auto, actual = 1.6
North Bridge Voltage : set = 1.49 actual = 1.48
DRAM Voltage : set = 2.08 actual 2.128
FSB Termination Voltage : 1.424
South Bridge Voltage : 1.056
Loadline Calibration : enabled
CPU GTL Reference : 1.072
North Bridge GTL Reference : auto
DDR2 Channel A REF Voltage : auto
DDR2 Channel B REF Voltage : auto
DDR2 Controller REF Voltage : auto
SB 1.5V Voltage : 1.504
NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting :
C1E Suppport : Disabled
CPU TM Function : Disabled
Vanderpool Technology : Disabled
Execute Disable Bit : Disabled
Max CPUID Value Limit : Disabled
USB Configuration
USB Functions: Enabled
Legacy USB Support : Disabled
i sincerely hope my board isnt screwed, but its been running fine minus the supreme commander crash during a certain skirmish level, but i believe thats more a SC/VISTA/Driver/Patch problem or something. Any suggestions would be much appreciated