Question Random Crash and BSOD

[Frankenstein56]

Hello everyone, I need some help please,

Recently, I’ve been experiencing multiple crashes while playing games (the game just closes), sometimes BSOD doing nothing and everything (distorted image and other times with normal image), and errors when playing videos on YouTube in chrome and edge (status_access_violation).

My PC specs are:

CPU: AMD Ryzen 5 3600X 6-core
CPU cooler: AMD stock
Motherboard: TUF B450 Plus Gaming
Ram: 2 sticks x 16GB (NEW) Slot2 Slot4
G-Skill TridentZ DDR4 3200MHz CL16
CL16-18-18-38 1.35V
F4-3200C16D-32GTZRX
SSD/HDD:
GPU: AMD RX 5700 8GB
PSU: Kolink KL-1000M 1000W Modular 80PLUS Bronze (4~5 years)
Chassis: NOX Hummer ZX Black
OS: Windows 11 Home v10.026100
Monitor:
DP: OZONE DSP27 IPS 27" 2K QHD (OZDSP27IPS)
HDMI: 24” LG LED Full HD 144Hz 1ms (24GM79G-B)
BIOS: 4604 - 2024/04/08

Everything is running without overclocking.
I ran the memtest86 with no errors.
However, when running the FULL Prime95 test, I got the following errors in two consecutive tests on CPU core 2:

WORKER #2
[May 14 18:32] Worker starting
[May 14 18:32] Beginning a continuous torture test on your computer.
[May 14 18:32] Please read stress.txt. Choose Test/Stop to end this test.
[May 14 18:32] Test 1, 16000 Lucas-Lehmer iterations of M18474367 using FMA3 FFT length 960K, Pass1=768, Pass2=1280, clm=1, 2 threads.
[May 14 18:32] FATAL ERROR: Rounding was 0.814848755, expected less than 0.4
[May 14 18:32] Hardware failure detected running 960K FFT size, consult stress.txt file.
[May 14 18:32] Torture Test completed 0 tests in 0 minutes - 1 errors, 0 warnings.
[May 14 18:32] Worker stopped.

[May 14 18:41] Worker starting
[May 14 18:41] Beginning a continuous torture test on your computer.
[May 14 18:41] Please read stress.txt. Choose Test/Stop to end this test.
[May 14 18:41] Test 1, 16000 Lucas-Lehmer iterations of M18474367 using FMA3 FFT length 960K, Pass1=768, Pass2=1280, clm=1, 2 threads.
[May 14 18:41] FATAL ERROR: Rounding was 6.06774355e+10, expected less than 0.4
[May 14 18:41] Hardware failure detected running 960K FFT size, consult stress.txt file.
[May 14 18:41] Torture Test completed 0 tests in 0 minutes - 1 errors, 0 warnings.
[May 14 18:41] Worker stopped.

Then I ran the "Smallest FFTs" and "Small FFTs" tests without any errors — the processor reached 100% usage and stable 85°Celsius.

I suspect there may be an issue with the CPU, but since it's rare for a CPU to be damaged, I'm unsure of the next step.

Can you please help me?
Thank you.

 

[Lutfij]

Welcome to the forums, newcomer!

My PC specs are:
CPU: AMD Ryzen 5 3600X 6-core
Motherboard: TUF B450 Plus Gaming
Memory: G-Skill TridentZ DDR4 3200MHz CL16
2 sticks x 16GB
CL16-18-18-38 1.35V
F4-3200C16D-32GTZRX
Graphics card: AMD RX 5700 8GB
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

and errors when playing videos on YouTube (status_access_violation).
Using which browser? Chrome?

Pertaining to your BSoD, please pass on the .dmp files for us to take a look at them.

 

[Frankenstein56]

Welcome to the forums, newcomer!

My PC specs are:
CPU: AMD Ryzen 5 3600X 6-core
Motherboard: TUF B450 Plus Gaming
Memory: G-Skill TridentZ DDR4 3200MHz CL16
2 sticks x 16GB
CL16-18-18-38 1.35V
F4-3200C16D-32GTZRX
Graphics card: AMD RX 5700 8GB
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

and errors when playing videos on YouTube (status_access_violation).
Using which browser? Chrome?

Pertaining to your BSoD, please pass on the .dmp files for us to take a look at them.

Thanks for the answer.
I updated the original post with the info that was asked.

Below is the .dmp information from today.

 

[Frankenstein56]

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: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000006, 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: fffff807efe521a0, address which referenced memory

BUGCHECK_CODE: a
BUGCHECK_P1: 0
BUGCHECK_P2: ff
BUGCHECK_P3: 6
BUGCHECK_P4: fffff807efe521a0
FILE_IN_CAB: 051825-4234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump

FAULTING_THREAD: ffff898b476ce280

READ_ADDRESS: fffff807f09c34c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System

