Welcome to WhoCrashed (Home Edition) v 6.70
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 a lot of system 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: RENO-THINK
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: 031928G, LENOVO
CPU: GenuineIntel Intel(R) Pentium(R) CPU P6100 @ 2.00GHz 8664, level: 6
2 logical processors, active mask: 3
RAM: 4081639424 bytes (3,8GB)
Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Fri 26/11/2021 20:15:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112621-35490-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0)
Bugcheck code: 0x7A (0xFFFFF6FB80000000, 0xFFFFFFFFC000000E, 0x80018B1C880, 0xFFFFF70000000000)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
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 26/11/2021 20:15:52 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!MmUnlockPages+0xE9E)
Bugcheck code: 0x7A (0xFFFFF6FB80000000, 0xFFFFFFFFC000000E, 0x80018B1C880, 0xFFFFF70000000000)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 25/11/2021 19:15:11 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112521-24226-01.dmp
This was probably caused by the following module: volmgr.sys (0xFFFFF88000EDD3C4)
Bugcheck code: 0x7A (0xFFFFF6FC400076E8, 0xFFFFFFFFC000000E, 0x8009BE0C860, 0xFFFFF88000EDD3C4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\volmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Manager Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 21/11/2021 10:30:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112121-25677-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF88001936A74)
Bugcheck code: 0x7A (0xFFFFF6FC4000C9B0, 0xFFFFFFFFC000000E, 0x8003D4CB860, 0xFFFFF88001936A74)
Error: KERNEL_DATA_INPAGE_ERROR
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 bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.
Conclusion
4 crash dumps have been found and 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.