Ordinateur qui pars sur un écran bleu
Fermé
Mista No
-
22 mars 2017 à 19:37
luckydu43 Messages postés 3484 Date d'inscription vendredi 9 janvier 2015 Statut Membre Dernière intervention 30 juin 2022 - 23 mars 2017 à 23:49
luckydu43 Messages postés 3484 Date d'inscription vendredi 9 janvier 2015 Statut Membre Dernière intervention 30 juin 2022 - 23 mars 2017 à 23:49
A voir également:
- Ordinateur qui pars sur un écran bleu
- Ordinateur qui rame - Guide
- Double ecran - Guide
- Ordinateur ecran noir - Guide
- Écran bleu - Guide
- Comment réinitialiser un ordinateur - Guide
2 réponses
luckydu43
Messages postés
3484
Date d'inscription
vendredi 9 janvier 2015
Statut
Membre
Dernière intervention
30 juin 2022
815
22 mars 2017 à 20:09
22 mars 2017 à 20:09
Bonjour !
Demander si les pilotes sont à jour me paraît inutile (vous semblez connaitre un peu le milieu) mais tant pis. Je pose la question :-D
Vos pilotes sont-ils à jour ?
Ensuite.
L'idée c'est de savoir la cause du bazar. Installez Whocrashed, manipez sur votre pc, et une fois que le BSOD se produit, juste après le redémarrage...
- lancez le logiciel
- Cliquez sur Analyse
- Copiez-collez le rapport en réponse à mon message ;-)
Si vos dumps sont désactivés (et faut pas pour ce cas), je vous laisse lire ce qui suit :
Menu démarrer > clique droit sur Ordinateur > Propriétés > Paramètres systèmes avancés (sur la gauche) > dans la partie "démarrage et récupération, cliquer sur "Paramètres..." > Sélectionner "Image mémoire du noyau et décocher "Redémarrer automatiquement".
Bonne journée
Luc
Demander si les pilotes sont à jour me paraît inutile (vous semblez connaitre un peu le milieu) mais tant pis. Je pose la question :-D
Vos pilotes sont-ils à jour ?
Ensuite.
L'idée c'est de savoir la cause du bazar. Installez Whocrashed, manipez sur votre pc, et une fois que le BSOD se produit, juste après le redémarrage...
- lancez le logiciel
- Cliquez sur Analyse
- Copiez-collez le rapport en réponse à mon message ;-)
Si vos dumps sont désactivés (et faut pas pour ce cas), je vous laisse lire ce qui suit :
Menu démarrer > clique droit sur Ordinateur > Propriétés > Paramètres systèmes avancés (sur la gauche) > dans la partie "démarrage et récupération, cliquer sur "Paramètres..." > Sélectionner "Image mémoire du noyau et décocher "Redémarrer automatiquement".
Bonne journée
Luc
Mistano
Messages postés
1
Date d'inscription
mercredi 22 mars 2017
Statut
Membre
Dernière intervention
23 mars 2017
23 mars 2017 à 17:03
23 mars 2017 à 17:03
Bonjour,
A première vue, mes drivers ont l'air à jour, je vous donne la réponse du logiciel :
System Information (local)
Computer name: ANONYMOUS
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-PRO
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17118597120 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 17/02/2017 12:17:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021717-14968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x69B75)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803B5AF1B75, 0xFFFFB181EC089158, 0xFFFFB181EC088980)
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 Fri 17/02/2017 12:17:37 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x4C1F7)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803B5AF1B75, 0xFFFFB181EC089158, 0xFFFFB181EC088980)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f37f8f12da8b10d7\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 378.92
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 378.92
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 378.92 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Wed 15/02/2017 17:17:16 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021517-9875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8001DE77B75)
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 15/02/2017 17:05:58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021517-9640-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x69B75)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8024A2F3B75, 0xFFFFC2007A824158, 0xFFFFC2007A823980)
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 Wed 15/02/2017 00:39:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021517-9640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x69B75)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801F287DB75, 0xFFFFD20103F10158, 0xFFFFD20103F0F980)
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.
Conclusion
10 crash dumps have been found and analyzed. Only 5 are included in this report. 2 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:
_hid_0738_1714.sys (Saitek Hid Driver, Saitek)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 378.92 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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 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.
Paramètres réglés comme demandé mais sans résolution du problème.
Cordialement
Mista No
A première vue, mes drivers ont l'air à jour, je vous donne la réponse du logiciel :
System Information (local)
Computer name: ANONYMOUS
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-PRO
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17118597120 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 17/02/2017 12:17:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021717-14968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x69B75)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803B5AF1B75, 0xFFFFB181EC089158, 0xFFFFB181EC088980)
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 Fri 17/02/2017 12:17:37 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x4C1F7)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803B5AF1B75, 0xFFFFB181EC089158, 0xFFFFB181EC088980)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f37f8f12da8b10d7\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 378.92
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 378.92
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 378.92 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Wed 15/02/2017 17:17:16 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021517-9875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8001DE77B75)
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 15/02/2017 17:05:58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021517-9640-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x69B75)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8024A2F3B75, 0xFFFFC2007A824158, 0xFFFFC2007A823980)
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 Wed 15/02/2017 00:39:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\021517-9640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x69B75)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801F287DB75, 0xFFFFD20103F10158, 0xFFFFD20103F0F980)
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.
Conclusion
10 crash dumps have been found and analyzed. Only 5 are included in this report. 2 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:
_hid_0738_1714.sys (Saitek Hid Driver, Saitek)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 378.92 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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 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.
Paramètres réglés comme demandé mais sans résolution du problème.
Cordialement
Mista No
luckydu43
Messages postés
3484
Date d'inscription
vendredi 9 janvier 2015
Statut
Membre
Dernière intervention
30 juin 2022
815
23 mars 2017 à 23:49
23 mars 2017 à 23:49
Ok !
Ça me donne une impression de déjà vu tout ça... ntoskrnl.exe, nvlddmkm.sys...
A vue de nez, problème de RAM ET/OU de pilote graphique.
Téléchargez la version la plus stable d'après le site de nVidia concernant votre carte/chipset graphique.
Désinstallez proprement le logiciel Geforce Experience ainsi que son driver
Passez ensuite par la case "gestionnaire de périphériques" (en tapant devmgmt.msc sous Win + R si vous avez la flemme de chercher où c'est ;-) ) et :
Désinstallez la carte graphique et les pilotes des écrans. Vous inquiétez pas, les pilotes Microsoft prendront la relève.
Redémarrez
Installez le pilote graphique que vous avez téléchargé.
Si le problème persiste, on passe à la RAM.
Pour ce qui est de la RAM...
Si vous avez 1 barrette, essayez de la changer de slot.
SI vous avez 2 barrettes ou plus :
gardez une seule barrette.
Si ça persiste, changez le slot
Si ça persiste, c'est que les slots sont hors de cause. Essayez avec une autre barrette.
Aussi, rien n'empêche de faire un Memtest x86 en gardant en tête qu'il peut laisser passer des barrettes défectueuses (true story) même après 4 passages.
Ça me donne une impression de déjà vu tout ça... ntoskrnl.exe, nvlddmkm.sys...
A vue de nez, problème de RAM ET/OU de pilote graphique.
Téléchargez la version la plus stable d'après le site de nVidia concernant votre carte/chipset graphique.
Désinstallez proprement le logiciel Geforce Experience ainsi que son driver
Passez ensuite par la case "gestionnaire de périphériques" (en tapant devmgmt.msc sous Win + R si vous avez la flemme de chercher où c'est ;-) ) et :
Désinstallez la carte graphique et les pilotes des écrans. Vous inquiétez pas, les pilotes Microsoft prendront la relève.
Redémarrez
Installez le pilote graphique que vous avez téléchargé.
Si le problème persiste, on passe à la RAM.
Pour ce qui est de la RAM...
Si vous avez 1 barrette, essayez de la changer de slot.
SI vous avez 2 barrettes ou plus :
gardez une seule barrette.
Si ça persiste, changez le slot
Si ça persiste, c'est que les slots sont hors de cause. Essayez avec une autre barrette.
Aussi, rien n'empêche de faire un Memtest x86 en gardant en tête qu'il peut laisser passer des barrettes défectueuses (true story) même après 4 passages.
