T
t.cruise
Windows XP Home Edition SP1 formatted NTFS: On boot BSOD:
Stop 0x00000023 (0x000E00E0, 0xF9739D0, 0xF94D0, 0xF025C9BC) Fastfat.sys
Address F025C93BC B50259000
I searched the KBs, for the Stop error, and have gone to a some Stop Error
sites, and have searched Google. The only information for the Stop Error
0x00000023 that I can find deals with either the need to install an NT
update, floppy disks, Windows 2000, and FAT formatted drives, all of which
don't apply. The system runs fine for a week. I'm basing the time between
the BSODs by the dates of the two files in the Minidump folder. Then, the
BSOD error comes back on boot. I reboot, and all is fine. Then I use a
Restore Point from the day before, turn off virtual memory, go to Safe Mode,
delete pagefile.sys., boot to Normal mode, turn virtual memory back on to be
managed by system, and all goes well for about a week, and then the BSOD is
back.
This has happened twice, on boot, in about two weeks. I haven't installed
any new drivers, or software/utilities/hardware, and the only Windows Update
that I installed was a manual update for the Sasser vulnerability. The only
other information that I found was a suggestion by Kelly to download and use
the Debugging Tools. I went to the site, and it's well over my head. I
have also done diagnostics on my WD Ultra ATA/100 hard drive, and it's OK.
There any power outages on this small Hawaiian island. I do have good surge
suppressors, but am wondering if the power outages might have caused some
corruption? No viruses, worms or malware/spyware. All is fine except for
that BSOD every week or so. Could the Sasser vulnerability update have
caused the problem? The only thing that I found in the Event Viewer is:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 5/20/2004
Time: 7:11:24 AM
User: N/A
Computer: TCRUISE
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000023
(0x000e00e0, 0xf97397d0, 0xf97394d0, 0xf025c9bc). A dump was saved in:
C:\WINDOWS\Minidump\Mini052004-01.dmp.
There isn't any ERROR listed for today in the Event Viewer.
Any ideas what could have made this BSOD come up twice in about two weeks,
and a fix?
Stop 0x00000023 (0x000E00E0, 0xF9739D0, 0xF94D0, 0xF025C9BC) Fastfat.sys
Address F025C93BC B50259000
I searched the KBs, for the Stop error, and have gone to a some Stop Error
sites, and have searched Google. The only information for the Stop Error
0x00000023 that I can find deals with either the need to install an NT
update, floppy disks, Windows 2000, and FAT formatted drives, all of which
don't apply. The system runs fine for a week. I'm basing the time between
the BSODs by the dates of the two files in the Minidump folder. Then, the
BSOD error comes back on boot. I reboot, and all is fine. Then I use a
Restore Point from the day before, turn off virtual memory, go to Safe Mode,
delete pagefile.sys., boot to Normal mode, turn virtual memory back on to be
managed by system, and all goes well for about a week, and then the BSOD is
back.
This has happened twice, on boot, in about two weeks. I haven't installed
any new drivers, or software/utilities/hardware, and the only Windows Update
that I installed was a manual update for the Sasser vulnerability. The only
other information that I found was a suggestion by Kelly to download and use
the Debugging Tools. I went to the site, and it's well over my head. I
have also done diagnostics on my WD Ultra ATA/100 hard drive, and it's OK.
There any power outages on this small Hawaiian island. I do have good surge
suppressors, but am wondering if the power outages might have caused some
corruption? No viruses, worms or malware/spyware. All is fine except for
that BSOD every week or so. Could the Sasser vulnerability update have
caused the problem? The only thing that I found in the Event Viewer is:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 5/20/2004
Time: 7:11:24 AM
User: N/A
Computer: TCRUISE
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000023
(0x000e00e0, 0xf97397d0, 0xf97394d0, 0xf025c9bc). A dump was saved in:
C:\WINDOWS\Minidump\Mini052004-01.dmp.
There isn't any ERROR listed for today in the Event Viewer.
Any ideas what could have made this BSOD come up twice in about two weeks,
and a fix?