Jump to content
Corsair Community

Valuselect VS1GBKIT400C3


Paulr

Recommended Posts

Even though this memory isn't listed as compatible with the KT600-A motherboard are there settings I can use to make it work?

 

I am getting stops when trying to install WIN2000

 

0x0000000A (0xC0483BE8, 0x00000002, 0x00000000, 0x804411e6)

 

address 804411e6 base at 80400000, date stamp 3ad77869 ntoskrnl.exe

 

Basically what I have read so far this is do to memory issues I am using the latest bios 1.2c and have refalshed it to 1.2c with the same result and had no problems using the flash utility.

 

here are the settings I have

FSB 200

Dram freq 200

dram clock by SPD

dram timing auto by spd

latency 2.5

bank interleave 2 bank

precharge 5t

active to precharge 7t

active to cmd 5t

dram burst length 4

dram command rate 2t command

write recovery time 3t

 

I am most open to suggestions.

 

Thanks for your thoughts.

Link to comment
Share on other sites

I'd love to set the dim voltage to 2.7 but I don't know where in the Bios settings that this is controlled or set. Also above I have shown what the award bios calls the various settings for memory. Is it possible you could translate your settings for 3-3-3-8 or 3-4-4-8 into the setings below?

 

here are the settings I have

FSB 200

Dram freq 200

dram clock by SPD

dram timing auto by spd

latency 2.5 Your suggestion ____

bank interleave 2 bank _____

precharge 5t _____

active to precharge 7t ____

active to cmd 5t ____

dram burst length 4 ____

dram command rate 2t command ____

write recovery time 3t ____

 

I have run MEMTEST on the individual 512 Sticks and have not received an error no matter what settings.

 

I can run the install on WIN2000 up to a point. The install process sees the Seagate IDE/ATA drive and begins to copy the files to the harddrive. However the HDD lite is sporadically blinking instead of a steady flashing like I usually see when installing. After about 10 seconds and 3% copied I get the following error.

 

STOP: 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)

 

Unexpected_Kernel_Mode_Trap.

 

According to MS, "Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware".

 

I am at a complete loss. I don't think the memory or the MB is bad I just think the combination is not compatible. I notice you suggest to most, to increase the voltage to the memory to 2.7 instead of 2.6. If I knew where to make the change I would give that a try.

 

Thanks for your earlier quick response and as always I am open to others suggestions.

 

 

 

 

 

The suggested settings for this module would be Cass 3-3-3-8 or Cass 3-4-4-8 and I would set the Dim Voltage to 2.7 Volts and test the modules one at a time with http://www.memtest.org.
Link to comment
Share on other sites

After trying many things

 

Solved problem Reset MB jumpers for FSB to 166

 

now Bios picks up CPU as AMD 2600+ instead of just reporting the speed

 

 

 

Even though this memory isn't listed as compatible with the KT600-A motherboard are there settings I can use to make it work?

 

I am getting stops when trying to install WIN2000

 

0x0000000A (0xC0483BE8, 0x00000002, 0x00000000, 0x804411e6)

 

address 804411e6 base at 80400000, date stamp 3ad77869 ntoskrnl.exe

 

Basically what I have read so far this is do to memory issues I am using the latest bios 1.2c and have refalshed it to 1.2c with the same result and had no problems using the flash utility.

 

here are the settings I have

FSB 200

Dram freq 200

dram clock by SPD

dram timing auto by spd

latency 2.5

bank interleave 2 bank

precharge 5t

active to precharge 7t

active to cmd 5t

dram burst length 4

dram command rate 2t command

write recovery time 3t

 

I am most open to suggestions.

 

Thanks for your thoughts.

Link to comment
Share on other sites

  • Corsair Employees
If you do have a 2600+ CPU they would run at 166 MHz not 200. What CPU do you have? And with a 333 FSB CPU you would need to run the memory at DDR333 as well or it will cause a bottleneck in the chipset.
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...