Various BSOD while gaming

[powerslyde]

Hi I wanted to get someone else's take on this.

System info not included in my profile:

USAGE: gaming almost exclusively
CPU: 5820k overclocked to 4.2; stock speeds didn’t help
RAM: 2400MHz XMP (stock) 6 passes of memtest 0 errors
BOARD: ASUS X99A, latest chipset drivers, bios 1401, latest BIOS didn't help; this one is better with my SSD
GPU: nVidia GTX 980 stock speeds, latest drivers, which aren't great
SSD: Samsung XP941 actively cooled and “passed” checkdisk, crystaldiskmark/info, and HDTune
PSU: have used 3 different know reliable PSUs and have had the same issues

I appreciate the help. I bluescreen pretty much every time I use this computer. I don't know maybe games/drivers are just buggy now.

 

[axe0]

Hi powerslyde,

Welcome to the 8forums.

I have a few questions:
- Do you know what errors you get?
- You have done MemTest86+? If not, what other memory test?
- Where/Who did you ask about the problem and what were there answers? Do you have some links?

I'll take a look at the files as soon as I am home from school within 45min.

 

[axe0]

I have taken a look at the dumps from this month.

The display drivers and the memory have been blamed.

For the drivers there are 2 things to test to start with.
1. Check Nvidia site for driver updates.
2. Disable the nvidia streaming kernel service or the nvidia streamer service in msconfig.

​

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

[powerslyde]

Well, the large variety of errors is what's so confusing. I probably get memory_management and irql_not_less_or_equal the most but there's more. Many seem driver related but it's usually a blue screen/random restart more than a ctd.

I ran memtest86 overnight.

I haven't asked anyone else about this except the MS support forums simultaneously with this thread.

 

[powerslyde]

I have the latest nVidia drivers...I will try the 2nd suggestion when I get home.

When you say memory, could that be video memory?

 

[axe0]

RAM

 

[powerslyde]

OK. I'll run memtest86 again, too.

 

[axe0]

OK. I'll run memtest86 again, too.

This time please 8 complete passes, because less is not conclusive which makes it a waste of time.

 

[powerslyde]

OK I went through 8 passes with zero errors. So, my ram, PSU, SSD, and CPU seem fine. I just ordered a new card to replace mt 980. The only thing left after that is my board or it's software/drivers.

Not sure what else could cause memory_management BSOD.

 

[axe0]

We might find the cause with drivers with stressing them out.

Diagnostic Test

DRIVER VERIFIER

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[powerslyde]

OK I'll try that today.

 

[powerslyde]

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
---------

 

[axe0]

Use the tool again and upload the zip file.
You can't upload dump files.

 

[powerslyde]

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.

 

[axe0]

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

 

[axe0]

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*[URL]http://msdl.microsoft.com/download/symbols[/URL]
Symbol search path is: SRV*c:\symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
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
[B]Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+24b )[/B]


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.

 

[Stevles]

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.

 

[powerslyde]

View attachment 65446

View 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,.

 

[Stevles]

View attachment 65446

View 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?

 

[powerslyde]

8.1