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: TASNIME
Windows version: Windows 8.1, 6.3, build: 9600
Windows dir: C:\Windows
Hardware: HP Compaq dc7800 Convertible Minitower, Hewlett-Packard, 0AACh
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 586, level: 6
2 logical processors, active mask: 3
RAM: 2133082112 bytes (2,0GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 02/11/2021 13:06:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-22562-01.dmp
This was probably caused by the following module: rtwlanu.sys (rtwlanu+0x334EE)
Bugcheck code: 0x139 (0x3, 0xFFFFFFFF8591D61C, 0xFFFFFFFF8591D540, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\rtwlanu.sys
product: Realtek WLAN Wireless USB 2.0 Adapter
company: Realtek Semiconductor Corporation
description: Realtek WLAN USB NDIS Driver 55584
Bug check description: The kernel has detected the corruption of a critical data structure.
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: rtwlanu.sys (Realtek WLAN USB NDIS Driver 55584, Realtek Semiconductor Corporation ).
Google query: rtwlanu.sys Realtek Semiconductor Corporation KERNEL_SECURITY_CHECK_FAILURE
On Tue 02/11/2021 13:15:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-19937-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0x511C)
Bugcheck code: 0x50 (0xFFFFFFFFAEB89C38, 0x0, 0xFFFFFFFF8B3C61BD, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 Tue 02/11/2021 13:06:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-18437-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9B5AE)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF9033DD80, 0x0, 0xFFFFFFFF9033DD80)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that a pool header is corrupt.
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 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 Tue 02/11/2021 13:11:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-17921-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3379)
Bugcheck code: 0x139 (0x3, 0xFFFFFFFFB1007940, 0xFFFFFFFFB1007870, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Tue 02/11/2021 13:12:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-20171-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x25699)
Bugcheck code: 0x1A (0x41284, 0x6BA2000, 0x1FDA, 0xFFFFFFFFC0802000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a severe memory management error occurred. A PTE or the working set list is corrupted.
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 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 Tue 02/11/2021 13:09:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-18234-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xB673)
Bugcheck code: 0x50 (0xFFFFFFFFB33F8EA0, 0x0, 0xFFFFFFFF8280D673, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 02/11/2021 13:08:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-16406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE3268)
Bugcheck code: 0x19 (0xE, 0xFFFFFFFF9836FB30, 0x590C0960, 0x590CD922)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Tue 02/11/2021 13:21:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110221-15484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE3268)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC003F508, 0x450D0967, 0xFFFFFFFF96975F20)
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 01/11/2021 14:48:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110121-51281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xFBB04)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0028D38, 0x22397867, 0xFFFFFFFFB0AB6C60)
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 01/11/2021 14:48:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110121-33609-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x3AF6)
Bugcheck code: 0x44 (0xFFFFFFFF9551E2D0, 0x1E8C, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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.
Conclusion
On your computer a total of 15 crash dumps have been found. Only 10 have been analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
rtwlanu.sys (Realtek WLAN USB NDIS Driver 55584, Realtek Semiconductor Corporation )
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.