STACK_TEXT:
fffffc0a`49061428 fffff807`f00b8fe9 : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`00000006 : nt!KeBugCheckEx
fffffc0a`49061430 fffff807`f00b42a8 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffc0a`49061570 fffff807`efe521a0 : 00000000`00200001 ffffe701`8d08a180 ffff898b`4f29a000 ffffffff`ffffffff : nt!KiPageFault+0x468
fffffc0a`49061700 fffff807`efe508d1 : fffffc0a`49061be0 00000000`00000001 ffff898b`4f29a010 00000000`00000001 : nt!PpmEstimateIdleDuration+0x20c
fffffc0a`490618e0 fffff807`efe4fdf5 : ffff898b`4f29a010 ffff898b`4f29a010 ffffe701`8d08a180 00012c62`0b8febcb : nt!PpmIdleSelectStates+0x7a1
fffffc0a`49061b70 fffff807`f00a6044 : ffffe701`8d08a180 ffffe701`00000000 00000000`00000000 00000000`00000000 : nt!PoIdle+0x115
fffffc0a`49061c40 00000000`00000000 : fffffc0a`49062000 fffffc0a`4905c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!PpmEstimateIdleDuration+20c
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.26100.4061
STACK_COMMAND: .process /r /p 0xfffff807f09cdf80; .thread 0xffff898b476ce280 ; kb
BUCKET_ID_FUNC_OFFSET: 20c
FAILURE_BUCKET_ID: AV_CODE_AV_nt!PpmEstimateIdleDuration
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0458e2b3-8cd9-3b46-4e46-7bd1f7ae8a83}

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

 

[Frankenstein56]

Hello, anyone can please help me understand the DMP file error?
Thanks.

 

[johnbl]

put the actual dump file on a server, share it for public access and post a link.
if you have a memory.dmp file it will have better debug info and internal logs. (but it is a much bigger file)

 

[Frankenstein56]

put the actual dump file on a server, share it for public access and post a link.
if you have a memory.dmp file it will have better debug info and internal logs. (but it is a much bigger file)

Hello, thanks in advance.
I got a minidump and a complete memory dump, but the last one is 33gb and i think i cant upload it due its size.
What is the advice?

 

[Frankenstein56]

*******************************************************************************
* *
* 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: fffff804c285f092, Address of the instruction which caused the BugCheck
Arg3: ffff83005cf3a8d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2390

Key : Analysis.Elapsed.mSec
Value: 10687

Key : Analysis.IO.Other.Mb
Value: 2

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 19

Key : Analysis.Init.CPU.mSec
Value: 734

Key : Analysis.Init.Elapsed.mSec
Value: 15904

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

Key : Analysis.Version.DbgEng
Value: 10.0.27829.1001

Key : Analysis.Version.Description
Value: 10.2503.24.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2503.24.1

Key : Bugcheck.Code.KiBugCheckData
Value: 0x3b

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Bugcheck.Code.TargetModel
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 0x21000

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : Failure.Bucket
Value: AV_nt!KiComputeThreadQos

Key : Failure.Exception.IP.Address
Value: 0xfffff804c285f092

Key : Failure.Exception.IP.Module
Value: nt

Key : Failure.Exception.IP.Offset
Value: 0x25f092

Key : Failure.Hash
Value: {f8fb359d-e3f5-dbbb-8066-03431b5c9b83}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 0x1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0x0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: ge_release

Key : WER.OS.Version
Value: 10.0.26100.1


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff804c285f092

BUGCHECK_P3: ffff83005cf3a8d0

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x21000

FAULTING_THREAD: ffffcc86f89f6080

CONTEXT: ffff83005cf3a8d0 -- (.cxr 0xffff83005cf3a8d0)
rax=ffff9e1d8f834378 rbx=ffffcc86d86c9cf0 rcx=0004ecb90010000c
rdx=0000000000000000 rsi=ffffcc86e137f158 rdi=ffffcc86d86c9cf0
rip=fffff804c285f092 rsp=ffffe083797fe500 rbp=ffffe083797fe640
r8=0000000000000000 r9=ffffe083797fe5b8 r10=0000000000000000
r11=0000000000000000 r12=fffff804c35cff40 r13=ffff83005cf40180
r14=0000000000000001 r15=ffffcc86d86c9d18
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!KiComputeThreadQos+0x132:
fffff804`c285f092 0fb68104020000 movzx eax,byte ptr [rcx+204h] ds:002b:0004ecb9`00100210=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Last Epoch.exe

IP_IN_FREE_BLOCK: 0

STACK_TEXT:
ffffe083`797fe500 fffff804`c285fb6c : ffffe083`797fe640 00000000`00000000 fffff804`c3415500 00000000`00000000 : nt!KiComputeThreadQos+0x132
ffffe083`797fe540 fffff804`c2961991 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSearchForNewThreadsForRescheduleContext+0x5cc
ffffe083`797fe720 fffff804`c29608e6 : ffffe083`797fe849 00000000`00000000 ffffcc86`f1be2080 ffffcc86`f89f6b10 : nt!KiSearchForNewThread+0x261
ffffe083`797fe7e0 fffff804`c28e0171 : ffffcc86`f89f6080 ffff8300`5cf40180 ffffe083`797fe9c8 00000000`00000000 : nt!KiSwapThread+0x506
ffffe083`797fe8b0 fffff804`c28deff3 : ffffcc86`00000000 fffff804`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x271
ffffe083`797fe950 fffff804`c2e4abbf : ffffcc86`f60d3ee0 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x773
ffffe083`797fea40 fffff804`c2e4aaea : ffffcc86`f89f6080 00000000`ffffffff 00000000`00000000 00000013`fc664000 : nt!ObWaitForSingleObject+0xbf
ffffe083`797feaa0 fffff804`c2cb8658 : ffffcc86`f89f6080 00000013`fe1ff900 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
ffffe083`797feae0 00007ffa`e9481ff4 : 00007ffa`e6a8d1df 00000000`00000001 000001c7`200025b0 000001cc`0441cd10 : nt!KiSystemServiceCopyEnd+0x28
00000013`fe1ff858 00007ffa`e6a8d1df : 00000000`00000001 000001c7`200025b0 000001cc`0441cd10 00007ffa`99f0b628 : ntdll!NtWaitForSingleObject+0x14
00000013`fe1ff860 00007ffa`9a0d04d2 : 00000000`00000000 000001c7`200025b0 00000000`00000000 00000000`000005c4 : KERNELBASE!WaitForSingleObjectEx+0xaf
00000013`fe1ff900 00000000`00000000 : 000001c7`200025b0 00000000`00000000 00000000`000005c4 00000000`00000000 : UnityPlayer!UnityMain+0x9db722


