Blue Screen of Death-memory dumping

There are no errors reported prior to 02 Nov 2010 - have you used a cleaning program on the system?

I would temporarily disable your USB Antivirus program to see if it's conflicting with your AVG
The dump files blame either a driver named FDCDNT.SYS (a component of a program named Hide Files and Folders - have you had this program installed previously?) or your AVG antivirus.

For the AVG, please try this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the AVG from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of AVG using this free tool: AVG - Download tools
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

For the FDCDNT.SYS driver, if you've already uninstalled the program, please go to C:\Windows\System32\drivers and rename FDCDNT.SYS to FDCDNT.BAK

Also,

How To Find Drivers:
It is possible that the following older drivers may be causing your problems.

As such, please either REMOVE or Update them.
DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

The most common drivers are located on this page: Driver Reference
If you can't find the driver, post back and we'll see what we can do.

Here's the older drivers:

Code:

ti21sony.sys Thu Sep 14 08:31:37 2006 (45094BA9)
 - Texas Instruments PCIxx21 PCIxx12 Integrated FlashMedia Controller
 - Driver Reference

SonyPI.sys   Fri Aug 03 01:41:08 2007 (46B2BFF4)
 - Sony Programmable I/O Control Device
 - Driver Reference

SFEP.sys     Fri Aug 03 01:36:08 2007 (46B2BEC8)
 - Sony Firmware Extension Parser driver (known BSOD cause)
 - Driver Reference

VSTAZL3.SYS  Wed Oct 15 20:30:03 2008 (48F68B0B)
 - Conexant SoftK56 Modem Driver
 - Driver Reference

VSTDPV3.SYS  Wed Oct 15 20:32:04 2008 (48F68B84)
 - Conexant SoftK56 Modem Driver
 - Driver Reference

VSTCNXT3.SYS Wed Oct 15 20:29:13 2008 (48F68AD9)
 - Conexant SoftK56 Modem Driver
 - Driver Reference

If that doesn't help, then please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 08:34:31.632 2010 (UTC - 4:00)
System Uptime: 0 days 2:26:30.926
*** WARNING: Unable to verify timestamp for FDCDNT.SYS
*** ERROR: Module load completed but symbols could not be loaded for FDCDNT.SYS
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
*** WARNING: Unable to verify timestamp for avgmfx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx86.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
Bugcheck code 00000050
Arguments b631d000 00000000 82ca5845 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 00:43:14.898 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:19.099
*** WARNING: Unable to verify timestamp for FDCDNT.SYS
*** ERROR: Module load completed but symbols could not be loaded for FDCDNT.SYS
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
*** WARNING: Unable to verify timestamp for avgmfx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx86.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
Bugcheck code 00000050
Arguments b347f000 00000000 82c9e845 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 00:32:05.895 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:29.095
*** WARNING: Unable to verify timestamp for FDCDNT.SYS
*** ERROR: Module load completed but symbols could not be loaded for FDCDNT.SYS
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
*** WARNING: Unable to verify timestamp for avgmfx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx86.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
Bugcheck code 00000050
Arguments b7baa000 00000000 82ca7845 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 00:21:55.782 2010 (UTC - 4:00)
System Uptime: 0 days 0:27:34.857
*** WARNING: Unable to verify timestamp for FDCDNT.SYS
*** ERROR: Module load completed but symbols could not be loaded for FDCDNT.SYS
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
Bugcheck code 00000050
Arguments c6f65000 00000000 82c8b845 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``