Depuis 2 jours, je n'arrive plus à allumer mon ordinateur, un BSOD arrive de suite "IRQL_NOT_LESS_OR_EQUAL".
Je n'arrive à accéder à mon bureau Windows 7 seulement en "mode sans échec avec prise en charge réseau".
Auparavant, j'ai eu aussi assez régulièrement des BSOD mais rien qui ne m’empêchais d'allumer mon ordinateur.
Comme conseillé, j'ai téléchargé le logiciel "Whocrashed" et j'ai effectué l'analyse, que voici:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 14/02/2011 12:50:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021411-19016-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x90BD4)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFFFFF82C7EB69)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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.
Google query: dxgkrnl.sys Microsoft Corporation IRQL_NOT_LESS_OR_EQUAL
On Mon 14/02/2011 12:50:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x321B)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFFFFF82C7EB69)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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.
Google query: dxgkrnl.sys Microsoft Corporation IRQL_NOT_LESS_OR_EQUAL
On Sun 13/02/2011 13:58:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021311-17472-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120996)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAA2B6A80, 0xFFFFFFFFA470ADD0, 0xFFFFFFFFA4073810)
Error: BAD_POOL_HEADER
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 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 Fri 11/02/2011 16:58:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021111-18252-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFF8B45D543, 0x0, 0x0, 0xFFFFFFFF82CC4631)
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 Wed 02/02/2011 18:55:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020211-31465-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120067)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D2D067, 0xFFFFFFFF95E75AAC, 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 Wed 02/02/2011 18:54:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020211-23992-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88738478, 0xFFFFFFFF887386E8, 0xA4E080B)
Error: BAD_POOL_HEADER
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 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 Wed 02/02/2011 18:48:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020211-20716-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x99227)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA5043138, 0xFFFFFFFFA50433F0, 0xA570208)
Error: BAD_POOL_HEADER
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 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 Wed 02/02/2011 18:47:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020211-17830-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x747AD)
Bugcheck code: 0xDE (0x2, 0xFFFFFFFFB30EB278, 0xFFFFFFFFA6B76249, 0x2F5918C4)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 27/01/2011 16:38:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-17815-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120996)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFA773DC70, 0xFFFFFFFFAE007400, 0x31002E00)
Error: BAD_POOL_HEADER
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 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 Tue 25/01/2011 17:54:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16161-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x73EC5, 0x2, 0x73E84)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Sun 16/01/2011 19:18:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-21949-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA253D238, 0xFFFFFFFFA253D4D0, 0xA530201)
Error: BAD_POOL_HEADER
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 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 Sun 16/01/2011 19:16:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-15724-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFFFFA474FD00)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 16/01/2011 19:14:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-16738-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA7590)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC000A038, 0x23443867, 0xFFFFFFFFC047A050)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Sun 16/01/2011 19:09:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-17128-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA7590)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC00324B8, 0x42F8E867, 0xFFFFFFFFC0000002)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Sun 16/01/2011 19:07:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-16192-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA2245EB8, 0xFFFFFFFFA22460D0, 0xA43060D)
Error: BAD_POOL_HEADER
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
20 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:
dxgkrnl.sys (DirectX Graphics Kernel, Microsoft Corporation)
dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
J'ai moi même effectué quelques recherche mais je n'ai rien trouvé de concluant.
En espérant que quelqu’un puisse m'aider
Je vous remercie d'avance,
Nko78
