Maiwen77
Nouveau membre
Bonjour,
Je ne sais pas si mon message est dans la bonne section, dans le cas contraire, je m'en excuse et vous demanderai de le déplacer au bon endroit.
Cela fait une semaine et demi maintenant que j'ai des écrans bleu sur mon pc (Toshiba Satellite L450D) il tourne sur un Windows 7 en version 64 Bits.
J'ai tenté un formatage complet, mais le problème est toujours présent.
J'ai essayé de faire un test de mémoire avec l’outil intégré à windows, mais l'ordinateur s'éteint à la moitié du test... donc impossible de faire le test.
J'ai chargé Memtest86+ sur une clé usb et si mes souvenirs sont bons je crois qu'il m'avait rapporté une liste d'erreur. Je vais attendre vos consignes et si besoin j'en referai un.
A savoir que je rédige actuellement mon message avec ce pc, que la température du processeur est de 60° et celle du disque-dur est de 36°
Merci à ceux qui pourront m'aider à identifier la panne.
Ci-joint en dessous une copie de WhoCrashed.
Cordialement
-----
Voici une copie de WhoCrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 20/06/2013 03:58:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF800028DB692)
Bugcheck code: 0xA (0x40000000000, 0x2, 0x0, 0xFFFFF800028DB692)
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.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Thu 20/06/2013 03:32:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-47299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF8800096B1E0, 0x0, 0xFFFFF8800096B1E0)
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 that cannot be identified at this time.
On Thu 20/06/2013 00:56:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-51870-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028DAE6F, 0xFFFFF88001FA8B50, 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 that cannot be identified at this time.
On Wed 19/06/2013 22:38:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-66066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8000288DE47, 0xFFFFF88002758E40, 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 that cannot be identified at this time.
On Wed 19/06/2013 15:27:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-46956-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000288CB05, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.
On Wed 19/06/2013 14:56:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-43196-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0xA)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000288E990)
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 Wed 19/06/2013 14:52:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-41558-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41287, 0x80, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Wed 19/06/2013 03:13:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-45661-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00723CB40, 0xFFFFF8A00723CB40, 0xFFFFF8A00723DB40)
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 that cannot be identified at this time.
Je ne sais pas si mon message est dans la bonne section, dans le cas contraire, je m'en excuse et vous demanderai de le déplacer au bon endroit.
Cela fait une semaine et demi maintenant que j'ai des écrans bleu sur mon pc (Toshiba Satellite L450D) il tourne sur un Windows 7 en version 64 Bits.
J'ai tenté un formatage complet, mais le problème est toujours présent.
J'ai essayé de faire un test de mémoire avec l’outil intégré à windows, mais l'ordinateur s'éteint à la moitié du test... donc impossible de faire le test.
J'ai chargé Memtest86+ sur une clé usb et si mes souvenirs sont bons je crois qu'il m'avait rapporté une liste d'erreur. Je vais attendre vos consignes et si besoin j'en referai un.
A savoir que je rédige actuellement mon message avec ce pc, que la température du processeur est de 60° et celle du disque-dur est de 36°
Merci à ceux qui pourront m'aider à identifier la panne.
Ci-joint en dessous une copie de WhoCrashed.
Cordialement
-----
Voici une copie de WhoCrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 20/06/2013 03:58:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF800028DB692)
Bugcheck code: 0xA (0x40000000000, 0x2, 0x0, 0xFFFFF800028DB692)
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.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Thu 20/06/2013 03:32:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-47299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF8800096B1E0, 0x0, 0xFFFFF8800096B1E0)
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 that cannot be identified at this time.
On Thu 20/06/2013 00:56:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-51870-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028DAE6F, 0xFFFFF88001FA8B50, 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 that cannot be identified at this time.
On Wed 19/06/2013 22:38:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-66066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8000288DE47, 0xFFFFF88002758E40, 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 that cannot be identified at this time.
On Wed 19/06/2013 15:27:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-46956-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000288CB05, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.
On Wed 19/06/2013 14:56:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-43196-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0xA)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000288E990)
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 Wed 19/06/2013 14:52:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-41558-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41287, 0x80, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Wed 19/06/2013 03:13:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-45661-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00723CB40, 0xFFFFF8A00723CB40, 0xFFFFF8A00723DB40)
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 that cannot be identified at this time.