On Tue 30/06/2020 17:49:26 
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20) 
Bugcheck code: 0x1 (0x7FF9BCAEAE14, 0x0, 0xFFFF, 0xFFFFAB0951764B80)
Error: APC_INDEX_MISMATCH

On Tue 30/06/2020 18:23:48 
This was probably caused by the following module: hwinfo64a_150.sys (HWiNFO64A_150+0x88F3) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80354040E7C, 0xFFFFE18982B68850, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hwinfo64a_150.sys . 
Google query: hwinfo64a_150.sys SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe

On Tue 30/06/2020 22:05:35
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80764A7A2F1) 
Bugcheck code: 0xD1 (0x330, 0x2, 0x0, 0xFFFFF80764A7A2F1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 451.48 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 451.48
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 451.48 , NVIDIA Corporation). 
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Wed 01/07/2020 10:41
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x3E2B9) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFF, 0x8, 0xFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 

On Wed 01/07/2020 11:16:07
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!ExAcquirePushLockExclusiveEx+0x14B) 
Bugcheck code: 0x192 (0xFFFF890F94BCB080, 0xFFFF890F96BC33E8, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.