Question PC keeps crashing to a green screen and sometimes a BSOD ?

[cgrimm76]

compter specs
CPU: Ryzen3700x
CPU cooler: stock
Motherboard: asrock b550m pro4
Ram: jigsaw 3200 32 gb 8x4
SSD/HDD:m2 1 tb
GPU: radeon asrock rx 6950xt phantom gaming
PSU: NZXT C850 FM 80+G ATX 800 watts gold
Chassis:
OS:windows 10 pro
Monitor:acer predator

i keep crashing computer shows a green screen then restarts once in a while i get a bsod.i thought i had it figured out when i tested the ram in a test had bad sectors replaced the ram had to reinstall windows due tothe computer cpu running at high % anyways new ram and fresh install of windows lasted 4 days now getting these crashes when i try to play a game of warzone. got a bsod once when i trried to start windows.
i get errors in the log files that say simular to this it was doing tis in windows 11 and windows 10

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 3

The details view of this entry contains further information.
and a bunch of these errors
The AMDRyzenMasterDriverV22 service failed to start due to the following error:
Cannot create a file when that file already exists.
and here is the dump file for the bsod

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff800`63000000 PsLoadedModuleList = 0xfffff800`63c2a770
Debug session time: Wed Mar 13 07:20:34.816 2024 (UTC - 5:00)
System Uptime: 0 days 9:20:01.443
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`633fd5b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8002`fcb02550=0000000000000050

any help would be greatly appreciated

 

[Lutfij]

Welcome to the forums, newcomer!

PSU: 800 watts gold
800W is the advertised wattage of the unit. What is the make and model of the unit and it's age?

Motherboard: asrock b550 pro4
BIOS version for your motherboard?

fresh install of windows lasted 4 days
Where did you source the installer for your OS? Did you recreate it to rule out a corrupt installer? You're advised to install the OS in offline mode. Then manually install the latest drivers in an elevated command, i.e, Right click installer>Run as Administrator.

 

[cgrimm76]

hello thanks for the reply here to answer your questions

psu is a NZXT C850 FM 80+G ATX PSU I did see that the psu Supports NVIDIA GPUs up to 3090 and AMD GPUs up to RX 6900 XT i have the rx 6950xt I would not think that would be a problem

motherboard bios version is l2.71 its actually a asrock b550m pro4 mistyped
OS was downloaded from microsoft i did not reinstall windows to fix this problem i was forced to reinstall due to when i replaced my ram sticks the computer became very slow on which i tried to reset the bios that did not work. so when i reinstalled windows it fixed that issue.

so basically its doing the same thing it did before i installed the ram before the os install. the error codes are there the
The AMDRyzenMasterDriverV22 service failed to start due to the following error:
Cannot create a file when that file already exists. was there i tried deleting the gpu drivers and reinstalling but amd only gets me the latest drivers for this card.

 

[cgrimm76]

sorry here is a more detailed dump.file

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`57e00000 PsLoadedModuleList = 0xfffff807`58a2a730
Debug session time: Thu Mar 14 22:03:55.280 2024 (UTC - 5:00)
System Uptime: 0 days 2:19:47.906
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols

Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`581fd890 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffde82`98299550=0000000000000050
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffc2091d06, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: ffffc6f8a422fd61, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Write

Key : Analysis.CPU.mSec
Value: 4061

Key : Analysis.Elapsed.mSec
Value: 4155

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

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

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

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x50

Key : Bugcheck.Code.LegacyAPI
Value: 0x50

Key : Bugcheck.Code.TargetModel
Value: 0x50

Key : Failure.Bucket
Value: AV_W_(null)_win32kbase!SURFACE::bDeleteSurface

Key : Failure.Hash
Value: {f8b3c92a-57bc-4949-7d55-15dd4028f835}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

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: 1020000

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: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 50

BUGCHECK_P1: ffffffffc2091d06

BUGCHECK_P2: 2

BUGCHECK_P3: ffffc6f8a422fd61

BUGCHECK_P4: 2

