I’ve had this problem about 4-5 times in a few months. The first time it was when I first got my comp and installed all my crap, I got a Stop 0X00000023 FastFat.sys error. So I defraged, Scandisk, and it never happened again… until I got Avast. It’s happeneded 4 or so more times at boot up since then. I’ve ran memtest/ some hard drive fitness/ no viruses/trojans/spyware/I’ve talked to my computer manufacturer and did everything they told me to do with everytime coming back ok. So i’m kinda at a dead end… ??? Has anyone else had this problem and if so any solutions/other good free antiviruses (not AVG, AVG let me down to much, so I switched to Avast). My theory is the first stop 0x00000023 error was caused by like all my crap being installed and not having defraged yet/etc. and then the rest followed after I installed avast so… Yeah…
XP and trust me I searched everthing and did everything it said and all the problems that could cause it, (not defragged, bad ram (I got good ram), and turn off antivirus software) so could it be avast? I’d rather switch and test rather then disable it for X ammount of time waiting to see if it would occur again…
You said you were getting this BSOD before avast! so it’s not avast!'s fault for sure.
But it can be accelerated since FastFat.sys is a FAT access driver and antivirus checks data on disk more often,so you get BSOD more often with avast! installed.
Yeah but like I said, It said online one of the causes could be not defraging, and after I got my comp and installed everything on it that is alot of stuff and I never defraged until I got the first error and then until a month or two later when I got Avast, before that point I never had the BSOD.
Yeah well everything i’ve read online says defrag or scandisk is the first step to fixing the error, blah blah, contact cpu company, blah blah, disable antivirus software, now steps #1 and #2 i’ve done, now I just simply want to know if avast would and could cause this!?!
Any error(s) in the system log or event log files that may tell us more?
Also check all other log files you can find, to see if they have anything in it that could be related.
Have you already posted this on the MS support board?
No I haven’t posted. I can’t tell you the exact date of the last error so I can’t really get an accurate check in the event logs, Next time it happens I’ll go look into the logs and see if it says anything
0x23 error code says: This indicates that a problem occurred in the FAT file system.
Cause
One possible cause of this bug check is disk corruption. Corruption in the file system or bad blocks (sectors) on the disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system’s ability to read and write to the disk, thus causing the error.
Resolving the Problem
To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.
Not defragging is NOT the cause!!! Fragmentation alone don’t cause HDD data corruption!!! It’s caused by a far more serious problem, usally bad sectors or RAM module malfunction problems.
actually I have the same problem: error in fastfat.sys occured only once since I got the computer without avast. And as soon as I install Avast the system crashes all the time, even if I disable all antivirus services.
After some search I thought it was related to dual core, but according to your thread it due to hard drive or memory failure. I looked into events and I got this:
Harddisk Controller error
is it motherboard or harddisk related ? I saw that other people were using the same motherboard as me with an single core athlon 64 and they didn’t have any problems.
This really has nothing to do with the cpu being duel core or single core … nor that it is an Athon64. This problem indicates something bad/wrong related to either a harddrive (most likely), bad memory module, or both. Have you checked to make sure the memory sticks are properly seated in the slots? Are the harddrive cables securely connected on both ends? ???
Remember, even new harddrives/memory sticks can be bad or go bad in a short time. Although these do not happen often, nothing is perfect.
