System Information (local) -------------------------------------------------------------------------------- Computer name: CONCEPTHOR Windows version: Windows 10, 10.0, version 1909, build: 18363 Windows dir: C:\WINDOWS Hardware: CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 970 @ 3.20GHz 8664, level: 6 12 logical processors, active mask: 4095 RAM: 25760485376 bytes (24,0GB) -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dumps are enabled on your computer. Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Wed 14/04/2021 23:55:11 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\041521-42015-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8033624AB83, 0xFFFF820705332610, 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 14/04/2021 23:55:11 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\MEMORY.DMP This was probably caused by the following module: ntfs.sys (Ntfs+0x11D03E) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8033624AB83, 0xFFFF820705332610, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\drivers\ntfs.sys product: Système d’exploitation Microsoft® Windows® company: Microsoft Corporation description: Pilote du système de fichiers NT 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 file system 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 Tue 30/03/2021 05:08:50 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\041421-53328-01.dmp This was probably caused by the following module: win32kbase.sys (0xFFFFC9323CFE5A2F) Bugcheck code: 0x3B (0xC0000005, 0xFFFFC9323CFE5A2F, 0xFFFFDE8ABA3C9BE0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 Fri 26/03/2021 19:33:27 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032921-41921-01.dmp This was probably caused by the following module: win32kbase.sys (0xFFFF9513C5A8BFBB) Bugcheck code: 0x3B (0xC0000005, 0xFFFF9513C5A8BFBB, 0xFFFF988AD4E97E10, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 24/03/2021 17:58:25 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032621-43015-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80773486465, 0xFFFFEC00065CDB00, 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 24/03/2021 11:13:53 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032421-42921-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x1A (0x6194A, 0x0, 0x1, 0x0) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. 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. This problem might also be caused because of overheating (thermal issue). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 22/03/2021 21:20:09 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032321-52109-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8026ED1CF7C, 0xFFFFB20A11DE9828, 0xFFFFB4800BDEE930) 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. On Sat 20/03/2021 18:00:38 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032221-40703-01.dmp This was probably caused by the following module: netio.sys (0xFFFFF804571474F8) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF804571474F8, 0xFFFF8101ECC78930, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\drivers\netio.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Network I/O Subsystem 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 Fri 19/03/2021 19:35:48 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032021-40296-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8002145DAAE, 0xFFFFF909086D1A68, 0xFFFFD680FF7BF930) 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 Fri 19/03/2021 08:23:40 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\031921-41218-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8012A91D176, 0xFFFFE1001B7E4550, 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- On your computer a total of 46 crash dumps have been found. Only 10 have been analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.