Games Keep Crashing

[TheDonkeyShow]

Lots of different games keep crashing my PC. Sometimes they will crash back to desktop, and sometimes to blue screen. 

I figured out how to get the memory dump, but i don't know what any of it means. I'll post it under the hardware. I pretty sure that they have been memory related, but not always the same problem.

 

I'm using

 

Windows 8.1

 

AMD Radeon™ R9 Gamer Series

16GB (4 x 4GB) DDR3 2133 MHz CL10

Graphics Chipset
AMD Radeon R9 290x Series

CPU Type
AMD FX(tm)-9590 Eight-Core Processor

Mother Board
Asus SABERTOOTH 990FX R2.0

 

 

 

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

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.18202.amd64fre.winblue_ltsb.160119-0600
Machine Name:
Kernel base = 0xfffff801`2b48d000 PsLoadedModuleList = 0xfffff801`2b760630
Debug session time: Fri Feb 19 18:08:33.785 2016 (UTC - 8:00)
System Uptime: 0 days 3:19:46.468
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {51157, ffffd0012a86a418, ffffd0012a869c20, fffff8012b4c2d7a}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000051157
Arg2: ffffd0012a86a418
Arg3: ffffd0012a869c20
Arg4: fffff8012b4c2d7a

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

EXCEPTION_RECORD:  ffffd0012a86a418 -- (.exr 0xffffd0012a86a418)
ExceptionAddress: fffff8012b4c2d7a (nt!KxWaitForLockOwnerShip+0x0000000000000012)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffd0012a869c20 -- (.cxr 0xffffd0012a869c20;r)
rax=fffff8012b7e2300 rbx=0000000000000001 rcx=ffffd0012a86a6b0
rdx=0800000000000000 rsi=fffff8012b7e22a8 rdi=ffffd0012a86a6b0
rip=fffff8012b4c2d7a rsp=ffffd0012a86a650 rbp=ffffd0012a86a6d0
 r8=0000058000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000fffffffff
r14=0000000000000001 r15=000000000000000f
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff801`2b4c2d7a 48890a          mov     qword ptr [rdx],rcx ds:002b:08000000`00000000=????????????????
Last set context:
rax=fffff8012b7e2300 rbx=0000000000000001 rcx=ffffd0012a86a6b0
rdx=0800000000000000 rsi=fffff8012b7e22a8 rdi=ffffd0012a86a6b0
rip=fffff8012b4c2d7a rsp=ffffd0012a86a650 rbp=ffffd0012a86a6d0
 r8=0000058000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000fffffffff
r14=0000000000000001 r15=000000000000000f
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff801`2b4c2d7a 48890a          mov     qword ptr [rdx],rcx ds:002b:08000000`00000000=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff801`2b4c2d7a 48890a          mov     qword ptr [rdx],rcx

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff801`2b4c2d7a 48890a          mov     qword ptr [rdx],rcx

BUGCHECK_STR:  0x34

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8012b639dbd to fffff8012b4c2d7a

STACK_TEXT:  
ffffd001`2a86a650 fffff801`2b639dbd : 00000000`00000001 00000000`00000000 00000000`00000000 fffff801`2b7e2288 : nt!KxWaitForLockOwnerShip+0x12
ffffd001`2a86a680 fffff801`2b5f913b : 00000000`00000001 fffff801`2b7e2300 00000000`00000000 ffffe001`4945a000 : nt! ?? ::FNODOBFM::`string'+0x4e4fd
ffffd001`2a86a710 fffff801`2b8263aa : 00000000`00000000 00000000`00000000 ffffe001`00000001 ffffe001`4945a000 : nt! ?? ::FNODOBFM::`string'+0xd87b
ffffd001`2a86a780 fffff801`2b90a8e5 : 00000000`00000000 ffffe001`460a0dc0 00000000`02b7f000 00000000`00000555 : nt!MiPfPrepareSequentialReadList+0x2ca
ffffd001`2a86a840 fffff801`2b4c3aee : 00000000`02b7f000 00000000`02b7f000 00000000`00000000 00000000`00000005 : nt!MmPrefetchForCacheManager+0x6d
ffffd001`2a86a8b0 fffff801`2b51c467 : 01d16b83`99ebf400 ffffe001`4a559690 01d16b83`99ebf400 ffffe001`4a559690 : nt!CcPerformReadAhead+0x2c6
ffffd001`2a86aa20 fffff801`2b53288f : ffffc001`8fb75000 ffffe001`49a31900 fffff801`2b76f7f0 00000000`00000000 : nt!CcWorkerThread+0x28b
ffffd001`2a86aad0 fffff801`2b588280 : 00000000`ca4ca000 ffffe001`49a31880 00000000`00000080 ffffe001`49a31880 : nt!ExpWorkerThread+0x69f
ffffd001`2a86ab80 fffff801`2b5e19c6 : fffff801`2b78a180 ffffe001`49a31880 fffff801`2b7e2a00 ffffe001`478f7290 : nt!PspSystemThreadStartup+0x58
ffffd001`2a86abe0 00000000`00000000 : ffffd001`2a86b000 ffffd001`2a864000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  569e61fd

STACK_COMMAND:  .cxr 0xffffd0012a869c20 ; kb

BUCKET_ID_FUNC_OFFSET:  12

FAILURE_BUCKET_ID:  0x34_nt!KxWaitForLockOwnerShip

BUCKET_ID:  0x34_nt!KxWaitForLockOwnerShip

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x34_nt!kxwaitforlockownership

FAILURE_ID_HASH:  {75ed37ef-4272-8978-0a35-6a11f2a16076}

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

Edited February 22, 2016 by TheDonkeyShow

[shadowbyte]

try using DDU (display driver uninstaller)

to completely remove your 290x drivers and reinstall them cleanly

 

I kept getting black screens on the desktop w/ my 290x, but DDU solved the issue

[TheDonkeyShow]

On 2/20/2016 at 8:47 PM, valdyrgramr said:

Do you have the 16.1 hotfix driver installed?  Any OCs?

I'll have to check to see if the 16.1 hotfix driver is installed. No OC.

[TheDonkeyShow]

On 2/20/2016 at 8:48 PM, shadowbyte said:

try using DDU (display driver uninstaller)

to completely remove your 290x drivers and reinstall them cleanly

 

I kept getting black screens on the desktop w/ my 290x, but DDU solved the issue

A couple months ago I did a clean install of Windows to see if that was the problem. Needless to say I had to reinstall them again. I still have the crashing problem.

 

[TheDonkeyShow]

On 2/20/2016 at 8:47 PM, valdyrgramr said:

Do you have the 16.1 hotfix driver installed?  Any OCs?

I installed the 16.1 hotfix. But I'm still getting crashes.