Ecran bleu sur W10 au bout de 10/15mn d'innactivitée

Recherche :

Mot : Pseudo : Filtrer
Bas de page
Auteur	Sujet : Ecran bleu sur W10 au bout de 10/15mn d'innactivitée

shakaah

Bonjour a tous,

Je commence par me présenter moi et mon pc,
Je me fait surnommer shakaah, je suis de Montpellier et j'ai 35 ans.

Mon pc est composer de :
un i5-2500 a 3.30Ghz
16Go de Ram
Windows 10 64Bit
Une GTX 760 2Go Gigabit avec 2 écrans iiyama

Son utilité première : Jeux, Twitch (Live), Internet, Vidéo (création)

Mon problème depuis le 9/03/2016, date de la mise à jour buggé de Nvidia (je ne suis pas sur que le problème vienne de lui mais c'est une possibilité), et date de la mise a jour Windows KB3140768 (ce sont les deux seules modification que mon pc a eu ce jour là), est assez compliquer a expliquer.
Mon pc fonctionne très bien tant que je l'utilise, si par malheur je doit être AFK pendant une durée entre 10 et 15 minutes, quand je reviens un jolie écran bleu "REGISTRY ERROR"
Si quand je m'absente je met une vidéo en plein écran et même pendant une nuit complète, l'erreur ne se produit pas, en jeu ou en surfant, pas d'erreur, il faut vraiment que mon ordi n'ai rien a faire pendant environ 10mn pour que l’écran bleu se produise.

J'ai testé les manipulation suivante, sans succès, d'où mon appel a l'aide ici, car j'aimerai éviter une réinstallation complète.

- Désinstallation et réinstallation des drivers Nvidia en mettant la version corrigée
- Désactivation de tout les paramètre de veille (écran, disque dur, usb)
- Scan complet antivirus - RAS

Si quelqu'un aurais l'amabilité de m'aider à trouver une solution ...
Si vous avez besoin d'information complémentaire je suis aussi disponible.

Merci d'avance

Publicité

nex84

Dura lex, sed lex

Lance l'utilitaire whocrashed et envoie nous le rapport.

Sinon teste ta mémoire (avec memtest) et tes disques durs (avec crystaldiskinfo)

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

shakaah

Merci pour ta réponse Nex84.

Voici pour commencer le rapport de Whocrashed, j'essaye de m'occuper du memtest dès que possible, pour les disques dur se sont des SSD sauf 1, est-ce nécessaire de lancer crystaldiskinfo sur du ssd?

Citation :

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

Computer name: xxxxxx
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASUSTeK Computer INC., P8Z68-V GEN3
CPU: GenuineIntel Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17156034560 bytes total

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 13/03/2016 12:31:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031316-8843-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC00176D22000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 13/03/2016 12:31:02 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC00176D22000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 12/03/2016 09:58:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031216-8828-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC001CD12F000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 11/03/2016 14:56:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031116-9125-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC000A7914000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 11/03/2016 14:43:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031116-8968-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC000A9540000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 10/03/2016 23:23:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031116-9156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC001451A3000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 10/03/2016 16:33:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031016-8953-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC00013F21000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 10/03/2016 07:13:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031016-8984-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC001D292A000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 09/03/2016 15:27:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030916-9156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC0019E79B000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 09/03/2016 15:14:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030916-9109-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFC0000E7C1000, 0xC9E8770D, 0x2D2)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

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

11 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

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.

nex84

Dura lex, sed lex

Le registre de Windows est stocké sous forme de fichier.
Du coup un problème d'accès au disque au sens large pourrait provoquer cette erreur.

Sinon vérifie :
- les potentielles erreurs dans les journaux d'évenements
- l'intégrité de Windows avec la commande :

Code :

SFC /SCANNOW

Vu que tu connais la date à partir de laquelle le problème est survenu, tu peux essayer de restaurer à une date antérieure.

Message cité 1 fois

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

shakaah

nex84 a écrit :

Vu que tu connais la date à partir de laquelle le problème est survenu, tu peux essayer de restaurer à une date antérieure.

Malheureusement restauration désactivée

Je m'occupe des autres scan demandé et vous tien au courant

edit : SFC ->

Citation :

Microsoft Windows [version 10.0.10586]
(c) 2015 Microsoft Corporation. Tous droits réservés.

C:\WINDOWS\system32>SFC /SCANNOW

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.

Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.

C:\WINDOWS\system32>

Message édité par shakaah le 14-03-2016 à 18:00:54

shakaah

bonjour, comment puis je faire un memtest sur w10?

FORUM HardWare.fr

Windows & Software

Win 10

Ecran bleu sur W10 au bout de 10/15mn d'innactivitée

Sujets relatifs
Reinstallation de W10 ??	Freeze/Ecran Noir après upgrade processeur vers i5-3570K
recuperer un fond d'écran	ASUS P7P55D - Crash après sleep mode (écran noir)
Ecran Bleu de la mort Windows 7	Migration Outlook Express XP > Outlook W10
Réinitialisation W10 après update	W10 quelle taille?
[W10] Hôte de service: Système locale qui me bouffe toute ma co
Plus de sujets relatifs à : Ecran bleu sur W10 au bout de 10/15mn d'innactivitée

Page générée en 0.058 secondes