Constant BSOD while gaming.

[rg2007]

I've checked everywhere to see if anyone had the same issue as mine and haven't found a thread. I greatly appreciate the help. Been wanting to tear my hair out trying to figure this out.

So ever since I started playing Fortnite at random times I would get constant BSOD's. Different ones. From the passed 4 days I have about 7 minidumps saved on my desktop. I can browse and play WoW with no problem. The problem only occurs when I play fortnite.
Also my ram is running 668mhz. I dont know if this is normal. I tried going into the bios and changing them.


OS : Windows 10
CPU : AMD Phenom II X6 1100T Thuban 45nm Technology
Ram : PNY Anarchy DDR3 16gb 1866
Mobo : ASRock 880GXH/USB3 (CPUSocket)
GPU : NVIDIA GeForce GTX 1050 Ti 4GB XLR8
HDD : 465GB Seagate ST3500418AS ATA Device (SATA)





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


Loading Dump File [C:\Users\Roy Garcia\Desktop\040918-34343-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 16299 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`bb40a000 PsLoadedModuleList = 0xfffff800`bb771130
Debug session time: Mon Apr 9 21:34:44.354 2018 (UTC - 7:00)
System Uptime: 0 days 0:26:47.078
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff800bc448146, ff, 0, fffff800bb454ab7}

Probably caused by : ntkrnlmp.exe ( nt!ExReleaseResourceLite+57 )

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

nt!KeBugCheckEx:
fffff800`bb57f510 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb004`f0bcce10=000000000000000a
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff800bc448146, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800bb454ab7, address which referenced memory

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.309 (WinBuild.160101.0800)

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.20

BIOS_DATE: 06/24/2010

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: 880GXH/USB3

BASEBOARD_VERSION:

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: fffff800bc448146

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff800bb454ab7

READ_ADDRESS: fffff800bb807380: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff800bc448146

CURRENT_IRQL: 0

FAULTING_IP:
nt!ExReleaseResourceLite+57
fffff800`bb454ab7 0fb60588363b00 movzx eax,byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff800`bb808146)]

CPU_COUNT: 6

CPU_MHZ: cea

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 10

CPU_MODEL: a

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: WmiPrvSE.exe

ANALYSIS_SESSION_HOST: RG

ANALYSIS_SESSION_TIME: 04-09-2018 22:08:12.0776

ANALYSIS_VERSION: 10.0.17074.1002 amd64fre

TRAP_FRAME: ffffb004f0bccf50 -- (.trap 0xffffb004f0bccf50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd90a2a8edff0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800bb454ab7 rsp=ffffb004f0bcd0e0 rbp=ffffb004f0bcdc01
r8=0000000000000001 r9=000000000000001c r10=7ffffffffffffffc
r11=ffffb004f0bcd110 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!ExReleaseResourceLite+0x57:
fffff800`bb454ab7 0fb60588363b00 movzx eax,byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff800`bb808146)] ds:fffff800`bb808146=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800bb592529 to fffff800bb57f510

STACK_TEXT:
ffffb004`f0bcce08 fffff800`bb592529 : 00000000`0000000a fffff800`bc448146 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffb004`f0bcce10 fffff800`bb58e659 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb004`f0bccf50 fffff800`bb454ab7 : ffffb38f`8fe98480 ffffd90a`2c2134c0 ffffb004`f0bcdcc0 fffff800`bb8a3b90 : nt!KiPageFault+0x519
ffffb004`f0bcd0e0 fffff800`bb4275c6 : ffffb38f`8fe73060 ffffd90a`2a8edf02 ffffb38f`8fe9b400 ffffd90a`2c213818 : nt!ExReleaseResourceLite+0x57
ffffb004`f0bcd140 fffff800`bb90094c : 000002bf`c5753580 fffff800`bbb925e8 00000000`00000000 000002bf`c5753410 : nt!SeSecurityAttributePresent+0x106
ffffb004`f0bcd1a0 fffff800`bb8f0800 : ffffa300`00000000 ffffa301`00018000 00000000`00000001 00000000`00000000 : nt!ExpGetProcessInformation+0x7dc
ffffb004`f0bcd7c0 fffff800`bb8ef9eb : 00000000`00000000 000002bf`c5736df0 000002bf`c4f40000 00000000`00000377 : nt!ExpQuerySystemInformation+0xd00
ffffb004`f0bcdc00 fffff800`bb592003 : ffffd90a`2ccda340 000002bf`c5714640 ffffd90a`2ccda340 000002bf`c5719c90 : nt!NtQuerySystemInformation+0x2b
ffffb004`f0bcdc40 00007ff8`7b570544 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000f1`4f2fd418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`7b570544


THREAD_SHA1_HASH_MOD_FUNC: 2e64ad086b041861fae24bf7495d8df6a4e5f27b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1b536c20c008b9aadab8039be39c69ae7e2170df

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!ExReleaseResourceLite+57
fffff800`bb454ab7 0fb60588363b00 movzx eax,byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff800`bb808146)]

FAULT_INSTR_CODE: 8805b60f

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ExReleaseResourceLite+57

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5a979177

IMAGE_VERSION: 10.0.16299.309

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 57

FAILURE_BUCKET_ID: AV_nt!ExReleaseResourceLite

BUCKET_ID: AV_nt!ExReleaseResourceLite

PRIMARY_PROBLEM_CLASS: AV_nt!ExReleaseResourceLite

TARGET_TIME: 2018-04-10T04:34:44.000Z

OSBUILD: 16299

OSSERVICEPACK: 309

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-02-28 21:36:55

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.309

ANALYSIS_SESSION_ELAPSED_TIME: 71d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!exreleaseresourcelite

FAILURE_ID_HASH: {d53d9298-73cb-08e9-5850-7f2339d4491f}

Followup: MachineOwner

 

[Colif]

the driver it is blaming is part of the windows kernel and not going to be the cause.

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it