When in safe mode I keep getting this error popup "The system detected an overrun of a stack-based buffer in this application"

To build your profile on this forum click on your username at the top of the page and select system specs. By filling that in, we can always know how your laptop is equipped in the future.

I meant that you should add the specs to your user account on this forum then anyone will be able to see them through the my computer links in these threads. Go into your account to add your specs there. The specs you put in the thread will be plenty.
https://www.elevenforum.com/members/mm71.6572/

Did you try running sfc from command prompt? Open an administrator command prompt and type sfc /scannow note that there is a space between the sfc and the forward slash. If it finds errors and fixes them be sure to run it again until it reports no errors.
Running the dism tool may fix things though not guaranteed.
Use System File Checker (SFC) to Repair System Files in Windows 11 Tutorial
Repair Windows Image Component Store in Windows 11 Tutorial

I filled in some info....

Yes, I tried sfc /scannow and it did not find any integrity problems.

For post #6 please include all collected V2 and event script files.

########################## Crash Dump Settings #########################


AutoReboot : 1
CrashDumpEnabled : 7
DumpFile : C:\Windows\MEMORY.DMP
DumpLogLevel : 0
EnableLogFile : 1
LogEvent : 1
MinidumpDir : C:\Windows\Minidump
MinidumpsCount : 5
Overwrite : 1
DumpFilters : {dumpfve.sys}
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
PSChildName : CrashControl
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry




######################## Crash Dump Type Matrix ########################



CrashDumpEnabled FilterPages

Disabled 0 <does not exist>

Complete 1 <does not exist>

Active 1 1

Kernel 2 <does not exist>

Small 3 <does not exist>

Automatic 7 <does not exist>

Events from today:

Event[591]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T08:29:21.0190000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[592]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T08:29:21.1250000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[593]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T08:29:21.3420000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[594]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:38:58.3210000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[595]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:38:58.5220000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[596]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:38:58.7730000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[597]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:40:03.5690000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[598]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:40:03.5760000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[599]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:47:16.3840000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[600]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:49:25.1130000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[601]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:49:25.1590000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[602]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:52:13.9360000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[603]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:52:14.0380000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[604]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T09:52:14.2520000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[605]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:01:23.2040000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[606]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:01:23.3460000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[607]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:01:23.5720000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[608]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:47:03.1140000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[609]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:58:17.6980000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[610]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:58:17.7810000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[611]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T11:58:17.9710000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[612]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T13:33:58.4090000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[613]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T13:33:58.4190000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[614]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T13:37:03.3310000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[615]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T13:37:03.6810000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[616]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T13:37:04.6260000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[617]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:08:31.9700000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[618]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:08:32.0670000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[619]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:08:32.2820000Z
Event ID: 420
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[620]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:33:44.4050000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[621]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:33:44.4460000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[622]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:33:44.8350000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[623]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T14:33:44.8370000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[624]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T15:13:04.6300000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[625]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T15:13:04.6420000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[626]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T15:32:08.7990000Z
Event ID: 430
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[627]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T15:33:29.5500000Z
Event ID: 400
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[628]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T15:33:29.5610000Z
Event ID: 410
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Event[629]
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 2022-01-21T15:33:29.6130000Z
Event ID: 430
Task: N/A
Level: N/A
Opcode: N/A
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BELIEVEINYOURSELF
Description:
N/A

Why not follow the instructions?