BSOD en tout genre (surtout quand je joue)
Astraal
-
Astraal -
Astraal -
Bonjour,
J'écris sur ce forum pour espérer trouver une réponse à mon problème. Je suis actuellement en étude, et donc durant les vacances je rentre chez moi. Je dis ça car les problèmes ont commencé après mon retour des vacances de noel. En effet, avant lorsque je jouais, je n'avais strictement aucun problème, alors que maintenant, je me retrouve fréquemment avec des bsod. Ceux que j'ai eu souvent sont liés aux fichiers atikmpag.sys, dxgmms1.sys, tout à l'heure en redémarrant j'ai eu usbehci.sys avec plusieurs bccode différent et différentes causes (bad_pool_header, driver_irql_not_less_or_equal, etc ...)
Je tiens à préciser que toutes les mises à jour windows sont faites, et que tous mes drivers sont à jours. Je n'ai installé aucun matériel en revenant de vacances (ah si mon tapis de souris lol).
J'ai fait une analyse avec whocrashed, et en voici le rapport :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 23/01/2012 21:42:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x01870A9E)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8006995B10, 0xFFFFFA8006995B00, 0xFFFFFA8006995B10)
Error: BAD_POOL_HEADER
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.
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: Unknown .
Google query: Unknown BAD_POOL_HEADER
On Mon 23/01/2012 21:02:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-30747-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.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 14:44:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-54584-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x78C8)
Bugcheck code: 0x116 (0xFFFFFA800C5054E0, 0xFFFFF8800CFA28C8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
On Mon 23/01/2012 13:35:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-38610-01.dmp
This was probably caused by the following module: unknown_module_00000000'00000000.sys (Unloaded_Unknown_Module_00000000'00000000+0x26BE67)
Bugcheck code: 0xA (0x3240, 0x2, 0x1, 0xFFFFF800030EE985)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: unknown_module_00000000'00000000.sys .
Google query: unknown_module_00000000'00000000.sys IRQL_NOT_LESS_OR_EQUAL
On Mon 23/01/2012 13:22:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-34179-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007F7DCEE, 0xFFFFF880055F96A8, 0xFFFFF880055F8F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 23/01/2012 09:28:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-26629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF800032194B0, 0xFFFFFA8008C8D060, 0xFFFFF800032194B0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 21/01/2012 10:51:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-25677-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22620)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000C22620, 0xFFFFF88009A52040, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Mon 16/01/2012 17:38:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-20404-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xA82F)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88006AED82F, 0xFFFFF8800D3998E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION
On Sun 15/01/2012 13:21:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-24211-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20FFB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007F82FFB, 0xFFFFF880063DB698, 0xFFFFF880063DAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 15/01/2012 12:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-35895-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6FFB)
Bugcheck code: 0x19 (0x3, 0xFFFFF8800A049FA0, 0xFFFFF8800A049FA0, 0x34316847001B0000)
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 Sun 15/01/2012 12:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-46893-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007F5ACEE, 0xFFFFF8800D9FE6A8, 0xFFFFF8800D9FDF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 15/01/2012 11:32:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-20389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFF8800D853A90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 13/01/2012 17:20:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011312-21153-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007163CEE, 0xFFFFF88005FDB6A8, 0xFFFFF88005FDAF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 11/01/2012 15:28:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011112-28735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88000FC2EB3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 11/01/2012 15:11:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011112-38906-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x21008)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007421008, 0xFFFFF880069D1698, 0xFFFFF880069D0EF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\010412-24398-01.dmp
Sinon comme autre renseignement, je suis sous windows 7 64 bit, avec :
- Processeur AMD Athlon(tm) II X4 620 Processor
- Mémoire vive 8,00 Go
- Graphiques ATI Radeon HD 5700 Series
En espérant que la solution à ce problème qui devient de pire en pire chaque jour soit révélée.
Merci d'avance à toutes les propositions d'aide et bonne soirée.
J'écris sur ce forum pour espérer trouver une réponse à mon problème. Je suis actuellement en étude, et donc durant les vacances je rentre chez moi. Je dis ça car les problèmes ont commencé après mon retour des vacances de noel. En effet, avant lorsque je jouais, je n'avais strictement aucun problème, alors que maintenant, je me retrouve fréquemment avec des bsod. Ceux que j'ai eu souvent sont liés aux fichiers atikmpag.sys, dxgmms1.sys, tout à l'heure en redémarrant j'ai eu usbehci.sys avec plusieurs bccode différent et différentes causes (bad_pool_header, driver_irql_not_less_or_equal, etc ...)
Je tiens à préciser que toutes les mises à jour windows sont faites, et que tous mes drivers sont à jours. Je n'ai installé aucun matériel en revenant de vacances (ah si mon tapis de souris lol).
J'ai fait une analyse avec whocrashed, et en voici le rapport :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 23/01/2012 21:42:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x01870A9E)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8006995B10, 0xFFFFFA8006995B00, 0xFFFFFA8006995B10)
Error: BAD_POOL_HEADER
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.
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: Unknown .
Google query: Unknown BAD_POOL_HEADER
On Mon 23/01/2012 21:02:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-30747-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.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 14:44:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-54584-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x78C8)
Bugcheck code: 0x116 (0xFFFFFA800C5054E0, 0xFFFFF8800CFA28C8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
On Mon 23/01/2012 13:35:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-38610-01.dmp
This was probably caused by the following module: unknown_module_00000000'00000000.sys (Unloaded_Unknown_Module_00000000'00000000+0x26BE67)
Bugcheck code: 0xA (0x3240, 0x2, 0x1, 0xFFFFF800030EE985)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: unknown_module_00000000'00000000.sys .
Google query: unknown_module_00000000'00000000.sys IRQL_NOT_LESS_OR_EQUAL
On Mon 23/01/2012 13:22:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-34179-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007F7DCEE, 0xFFFFF880055F96A8, 0xFFFFF880055F8F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 23/01/2012 09:28:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-26629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF800032194B0, 0xFFFFFA8008C8D060, 0xFFFFF800032194B0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 21/01/2012 10:51:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-25677-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22620)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000C22620, 0xFFFFF88009A52040, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Mon 16/01/2012 17:38:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-20404-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xA82F)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88006AED82F, 0xFFFFF8800D3998E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION
On Sun 15/01/2012 13:21:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-24211-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20FFB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007F82FFB, 0xFFFFF880063DB698, 0xFFFFF880063DAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 15/01/2012 12:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-35895-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6FFB)
Bugcheck code: 0x19 (0x3, 0xFFFFF8800A049FA0, 0xFFFFF8800A049FA0, 0x34316847001B0000)
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 Sun 15/01/2012 12:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-46893-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007F5ACEE, 0xFFFFF8800D9FE6A8, 0xFFFFF8800D9FDF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 15/01/2012 11:32:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-20389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFF8800D853A90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 13/01/2012 17:20:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011312-21153-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007163CEE, 0xFFFFF88005FDB6A8, 0xFFFFF88005FDAF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 11/01/2012 15:28:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011112-28735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88000FC2EB3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 11/01/2012 15:11:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011112-38906-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x21008)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007421008, 0xFFFFF880069D1698, 0xFFFFF880069D0EF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\010412-24398-01.dmp
Sinon comme autre renseignement, je suis sous windows 7 64 bit, avec :
- Processeur AMD Athlon(tm) II X4 620 Processor
- Mémoire vive 8,00 Go
- Graphiques ATI Radeon HD 5700 Series
En espérant que la solution à ce problème qui devient de pire en pire chaque jour soit révélée.
Merci d'avance à toutes les propositions d'aide et bonne soirée.
A voir également:
- BSOD en tout genre (surtout quand je joue)
- Bsod - Guide
- Logiciel classement musique par genre gratuit - Télécharger - Lecture & Playlists
- Gif bien joué - Guide
- Livre de cp1 mariam joue à la balle pdf - Télécharger - Études & Formations
- Pourquoi mon pc freeze quand je joue - Guide
23 réponses
- 1
- 2
Suivant
Tu semble avoir des problemes aux niveau de ta carte graphique, ce qui ma fait dire ca :
-Amd (meme si ton processeur est amd)
-driver (des problemes de driver)
-memoire graphique
A mon avis essaye de remplacer ta carte graphique ou je t'en dirais plus dans quelque minute.
Merci
-Amd (meme si ton processeur est amd)
-driver (des problemes de driver)
-memoire graphique
A mon avis essaye de remplacer ta carte graphique ou je t'en dirais plus dans quelque minute.
Merci
Chaque fois que j'ai essayé de réinstaller les drivers de ma carte graphique, j'ai eu le droit à des écrans bleus, donc je pense que ça a affecté l'installation =S
Sinon je peux pas changer de carte graphique, en plus elle a à peine un an.
Pourrais-tu me décrire la procédure pour désinstaller entièrement et proprement un driver pour ensuite le réinstaller s'il te plaît ?
Sinon je peux pas changer de carte graphique, en plus elle a à peine un an.
Pourrais-tu me décrire la procédure pour désinstaller entièrement et proprement un driver pour ensuite le réinstaller s'il te plaît ?
Essaye en mode sans echec avant et dit moi si sa plante tout seul au bout d'une bonne heure. Ou alors le driver est incompatible avec un logiciel ou autre (ne me demande pas pourquoi, Windows est con) et change le slot de ta carte mere si tu a deux pci-e.
Qu'est-ce qu'il faut que j'essaye en mode sans échec ? L'installation du driver ? ou la Désinstallation ?
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
La desinstallation puis la reinstallation et si ca continu essaye un driver different pour voir en profondeur d'ou le probleme vient.
Un driver différent pour ma carte graphique ? C'est-à-dire une ancienne version ? Ou alors un driver d'un autre fabriquant ?
Donc hier j'ai pu jouer sans strictement aucun problème, j'ai également regardé un film en bluray, et je n'ai eu aucun bsod.
Par contre depuis ce matin, impossible de démarrer mon pc, j'ai un écran bleu lorsque le logo windows commence à apparaître (le logo sur le fond noir). c'est un STOP : 0x0000001E (OxFFFFFFFC0000005, 0xFFFFF80003090356, 0X000000000000000, 0x000000000000)
Je sais vraiment pas quoi faire ! HELP PLEASE !
PS : je peux démarrer en mode sans échec
Edit : après une restauration système, j'ai pu redémarrer normalement. Précisons que le démarrage a foiré après que j'ai essayé mon nouveau casque, logitech. Peut-être un indice sur la source de ces écrans bleus
Par contre depuis ce matin, impossible de démarrer mon pc, j'ai un écran bleu lorsque le logo windows commence à apparaître (le logo sur le fond noir). c'est un STOP : 0x0000001E (OxFFFFFFFC0000005, 0xFFFFF80003090356, 0X000000000000000, 0x000000000000)
Je sais vraiment pas quoi faire ! HELP PLEASE !
PS : je peux démarrer en mode sans échec
Edit : après une restauration système, j'ai pu redémarrer normalement. Précisons que le démarrage a foiré après que j'ai essayé mon nouveau casque, logitech. Peut-être un indice sur la source de ces écrans bleus
Finalement non je ne pense pas, après la récupération, j'ai remis mon casque, et je n'ai pas eu de problème différent de ceux que j'avais avant. Donc avec ou sans le casque, je me retrouve avec les mêmes problèmes.
Des fois, après un bsod, mon écran n'affiche plus rien, et le bouton clignote comme quand l'unité centrale est éteinte. Je suis alors obligé d'éteindre l'unité en maintenant le bouton power et de la relancer, en espérant que l'écran affiche ce qu'il doit afficher.
Des fois, après un bsod, mon écran n'affiche plus rien, et le bouton clignote comme quand l'unité centrale est éteinte. Je suis alors obligé d'éteindre l'unité en maintenant le bouton power et de la relancer, en espérant que l'écran affiche ce qu'il doit afficher.
C'est logique je pense a une reparation avec le cd de Windows ou un truc comme ca tu a verifier la totalite de tes composants ?
Parce que je veux t'eviter une reinstallation (formatage du disque dur) car tu perdrais l'ensemble de tes donnees non sauvegardes.
Parce que je veux t'eviter une reinstallation (formatage du disque dur) car tu perdrais l'ensemble de tes donnees non sauvegardes.
Vu comment j'en ai marre, je comptais le formater, donc ne tkt pas ^^ (je compte en profiter pour mettre windows 7 professionnal à la place)
J'attends juste de pouvoir rentrer chez moi pour récupérer ce qu'il me faut (comme l'antivirus)
J'attends juste de pouvoir rentrer chez moi pour récupérer ce qu'il me faut (comme l'antivirus)
Tu as quelle edition actuellement ? Professionnel je lai mais si ta config est pas diffusement puissante (comme la mienne) sa tournera un peu mal mais reste leger. Je te conseille Seven integral.
je pense que mon pc est assez puissant pour le faire tourner sans problème
Par contre, mon pc vient d'être formater et j'ai eu un bsod avec un bccode 3B et system_service_exception
Est-ce que ces écrans bleus peuvent être dû au bios ? Il date de 2009
Par contre, mon pc vient d'être formater et j'ai eu un bsod avec un bccode 3B et system_service_exception
Est-ce que ces écrans bleus peuvent être dû au bios ? Il date de 2009
Voilà le rapport de whocrashed, après le formatage :
On Sat 28/01/2012 20:41:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED
On Sat 28/01/2012 20:38:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-27097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E238B0, 0xFFFFF80002E238A0, 0xFFFFF80002E238B0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 28/01/2012 20:11:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-24882-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CB581E, 0xFFFFF8800AF6E8C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Il semblerait que ce soit lié au fichier ntoskrnl.exe. Qu'est-ce donc ? Et que puis-je faire ?
On Sat 28/01/2012 20:41:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED
On Sat 28/01/2012 20:38:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-27097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E238B0, 0xFFFFF80002E238A0, 0xFFFFF80002E238B0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 28/01/2012 20:11:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-24882-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CB581E, 0xFFFFF8800AF6E8C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Il semblerait que ce soit lié au fichier ntoskrnl.exe. Qu'est-ce donc ? Et que puis-je faire ?
Peut-être, je vais télécharger memtest 86+ pour vérifier les barettes. Comment faire pour les disques durs ?
Sinon, deux rapports supplémentaires :
On Sat 28/01/2012 21:35:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-24632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x375D85)
Bugcheck code: 0xA (0x78, 0x2, 0x1, 0xFFFFF80002C8EC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.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 21:35:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltFindExtraCreateParameter+0x115A)
Bugcheck code: 0xA (0x78, 0x2, 0x1, 0xFFFFF80002C8EC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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.
Sinon, deux rapports supplémentaires :
On Sat 28/01/2012 21:35:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-24632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x375D85)
Bugcheck code: 0xA (0x78, 0x2, 0x1, 0xFFFFF80002C8EC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.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 21:35:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltFindExtraCreateParameter+0x115A)
Bugcheck code: 0xA (0x78, 0x2, 0x1, 0xFFFFF80002C8EC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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.
De nouvelle erreur :
On Sun 29/01/2012 09:23:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012912-25537-01.dmp
This was probably caused by the following module: avc3.sys (avc3+0x82E0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF880010842E0, 0xFFFFF880057A5E80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\avc3.sys
product: BitDefender AVC
company: BitDefender
description: Active Virus Control filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: avc3.sys (Active Virus Control filter driver, BitDefender).
Google query: avc3.sys BitDefender SYSTEM_SERVICE_EXCEPTION
On Sun 29/01/2012 09:23:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avc3.sys (avc3!DllUnload+0x58B1)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF880010842E0, 0xFFFFF880057A5E80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\avc3.sys
product: BitDefender AVC
company: BitDefender
description: Active Virus Control filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: avc3.sys (Active Virus Control filter driver, BitDefender).
Google query: avc3.sys BitDefender SYSTEM_SERVICE_EXCEPTION
On Sun 29/01/2012 09:23:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012912-25537-01.dmp
This was probably caused by the following module: avc3.sys (avc3+0x82E0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF880010842E0, 0xFFFFF880057A5E80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\avc3.sys
product: BitDefender AVC
company: BitDefender
description: Active Virus Control filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: avc3.sys (Active Virus Control filter driver, BitDefender).
Google query: avc3.sys BitDefender SYSTEM_SERVICE_EXCEPTION
On Sun 29/01/2012 09:23:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avc3.sys (avc3!DllUnload+0x58B1)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF880010842E0, 0xFFFFF880057A5E80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\avc3.sys
product: BitDefender AVC
company: BitDefender
description: Active Virus Control filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: avc3.sys (Active Virus Control filter driver, BitDefender).
Google query: avc3.sys BitDefender SYSTEM_SERVICE_EXCEPTION
Ton disque dur ne fait pas des bruit bizarre ? Si oui c'est qu'il va bientot claquer si non c'est que s'est bon. Tu viens de formater ou pas ? Car il semblerai que un virus ou quelque chose comme ca fasse planter tes drivers et te fasse des bsod. Alors fais une analyse avec bitdefender et dit moi apres. Il semblerai avoir une incompatibilite entre CCC (catalyst) et un logiciel. Verifie tout tes logiciel que tu a installer avant avoir eu ton premier bsod.
- 1
- 2
Suivant
