EXTREMELY frustrated with my new cpu...

[Kokomo]

Best guess, bad O/S.

 

[someone16]

If all those things still didn't work I would suggest you to just take it to a local computer shop for them to take a look at it. 40 bux can save alot of headaches.

 

[Skibby9]

Maybe your hard drive is the culprit... try Knoppix and see how well that runs. From what I've heard, Knoppix is a distribution of Linux that does not require/use a hard drive.

http://www.knoppix.org/

 

[Huskair]

I'm trying XP... no problems yet...I'll see what happens though...

 

[MAME]

use your brother's memory again and if it never has a problem, you know it's the ram

 

[NokiaDude]

Your motherboard is the culprit. MSI has a history of memory and compatibility.

 

[WTT0001]

As has been said, back off on the memory settings (if you have a command rate of 1 back it off to 2). Then reinstall Windows.

Oh, and if you do decide to throw it out the windows just mail it to me and i'll take it

 

[Regs]

And the hard drive in which contains the OS is on master right?

 

[hausdave]

I had an Athlon64 with a K8NNXP which would not even POST. I RMA'd and bought MSI NEO K8T and it works great. One thing you might want to check is the memory compatibility list on their website: Here

 

[chocoruacal]

Amazing...you've been given the right advice: friggin run Memtest86 off a bootable floppy or CD, and yet several posts later you haven't done it.

"Computer was fine for 2 weeks."

No, it wasn't. Since your system is thoroughly fubared:

1. Run Memtest86. Overnight w/all tests enabled.. If you get errors, try backing off the memory timings. Don't get too carried away though, if SPD isn't good enough, and you've tried two separate brands, it could very well be a bad mobo.
2. If Memtest86 passes, install Windows (2000 or XP) and do all of the updates. Do not install any 3rd party software yet. Run Prime95 for at least 12 hours.
3. If Prime95 errors, install Motherboard Monitor, turn on logging, and watch for fluctuations in voltages. If they are present, then buy a real power supply.
4. And if none of that works, send the board back.

NEVER NEVER NEVER build a new system without testing the pieces for stability...you just end up with the same problems you have now and possibly end up losing any important data.

 

[Luthien]

Replace your HD with another and install your OS on it and see what happens. Have you run tests on your HD to see if it is failing? Try another PS. Most pc builders have been through some hell with a pc at one time or another. I totally sympathize with you and I know your pain. These problems are much more painful when you cannot afford to fix. Good luck and try to be patient giving yourself up to the idea that you will solve the problems eventually even if it takes a month or two because of your income.

 

[Zinn2b]

Huskair you have not posted since you reinstalled windows please post tell us what you found I would like my Donut

 

[PaxVitae]

I?m having the same problem as Huskair.

AMD64 3Gz ? MSI K8T NEO
Corsair Value PC3200 DDR-DIMM 512MB
Seagate Barracuda 7200.7 - hard drive - 120 GB - SATA-150

I think it has to do with Windows shutting down, as it only ever happens to me if I completely power down my system, and never on a soft or hard reboot. So it might have something to do with a SATA / HD buffer not been written fully to the hard drive before the system?s power is turned off.

I?ve downloaded the new K8T NEO BIOS 1.20, which updates the SATA BIOS as well, so I?m hoping this will fix the problem. But it?s possible to recover from the above error without reinstalling your windows, so long as you backup your ?C:\winnt\system32\config\system? file to another name. This is what I?ve been doing. For me it also requires a ?chkdsk /r? to fix an error normally on the above ?system? file. I think Windows must write this every time the system is shutdown or when a new system driver was installed during the last operating session. But I?m just speculating.

I?ll let you know if the BIOS was any help.

 

[dwendel]

Doesn't anyone recognize this problem as being the same as the ABIT IS/IC memory problem? I bet, as many have already said, that lowering the memory timings will solve the problem. The Abits give identical errors and missing operating system if the memory is on fast timing, usually over 225. Putting the mem divider at 5/4 solves the issue but puts mem well below 200.

 

[PaxVitae]

Well since I've updated the BIOS to 1.20 I've had no more problems with this issue and I've done a lot of testing to try and make it happen again. I've started up and shutdown the PC close to 40 times, done software installs and driver updates to see if I could get it to cause the error. But so far its worked flawlessly, while before the update it was dieing on almost every shutdown.

