Spencer said:
Well I believe I have gotten some sort of virus on my computer. When I
start
it up I get a blue screen with the error code 0X00000024 (0X001902FE,
0XB84EB4E0, 0XB84EB1DC, 0X8A4FE889). My computer only runs in safe
mode right
now. I've tried anti malware and registry fixes but I still get a blue
screen. Any possible solutions?
The first thing I would check is the hard drive and file system. If
possible, back up your important data, then run:
CHKDSK /r
from the command prompt in Safe Mode, or from a Safe Mode Command Prompt
boot.
I would also be advisable to run a hard drive diagnostic from bootable
media (e.g. CD). Seagate Seatools for DOS or the diagnostic from your
particular hard drive manufacturer. If the issue still exists after
CHKDSK and a diagnostic, then explore the other possibilities.
0x00000024: NTFS_FILE_SYSTEM
http://aumha.org/a/stop.php#0x24
<quote>
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.
</quote>
Bug Check 0x24: NTFS_FILE_SYSTEM
http://msdn.microsoft.com/en-gb/library/ms793935.aspx
<quote>
One possible cause of this bug check is disk corruption. Corruption in
the NTFS file system or bad blocks (sectors) on the hard disk can induce
this error. Corrupted SCSI and IDE drivers can also adversely affect the
system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the
nonpaged pool memory is completely depleted, this error can stop the
system. However, during the indexing process, if the amount of available
nonpaged pool memory is very low, another kernel-mode driver requiring
nonpaged pool memory can also trigger this error.
</quote>