crash dump file: C:\WINDOWS\Minidump\112119-6296-01.dmp
This was probably caused by the following module:
dump_iastorac.sys (0xFFFFF80163C436F0)
Bugcheck code: 0xFC (0xFFFFF80163C436F0, 0x89000003CC825863, 0xFFFF92043575F2D0, 0x2)
Error:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\System32\drivers\dump_iaStorAC.sys
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 21-Nov-19 7:43:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module:
dump_iastorac.sys (0xFFFFF80163C436F0)
Bugcheck code: 0xFC (0xFFFFF80163C436F0, 0x89000003CC825863, 0xFFFF92043575F2D0, 0x2)
Error:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\System32\drivers\dump_iaStorAC.sys
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 21-Nov-19 5:45:00 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112119-6031-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5ECF5D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF807351ECF5D, 0xFFFFD80436407408, 0xFFFFD80436406C50)
Error:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 19-Nov-19 9:26:40 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111919-12671-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFFD70570A22080, 0x0, 0x0, 0x0)
Error:
CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 14-Nov-19 5:19:41 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111419-6218-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8045942FB4D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.