STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
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.
Your latest dump file lists
dxgmms1.sys as the probable cause. This is the Windows System DirectX Graphics file and for it to be the cause of your crash is highly unlikely.
Your drivers are looking pretty good. The ASACPI.SYS is now dated 2009. As we're talking graphics you could try re-setting your graphics drivers again, although I have my doubts this will cure your problem.
nVidia Graphics Drivers. - Download and install Driver Sweeper.
- Uninstall your current Graphics setup through Programs and Features
- Boot to Safe Mode
- Run Driver Sweeper to clean up the remnants of your current Graphics set up.
- Reboot to Normal Mode.
- Install your new Graphics set up.
Logically, this is saying to me it's a problem with Perfect World, especially as the machine runs fine at all other times. Do you know if there are any issues with Win 7 64bit and Perfect World?
Bugcheck Analysis: Code:
Loading Dump File [D:\DOWNLOADS\ DUMPS\natewin7user.dmp]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004197d90, fffff880044f26a8, fffff880044f1f10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004197d90, The address that the exception occurred at
Arg3: fffff880044f26a8, Exception Record Address
Arg4: fffff880044f1f10, 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::ReferenceAllocationForPreparation+c4
fffff880`04197d90 8b4810 mov ecx,dword ptr [rax+10h]
EXCEPTION_RECORD: fffff880044f26a8 -- (.exr 0xfffff880044f26a8)
ExceptionAddress: fffff88004197d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880044f1f10 -- (.cxr 0xfffff880044f1f10)
rax=0200000000000000 rbx=fffff8a0077f84c0 rcx=fffffa8005f54ad0
rdx=fffffa80061b82a0 rsi=fffffa8005f45000 rdi=fffffa8005f45000
rip=fffff88004197d90 rsp=fffff880044f28e0 rbp=fffffa8004d3f110
r8=fffffa80061e9f00 r9=0000000000000000 r10=0000000000000000
r11=0000000000000096 r12=fffffa80061b82a0 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`04197d90 8b4810 mov ecx,dword ptr [rax+10h] ds:002b:02000000`00000010=????????
Resetting default scope
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 fffff80002f000e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`04197d90 8b4810 mov ecx,dword ptr [rax+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004194ed3 to fffff88004197d90
STACK_TEXT:
fffff880`044f28e0 fffff880`04194ed3 : 00000000`00000000 fffffa80`04a27058 00000000`0000008b 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`044f2910 fffff880`041af65d : 00000000`00000000 fffff8a0`0259d2d0 fffffa80`00000000 fffffa80`061e9f10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`044f2ae0 fffff880`041af398 : fffff880`009eaec0 fffff880`041aed00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`044f2cd0 fffff880`041aee96 : 00000000`00000000 fffffa80`049b3010 00000000`00000080 fffffa80`05da3010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`044f2d00 fffff800`02f6bbc6 : 00000000`176d060c fffffa80`05f33060 fffffa80`03cce040 fffffa80`05f33060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`044f2d40 fffff800`02ca6bc6 : fffff880`009e6180 fffffa80`05f33060 fffff880`009f0f40 fffff880`0120e2b4 : nt!PspSystemThreadStartup+0x5a
fffff880`044f2d80 00000000`00000000 : fffff880`044f3000 fffff880`044ed000 fffff880`044f2690 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174
STACK_COMMAND: .cxr 0xfffff880044f1f10 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Followup: MachineOwner