Win2k Installation haulted by bluescreen STOP 0x24 ntfs.sys

  • Thread starter Thread starter Dennis
  • Start date Start date
D

Dennis

I really need to speak with someone thats done a few dozen windows
installations. I spent the evening attempting to Install Win2k over 10
times. Now its personal! I will not rest until this POS does what it's
supposed to.
I've done dozens of Windoze installations over the years and built
many computers, I've never had this much trouble. Any help is
appreciated.

History: This machine (Asus P4S800 2.6gzh P4 w/ 256m ddr400)
originally had Windows XP on it when I received it. But I quickly
discovered something was very wrong with the XP install. When I tried
to access anything related to the system (such as "Windows Update" or
add Users) I got the blue screen of death quoting STOP: 0x24 etc etc
regarding ntfs.sys. Various attempts to access deeper functions of the
OS got the same result. Also heavy LAN traffic would cause this.

So I wiped XP and did a fresh install of Win2k. I formatted the drive
nice and clean, made new ntfs partitions, etc. On install I got the
blue screen of death with the same STOP 0x24 error. On install! Before
win2k was even really loaded. Refusing to quit I reformatted with ntsc
and tried again a few more times with no love. Out of desparation I
formatted it again as FAT32 and was able to get the system booted. But
when I went to "Windows Update" again I got my old blue friend with
the same STOP 0x24 error this time referencing a fat32 driver file.

This goes on and on, I tried every trick in my book including three
seperate installs w/ format from three different Win2k disks and one
WinXP disk. It becomes very clear that this is a hardware problem not
a software problem.

Any help is appreciated. My eyes hurt from looking at the MS knowledge
base and trying different google searches. I have gone from suspecting
the CD, to suspecting bad sectors on the harddrive, to suspecting the
CPU and memory clock speed (Which I tried lowering). I am left
suspecting the stick of memory I have and the motherboard. How can I
find out? Could this be caused by a bad stick of memory?


TIA
 
(e-mail address removed) (Dennis) wrote in @posting.google.com:
I really need to speak with someone thats done a few dozen windows
installations. I spent the evening attempting to Install Win2k over 10
times. Now its personal! I will not rest until this POS does what it's
supposed to.
I've done dozens of Windoze installations over the years and built
many computers, I've never had this much trouble. Any help is
appreciated.

History: This machine (Asus P4S800 2.6gzh P4 w/ 256m ddr400)
originally had Windows XP on it when I received it. But I quickly
discovered something was very wrong with the XP install. When I tried
to access anything related to the system (such as "Windows Update" or
add Users) I got the blue screen of death quoting STOP: 0x24 etc etc
regarding ntfs.sys. Various attempts to access deeper functions of the
OS got the same result. Also heavy LAN traffic would cause this.

So I wiped XP and did a fresh install of Win2k. I formatted the drive
nice and clean, made new ntfs partitions, etc. On install I got the
blue screen of death with the same STOP 0x24 error. On install! Before
win2k was even really loaded. Refusing to quit I reformatted with ntsc
and tried again a few more times with no love. Out of desparation I
formatted it again as FAT32 and was able to get the system booted. But
when I went to "Windows Update" again I got my old blue friend with
the same STOP 0x24 error this time referencing a fat32 driver file.

This goes on and on, I tried every trick in my book including three
seperate installs w/ format from three different Win2k disks and one
WinXP disk. It becomes very clear that this is a hardware problem not
a software problem.

Any help is appreciated. My eyes hurt from looking at the MS knowledge
base and trying different google searches. I have gone from suspecting
the CD, to suspecting bad sectors on the harddrive, to suspecting the
CPU and memory clock speed (Which I tried lowering). I am left
suspecting the stick of memory I have and the motherboard. How can I
find out? Could this be caused by a bad stick of memory?


TIA
Click to expand...

As you have discovered you have a hardware problem. Yes it could be
memory but more likely it is a drive problem. Usually when it is bad
memory or a more general motherboard problem you will get a variety of
stop errors. Sometimes it is a consistent stop error but an odd one that
is normally not seen. In your case you always get a stop 0x24. So I
would suspect the drive, cable or controller. There is really not a way
to determine which without swapping hardware. Also it does not appear to
be a media problem on the drive because you are able to format it
multiple times. It could however be an electronic failure on the hard
drive. I would start by replacing the cable and/or the hard drive.

Leonard Severt

Windows 2000 Server Setup Team
 
Dennis,

A Bugcheck 0x24 indicates a problem with file system or disk. This would
lead me to believe that you have a problem with your disk controller, your
cable between controller and drive, or the hard drive themselves.

(JD)
 
Most manufacturers such as Seagate, IBM, and Western Digital have hard drive
test utilities that extensively check the functionality of the drive and
associated hardware so a good drive is not returned unnecessarily for
repair. You might download and run the utility for your drive to see what
the test utility indicates. These utilities usually run from a self-booting
diskette.
 
Back
Top