
Quote: Originally Posted by
Josh185
I have been getting several types of BSOD while I am playing Aion. They happen quite often and only seem to happen while playing this game so it may be related to it. I got 2 today and both seemed different.
I was hoping someone could tell me what they mean and if there is something I can do to keep them from happening. I have attached the dump files for both BSODs. My system specs are in my profile.
Does anyone else experience BSOD while playing Aion?
Hi and welcome
Welcome Josh
There are two issues going on here. First this dmp was likely caused by the video driver and specifically the dxgmms1.sys file. You were playing Aion in both. In this one the video driver caused it in the other the video driver and TCP.IP failed.
I would update the video driver
This is the 8th crash involving dxgmms1.sys. TODAY. there is a specific method to un-install and reinstall it. google the file.
If you are running 64bit and have this file pretty good guess it is causing you grief
I would update all the critical drivers as there are at least 4drivers older than 3 years on your system
Then I would run a system file check to verrify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow
If yo are overclocking stop
If you have a raid update its driver
You may have a heat issue causing this problem so I would download an app to monitor it like cpu-z, and gpu-z which are both free.
Hope this helps
Kenn J+
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\112909-16645-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50
Debug session time: Sun Nov 29 14:29:38.987 2009 (GMT-5)
System Uptime: 0 days 2:10:32.704
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880043bbce5, fffff880050f56a8, fffff880050f4f00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
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: fffff880043bbce5, The address that the exception occurred at
Arg3: fffff880050f56a8, Exception Record Address
Arg4: fffff880050f4f00, 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+19
fffff880`043bbce5 488b02 mov rax,qword ptr [rdx]
EXCEPTION_RECORD: fffff880050f56a8 -- (.exr 0xfffff880050f56a8)
ExceptionAddress: fffff880043bbce5 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000019)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000071ccf70
Attempt to read from address 00000000071ccf70
CONTEXT: fffff880050f4f00 -- (.cxr 0xfffff880050f4f00)
rax=fffff880050f5908 rbx=0000000000000000 rcx=fffffa8005873000
rdx=00000000071ccf70 rsi=fffffa800457c080 rdi=fffffa8005873000
rip=fffff880043bbce5 rsp=fffff880050f58e0 rbp=fffffa8004542188
r8=fffffa8006889e01 r9=0000000000000000 r10=0000000000000000
r11=0000000000000098 r12=0000000000000088 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19:
fffff880`043bbce5 488b02 mov rax,qword ptr [rdx] ds:002b:00000000`071ccf70=????????????????
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: 00000000071ccf70
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f30e0
00000000071ccf70
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`043bbce5 488b02 mov rax,qword ptr [rdx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880043b8ed3 to fffff880043bbce5
STACK_TEXT:
fffff880`050f58e0 fffff880`043b8ed3 : 00000000`00000000 fffffa80`0457c080 00000000`00000088 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffff880`050f5910 fffff880`043d365d : 00000000`00000000 fffff8a0`0bc26cb0 fffffa80`00000000 fffffa80`06889e80 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`050f5ae0 fffff880`043d3398 : fffff800`00b96080 fffff880`043d2d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`050f5cd0 fffff880`043d2e96 : 00000000`00000000 fffffa80`0425dd50 00000000`00000080 fffffa80`05853010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`050f5d00 fffff800`03160166 : 00000000`029db367 fffffa80`058704d0 fffffa80`039ed040 fffffa80`058704d0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`050f5d40 fffff800`02e9b486 : fffff800`03035e80 fffffa80`058704d0 fffff800`03043c40 fffff880`01248534 : nt!PspSystemThreadStartup+0x5a
fffff880`050f5d80 00000000`00000000 : fffff880`050f6000 fffff880`050f0000 fffff880`050f5690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff880050f4f00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
Followup: MachineOwner
---------