BSoD when writing to FAT32 storage

[Rooie Rinus]

I recently upgraded my Dell Latitude XT from XP to Windows 7 (fresh install). Everything works pretty fine (although Dell did not bring out Win 7 drivers yet).

Nevertheless, I figured out that when writing/modifying files on a FAT32 storage medium (Internal/external Hard drive/USB stick) I get a BSoD. Sometimes I am able to view the files, sometimes the BSoD occurs immediately after connecting the FAT32 device.

The event viewer does not show many problems. The message related to the BsOD is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x801de000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111209-29515-01.

The other message is (I think) related to a residual of the f-secure virus scanner that I previously installed

The following boot-start or system-start driver(s) failed to load:
FSES

I do not know whether this has any influence on the FAT32 issue.

Could someone help? Thanks in advance.

Martin

 

[torrentg]

Hi.

Please see this link and follow along with what it says. We'll check on your .dmps and have a look.

 

[zigzag3143]

I recently upgraded my Dell Latitude XT from XP to Windows 7 (fresh install). Everything works pretty fine (although Dell did not bring out Win 7 drivers yet).

Nevertheless, I figured out that when writing/modifying files on a FAT32 storage medium (Internal/external Hard drive/USB stick) I get a BSoD. Sometimes I am able to view the files, sometimes the BSoD occurs immediately after connecting the FAT32 device.

The event viewer does not show many problems. The message related to the BsOD is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x801de000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111209-29515-01.

The other message is (I think) related to a residual of the f-secure virus scanner that I previously installed

The following boot-start or system-start driver(s) failed to load:
FSES

I do not know whether this has any influence on the FAT32 issue.

Could someone help? Thanks in advance.

Martin

Martin

Can you go into c:\windows\mindump, zip the dump file (*.dmp) and upload it to us for debugging

thanks

Ken J

 

[Rooie Rinus]

Please find the minidump files attached to this reply.

Thank you very much for your assistance!

Cheers,
Martin

 

[torrentg]

"0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

• A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use the !thread debugger extension to determine the stack limits, and then use the kb (Display Stack Backtrace) debugger command with a large parameter (for example, kb 100) to display the full stack.
• A hardware problem."

The above describes one of the types of errors you're getting. The best thing to do I suppose, is to check the mohterboard manufacturer's site for any bios and chipset updates. Apply them and see how it goes.

 

[pvoegele]

I have recently upgraded from Windows Vista to Windows 7. When HP sent me the update disc, it contained a bios update, which I applied. Also, I installed the most update Intel chipset driver. I am still receiving the BSOD when I try to write to FAT32 devices.

What should I do next?

 

[torrentg]

Covert the FAT32 drive to NTFS. Problem resolved and better too.

 

[usasma]

pvoegele - Your next step should be to start your own topic. That way your issue will get the attention that it deserves - and you won't detract from Rooie Rinus' issue