Keep getting BSOD. Updated drivers. Can't seem to figure it out. Can't read minidump, can someone help?

arktose

Honorable
Aug 19, 2012
7
0
10,510
I've been trying to solve my BSODs that've been happening for a while now. They all seem to be caused by either driver issues or bad hardware. I thought it was my ram at first, so i replaced my ram, but i still get the BSODs. It could be my GPU, but that's a costly replacement, and if I do it but still get BSODs I might go crazy.

I installed windebugging tool, but I can't seem to get the dang thing to read my minidump. Would someone be willing to read this for me and tell me what it says in regards to what's causing my crashes?

Thank you

Here is the dmp file


http://www.filedropper.com/090416-7796-01

 

arktose

Honorable
Aug 19, 2012
7
0
10,510
found a website to do it, but can't read it. Is this saying rzsynapse.exe caused the error?


Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.545.amd64fre.th2_release.160802-1857
Machine Name:
Kernel base = 0xfffff801`9a286000 PsLoadedModuleList = 0xfffff801`9a563cf0
Debug session time: Sun Sep 4 20:36:36.016 2016 (UTC - 4:00)
System Uptime: 0 days 0:25:06.680
*******************************************************************************
* *
* 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: fffff800f3b16e79, Address of the instruction which caused the bugcheck
Arg3: ffffd00022a8ccf0, 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

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

FAULTING_IP:
Wdf01000!FxPkgGeneral::Dispatch+3a309
fffff800`f3b16e79 4c394130 cmp qword ptr [rcx+30h],r8

CONTEXT: ffffd00022a8ccf0 -- (.cxr 0xffffd00022a8ccf0)
rax=ffffcf80432fcea0 rbx=ffffe000aafe6948 rcx=ff150801ff140801
rdx=ffffcf80432fcf48 rsi=ffffe000a91e05d0 rdi=ffffcf804331cea0
rip=fffff800f3b16e79 rsp=ffffd00022a8d710 rbp=ffffd00022a8d789
r8=ffffe000a754d820 r9=ffffe000aafe6680 r10=0000000000000540
r11=ffffcf804331cea0 r12=ffffe000a91e2ef0 r13=ffffe000a91e2e70
r14=ffffe000aafe65c0 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
Wdf01000!FxPkgGeneral::Dispatch+0x3a309:
fffff800`f3b16e79 4c394130 cmp qword ptr [rcx+30h],r8 ds:002b:ff150801`ff140831=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x3B

PROCESS_NAME: RzSynapse.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800f3ad11b1 to fffff800f3b16e79

STACK_TEXT:
ffffd000`22a8d710 fffff800`f3ad11b1 : ffffe000`ab69f400 ffffe000`ae13a400 ffffe000`a91e2c70 00000000`00000000 : Wdf01000!FxPkgGeneral::Dispatch+0x3a309
ffffd000`22a8d7f0 fffff801`9a937ebe : fffff801`9a744d60 ffffcf80`4331cea0 ffffe000`a91e2c70 ffffe000`a6078d98 : Wdf01000!FxDevice::DispatchWithLock+0x111
ffffd000`22a8d850 fffff801`9a351cd2 : ffffe000`a754d820 ffffe000`a91e2c70 00000000`00000000 ffffe000`ae13a460 : nt!IovCallDriver+0x252
ffffd000`22a8d890 fffff801`9a744d60 : ffffe000`a754d820 ffffe000`a91e2c70 00000000`00000000 00000000`008be8d0 : nt!IofCallDriver+0x72
ffffd000`22a8d8d0 fffff801`9a732d25 : 00000000`00000001 00000000`00000000 00000000`00000001 ffffe000`00000001 : nt!IopCloseFile+0x150
ffffd000`22a8d960 fffff801`9a6beced : ffffe000`ab6a2080 ffffd000`22a8db80 00000000`008be8d0 00000000`88883004 : nt!ObCloseHandleTableEntry+0x595
ffffd000`22a8daa0 fffff801`9a3d31a3 : ffffe000`ab6a2080 00000000`55bf7df0 ffffe000`ab6a2080 ffffd000`22a8db80 : nt!NtClose+0xcd
ffffd000`22a8db00 00000000`55be21bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`008be878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x55be21bc


FOLLOWUP_IP:
Wdf01000!FxPkgGeneral::Dispatch+3a309
fffff800`f3b16e79 4c394130 cmp qword ptr [rcx+30h],r8

FAULTING_SOURCE_LINE: d:\th\minkernel\wdf\framework\shared\irphandlers\general\fxpkggeneral.cpp

FAULTING_SOURCE_FILE: d:\th\minkernel\wdf\framework\shared\irphandlers\general\fxpkggeneral.cpp

FAULTING_SOURCE_LINE_NUMBER: 793

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Wdf01000!FxPkgGeneral::Dispatch+3a309

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d4db

STACK_COMMAND: .cxr 0xffffd00022a8ccf0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_VRF_Wdf01000!FxPkgGeneral::Dispatch+3a309

BUCKET_ID: X64_0x3B_VRF_Wdf01000!FxPkgGeneral::Dispatch+3a309

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