Sys config:
Soyo Dragon Ultra (KT400) (about 1 week old)
Athlon 1.4 GHz
512 MB PC2100 SDRAM (2 sticks of 256)
XP Pro
WD 120 GB 7200 RPM HD (model?)
This problem has me baffled! It started with my system randomly restarting one night. So, it restarts and gets to the windows boot screen. Then it restarts again. So, upon restart I go into the BIOS to make sure everything is OK. Everything is fine so I reboot. Upon reboot I notice that the BIOS reports 384 MB RAM. Well, I have 512, how does that work? So, XP complains about some corrupt file that needs to be repaired (with recovery console). So I reboot, select “Last Known good configuration” and XP boots fine.
About 2 hours later I reboot. Upon reboot BIOS reports 512 MB RAM. Good. XP won’t boot, says something about ntfs.sys being corrupt. So I reboot and try recovery console a few more times. On some of the boots, I get very strange intermittent hard drive sounds; it almost sounds like the hard drive is spinning, then is stopped abruptly (with almost sort of a little click) and then spins back up. So, I shut down and do a cold boot. System recognizes 384 MB system ram. Go into XP boot menu, select last known good config, and here I am typing. What is going on here? At first I thought that it might be some RAM going bad, but then with the boot problems later I begin to question that result.
However, tell me if my reasoning is right (I don’t know details when it comes to memory). Perhaps the memory is in some sort of metastable state where sometimes it reports as 512, and others it reports as 384 (one of the modules reports 128 instead of 256). Well, on bootup the system loads some files into memory and then reads them from there. If the memory is metastable, then at one point in time Windows could “store” some of any given file in the “bad” part of the ram and some in the “good” part. Then when it goes back to read it, the bad part cops out again, and windows sees the file as corrupt. This would also explain why I am not getting the same file everytime I start the machine (sometimes it says ntfs.sys, and sometimes it’s a system directory, and sometimes it’s another file). Also, if I am in windows now, then the file(s) and directorie(s) aren’t corrupt, so something is fishy here.
Does anyone have any ideas about this problem? I just got this motherboard a week ago (actually I upgraded from an ECS K7S5A, because it was giving me problems), so I’m pretty sure it’s not that. I am REALLY leaning toward the ram, however.
Any ideas?
Thanks in advance;
Soyo Dragon Ultra (KT400) (about 1 week old)
Athlon 1.4 GHz
512 MB PC2100 SDRAM (2 sticks of 256)
XP Pro
WD 120 GB 7200 RPM HD (model?)
This problem has me baffled! It started with my system randomly restarting one night. So, it restarts and gets to the windows boot screen. Then it restarts again. So, upon restart I go into the BIOS to make sure everything is OK. Everything is fine so I reboot. Upon reboot I notice that the BIOS reports 384 MB RAM. Well, I have 512, how does that work? So, XP complains about some corrupt file that needs to be repaired (with recovery console). So I reboot, select “Last Known good configuration” and XP boots fine.
About 2 hours later I reboot. Upon reboot BIOS reports 512 MB RAM. Good. XP won’t boot, says something about ntfs.sys being corrupt. So I reboot and try recovery console a few more times. On some of the boots, I get very strange intermittent hard drive sounds; it almost sounds like the hard drive is spinning, then is stopped abruptly (with almost sort of a little click) and then spins back up. So, I shut down and do a cold boot. System recognizes 384 MB system ram. Go into XP boot menu, select last known good config, and here I am typing. What is going on here? At first I thought that it might be some RAM going bad, but then with the boot problems later I begin to question that result.
However, tell me if my reasoning is right (I don’t know details when it comes to memory). Perhaps the memory is in some sort of metastable state where sometimes it reports as 512, and others it reports as 384 (one of the modules reports 128 instead of 256). Well, on bootup the system loads some files into memory and then reads them from there. If the memory is metastable, then at one point in time Windows could “store” some of any given file in the “bad” part of the ram and some in the “good” part. Then when it goes back to read it, the bad part cops out again, and windows sees the file as corrupt. This would also explain why I am not getting the same file everytime I start the machine (sometimes it says ntfs.sys, and sometimes it’s a system directory, and sometimes it’s another file). Also, if I am in windows now, then the file(s) and directorie(s) aren’t corrupt, so something is fishy here.
Does anyone have any ideas about this problem? I just got this motherboard a week ago (actually I upgraded from an ECS K7S5A, because it was giving me problems), so I’m pretty sure it’s not that. I am REALLY leaning toward the ram, however.
Any ideas?
Thanks in advance;