HP ENVY x360 Convertible 15-es1xxx constant BSOD

[SBGAdmin]

Computer name:	SBGMBLWRKSTTN2
Windows version:	Windows 11, 10.0, version 2009, build: 22621 (x64)
Windows dir:	C:\WINDOWS
Hardware:	HP ENVY x360 Convertible 15-es1xxx, HP, 8982
CPU:	GenuineIntel 11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz 8664, level: 6
Processor count:	8 logical processors, active mask: 255
RAM:	16151.6MB

here are the last crash dumps

Crash dump directories:
C:\windows
C:\windows\Minidump

On Sun 6/25/2023 10:18:12 AM your computer crashed or a problem was reported

Crash dump file:	C:\windows\Minidump\062523-15796-01.dmp (Minidump)
Bugcheck code:	0xC2(0x99, 0xFBFF900A66925D40, 0x0, 0x0)
Bugcheck name:	BAD_POOL_CALLER
Bug check description:	This indicates that the current thread is making a bad pool request.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

On Sun 6/25/2023 10:14:27 AM your computer crashed or a problem was reported

Crash dump file:	C:\windows\Minidump\062523-13671-01.dmp (Minidump)
Bugcheck code:	0xC2(0x99, 0xFBFFA6002244CA80, 0x0, 0x0)
Bugcheck name:	BAD_POOL_CALLER
Bug check description:	This indicates that the current thread is making a bad pool request.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

On Sat 6/24/2023 1:42:06 PM your computer crashed or a problem was reported

Crash dump file:	C:\windows\Minidump\062423-16531-01.dmp (Minidump)
Bugcheck code:	0x1000007E(0xFFFFFFFFC0000005, 0xFFFFF80543A06EBC, 0xFFFF9D0C58696A78, 0xFFFF9D0C58696290)
Bugcheck name:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Driver or module in which error occurred:	Wdf01000.sys (Wdf01000+0x6EBC)
File path:	Wdf01000.sys
Description:	Kernel Mode Driver Framework Runtime
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	This indicates that a system thread generated an exception which the error handler did not catch.
Analysis:	This is likely a software problem which means that it was probably caused by a bug in a driver. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues The crash took place in a Microsoft module. Possibly this problem was caused by another driver on your system that cannot be identified at this time.

On Sat 6/24/2023 1:00:03 PM your computer crashed or a problem was reported

Crash dump file:	C:\windows\Minidump\062423-15984-01.dmp (Minidump)
Bugcheck code:	0xC2(0x99, 0xFBFFCB0935006B00, 0x0, 0x0)
Bugcheck name:	BAD_POOL_CALLER
Bug check description:	This indicates that the current thread is making a bad pool request.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

On Sat 6/24/2023 11:21:00 AM your computer crashed or a problem was reported

Crash dump file:	C:\windows\Minidump\062423-14359-01.dmp (Minidump)
Bugcheck code:	0xC2(0x99, 0xFBFFCE06CC6D6840, 0x0, 0x0)
Bugcheck name:	BAD_POOL_CALLER
Bug check description:	This indicates that the current thread is making a bad pool request.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

On Tue 5/2/2023 5:34:04 AM your computer crashed or a problem was reported

Crash dump file:	C:\windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x139(0xA, 0x0, 0x0, 0xFFFF860105FEB900)
Bugcheck name:	KERNEL_SECURITY_CHECK_FAILURE
Bug check description:	The kernel has detected the corruption of a critical data structure.
Analysis:	This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues