Need help with BSOD - multiple different errors.

Anonymous

Hello,

A year and a while back my laptop began to crash once a day, and all of a sudden began crashing 2-3 times a day, later on it became hysterical from every 2 hours to 30 mins.

Problem is I keep getting different errors everytime. I sent it to some professionals here in Egypt, their final analysis is the motherboard is bad, which I don't believe tbh.

Now I tried to fix it with another shop who could not really fix it yet, we are in the testing phase. However I started troubleshooting on my own. Sometimes I would think I got the fix and others not. I regret buying a laptop with Ryzen processor, I feel the AMD is the issue here.

MY PC:

Processor AMD Ryzen 7 4800H with Radeon Graphics 2.90 GHz

Installed RAM 16.0 GB (15.4 GB usable)

Device ID B35B1B55-6E7B-4EA1-9B90-CF367E437104

Product ID 00327-30926-80177-AAOEM

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

However I want help to fix this. Currently From the last crash I got the following DUMP:

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

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

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

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

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

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

Loading Dump File [C:\Windows\Minidump\051925-12625-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff804`0e800000 PsLoadedModuleList = 0xfffff804`0f413510
Debug session time: Mon May 19 23:02:42.571 2025 (UTC + 3:00)
System Uptime: 0 days 0:24:36.381
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000cd`b8eff018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`0ec17ba0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc201`4da67ed0=0000000000000139
4: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000cd`b8eff018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: ffffc2014da681f0, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffc2014da68148, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3109

    Key  : Analysis.Elapsed.mSec
    Value: 8540

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

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

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

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

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

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

    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.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : FailFast.Name
    Value: STACK_COOKIE_CHECK_FAILURE

    Key  : FailFast.Type
    Value: 2

    Key  : Failure.Bucket
    Value: 0x139_MISSING_GSFRAME_dxgkrnl!_report_gsfailure

    Key  : Failure.Exception.Code
    Value: 0xc0000409

    Key  : Failure.Exception.Record
    Value: 0xffffc2014da68148

    Key  : Failure.Hash
    Value: {1685fa82-f4b9-d129-b6b1-78c3bba339a9}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

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

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: ffffc2014da681f0

BUGCHECK_P3: ffffc2014da68148

BUGCHECK_P4: 0

FILE_IN_CAB:  051925-12625-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

FAULTING_THREAD:  ffffad89f20760c0

TRAP_FRAME:  ffffc2014da681f0 -- (.trap 0xffffc2014da681f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804218d43a5 rsp=ffffc2014da68388 rbp=ffffc2014da68490
 r8=ffffc2014da68480  r9=ffffad89f29d5470 r10=fffff8040eacfcf0
r11=ffffc2014da68440 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgkrnl!_report_gsfailure+0x5:
fffff804`218d43a5 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffc2014da68148 -- (.exr 0xffffc2014da68148)
ExceptionAddress: fffff804218d43a5 (dxgkrnl!_report_gsfailure+0x0000000000000005)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
ffffc201`4da67ec8 fffff804`0ec2db29     : 00000000`00000139 00000000`00000002 ffffc201`4da681f0 ffffc201`4da68148 : nt!KeBugCheckEx
ffffc201`4da67ed0 fffff804`0ec2e0f2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc201`4da68010 fffff804`0ec2bddb     : ffffad89`ed579000 ffffad89`f3348010 00000000`0000000d fffff804`34b0866e : nt!KiFastFailDispatch+0xb2
ffffc201`4da681f0 fffff804`218d43a5     : fffff804`218d5258 ffffad89`e06750a0 00000000`00000018 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x35b
ffffc201`4da68388 fffff804`218d5258     : ffffad89`e06750a0 00000000`00000018 00000000`00000000 00000000`00000000 : dxgkrnl!_report_gsfailure+0x5
ffffc201`4da68390 fffff804`21a437ac     : 00000000`00000000 00000000`00000000 00000000`00000001 ffffc201`4da68638 : dxgkrnl!DXGCONTEXT::ReleaseReference+0x110
ffffc201`4da684b0 fffff804`21a40f54     : ffffad89`f20760c0 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!SignalSynchronizationObjectInternal+0xf3c
ffffc201`4da68930 fffff804`21a4085b     : 00000000`00000000 00000207`1cc3b0d0 ffffad89`f20760c0 ffff6fff`26400000 : dxgkrnl!DxgkSignalSynchronizationObjectFromGpu2Impl+0x6e4
ffffc201`4da68ab0 fffff804`0ec2d208     : ffffad89`f20760c0 ffffc201`4da68b60 00000207`0abef750 ffffffff`ff676980 : dxgkrnl!DxgkSignalSynchronizationObjectFromGpu2+0xb
ffffc201`4da68ae0 00007ff9`51766004     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000cd`b97fc878 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`51766004

SYMBOL_NAME:  dxgkrnl!_report_gsfailure+5

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.22621.5331

STACK_COMMAND: .process /r /p 0xffffad89f1e870c0; .thread 0xffffad89f20760c0 ; kb

BUCKET_ID_FUNC_OFFSET:  5

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_dxgkrnl!_report_gsfailure

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1685fa82-f4b9-d129-b6b1-78c3bba339a9}

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

23 answers

Jonathan Deives 73,715 Reputation points Independent Advisor

2025-05-20T05:06:10+00:00

This error is usually related to the CPU. If you have updated your drivers, check if the problem persists.

If you want to do some testing, you can stress test your CPU using testing softwares.
Was this answer helpful?

0 comments No comments
Anonymous

2025-05-20T04:44:38+00:00

I have not applied overclock nor do I have an XMP profile. I have updated the BIOS yesterday. I just updated the chipset drivers.

How should I test it for now ? Is there any recommended stress test to use to test if my PC will crash ?

Should I be concerned of the graphics card ? This PC has Radeon Graphics and NVIDIA GEFORCE GTX 1650 Ti

It is currently using the Radeon as the PhysX processor.

Thank you for the advice and support.
Was this answer helpful?

0 comments No comments
Jonathan Deives 73,715 Reputation points Independent Advisor

2025-05-20T03:26:15+00:00

The minidump file indicated that the cause is "AuthenticAMD.sys", are you using an overclock or XMP profile in the RAM? If yes, disable it and set default.

Go to the manufacturer's website, download the available chipset drivers and update the BIOS as well.
Was this answer helpful?

0 comments No comments
Anonymous

2025-05-20T03:18:36+00:00
Hello Johnathan,

I appreciate you taking the time to help me with this. Please note that I have done the following:
- Reinstalled Windows 11 ( it crashed during the windows setup where you choose the language, keyboard, etc ..)
- Ran Memory Diagnostics, no problems reported.
- sfc /scannow no issues
- changed the start registry for AmdPPS to 4
- DISM /Online /Cleanup-Image /RestoreHealth no issues
I am getting frustrated and hopeless. I hope you can analyze the dumps and tell me your thoughts:

https://drive.google.com/file/d/1H8OTkW5EdU328MYgkMIR-je5PC0bIyji/view?usp=sharing
Was this answer helpful?

0 comments No comments
Jonathan Deives 73,715 Reputation points Independent Advisor

2025-05-19T22:16:48+00:00

Hello my name is Jonathan, I'm here to help you with this problem.

See if your computer is creating minidump files.

To find these files, this is the path "C:\Windows\Minidump".

First copy and paste all the minidump files you have to another folder and then zip it. Then upload the ZIP file to the cloud on a website like OneDrive, Google Drive or Dropbox.

Choose to share or right click and get the share link.

Please post the link to the ZIP file here so it can be reviewed.
Was this answer helpful?

0 comments No comments

Share via

Need help with BSOD - multiple different errors.

23 answers