Solved BSODs new Win732 on amd/nvidia chipset ck804 w fernandos drivers

[bam12]

it only crashes with 4 modules.
sorry but i though copying all the easytune screens gave what you needed from bios.
(this is sorta getting into voodoo mode for me now)

ht frequency ratio, k8 cpu clock ratio, ddr clock/timing mode settings are on auto.
cpu frequency 200
cpu/ddr clock ratio 2/1.66
ddr speed 333
cas# latency 2.5
min ras# active time 7t
ras# to cas# delay 3t
row precharge time 3t
row to row delay 2t
row cycle time 10t
row refresh cycle time 12t
read to write time 4t
write recovery time 3 bus clock
write to read delay 1 bus clock
refresh rate 166 mhz, 7.8 us
read preamble value 6 ns
async latency value 7 ns
cpu spread spectrum center spread
pcie clock 100 mhz
hammer vid control = startup
robust graphics booster auto
cpu voltage control normal
normal cpu vcore 1.400 v
chipset core pcie voltage normal
ht link voltage control normal
ddr voltage control normal

please let me know if i left anything out.

 

[writhziden]

Are you running with optimized defaults loaded or top performance settings loaded through the BIOS? Load optimized defaults, save, and exit the BIOS.

 

[bam12]

Writhziden

Sorry for delay answering your question. I have been using the 'optimized defaults'. When I tried the 'top performance' awhile back, it crashed immediately with a video card related error. Over the weekend, tried all possible stick/slot combinations and as long as there are two in, no crashes. I am convinced the two kits are not working together on this mb in W7 but cannot see why - they were the same sticks.

Note the settings have changed now (with two in) as follows:

cpu/ddr clock ratio 2/2
ddr speed 400
cas# latency 3
min ras# active time 8t
row cycle time 11t
row refresh cycle time 14t
write to read delay 2 bus clock
refresh rate 200 mhz, 7.8 us
read preamble value 5.5 ns

cpu/ddr clock ratio 2/1.66
ddr speed 333
cas# latency 2.5
min ras# active time 8t
ras# to cas# delay 3t
row precharge time 3t
row to row delay 2t
row cycle time 10t
row refresh cycle time 12t
read to write time 4t
write recovery time 3 bus clock
write to read delay 1 bus clock
refresh rate 166 mhz, 7.8 us
read preamble value 6 ns
async latency value 7 ns
cpu spread spectrum center spread
pcie clock 100 mhz
hammer vid control = startup
robust graphics booster auto
cpu voltage control normal
normal cpu vcore 1.400 v
chipset core pcie voltage normal
ht link voltage control normal
ddr voltage control normal

 

[writhziden]

It is possible the two kits were manufactured at different times. Occasionally, that causes problems.

 

[bam12]

writhziden

you mean the manufacture dates cause discrepancies in the bios readings, or reduce compatability between kits? Is it your opinion my system problems (those that still remain) are due to the 2 kits? if so i think the solution is just running 2gb unless willing to invest in new 1x4gb kit (ddr1s, may not even exist) - which i cannot do.

just picking your brain here:

do older mbs run designed for ddr1 work with ddr2. my user manual does not contemplate existance of ddr2.

is this windows 7 or the bios that doesnt like the mixed kits?

if the bios readings on some older 512mb sticks i have on hand were to match the 1gb, you think they would work together?

 

[writhziden]

I wouldn't advise using ddr2 if the motherboard does not say it will support it.

The RAM incompatibility is essentially at a hardware level. The problem with buying two "identical" kits is if one of the kits was manufactured at a different time than the other kit, it may have had a different set of circuit components used. Having two kits with varying components inside can result in conflicts due to the components not passing voltage/current the same way. Think of it as two pipes that can withstand different sets of water pressure. You would not want to have one pipe that can handle 2 kPa (0.29 psi) pass the flow to another pipe that can only handle 1 kpa (0.145 psi) because the second set of pipes would likely burst.

 

[bam12]

Writhziden

Running great thoughout the weekend including several extended FARCRY sessions; so it seems we have done all that can be done, resulting in a fully functional computer (albeit with half memory).

Before I mark this thread as solved I just want to thank you again for your excellent guidance and advice here on this fantastic website. I really could not have met the challenge without this support.

 

[writhziden]

You're very welcome. I am glad to see a solved case as the final result!