Korean Job Discussion Forums

[Cigar_Guy]

This is a somewhat involved computer problem, so please bear with me.

I built a new desktop more than a month ago, the stats of which are:

Antec Sonata II case
Antec TruPower 2.0 450W PSU
AMD 64 Athlon 3000+
Chaintech VNF4 Ultra Motherboard
Asus Extreme N6600GT Video Card
2 512MB Dual Channel DDR400 Samsung RAM chips
Samsung HD080HJ 80GB HD (SATA, 7200 rpm)
Windows XP Professional (English)
BIOS and everything else are standard. No RAID (obviously), no overclocking, no nothing. And no, I don't have a floppy drive.

The thing worked great for about a week. I wanted to play HL2 and had suggested to me that I dl some new drivers. I did so and foolishly clicked "ok" when I got a message akin to "Warning: This software doesn't have the Window's logo of approval and could therefore set your machine on fire", thinking it would be ok since it was by nVidia. The motherboard drivers caused problems with the ethernet, and I had to delete 'em and go back to the original ones. However, I didn't think to go back to the original drivers for the video card, which may or may not have contributed to the later problem.

After getting the ethernet fixed, I went in for a few hours to play HL2. Everything was fine and then suddenly I got some strange blue screen error message that restarted the system (sorry I can't be more specific, but it restarted my system after about 0.6 seconds on the screen). The system restarted fine and I could play the game again for a few more minutes until it happened again. Unfortunately, this time I got the following error message before Windows could boot:

"Windows could not start because the following file is missing or corrupt:
\windows\sytem32\config\system

You can attempt to repair this file by starting windows setup using the orginal setup CD-rom. Selet "r" a the first sreen to start repair"

The only problem is that when I told the machine to boot using the Windows disc, the system would restart before I could tell it to repair the file. After multiple attempts, I found that by removing my second stick of RAM, the system would work fine (though, of course, with half as much RAM as I'd like). By swapping the two RAM sticks, I've confirmed that the second one is damaged in some way.

Now, here's the tricky part. The manual for my Chaintech motherboard has a fun little warning inside: "Due to CPU specifications limiation, two DDR400 memory modules inserted into DIMM1/3, three DDR400 into DIMM1/2/3, or four DDR400 into DIMM1/2/3/4 is not recommended." Now, I haven't done this. I do have two DDR400 chips, but they were in DIMM1 and 2.

As if that weren't confusing enough Chaintech's list of compatible RAM (http://www.chaintechusa.com/download/list/VNF4Ultra.pdf) lists two kinds of Samsung RAM. For some reason, Samsung PC-2700 is put on their list in red (no other type of RAM is listed this way, and there's nothing on their site so far as I can see that explains what red font means). To make this even more confusing, the sticker on my RAM sticks tells me that they are the PC-3200 variety, but the writing on the stick itself indicates that it is the PC-2700 type.

So, basically, my problem is thus. I know that I had a problem with the RAM and that I will have to replace it. However, given the fact that it could be (a) bad drivers, (b) bad placement of sticks, (c) incompatible brand/type of RAM, or just (d) a lemon stick of RAM, it seems foolish to go out and buy another stick until I know exactly what it is that I need (the wrong purchase could either cause more damage or just more money).

Anyone have any thoughts on this tremendously wordy problem?

[Wrench]

http://www.memtest.org/

Make a bootable floppy or cdrom directions are available on the website.

Go to chainteck's website and check if that motherboard is compatible with the memory.

[Cigar_Guy]

[Wrench]

[Cigar_Guy]

Nope, haven't messed with anything (other than the drivers). All the hardware configs are exactly as they were right out of the package.

[Wrench]

Well aprantley some memory has a hard time running in dual channel on nf4 boards. Do a hard Bios reset if you can, clear cmos with out the battery. Let the comp redetect everything.

Can you roll back your drivers that you installed?

[keninseoul]

sounds like a two-point problem; drivers and physically the RAM. Just happened about the same time. Doubt any connection. Might be best to replace all the RAM with RAM that is okay w Chaintech guidelines


interesting specs by Chaintech - doubt I will get their product!