PC just shuts down and then won't boot, returning a Missing /Corrupt File error

[ViperZ]

Hello All, I have a PC that just shuts down for no reason and then will not boot returning this error message:

Windows could not start because the following file is missing or corrupt.

System 32 Drivers NTFS.SYS

This happened once and I was able to recover the drives contents. I reformated and reinstalled Windows XP, along with a new motherboard (A7N8X), I let the system run over night with out a problem. I then turn the PC back over to my friend, only to have the same thing happen again with the new mobo.

I suspected the hard drive was maybe on the way out when the first error occured, however a surface scan of the disk showed nothing was wrong.

Could there be some other periferal that may be causing this conflict such as a USB device or installed software? or is it most certainly the harddrive?

Asus A7N8X (previously was a ABIT KG7-R)
AMD 1700XP
2x256Mb Crucial RAM
Gainward Ti4600
2x60Gb Quantum AS 7200 Fireball Drives
Soundblaster Audigy Platinum
Windows XP Home

Edit added: Note the PC just blacks out to shut down, no BSOD or memory dump. Even if it was power supply wouldn't the NTFS file stucture survive the sudden shut down?

 

[LiLithTecH]

You may want to try removing one of the RAM MODULES
and then testing.

 

[r0tt3n1]

Came across a similar problem recently, altho with a different file name, ntoskrnl.exe. Anyhoo, turned out it was a hard drive issue concerning Int13, the 1023 cylinder limit of the drive in question. The registry gets fragmented and boot files cant be read for some reason. Check here for info about this issue and see if it may help....

 

[ViperZ]

LiLithTecH I had read somewhere else that RAM may be suspect as well, although I'm not sure I fundimentally understand how the RAM can create this problem. It should be noted the RAM has been runnning in the KG7 system for over a year and a half wothou out any problems. What is the likely hood of it going bad all of a sudden?

r0tt3n1, thanks for the link although I found it to be a bit confusing. How is Windows XP limited to this 7.8 GB System partition size? I have my current systems OS on Logical partition size of 25Gb. I have the problem PC on a logical Partition size of 20 GB.

 

[LiLithTecH]

A bad stick of RAM is one of the quickest ways
to corrupt data on a hard drive.

It just maybe this motherboard is not as tolerant
of the ram as the other, older motherboard.

Try one stick, than the other and see what you come up with.
It could be both.

 

[ViperZ]

LiLithTecH Thanks for your help so far... I should clarify that the RAM ran fine in the old KG7 for a year and a half and then displayed the same corrupt / missing message as on the new A7N8X board. We just installed the new board for he had it sitting around waiting for a reason to install.

If it was memory would not the corrupt files be more random rather than the same file each time? Just a thought....

I may get a chance to look at it tonight. I'm going to install the OS on a different Hard Drive and see if that solves it. As well I'll see about downloading a RAM checking program.

 

[ViperZ]

Just an additional thought. This is in regards to the link r0tt3n1 provided. Could it be strongly assumed that it is Harddrive because the same file becomes corrupt in the boot partion that may have bad sectors?

 

[lobadobadingdong]

Originally posted by: ViperZ
Just an additional thought. This is in regards to the link r0tt3n1 provided. Could it be strongly assumed that it is Harddrive because the same file becomes corrupt in the boot partion that may have bad sectors?

yes check here and do a search on the codes that come up on the blue screen, it will tell what and where and how to fix whatever problems you are having. you could also simply have to add a delay in your shutdown to allow windows to finish writing cached information to your hard drive, sometimes it's just that simple.

 

[ViperZ]

I tested the RAM today with Memtest 86 and it turns out the problem was with a stick of Crucial gone bad...

Thanks for everyones help and thoughts.

Anyone know what causes RAM to go bad over time?

 

[ScrapSilicon]

Originally posted by: ViperZ
I tested the RAM today with Memtest 86 and it turns out the problem was with a stick of Crucial gone bad...

Thanks for everyones help and thoughts.

Anyone know what causes RAM to go bad over time?

it might have been the move and/or possible static discharge..any of numerous things..remembering a stick of ram is a bunch of electronics and you won't ask that question much..

 

[ViperZ]

Yeah, thanks for that