Bluescreen in windows 2000

[Malladine]

Nobody is answering this is tech support, so here goes:

All the advice I can find points to reloading ntfs.sys which is mentioned in the blue screen. How can I do that if I can't get anywhere? No DOS prompt (tried booting from w2k disks) no safe mode with command prompt, no safe mode period.

Is there a fix for this?

THis is the result of a recent CPU purchase, current specs are:

Athlon XP 3000+ (the new cpu)
Radeon 9800
Fortissimo III
Gigabyte GA7VAX
1gb PC2700

System was fine, but I wanted an upgrade from 1700+ to 3000+. at first I just installed it, but it was far from stable. So, I installed the updated BIOS (F10) and changed the jumpers on the motherboard to 166 fsb (duh i know) and at first it seemed ok. Then the same crashes/reboots started occuring (within 5mins). The thing also powers up on its own sometimes.

Anyway, now i'm getting a STOP blue screen referring me to NTFS_FILE_SYSTEM and ntfs.sys

Can anyone offer assistance??

Update: just tried autoclave to wipe entirely from scratch and it reports a "killing interrupt handler" and "interrupt handler - not syncing"

Bad motherboard? Crippled HDD? Just a bad CPU? I'll try the old cpu again (although I did try that with a standard boot and got the same results.)

 

[Regs]

Powers up on its own? If it does that, then there is something seriously wrong with the motherboard. More than likely a currupted Bios.

 

[gururu]

boot up using the windows 2000/xp cd and reinstall windows over the old directory. No need to format or anything like that so you won't lose anything. you will have to reinstall programs. you can also try the repair features first, but thats not so solid.

 

[Malladine]

Originally posted by: gururu
boot up using the windows 2000/xp cd and reinstall windows over the old directory. No need to format or anything like that so you won't lose anything. you will have to reinstall programs. you can also try the repair features first, but thats not so solid.

Can't get that far, it blue screens after installing the setup files before the option menus.

 

[Regs]

Your first problem was thinking your Bios was the problem. Updating a bios would be the last thing I would do to trouble shoot instability.

I would of first checked to see if I was getting sufficant power from the PSU using a mobo monitor, then check to see what errors show up in the log of Windows Manager, then tested out the memory.


And then you should know the limitations of your KT400 chipset. It only supports 166 FSB so a 200 FSB AMD 3000 XP would not function on your motherboard.

 

[Malladine]

Originally posted by: Regs
Your first problem was thinking your Bios was the problem. Updating a bios would be the last thing I would do to trouble shoot instability.

I would of first checked to see if I was getting sufficant power from the PSU using a mobo monitor, then check to see what errors show up in the log of Windows Manager, then tested out the memory.


And then you should know the limitations of your KT400 chipset. It only supports 166 FSB so a 200 FSB AMD 3000 XP would not function on your motherboard.

This chip is the 166 3000+. Updating the bios was a wise choice it seemed to me, considering Gigabyte released a new bios specifically to support barton cpus.

 

[Regs]

Sorry. -

Can you get into your BIOS at all now?

 

[Malladine]

Yes, i can. I've actually managed to boot successfully from win2k cd too so formatting as we speak. Tons of crap lost, but oh well, I guess I should expect a complete wipe whenever I install a new part from now on.

18% and no crash yet.

I did notice the cpu running close to recommened maximum: 79c. I am using a recommended hs/fan too, with thermal grease, albeit the default kind that came pasted onto the hs (not a pad, actual grease). We'll see on that I guess.

if the cpu was not compatible or was damaged in some way surely I wouldn't be getting this far in formatting??? Same goes for the motherboard?

 

[Regs]

Im all out of guesses. It could be anything from the RAM, CPU, hard drive, and mobo.