I looked at the three most recent dumps. This is a hardware/hardware related issue.
Error code 1E, KMODE_EXCEPTION_NOT_HANDLED - usual causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M - usual causes are Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
The dumps give us a specific cause but they point to memory corruption and possibly a video card or driver problem.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+5dd3952f01f0d8e8
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff880097a7ae8 -- (.exr 0xfffff880097a7ae8)
ExceptionAddress: fffff80002ec75ce (nt!KySwitchKernelStackCallout+0x000000000000002e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff880097a7b90 -- (.trap 0xfffff880097a7b90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fefff880097a7d70
rdx=fffff8800336c138 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec75ce rsp=fffff880097a7d20 rbp=fffff88002fcafa0
r8=0000000000000004 r9=0000000000020000 r10=fffffa800b037000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!KySwitchKernelStackCallout+0x2e:
fffff800`02ec75ce 4c8b5128 mov r10,qword ptr [rcx+28h] ds:f000:fefff880`097a7d98=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ec746e to fffff80002ecf710
STACK_TEXT:
fffff880`097a6bd8 fffff800`02ec746e : 80000000`7a805867 fffff880`097a6c40 fffff880`097a7350 fffff800`02efc668 : nt!KeBugCheck
fffff880`097a6be0 fffff800`02ef540d : fffff800`030dbcf8 fffff800`0301eaf0 fffff800`02e5f000 fffff880`097a7ae8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`097a6c10 fffff800`02efca90 : fffff800`0301eae8 fffff880`097a6c88 fffff880`097a7ae8 fffff800`02e5f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`097a6c40 fffff800`02f099ef : fffff880`097a7ae8 fffff880`097a7350 fffff880`00000000 fffff880`02fcad90 : nt!RtlDispatchException+0x410
fffff880`097a7320 fffff800`02eced82 : fffff880`097a7ae8 00000000`00000000 fffff880`097a7b90 fffffa80`03ce3040 : nt!KiDispatchException+0x16f
fffff880`097a79b0 fffff800`02ecd68a : 00000000`00000000 fffffa80`04a82f20 fffffa80`04df7b60 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`097a7b90 fffff800`02ec75ce : 00000000`00000000 00000000`0014eaa0 00000000`77d64270 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`097a7d20 fffff800`02ec7581 : 00000000`00000000 fffffa80`03ce3040 fffff880`097a8000 fffff800`02edf01a : nt!KySwitchKernelStackCallout+0x2e
fffff880`02fcad90 fffff800`02edf01a : fffff880`02fcaf50 fffffa80`03ce3040 fffff880`02fcb350 fffff8a0`02b33140 : nt!KiSwitchKernelStackContinue
fffff880`02fcadb0 fffff880`0123fb69 : fffff880`01241534 fffff880`02fcaec8 fffff6fc`00001000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x29a
fffff880`02fcae90 fffff880`0123f036 : fffffa80`048c8d80 00000000`00000000 fffff8a0`02b33140 00000000`00000000 : Ntfs!NtfsMultipleAsync+0xa9
fffff880`02fcaf00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsNonCachedIo+0x216
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec746e 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800fe2105b, fffff8800408d658, fffff8800408cec0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )
Followup: MachineOwner
---------
1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800fe2105b, The address that the exception occurred at
Arg3: fffff8800408d658, Exception Record Address
Arg4: fffff8800408cec0, 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_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`0fe2105b 48392cf0 cmp qword ptr [rax+rsi*8],rbp
EXCEPTION_RECORD: fffff8800408d658 -- (.exr 0xfffff8800408d658)
ExceptionAddress: fffff8800fe2105b (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x000000000000010b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800408cec0 -- (.cxr 0xfffff8800408cec0)
rax=fefff8a00d93eb00 rbx=fffff8a00dd248c0 rcx=fffff8a00d93eb30
rdx=0000000000000005 rsi=0000000000000004 rdi=fffffa8006613000
rip=fffff8800fe2105b rsp=fffff8800408d890 rbp=0000000000001a01
r8=0000000000000006 r9=0000000000000006 r10=0000000000000030
r11=fffffa80066143d8 r12=0000000000000003 r13=0000000000000004
r14=fffffa8005cbc840 r15=0000000000000007
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b:
fffff880`0fe2105b 48392cf0 cmp qword ptr [rax+rsi*8],rbp ds:002b:fefff8a0`0d93eb20=????????????????
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: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b90e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`0fe2105b 48392cf0 cmp qword ptr [rax+rsi*8],rbp
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800fe1e8af to fffff8800fe2105b
STACK_TEXT:
fffff880`0408d890 fffff880`0fe1e8af : 00000000`00000000 fffffa80`04f67028 00000000`00000007 fffffa80`04f68050 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b
fffff880`0408d8d0 fffff880`0fe3865d : 00000000`00000000 fffff8a0`0c2aa950 fffffa80`00000004 fffffa80`05cbc840 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0408daa0 fffff880`0fe38398 : fffff880`009edec0 fffff880`0fe37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0408dc90 fffff880`0fe37e96 : 00000000`00000000 fffffa80`05cdb330 00000000`00000080 fffffa80`065f4150 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0408dcc0 fffff800`03125c06 : 00000000`0380cecc fffffa80`065808c0 fffffa80`03ccfb30 fffffa80`065808c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0408dd00 fffff800`02e5fc26 : fffff880`009e9180 fffffa80`065808c0 fffff880`009f3f40 fffff880`01247534 : nt!PspSystemThreadStartup+0x5a
fffff880`0408dd40 00000000`00000000 : fffff880`0408e000 fffff880`04088000 fffff880`0408d650 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff8800408cec0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
Probably caused by : storport.sys ( storport!StorPortNotification+46 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+5dd3952f01f4df14
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80000b9c828 -- (.exr 0xfffff80000b9c828)
ExceptionAddress: fffff880010830f6 (storport!StorPortNotification+0x0000000000000046)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80000b9c8d0 -- (.trap 0xfffff80000b9c8d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fefffa8005105a90 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800378a010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010830f6 rsp=fffff80000b9ca60 rbp=fffffa80046ca990
r8=fffffa8005c9e448 r9=fffff80000b9caf0 r10=fffffa80046c5008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
storport!StorPortNotification+0x46:
fffff880`010830f6 c6808d000000ab mov byte ptr [rax+8Dh],0ABh ds:0001:fefffa80`05105b1d=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e6f46e to fffff80002e77710
STACK_TEXT:
fffff800`00b9b918 fffff800`02e6f46e : fffff800`02ec1f5d fffff800`02ec1f5e fffff800`00b9c090 fffff800`02ea4668 : nt!KeBugCheck
fffff800`00b9b920 fffff800`02e9d40d : fffff800`03085b7c fffff800`02fbfe84 fffff800`02e07000 fffff800`00b9c828 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b950 fffff800`02ea4a90 : fffff800`02fc6b14 fffff800`00b9b9c8 fffff800`00b9c828 fffff800`02e07000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b980 fffff800`02eb19ef : fffff800`00b9c828 fffff800`00b9c090 fffff800`00000000 fffffa80`05c9e448 : nt!RtlDispatchException+0x410
fffff800`00b9c060 fffff800`02e76d82 : fffff800`00b9c828 fffffa80`046c41b0 fffff800`00b9c8d0 fffffa80`046c5008 : nt!KiDispatchException+0x16f
fffff800`00b9c6f0 fffff800`02e7568a : fffffa80`048ad1b0 fffffa80`03ec1c10 fffffa80`048b1030 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c8d0 fffff880`010830f6 : 00000000`00000004 fffffa80`046c9f68 fffff880`0378a380 00000000`00000004 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9ca60 fffff880`01048453 : 00000000`00000000 fffffa80`046c5008 fffffa80`05c9e448 00000000`00000000 : storport!StorPortNotification+0x46
fffff800`00b9cae0 00000000`00000000 : fffffa80`046c5008 fffffa80`05c9e448 00000000`00000000 00000000`00000210 : nvstor64+0x5453
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!StorPortNotification+46
fffff880`010830f6 c6808d000000ab mov byte ptr [rax+8Dh],0ABh
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: storport!StorPortNotification+46
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcace
FAILURE_BUCKET_ID: X64_0x1E_storport!StorPortNotification+46
BUCKET_ID: X64_0x1E_storport!StorPortNotification+46
Followup: MachineOwner
---------
Two of the dumps show error c0000005 which is memory corruption. One blames Direct X which indicates your graphics adapter and keynoter blames storport.sys which is a Microsoft program very likely not the real cause.
I find some out of date drivers on your system. Win 7 does not like older drivers; they can and do cause memory corruption and crashes. I suggest you start with updating these drivers -
BCM42RLY.sys Tue Jul 07 20:34:55 2009
bcmwl664.sys Tue Jul 07 20:45:04 2009
itecir.sys Mon Mar 09 04:58:47 2009
nvmf6264.sys Wed Jul 01 14:55:18 2009
nvsmu.sys Mon Jun 29 03:36:37 2009
OA001Ufd.sys Tue Jun 03 05:30:37
2008
OA001Vid.sys Mon Aug 25 09:07:17
2008
rimmpx64.sys Thu Jun 25 04:04:18 2009
rimspx64.sys Thu Jun 25 03:13:43 2009
rixdpx64.sys Thu Jun 25 03:38:50 2009
stwrt64.sys Mon Jun 29 13:52:05 2009
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (
DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
Once you update these drivers, let us know and run your system. If you get another BSOD, please upload it and we will take the next step which will be to test your RAM.
Quote