Problème Ecran Bleu

salut

donne la marque et le modèle de ton pc

son OS (W10 ou autres)

télécharge et exécute Whocrashed --> clique ici

et poste le rapport via 1 copier/coller

@+

Bonjour, je ne sais pas comment on peux voir le modèle donc je t'envoie le lien du pc que j'ai pris ^^
Lien du site :
https://www.amazon.fr/gp/product/B017Z4RWW2/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

re

c'est 1 pc monté?

il faut le nom de la carte mère

tu n'as pas posté le rapport de Whocrashed

@+

Voici le rapport : Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 18/08/2021 18:54:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081821-28671-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x1, 0x1A7AFD65, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

On Wed 18/08/2021 18:54:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x1, 0x1A7AFD65, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

On Wed 18/08/2021 17:55:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081821-52390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x139 (0x3, 0xFFFFA18B9EC5A050, 0xFFFFA18B9EC59FA8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\080121-25171-01.dmp
C:\WINDOWS\Minidump\073021-29062-01.dmp
C:\WINDOWS\Minidump\072721-29218-01.dmp
C:\WINDOWS\Minidump\072321-26781-01.dmp
C:\WINDOWS\Minidump\072221-26468-01.dmp
Conclusion

8 crash dumps have been found and analyzed. Only 3 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.

re

dans recherche, tape WINVER et clique sur ouvrir

donne moi la version de W10

exemple



@+

Voilà

re

tu as la dernière version de W10, et ton souci provient d'1 pilote non à jour ou d'1 souci matériel

clique droit sur Démarrer --> Gestionnaire de périphériques

regarde si tu as des alertes (/!\ ou ?) jaune et poste 1 capture d'écran

@+

Je n'en ai pas trouver d'alertes mais je vous envoie un screen au cas ou ^^

re

tu n'as pas d'alertes dans le gestionnaire de périphériques, donc il est probable que ton souci soit d'ordre matériel

télécharge CrystalDiskInfo sur ton bureau et "exécute le en tant qu'administrateur" (clic droit) --> clique ici

donne l'état de santé du HDD/SSD et la T°, ou poste 1 capture d'écran

@+

re

les 2 disques sont OK

fait ceci:

quitte tous tes programmes en cours

dans recherche, tape CMD --> exécuter en tant qu'administrateur dans la fenêtre qui s'ouvre

dans CMD, copie/colle cette commande --> chkdsk c: /F /R et clique sur Enter

il te sera demandé 1 confirmation pour l'exécution du checkdisk, tape O pour oui et redémarre le pc



le scan va s'effectuer, laisse bosser le pc

ATTENTION: le checkdisk ne doit pas être interrompu

@+

salut

tu as fait le Checkdisk?

tu as toujours des BSOD?

@+

re

Oui j'ai fais le Checkdisk, et pour ce qui est du bsod je n'en ai pas actuellement.

je pense que c'est ok si tu n'as plus de BSOD :)

regarde ce que ça donne après 1 ou 2 jours d'utilisation, et si tu n'as plus de soucis, tu pourras mettre ton topic en résolu --> clique ici

merci

@+

salut

ça donne quoi avec ton pc?

@+

re

pas de souci pour l'aide, et merci du retour d'info :)

@+