Crash fréquent de mon pc -écran bleu
Résolu/Fermé
ganzalistik
Messages postés
9
Date d'inscription
vendredi 16 mars 2012
Statut
Membre
Dernière intervention
7 juillet 2018
-
18 mars 2012 à 17:52
qwerty- Messages postés 14568 Date d'inscription lundi 11 août 2008 Statut Contributeur Dernière intervention 29 décembre 2022 - 20 mars 2012 à 23:57
qwerty- Messages postés 14568 Date d'inscription lundi 11 août 2008 Statut Contributeur Dernière intervention 29 décembre 2022 - 20 mars 2012 à 23:57
A voir également:
- Mfefirek.sys blue screen
- Double ecran pc - Guide
- Ecran noir pc - Guide
- Écran bleu - Guide
- Benchmark pc - Guide
- Mon pc rame que faire - Guide
4 réponses
qwerty-
Messages postés
14568
Date d'inscription
lundi 11 août 2008
Statut
Contributeur
Dernière intervention
29 décembre 2022
1 446
18 mars 2012 à 22:27
18 mars 2012 à 22:27
hello !
ok donc t'as 2 drivers qui font planter ton pc,
des 15 rapports ici, 100% viennent de mc affee (l'antivirus)
et de F Secure (pour du backup en ligne)
1. désinstalles et réinstalles macaffee, et
2. utilises tu f secure ? de plus 2 antivirus c'est mort.
désinstalle sentièrement f secure...
ok donc t'as 2 drivers qui font planter ton pc,
des 15 rapports ici, 100% viennent de mc affee (l'antivirus)
et de F Secure (pour du backup en ligne)
1. désinstalles et réinstalles macaffee, et
2. utilises tu f secure ? de plus 2 antivirus c'est mort.
désinstalle sentièrement f secure...
ganzalistik
Messages postés
9
Date d'inscription
vendredi 16 mars 2012
Statut
Membre
Dernière intervention
7 juillet 2018
1
20 mars 2012 à 20:26
20 mars 2012 à 20:26
Bonsoir les amis
Pour qwerty, Je te remercie énormément de ton intervention qui m'a aidé à résoudre ce problème.
J'ai désinstallé les 2 antivirus entièrement (macafee et F'secure ) je viens d'acheter et installé Kaspersky ce qui marche nikel. Je suis ravi de t'informer que je n'ai plus de crash de mon ordinateur depuis cette changement et je t'en remercie beaucoup !
Très bonne soirée !!
Pour qwerty, Je te remercie énormément de ton intervention qui m'a aidé à résoudre ce problème.
J'ai désinstallé les 2 antivirus entièrement (macafee et F'secure ) je viens d'acheter et installé Kaspersky ce qui marche nikel. Je suis ravi de t'informer que je n'ai plus de crash de mon ordinateur depuis cette changement et je t'en remercie beaucoup !
Très bonne soirée !!
qwerty-
Messages postés
14568
Date d'inscription
lundi 11 août 2008
Statut
Contributeur
Dernière intervention
29 décembre 2022
1 446
20 mars 2012 à 23:57
20 mars 2012 à 23:57
cool !
c'est pour ça qu'on est la !
si y a quoi que ce soit d'autre, n'hésite pas !
=)
c'est pour ça qu'on est la !
si y a quoi que ce soit d'autre, n'hésite pas !
=)
qwerty-
Messages postés
14568
Date d'inscription
lundi 11 août 2008
Statut
Contributeur
Dernière intervention
29 décembre 2022
1 446
Modifié par qwerty- le 18/03/2012 à 17:56
Modifié par qwerty- le 18/03/2012 à 17:56
salut,
downloade whocrashed et installes le.
il me fournira un vrai rapport sur tes bluescreen, pas comme le rapport de windows, qui est tout pourri.
des que tu auras un ecran bleu il va générer automatiquement un rapport,
poste le en entier ici stp
Il ne faut pas prendre les gens pour des cons,
Mais il ne faut jamais oublier qu'ils le sont .
downloade whocrashed et installes le.
il me fournira un vrai rapport sur tes bluescreen, pas comme le rapport de windows, qui est tout pourri.
des que tu auras un ecran bleu il va générer automatiquement un rapport,
poste le en entier ici stp
Il ne faut pas prendre les gens pour des cons,
Mais il ne faut jamais oublier qu'ils le sont .
ganzalistik
Messages postés
9
Date d'inscription
vendredi 16 mars 2012
Statut
Membre
Dernière intervention
7 juillet 2018
1
18 mars 2012 à 18:32
18 mars 2012 à 18:32
Merci e" votre réponse!
Je viens d'effectuer "whocrashed" and voici le rapport entier !:
On Sun 18/03/2012 13:36:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031812-02.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFDD2E72F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 18/03/2012 13:36:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFDD2E72F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sat 17/03/2012 23:09:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031812-01.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BCA5164, 0xFFFFFFFFD6DC32F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 17/03/2012 14:16:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031712-02.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFC873D2F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 23:14:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031712-01.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9C9C)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120006, 0xFFFFFFFF86CDE220)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation BAD_POOL_CALLER
On Fri 16/03/2012 22:03:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-08.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9C9C)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120035, 0xFFFFFFFF86C1A5D8)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation BAD_POOL_CALLER
On Fri 16/03/2012 18:37:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-07.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9B164, 0xFFFFFFFFB88B32F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 17:37:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-06.dmp
This was probably caused by the following module: mfefirek.sys (mfefirek+0x39F02)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA43D9F02, 0xFFFFFFFFADA70720, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfefirek.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Core Firewall Engine Driver
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.
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: mfefirek.sys (McAfee Core Firewall Engine Driver, McAfee, Inc.).
Google query: mfefirek.sys McAfee, Inc. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 16:43:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-05.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFBF1B52F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 16:12:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-04.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x5C13B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8B5CD13B, 0xFFFFFFFF8C957C08, 0xFFFFFFFF8C957904)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a system thread 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.
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: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 15:45:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-03.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9E164, 0xFFFFFFFF8A23F2F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 08:30:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-02.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x11A3E)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82FDAFE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
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.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. IRQL_NOT_LESS_OR_EQUAL
On Thu 15/03/2012 23:29:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-01.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x809D)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120001, 0xFFFFFFFF8993D448)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. BAD_POOL_CALLER
On Thu 15/03/2012 15:22:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031512-04.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFC587B2F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Thu 15/03/2012 14:43:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031512-03.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x809D)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120005, 0xFFFFFFFF892C4D90)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. BAD_POOL_CALLER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
76 crash dumps have been found and analyzed. Only 15 are included in this report. 5 third party drivers have 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:
fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation)
mfehidk.sys (McAfee Link Driver, McAfee, Inc.)
mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.)
mfefirek.sys (McAfee Core Firewall Engine Driver, McAfee, Inc.)
fsgk.sys (F-Secure Gatekeeper (Minifilter) for Windows x86, F-Secure Corporation)
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 actually 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.
Je viens d'effectuer "whocrashed" and voici le rapport entier !:
On Sun 18/03/2012 13:36:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031812-02.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFDD2E72F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 18/03/2012 13:36:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFDD2E72F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sat 17/03/2012 23:09:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031812-01.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BCA5164, 0xFFFFFFFFD6DC32F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 17/03/2012 14:16:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031712-02.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFC873D2F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 23:14:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031712-01.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9C9C)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120006, 0xFFFFFFFF86CDE220)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation BAD_POOL_CALLER
On Fri 16/03/2012 22:03:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-08.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9C9C)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120035, 0xFFFFFFFF86C1A5D8)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation BAD_POOL_CALLER
On Fri 16/03/2012 18:37:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-07.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9B164, 0xFFFFFFFFB88B32F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 17:37:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-06.dmp
This was probably caused by the following module: mfefirek.sys (mfefirek+0x39F02)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA43D9F02, 0xFFFFFFFFADA70720, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfefirek.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Core Firewall Engine Driver
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.
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: mfefirek.sys (McAfee Core Firewall Engine Driver, McAfee, Inc.).
Google query: mfefirek.sys McAfee, Inc. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 16:43:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-05.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFBF1B52F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 16:12:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-04.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x5C13B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8B5CD13B, 0xFFFFFFFF8C957C08, 0xFFFFFFFF8C957904)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a system thread 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.
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: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 15:45:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-03.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9E164, 0xFFFFFFFF8A23F2F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 16/03/2012 08:30:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-02.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x11A3E)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82FDAFE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
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.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. IRQL_NOT_LESS_OR_EQUAL
On Thu 15/03/2012 23:29:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031612-01.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x809D)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120001, 0xFFFFFFFF8993D448)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. BAD_POOL_CALLER
On Thu 15/03/2012 15:22:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031512-04.dmp
This was probably caused by the following module: fsdfw.sys (fsdfw+0x9E0D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC9C164, 0xFFFFFFFFC587B2F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fsdfw.sys
product: F-Secure Internet Shield
company: F-Secure Corporation
description: F-Secure Internet Shield Driver
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.
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: fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation).
Google query: fsdfw.sys F-Secure Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Thu 15/03/2012 14:43:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031512-03.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x809D)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8120005, 0xFFFFFFFF892C4D90)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. BAD_POOL_CALLER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
76 crash dumps have been found and analyzed. Only 15 are included in this report. 5 third party drivers have 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:
fsdfw.sys (F-Secure Internet Shield Driver, F-Secure Corporation)
mfehidk.sys (McAfee Link Driver, McAfee, Inc.)
mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.)
mfefirek.sys (McAfee Core Firewall Engine Driver, McAfee, Inc.)
fsgk.sys (F-Secure Gatekeeper (Minifilter) for Windows x86, F-Secure Corporation)
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 actually 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.
