Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Result:Automatically Rebuild the Icon Cache
1.Click/tap on the download button below to download the file below.
Rebuild_Icon_Cache.bat2. Save the file to your desktop, and run it.
3. Click/tap on Run when prompted.
4. Follow the instructions in the command prompt to rebuild the Icon Cache. (see screenshot below)
DownloadWhoCrashed and move the executable to your desktop.
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 Tue 17/03/2020 01:52:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031720-19016-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0)
Bugcheck code: 0x7A (0xFFFFF6FC5006D620, 0xFFFFFFFFC0000185, 0x200035C0A820, 0xFFFFF8A00DAC49B4)
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 Tue 17/03/2020 01:52:16 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 (0xFFFFF6FC5006D620, 0xFFFFFFFFC0000185, 0x200035C0A820, 0xFFFFF8A00DAC49B4)
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.
Conclusion
2 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.
Has Sysnative Forums helped you? Please consider donating to help us support the site!