Simviation Forums

All tests, Occt, Memtest, PI - show a stable clock. Have NO issues with any other programs.

Run FSX as I normally do and within 2 or 3 minutes of clicking fly now I get a semi freeze. Meaning sound is fine but screen freezes and blinks every 10 or 15 seconds. If I hit ESC and wait a minute or two I'll get the end flight screen and after another 2 or 3 minutes I'll be able to exit FSX and get back to the desktop where things seem normal.

In the past, this is the same actions that I get when I try a new driver and it doesn't work.

BTW 3dMark ran fine and showed 12292 with defaults.

As I write this I realize that after changing the mobo, I did not uninstall,clean and reinstall the video driver (174.74) so I will try that first. I did remove the clock on the video card and am running default now - same problem.

My vCore is 1.28675 and nb is 1.51097.

After reinstalling the driver I assume that I should kick up the vCore and try again or should I try the NB first?

Thanx,

Vic

Probably NB.. but yes, could need a touch more Vcore or both

Also, you are on DDR3 now so it may be possible a bit of SKEW or GTL may be needed. If after you try increasing Vcore and NB you get the same result we may need to look at some skew

As a matter of fact I think the Mushkin support forum shows the settings for DDR3 1800 with their product and and Rampage

Yes they do - my settings are as they have on the site including the skew. I just reinstalled the driver and will test again, then nb and vcore in that order.

Vic

so have gone up to 1.52747NB and 1.31250 vCore with no success. I may be crazy but it seems to crash faster (< 1minute) as opposed to < 2m.

Will increase both a bit more and try again.

ok - now I'm stuck

Increased NB to 1.55 - no joy

increased vCore to 1.33125

FSX loaded and froze immediately.


?

Thanx,

Vic

Now I am really confused.

Reset the BIOS to defaults - everything on Auto

Same problem screen freeze in

a new wrinkle - switched to the 178.24 drivers - now FSX just disappears to the desktop after a minute or so.

Vic

I know you dont want to hear this but changing motherboads and platforms its never wise to do a repair install


We went through this in the past. I would have thought you would have learned your lesson by now

I understand Nick but this time I didn't reinstall XP at all - it just booted fine. I uninstalled and reinstalled the Extreme drivers.

I am in agreement about the auto uninstall programs - I just keep hoping...

I guess what has me confused more is the fact that the system seems stable with everything BUT FSX.

Not sure which way to go here -

I could reset everything back to default and (ugh!) do a fresh install of XP and everything else and start again or

given that I used the BIOS settings that Mushkin posted for 450x9 - any adjustments you think I should make?
This is what I have now:

Extreme Tweaker
Ai Overclock Tuner: Manual
OC From Memory Level Up: Auto
FSB Frequency: 450
CPU Ratio Setting: 09.0
CPU Configuration

CPU Ratio Setting: 09.0
C1E Support: Disabled
CPU TM Function: Disabled
Max CPUID Value Limit: Disabled
Vanderpool Technology: Enabled
Execute Disable Bit: Enabled
Core Multi-Processing: Enabled
CPU Clock Skew: Auto
NB Clock Skew: Auto
FSB Strap to North Bridge: Auto
PCIE Frequency: 100
DRAM Frequency: 1801Mhz
DRAM Command Rate: 1N
DRAM Timing Control: Manual
1st Information: 8-8-8-24-8-82-6-3
CAS# Latency: 8
RAS# to CAS# Delay: 8
RAS# Pre Time: 8
RAS# ACT Time: 24
RAS# To RAS# Delay: 8
REF Cycle Time: 82
WRITE Recovery Time: 6
READ to Pre Time: 3
2nd Information : 9-4-5-4-6-4-6
READ to WRITE Delay (S/D): 9
WRITE to READ Delay (S): 4
WRITE to READ Delay (D): 5
READ to READ (S): 4
READ to READ (D): 6
WRITE to WRITE (S): 4
WRITE to WRITE (D): 6
3RD Information: 21-7-1-9-9
WRITE to PRE Delay: 21
READ to PRE Delay: 7
PRE to PRE Delay: 1
ALL PRE to ACT Delay: 9
ALL PRE to REF Delay: 9
DRAM Static Read Control: Enabled
DRAM Dynamic Write Control: Enabled
DRAM Skew Control

DRAM CMD Skew on Channel A: Auto
DRAM CLK Skew on DIMM A1: Auto
DRAM CLK Skew on DIMM A2: Auto
DRAM CTL Skew on DIMM A1: Auto
DRAM CTL Skew on DIMM A2: Auto
DRAM CMD Skew on Channel B: Auto
DRAM CLK Skew on DIMM B1: Auto
DRAM CLK Skew on DIMM B2: Auto
DRAM CTL Skew on DIMM B1: Auto
DRAM CTL Skew on DIMM B2: Auto
Ai Clock Twister: Lighter
Ai Transaction Booster: Manual

Common Performance Level: 07
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
EPU II Phase Control: Auto
CPU Voltage: 1.28675
Load-Line Calibration: Enabled
CPU PLL Voltage: 1.51106
FSB Termination Voltage: 1.10016
CPU GTLVerf (0): +70mV
CPU GTLVerf (1): +70mV
CPU GTLVerf (2): +70mV
CPU GTLVerf (3): +70mV
NB GTLVerf: +60mV
North Bridge Voltage: 1.51097
DRAM Voltage: 1.86881
NB DDRVref: Auto
DDR3 ChannelA Vref: +25mV
DDR3 ChannelB Vref: +25mV
South Bridge 1.5 Voltage: 1.51106
South Bridge 1.05 Voltage: 1.06039
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled

Advanced menu
North Bridge Chipset Configuration
Memory Remap Feature: Enabled
Initiate Graphic Adapter:
PEG Port Control:

ok reset the CMOS using the switch - still using 178.24 driver

did not disable anything other than what was on your list, not even any auto updaters for java, etc.

you use Eset - do you disable the auto update feature when flying? Those are my main concern.


currently flying.........


ok - flew for a little over an hour with default BIOS settings.

thinking I should just try to get to 450x9 with default memory settings and see what FSX does then. try 450x9 with only vCore set - rest at auto - memory at auto -

or is a different approach better?

Vic you are going to have to bear with me as I am dialed into something else here.. probably get a better look tat this tomorrow

Lets try this.. set the clock back up but this time run 2T instead of 1T and see what happens


In my mind going from x48 to x48 should not be a problem however I am not an Intel engineer.. but I do know that only when Windows is installed clean will the HAL be updated and replaced (Hardware Abstract Layer) or the file that coordinates Windows with the motherboard. A repair or upgrade will not update the HAL so it is possible there may be an improper HAL loaded with this now


The reason I posted for everyone to use ESET NOD32 is becasue you do not have to shut it down. If there was anything else to shut down Vic my list would have it on it

so unless you are into placebo feelings about shutting down things.. its not making any difference

No problem Nick I realize you have a full plate. I have some other things I have to get done tonight also.

Eset was the only thing I had a concern over so I'm good to go on that.

I'll setup 450x9 using 2T later on and see how it goes.

Thanx!

well, creeping up on it. Using the above settings from Mushkin except for vCore 1.31250 NB 1.52422 and 2T I was able to get 30 minutes stable on Occt. Ran FSX and put it on autopilot - flew for 40 minutes before it froze.

That's it for tonight.

Sounds like the problem may be in dram channel stability

Try the test again at 1T and then 2T.. confirm the 1T/2T change is indeed equal and result

The sticks are manufacture 2T by design so that is what they should be set to for further testing until stability is achieved

I would diable MemSet and also set the common performance leve in the BIOS to AUTO allowing the automatic value be calculated

AI Clock Twister DISABLED

So that would be the next move...

just a fwiw - kicked up the vcore from the last setting to 1.31875 and system rebooted during OCCT. Also noticed that CPUz showed the vcore as 3.208

I think I tried it with everything on auto but i was floundering around a bit last night.

1.85 - 1.95 is the listed range on the memory

have to go out for an hour but will set the test and report as soon as I return.

BTW, for the 40 minutes that I WAS able to fly - I have NEVER seen the sim look that sharp - I couldn't believe it.

V