Problème écran bleu
Posté : lun. 11 juin 2012 11:04
Bonjour, j'ai aussi un problème d'écran bleu depuis quelques jours.
j'ai en premier lieu cru que le problème venait d'orange car il a débuté après que j'ai installé et configuré ma nouvelle livebox.
Néanmoins après avoir désinstallé les logiciels d'orange le problème persiste et je doute qu'il vienne d'une surchauffe car le problème ne se produit pas après x heures de connexion mais deux minutes!
J'ai avira en antivirus, je l'ai désinstallé et installé la nouvelle version qui n'a rien trouvé au scan.
L'ordi est vieux, il arrive certainement en bout de course. Je pense qu'un composant ou un problème de ram est à l'origine.
Pourriez vous m'aider à décrypter la situation.
Merci d'avance, Angéline
System Information (local)
--------------------------------------------------------------------------------
computer name: CARPENTER
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Sempron(tm) 3000+ AMD586, level: 6
1 logical processors, active mask: 1
RAM: 536330240 total
VM: 2147352576, free: 2028003328
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 11/06/2012 08:18:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD24C)
Bugcheck code: 0x10000050 (0xFFFFFFFF85FC1838, 0x1, 0xFFFFFFFF804E424C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 09/06/2012 15:18:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060912-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2CE8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF802CE8, 0xFFFFFFFFB9DC4CA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Thu 07/06/2012 19:00:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060712-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 07/06/2012 18:50:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF6A5)
Bugcheck code: 0x1000000A (0xFFFFFFFFEB800013, 0x2, 0x0, 0xFFFFFFFF804E66A5)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 03/06/2012 20:12:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060312-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD97E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8056BEF6, 0xFFFFFFFFB9E6CA98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Mon 02/04/2012 12:28:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD24C)
Bugcheck code: 0x10000050 (0xFFFFFFFF85FC0D28, 0x1, 0xFFFFFFFF804E424C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 02/04/2012 12:19:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-01.dmp
This was probably caused by the following module: hidusb.sys (hidusb+0x5BD)
Bugcheck code: 0x100000D1 (0x310046D, 0x2, 0x1, 0xFFFFFFFF82ED776B)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
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 Sun 20/11/2011 11:11:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini112011-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3A2B5)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Sun 20/11/2011 11:05:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini112011-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2AB5)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE2BF79B0, 0xFFFFFFFFE2BF79E8, 0xC070401)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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 01/11/2011 16:43:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110111-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x337B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF80337B, 0xFFFFFFFFB99BF630, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 19/10/2011 13:24:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101911-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD97E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8056BEF6, 0xFFFFFFFFBA547A98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Fri 14/10/2011 05:51:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF3B9)
Bugcheck code: 0x1000000A (0xFFFFFFFF8B55FF6B, 0x2, 0x0, 0xFFFFFFFF804E63B9)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 27/09/2011 15:56:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092711-01.dmp
This was probably caused by the following module: ftdisk.sys (ftdisk+0x991)
Bugcheck code: 0x100000D1 (0x94, 0x2, 0x0, 0xFFFFFFFFF8476991)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ftdisk.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de disque à FT
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 20/09/2011 16:54:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3AF70)
Bugcheck code: 0x1000000A (0x63, 0x2, 0x0, 0xFFFFFFFF80511F70)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 18/09/2011 00:16:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-01.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0x9815)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFF8411815, 0xFFFFFFFFB98686A5, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System 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.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
20 crash dumps have been found and analyzed. Only 15 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:
ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.)
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.
j'ai en premier lieu cru que le problème venait d'orange car il a débuté après que j'ai installé et configuré ma nouvelle livebox.
Néanmoins après avoir désinstallé les logiciels d'orange le problème persiste et je doute qu'il vienne d'une surchauffe car le problème ne se produit pas après x heures de connexion mais deux minutes!
J'ai avira en antivirus, je l'ai désinstallé et installé la nouvelle version qui n'a rien trouvé au scan.
L'ordi est vieux, il arrive certainement en bout de course. Je pense qu'un composant ou un problème de ram est à l'origine.
Pourriez vous m'aider à décrypter la situation.
Merci d'avance, Angéline
System Information (local)
--------------------------------------------------------------------------------
computer name: CARPENTER
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Sempron(tm) 3000+ AMD586, level: 6
1 logical processors, active mask: 1
RAM: 536330240 total
VM: 2147352576, free: 2028003328
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 11/06/2012 08:18:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD24C)
Bugcheck code: 0x10000050 (0xFFFFFFFF85FC1838, 0x1, 0xFFFFFFFF804E424C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 09/06/2012 15:18:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060912-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2CE8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF802CE8, 0xFFFFFFFFB9DC4CA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Thu 07/06/2012 19:00:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060712-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 07/06/2012 18:50:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF6A5)
Bugcheck code: 0x1000000A (0xFFFFFFFFEB800013, 0x2, 0x0, 0xFFFFFFFF804E66A5)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 03/06/2012 20:12:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060312-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD97E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8056BEF6, 0xFFFFFFFFB9E6CA98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Mon 02/04/2012 12:28:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD24C)
Bugcheck code: 0x10000050 (0xFFFFFFFF85FC0D28, 0x1, 0xFFFFFFFF804E424C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 02/04/2012 12:19:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-01.dmp
This was probably caused by the following module: hidusb.sys (hidusb+0x5BD)
Bugcheck code: 0x100000D1 (0x310046D, 0x2, 0x1, 0xFFFFFFFF82ED776B)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
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 Sun 20/11/2011 11:11:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini112011-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3A2B5)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Sun 20/11/2011 11:05:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini112011-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2AB5)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE2BF79B0, 0xFFFFFFFFE2BF79E8, 0xC070401)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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 01/11/2011 16:43:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110111-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x337B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF80337B, 0xFFFFFFFFB99BF630, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 19/10/2011 13:24:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101911-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD97E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8056BEF6, 0xFFFFFFFFBA547A98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Fri 14/10/2011 05:51:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF3B9)
Bugcheck code: 0x1000000A (0xFFFFFFFF8B55FF6B, 0x2, 0x0, 0xFFFFFFFF804E63B9)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 27/09/2011 15:56:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092711-01.dmp
This was probably caused by the following module: ftdisk.sys (ftdisk+0x991)
Bugcheck code: 0x100000D1 (0x94, 0x2, 0x0, 0xFFFFFFFFF8476991)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ftdisk.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de disque à FT
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 20/09/2011 16:54:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3AF70)
Bugcheck code: 0x1000000A (0x63, 0x2, 0x0, 0xFFFFFFFF80511F70)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 18/09/2011 00:16:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-01.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0x9815)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFF8411815, 0xFFFFFFFFB98686A5, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System 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.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
20 crash dumps have been found and analyzed. Only 15 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:
ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.)
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.
Il ne faut pas d'erreur dans le cadre en bas à droite.