-------------------------------------------------------------------------------- Welcome to WhoCrashed (HOME EDITION) v 5.51 -------------------------------------------------------------------------------- This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice. This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. To obtain technical support visit www.resplendence.com/support Click here to check if you have the latest version or if an update is available. Just click the Analyze button for a comprehensible report ... -------------------------------------------------------------------------------- Home Edition Notice -------------------------------------------------------------------------------- This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. Click here for more information on the professional edition. Click here to buy the the professional edition of WhoCrashed. -------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- Computer name: OLAFDEWIT Windows version: Windows 8.1 , 6.3, build: 9600 Windows dir: C:\WINDOWS Hardware: XPS 8700, Dell Inc., 0KWVT8 CPU: GenuineIntel Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 12833726464 bytes total -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Wed 21/09/2016 14:42:55 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\092116-19281-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0) Bugcheck code: 0xA (0x2DE9, 0x2, 0x0, 0xFFFFF802ADFD4EEA) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 21/09/2016 14:42:55 GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xA (0x2DE9, 0x2, 0x0, 0xFFFFF802ADFD4EEA) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 21/09/2016 12:04:07 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\092116-38531-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFF8B, 0x2, 0x0, 0xFFFFF8025ECAF07C) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 20/09/2016 17:48:45 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\092016-38937-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x5FCD1C) Bugcheck code: 0xFC (0xFFFFF801BD689D1C, 0x8000000313EFF021, 0xFFFFF803026183E0, 0x0) Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 372.70 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 372.70 Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. 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 372.70 , NVIDIA Corporation). Google query: NVIDIA Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY On Tue 20/09/2016 10:56:25 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\092016-43734-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0) Bugcheck code: 0x7F (0x8, 0xFFFFD001E49AE230, 0xFFFFD00022FC23D8, 0x2348C68B) Error: UNEXPECTED_KERNEL_MODE_TRAP 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 indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 18/09/2016 16:21:08 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\091816-42546-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0) Bugcheck code: 0xA (0x273F, 0x2, 0x0, 0xFFFFF802817A01F0) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 16/09/2016 14:16:17 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\091616-36218-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x570AD) Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF80258ECE0AD, 0xFFFFD00021919818, 0xFFFFD00021919020) 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 Mon 12/09/2016 14:14:07 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\091216-30875-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0) Bugcheck code: 0x7F (0x8, 0xFFFFD0010A35A230, 0xD, 0xFFFFF8024C0C496E) Error: UNEXPECTED_KERNEL_MODE_TRAP 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 indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 11/09/2016 18:20:28 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\091116-29718-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0) Bugcheck code: 0xA (0xFFFFF800D5D8B4B8, 0x2, 0x0, 0xFFFFF800CDAC0BF5) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 Sat 10/09/2016 21:42:09 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\091016-28640-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0) Bugcheck code: 0xA (0xFFFFE001D93FF998, 0x2, 0x0, 0xFFFFF80011E4416A) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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.