Question Random blue and black screen crashes while gaming since changing CPU ?

[sevack]

Hi everyone! I have recently replaced my ryzen 5 2600 with a ryzen 7 5800x. After the replacement I started getting blue screen crashes with KERNEL_DATA_INPAGE_ERROR or straight up black screen with no image with the pc rebooting afterwards (mostly while playing not very demanding games). The crashes happen randomly, sometimes 10 times a day, sometimes zero. Had no such problems with the old CPU so I think it has something to do with the new one. To clarify, the core temps are a bit higher than normal - up to around 70c in idle before I opened the case for airflow. Unforunately, no dumps were saved

SPECS
GPU inno3d rtx 2080 super
CPU ryzen 7 5800x stock
RAM corsair vengeance 2x8gb 3200 kit
MOTHERBOARD Gigabyte b450m
PSU bequiet system power 9 700w
CPU COOLER ID_COOLING se903xt 130w

If I forgot to add anything important please tell me. Asking for any ideas on how to diagnose or fix the issue

 

[Lutfij]

I have recently replaced my ryzen 5 2600 with a ryzen 7 5800x.
Did you update the BIOS on your motherboard to the latest prior to the CPU swap/upgrade? If you did verify that the BIOS was updated successfully, did you clear the CMOS after the update?

RAM corsair vengeance 2x9gb 3200 kit
You sure about that ram load out?

 

[sevack]

I have recently replaced my ryzen 5 2600 with a ryzen 7 5800x.
Did you update the BIOS on your motherboard to the latest prior to the CPU swap/upgrade? If you did verify that the BIOS was updated successfully, did you clear the CMOS after the update?

RAM corsair vengeance 2x9gb 3200 kit
You sure about that ram load out?

Thanks for the reply
Yeah I've updated the bios before swapping. Is CMOS the battery on the motherboard? Didn't touch it at all, did I need to? The memory config had a typo

 

[CelicaGT]

Thanks for the reply
Yeah I've updated the bios before swapping. Is CMOS the battery on the motherboard? Didn't touch it at all, did I need to? The memory config had a typo

Yes, there is a coin cell on the Motherboard. Remove and wait a few minutes before reinstalling, go into BIOS and reset to defaults (Not really necessary to do both but sometimes weird stuff happens). Make sure that you take note of any boot configuration, OC and or memory settings BEFORE you remove the battery as these will be lost. Taking a picture of each relevant screen with my phone is my preferred method.

 

[John Chesterfield]

Really important to do after a drop in AMD upgrade, update your AMD chipset drivers if you haven't done so already.

 

[John Chesterfield]

Also, it's possible a 130 watt air cooler isn't really sufficient for a Ryzen 5800x, which is a hot chip. Should be looking at a slightly better air cooler.

 

[sevack]

Random crashes after CPU upgrade

I have already posted a similar post (https://forums.tomshardware.com/thr...ing-since-changing-cpu.3803159/#post-22976503), but the crashes still persist, albeit differentely. PC now crashes randomly, although rarely, even with idle 40c CPU temperature.
What I have done:
reset and updated bios and amd drivers
ran chkdsk with no issues
ran ram checks with no issues
lowered CPU clock by 200 which drastically decreased temperatures and removed crashes for a few days altogether
put all my pc fans on 100 percent speed
reseated the cpu and applied new thermal paste
updated amd chipset drivers
checked system files with no issues
opened up the case for more airflow
SPECS
GPU inno3d rtx 2080 super
CPU ryzen 7 5800x stock
RAM corsair vengeance 2x8gb 3200 kit
MOTHERBOARD Gigabyte b450m
PSU bequiet system power 9 700w
CPU COOLER ID_COOLING se903xt 130w

The CPu temps under load now rarely rise above 75c so I think this is not related to overheating




I have managed to obtain 1 crash dump and analyzed it with Windbg (other crashes did not leave dumps)

Here is the result
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff968f95ae5080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000, The process object that initiated the termination.
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3811

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9192

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0xef

Key : Bugcheck.Code.Register
Value: 0xef

Key : CriticalProcessDied.ExceptionCode
Value: b76d6080

Key : CriticalProcessDied.Process
Value: svchost.exe

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 041523-39312-01.dmp

BUGCHECK_CODE: ef

BUGCHECK_P1: ffff968f95ae5080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

ERROR_CODE: (NTSTATUS) 0xb76d6080 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffbb8b`324978f8 fffff805`2530b102 : 00000000`000000ef ffff968f`95ae5080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbb8b`32497900 fffff805`252114c9 : 00000000`00000000 fffff805`24c55bdd 00000000`00000002 fffff805`24c5589b : nt!PspCatchCriticalBreak+0x10e
ffffbb8b`324979a0 fffff805`25050e80 : ffff968f`00000000 00000000`00000000 ffff968f`95ae5080 ffff968f`95ae54b8 : nt!PspTerminateAllThreads+0x1c05f9
ffffbb8b`32497a10 fffff805`25050c7c : ffff968f`95ae5080 00000000`00000000 000000cd`ac77f4bc fffff805`250fdf9a : nt!PspTerminateProcess+0xe0
ffffbb8b`32497a50 fffff805`24e0d8f8 : ffff968f`95ae5080 ffff968f`b76d6080 ffffbb8b`32497b40 ffff968f`95ae5080 : nt!NtTerminateProcess+0x9c
ffffbb8b`32497ac0 00007fff`71a4d644 : 00007fff`71ac3063 00007fff`71af7724 000000cd`ac77f480 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000cd`ac77c928 00007fff`71ac3063 : 00007fff`71af7724 000000cd`ac77f480 00000000`00000000 00007fff`719b0000 : 0x00007fff`71a4d644
000000cd`ac77c930 00007fff`71af7724 : 000000cd`ac77f480 00000000`00000000 00007fff`719b0000 00000000`00000004 : 0x00007fff`71ac3063
000000cd`ac77c938 000000cd`ac77f480 : 00000000`00000000 00007fff`719b0000 00000000`00000004 00007fff`71a5566d : 0x00007fff`71af7724
000000cd`ac77c940 00000000`00000000 : 00007fff`719b0000 00000000`00000004 00007fff`71a5566d 00007fff`71af7724 : 0x000000cd`ac77f480


SYMBOL_NAME: nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2728

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 10e

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_b76d6080_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3987b915-7796-1e4f-f815-38d165070aa6}

Followup: MachineOwner
---------
Thanks in advance to anyone answering