quelqu'un peut-il m'aider à résoudre mon problème d'écran bleu qui intervient à peu près 2 minutes après le démarrage de ma session
Je joins une analyse Whocrashed avec ma config si quelqu'un sait déchiffrer et me dire ce que je dois faire.
Je ne suis pas informaticien plutôt un bidouilleur
, à priori les écrans bleus seraient dus à un problème matériel ou de pilote.Merci de m'aider
System Information (local)
computer name: PC-DES-QUADS windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 2146492416 total VM: 2147352576, free: 1989017600
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Wed 14/09/2011 19:39:05 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-37221-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892F1487, 0xFFFFFFFF8B57CF7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 19:39:05 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61) Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF892F1487, 0xFFFFFFFF8B57CF7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED 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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED On Wed 14/09/2011 18:36:34 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-45989-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892F9487, 0xFFFFFFFFAF12AF7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 18:07:41 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-43383-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892EB487, 0xFFFFFFFF9AB63F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 18:01:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-40685-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892EC487, 0xFFFFFFFFA929AF7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware
company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:55:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-44023-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892F6487, 0xFFFFFFFFA10F2F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:50:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-42603-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892E3487, 0xFFFFFFFF8B466F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 14/09/2011 17:43:58 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-43290-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892FE487, 0xFFFFFFFFA6686F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:37:52 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-38703-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF89357487, 0xFFFFFFFFA00F8F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:31:49 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-39920-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892D3487, 0xFFFFFFFF8A7D3F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:25:41 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-42011-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892D3487, 0xFFFFFFFF8B5AEF7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:19:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-41886-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892CE487, 0xFFFFFFFF8B494F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 17:13:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-39343-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0xAA9C5)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFE, 0x0, 0xFFFFFFFF888E59C5, 0x0) 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 standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Wed 14/09/2011 16:24:13 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-36769-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892F6487, 0xFFFFFFFFA3A22F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Wed 14/09/2011 14:45:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\091411-34944-01.dmp This was probably caused by the following module: mbam.sys (mbam+0xAAA) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF892F8487, 0xFFFFFFFFB0002F7C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\mbam.sys product: Malwarebytes' Anti-Malware company: Malwarebytes Corporation description: Malwarebytes' Anti-Malware 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation). Google query: mbam.sys Malwarebytes Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Conclusion
26 crash dumps have been found and analyzed. Only 15 are included in this report. 2 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: mbam.sys (Malwarebytes' Anti-Malware, Malwarebytes Corporation) hal.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 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