Blue scree INFO

serverextreme · 05-21-2006, 01:44 PM

Sorry for the double topic I wanted to make sure someone seen the error message I was getting...

Hello OK this is the error message I am getting.

Disable or uninstall any antivirus disk defragmentation or backup utilities check your hard drive comfiguration and check for any updates.
Drivers run CHKDSK/F to check for hard drive corruption and then restart your computer....

***STOP*** 0x00000023 (0x000E00E0,0xf9740784,0xf8740480,0xf025991c)

FASTfat.SXS adress.f025991c.base at f0256000,datestamp,41107eb7

I am not sure what going on so any help would be greatly needed...Thank you

**G10** · 05-21-2006, 01:59 PM

Ok, if I recall corectly, your system is windows XP yes?

1. FASTFAT is a kernel-level driver that provides support for FAT16 volumes in Windows 2000, including features like delayed writes that are normally only supported for NTFS.

The first and more likely culprit, interestingly enough, is not the driver itself but a faulty SIMM or DIMM in the computer. If a FASTFAT error turns up in a system that has not had a problem before, the memory may be the first culprit, and you should swap it out to check.

Some flavors of memory, from specific manufacturers, do not work well in certain brands of motherboard. With DIMMs, one easy way to determine this is by running the machine first with a single DIMM and then with a pair (or more). If the machine runs well on one DIMM but badly with two or more, then that manufacturer's RAM is not working with this particular machine and should be changed out for another variety. (In the event that a machine refused to boot before now boots properly with a change in memory, the memory is the number one culprit.)

Barring faulty RAM, the driver itself is probably corrupt, and will need to be replaced either through a parallel install of Windows or via the Recovery Console. FASTFAT.SYS exists in the %SystemRoom%System32Drivers folder of the operating system, and is stored as FASTFAT.SY_ on the Windows CD-ROM. Running a repair operation from the CD may not work; the file should be replaced by hand.

2.

A problem occurred within a read or write to a FAT16 or FAT32 file system drive. There may be a physical problem with the disk, or an interrupt request packet (IRP) may not be able to be successfully completed or may be corrupted.

I suggest running ChkDsk or ScanDisk as a first effort to address it.

Disable all file system filter drivers such backup utilities, virus scanners, or firewall software. Check the file properties of FASTFAT.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.

These are just some things that should be tried.

It's not the easiest of faults to iron out but if it happened since something was added, then we may have a clue.

Also, was your system an upgrade from 2000 or was it a direct XP install?

serverextreme · 05-21-2006, 02:08 PM

Hello G10, My system was xp from the start I did not upgrade it to xp.
Let me see if I can remember. If I am correct it started when I bought a new memory card..Them I started getting that blue screen. Infact I also placed the same card in my wife Pc we have the same PC's
and it did the same thing to her pc.

Her PC is ok becaused I removed it but my machine keeps doing
the same thing even after I removed the card.

**G10** · 05-21-2006, 03:13 PM

I'm sorry about the basic question here but I don't fully understand - Memory card as in Stick of Ram or a Memory card that required some driver etc?

Can you give me some details on this little bugger - Make - Model, everything you can basically.

The fact that you said it happened on 2 systems with this device starts to ring alarm bells. - Of course this could be a red herring as I have seen this happen enough times but it's as good a place as any to start

serverextreme · 05-21-2006, 03:43 PM

Very sorry G10, As in stick of ram, I should have been clear on that.

Here is the spec on my machine
Dell Dimension 2350
Celeron (R) CPU.2.00 GHz
1.99.GHz 256.MB of Ram

**G10** · 05-21-2006, 03:56 PM

Try swapping all your RAM from your wife's PC into yours and visa-versa.

Lets see where that gets you. - Just wondering if the problem will follow.

Also, it could be a faulty memory slot on the board as I have seen something similar before but before we pursue something else, lets rule out the RAM.

serverextreme · 05-21-2006, 03:59 PM

Ummm I really think it's the ram slot of something along that line. I will try to see what I can do thank you

**G10** · 05-21-2006, 04:03 PM

Quote:

Originally Posted by serverextreme

Ummm I really think it's the ram slot of something along that line. I will try to see what I can do thank you

How many slots has your PC got dude?

Obviously, try a stick in one, if it falls over, move it to another one etc etc until the faulty slot is identified.

You will find it if it's a faulty slot or a faulty stick even.

Right, I will back off now and give you some breathing space

serverextreme · 05-21-2006, 04:17 PM

Quote:

Originally Posted by G10

How many slots has your PC got dude?

Obviously, try a stick in one, if it falls over, move it to another one etc etc until the faulty slot is identified.

You will find it if it's a faulty slot or a faulty stick even.

Right, I will back off now and give you some breathing space

My Pc has two slots, I will try moving the memory stick around to see what happens
if you don't see me on again that mean I am unable to login again