Stop 0x00000024 in NTFS.sys

CoolRunnings

Senior member
Jun 24, 2003
395
0
76
www.livewirepc.com
Ok, here's an issue that has been perplexing me for a while now. I'm going to lay out all the details so please bear with me if you can... 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!
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Send me the minidumps found in c:\windows\minidumps directory, zipped.
Send me the .cab file output when you run mpsreports (setup/perf version) from Microsoft; see .sig.
See .sig for e-mail info.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Stop 24 indicates an ntfs issue. Have you run chkdsk on the OS volume? If so, what's found? Use /f /r.

 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
All I can suggest then is opening a case with Microsoft, and they can look at it more deeply than I can. All it looks like to me is that there's a problem in the disk subsystem, and so the typical things to suggest are :

1. Eliminate filter drivers (Alcohol 120% and other similar programs, antivirus, anything traveling on the filesystem stack during reads/writes, anything in MPS Report's FILTERS textfile that isn't standard)
2. Chkdsk (as you've done)
3. Examine cabling of disk setup (but I doubt that, plus you aren't getting event 50 errors in the system event logs)
4. .....

MS will tell you the problem for $250 if you call them... no ifs, no buts, no maybe's. If they can't (and they always can....) then you don't pay.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Unless they've seen the dump, they can't really say. Have they seen it? They should get someone else to look at it as well and they can tell you what the solution is - as long as there's a dump (repeatable in this case) it should be an easy fix.

You might turn on driver verifier as well (verifier.exe).
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
If they don't know what to do, have them escalate internally to CPR, and CPR will tell you what to do to fix the problem.