BSOD - I think HDD error?!?!?!

jakedeez

Golden Member
Jun 21, 2005
1,100
0
0
Okay, so I am working on my cousin's laptop, a Dell Latitude 600 - I start it up, and during hte post it goes to a bsod with a stop error.

The stop error is:

0x00000024 (0x001902FE,0xF8736D4,0xF89733D0,0xF83F9F81)

ntfs.sys - Address F83F9F81 base at F83AA000, DateStapm 41107eea

Now I know assue this has something to do with the hdd/fs - since it says ntfs, but the problem is that I can't get passed this screen to work on it.

Anyone seen this before/have any ideas?

The MS Solution requires access to the desktop...

I am thinking maybe a low level format, or maybe trying to boot with a bartpe disc...

Does anyone think it may just be that the HDD died?
 

birdpup

Banned
May 7, 2005
746
0
0
There was more to that error message, something similar to IRQL_LESS_THAN_ERROR, that would be more helpful in diagnosing the problem than hexadecimal memory addresses. Please make note of the actual error code should it happen again. Then search for "support.microsoft.com <errorcode>".

The ntfs is helpful like you mentioned. The problem is probably with the hard drive drivers.

My suggestion is as follows:
  • Update drivers for each disk drive in Device Manager,
  • possibly, update your motherboard northbridge chipset drivers,
  • Test the drive with the manufacturer's diagnostic utility,
  • test your memory with memtest.

Do you have data on the drive(s) you wish to recover?

[*]Memory Tests[*]Hard Drive Manufacturer Diagnostic Utilities
 

jakedeez

Golden Member
Jun 21, 2005
1,100
0
0
The exact error message was:



*** STOP: 0x00000024 (0x001902FE,0xF8736D4,0xF89733D0,0xF83F9F81)

*** ntfs.sys - Address F83F9F81 base at F83AA000, DateStapm 41107eea

Thats all, there was nothing about irql or anything like that.

I can't do anything you suggested because I can't get into windows, it is just stuck on the bsod.
 

birdpup

Banned
May 7, 2005
746
0
0
Originally posted by: jakedeez
The exact error message was:



*** STOP: 0x00000024 (0x001902FE,0xF8736D4,0xF89733D0,0xF83F9F81)

*** ntfs.sys - Address F83F9F81 base at F83AA000, DateStapm 41107eea

Thats all, there was nothing about irql or anything like that.

I can't do anything you suggested because I can't get into windows, it is just stuck on the bsod.

In that case, test the drive with the manufacturer's diagnostic utility and then test the memory with memtest through at least one complete test cycle.

Sure, memtest sounds inappropriate for a possible drive error but until you know what the problem is, it is good to test those components you are able to.
 

jakedeez

Golden Member
Jun 21, 2005
1,100
0
0
Dude - I did google it, and I found the microsoft support answer...

I can't get into windows. It won't boot up, it stops during the post and gives me a bsod.
 

birdpup

Banned
May 7, 2005
746
0
0
Originally posted by: jakedeez
Dude - I did google it, and I found the microsoft support answer...
I am not hassling you and I apologize if it seems that way. I had no idea you had found the page and merely provided it, with the method I used to find it. Other people may provide problems, I do not. My answers may be short but in face to face interaction my short verbal responses are provided with a reasonable tone of voice and friendly body gestures. These are difficult for me to apply to words. :)

Originally posted by: jakedeez
I can't get into windows. It won't boot up, it stops during the post and gives me a bsod.

You are on a computer now with internet access. I advise following the link provided above for your hard drive manufacturer's diagnostic utility, downloading it, copying it to a floppy drive, then keeping the floppy in the drive as you reboot the machine. Then perform a test on the drive with the manufacturer's diagnostic utility. An error will either occur or not and it may help toward diagnosing the problem.

Another thing to check is whether or not the drive is physically connected to the motherboard properly. Maybe the IDE/SATA cable is lose. Maybe a jumper is mispositioned.

First thing to do is to check the physical components. If those are good, then we move on to software configuration, operating system recovery, or data recovery.
 

