I bought the professional version of whochrased, becaue I hoped to find more info this way... . In the conclusion (see below) something about : mpfilter.sys
Welcome to WhoCrashed (Professional Edition) v 5.02
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue 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 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.
Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network...
System Information (local)
computer name: SIEN-LT
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: HP ProBook 4720s, Hewlett-Packard, 1411
CPU: GenuineIntel Intel® Core™ i3 CPU M 350 @ 2.27GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3143495680 total
Crash Dump Analysis
Crash dump directory: C:\Users\Moham_000\Desktop\bsodsElvire
Crash dumps are enabled on your computer.
On Wed 5/11/2014 22:18:57 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\110514-44195-01.dmp
uptime: 00:23:00
This was probably caused by the following module: cng.sys (cng!GatherRandomKey+0x52F)
Bugcheck code: 0xA (0x10000, 0x2, 0x1, 0xFFFFF80002D05622)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 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 Wed 5/11/2014 21:40:17 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\110514-50684-01.dmp
uptime: 06:10:41
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF88014FABBA0, 0x2, 0x0, 0xFFFFF80002C7C1AC)
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 Tue 4/11/2014 18:52:22 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\110414-26847-01.dmp
uptime: 00:00:27
This was probably caused by the following module: win32k.sys (win32k!GreLockVisRgn+0x5D)
Bugcheck code: 0x50 (0xFFFFF960012ED5F8, 0x0, 0xFFFFF96000194F2D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
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 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 Sat 1/11/2014 8:57:56 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\110114-29374-01.dmp
uptime: 00:00:28
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xF, 0x8, 0xF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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 Sat 25/10/2014 7:51:39 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\102514-34039-01.dmp
uptime: 00:00:10
This was probably caused by the following module: ntfs.sys (Ntfs!BinarySearchIndex+0x1FC)
Bugcheck code: 0x50 (0xFFFFF88022ED2C58, 0x0, 0xFFFFF880012DA86C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
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 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 Mon 20/10/2014 16:33:15 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\102014-60497-01.dmp
uptime: 00:01:37
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA803131BFA8, 0x2, 0x0, 0xFFFFF80002D19825)
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 Mon 20/10/2014 16:30:52 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\102014-29140-01.dmp
uptime: 00:00:21
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF8801402D700, 0x0, 0xFFFFF80002D0D96C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 13/10/2014 15:22:51 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\101314-33150-01.dmp
uptime: 00:00:37
This was probably caused by the following module: fltmgr.sys (0xFFFFF88000E4B65C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000E4B65C, 0xFFFFF88002884B70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Microsoft Bestandssysteemfilterbeheer
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.
On Sat 11/10/2014 14:02:42 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\101114-37845-01.dmp
uptime: 01:09:54
This was probably caused by the following module: fltmgr.sys (fltmgr! ?? ::FNODOBFM::`string'+0x19D8)
Bugcheck code: 0xD1 (0xFFFFF800050FB748, 0x2, 0x0, 0xFFFFF8800100899C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Microsoft Bestandssysteemfilterbeheer
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 Mon 6/10/2014 22:29:57 GMT your computer crashed
crash dump file: C:\Users\Moham_000\Desktop\bsodsElvire\100714-58515-01.dmp
uptime: 07:09:16
This was probably caused by the following module: mpfilter.sys (MpFilter+0x1A834)
Bugcheck code: 0xFC (0xFFFFF88001C29AE0, 0x800000006FE40121, 0xFFFFF880082797B0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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: mpfilter.sys .
Google query: mpfilter.sys ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Conclusion
12 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
mpfilter.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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.
Sign In
Create Account
