Stop 0x00000024 in NTFS.SYS

C

coolrunnings

Limp Gawd
Joined
Nov 21, 2004
Messages
511
First, I'm going to apologize for the length of this post. If you can bear with me, I'd appreciate it.

My file server has been randomly crashing with Stop codes ranging from Stop 0x00000050, Stop 0x0000008E, and most recently Stop 0x00000024. Below is the troubleshooting already performed.

Initially the hardware in the file server was as follows:

Abit KN9 Ultra
Athlon X2 3800+
2gb Corsair XMS2 DDR2 (the 5,5,5,12 stuff - running SPD settings always)
ATI Radeon x300SE 128mb PCI-E
5x Seagate 320gb SATA 3G 7200.10 drives
NEC 3550A DVD Burner
Enermax 485watt PSU
Server 2003 R2

I started randomly having problems with the system rebooting itself. It's not constant - just every few days it would reboot and the machine would boot up indicating an error but not giving a stop code. Other times it would generate a Stop 0x000000D1 or occasionally a Stop 0x00000024. Almost never would a driver be mentioned in the stop code screens.

Frustrated with the above situation, I upped the voltage to 1.9v and later 2.0v on the RAM. Same problem. Ran memtest86 and Microsoft's memory test overnight (at least 8 hours and 24+ passes) and never got an error. I've run chkdsk /r individually on each of the 5 Seagate 320gb drives and they come back fine. I've looked at the SMART data on each of the drives and it reports the same. Doing this was a bit of a pain because 4 of the drives are in an Nvidia RAID 0+1 setup and I had to break the RAID to read the SMART info and all. At this point, I ran 2 instances (one set for each core) of CPU Burn to test the processor. It never overheated or generated any errors. Next I tried updating all drivers to the latest available. No change. It would still randomly reboot. From there I replaced the power supply with an Xclio StablePower 500watt unit. That night the same problem happened. I checked the SATA cables and replaced most of them even though they didn't appear to be damaged. Same problem. At this point I wondered if the motherboard might be the issue. I replaced the motherboard and processor with an Asus P5N32-E Plus and a Intel E6300 dual core chip. I had to reinstall the OS obviously (fresh format, this time I did it on an 80gb drive). While I was at it, I upgraded from a Coolermaster Centurion case to an Antec P180. The night after the install, I started getting stop codes again but this time they've been more frequent. First I got a Stop 0x00000050 in a system file I can't remember the name of (yeah I know I should have written it down) and lately two Stop 0x00000024 errors in NTFS.sys. I ran chkdsk /r on the hard drives again without incident. I ran memtest86 over night and it passed 24 passes.

I'm frustrated as all get out at this point because I've troubleshot the machine to the best of my ability and it's still generating errors. The current hardware and configuration is as follows:

Asus P5N32-E Plus
Intel E6300
2gb Corsair XMS2 DDR2 (the 5,5,5,12 stuff - running SPD settings always)
ATI Radeon x300SE 128mb PCI-E
5x Seagate 320gb SATA 3G 7200.10 drives - 4 in a RAID 0+1 (onboard SATA controller) and an 80gb 7200.9 SATA 3G Seagate drive as the OS drive (one 320gb stand-alone).
NEC 3550A DVD Burner
XClio StablePower 500watt PSU
Antec P180B case
Server 2003 R2

Any help you guys can offer would be tremendously appreciated. Thanks for bearing with the long-winded post!
 
You aren't overclocking are you? I got similar, weird errors when my CPU was not getting enough volts to sustain its overclock; blue screens with every driver imaginable (but usually ntfs.sys).
 
I'd reinstall the OS if you can, or do a Repair Installation. Getting multiple types of Stop errors with that much hardware changed out (if I read it right, the only thing you haven't changed is memory, video card, and drives. Maybe there are some different drives for the controllers? For the video card? I think something that's seemingly unrelated here. Try disabling devices you're not using in BIOS, maybe?

Have you checked the voltages you're getting from the PSU? Do you have an UPS? That'd probably be a good investment even if it's unrelated to the current problem.
 
I tried another video card, albeit the same model but got the same results. It is on a 1000VA battery backup with nothing but the tower and monitor plugged into it. I've checked the voltages and they appear to be well within tolerance. It's bone stock, never been overclocked. This is the 3rd install of Server 2003 so I doubt a reinstall of the OS is going to do anything. I've installed onto both a 320 gig drive and an 80 gig drive with the same results but the remaining 4 drives have been in the system all along...
 
coolrunnings said:
Initially the hardware in the file server was as follows:

Abit KN9 Ultra
Athlon X2 3800+
2gb Corsair XMS2 DDR2 (the 5,5,5,12 stuff - running SPD settings always)
ATI Radeon x300SE 128mb PCI-E
5x Seagate 320gb SATA 3G 7200.10 drives
NEC 3550A DVD Burner
Enermax 485watt PSU
Server 2003 R2
Click to expand...

I've highlighted the cause of your problems. And a dual core "file" server? Why?
 
Why would a server OS be the problem? And yes, a dual core file server because it's used for more than just a file server. I also run it as a peseudo-workstation for Quickbooks and such. The only reason I've got server on it is because I want it running 24x7 and I don't want to run into the 10 user connection limit imposed by XP Pro. It's not on a domain or anything like that.
 
You must log in or register to reply here.
Back
Top