birdpup

Banned
May 7, 2005
746
0
0
Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
At the bottom of the page,
If none of these methods work, you may have to delete, re-create, and format the corrupted NTFS partition, and restore the partition from your last good backup of the volume.

This provides a good idea of how to procede with operating system recovery. But let's first discover if the hardware is working the way it should. Test the hard drive and then memory.

How is your power supply?
What brand and wattage is your psu?
How old is the wiring in your house?
Do you have a UPS battery backup with undervoltage (brownout) protection?
 

jakedeez

Golden Member
Jun 21, 2005
1,100
0
0
I appologize if I sounded harsh. I know your only trying to help, I just get annoyed with people who come to the fourm when they could try and find the answer themselves - this is why I sounded defensive, I did do quite a bit of searching the internet for the answer.

Its a laptop - Dell Latitude 600
 

birdpup

Banned
May 7, 2005
746
0
0
Then the power supply questions and need for a separate PSU are not useful. The laptop battery should filter the supplied power.
This also eliminates the possibility of a loose cable connection or mispositioned jumper.

Please let me/us know the result of the test with the manufacturer's diagnostic utility.

After that, please test the memory with memtest.
Seriously. Memory failures often cause weird problems that are difficult to pinpoint. This is why it is good to test the memory, just in case. An easy test now can save hours of frustration later.
 

jakedeez

Golden Member
Jun 21, 2005
1,100
0
0
Which HDD diagnostic would you suggest, the hdd is listed as: HARD DRIVE, 40GB, I, 9.5MM, 5.4K, HIT-EUCL

Think that means Hitachi?
 

birdpup

Banned
May 7, 2005
746
0
0
Good point. In Device Manager, you can select "Disk Drives", and your hard drive will be listed. The manufacturer of the hard drive should also be shown. And, I just double-checked, the Hitachi link was provided above. The Hitachi Drive Fitness Test should be helpful.

To get to Device Manager:
right click My Computer,
select Properties,
select Hardware Tab,
select Device Manager button,

Then select "Disk Drives", and the manufacturer should be listed.
 

birdpup

Banned
May 7, 2005
746
0
0
My mind is elsewhere, sorry about that. :eek:

It is a good probability the HIT is for Hitachi. It is acceptable to run the Hitachi Drive Fitness without knowing the drive manufacturer. If the drive is manufacturered by a different company then the program will just state it cannot find a Hitachi drive.
 

jakedeez

Golden Member
Jun 21, 2005
1,100
0
0
I ran the diagnostic, it said the HDD was fine, then I tried running the Recovery Console, and then even tried to just format the drive and reinstall windows...

Nothing same error message and BSOD.

I think the hdd is busted.
 

birdpup

Banned
May 7, 2005
746
0
0
Can you test the memory with memtest?
And then test the drive with the Hitachi diagnostic.
Maybe even try the Everest diagnostic utility.

Other people have mentioned that their drive does not work yet the test would state the drive is fine.

It is a relatively simple procedure to replace the hard drive but it is preferable to verify the drive is the problem before purchasing a replacement.
 

stevty2889

Diamond Member
Dec 13, 2003
7,036
8
81
Yeah sometimes the hard drive diagnostics are not accurate when they say the drive is good. My hard drive was giving clicks of death, and not always even being detected by bios..but when I managed to get it detected, and ran the diagnostics on it...it said the drive was fine..

Running memtest is also a good idea. Bad memory can cause hard drive corruption, and you can end up with similar BSOD messages as a bad hard drive would give.
 

birdpup

Banned
May 7, 2005
746
0
0
Originally posted by: jakedeez
Yeah, but I can't run memtest, I can't get into windows..

And now I see what the problem is. :)

memtest is not a windows function and windows is not needed to test the memory. I provided a link earlier to memtest86 and memtest86+. Each of those is a separate bootable program that is loaded onto a floppy disk. With this program in the floppy drive, you will reboot the computer and control of the system will be taken by the memtest program on the floppy. Windows is not needed for a memory test.