Ecran bleu, rapport d'analyse, aidez moi svp :)
Fermé
SamiGH
Messages postés
5
Date d'inscription
mercredi 14 octobre 2015
Statut
Membre
Dernière intervention
1 novembre 2015
-
14 oct. 2015 à 15:05
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 1 nov. 2015 à 11:16
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 1 nov. 2015 à 11:16
A voir également:
- Ecran bleu, rapport d'analyse, aidez moi svp :)
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Capture d'écran samsung - Guide
- Retourner ecran windows - Guide
6 réponses
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 665
14 oct. 2015 à 15:07
14 oct. 2015 à 15:07
Salut,
Tu n'aurais pas mis à jour tes pilotes NVidia récemment ?
Tu n'aurais pas mis à jour tes pilotes NVidia récemment ?
SamiGH
Messages postés
5
Date d'inscription
mercredi 14 octobre 2015
Statut
Membre
Dernière intervention
1 novembre 2015
14 oct. 2015 à 16:48
14 oct. 2015 à 16:48
Salut,
oui je les mets à jour quotidiennement, j'ai peut-être fais 2 ou 3 MaJ depuis que j'ai ces soucis d'écran bleu
oui je les mets à jour quotidiennement, j'ai peut-être fais 2 ou 3 MaJ depuis que j'ai ces soucis d'écran bleu
SamiGH
Messages postés
5
Date d'inscription
mercredi 14 octobre 2015
Statut
Membre
Dernière intervention
1 novembre 2015
14 oct. 2015 à 16:48
14 oct. 2015 à 16:48
dont une aujourd'hui, entre deux écrans bleus
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 665
14 oct. 2015 à 16:56
14 oct. 2015 à 16:56
Fais une restauration du système antérieure à 2 semaines si tu peux pour voir.
SamiGH
Messages postés
5
Date d'inscription
mercredi 14 octobre 2015
Statut
Membre
Dernière intervention
1 novembre 2015
14 oct. 2015 à 23:08
14 oct. 2015 à 23:08
la restauration système a pas fonctionnée. ça a rencontré une erreur indeterminée...
pour résoudre mon problème je devrais peut etre mettre a jour mon BIOS je pense, non? sauf que je sais pas comment faire
pour résoudre mon problème je devrais peut etre mettre a jour mon BIOS je pense, non? sauf que je sais pas comment faire
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 665
15 oct. 2015 à 08:08
15 oct. 2015 à 08:08
Tu peux toujours tenter pour le BIOS.
Regarde aussi les conseils de ce sujet : Comprendre les BSOD.
Tenter de désinstaller l'antivirus.
Démarrer en Windows minimal etc.
Regarde aussi les conseils de ce sujet : Comprendre les BSOD.
Tenter de désinstaller l'antivirus.
Démarrer en Windows minimal etc.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
SamiGH
Messages postés
5
Date d'inscription
mercredi 14 octobre 2015
Statut
Membre
Dernière intervention
1 novembre 2015
1 nov. 2015 à 01:15
1 nov. 2015 à 01:15
Salut,
les messages bleus continuent, je sais pas comment m'y prendre...
le crash test:
On Sun 01.11.2015 00:09:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110115-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D453A, 0x0, 0xB4EF8D4BF43F4161, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Sat 31.10.2015 17:34:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103115-19578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D3820, 0x0, 0x4D92E00435CBE66, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 30.10.2015 00:54:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103015-16629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D8584, 0x0, 0x24EA3ED5CD7871ED, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 29.10.2015 09:20:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102915-15600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800377E688, 0xFFFFF8800377DEE0, 0xFFFFF80002F7E20B)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 Tue 27.10.2015 21:31:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102715-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFF80003400000, 0x0, 0xFFFFFA800CD5769B, 0x2)
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.
On Fri 23.10.2015 22:42:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102415-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D134F0)
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 Mon 19.10.2015 20:26:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-11544-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xD1 (0xFFFFF8C000EBA1B0, 0x2, 0x8, 0xFFFFF8C000EBA1B0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 17.10.2015 12:20:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D66F4, 0x0, 0xECF148203AE9B41, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.
les messages bleus continuent, je sais pas comment m'y prendre...
le crash test:
On Sun 01.11.2015 00:09:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110115-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D453A, 0x0, 0xB4EF8D4BF43F4161, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Sat 31.10.2015 17:34:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103115-19578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D3820, 0x0, 0x4D92E00435CBE66, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 30.10.2015 00:54:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103015-16629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D8584, 0x0, 0x24EA3ED5CD7871ED, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 29.10.2015 09:20:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102915-15600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800377E688, 0xFFFFF8800377DEE0, 0xFFFFF80002F7E20B)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 Tue 27.10.2015 21:31:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102715-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFF80003400000, 0x0, 0xFFFFFA800CD5769B, 0x2)
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.
On Fri 23.10.2015 22:42:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102415-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D134F0)
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 Mon 19.10.2015 20:26:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-11544-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xD1 (0xFFFFF8C000EBA1B0, 0x2, 0x8, 0xFFFFF8C000EBA1B0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 17.10.2015 12:20:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D66F4, 0x0, 0xECF148203AE9B41, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 665
1 nov. 2015 à 11:16
1 nov. 2015 à 11:16
Problème matériel, barrette de mémoire endommage apparemment.
Utilisateur anonyme
Modifié par FISQ le 1/11/2015 à 02:04
Modifié par FISQ le 1/11/2015 à 02:04
Bonsoir,
driver incompatible peut afficher un écran BSOD
programme incompatible peut afficher un écran BSOD exemple un jeux gourmand en pixel processeurs , RAM , carte graphique ne supportent pas le jeux
matériel incompatible peut afficher un écran BSOD exemple ajout d'une barrette de mémoire ou modification de la carte graphique etc
anomalie fichiers du système peut afficher un écran BSOD
anomalie dans le disque dur principal peut afficher un écran BSOD
depuis quelques jours que votre écran affiche plusieurs fois un BSOD vous avez modifié quelque chose dans le système " machine "
vous n'avez rien modifier ni pousser Windows a se crasher alors c'est un problème HARDWARE le plus souvent dans la ligne de mire le disque dur principal de temps en temps une barrette qui jette l'éponge , parfois un ventilateur qui a du mal a évacuer la chaleur , une petite pincée de hausse de chaleur exemple ->CPU Pâte thermique .
driver incompatible peut afficher un écran BSOD
programme incompatible peut afficher un écran BSOD exemple un jeux gourmand en pixel processeurs , RAM , carte graphique ne supportent pas le jeux
matériel incompatible peut afficher un écran BSOD exemple ajout d'une barrette de mémoire ou modification de la carte graphique etc
anomalie fichiers du système peut afficher un écran BSOD
anomalie dans le disque dur principal peut afficher un écran BSOD
depuis quelques jours que votre écran affiche plusieurs fois un BSOD vous avez modifié quelque chose dans le système " machine "
vous n'avez rien modifier ni pousser Windows a se crasher alors c'est un problème HARDWARE le plus souvent dans la ligne de mire le disque dur principal de temps en temps une barrette qui jette l'éponge , parfois un ventilateur qui a du mal a évacuer la chaleur , une petite pincée de hausse de chaleur exemple ->CPU Pâte thermique .