blue screen with 0x00000024 error

T20

Weaksauce
Joined
May 3, 2003
Messages
73
Unit: A dell optiplex 745 tower with 2 80gb sata drives. Windows XP Pro. One drive connected to sata0, another one is connected to sata4 on the mobo.

Error code: 0x00000024 (0x00190203, 0x8A6C6008, 0xC0000102, 0x00000000).

Problem: Unit was infected with trojan/malwares(PAV or Personal AntiVirus) I was able to boot into Windows at first, then I reboot it into safe mode and got bsod. The only setting I changed was turn on the smart setting in the bios. Still getting the bsod after I turned the smart setting off. I used UBCD4WIN to boot up the pc. I see drive C with no hard drive space info on it, drive D with 80gb of free space. At first, I though the drives were setup as raid setting, but the owner of the unit doesn't remember anything about raid when he got it from dell. Also two drives are connected to sata0 and sata4 on the mobo. I don't want to running any kind of disk diagnostic program on the drives, afraid it would've do more damage to the drives. I was able to see the Windows logo screen when I disconnected the power to drive2 on the sata4 port, but still got bsod with it. The owner told me that he tried adaware, spybot and spyhunter to remove the PAV, but no success.

Any suggestion on how to fix the problem? Probably have to do a system restore on it, but why I can't see the data on drive 1 in UBCD4WIN, but still able to see the Windows logo screen when I boot up the pc with just that drive?
 
well i found a thread on another site which talks about a similar problem you are having.... i tried reading it all to see if i could explain it better.. but i think its just easier to read the thread your self.. maybe it will give you some idea's on how to fix the problem..

http://www.techspot.com/vb/topic5352.html
 
From aumha.org...
0x00000024: NTFS_FILE_SYSTEM

A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

I'd try a repair installation.
 
Back
Top