Depuis peu, j'ai un gros problème avec mon pc portable. Après avoir effectué un scan antivirus complet au moyen de l'antivirus gratuit AVAST, mon pc plante et un écran bleu furtif apparaît à chaque fois. J'ai effectué une analyse "whocrased" et voici ce qui en ressort ... ce n'est pas triste lol :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-ADMIN
windows version: Windows Vista Service Pack 1, 6.0, build: 6001
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3148955648 total
VM: 2147352576, free: 2033156096
On Sat 18/02/2012 7:08:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021812-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1A36)
Bugcheck code: 0xA (0xFFFFFFFF836B3A40, 0x2, 0x1, 0xFFFFFFFF882C37FC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 which cannot be identified at this time.
On Sat 18/02/2012 7:08:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1A36)
Bugcheck code: 0xA (0xFFFFFFFF836B3A40, 0x2, 0x1, 0xFFFFFFFF882C37FC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 which cannot be identified at this time.
On Sat 28/01/2012 11:22:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012812-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xA (0x686B, 0x1B, 0x1, 0xFFFFFFFF8823F9BD)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Sat 28/01/2012 11:16:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012812-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3841D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C9E64F7, 0xFFFFFFFF8C170BB8, 0xFFFFFFFF8C1708B4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 27/01/2012 13:51:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012712-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1A36)
Bugcheck code: 0xA (0xFFFFFFFF83D868A8, 0x2, 0x1, 0xFFFFFFFF882E87FC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 which cannot be identified at this time.
On Tue 24/01/2012 18:31:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012412-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x21F61A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8846561A, 0xFFFFFFFFE2BDA91C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Mon 23/01/2012 9:37:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012312-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x21F61A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8842F61A, 0xFFFFFFFF90B5791C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Mon 23/01/2012 9:31:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012312-01.dmp
This was probably caused by the following module: usbccgp.sys (usbccgp+0x8E64)
Bugcheck code: 0xD1 (0xFFFFFFFFBADBADBA, 0x2, 0x0, 0xFFFFFFFFCC933E64)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbccgp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Common Class Generic Parent Driver
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 which cannot be identified at this time.
On Tue 17/01/2012 8:32:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011712-02.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1A36)
Bugcheck code: 0xA (0xFFFFFFFF8212AA88, 0x2, 0x1, 0xFFFFFFFF882F87FC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 which cannot be identified at this time.
On Tue 17/01/2012 8:27:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011712-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x21F61A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8846D61A, 0xFFFFFFFF90B6791C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Fri 13/01/2012 14:59:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x21F61A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8843961A, 0xFFFFFFFFD1B1991C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Sun 25/12/2011 10:58:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122511-01.dmp
This was probably caused by the following module: klif.sys (klif+0x2E343)
Bugcheck code: 0xF7 (0xFFFFFFFF97175A7C, 0xFFFFFFFF9635416B, 0x69CABE94, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Klif Mini-Filter fre_wlh_x86
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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: klif.sys (Klif Mini-Filter fre_wlh_x86, Kaspersky Lab).
Google query: klif.sys Kaspersky Lab DRIVER_OVERRAN_STACK_BUFFER
On Sat 24/12/2011 10:06:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122411-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xA (0x6C, 0x1B, 0x1, 0xFFFFFFFF882769BD)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Mon 19/12/2011 16:32:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121911-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x21F61A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8842F61A, 0xFFFFFFFFE370291C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Tue 13/12/2011 11:34:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121311-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1DDD)
Bugcheck code: 0xD1 (0xFFFFFFFF80580898, 0x2, 0x0, 0xFFFFFFFF881A7DDD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 which cannot be identified at this time.
86 crash dumps have been found and analyzed. Only 15 are included in this report. 4 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:
jmcr.sys (JMicron JMB38X Flash Media Controller Driver, JMicron Technology Corporation)
portcls.sys (Port Class (Class Driver for Port/Miniport Devices), Microsoft Corporation)
Mikiz86
Messages postés127Date d'inscriptionjeudi 23 février 2012StatutMembreDernière intervention24 août 201522 2 mars 2012 à 16:17
Apparemment tes crash seraient dus a des drivers défectueux, tente de mettre tes drivers a jour avec le site https://www.touslesdrivers.com/ rend toi sur la page "mes drivers" il te sera proposé d'installer le module MaConfig, pour detecter tes drivers actuels, fait le et ensuite le systeme analysera ton pc pour t'indiquer si des drivers plus recents sont disponibles (verifie que ton systeme d'exploitation est correctement detecté et ne prends que les drivers certifié WHQL et plus recent que les tiens, decoche l'affichage des drivers beta)
Il ne te restera qu'a telecharger et installer les drivers disponibles et verifier si le problème persiste.
