Votre question

BSOD Windows 10

Tags :
  • Bsod
  • Windows 10
  • Écran bleu
Dernière réponse : dans Systèmes d'exploitation
14 Décembre 2017 20:33:16

Bonjour ou bonsoir, tout d'abord merci de prendre le temps de lire ce topic.

Alors voila j'ai eux des blue screen sur mon pc. Je suis sur windows 10. Ces écrans bleu survienne a n'importe quel moment et sa peux venir 2 fois en 1h comme 1 fois en 2 semaines.
Ps : lorsque je boot en mode sans échec quand je vais dans mes périphériques j'ai une erreur de driver de mon écran donc je le désinstalle et ... L'erreur revient.(Info : avant j'avais un pc portable et j'avais le même problème)

J'ai déjà tester :

- test memoire
- test ssd/hdd
- température
- mis a jour windows
- mis a jour mes drivers
- désinstaller le driver de mon écran
- mettre à jour mes driver en mode sans échec

Mis a part les écrans bleu, mon pc fonctionne et démarre super bien.
tout le matériel à 2 mois environs.

Spoiler
Mon WhoCrashed :

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 13/12/2017 20:31:28 your computer crashed
crash dump file: C:\Windows\Minidump\121317-8796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x100000B8 (0xFFFFCE094E6347C0, 0xFFFFCE094CCCB7C0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/12/2017 20:31:28 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: 0xB8 (0xFFFFCE094E6347C0, 0xFFFFCE094CCCB7C0, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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 10/12/2017 00:13:54 your computer crashed
crash dump file: C:\Windows\Minidump\121017-8171-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0xA, 0x945925, 0x945926, 0xFFFFA60DBE2BF0C0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 02/11/2017 15:38:24 your computer crashed
crash dump file: C:\Windows\Minidump\110217-5765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x170E06)
Bugcheck code: 0x100000B8 (0xFFFFC88EAD1867C0, 0xFFFFC88EA3BFD080, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 18/10/2017 14:23:47 your computer crashed
crash dump file: C:\Windows\Minidump\101817-4875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x100000B8 (0xFFFF820A61AF57C0, 0xFFFF820A4ED6F7C0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

ma config :

écran : Acer g246hl
RAM : DDR4 corsair, 2 x 8 Go, 2800 MHz, CAS 14
Proc : Intel Core i5-7600K (3.80 GHz)
Carte mère : Msi z270 pc mate
Vantirad: Be Quiet ! Dark rock 3
CG : Gigabyte GeForce GTX 1070 G1 GAMING, 8 Go
Alim : Be quiet pure power 10 600W
SSD OS : SDD kfa2 , 240 Go, SATA III
HDD2 : Seagate HHD, 1 To
Boitier: Nxzt s340


Voila j’espère avoir donner assez d'infos. Merci d'avance pour vos réponses.

Autres pages sur : bsod windows

15 Décembre 2017 08:04:35

Hello, c'est un problème software apparemment, essayes peut être de nettoyer les pilotes de ta carte graphique avec DDU puis de les réinstaller en alalnt les chercher manuellement sur le site de Nvidia.
http://www.guru3d.com/files-details/display-driver-unin...

Sinon ton cpu est overclocké? Tu as touché aux rams dans le bios? Tu as essayé d'activer le profil xmp?
m
0
l
15 Décembre 2017 18:44:57

dandibot a dit :
Hello, c'est un problème software apparemment, essayes peut être de nettoyer les pilotes de ta carte graphique avec DDU puis de les réinstaller en alalnt les chercher manuellement sur le site de Nvidia.
http://www.guru3d.com/files-details/display-driver-unin...

Sinon ton cpu est overclocké? Tu as touché aux rams dans le bios? Tu as essayé d'activer le profil xmp?


Salut, merci déjà de m'avoir pris le temps a me répondre !
Mon cpu n'est pas overclocké / je n'ai pas touché au ram / et j'ai activer le profil xmp
Pour la partie ddu je vais essayer ça :D 

m
0
l
Contenus similaires
21 Décembre 2017 17:14:24

Je ne sais pas si le problème a été résolu mais voici un article qui propose des pistes/solutions pour l'écran bleu / blue screen.
https://www.supergeek.fr/blog/lecran-bleu-de-la-mort/


Spoiler
DIKING a dit :
Bonjour ou bonsoir, tout d'abord merci de prendre le temps de lire ce topic.

Alors voila j'ai eux des blue screen sur mon pc. Je suis sur windows 10. Ces écrans bleu survienne a n'importe quel moment et sa peux venir 2 fois en 1h comme 1 fois en 2 semaines.
Ps : lorsque je boot en mode sans échec quand je vais dans mes périphériques j'ai une erreur de driver de mon écran donc je le désinstalle et ... L'erreur revient.(Info : avant j'avais un pc portable et j'avais le même problème)

J'ai déjà tester :

- test memoire
- test ssd/hdd
- température
- mis a jour windows
- mis a jour mes drivers
- désinstaller le driver de mon écran
- mettre à jour mes driver en mode sans échec

Mis a part les écrans bleu, mon pc fonctionne et démarre super bien.
tout le matériel à 2 mois environs.

Mon WhoCrashed :

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 13/12/2017 20:31:28 your computer crashed
crash dump file: C:\Windows\Minidump\121317-8796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x100000B8 (0xFFFFCE094E6347C0, 0xFFFFCE094CCCB7C0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/12/2017 20:31:28 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: 0xB8 (0xFFFFCE094E6347C0, 0xFFFFCE094CCCB7C0, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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 10/12/2017 00:13:54 your computer crashed
crash dump file: C:\Windows\Minidump\121017-8171-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0xA, 0x945925, 0x945926, 0xFFFFA60DBE2BF0C0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 02/11/2017 15:38:24 your computer crashed
crash dump file: C:\Windows\Minidump\110217-5765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x170E06)
Bugcheck code: 0x100000B8 (0xFFFFC88EAD1867C0, 0xFFFFC88EA3BFD080, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 18/10/2017 14:23:47 your computer crashed
crash dump file: C:\Windows\Minidump\101817-4875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x100000B8 (0xFFFF820A61AF57C0, 0xFFFF820A4ED6F7C0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

ma config :

écran : Acer g246hl
RAM : DDR4 corsair, 2 x 8 Go, 2800 MHz, CAS 14
Proc : Intel Core i5-7600K (3.80 GHz)
Carte mère : Msi z270 pc mate
Vantirad: Be Quiet ! Dark rock 3
CG : Gigabyte GeForce GTX 1070 G1 GAMING, 8 Go
Alim : Be quiet pure power 10 600W
SSD OS : SDD kfa2 , 240 Go, SATA III
HDD2 : Seagate HHD, 1 To
Boitier: Nxzt s340

Voila j’espère avoir donner assez d'infos. Merci d'avance pour vos réponses.


m
0
l
23 Décembre 2017 12:06:46

Spoiler
super_geek a dit :
Je ne sais pas si le problème a été résolu mais voici un article qui propose des pistes/solutions pour l'écran bleu / blue screen.
https://www.supergeek.fr/blog/lecran-bleu-de-la-mort/


DIKING a dit :
Bonjour ou bonsoir, tout d'abord merci de prendre le temps de lire ce topic.

Alors voila j'ai eux des blue screen sur mon pc. Je suis sur windows 10. Ces écrans bleu survienne a n'importe quel moment et sa peux venir 2 fois en 1h comme 1 fois en 2 semaines.
Ps : lorsque je boot en mode sans échec quand je vais dans mes périphériques j'ai une erreur de driver de mon écran donc je le désinstalle et ... L'erreur revient.(Info : avant j'avais un pc portable et j'avais le même problème)

J'ai déjà tester :

- test memoire
- test ssd/hdd
- température
- mis a jour windows
- mis a jour mes drivers
- désinstaller le driver de mon écran
- mettre à jour mes driver en mode sans échec

Mis a part les écrans bleu, mon pc fonctionne et démarre super bien.
tout le matériel à 2 mois environs.

Mon WhoCrashed :

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 13/12/2017 20:31:28 your computer crashed
crash dump file: C:\Windows\Minidump\121317-8796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x100000B8 (0xFFFFCE094E6347C0, 0xFFFFCE094CCCB7C0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/12/2017 20:31:28 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: 0xB8 (0xFFFFCE094E6347C0, 0xFFFFCE094CCCB7C0, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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 10/12/2017 00:13:54 your computer crashed
crash dump file: C:\Windows\Minidump\121017-8171-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0xA, 0x945925, 0x945926, 0xFFFFA60DBE2BF0C0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 02/11/2017 15:38:24 your computer crashed
crash dump file: C:\Windows\Minidump\110217-5765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x170E06)
Bugcheck code: 0x100000B8 (0xFFFFC88EAD1867C0, 0xFFFFC88EA3BFD080, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 18/10/2017 14:23:47 your computer crashed
crash dump file: C:\Windows\Minidump\101817-4875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x100000B8 (0xFFFF820A61AF57C0, 0xFFFF820A4ED6F7C0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

ma config :

écran : Acer g246hl
RAM : DDR4 corsair, 2 x 8 Go, 2800 MHz, CAS 14
Proc : Intel Core i5-7600K (3.80 GHz)
Carte mère : Msi z270 pc mate
Vantirad: Be Quiet ! Dark rock 3
CG : Gigabyte GeForce GTX 1070 G1 GAMING, 8 Go
Alim : Be quiet pure power 10 600W
SSD OS : SDD kfa2 , 240 Go, SATA III
HDD2 : Seagate HHD, 1 To
Boitier: Nxzt s340
a dit :
a dit :

Voila j’espère avoir donner assez d'infos. Merci d'avance pour vos réponses.




Salut, et merci d'avoir pris le temps de me répondre !
Tout d'abord cela fait environ quasiment une semaine que je n'ai pas eu de BSOD, je vous tiendrait au courant si jamais cela se reproduit.
Pour les pistes que j'ai essayer : Mise à jour windows
Réinstallation des drivers de ma carte graphique avec ddu
Mise à jour de tous mes drivers

m
0
l
26 Décembre 2017 08:03:02

Si les BSOD ne reviennent pas, c'était alors bien un conflit de pilotes, il est courant que ce soit la cause de ce genre d'erreurs.
m
0
l
2 Janvier 2018 12:24:30

dandibot a dit :
Si les BSOD ne reviennent pas, c'était alors bien un conflit de pilotes, il est courant que ce soit la cause de ce genre d'erreurs.


Merci d'avoir pris le temps de répondre !
Il s’avère que je n'ai plus de blue screen donc oui sa semblait bien un conflit de pilotes mes maintenant j'ai un autre problème qui me préoccupe lorsque je joue a des jeux notamment gta 5 j'ai des sortes de micro freezes quand j'ouvre le menu pareille sur un autre jeu.
J'ai cherché sur des forums et j'ai trouvé qu'il s'agirait de 'latence entre mes drivers"
J'ai installer latency moon et il relève bien des problème de latence
Voici les stats de latency moon :
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:09:14 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DIKING-PC
OS version: Windows 10 , 10.0, build: 15063 (x64)
Hardware: MS-7A72, MSI, Z270 PC MATE (MS-7A72)
CPU: GenuineIntel Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
Logical processors: 4
Processor groups: 1
RAM: 16341 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3792 MHz
Measured CPU speed: 1 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 3434,932999
Average measured interrupt to process latency (µs): 2,079467

Highest measured interrupt to DPC latency (µs): 3432,502621
Average measured interrupt to DPC latency (µs): 0,703347


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 615,165612
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,151384
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,213155

ISR count (execution time <250 µs): 455543
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 3
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 1595,745781
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 388.59 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,078018
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in DPCs (%) 0,285678

DPC count (execution time <250 µs): 1747214
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 5
DPC count (execution time 1000-1999 µs): 2
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.


Process with highest pagefault count: none

Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0,0
Total time spent in hard pagefaults (%): 0,0
Number of processes hit: 0


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 15,273486
CPU 0 ISR highest execution time (µs): 615,165612
CPU 0 ISR total execution time (s): 4,600464
CPU 0 ISR count: 437823
CPU 0 DPC highest execution time (µs): 1595,745781
CPU 0 DPC total execution time (s): 5,575828
CPU 0 DPC count: 1584778
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 5,306244
CPU 1 ISR highest execution time (µs): 161,415612
CPU 1 ISR total execution time (s): 0,122755
CPU 1 ISR count: 16766
CPU 1 DPC highest execution time (µs): 213,572257
CPU 1 DPC total execution time (s): 0,373401
CPU 1 DPC count: 66113
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5,014190
CPU 2 ISR highest execution time (µs): 97,184072
CPU 2 ISR total execution time (s): 0,007705
CPU 2 ISR count: 928
CPU 2 DPC highest execution time (µs): 186,880802
CPU 2 DPC total execution time (s): 0,217409
CPU 2 DPC count: 49849
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4,842130
CPU 3 ISR highest execution time (µs): 18,438819
CPU 3 ISR total execution time (s): 0,000058
CPU 3 ISR count: 29
CPU 3 DPC highest execution time (µs): 214,288502
CPU 3 DPC total execution time (s): 0,173994
CPU 3 DPC count: 46481
_________________________________________________________________________________________________________

Merci d'avance, et bonne année à tous !
m
0
l
Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS