Stability problems with F3-10666CL9D-4GBRL

[cameleon33]

Hey,

Maybe you are right! I saw this setting and checked what it was meaning, but I didn't make the connection
I'll try this too and see if it solves the mystery of the B's slots frequeny

EDIT: Ok I'll first set all in the bios on correct values and see if the computer still starts
Then I'll try the Ram clock thing and see if it solves the frequency problem.
Then if everything is stable, I'll run a memtest 86+ test during the night and we'll see.

Cam'

[wevsspot]

Sounds like a plan - and my fingers are still crossed for you

Good luck.

[wevsspot]

Cam,

And if all this still fails I'd like you to try the following;

Make sure you're running the latest BIOS I think it is v.2102?

DRAM Frequency [1333Mhz]
DRAM Voltage [1.500v]

Timing RAM:
CAS Latency (CL) 9
RAS To CAS Delay (tRCD) 9
RAS Precharge (tRP) 9
RAS Active Time (tRAS) 24
Row Cycle Time (tRC) 25T
Command Rate (CR) 2
RAS To RAS Delay (tRRD) 4T
Write Recovery Time (tWR) 5T
Write To Read Delay (tWTR) 5T
Read To Precharge Delay (tRTP) 4T
Four Activate Window Delay (tFAW) 24T
Write CAS Latency (tWCL) 6T
Refresh Period (tREF) 7.8 us
DRAM Drive Strength 1.0x
DRAM Data Drive Strength 1.25x
Clock Drive Strength 1.5x
CKE Drive Strength 1.5x
Idle Cycle Limit 16

[cameleon33]

Ok, if there is a problem with previous settings, I'll try your last one.
Yes the bios version is the latest v2102.

Cam'

[cameleon33]

Hi,

Ok so when I set AI Overclock tuner on manual, there are two more settings to fill:

CPU Bus Frequency: 200
PCIE Frequency : 100

I let them on default values,
Then I can't set CPU/NB Frequency on 200. I have values from 800 to 6000MHz. I think I should set it on 3400MHz... But I let it on Auto for now.

For the NBVoltage, when I set it to 1,40V, the value is displayed in red... is it ok? I let it on Auto for now.

For DRam command rate I don't have 2N, only 2T. I let it on Auto.

With these settings, windows is starting (but only showing processor frequency at 3,39GHz instead of 3,40GHz.. probably because I should set CPU/NB frequency on 3400MHz. I'll wait for more input from you.

EDIT: Setting the DRAM clock thing on Enabled didn't solve the frequency problem on second slots.

Cam'

[cameleon33]

Ok I downloaded bluescreenviewer and there are 2 blue screens.

First one report problems with:

fltmgr.sys
ntoskrnl.exe

and the second one only with

ntoskrnl.exe

Does it help??

Cam'

[wevsspot]

Cam - responses in red.....................

Hi,

Ok so when I set AI Overclock tuner on manual, there are two more settings to fill:

CPU Bus Frequency: 200 = ok to leave as is
PCIE Frequency : 100 = ok to leave as is
I let them on default values,

Then I can't set CPU/NB Frequency on 200. I have values from 800 to 6000MHz. I think I should set it on 3400MHz... But I let it on Auto for now = input a value of 2000Mhz (missed a zero)

For the NBVoltage, when I set it to 1,40V, the value is displayed in red... is it ok? I let it on Auto for now. = it's ok to set at 1.40v which is the max for now. once we are sure you're stable we can start reducing the voltage

For DRam command rate I don't have 2N, only 2T. I let it on Auto. = 2N is the same as 2T and 2CR - please manually change it to 2T

With these settings, windows is starting (but only showing processor frequency at 3,39GHz instead of 3,40GHz.. probably because I should set CPU/NB frequency on 3400MHz. I'll wait for more input from you = don't worry about this, it is a rounding error (cpu bus frequency * cpu multiplier so 200*17=3400Mhz or 3.40Ghz)

EDIT: Setting the DRAM clock thing on Enabled didn't solve the frequency problem on second slots. = this is the weirdest thing

Cam'

Please install memory in blue slots for the remainder of testing

[wevsspot]

I forgot to address your blue screen analysis. both of those are critical .exe files required for windows to function properly.

ntoskrnl = process and memory management (among other things)

fltmgr = file system filter manager

Both of these being corrupted or missing could have been a result of the previous instability in your system.

If such is the case - once we have your settings ironed out and your rig can pass 8 hours of memtest - it would be time to reinstall windows........ sigh - I know, but it is the only way.

[cameleon33]

Ok thanks, I'll set the others settings in the BIOS.
I launched a check of my disk (Western Digital Tools) just to be sure there isn't any problem from this side.

Cam'

[wevsspot]

ok

please keep me posted

[cameleon33]

Ok, no errors found on the HDD and values are all set in the BIOS.

Windows is starting and apparently running fine.
So I'll let the settings as they are, and will run a memtest during the night. (will test for 7 to 8hours).
I'll give you the results tomorrow morning.

Just to be sure, there is no risks of overheating or anything else with those results (it seems to be "safe" settings, so I guess it's ok )

Cam'

[wevsspot]

No risk Cam. I never recommend voltages that would be high enough to damage someone else's system.

Once we have confirmed stability and get a fresh install of Windows done, we'll start backing off the NB and SB voltages and find out where we can keep them stable at the lowest voltage.

The only other voltage we might adjust after this would be the CPU/NB Voltage = [Auto]

What range of settings is available in your BIOS for that?

[cameleon33]

Hi again,

For the CPU/NB Voltage, range is from 0.8 to 1.55V
Ok, for the fresh install of windows, it'll take some time as I'll need to save some data before formating and reinstalling (I also need my computer tomorrow evening and maybe wednesday).

Cam'

[wevsspot]

Set the CPU/NB Voltage to 1.26v as a starting point

[cameleon33]

Hi,

Ok I ran a memtest for 8hours (8 passes) and no errors found.
The CPU/NB Voltage was on Auto.

What do I do next?

Cam'