BSOD :( Memory Corruption or Bad driver?! Please help :)

schnub

Commendable
Oct 19, 2016
2
0
1,510
Hello Guys,

i got some bluescreens randomly around the day while playing.

system setup:

board: asus m5A99FX PRO R2.0 990FX
cpu: amd fx 8350
gfx: EVGA 1070 SC
RAM: 8gb Kingston Hyper X Blu DDR3

I switched the ram to a known as fully working ram.

now i think its a driver problem..

i got the dumps uploaded here :

https://1drv.ms/f/s!AoyEAXTcymnve3SBbCyxbY8uMaw

I also got an online check of 1 minidump. but it says nothing other than memory corruption.

C++:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See [url=http://www.osronline.com]http://www.osronline.com[/url] for more information
Windows 8 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
Machine Name:
Kernel base = 0xfffff801`fb415000 PsLoadedModuleList = 0xfffff801`fb719080
Debug session time: Wed Oct 19 12:06:22.885 2016 (UTC - 4:00)
System Uptime: 0 days 0:11:13.588
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801fb49d914, Address of the instruction which caused the bugcheck
Arg3: ffff88013464d3b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

OVERLAPPED_MODULE: Address regions for 'mrxsmb' and 'dump_storpor' overlap

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

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+14
fffff801`fb49d914 48890a          mov     qword ptr [rdx],rcx

CONTEXT:  ffff88013464d3b0 -- (.cxr 0xffff88013464d3b0)
rax=ffff9c8000000500 rbx=0000000000000000 rcx=ffff88013464de70
rdx=0408000000000000 rsi=fffff801fb738400 rdi=ffff88013464de70
rip=fffff801fb49d914 rsp=ffff88013464ddc0 rbp=ffff88013464de40
 r8=ffff998005f2d428  r9=0000000000000005 r10=0000000000000001
r11=fffff801fb736130 r12=ffff9c8000000e00 r13=0000000000000001
r14=00000000001fb9c5 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!KxWaitForLockOwnerShip+0x14:
fffff801`fb49d914 48890a          mov     qword ptr [rdx],rcx ds:002b:04080000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  bf1.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff801fb4c0db8 to fffff801fb49d914

STACK_TEXT:  
ffff8801`3464ddc0 fffff801`fb4c0db8 : ffff9980`05f2d4f0 ffff9980`000003ff 0000000f`00000001 ffff9980`05f2d400 : nt!KxWaitForLockOwnerShip+0x14
ffff8801`3464ddf0 fffff801`fb4bff68 : 00000000`05f2d4f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiInsertPageInFreeOrZeroedList+0x618
ffff8801`3464df00 fffff801`fb4ad6a0 : 00000000`00000000 ffff8801`3464e0f0 00000000`00000001 fffff080`00d64f60 : nt!MiPfnShareCountIsZero+0xd8
ffff8801`3464df40 fffff801`fb48c333 : 00000000`0000001f ffffb802`fa24f640 00000000`00000200 ffff8801`3464e9b0 : nt!MiDeletePteList+0x1b0
ffff8801`3464e010 fffff801`fb89c89e : ffffb802`00000010 ffffb802`fa24f640 ffffb802`f94c1b90 00000000`00000103 : nt!MiDecommitPages+0xd63
ffff8801`3464e970 fffff801`fb8cf442 : 00000000`00000000 ffff8801`3464eb80 00000001`ac6d1000 00000000`00000003 : nt!MiDecommitRegion+0x6e
ffff8801`3464e9e0 fffff801`fb569f93 : ffffb802`f60d4800 ffffb802`fbdc6800 00000000`00000000 ffffb802`fb16fe20 : nt!NtFreeVirtualMemory+0x252
ffff8801`3464eb00 00007ffb`81685214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`660fdab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffb`81685214


MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffff88013464d3b0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption

it would be very kind if someone find out wich driver causes that issue?

Thank you guys so much for the help!

PS: if you need more info, feel free to ask me.

 

schnub

Commendable
Oct 19, 2016
2
0
1,510
Code:
On Wed 19.10.2016 18:06:22 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101916-6296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801FB49D914, 0xFFFF88013464D3B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Wed 19.10.2016 13:52:01 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101916-6781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD6002) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8028F15B002, 0xFFFFD10078462838, 0xFFFFD10078462060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.