TechSpot

Blue Screen - During games.

By Eddzzz
Aug 9, 2009
  1. Hey ive been noticing a blue screen of death on my computer playing one game in particular, Call Of Duty: WAW and it only happens when i play multiplayer on a certain map. However, i am stumped on where to start so any advice will be greatly appreciated. (And im new - haha)

    Thanks, Kris
     
  2. Eddzzz

    Eddzzz TS Rookie Topic Starter

    Just been reading some othewr posts and i have located and extracted my minidump file and seems to be pointing to atkdisp??? will load on the mini dump file and i imagine that it has something to do with the video card. I have a 8800gt. Minidump:


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini080909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.090206-1234
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun Aug 9 19:10:54.328 2009 (GMT+1)
    System Uptime: 0 days 4:13:26.921
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    ....................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, bf85b6bc, b461c42c, 0}

    Unable to load image atkdisp.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atkdisp.dll
    *** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll
    Probably caused by : atkdisp.dll ( atkdisp+ded0 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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: bf85b6bc, The address that the exception occurred at
    Arg3: b461c42c, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    win32k!MultiUserGreTrackRemoveEngResource+1c
    bf85b6bc 8901 mov dword ptr [ecx],eax

    TRAP_FRAME: b461c42c -- (.trap 0xffffffffb461c42c)
    ErrCode = 00000002
    eax=00000000 ebx=b461cce8 ecx=00000000 edx=00000000 esi=bfa05c14 edi=b461c4fc
    eip=bf85b6bc esp=b461c4a0 ebp=b461c4a0 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    win32k!MultiUserGreTrackRemoveEngResource+0x1c:
    bf85b6bc 8901 mov dword ptr [ecx],eax ds:0023:00000000=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: hl2.exe

    LAST_CONTROL_TRANSFER: from bf85b690 to bf85b6bc

    STACK_TEXT:
    b461c4a0 bf85b690 bfa05c14 b461c6fa b461c51c win32k!MultiUserGreTrackRemoveEngResource+0x1c
    b461c4b0 bf9e2ed0 bfa05c24 b461c5ef b461c6fa win32k!EngFreeMem+0x16
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b461c51c bf9e3fa9 bfa089e8 00000010 e4912ba8 atkdisp+0xded0
    b461c554 bf9e4253 00000004 00008000 bfa089e0 atkdisp+0xefa9
    b461c56c bf9e4517 00008000 bfa089e0 b461c804 atkdisp+0xf253
    b461c57c bf9eb6fe b461cc78 e24d3010 00000000 atkdisp+0xf517
    b461c804 bf9ed2ee 00000002 00000100 00000002 atkdisp+0x166fe
    b461c8c0 bf9f6ecf bfa01930 b461cc98 bf9d892e atkdisp+0x182ee
    b461c8cc bf9d892e bfa01930 e24af714 b461cce8 atkdisp+0x21ecf
    b461cc98 bf907de2 0000cce8 e24af714 e48a36d0 atkdisp+0x392e
    b461ccd0 bf9c8329 b461cce8 b461cd64 0013e02c win32k!WatchdogDdFlip+0x38
    b461cd48 8054162c 14400004 45400007 00000000 dxg!DxDdFlip+0x261
    b461cd48 7c90e514 14400004 45400007 00000000 nt!KiFastCallEntry+0xfc
    0013e060 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    atkdisp+ded0
    bf9e2ed0 ?? ???

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: atkdisp+ded0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: atkdisp

    IMAGE_NAME: atkdisp.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 46e53977

    FAILURE_BUCKET_ID: 0x8E_atkdisp+ded0

    BUCKET_ID: 0x8E_atkdisp+ded0

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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: bf85b6bc, The address that the exception occurred at
    Arg3: b461c42c, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    win32k!MultiUserGreTrackRemoveEngResource+1c
    bf85b6bc 8901 mov dword ptr [ecx],eax

    TRAP_FRAME: b461c42c -- (.trap 0xffffffffb461c42c)
    ErrCode = 00000002
    eax=00000000 ebx=b461cce8 ecx=00000000 edx=00000000 esi=bfa05c14 edi=b461c4fc
    eip=bf85b6bc esp=b461c4a0 ebp=b461c4a0 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    win32k!MultiUserGreTrackRemoveEngResource+0x1c:
    bf85b6bc 8901 mov dword ptr [ecx],eax ds:0023:00000000=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: hl2.exe

    LAST_CONTROL_TRANSFER: from bf85b690 to bf85b6bc

    STACK_TEXT:
    b461c4a0 bf85b690 bfa05c14 b461c6fa b461c51c win32k!MultiUserGreTrackRemoveEngResource+0x1c
    b461c4b0 bf9e2ed0 bfa05c24 b461c5ef b461c6fa win32k!EngFreeMem+0x16
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b461c51c bf9e3fa9 bfa089e8 00000010 e4912ba8 atkdisp+0xded0
    b461c554 bf9e4253 00000004 00008000 bfa089e0 atkdisp+0xefa9
    b461c56c bf9e4517 00008000 bfa089e0 b461c804 atkdisp+0xf253
    b461c57c bf9eb6fe b461cc78 e24d3010 00000000 atkdisp+0xf517
    b461c804 bf9ed2ee 00000002 00000100 00000002 atkdisp+0x166fe
    b461c8c0 bf9f6ecf bfa01930 b461cc98 bf9d892e atkdisp+0x182ee
    b461c8cc bf9d892e bfa01930 e24af714 b461cce8 atkdisp+0x21ecf
    b461cc98 bf907de2 0000cce8 e24af714 e48a36d0 atkdisp+0x392e
    b461ccd0 bf9c8329 b461cce8 b461cd64 0013e02c win32k!WatchdogDdFlip+0x38
    b461cd48 8054162c 14400004 45400007 00000000 dxg!DxDdFlip+0x261
    b461cd48 7c90e514 14400004 45400007 00000000 nt!KiFastCallEntry+0xfc
    0013e060 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    atkdisp+ded0
    bf9e2ed0 ?? ???

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: atkdisp+ded0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: atkdisp

    IMAGE_NAME: atkdisp.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 46e53977

    FAILURE_BUCKET_ID: 0x8E_atkdisp+ded0

    BUCKET_ID: 0x8E_atkdisp+ded0

    Followup: MachineOwner
     
  3. Eddzzz

    Eddzzz TS Rookie Topic Starter

    worked it out just disabled gamer osd and splendid and hasnn't dont it since (touch wood)
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...