SYMBOL_NAME: nt!KiComputeThreadQos+132

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr 0xffff83005cf3a8d0 ; kb

BUCKET_ID_FUNC_OFFSET: 132

FAILURE_BUCKET_ID: AV_nt!KiComputeThreadQos

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f8fb359d-e3f5-dbbb-8066-03431b5c9b83}

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

 

[Frankenstein56]

Link to the minidump:
052525-4671-01.zip

The text above is from the complete memory dump, and the file is from the minidump.

 

[Frankenstein56]

Did a driver verifier and the PC get stuck in boot loop always getting BSOD.
I ran a restore point and it boot to windows now.
This means that i have some bad driver?
Need help please.

 

[johnbl]

some driver corrupted driver memory and crashed a network function.
my guess would be this driver
C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys Thu Jun 9 00:43:50 2022

(Thaiphoon Burner ?)

I would download and install microsoft autoruns64, locate the driver and disable or remove it.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

i would also update the realtek network adapter for your motherboard.(rtcx21x64.sys Sun Oct 3 23:54:20 2021)

https://www.asus.com/motherboards-c...desk_download?model2Name=TUF-B450-PLUS-GAMING

new realtek driver is dated 3-10/2025

notes:
C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys Thu Jun 9 00:43:50 2022
rtcx21x64.sys Sun Oct 3 23:54:20 2021
CtiAIo64.sys Mon Jul 8 19:39:21 2024
IOMap64.sys Mon Dec 2 00:42:15 2024
AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024

: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3793
Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600X 6-Core Processor
3: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=2791]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends Inc.
BiosVersion = 4604
BiosReleaseDate = 03/22/2024
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = TUF B450-PLUS GAMING
BaseBoardVersion = Rev X.0x

 

[johnbl]

some driver corrupted driver memory and crashed a network function.
my guess would be this driver
C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys Thu Jun 9 00:43:50 2022

(Thaiphoon Burner ?)

I would download and install microsoft autoruns64, locate the driver and disable or remove it.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

i would also update the realtek network adapter for your motherboard.(rtcx21x64.sys Sun Oct 3 23:54:20 2021)

https://www.asus.com/motherboards-c...desk_download?model2Name=TUF-B450-PLUS-GAMING

new realtek driver is dated 3-10/2025

notes:
C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys Thu Jun 9 00:43:50 2022
rtcx21x64.sys Sun Oct 3 23:54:20 2021
CtiAIo64.sys Mon Jul 8 19:39:21 2024
IOMap64.sys Mon Dec 2 00:42:15 2024
AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024

: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3793
Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600X 6-Core Processor
3: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=2791]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends Inc.
BiosVersion = 4604
BiosReleaseDate = 03/22/2024
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = TUF B450-PLUS GAMING
BaseBoardVersion = Rev X.0x

the first time you run verifier it is a good idea to only run it for the next boot. you can do this by adding a command line switch /bootmode oneboot

so you would run cmd.exe as an admin then run
something like
verifier.exe /all /bootmode oneboot

this will boot, if the system crashes it will make the memory dump and verifier will be on turned on and you can reboot normally without having to try to get into safe mode and typing verifier.exe /reset

there are other boot mode settings that can be useful:
https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/verifier-command-line

note: the option to exclued drivers from being checked is also very useful. often verifier will just flag the first stupid driver and call a bugcheck but it will not be the driver that is causing your problems. So you can add
/driver.exclude DriverList
option to the verifier.exe command and it will not check the drivers you put in the list. It will allow you to check for other bad drivers without waiting for a fix for the first bad driver.