I finally got your files to download. The error codes point to hardware/hardware related problems.
BugCheck 50 - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 1A - Device driver, memory, kernel
BugCheck 7E - 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.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\Downloads\A-Rar\081210-12589-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b49810
Debug session time: Thu Aug 12 03:44:15.606 2010 (GMT-4)
System Uptime: 0 days 1:50:32.135
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 90b87f3f, 8af979d4, 8af975b0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::ReferenceCommitment+31 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 90b87f3f, The address that the exception occurred at
Arg3: 8af979d4, Exception Record Address
Arg4: 8af975b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VIDMM_DEVICE::ReferenceCommitment+31
90b87f3f 8902 mov dword ptr [edx],eax
EXCEPTION_RECORD: 8af979d4 -- (.exr 0xffffffff8af979d4)
ExceptionAddress: 90b87f3f (dxgmms1!VIDMM_DEVICE::ReferenceCommitment+0x00000031)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 21002000
Attempt to write to address 21002000
CONTEXT: 8af975b0 -- (.cxr 0xffffffff8af975b0)
eax=84ef50d8 ebx=86626000 ecx=00010057 edx=21002000 esi=866e3a28 edi=84ef50a8
eip=90b87f3f esp=8af97a9c ebp=8af97aa0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
dxgmms1!VIDMM_DEVICE::ReferenceCommitment+0x31:
90b87f3f 8902 mov dword ptr [edx],eax ds:0023:21002000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 21002000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b69718
Unable to read MiSystemVaType memory at 82b49160
21002000
FOLLOWUP_IP:
dxgmms1!VIDMM_DEVICE::ReferenceCommitment+31
90b87f3f 8902 mov dword ptr [edx],eax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 90b80bf7 to 90b87f3f
STACK_TEXT:
8af97aa0 90b80bf7 84ef50a8 850da014 86626000 dxgmms1!VIDMM_DEVICE::ReferenceCommitment+0x31
8af97ab8 90b829be 00000000 84ef50a8 00000001 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x67
8af97bb8 90b9993e a5b0ac10 00000000 84d75da0 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xa68
8af97d18 90b9a22f 84ce1550 84c6e008 8af97d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
8af97d28 90b9a4cc 84ce1550 82a3d3f1 865da788 dxgmms1!VidSchiSubmitQueueCommand+0x61
8af97d3c 90b9a573 865da788 00000000 86695d48 dxgmms1!VidSchiRun_PriorityTable+0x24
8af97d50 82c0f6d3 865da788 ac910372 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8af97d90 82ac10f9 90b9a4f4 865da788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_DEVICE::ReferenceCommitment+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265
STACK_COMMAND: .cxr 0xffffffff8af975b0 ; kb
FAILURE_BUCKET_ID: 0x7E_dxgmms1!VIDMM_DEVICE::ReferenceCommitment+31
BUCKET_ID: 0x7E_dxgmms1!VIDMM_DEVICE::ReferenceCommitment+31
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\Downloads\A-Rar\080710-13338-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x82a0a000 PsLoadedModuleList = 0x82b52810
Debug session time: Sat Aug 7 02:50:27.677 2010 (GMT-4)
System Uptime: 0 days 0:58:50.207
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
1: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41285, 86449bb8, 76ffe000, 1}
Probably caused by : memory_corruption ( nt!MiUpdateWsleHash+11a )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041285, The subtype of the bugcheck.
Arg2: 86449bb8
Arg3: 76ffe000
Arg4: 00000001
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41285
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: MDM.EXE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a7e152 to 82a7df1c
STACK_TEXT:
8af4b8f8 82a7e152 76ffe000 000000b3 86449bb8 nt!MiUpdateWsleHash+0x11a
8af4b920 82a7fa11 000000b3 86449bb8 c0802000 nt!MiRemoveWsle+0xaa
8af4bb50 82a2caed 86449bb8 8af4bb6c 86449bb8 nt!MiFreeWsleList+0x618
8af4bc14 82a7d5cf 00000136 86449bb8 00000006 nt!MiTrimWorkingSet+0x162
8af4bc5c 82a7d2e0 00000001 00000001 00000000 nt!MiProcessWorkingSets+0x20f
8af4bc88 82a9321f 00000000 84ac49c8 00000000 nt!MmWorkingSetManager+0xa4
8af4bd50 82c186bb 00000000 aca135b0 00000000 nt!KeBalanceSetManager+0x1af
8af4bd90 82aca0f9 82a93070 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiUpdateWsleHash+11a
82a7df1c cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiUpdateWsleHash+11a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cacf
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_41285_nt!MiUpdateWsleHash+11a
BUCKET_ID: 0x1a_41285_nt!MiUpdateWsleHash+11a
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\Downloads\A-Rar\080310-18158-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x82a44000 PsLoadedModuleList = 0x82b8c810
Debug session time: Tue Aug 3 11:19:25.771 2010 (GMT-4)
System Uptime: 0 days 4:22:54.301
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
........
1: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fe0c35dc, 0, 957db768, 0}
Unable to load image \SystemRoot\System32\cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd+b768 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fe0c35dc, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 957db768, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bac718
Unable to read MiSystemVaType memory at 82b8c160
fe0c35dc
FAULTING_IP:
cdd+b768
957db768 3b81cc050000 cmp eax,dword ptr [ecx+5CCh]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Crysis.exe
CURRENT_IRQL: 0
TRAP_FRAME: acf43abc -- (.trap 0xffffffffacf43abc)
ErrCode = 00000000
eax=852b3030 ebx=88feb07e ecx=fe0c3010 edx=00000001 esi=fe1bc320 edi=00000000
eip=957db768 esp=acf43b30 ebp=acf43b5c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
cdd+0xb768:
957db768 3b81cc050000 cmp eax,dword ptr [ecx+5CCh] ds:0023:fe0c35dc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82a8a638 to 82ac9903
STACK_TEXT:
acf43aa4 82a8a638 00000000 fe0c35dc 00000000 nt!MmAccessFault+0x106
acf43aa4 957db768 00000000 fe0c35dc 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
acf43b5c 957d1753 fe1bc320 acf43bfc 9560d2ec cdd+0xb768
acf43b68 9560d2ec fe1bc320 00000002 acf43c20 cdd+0x1753
acf43bfc 9560e700 00000001 00000000 66051637 win32k!SURFACE::bDeleteSurface+0x235
acf43c10 95610bfd 00000001 00000001 fe096858 win32k!SURFREF::bDeleteSurface+0x14
acf43c24 9561039d 000009e4 00000001 000009e4 win32k!vCleanupSurfaces+0x43
acf43c44 9560c03a fe9aa260 00000000 00000000 win32k!NtGdiCloseProcess+0xc5
acf43c64 9560e91f fe9aa260 00000000 8608de58 win32k!GdiProcessCallout+0x151
acf43c80 82c8cb4c 858dfb68 00000000 8aa1af9d win32k!W32pProcessCallout+0x5d
acf43cfc 82ca5d77 c000004b ffffffff 0032e408 nt!PspExitThread+0x46d
acf43d24 82a8744a ffffffff c000004b 0032e458 nt!NtTerminateProcess+0x1fa
acf43d24 76e264f4 ffffffff c000004b 0032e458 nt!KiFastCallEntry+0x12a
0032e458 00000000 00000000 00000000 00000000 0x76e264f4
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd+b768
957db768 3b81cc050000 cmp eax,dword ptr [ecx+5CCh]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: cdd+b768
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x50_cdd+b768
BUCKET_ID: 0x50_cdd+b768
Followup: MachineOwner
---------
Dumps blamed various drivers and memory corruption as the causes.
Let's start by enabling Driver Verifier. Driver Verifier will cause a BSOD when it encounters a faulty driver. Upload any dumps generated by Driver Verifier.
Driver Verifier - Enable and Disable
I found some obsolete drivers on your system. Win 7 generally does not like older drivers. They can and will cause crashes.
AsIO.sys Mon Dec 17 04:10:20 2007
aztslu7v.SYS Sat Mar 21 10:47:30 2009
KMWDFilter.SYS Thu Mar 29 03:00:14 2007
teamviewervpn.sys Thu Nov 29 03:27:19 2007
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, I found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
The drivers in red font are badly out of date. Update the above drivers or software they are associated with. If you are not using TeamViewer, uninstall it. If you do use it, uninstall this old version and download and install the latest version.
If you need help finding these drivers, please post. We recommend going to the manufacturer's sites rather than using Windows Update or Device Manager.