Windows 8 and 8.1 Forums

Various BSOD while gaming

  1. #11


    Posts : 14
    Windows 8.1


    OK I'll try that today.

      My System SpecsSystem Spec

  2. #12


    Posts : 14
    Windows 8.1


    By the way, thank you for all your help.

    I'm having a hard time uploading the dmp file. I'll just copy it here. Seems to be driver related?

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.




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




    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17936.amd64fre.winblue_ltsb.150715-0840
    Machine Name:
    Kernel base = 0xfffff801`d841c000 PsLoadedModuleList = 0xfffff801`d86f17b0
    Debug session time: Thu Sep 10 23:01:36.561 2015 (UTC - 7:00)
    System Uptime: 0 days 0:23:52.310
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    Use !analyze -v to get detailed debugging information.


    BugCheck 50, {ffffc00166b42b40, 0, fffff800066b91cb, 2}




    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b )


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


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


    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffc00166b42b40, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800066b91cb, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)


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




    Could not read faulting driver name


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff801d877b138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    ffffc00166b42b40


    FAULTING_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000 mov rax,qword ptr [rbx+1F0h]


    MM_INTERNAL_CODE: 2


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


    BUGCHECK_STR: AV


    PROCESS_NAME: Attila.exe


    CURRENT_IRQL: 0


    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


    TRAP_FRAME: ffffd000231e16e0 -- (.trap 0xffffd000231e16e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc0016964dcb0 rbx=0000000000000000 rcx=000000000000161a
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800066b91cb rsp=ffffd000231e1870 rbp=ffffd000231e1dc0
    r8=0000000000000002 r9=ffffc0017307a000 r10=ffffe000232cef00
    r11=ffffd000231e1c98 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b:
    fffff800`066b91cb 488b83f0010000 mov rax,qword ptr [rbx+1F0h] ds:00000000`000001f0=????????????????
    Resetting default scope


    LAST_CONTROL_TRANSFER: from fffff801d857fdf9 to fffff801d856b9a0


    STACK_TEXT:
    ffffd000`231e1478 fffff801`d857fdf9 : 00000000`00000050 ffffc001`66b42b40 00000000`00000000 ffffd000`231e16e0 : nt!KeBugCheckEx
    ffffd000`231e1480 fffff801`d846f509 : 00000000`00000000 ffffe000`229a0780 ffffd000`231e16e0 fffff801`d84791be : nt! ?? ::FNODOBFM::`string'+0x3f39
    ffffd000`231e1520 fffff801`d8575c2f : 00000000`00000000 ffffc001`66b42950 fffff6e0`00b9bd00 80000003`32dcc963 : nt!MmAccessFault+0x769
    ffffd000`231e16e0 fffff800`066b91cb : ffffe000`2348fc70 00000000`74d60000 fffff800`0655e000 ffffe000`234c7080 : nt!KiPageFault+0x12f
    ffffd000`231e1870 fffff800`0668fa31 : 00000000`00000000 fffff800`066b2cbe 00000000`00000002 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b
    ffffd000`231e1c40 fffff800`0655a049 : 00000000`00000200 ffffd000`231e2950 ffffc001`6b496ec0 ffffd000`231e1dc0 : dxgmms1!VidMmReferenceDmaBuffer+0x55
    ffffd000`231e1ca0 fffff800`06552c35 : ffffc001`6b4d4000 00000000`00000000 00000000`00000000 00000000`ff34b000 : dxgkrnl!DXGCONTEXT::Render+0x229
    ffffd000`231e27f0 fffff801`d85771b3 : ffffe000`234c7080 ffffe000`234c7080 00000000`0f970000 ffffe000`23539880 : dxgkrnl!DxgkRender+0x325
    ffffd000`231e2b00 00000000`77a177fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0e75e6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a177fa




    STACK_COMMAND: kb


    FOLLOWUP_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000 mov rax,qword ptr [rbx+1F0h]


    SYMBOL_STACK_INDEX: 4


    SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: dxgmms1


    IMAGE_NAME: dxgmms1.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 54505506


    IMAGE_VERSION: 6.3.9600.17415


    BUCKET_ID_FUNC_OFFSET: 24b


    FAILURE_BUCKET_ID: AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer


    BUCKET_ID: AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer


    ANALYSIS_SOURCE: KM


    FAILURE_ID_HASH_STRING: km:av_dxgmms1!vidmm_global::referencedmabuffer


    FAILURE_ID_HASH: {ab9700ce-55f9-ad00-8448-fe686b7375c6}


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


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


    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffc00166b42b40, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800066b91cb, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)


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




    Could not read faulting driver name


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump


    READ_ADDRESS: ffffc00166b42b40


    FAULTING_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000 mov rax,qword ptr [rbx+1F0h]


    MM_INTERNAL_CODE: 2


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


    BUGCHECK_STR: AV


    PROCESS_NAME: Attila.exe


    CURRENT_IRQL: 0


    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


    TRAP_FRAME: ffffd000231e16e0 -- (.trap 0xffffd000231e16e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc0016964dcb0 rbx=0000000000000000 rcx=000000000000161a
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800066b91cb rsp=ffffd000231e1870 rbp=ffffd000231e1dc0
    r8=0000000000000002 r9=ffffc0017307a000 r10=ffffe000232cef00
    r11=ffffd000231e1c98 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b:
    fffff800`066b91cb 488b83f0010000 mov rax,qword ptr [rbx+1F0h] ds:00000000`000001f0=????????????????
    Resetting default scope


    LAST_CONTROL_TRANSFER: from fffff801d857fdf9 to fffff801d856b9a0


    STACK_TEXT:
    ffffd000`231e1478 fffff801`d857fdf9 : 00000000`00000050 ffffc001`66b42b40 00000000`00000000 ffffd000`231e16e0 : nt!KeBugCheckEx
    ffffd000`231e1480 fffff801`d846f509 : 00000000`00000000 ffffe000`229a0780 ffffd000`231e16e0 fffff801`d84791be : nt! ?? ::FNODOBFM::`string'+0x3f39
    ffffd000`231e1520 fffff801`d8575c2f : 00000000`00000000 ffffc001`66b42950 fffff6e0`00b9bd00 80000003`32dcc963 : nt!MmAccessFault+0x769
    ffffd000`231e16e0 fffff800`066b91cb : ffffe000`2348fc70 00000000`74d60000 fffff800`0655e000 ffffe000`234c7080 : nt!KiPageFault+0x12f
    ffffd000`231e1870 fffff800`0668fa31 : 00000000`00000000 fffff800`066b2cbe 00000000`00000002 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b
    ffffd000`231e1c40 fffff800`0655a049 : 00000000`00000200 ffffd000`231e2950 ffffc001`6b496ec0 ffffd000`231e1dc0 : dxgmms1!VidMmReferenceDmaBuffer+0x55
    ffffd000`231e1ca0 fffff800`06552c35 : ffffc001`6b4d4000 00000000`00000000 00000000`00000000 00000000`ff34b000 : dxgkrnl!DXGCONTEXT::Render+0x229
    ffffd000`231e27f0 fffff801`d85771b3 : ffffe000`234c7080 ffffe000`234c7080 00000000`0f970000 ffffe000`23539880 : dxgkrnl!DxgkRender+0x325
    ffffd000`231e2b00 00000000`77a177fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0e75e6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a177fa




    STACK_COMMAND: kb


    FOLLOWUP_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000 mov rax,qword ptr [rbx+1F0h]


    SYMBOL_STACK_INDEX: 4


    SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: dxgmms1


    IMAGE_NAME: dxgmms1.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 54505506


    IMAGE_VERSION: 6.3.9600.17415


    BUCKET_ID_FUNC_OFFSET: 24b


    FAILURE_BUCKET_ID: AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer


    BUCKET_ID: AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer


    ANALYSIS_SOURCE: KM


    FAILURE_ID_HASH_STRING: km:av_dxgmms1!vidmm_global::referencedmabuffer


    FAILURE_ID_HASH: {ab9700ce-55f9-ad00-8448-fe686b7375c6}


    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  3. #13



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Use the tool again and upload the zip file.
    You can't upload dump files.
      My System SpecsSystem Spec

  4. #14


    Posts : 14
    Windows 8.1


    OK I'll upload them again. I think there's something wrong with driver verifier. I remember using it in the past everything became really sluggish. Now I'm not seeing any indication it's running. I started it three times. I'll upload the zip file tonight.
      My System SpecsSystem Spec

  5. #15



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Quote Originally Posted by powerslyde View Post
    OK I'll upload them again. I think there's something wrong with driver verifier. I remember using it in the past everything became really sluggish. Now I'm not seeing any indication it's running. I started it three times. I'll upload the zip file tonight.
    Driver verifier stresses the drivers, this is why the system becomes really sluggish,
    It might take some time before it happens
      My System SpecsSystem Spec

  6. #16



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Quote Originally Posted by powerslyde View Post
    By the way, thank you for all your help.

    I'm having a hard time uploading the dmp file. I'll just copy it here. Seems to be driver related?

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    
    
    Loading Dump File [C:\Windows\Minidump\091015-9328-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17936.amd64fre.winblue_ltsb.150715-0840
    Machine Name:
    Kernel base = 0xfffff801`d841c000 PsLoadedModuleList = 0xfffff801`d86f17b0
    Debug session time: Thu Sep 10 23:01:36.561 2015 (UTC - 7:00)
    System Uptime: 0 days 0:23:52.310
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 50, {ffffc00166b42b40, 0, fffff800066b91cb, 2}
    
    
    
    
    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b )
    
    
    Followup: MachineOwner
    ---------
    
    
    9: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffc00166b42b40, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800066b91cb, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    
    
    Debugging Details:
    ------------------
    
    
    
    
    Could not read faulting driver name
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff801d877b138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     ffffc00166b42b40 
    
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000  mov     rax,qword ptr [rbx+1F0h]
    
    
    MM_INTERNAL_CODE:  2
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  AV
    
    
    PROCESS_NAME:  Attila.exe
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    TRAP_FRAME:  ffffd000231e16e0 -- (.trap 0xffffd000231e16e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc0016964dcb0 rbx=0000000000000000 rcx=000000000000161a
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800066b91cb rsp=ffffd000231e1870 rbp=ffffd000231e1dc0
     r8=0000000000000002  r9=ffffc0017307a000 r10=ffffe000232cef00
    r11=ffffd000231e1c98 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b:
    fffff800`066b91cb 488b83f0010000  mov     rax,qword ptr [rbx+1F0h] ds:00000000`000001f0=????????????????
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff801d857fdf9 to fffff801d856b9a0
    
    
    STACK_TEXT:  
    ffffd000`231e1478 fffff801`d857fdf9 : 00000000`00000050 ffffc001`66b42b40 00000000`00000000 ffffd000`231e16e0 : nt!KeBugCheckEx
    ffffd000`231e1480 fffff801`d846f509 : 00000000`00000000 ffffe000`229a0780 ffffd000`231e16e0 fffff801`d84791be : nt! ?? ::FNODOBFM::`string'+0x3f39
    ffffd000`231e1520 fffff801`d8575c2f : 00000000`00000000 ffffc001`66b42950 fffff6e0`00b9bd00 80000003`32dcc963 : nt!MmAccessFault+0x769
    ffffd000`231e16e0 fffff800`066b91cb : ffffe000`2348fc70 00000000`74d60000 fffff800`0655e000 ffffe000`234c7080 : nt!KiPageFault+0x12f
    ffffd000`231e1870 fffff800`0668fa31 : 00000000`00000000 fffff800`066b2cbe 00000000`00000002 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b
    ffffd000`231e1c40 fffff800`0655a049 : 00000000`00000200 ffffd000`231e2950 ffffc001`6b496ec0 ffffd000`231e1dc0 : dxgmms1!VidMmReferenceDmaBuffer+0x55
    ffffd000`231e1ca0 fffff800`06552c35 : ffffc001`6b4d4000 00000000`00000000 00000000`00000000 00000000`ff34b000 : dxgkrnl!DXGCONTEXT::Render+0x229
    ffffd000`231e27f0 fffff801`d85771b3 : ffffe000`234c7080 ffffe000`234c7080 00000000`0f970000 ffffe000`23539880 : dxgkrnl!DxgkRender+0x325
    ffffd000`231e2b00 00000000`77a177fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0e75e6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a177fa
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000  mov     rax,qword ptr [rbx+1F0h]
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: dxgmms1
    
    
    IMAGE_NAME:  dxgmms1.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54505506
    
    
    IMAGE_VERSION:  6.3.9600.17415
    
    
    BUCKET_ID_FUNC_OFFSET:  24b
    
    
    FAILURE_BUCKET_ID:  AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer
    
    
    BUCKET_ID:  AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:av_dxgmms1!vidmm_global::referencedmabuffer
    
    
    FAILURE_ID_HASH:  {ab9700ce-55f9-ad00-8448-fe686b7375c6}
    
    
    Followup: MachineOwner
    ---------
    
    
    9: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffc00166b42b40, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800066b91cb, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    
    
    Debugging Details:
    ------------------
    
    
    
    
    Could not read faulting driver name
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    READ_ADDRESS:  ffffc00166b42b40 
    
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000  mov     rax,qword ptr [rbx+1F0h]
    
    
    MM_INTERNAL_CODE:  2
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  AV
    
    
    PROCESS_NAME:  Attila.exe
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    TRAP_FRAME:  ffffd000231e16e0 -- (.trap 0xffffd000231e16e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc0016964dcb0 rbx=0000000000000000 rcx=000000000000161a
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800066b91cb rsp=ffffd000231e1870 rbp=ffffd000231e1dc0
     r8=0000000000000002  r9=ffffc0017307a000 r10=ffffe000232cef00
    r11=ffffd000231e1c98 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b:
    fffff800`066b91cb 488b83f0010000  mov     rax,qword ptr [rbx+1F0h] ds:00000000`000001f0=????????????????
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff801d857fdf9 to fffff801d856b9a0
    
    
    STACK_TEXT:  
    ffffd000`231e1478 fffff801`d857fdf9 : 00000000`00000050 ffffc001`66b42b40 00000000`00000000 ffffd000`231e16e0 : nt!KeBugCheckEx
    ffffd000`231e1480 fffff801`d846f509 : 00000000`00000000 ffffe000`229a0780 ffffd000`231e16e0 fffff801`d84791be : nt! ?? ::FNODOBFM::`string'+0x3f39
    ffffd000`231e1520 fffff801`d8575c2f : 00000000`00000000 ffffc001`66b42950 fffff6e0`00b9bd00 80000003`32dcc963 : nt!MmAccessFault+0x769
    ffffd000`231e16e0 fffff800`066b91cb : ffffe000`2348fc70 00000000`74d60000 fffff800`0655e000 ffffe000`234c7080 : nt!KiPageFault+0x12f
    ffffd000`231e1870 fffff800`0668fa31 : 00000000`00000000 fffff800`066b2cbe 00000000`00000002 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x24b
    ffffd000`231e1c40 fffff800`0655a049 : 00000000`00000200 ffffd000`231e2950 ffffc001`6b496ec0 ffffd000`231e1dc0 : dxgmms1!VidMmReferenceDmaBuffer+0x55
    ffffd000`231e1ca0 fffff800`06552c35 : ffffc001`6b4d4000 00000000`00000000 00000000`00000000 00000000`ff34b000 : dxgkrnl!DXGCONTEXT::Render+0x229
    ffffd000`231e27f0 fffff801`d85771b3 : ffffe000`234c7080 ffffe000`234c7080 00000000`0f970000 ffffe000`23539880 : dxgkrnl!DxgkRender+0x325
    ffffd000`231e2b00 00000000`77a177fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0e75e6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a177fa
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    fffff800`066b91cb 488b83f0010000  mov     rax,qword ptr [rbx+1F0h]
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: dxgmms1
    
    
    IMAGE_NAME:  dxgmms1.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54505506
    
    
    IMAGE_VERSION:  6.3.9600.17415
    
    
    BUCKET_ID_FUNC_OFFSET:  24b
    
    
    FAILURE_BUCKET_ID:  AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer
    
    
    BUCKET_ID:  AV_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:av_dxgmms1!vidmm_global::referencedmabuffer
    
    
    FAILURE_ID_HASH:  {ab9700ce-55f9-ad00-8448-fe686b7375c6}
    
    
    Followup: MachineOwner
    ---------
    This seems GPU related, either the GPU itself or the drivers.
    But I would need to have the zip to know it.
      My System SpecsSystem Spec

  7. #17


    Wow you're clearly well off if you're replacing expensive parts willy nilly for something that is pretty clearly a driver problem. Fresh install of windows and download only essential drivers and I bet the problem goes away.
      My System SpecsSystem Spec

  8. #18


    Posts : 14
    Windows 8.1


    Attachment 65446

    Attachment 65446


    Hi I hope I attached the zip file correctly.

    I activated verifier and I couldn't get an additional blue screen. Again, everything seemed to run fine. I'll keep trying that.

    Stevles I reinstalled windows twice and got the latest drivers for the board and card form the motherboard/card vendors. The only thing I have on this computer is the appropriate drivers and games.

    Yes after I install my new card and SSD next weekend I will have replaced everything except the board. I guess I found it hard to believe games/drivers could be this buggy but maybe they are,.
      My System SpecsSystem Spec

  9. #19


    Quote Originally Posted by powerslyde View Post
    Attachment 65446

    Attachment 65446


    Hi I hope I attached the zip file correctly.

    I activated verifier and I couldn't get an additional blue screen. Again, everything seemed to run fine. I'll keep trying that.

    Stevles I reinstalled windows twice and got the latest drivers for the board and card form the motherboard/card vendors. The only thing I have on this computer is the appropriate drivers and games.

    Yes after I install my new card and SSD next weekend I will have replaced everything except the board. I guess I found it hard to believe games/drivers could be this buggy but maybe they are,.
    What version of windows are you using?
      My System SpecsSystem Spec

  10. #20


    Posts : 14
    Windows 8.1


    8.1
      My System SpecsSystem Spec

Page 2 of 4 FirstFirst 1234 LastLast
Various BSOD while gaming
Related Threads
BSOD While Gaming in BSOD Crashes and Debugging
Hi All, This is a brand new build and I'm getting BSOD's while gaming - seems random. Some times games work without issue and sometimes I can only get 5 minutes into them. I have seen this with 3 different games at this point. Doesn't seem to be happening when just normal computing. I have...
Solved BSOD? Only while gaming. in BSOD Crashes and Debugging
Hey there. This problem has been going on for a few months but I just though that is was not a big deal in the beginning until recently since it's been happening multiple times a day. I cant really say that it's a BSOD since the computer just freezes and show a random color each before either...
Bsod while gaming in BSOD Crashes and Debugging
Hi I get bsod when I play games usually between 10-30 mins with high graphics games like BF4 and around 1-3 hours with games like WoW.
BSOD after gaming (and afk..) in BSOD Crashes and Debugging
Hi. I was playing to a steam game, and i've been afk for ~ 10 min. When i came back, my computer had reboot. And i had this error the same error as : https://www.eightforums.com/bsod-crashes-debugging/18340-windows-8-pro-memory-dump-error-after-power.html So if you can solve my problem, it would...
BSOD when gaming in BSOD Crashes and Debugging
Hi, I have been experiencing a number of crashes recently when gaming which have been become increasingly frequent. Initially I assumed it may be due to overheating, but all temperatures were normal when checked with coretemp and nvidiainspector. Attached is the SF file. Please can somebody...
BSOD when gaming in BSOD Crashes and Debugging
Hello, I bought my laptop about a month ago and it is constantly crashing when I am playing games. I tried to update video driver for my Radeon (TM) HD 7670M card and games started to appear with flashing screen. I had to rollback that driver. Sometimes it's just showing me error and closing game....
BSOD Only in gaming!!! in BSOD Crashes and Debugging
I am running windows 8 x64 Single Language on a custom built pc. Motherboard: GA-EX58-UD3R Rev.1 (Doesn't have driver update for windows 8 from Gigabyte site anymore) Processor: Intel (R) Core(TM) i7 CPU 920@ 2.67Ghz Ram: 16GB from 2 x Kingmax 8GB DDR3 1333 (Newly Purchased in 2012) VGA:...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook