Ecran bleu sans arret
maryline
-
paslau35 Messages postés 8783 Statut Membre -
paslau35 Messages postés 8783 Statut Membre -
Bonjour,
j'ai des écrans bleu sans arret, j'ai mis à jour le pilote de la carte graphique mais sans résultat.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 28/02/2013 12:12:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-18642-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x732FD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044A22FD, 0xFFFFF8800634EAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
On Thu 28/02/2013 12:12:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x16511)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044A22FD, 0xFFFFF8800634EAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
On Thu 28/02/2013 11:53:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-22417-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xDD09)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960006ADD09, 0xFFFFF8800476DF30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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.
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 that cannot be identified at this time.
On Thu 28/02/2013 11:51:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-20592-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x30, 0x2, 0x1, 0xFFFFF80002CCE35F)
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 that cannot be identified at this time.
On Thu 28/02/2013 09:15:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-22167-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41287, 0x50, 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 Thu 28/02/2013 08:51:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-48157-01.dmp
This was probably caused by the following module: rdyboost.sys (0xFFFFF880019230E5)
Bugcheck code: 0xD1 (0x5E4120C4, 0x2, 0x0, 0xFFFFF880019230E5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 27/02/2013 06:20:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-16863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 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 that cannot be identified at this time.
On Wed 27/02/2013 06:01:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-18127-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xB3C58)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC40050BC0, 0xA800, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. MEMORY_MANAGEMENT
On Wed 27/02/2013 05:49:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-18408-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003C77330, 0xFFFFF88003C773D0, 0xFFFFF80002CC6B80)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 that cannot be identified at this time.
On Wed 27/02/2013 05:34:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-16707-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF88000E3D828)
Bugcheck code: 0x50 (0xFFFFF8805A706F68, 0x1, 0xFFFFF88000E3D828, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l'infrastructure de pilotes en mode noyau
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.
On Tue 26/02/2013 15:37:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-16239-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x16700)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF88003763978, 0xFFFFF880037631D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 that cannot be identified at this time.
On Tue 26/02/2013 15:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-23509-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFF8580063906D8, 0x2, 0x1, 0xFFFFF80002CD9D6C)
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 that cannot be identified at this time.
On Tue 26/02/2013 15:32:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-24148-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
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 that cannot be identified at this time.
On Tue 26/02/2013 15:15:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-17035-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x14067)
Bugcheck code: 0xD1 (0x1860, 0x2, 0x1, 0xFFFFF8800448B067)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 26/02/2013 11:24:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-21169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFF80002405100, 0x8, 0xFFFFF80002405100, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.
j'ai des écrans bleu sans arret, j'ai mis à jour le pilote de la carte graphique mais sans résultat.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 28/02/2013 12:12:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-18642-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x732FD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044A22FD, 0xFFFFF8800634EAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
On Thu 28/02/2013 12:12:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x16511)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044A22FD, 0xFFFFF8800634EAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
On Thu 28/02/2013 11:53:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-22417-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xDD09)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960006ADD09, 0xFFFFF8800476DF30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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.
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 that cannot be identified at this time.
On Thu 28/02/2013 11:51:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-20592-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x30, 0x2, 0x1, 0xFFFFF80002CCE35F)
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 that cannot be identified at this time.
On Thu 28/02/2013 09:15:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-22167-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41287, 0x50, 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 Thu 28/02/2013 08:51:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-48157-01.dmp
This was probably caused by the following module: rdyboost.sys (0xFFFFF880019230E5)
Bugcheck code: 0xD1 (0x5E4120C4, 0x2, 0x0, 0xFFFFF880019230E5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 27/02/2013 06:20:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-16863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 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 that cannot be identified at this time.
On Wed 27/02/2013 06:01:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-18127-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xB3C58)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC40050BC0, 0xA800, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. MEMORY_MANAGEMENT
On Wed 27/02/2013 05:49:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-18408-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003C77330, 0xFFFFF88003C773D0, 0xFFFFF80002CC6B80)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 that cannot be identified at this time.
On Wed 27/02/2013 05:34:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-16707-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF88000E3D828)
Bugcheck code: 0x50 (0xFFFFF8805A706F68, 0x1, 0xFFFFF88000E3D828, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l'infrastructure de pilotes en mode noyau
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.
On Tue 26/02/2013 15:37:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-16239-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x16700)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF88003763978, 0xFFFFF880037631D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 that cannot be identified at this time.
On Tue 26/02/2013 15:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-23509-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFF8580063906D8, 0x2, 0x1, 0xFFFFF80002CD9D6C)
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 that cannot be identified at this time.
On Tue 26/02/2013 15:32:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-24148-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
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 that cannot be identified at this time.
On Tue 26/02/2013 15:15:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-17035-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x14067)
Bugcheck code: 0xD1 (0x1860, 0x2, 0x1, 0xFFFFF8800448B067)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 26/02/2013 11:24:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022613-21169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFF80002405100, 0x8, 0xFFFFF80002405100, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.
19 réponses
Résumé de la discussion
Plusieurs plantages et écrans bleus apparaissent sous Windows 7 avec les rapports de crash alignés sur des modules graphique et système, notamment dxgkrnl.sys et ntoskrnl.exe, indiquant une erreur du pilote logiciel. La tentative de mise à jour du pilote graphique a été inefficace et les traces de crash mentionnent aussi des éléments comme cdd.dll et rdyboost.sys, ce qui oriente l’analyse vers des conflits logiciel-driver. Des hypothèses utiles émergent, incluant une possible défaillance matérielle du disque ou des malfonctionnements de mémoire, mais certains éléments pointent aussi vers des drivers tiers et des questions de configuration système. En pratique, l’analyse suggère de tester les composants critiques et les câbles, examiner les rapports de dump, et envisager des mises à jour ou réinstallations de pilotes, sans conclure sur une résolution immédiate.
-
Bonjour,
Essaie de faire une restauration système en appuyant sur F8 au démarrage de ton PC-
j'ai fait réparer, ça m'a proposer de restaurer mais je n'ai pas de restauration dispo avant l'apparation des problème, j'ai donc fait redemarré le pc comme suite au plantage et j'ai eut le menu d'outils de réparation ou je sais plus trop quoi ou j'ai eut restauration de windows et ça a fait un truc tout seul. Je ne sais pas si c'est bon, on va attendre voir si les écran bleu reviennent
-
-
met tes driver à jour parce que les driver irql c'est souvent ça la cause pour els autres passerait un memtest sur tes mémoires et tant qu'à faire un test de DD avec hd tune par exemple :)
-
-
-
-
même si plus accès au windows il y a des moyen comme démarrer sur un live cd et lancer le programme hdtune pour le dd par exemple.... et puis le memtest c'est un live cd aussi lol donc pas besoin accès au windows :)
grave un hiren boot cd par exemple tu pourra alors demarrer sur un xp en live cd et de là lancer un hdtune par exemple
et si ton pc en plante pas en live cd c'est que c'est déjà presque sur que c'est l'os :)
mais test d'abord tes ram :)
-
-
j'ai commencé par hd tune car plus simple que de trouvé un cd vierge ou une clé usb :)
mais j'y comprends pas grande chose dans health j'ai un warning :
Ultra DMA CRC Error Count : current 100 worst 99 threshold 0 data 11200
Number of interface communication errors : 11200
There were communication errors. This may be caused by a damaged cable.
Le cable de branchement de mon dd est abimé ? -
je partirai plus sur un prob hardware de ton disque les têtes...en gros ton dd est mourru :s
sinon test un autre cable et autre connecteur sur ta carte mère mais j'ai des doutes.... -
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question -
je viens de finir le memtest aucune erreur.
Donc les écran bleu viendrais du disque dur ?
sinon j'ai des scintillement sur l'écran souvent -
-
On Sat 02/03/2013 18:45:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030213-26176-01.dmp
This was probably caused by the following module: cdrom.sys (0xFFFFF880013E39E9)
Bugcheck code: 0x50 (0xFFFFFA804D15E254, 0x1, 0xFFFFF880013E39E9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\cdrom.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI CD-ROM Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.
On Sat 02/03/2013 18:45:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cdrom.sys (cdrom+0x1F9E9)
Bugcheck code: 0x50 (0xFFFFFA804D15E254, 0x1, 0xFFFFF880013E39E9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\cdrom.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI CD-ROM Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.
-
-
Bonjour, regarde mon post avec même sujet moi ça a marché.
-
bjr
aux début ça parler de diectx
ton dernier parle de drives de ton CD-rom
je pense que ton pc et bien malade et
une réinstalle complète s impose
comme ça tu serra fixe
tu a quoi comme protection sur ce pc ,,,,,,,,,,,
-
Mais non de nombreuses personnes ont le même problème suite à une mise à jour de microsoft
-
vieu bison boiteu Messages postés 44334 Date d'inscription Statut Contributeur Dernière intervention Ambassadeur 3 591
salut maryline
dans Ordinateur ( ou Poste de travail ) , tu cliques "droit" sur le disque "C:\" => Propriétés => Outils => Vérification des erreurs => Vérifier maintenant => tu coches les deux cases => Redémarrer
il y aura un écran bleu de scanne pendant 10 à 30 mn suivant le volume
( jusqu'à 2 heures et plus pour un volume de 1 To )
à+ -
vieu bison boiteu Messages postés 44334 Date d'inscription Statut Contributeur Dernière intervention Ambassadeur 3 591
dxgkrnl.sys = > directX
met à jour directX , tu télécharges et tu exécutes
http://www.microsoft.com/fr-fr/download/details.aspx?id=35
usbport.sys = tu as Windows XP ??? -
-
comme je l ais dit aux début
je pense q une réinstalle de ton pc serais bien a prévoir
tu a quelle marque de pc ,,,, ou pas
fixe ou portable
et puits un antivirus de nos jours ne suffit plus
-
-
-
vieu bison boiteu Messages postés 44334 Date d'inscription Statut Contributeur Dernière intervention Ambassadeur 3 591
<<<...il faut désactiver le redémarrage auto ...>>>
OK
mais comment ???
elle n' arrive pas sur le "Bureau" , même en mode sans échec -
vieu bison boiteu Messages postés 44334 Date d'inscription Statut Contributeur Dernière intervention Ambassadeur 3 591
si tu arrives à installer Windows , ta carte graphique fonctionne
aussi , ton DVD de Windows ne serait pas rayé ??? -
non j'ai installé avec une clé usb :p mais je ne vois pas le rapport....
car mon windows s'est mis a planté d'un coup et j'ai fait une réinstalle et ça a planté après donc pas de rapport avec le dvd de windows -
comment tu peux lancer une réinstallation d'un windows qui vient d'un autre PC sur celui là?? c'est normal qu'il plante si le système ne reconnait pas le matériel qui lui est dédié...
-
-
-
-
a ok
quand ont sais reconnaitre c est erreurs ,,,,
Maryline comme je vois que tu a des soucis pour trouver une C G
moi quand il manque de pièces pour tester des pannes
je fais comme suit
je commende sur https://www.amazon.fr/
l avantage avec eux c est les retours jamais de soucis
par contre bien prendre avec amazon pas avec un partenaires
et bien le dire avant 7 jours
comme ça tu pourrais tester une C G
une idée ,,,,,,,,,, -
-
