Welcome to WhoCrashed (HOME EDITION) v 5.54
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 might help you find the root cause of the problem and 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 or black 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.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: MSI
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: GS70 2QE, Micro-Star International Co., Ltd., MS-1773
CPU: GenuineIntel Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8497233920 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 12/05/2017 07:58:38 your computer crashed
crash dump file: C:\WINDOWS\Minidump\051217-6812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)
Bugcheck code: 0xBE (0xFFFFE7B0004473A8, 0x8000000001400121, 0xFFFFAE8063303DB0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 12/05/2017 07:58:38 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: 0xBE (0xFFFFE7B0004473A8, 0x8000000001400121, 0xFFFFAE8063303DB0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 09/05/2017 21:09:20 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050917-7953-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0xAC84)
Bugcheck code: 0xD1 (0xFFFFBD841E768002, 0x2, 0x1, 0xFFFFF80FFD41AC84)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 standard 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 Tue 09/05/2017 10:02:34 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050917-7281-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x3CF825A0BD48, 0xFFFFC307DA5F42B0, 0xFFFFC307DAAC4010)
Error: WDF_VIOLATION
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 Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 standard 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 Tue 09/05/2017 09:22:33 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050917-10046-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x2DA86)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8E09882DA86, 0xFFFF8D01D74F93E0, 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 standard 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.
Conclusion
13 crash dumps have been found and analyzed. Only 5 are included in this report. 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.