locked
Blue Screen problem on Windows 7 RRS feed

  • Question

  • I recently bought a customized gaming computer a little more than month ago, and I get the bluescreen when I play my games and it just restarts the whole system. This has happened about 5 times. I'm not that fluent with computers... so can anyone help me find a solution to this? It's a Windows 7 Home Premium 32-bit if that makes a difference. Here's the report:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.768.3
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    1000008e
      BCP1:    C0000005
      BCP2:    928CF8B3
      BCP3:    8F19E604
      BCP4:    00000000
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    768_1

    Files that help describe the problem:
      C:\Windows\Minidump\110210-19203-01.dmp
      C:\Users\Bianca\AppData\Local\Temp\WER-53453-0.sysdata.xml

    Tuesday, November 2, 2010 1:21 PM

Answers

  • Please do two things,

    Verify that your ATI graphics driver is fully up to date: http://www.amd.com/us/Pages/AMDHomePage.aspx

    Verify the protected OS files for your system from an elevated command prompt by running the following command: sfc /scannow

    If you still receive BSODs afterwards, please upload the latest dumps. If any new dumps show the same errors after you , then you may want to replace the video card.

    1: kd> lmvm atikmpag
    start end module name
    91c09000 91c44000 atikmpag T (no symbols)
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp: Wed Aug 25 19:20:36 2010 (4C75C164)
    CheckSum: 00038DBD
    ImageSize: 0003B000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    1: kd> lmvm atikmdag
    start end module name
    9261c000 92c80000 atikmdag T (no symbols)
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp: Wed Aug 25 19:43:45 2010 (4C75C6D1)
    CheckSum: 00625301
    ImageSize: 00664000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


    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: 928cf8b3, The address that the exception occurred at Arg3: 8f19e604, 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: atikmdag+2c98b3 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx TRAP_FRAME: 8f19e604 -- (.trap 0xffffffff8f19e604) ErrCode = 00000000 eax=00000000 ebx=85607008 ecx=00000aae edx=c4f891d0 esi=0aae0800 edi=85b344c0 eip=928cf8b3 esp=8f19e678 ebp=8f19e680 iopl=0 nv up ei pl nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212 atikmdag+0x2c98b3: 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx ds:0023:0000007c=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: Wow.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 928cfdb3 to 928cf8b3 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8f19e680 928cfdb3 c4f891d0 85b344c0 00020000 atikmdag+0x2c98b3 8f19e700 928cf04d 0019eaa0 a1470000 000000be atikmdag+0x2c9db3 8f19e720 928d070c 8f19eaa0 85607008 855b2b80 atikmdag+0x2c904d 8f19e740 92616750 00000000 8f19e778 91c0e7e5 atikmdag+0x2ca70c 8f19e74c 91c0e7e5 8545a1d0 8f19eaa0 82e1d6ee atikmdag+0x10750 8f19e778 92c8c696 85b34000 8f19eaa0 00000000 atikmpag+0x67e5 8f19e7a0 92c86b79 855b2b80 8f19eaa0 00020000 dxgkrnl+0x22696 8f19eb44 92c88a2b 85795be0 8f19ecb8 1dd1af81 dxgkrnl+0x1cb79 8f19ed28 82a4b44a 072ff694 072ff7e8 771864f4 dxgkrnl+0x1ea2b 8f19ed28 771864f4 072ff694 072ff7e8 771864f4 nt!KiFastCallEntry+0x12a 072ff7e8 00000000 00000000 00000000 00000000 0x771864f4 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+2c98b3 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+2c98b3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c75c6d1 FAILURE_BUCKET_ID: 0x8E_atikmdag+2c98b3 BUCKET_ID: 0x8E_atikmdag+2c98b3 Followup: MachineOwner --------- 0: kd> .trap 8f19e604 ErrCode = 00000000 eax=00000000 ebx=85607008 ecx=00000aae edx=c4f891d0 esi=0aae0800 edi=85b344c0 eip=928cf8b3 esp=8f19e678 ebp=8f19e680 iopl=0 nv up ei pl nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212 atikmdag+0x2c98b3: 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx ds:0023:0000007c=???? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 8f19e680 928cfdb3 c4f891d0 85b344c0 00020000 atikmdag+0x2c98b3 8f19e700 928cf04d 0019eaa0 a1470000 000000be atikmdag+0x2c9db3 8f19e720 928d070c 8f19eaa0 85607008 855b2b80 atikmdag+0x2c904d 8f19e740 92616750 00000000 8f19e778 91c0e7e5 atikmdag+0x2ca70c 8f19e74c 91c0e7e5 8545a1d0 8f19eaa0 82e1d6ee atikmdag+0x10750 8f19e778 92c8c696 85b34000 8f19eaa0 00000000 atikmpag+0x67e5 8f19e7a0 92c86b79 855b2b80 8f19eaa0 00020000 dxgkrnl+0x22696 8f19eb44 92c88a2b 85795be0 8f19ecb8 1dd1af81 dxgkrnl+0x1cb79 8f19ed28 82a4b44a 072ff694 072ff7e8 771864f4 dxgkrnl+0x1ea2b 8f19ed28 771864f4 072ff694 072ff7e8 771864f4 nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ 8f19ed34) 072ff7e8 00000000 00000000 00000000 00000000 0x771864f4 0: kd> .trap 8f19ed34 ErrCode = 00000000 eax=00000000 ebx=05a1c030 ecx=05b43210 edx=05b2ac30 esi=072ff820 edi=05a1cf28 eip=771864f4 esp=072ff67c ebp=072ff7e8 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246 001b:771864f4 ?? ??? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child WARNING: Frame IP not in any known module. Following frames may be wrong. 072ff7e8 00000000 00000000 00000000 00000000 0x771864f4

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

    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 07000000, The subtype of the bugcheck:
    Arg2: 87489788
    Arg3: 85866990
    Arg4: 85836f08

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

    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x119

    PROCESS_NAME: Wow.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 8b40a276 to 82b32d10

    STACK_TEXT:
    807e5ac4 8b40a276 00000119 07000000 87489788 nt!KeBugCheckEx+0x1e
    807e5aec 92d3e95a 02000000 86d451d8 85836f08 watchdog!WdLogEvent5+0xc6
    807e5b04 92d3e9a1 0000378e 87489bc8 82abd6c5 dxgmms1!VidSchiCheckConditionDeviceCommand+0x7a
    807e5b20 92d42d3f 858669c0 87489788 875f12d0 dxgmms1!VidSchiCheckPendingDeviceCommand+0x33
    807e5b6c 92d42d77 0240e008 807e5bbc 92d4435c dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x485
    807e5b78 92d4435c 8540e008 875f0000 875f12d0 dxgmms1!VidSchiProcessCompletedQueuePacket+0xd
    807e5bbc 92d44451 87489788 875f12d0 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3e4
    807e5bd8 92d4451e 87489788 86d4f000 87489788 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
    807e5bf0 92d44832 86d4f000 00000001 86d4e920 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
    807e5c14 92c81bf5 86d4e920 807e5c34 92c81cc4 dxgmms1!VidSchDdiNotifyDpc+0x78
    WARNING: Stack unwind information not available. Following frames may be wrong.
    807e5c20 92c81cc4 86981ae8 86d4e920 00000000 dxgkrnl+0x1bf5
    807e5c34 91c0cf51 86d4e920 00000000 87625ea0 dxgkrnl+0x1cc4
    807e5c48 92634130 86d4e920 807e5c60 92633bb9 atikmpag+0x3f51
    807e5c54 92633bb9 a0000001 807e5c70 92633cbf atikmdag+0x18130
    807e5c60 92633cbf 87438008 a0000001 807e5c80 atikmdag+0x17bb9
    807e5c70 9263f8d0 87438008 807e5d4c 807e5cd0 atikmdag+0x17cbf
    807e5c80 9269ac9c 862c9000 807e5c90 00000040 atikmdag+0x238d0
    807e5cd0 9269f7b1 87609000 92633ca1 87438008 atikmdag+0x7ec9c
    807e5d94 9269f8fb 87609000 876190b0 00000001 atikmdag+0x837b1
    807e5ddc 9269fdac 00000001 876190b0 87609000 atikmdag+0x838fb
    807e5e40 9269ff7d 87609000 876190b0 00000001 atikmdag+0x83dac
    807e5ea8 9269e895 87609000 876190b0 00000001 atikmdag+0x83f7d
    807e5ecc 9269ebce 87609000 807e5ee0 87609000 atikmdag+0x82895
    807e5ef8 92699e12 87609000 8632db40 807e5f18 atikmdag+0x82bce
    807e5f08 926348a6 87609000 86d4e9d8 807e5f28 atikmdag+0x7de12
    807e5f18 91c0d5f9 8632db40 8647b478 807e5f48 atikmdag+0x188a6
    807e5f28 92c818c1 8632db40 86d4ed10 85837dcc atikmpag+0x45f9
    807e5f48 82abe3b5 86d4ed10 86d4e920 00000000 dxgkrnl+0x18c1
    807e5fa4 82abe218 807c5120 85837d48 00000000 nt!KiExecuteAllDpcs+0xf9
    807e5ff4 82abd9dc 9eb77ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
    807e5ff8 9eb77ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
    82abd9dc 00000000 0000001a 00d6850f bb830000 0x9eb77ce4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    dxgmms1!VidSchiCheckConditionDeviceCommand+7a
    92d3e95a c7450871c8ffff mov dword ptr [ebp+8],0FFFFC871h

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: dxgmms1!VidSchiCheckConditionDeviceCommand+7a

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME: dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265

    FAILURE_BUCKET_ID: 0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+7a

    BUCKET_ID: 0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+7a

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


    -- Mike Burr
    • Marked as answer by Leo Huang Tuesday, November 9, 2010 9:11 AM
    Wednesday, November 3, 2010 10:34 PM

