Aller au contenu
Site Communauté

ivolerg650m

Membres
 Afficher le profil  Afficher son activité

  • Nbre de contenus

    6

  • Inscription

  • Dernière visite

 Type de contenu 

Messages posté(e)s par ivolerg650m

    Pc qui redémarre tout seul ou écran bleu DPC_WATCHDOG_VIOLATION

    dans Windows

    Posté(e)

    j'ai fait une analyse avec whocrashed et voila le rapport 

     

     

    System Information (local)
    Computer name: DESKTOP-71969Q3
    Windows version: Windows 10 , 10.0, version 1903, build: 18362
    Windows dir: C:\Windows
    Hardware: Z370 AORUS Ultra Gaming, Gigabyte Technology Co., Ltd., Z370 AORUS Ultra Gaming-CF
    CPU: GenuineIntel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz Intel8664, level: 6
    6 logical processors, active mask: 63
    RAM: 17123246080 bytes (15,9GB)



    Crash Dump Analysis
    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\Windows
    C:\Windows\Minidump

    On Mon 07/10/2019 15:17:20 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\100719-14171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
    Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80135373358, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
    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 07/10/2019 15:17:20 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ndis.sys (ndis!ndisqueueioworkitem+0x16df8)
    Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80135373358, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Système d’exploitation Microsoft® Windows®
    company: Microsoft Corporation
    description: NDIS (Network Driver Interface Specification)
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
    The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.



    On Wed 28/08/2019 18:18:19 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\082819-15750-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
    Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8074D771350, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
    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 28/08/2019 14:07:44 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\082819-15703-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x491E1)
    Bugcheck code: 0x9C (0x0, 0xFFFF8F809B6A5CD0, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    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/08/2019 21:28:51 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\082719-13031-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80410F71350)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
    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/08/2019 20:44:12 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\082719-13296-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
    Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80164171350, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    Conclusion
    6 crash dumps have been found and analyzed. 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.
     

     

    Pc qui redémarre tout seul ou écran bleu DPC_WATCHDOG_VIOLATION

    dans Windows

    Posté(e)

    Bonjour a tous je viens chercher de l'aide sur le forum car j'ai un gros soucie avec mon ordi et c'est insupportable j'ai envie de le balancer par la fenêtre x)!!

    Alors soit il redémarre tout seul genre d'un coup il s’éteint et se rallume sans que je soit obliger de faire quoi que se soit OU bien il plante et affiche l’écran bleu avec  le code d’arrêt DPC_WATCHDOG_VIOLATION

    je n'en peu plus...

    Je vous liste ma config:

    -carte mere Aorus z370 gigabyte ultra gaming
    -processeur i5 8600k
    -carte graphique AMD RX 480 8go
    -SSD 750 EVO 250GB
    -Ram corsair vengeance DDR4 2666 2x8go
    -Corsair vs550
    -Carte wifi
     

    enfin voila si vous pouviez m'aider a trouver d'ou ce problème vient ça serais vraiment super car je n'en peu plus et je n'ai pas les compétences pour trouver seul...

    Merci a vous a très vite j’espère 

×
×
  • Créer...