- Huskair
Are you still having problems???

 

[PaxVitae]

Just to be clear all my tests where on Windows 200 Pro

 

[zodder]

Just wanted to post an FYI:

My MSI K8T NEO-FIS2R works perfectly with 2 x 512 Corsair XMS PC3200LL (part # XMS3205v1.1). I have it running at 215, very aggressively.

 

[dennisj]

Similar problem. New system with Athlon 64-bit 3200, Asus K8V motherboard, and Kingston memory (don't have specs right now).

Have re-installed Win XP maybe 5 times now. After some period of time from the install I get the following error message:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Now here's the odd part. This initially happened on my old system. I replaced *everything* except for the computer case, floppy drive, CD-RW drive and DVD-RW drive. I got the same problem. In some cases, my computer freezes within WinXP followed by the above message upon reboot; in one case WinXP shut down properly and upon restart I got the message. Each time I've re-installed WinXP, I've deleted my HD partition and reformatted. After this problem happens, my BIOS seems to behave in a flakey manner - resetting my settings and occasionally requiring multiple resets to get past the POST.

Virus?

Anyhow, I'll stress-test the memory and hard drive with a separate boot CD to see what happens. If that goes well, then I'll go with a minimum XP install and try to maintain that for several days w/o installing additional progs.

Am certainly interested in anyone's success at dealing with this issue.

Thanks,

Dennis

 

[Viper96720]

Originally posted by: dennisj
Similar problem. New system with Athlon 64-bit 3200, Asus K8V motherboard, and Kingston memory (don't have specs right now).

Have re-installed Win XP maybe 5 times now. After some period of time from the install I get the following error message:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Now here's the odd part. This initially happened on my old system. I replaced *everything* except for the computer case, floppy drive, CD-RW drive and DVD-RW drive. I got the same problem. In some cases, my computer freezes within WinXP followed by the above message upon reboot; in one case WinXP shut down properly and upon restart I got the message. Each time I've re-installed WinXP, I've deleted my HD partition and reformatted. After this problem happens, my BIOS seems to behave in a flakey manner - resetting my settings and occasionally requiring multiple resets to get past the POST.

Virus?

Anyhow, I'll stress-test the memory and hard drive with a separate boot CD to see what happens. If that goes well, then I'll go with a minimum XP install and try to maintain that for several days w/o installing additional progs.

Am certainly interested in anyone's success at dealing with this issue.

Thanks,

Dennis

Your memory timings need changing. Try setting TRCD to 3 or 4 leave everything else auto. I get that when I try setting the ram timings too fast.
Something to do with the read command being sent early and violating the TRCD. Increasing it should help.
Click A64 report at bottom

 

[sandorski]

Originally posted by: dennisj
Similar problem. New system with Athlon 64-bit 3200, Asus K8V motherboard, and Kingston memory (don't have specs right now).

Have re-installed Win XP maybe 5 times now. After some period of time from the install I get the following error message:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Now here's the odd part. This initially happened on my old system. I replaced *everything* except for the computer case, floppy drive, CD-RW drive and DVD-RW drive. I got the same problem. In some cases, my computer freezes within WinXP followed by the above message upon reboot; in one case WinXP shut down properly and upon restart I got the message. Each time I've re-installed WinXP, I've deleted my HD partition and reformatted. After this problem happens, my BIOS seems to behave in a flakey manner - resetting my settings and occasionally requiring multiple resets to get past the POST.

Virus?

Anyhow, I'll stress-test the memory and hard drive with a separate boot CD to see what happens. If that goes well, then I'll go with a minimum XP install and try to maintain that for several days w/o installing additional progs.

Am certainly interested in anyone's success at dealing with this issue.

Thanks,

Dennis

Check for a BIOS update first, try that if there is one.

Check your voltages in BIOS, it is possible that this is a weak Power Supply issue. If they seem low, try bumping up the voltage to cpu/ram/AGP or whatever is reported as low. Might want to post the voltages here so we can see them.

Definitely scan for a virus, but that might not detect anything.

If either of those don't work, try completely redoing you HD drive. Remove all partitions stripping it down to nothing, then re-partition, format ect.

 

[dennisj]

Thanks for the tips. I will try them when I get home.

BTW, have already updated the BIOS and have started my HD fresh with each re-install. My power supply is 350W.

Thanks again,

Dennis