All replies

  • Please zip up and upload the files in C:\Windows\Minidump and upload
    them to skydrive and post a link. Note that you may need to copy them to
    your desktop or documents folder first.
     
     

    -- Mike Burr
    Wednesday, November 3, 2010 4:32 AM
  • The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.

    http://msdn.microsoft.com/en-us/library/ff559271(v=VS.85).aspx

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors. - help to do the checks can be found here. http://www.mypchealth.co.uk/GuideTests.php
    4. Check your memory for errors.

    www.mypchealth.co.uk
    Wednesday, November 3, 2010 9:15 AM
  • Alright, I hope I did this right..

     

    http://cid-5347f77f529905d9.office.live.com/embedicon.aspx/Public

    Wednesday, November 3, 2010 1:20 PM
  • Please do two things,

    Verify that your ATI graphics driver is fully up to date: http://www.amd.com/us/Pages/AMDHomePage.aspx

    Verify the protected OS files for your system from an elevated command prompt by running the following command: sfc /scannow

    If you still receive BSODs afterwards, please upload the latest dumps. If any new dumps show the same errors after you , then you may want to replace the video card.

    1: kd> lmvm atikmpag
    start end module name
    91c09000 91c44000 atikmpag T (no symbols)
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp: Wed Aug 25 19:20:36 2010 (4C75C164)
    CheckSum: 00038DBD
    ImageSize: 0003B000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    1: kd> lmvm atikmdag
    start end module name
    9261c000 92c80000 atikmdag T (no symbols)
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp: Wed Aug 25 19:43:45 2010 (4C75C6D1)
    CheckSum: 00625301
    ImageSize: 00664000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


    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: 928cf8b3, The address that the exception occurred at Arg3: 8f19e604, 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: atikmdag+2c98b3 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx TRAP_FRAME: 8f19e604 -- (.trap 0xffffffff8f19e604) ErrCode = 00000000 eax=00000000 ebx=85607008 ecx=00000aae edx=c4f891d0 esi=0aae0800 edi=85b344c0 eip=928cf8b3 esp=8f19e678 ebp=8f19e680 iopl=0 nv up ei pl nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212 atikmdag+0x2c98b3: 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx ds:0023:0000007c=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: Wow.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 928cfdb3 to 928cf8b3 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8f19e680 928cfdb3 c4f891d0 85b344c0 00020000 atikmdag+0x2c98b3 8f19e700 928cf04d 0019eaa0 a1470000 000000be atikmdag+0x2c9db3 8f19e720 928d070c 8f19eaa0 85607008 855b2b80 atikmdag+0x2c904d 8f19e740 92616750 00000000 8f19e778 91c0e7e5 atikmdag+0x2ca70c 8f19e74c 91c0e7e5 8545a1d0 8f19eaa0 82e1d6ee atikmdag+0x10750 8f19e778 92c8c696 85b34000 8f19eaa0 00000000 atikmpag+0x67e5 8f19e7a0 92c86b79 855b2b80 8f19eaa0 00020000 dxgkrnl+0x22696 8f19eb44 92c88a2b 85795be0 8f19ecb8 1dd1af81 dxgkrnl+0x1cb79 8f19ed28 82a4b44a 072ff694 072ff7e8 771864f4 dxgkrnl+0x1ea2b 8f19ed28 771864f4 072ff694 072ff7e8 771864f4 nt!KiFastCallEntry+0x12a 072ff7e8 00000000 00000000 00000000 00000000 0x771864f4 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+2c98b3 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+2c98b3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c75c6d1 FAILURE_BUCKET_ID: 0x8E_atikmdag+2c98b3 BUCKET_ID: 0x8E_atikmdag+2c98b3 Followup: MachineOwner --------- 0: kd> .trap 8f19e604 ErrCode = 00000000 eax=00000000 ebx=85607008 ecx=00000aae edx=c4f891d0 esi=0aae0800 edi=85b344c0 eip=928cf8b3 esp=8f19e678 ebp=8f19e680 iopl=0 nv up ei pl nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212 atikmdag+0x2c98b3: 928cf8b3 6639487c cmp word ptr [eax+7Ch],cx ds:0023:0000007c=???? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 8f19e680 928cfdb3 c4f891d0 85b344c0 00020000 atikmdag+0x2c98b3 8f19e700 928cf04d 0019eaa0 a1470000 000000be atikmdag+0x2c9db3 8f19e720 928d070c 8f19eaa0 85607008 855b2b80 atikmdag+0x2c904d 8f19e740 92616750 00000000 8f19e778 91c0e7e5 atikmdag+0x2ca70c 8f19e74c 91c0e7e5 8545a1d0 8f19eaa0 82e1d6ee atikmdag+0x10750 8f19e778 92c8c696 85b34000 8f19eaa0 00000000 atikmpag+0x67e5 8f19e7a0 92c86b79 855b2b80 8f19eaa0 00020000 dxgkrnl+0x22696 8f19eb44 92c88a2b 85795be0 8f19ecb8 1dd1af81 dxgkrnl+0x1cb79 8f19ed28 82a4b44a 072ff694 072ff7e8 771864f4 dxgkrnl+0x1ea2b 8f19ed28 771864f4 072ff694 072ff7e8 771864f4 nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ 8f19ed34) 072ff7e8 00000000 00000000 00000000 00000000 0x771864f4 0: kd> .trap 8f19ed34 ErrCode = 00000000 eax=00000000 ebx=05a1c030 ecx=05b43210 edx=05b2ac30 esi=072ff820 edi=05a1cf28 eip=771864f4 esp=072ff67c ebp=072ff7e8 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246 001b:771864f4 ?? ??? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child WARNING: Frame IP not in any known module. Following frames may be wrong. 072ff7e8 00000000 00000000 00000000 00000000 0x771864f4

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

    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 07000000, The subtype of the bugcheck:
    Arg2: 87489788
    Arg3: 85866990
    Arg4: 85836f08

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

    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x119

    PROCESS_NAME: Wow.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 8b40a276 to 82b32d10

    STACK_TEXT:
    807e5ac4 8b40a276 00000119 07000000 87489788 nt!KeBugCheckEx+0x1e
    807e5aec 92d3e95a 02000000 86d451d8 85836f08 watchdog!WdLogEvent5+0xc6
    807e5b04 92d3e9a1 0000378e 87489bc8 82abd6c5 dxgmms1!VidSchiCheckConditionDeviceCommand+0x7a
    807e5b20 92d42d3f 858669c0 87489788 875f12d0 dxgmms1!VidSchiCheckPendingDeviceCommand+0x33
    807e5b6c 92d42d77 0240e008 807e5bbc 92d4435c dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x485
    807e5b78 92d4435c 8540e008 875f0000 875f12d0 dxgmms1!VidSchiProcessCompletedQueuePacket+0xd
    807e5bbc 92d44451 87489788 875f12d0 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3e4
    807e5bd8 92d4451e 87489788 86d4f000 87489788 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
    807e5bf0 92d44832 86d4f000 00000001 86d4e920 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
    807e5c14 92c81bf5 86d4e920 807e5c34 92c81cc4 dxgmms1!VidSchDdiNotifyDpc+0x78
    WARNING: Stack unwind information not available. Following frames may be wrong.
    807e5c20 92c81cc4 86981ae8 86d4e920 00000000 dxgkrnl+0x1bf5
    807e5c34 91c0cf51 86d4e920 00000000 87625ea0 dxgkrnl+0x1cc4
    807e5c48 92634130 86d4e920 807e5c60 92633bb9 atikmpag+0x3f51
    807e5c54 92633bb9 a0000001 807e5c70 92633cbf atikmdag+0x18130
    807e5c60 92633cbf 87438008 a0000001 807e5c80 atikmdag+0x17bb9
    807e5c70 9263f8d0 87438008 807e5d4c 807e5cd0 atikmdag+0x17cbf
    807e5c80 9269ac9c 862c9000 807e5c90 00000040 atikmdag+0x238d0
    807e5cd0 9269f7b1 87609000 92633ca1 87438008 atikmdag+0x7ec9c
    807e5d94 9269f8fb 87609000 876190b0 00000001 atikmdag+0x837b1
    807e5ddc 9269fdac 00000001 876190b0 87609000 atikmdag+0x838fb
    807e5e40 9269ff7d 87609000 876190b0 00000001 atikmdag+0x83dac
    807e5ea8 9269e895 87609000 876190b0 00000001 atikmdag+0x83f7d
    807e5ecc 9269ebce 87609000 807e5ee0 87609000 atikmdag+0x82895
    807e5ef8 92699e12 87609000 8632db40 807e5f18 atikmdag+0x82bce
    807e5f08 926348a6 87609000 86d4e9d8 807e5f28 atikmdag+0x7de12
    807e5f18 91c0d5f9 8632db40 8647b478 807e5f48 atikmdag+0x188a6
    807e5f28 92c818c1 8632db40 86d4ed10 85837dcc atikmpag+0x45f9
    807e5f48 82abe3b5 86d4ed10 86d4e920 00000000 dxgkrnl+0x18c1
    807e5fa4 82abe218 807c5120 85837d48 00000000 nt!KiExecuteAllDpcs+0xf9
    807e5ff4 82abd9dc 9eb77ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
    807e5ff8 9eb77ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
    82abd9dc 00000000 0000001a 00d6850f bb830000 0x9eb77ce4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    dxgmms1!VidSchiCheckConditionDeviceCommand+7a
    92d3e95a c7450871c8ffff mov dword ptr [ebp+8],0FFFFC871h

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: dxgmms1!VidSchiCheckConditionDeviceCommand+7a

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME: dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265

    FAILURE_BUCKET_ID: 0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+7a

    BUCKET_ID: 0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+7a

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


    -- Mike Burr
    • Marked as answer by Leo Huang Tuesday, November 9, 2010 9:11 AM
    Wednesday, November 3, 2010 10:34 PM