Forum-seven : Communauté francaise de Windows 7

Bonjour
Depuis au moins 1 mois après chaque mise de windows 7 64 bits , à l'extinction du PC , celui-ci redémarre automatiquement avec un écran bleu en cours de reboot . Ensuite une fenêtre windows apparaît pour signaler le problème et envoie à Microsoft .
Après tout semble normal .
Cet incident est encore arrivé hier après les 12 MAJ et ce matin après les 6 MAJ .
Pouvez-vous me dire ce qui se passe et ce qu'il faut faire pour corriger .
Merci d'avance pour votre aide

Bonjour,
WhoCrashed Home Edition 3.01 de Resplendence

Tu l'installes et tu le lances par Analyze.
Tu postes un copier-coller de ce qui apparait .
Le rapport LOCALT~11.html sera dans le dossier du programme WhoCrashed.
@+

Merci Nardino
Voici le rapport .
Ce sont les crash du 15/11 qui m'intéresse car les précédents étaient dûs à ma carte graphique ASUS Nvidia GTX 460 que j'ai remplacé par une Gigabyte GTX 560 .

System Information (local)
--------------------------------------------------------------------------------

computer name: PC-LIAN-LI
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17080266752 total
VM: 2147352576, free: 1944498176




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 15/11/2012 21:41:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111512-23197-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800038F4F74)
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 15/11/2012 21:41:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x15995)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800038F4F74)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 that cannot be identified at this time.



On Thu 15/11/2012 08:08:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111512-51293-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000389CDF5)
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 Sat 13/10/2012 06:51:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101312-24741-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800038EBFF5)
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 26/07/2012 18:02:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-27705-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x4F444648, 0x2, 0x0, 0xFFFFF800038FBFF5)
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 Wed 13/06/2012 13:23:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061312-45801-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1ABB05)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800039CAB05, 0xFFFFF88003B692A8, 0xFFFFF88003B68B00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/04/2012 13:43:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-23197-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15064)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800039F9B05, 0xFFFFF88003B85438, 0xFFFFF88003B84C90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Sun 26/02/2012 17:21:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022612-48001-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 that cannot be identified at this time.



On Sun 26/02/2012 11:02:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022612-16582-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x4F444648, 0x2, 0x0, 0xFFFFF800036EE5B5)
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 Sat 25/02/2012 21:57:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022512-16816-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000369F734)
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 Sat 25/02/2012 21:53:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022512-16192-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800036975B5)
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 Fri 24/02/2012 23:13:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022512-47751-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x4F444648, 0x2, 0x0, 0xFFFFF800036AC5B5)
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 Fri 24/02/2012 22:18:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022412-32604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800036AE5B5)
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 Fri 24/02/2012 21:28:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022412-19219-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x4F444648, 0x2, 0x0, 0xFFFFF8000369F5B5)
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 Wed 22/02/2012 20:46:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-47018-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800036F55B5)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

30 crash dumps have been found and analyzed. Only 15 are included in this report.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Bonjour,
Vérifie dans le gestionnaire de périphériques que l'un d'eux ne pose pas problème.
@+

Non tout semble correct : je n'ai pas de point d'interrogation , même dans les phériphériques cachés

Bonsoir,
A voir, si les ports usb sont occupés débranche les tous et redémarre pour voir .

Une petite précision .
Je n'ai pas eu que des écrans bleus lors de la dernière MAJ de Windows 7. Sinon pas d'écran bleu en temps normal .

Bonsoir,
Alors voir les dernières mises à jour dans windows update pour savoir laquelle aurait engendrée ces écrans bleus (peut-être des Maj de périphériques) .
Car, dans ton rapport il y a bug Pilote de port USB 1.1 & 2.0

Merci grimpeur .
C'est quand même bizarre que dans la liste des périphériques , tout apparaît comme semblant fonctionner normalement .
Il y a quelques mois quand j'avais de soucis d'écran bleu , j'avais télécharger un autre logiciel "Bluescreen " que vous connaissez peut-être et qui mettait en évidence un problème .
ntoskrnl.exe et Kernel & System
qui semblait mettre en cause ma carte graphique .
Avec le logiciel que vous m'avez indiqué ici , je retrouve également ce problème .

Bonsoir,
Quelle est la référence de ta carte graphique dans le gestionnaire des périphériques (clique dessus pour aller vers pilote et donne la date et la version) .
Egalement dans la même page (gestionnaire), développe controleur de bus usb et post ce qui est présent sur le pc.