Merci pour votre réponse,
N'y a t-il pas d'autres alternatives ? Quelle est l'origine du problème selon vous ?
Merci d'avance.
Ecran bleu windows 10 lorsque le PC est inactif
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonyme
Bonjour,
J'ai monté mon PC moi même il y a environ 3 mois environ et jusque là tout allait bien. Cependant depuis 2-3 semaines, je remarque que lorsque je laisse mon PC inactif, de façon totalement aléatoire, le fameux écran bleu Windows apparait avec un code d'erreur différent à chaque fois ce qui m'oblige à redémarrer le PC de manière forcée… Ce problème est très embêtant notamment lorsqu'on bosse…
Je viens donc vers vous pour essayer de trouver une solution à ce problème.
Merci d'avance
Windows pour les particuliers | Windows 10 | Mode veille et mise sous/hors tension
Question verrouillée. Cette question a été migrée à partir de la Communauté Support Microsoft. Vous pouvez voter pour indiquer si elle est utile, mais vous ne pouvez pas ajouter de commentaires ou de réponses ni suivre la question.
24 réponses
Trier par : Le plus utile
-
Anonyme
2021-03-01T18:02:14+00:00 -
Anonyme
2021-03-01T17:40:08+00:00 Bonjour,
Je crains bien qu'une installation neuve soit nécessaire après sauvegarde des données
-
Anonyme
2021-03-01T17:22:29+00:00 Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\MinidumpOn Mon 01/03/2021 17:09:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030121-49187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3D (0xFFFFF80773B3A9C8, 0xFFFFF80773B3A200, 0x0, 0x0)
Error: INTERRUPT_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 bug check appears very infrequently.
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 01/03/2021 17:09:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeSetEventBoostPriority+0x55)
Bugcheck code: 0x3D (0xFFFFF80773B3A9C8, 0xFFFFF80773B3A200, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Bug check description: This bug check appears very infrequently.
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 28/02/2021 19:54:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022821-37828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8025C426F54, 0xFFFFCA8906098860, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/02/2021 14:04:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022821-34453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x7F (0x8, 0xFFFF9D000E3BBE70, 0xFFFFFA00F9C3FFB0, 0xFFFFF8065742A84B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 26/02/2021 17:20:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-8359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3D (0xFFFFCB80CD03FD48, 0xFFFFCB80CD03F580, 0x0, 0x0)
Error: INTERRUPT_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 bug check appears very infrequently.
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 22/02/2021 22:50:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022221-12421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xBE (0xFFFFF8004F5BC010, 0x87000003100C0121, 0xFFFFED84D5059AD0, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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. -
Anonyme
2021-03-01T14:11:28+00:00 Bonjour,
Fais une analyse en utilisant WhoCrashed
https://www.malekal.com/whocrashed-analyser-ecran-bleu-bsod-code-arret/
-
Anonyme
2021-03-01T12:30:38+00:00 Personne n'a de solution ?
Je précise également que parfois l'écran reste figé et je suis obligé de redémarrer le pc de manière forcée. C'est soit un écran bleu soit un freeze de l'écran... Je ne sais vraiment pas quoi faire.