Question Why is my pc crashing when I benchmark my gpu?

OneShotRengo

Commendable
Apr 17, 2017
18
0
1,510
0
Hey guys, I've been having this problem for a while and still haven't really been able to find the cause. The first thing I thought could be causing it was my ram but I've tried reseating my ram a dozen times and it never worked. I've almost completely forgot about the fact that this has been going on. Before I would constantly blue screen but now it happens atleast 1 a week and I just ignore it. But it's starting to bother me again as to what could be causing it. Keep in mind I don't have my gpu overclocked. Below Is my pc specs and I also am including a minidump from when my pc rebooted. I don't know anything about stuff like this so any help would be greatly appreciated.

CPU: Intel Core i7-8700k (Not overclocked but do have mce enabled)
CPU Cooler: NZXT Kraken X72
Motherboard: Asus ROG MAXIMUS XI HERO (Wifi)
RAM: G.Skill Trident Z RGB 16 GB (2x8 GB) DDR4-3200 ( Not running any xmp profiles for the ram)
Storage: Corsair Force MP500 120GB M.2
SanDisk SSD Plus 1 TB 2.5"
GPU: Asus GeForce RTX 2060 6 GB Gaming OC
Case: NZXT H700i
PSU: Corsair RMx 750W

Here is what event viewer tells me when I look at the Error
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000061941, 0xffffa8844e92d3d8, 0x0000000000000009, 0xffffcc00c81e7060). A dump was saved in: C:\WINDOWS\Minidump\090919-8046-01.dmp. Report Id: 662a9740-21a5-4f0f-8a47-7b2cf93fd599.

And here is what the minidump says. I used a windows app called Windbg to view this. I am not sure what any of this really means but if someone does and could tell me what I need to do I would greatly appreciate it.

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


Loading Dump File [C:\WINDOWS\Minidump\090919-8046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff80722e00000 PsLoadedModuleList = 0xfffff80723246490
Debug session time: Mon Sep 9 10:22:01.682 2019 (UTC - 6:00)
System Uptime: 0 days 0:05:04.425
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80722fbfcc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcc00c81e6ec0=000000000000001a
4: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: ffffa8844e92d3d8
Arg3: 0000000000000009
Arg4: ffffcc00c81e7060

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1CBU1CD

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 10

Key : Analysis.Memory.CommitPeak.Mb
Value: 72

Key : Analysis.System
Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffffa8844e92d3d8

BUGCHECK_P3: 9

BUGCHECK_P4: ffffcc00c81e7060

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: cam_helper.exe

TRAP_FRAME: ffffcc00c81e7060 -- (.trap 0xffffcc00c81e7060)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa8844e92d3c0 rbx=0000000000000000 rcx=ffffa8844e92d3c8
rdx=ffffa884412f82f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80726eae934 rsp=ffffcc00c81e71f0 rbp=01d5672ab5f71efd
r8=0000000000000001 r9=7fffd6026fdb4868 r10=fffff80722e36d90
r11=ffffcc00c81e7180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
WdFilter+0x3e934:
fffff80726eae934 ?? ???
Resetting default scope

STACK_TEXT:
ffffcc00
c81e6eb8 fffff8072300c3e4 : 000000000000001a 0000000000061941 ffffa8844e92d3d8 0000000000000009 : nt!KeBugCheckEx
ffffcc00
c81e6ec0 fffff80722fcdd20 : 0000000000000000 fffff80722e47e43 ffffd6027264c2c8 ffffd6027193a080 : nt!MmAccessFault+0x199d54
ffffcc00
c81e7060 fffff80726eae934 : ffffd6027264c398 ffffd6025ec8c440 ffffcc00c81e72b8 fffff807264c7bd2 : nt!KiPageFault+0x360
ffffcc00
c81e71f0 ffffd6027264c398 : ffffd6025ec8c440 ffffcc00c81e72b8 fffff807264c7bd2 fffff80726e81000 : WdFilter+0x3e934
ffffcc00
c81e71f8 ffffd6025ec8c440 : ffffcc00c81e72b8 fffff807264c7bd2 fffff80726e81000 fffff80726eae7d1 : 0xffffd6027264c398
ffffcc00c81e7200 ffffcc00c81e72b8 : fffff807264c7bd2 fffff80726e81000 fffff80726eae7d1 ffffd6026c33c080 : 0xffffd6025ec8c440
ffffcc00
c81e7208 fffff807264c7bd2 : fffff80726e81000 fffff80726eae7d1 ffffd6026c33c080 ffffcc00c81e74c9 : 0xffffcc00c81e72b8
ffffcc00c81e7210 fffff80726e88709 : 0000000000000000 0000000000000001 0000000000000000 ffffd6026f249100 : FLTMGR!FltGetStreamContext+0x42
ffffcc00c81e7250 0000000000000000 : 0000000000000001 0000000000000000 ffffd6026f249100 ffffcc0000000001 : WdFilter+0x18709


SYMBOL_NAME: WdFilter+3e934

MODULE_NAME: WdFilter

IMAGE_NAME: WdFilter.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 3e934

FAILURE_BUCKET_ID: 0x1a_61941_WdFilter!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {67c3637b-d3ae-063d-4e92-5dd4d6770aa7}

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

ASK THE COMMUNITY