BSOD with minidump files attached

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Please provide this information also: https://www.sevenforums.com/crashes-d...tructions.html

It is possible that the following older drivers may be causing your problems.
Please either REMOVE or Update the older drivers listed below.

HOW TO FIND DRIVERS:
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 find.

Here's the older drivers that were found in the memory dump files:

Code:

aswTdi.SYS   Wed Nov 26 12:16:37 2008 (492D8475)
 - avast! TDI Filter Driver
 - Driver Reference

aswRdr.SYS   Wed Nov 26 12:16:28 2008 (492D846C)
 - avast! TDI RDR Driver
 - Driver Reference

Rtnicxp.sys  Fri May 30 11:12:11 2008 (4840194B)
 - Realtek 10/100/1000 NDIS 5.1 Driver
 - Driver Reference

aswSP.SYS    Wed Nov 26 12:17:35 2008 (492D84AF)
 - avast! Self Protection Driver
 - Driver Reference

aswMonFlt.sys Mon Nov 24 13:09:57 2008 (492AEDF5)
 - avast! File System Minifilter Driver
 - Driver Reference

aswFsBlk.sys Mon Nov 24 13:10:09 2008 (492AEE01)
 - avast! File System Access Blocking Driver                                                              
 - Driver Reference

In the event that the above suggestions don't fix the issue, please run Driver Verifier according to these instructions:

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: Tue Nov  9 16:14:03.281 2010 (UTC - 5:00)
System Uptime: 0 days 0:19:06.029
Probably caused by : hardware ( nt!IopParseDevice+bdb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  svchost.exe
Bugcheck code 1000008E
Arguments c0000005 82a813b1 8c1876a4 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 15:27:41.680 2010 (UTC - 5:00)
System Uptime: 0 days 0:23:10.428
Probably caused by : hardware ( rdyboost!SmdProcessReadWrite+5d4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  System
Bugcheck code 1000008E
Arguments c0000005 88b5732e 8726bb3c 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 15:00:03.141 2010 (UTC - 5:00)
System Uptime: 0 days 0:09:48.765
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xDF
PROCESS_NAME:  System
Bugcheck code 000000DF
Arguments 828dfd82 848d1de8 848d1de8 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 14:24:01.617 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:57.365
Probably caused by : ntkrpamp.exe ( nt!ExfReleasePushLockShared+3d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  iexplore.exe
Bugcheck code 1000008E
Arguments c0000005 828ec4e5 89dd9950 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 14:14:29.839 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:38.587
Probably caused by : ntkrpamp.exe ( nt!CcUninitializeCacheMap+189 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  avast.setup
Bugcheck code 0000000A
Arguments 00040000 00000002 00000000 828e1342
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``