BSOD, Dump Provided

Do you get this error usually? I saw that internet explorer was running at the time of crash. What was you doing at that time? If this error is due to Internet explorer, I would like you to go to tool-->internet option-->advanced tab-->reset
Also, what antivirus software are you using? Third party software antivirus are known for causing BSODs on some system, I've seen this a lot. Please replace it by Microsoft Security Essential for testing purpose, make sure firewall is on. Please scan whole system for virus:
http://www.microsoft.com/security_essentials

Run system file check: SFC /SCANNOW Command - System File Checker
and disk check: Disk Check

Then, please update your networking driver such as wifi or ethernet etc...

This sounds like a lot to do, and we will get to next step if necessary

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.137\071010-20092-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82e4a000 PsLoadedModuleList = 0x82f92810
Debug session time: Sat Jul 10 14:48:41.486 2010 (UTC + 7:00)
System Uptime: 0 days 0:02:56.280
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 807cd750, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+b )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 807cd750
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

Tuan

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver
STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory

nvmf6232.sys was blamed in one of the dmp file. Nvmf6232.sys with description NVIDIA MCP Networking Function Driver. is a driver file from company NVIDIA Corporation belonging to product NVIDIA Networking Driver. Please download and install fresh copy of it.

Memory corruption was blamed as well. I would recommend to download third party called memtestx86, burn it to CD using ISO RECORDER: http://isorecorder.alexfeinman.com/W7.htm , and let it run for at least 7 passes.

Finally, I still want to ask you this question, what third software antivirus are you using?

Code:

BugCheck 4E, {99, af96e, 2, afc2d}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1000007F, {8, 807cd750, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+b )

Followup: MachineOwner
---------
BugCheck A, {c03ffda0, 0, 0, 8230a0ce}

Probably caused by : memory_corruption ( nt!MiDeletePageTableHierarchy+4e )

Followup: MachineOwner
---------
BugCheck D1, {dc1a, 2, 1, 8b805660}

Unable to load image \SystemRoot\system32\DRIVERS\nvmf6232.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6232.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6232.sys
Probably caused by : nvmf6232.sys ( nvmf6232+3f71 )

Followup: MachineOwner
---------

Hope it's help

Tuan

I rarely seen Avast cause BSODs. However, to eliminate all possible cause, I would like you to remove Avast and replace it by MSE: http://www.microsoft.com/security_essentials
Make sure to remove Avast right way:
avast! Uninstall Utility

Please let us know the result

Tuan

Time to get a new card then...