FILE_IN_CAB: MEMORY.DMP

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
ffffffffc2091d06

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: ffffde82982997f0 -- (.trap 0xffffde82982997f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=ffffc6f8a422fd61 rsp=ffffde8298299980 rbp=0000000000000080
r8=0000000000000020 r9=0000000000000001 r10=0000000000000000
r11=fffff80757e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
Page 8090e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 8090e1 not present in the dump file. Type ".hh dbgerr004" for details
ffffc6f8`a422fd61 ?? ???
Resetting default scope

STACK_TEXT:
ffffde82`98299548 fffff807`5823bf7d : 00000000`00000050 ffffffff`c2091d06 00000000`00000002 ffffde82`982997f0 : nt!KeBugCheckEx
ffffde82`98299550 fffff807`58024660 : 00000000`00000000 00000000`00000002 ffffde82`98299870 00000000`00000000 : nt!MiSystemFault+0x1d8afd
ffffde82`98299650 fffff807`5820d798 : 00000000`00000000 fffff807`535fe7e0 fffff807`535faac0 00000000`00000000 : nt!MmAccessFault+0x400
ffffde82`982997f0 ffffc6f8`a422fd61 : 00000000`0000006c ffffe206`000000f0 ffffe206`56669500 ffffe206`00000002 : nt!KiPageFault+0x358
ffffde82`98299980 00000000`0000006c : ffffe206`000000f0 ffffe206`56669500 ffffe206`00000002 ffffde82`00000001 : 0xffffc6f8`a422fd61
ffffde82`98299988 ffffe206`000000f0 : ffffe206`56669500 ffffe206`00000002 ffffde82`00000001 fffffeb6`c3e0b9a5 : 0x6c
ffffde82`98299990 ffffe206`56669500 : ffffe206`00000002 ffffde82`00000001 fffffeb6`c3e0b9a5 01000101`00910018 : 0xffffe206`000000f0
ffffde82`98299998 ffffe206`00000002 : ffffde82`00000001 fffffeb6`c3e0b9a5 01000101`00910018 ffffe206`5b0256d0 : 0xffffe206`56669500
ffffde82`982999a0 ffffde82`00000001 : fffffeb6`c3e0b9a5 01000101`00910018 ffffe206`5b0256d0 0002cc88`00910009 : 0xffffe206`00000002
ffffde82`982999a8 fffffeb6`c3e0b9a5 : 01000101`00910018 ffffe206`5b0256d0 0002cc88`00910009 ffffe206`42524000 : 0xffffde82`00000001
ffffde82`982999b0 ffffc6f8`a3200000 : 00000008`261ec000 00000008`261ec000 00000000`00000000 00000000`00e62000 : win32kbase!SURFACE::bDeleteSurface+0x785
ffffde82`98299b70 00000008`261ec000 : 00000008`261ec000 00000000`00000000 00000000`00e62000 ffffe206`425f56e0 : 0xffffc6f8`a3200000
ffffde82`98299b78 00000008`261ec000 : 00000000`00000000 00000000`00e62000 ffffe206`425f56e0 00000000`0002cc88 : 0x00000008`261ec000
ffffde82`98299b80 00000000`00000000 : 00000000`00e62000 ffffe206`425f56e0 00000000`0002cc88 00000000`0002cc88 : 0x00000008`261ec000


SYMBOL_NAME: win32kbase!SURFACE::bDeleteSurface+785

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 785

FAILURE_BUCKET_ID: AV_W_(null)_win32kbase!SURFACE::bDeleteSurface

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f8b3c92a-57bc-4949-7d55-15dd4028f835}

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

 

[ubuysa]

Please upload all the dumps you have to a cloud service with a link to them here. It's clear from the analyze -v output above that you don't have the correct symbols loaded. In any case, dump analysis is way more involved than just analyze -v.

 

[cgrimm76]

https://drive.google.com/file/d/1EEgumnJV4A6eSNwhbxiyctmJlWMJ8HsV/view?usp=drive_link
here are my min dump files two of them in zip format

 

[ubuysa]

Thanks. These two dumps are almost identical, both fail in more or less the same place and for the same reason: a garbage memory address was referenced...

TRAP_FRAME:  ffffde82982997f0 -- (.trap 0xffffde82982997f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=ffffc6f8a422fd61 rsp=ffffde8298299980 rbp=0000000000000080
 r8=0000000000000020  r9=0000000000000001 r10=0000000000000000
r11=fffff80757e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ffffc6f8`a422fd61 ??              ???
Resetting default scope

You can see that the instruction pointer address (in the RIP register) is pointing at an invalid address (note the ?? ??? at the bottom). The problem here then was a bad instruction pointer, so a jump or a call was made to an address that doesn't exist. That could be a rogue driver, although no third-party drivers appear to have been involved, or it could ba a hardware problem (bad RAM or even a bad CPU).

The System log error you posted is concerning...

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 3
The details view of this entry contains further information.

You said that you see many of these errors, is it always APIC ID: 3 or does the number vary? If it's always 3 then that might point strongly at a CPU issue, but if the id (that's the processor core number) varies then it's probably more likely RAM.

Because of those errors , and what's in the dumps, I think you'd be best off testing hardware first, the best way to do that is to run Prime95...

1. Download Prime95 and a temperature monitor of your choice (CoreTemp is fine for this)
2. Run the temperature monitor all the time that Prime95 is active because your CPU will run hot.
3. Run all three Prime95 tests (small FFTs, large FFts, and Blend) one after the other. Run each test for at least an hour, two hours if you can.
4. If Prime95 generates error messages, if the system BSODs/crashes/freezes, or if the CPU temp approaches 95°C (Tmax for your 3700X is 95°C) then stop Prime95 and let us know what happened.

A stable and well-cooled CPU should be able to run Prime95 pretty much indefinitely. This test stresses both CPU and RAM, some tests stress RAM more than others, so this will give you a good indication of whether hardware is the problem here.

 

[cgrimm76]

well i ran that for 4 hours and had no issues happened while running prime95 its funny most of the time it happens exact same time when i play the warzone. today I just updated my bios since i seen people have simular issues when they having the same symtoms but with different programs saying updated there bios fixed it. I boughts a ryzen 7 5800xsd processor wanted to upgrade anyways I see if this works

 

[cgrimm76]

so i got a new pcu i took the whole computer apart moved everything into a different case. made sure all the plug ins where connected properly.i did have another crash with the processor core code 12 the crash happened in a different spot this time. im lost updated bios new provessor new ram only thing i have left is gpu or motherboard.

 

[ubuysa]

Are the CPU and RAM are on the QVL for the motherboard? In other words are the compatible with the board. The CPU may be but is the RAM?

What PSU do you have?