[SOLVED] Getting BSOD on my PC

[M157ERA]

Hey there, new to PC building but wanted to build me own PC more for the experience than anything.

PC specs are:
B450 Steel legend ASRock Mobo
Ryzen 2700 CPU
Vengence Pro 3200 memory
Radeon RX5700
Thermaltake 700w PSU
Intel M.2 SSD

Anyway I built my PC and it was running fine, playing a few games here and there and randomly when my son was playing a game he got a blue screen. This has happened a couple more times since.

I managed to get the bug report after following how tos online. The information is below. Any help would be great.



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


Loading Dump File [C:\Windows\minidump\111019-6828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff80138000000 PsLoadedModuleList = 0xfffff801384480b0
Debug session time: Sun Nov 10 01:45:33.558 2019 (UTC + 0:00)
System Uptime: 1 days 7:31:19.545
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801381c1410 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb5025ec21f60=000000000000000a
7: 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: ffffb5025fc222d0, memory referenced
Arg2: 0000000000000002, 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: fffff801380d949b, address which referenced memory

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

*** WARNING: Unable to verify timestamp for Ntfs.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 5

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 6

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: a

BUGCHECK_P1: ffffb5025fc222d0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801380d949b

READ_ADDRESS: fffff801385733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8013842a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8013842a3d8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffb5025fc222d0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

TRAP_FRAME: ffffb5025ec220a0 -- (.trap 0xffffb5025ec220a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000e rbx=0000000000000000 rcx=000000000000000e
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801380d949b rsp=ffffb5025ec22230 rbp=ffff988093e00180
r8=0000000000000000 r9=0000000000000000 r10=000000000000000e
r11=ffffb5025ec22338 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeSetEventBoostPriorityEx+0x18f:
fffff801380d949b 0fb68424a0000001 movzx eax,byte ptr [rsp+10000A0h] ss:0018:ffffb5025fc222d0=??
Resetting default scope

STACK_TEXT:
ffffb5025ec21f58 fffff801381d32e9 : 000000000000000a ffffb5025fc222d0 0000000000000002 0000000000000000 : nt!KeBugCheckEx
ffffb5025ec21f60 fffff801381cf62b : 0000010001000000 fffff801010e7700 0000000000000000 ffffc20476893200 : nt!KiBugCheckDispatch+0x69
ffffb5025ec220a0 fffff801380d949b : ffffe60d3dacf700 0000000000000000 ffff988000000000 ffffb5025ecbe340 : nt!KiPageFault+0x46b
ffffb5025ec22230 fffff801380fad55 : ffffe60d00000000 0000000000000000 ffffb5025ec222e8 0000000000000000 : nt!KeSetEventBoostPriorityEx+0x18f
ffffb5025ec222b0 fffff80139cd9ca4 : ffffb50200000000 ffffc20479084790 ffffb5020000000e 0000000000000000 : nt!FsRtlReleaseEofLock+0x315
ffffb5025ec22340 ffffb50200000000 : ffffc20479084790 ffffb5020000000e 0000000000000000 ffffe60d40aa6dd0 : Ntfs+0x19ca4
ffffb5025ec22348 ffffc20479084790 : ffffb5020000000e 0000000000000000 ffffe60d40aa6dd0 ffffb5025ec22810 : 0xffffb50200000000 ffffb5025ec22350 ffffb5020000000e : 0000000000000000 ffffe60d40aa6dd0 ffffb5025ec22810 0000000000000000 : 0xffffc20479084790
ffffb5025ec22358 0000000000000000 : ffffe60d40aa6dd0 ffffb5025ec22810 0000000000000000 0000000000000001 : 0xffffb5020000000e CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff801380d94a2 - nt!KeSetEventBoostPriorityEx+196 [ 00:01 ] 1 error : !nt (fffff801380d94a2) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption MEMORY_CORRUPTOR: ONE_BIT STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7} Followup: memory_corruption --------- 7: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* 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: ffffb5025fc222d0, memory referenced Arg2: 0000000000000002, 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: fffff801380d949b, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-EAQFKSI Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 4 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: a BUGCHECK_P1: ffffb5025fc222d0 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff801380d949b READ_ADDRESS: Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff8013842a3d8: Unable to get Flags value from nt!KdVersionBlock ffffb5025fc222d0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe TRAP_FRAME: ffffb5025ec220a0 -- (.trap 0xffffb5025ec220a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000000e rbx=0000000000000000 rcx=000000000000000e rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff801380d949b rsp=ffffb5025ec22230 rbp=ffff988093e00180 r8=0000000000000000 r9=0000000000000000 r10=000000000000000e r11=ffffb5025ec22338 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeSetEventBoostPriorityEx+0x18f: fffff801380d949b 0fb68424a0000001 movzx eax,byte ptr [rsp+10000A0h] ss:0018:ffffb5025fc222d0=?? Resetting default scope STACK_TEXT: ffffb5025ec21f58 fffff801381d32e9 : 000000000000000a ffffb5025fc222d0 0000000000000002 0000000000000000 : nt!KeBugCheckEx ffffb5025ec21f60 fffff801381cf62b : 0000010001000000 fffff801010e7700 0000000000000000 ffffc20476893200 : nt!KiBugCheckDispatch+0x69 ffffb5025ec220a0 fffff801380d949b : ffffe60d3dacf700 0000000000000000 ffff988000000000 ffffb5025ecbe340 : nt!KiPageFault+0x46b ffffb5025ec22230 fffff801380fad55 : ffffe60d00000000 0000000000000000 ffffb5025ec222e8 0000000000000000 : nt!KeSetEventBoostPriorityEx+0x18f ffffb5025ec222b0 fffff80139cd9ca4 : ffffb50200000000 ffffc20479084790 ffffb5020000000e 0000000000000000 : nt!FsRtlReleaseEofLock+0x315 ffffb5025ec22340 ffffb50200000000 : ffffc20479084790 ffffb5020000000e 0000000000000000 ffffe60d40aa6dd0 : Ntfs+0x19ca4 ffffb5025ec22348 ffffc20479084790 : ffffb5020000000e 0000000000000000 ffffe60d40aa6dd0 ffffb5025ec22810 : 0xffffb50200000000
ffffb5025ec22350 ffffb5020000000e : 0000000000000000 ffffe60d40aa6dd0 ffffb5025ec22810 0000000000000000 : 0xffffc20479084790 ffffb5025ec22358 0000000000000000 : ffffe60d40aa6dd0 ffffb5025ec22810 0000000000000000 0000000000000001 : 0xffffb5020000000e


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff801380d94a2 - nt!KeSetEventBoostPriorityEx+196
[ 00:01 ]
1 error : !nt (fffff801380d94a2)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------

Thanks again if anyone can help
Andy

 

[wpgwpg]

As the report says, " This is usually caused by drivers using improper addresses". So right-click the START button, and click Device Manager. Then look for any device having ! or ? next to it. This would be the device needing the correct driver. You can download the driver from your manufacturer.

 

[Ketchup79]

Start with getting the latest driver for your Radeon.

 

[M157ERA]

Thanks for replies there is no device showing up with ! or ? but I have downloaded latest drivers from Radeon and All in One driver from AS Rock. Will monitor it and see how it goes

 

[Colif]

did you run asrock app shop? it would confirm you have latest drivers - https://www.asrock.com/mb/AMD/B450 Steel Legend/index.asp#Download

error blaming ntfs.sys which is the windows file system. Not exactly helpful.

Can you follow option one on the following link - 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 file sharing web site, and share the link in your thread so we can help fix the problem

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.