Citation :
System Information (local)
--------------------------------------------------------------------------------
Computer name: CORSAIR
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: B450M DS3H, Gigabyte Technology Co., Ltd., B450M DS3H-CF
CPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 34308431872 bytes (32,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. Crash dump directories: C:\Windows
C:\Windows\Minidump
On Thu 14/05/2020 01:20:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051420-8140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3D (0xFFFF840096536D48, 0xFFFF840096536590, 0x0, 0x0)
Error: INTERRUPT_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 bug check appears very infrequently. 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/05/2020 01:20:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeSetEventBoostPriority+0x55) Bugcheck code: 0x3D (0xFFFF840096536D48, 0xFFFF840096536590, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Bug check description: This bug check appears very infrequently. 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/05/2020 00:40:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051420-7328-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFF84A975BD198F) Bugcheck code: 0x50 (0xFFFF800A89956C52, 0x2, 0xFFFF84A975BD198F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
Bug check description: This indicates that invalid system memory has been referenced. 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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Thu 14/05/2020 00:40:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (0xFFFF84A975BD198F) Bugcheck code: 0x50 (0xFFFF800A89956C52, 0x2, 0xFFFF84A975BD198F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
Bug check description: This indicates that invalid system memory has been referenced. 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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Thu 14/05/2020 00:34:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051420-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8022D30F264, 0xFFFFDA800A1E6930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Thu 14/05/2020 00:34:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81D9) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8022D30F264, 0xFFFFDA800A1E6930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Wed 13/05/2020 23:21:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-7156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8060A31628F, 0xFFFF8384E28C9EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Wed 13/05/2020 23:21:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81D9) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8060A31628F, 0xFFFF8384E28C9EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Wed 13/05/2020 22:43:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8072351628F, 0xFFFFEF03B5901EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Wed 13/05/2020 21:21:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-6859-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8054A48C9CE, 0xFFFFD8000D7E6930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Wed 13/05/2020 21:03:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-7015-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF8007DD4DC88) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8007DD4DC88, 0xFFFF840709E27F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Wed 13/05/2020 19:53:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-7437-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF8065D1B20EE) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8065D1B20EE, 0xFFFFEC07B698DDC8, 0xFFFFEC07B698D610)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\u0353751.inf_amd64_309c4586870523c6\B353738\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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. 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). Google query: atikmdag.sys Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Wed 13/05/2020 04:05:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-6781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80681B1628F, 0xFFFFF58E54C8A5B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Wed 13/05/2020 03:46:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051320-7687-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF8027514DC88) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8027514DC88, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
|