PROBLEMA errore dpc watchdog violation windows 10

  • Autore discussione Autore discussione Dize
  • Data d'inizio Data d'inizio
Pubblicità
Dize

Dize

Nuovo Utente
Messaggi
21
Reazioni
3
Punteggio
23
Ciao a tutti, ormai è da circa una settimana che windows 10 mi freeza durante il gaming e test benchmark con conseguente schermata blu indicante l' errore watchdog violation.
Questo è ciò che bluescreenview ha trovato. Di seguito vi elenco il file di dump:

Dump File: 051316-6562-01.dmp
Crash Time: 13/05/2016 02:59:39
Bug Check Code: 0x00000133
Parameter 1: 00000000`00000001
Parameter 2: 00000000`00001e00
Parameter 3: 00000000`00000000
Parameter 4: 00000000`00000000
Caused By Driver: ntoskrnl.exe
Caused By Adress: ntoskrnl.exe+142780
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 10.0.10586.306 (th2_release_sec.160422-1850)
Processor: x64
Crash Adress: ntoskrnl.exe+142780
Full Path: C:\Windows\Minidump\051316-6562-01.dmp
Processors Count: 8
Major Version: 15
Minor Version: 10586
Dump File Size: 304.020
Dump File Time: 13/05/2016 03:00:51

La mia configurazione è la seguente:

os: Windows 10 64bit
ssd samsung 850 evo 500gb raid0 (sono 2 ssd da 250gb), western digital 500gb sata/300, western digital 3Tb sata/600
Asus Mximus Hero VIII aggiornata all' ultimo bios (1701), Intel Skylake 6700k, Sapphire amd 290x tri-x 4gb GDDR5 oc, scheda audio Creative X-Fi Titanium Fatal1ty Professional, Psu Corsair HX850, Ram Geil Superluce 8gbx2 DDR4 3000 MHz.
Sia il procio sia la scheda video sono raffreddate a liquido con impianto assemblato da me.
Spero possiate risolvere questo fastidioso Crash :cry:
 
Dize ha detto:
Ciao a tutti, ormai è da circa una settimana che windows 10 mi freeza durante il gaming e test benchmark con conseguente schermata blu indicante l' errore watchdog violation.
Questo è ciò che bluescreenview ha trovato. Di seguito vi elenco il file di dump:

Dump File: 051316-6562-01.dmp
Crash Time: 13/05/2016 02:59:39
Bug Check Code: 0x00000133
Parameter 1: 00000000`00000001
Parameter 2: 00000000`00001e00
Parameter 3: 00000000`00000000
Parameter 4: 00000000`00000000
Caused By Driver: ntoskrnl.exe
Caused By Adress: ntoskrnl.exe+142780
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 10.0.10586.306 (th2_release_sec.160422-1850)
Processor: x64
Crash Adress: ntoskrnl.exe+142780
Full Path: C:\Windows\Minidump\051316-6562-01.dmp
Processors Count: 8
Major Version: 15
Minor Version: 10586
Dump File Size: 304.020
Dump File Time: 13/05/2016 03:00:51

La mia configurazione è la seguente:

os: Windows 10 64bit
ssd samsung 850 evo 500gb raid0 (sono 2 ssd da 250gb), western digital 500gb sata/300, western digital 3Tb sata/600
Asus Mximus Hero VIII aggiornata all' ultimo bios (1701), Intel Skylake 6700k, Sapphire amd 290x tri-x 4gb GDDR5 oc, scheda audio Creative X-Fi Titanium Fatal1ty Professional, Psu Corsair HX850, Ram Geil Superluce 8gbx2 DDR4 3000 MHz.
Sia il procio sia la scheda video sono raffreddate a liquido con impianto assemblato da me.
Spero possiate risolvere questo fastidioso Crash :cry:
Clicca per espandere...

ciao scarica whocrashed e posta la lettura del dump
 
[FONT=Segoe UI, Arial]On Fri 13/05/2016 00:59:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051316-6562-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ha2.sys[/FONT] (ha20x22k+0x98AF5)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: [FONT=Segoe UI, Arial]ha2.sys DPC_WATCHDOG_VIOLATION[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Fri 13/05/2016 00:59:39 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ctaud2k.sys[/FONT] (ctaud2k+0x99EDC)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
file path: C:\Windows\system32\drivers\ctaud2k.sys
product: [FONT=Segoe UI, Arial]Creative Audio Product[/FONT]
company: [FONT=Segoe UI, Arial]Creative Technology Ltd[/FONT]
description: Creative WDM Audio Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ctaud2k.sys (Creative WDM Audio Device Driver, Creative Technology Ltd).
Google query: [FONT=Segoe UI, Arial]Creative Technology Ltd DPC_WATCHDOG_VIOLATION[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Fri 13/05/2016 00:38:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051316-6515-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ha2.sys[/FONT] (ha20x22k+0x98AF5)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: [FONT=Segoe UI, Arial]ha2.sys DPC_WATCHDOG_VIOLATION[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 12/05/2016 18:19:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051216-15281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 12/05/2016 17:29:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051216-6531-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ha2.sys[/FONT] (ha20x22k+0x98AF5)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: [FONT=Segoe UI, Arial]ha2.sys DPC_WATCHDOG_VIOLATION[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 12/05/2016 16:49:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051216-6625-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ha2.sys[/FONT] (ha20x22k+0x98AF5)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: [FONT=Segoe UI, Arial]ha2.sys DPC_WATCHDOG_VIOLATION[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 12/05/2016 15:46:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051216-6531-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ha2.sys[/FONT] (ha20x22k+0x98AF5)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DPC_WATCHDOG_VIOLATION[/FONT]
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: [FONT=Segoe UI, Arial]ha2.sys DPC_WATCHDOG_VIOLATION[/FONT]


questi sono tutti i file du[FONT=Segoe UI, Arial]mp che mi ha tr[FONT=Segoe UI, Arial]ovato e analizzato.[FONT=Segoe UI, Arial] Spero sia su[FONT=Segoe UI, Arial]fficiente per ca[FONT=Segoe UI, Arial]pire dove sia il problema[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]

- - - Updated - - -

Dovrei aver risolto. Ho disinstallato la creative soundblaster x-fi e rimossa dalla pci. Con l' audio integrato dell' asus non sto avendo problemi per quanto riguarda bsod. Solo che dopo una mezz' ora abbondante di gioco il pc si riavvia a caso :grat:. Ringrazio comunque Federico83 per avermi consigliato Whocrashed, almeno ho avuto la possibilità di vedere quali fossero i driver che causavano il crash ;).

- - - Updated - - -

Penso di aver risolto anche il problema riavvio pc durante il gaming. Ho disinstallato i driver amd della scheda video usando DDU in modalità provissoria, al riavvio ho fatto una bella pulizia con Ccleaner e installato nuovamenti gli ultimi driver Amd. Un paio d' ore di gioco e nessun riavvio. Spero che questo possa essere di aiuto anche per altri utenti. :)
 
Guarda io ho il tuo stesso problema (con driver diversi) da 3 giorni e ancora dopo tutte le prove che ho fatto non sono riuscito a risolvere.

Fino a lunedì sera non avevo mai avuto questi problemi, da allora non so cosa è successo ha cominciato a fare freeze e il classico blu screen di Watch Dogs!

Ma che sta succedendo? Non è che ci sono stati aggiornamenti Windows nascosti che stanno creando problemi?
 
Ciao, guarda io ho risolto scaricando whocrashed in modo tale da poter visionare il file dump e capire quali fossero i driver che causavano il crash. Alla fine era la scheda audio dedicata. Prova e fammi sapere :)
 
Io ho già fatto con un'altro programma, Bluescreenview mi pare...
Allora che hai fatto hai tolto la scheda audio, non la puoi più utilizzare?
 
Bluescreenview ti fa vedere solo il documento del dump, ma non ti analizza i file che causano il crash, quindi abbastanza inutile a parere mio. Si purtroppo la scheda audio non è compatibile con win10 nonostante avevo installato i driver dalla creative per 10, era una soundblaster titanium fatality series. Utilizzo per ora l audio integrato. Comunque scarica whocrashed che è free.
 
On Thu 02/06/2016 20:01:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060216-8171-02.dmp
This was probably caused by the following module: ha2.sys (ha20x22k+0xA5124)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: ha2.sys DPC_WATCHDOG_VIOLATION



On Thu 02/06/2016 20:01:22 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ctaud2k.sys (ctaud2k+0xE02A)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\ctaud2k.sys
product: Creative Audio Product
company: Creative Technology Ltd
description: Creative WDM Audio Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ctaud2k.sys (Creative WDM Audio Device Driver, Creative Technology Ltd).
Google query: Creative Technology Ltd DPC_WATCHDOG_VIOLATION



On Thu 02/06/2016 19:32:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060216-8234-01.dmp
This was probably caused by the following module: ha2.sys (ha20x22k+0x9463D)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: ha2.sys DPC_WATCHDOG_VIOLATION



On Thu 02/06/2016 11:55:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060216-7703-01.dmp
This was probably caused by the following module: ha2.sys (ha20x22k+0xA5118)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: ha2.sys DPC_WATCHDOG_VIOLATION



On Thu 02/06/2016 11:36:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060216-7765-01.dmp
This was probably caused by the following module: ha2.sys (ha20x22k+0xA3293)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: ha2.sys DPC_WATCHDOG_VIOLATION



On Thu 02/06/2016 10:06:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060216-8171-01.dmp
This was probably caused by the following module: ha2.sys (ha20x22k+0x95AE5)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ha2.sys .
Google query: ha2.sys DPC_WATCHDOG_VIOLATION

:asd:

Comunque mi sembra strano, io ho una Titanium HD, Windows 10 ce l'ho da quando è uscito e non ho avuto mai questo blu screen, perchè proprio ora?
 
Ultima modifica:
Infatti gli errori sono causati dai driver della scheda audio. Io la mia la presi 6 anni fa, ma anche a me dopo un mese di win10 in cui andava tutto bene, il pc aveva iniziato con questi crash. Tolta la scheda finiti i crash. Il motivo del perche siano iniziati i crash non saprei dirtelo. Comunque fa una prova, disinstalla prima la periferica da gestione dispositivi e poi diainstalla i driver. Togli la scheda fisicamente e vedrai che i crash nn ci sono piu. Comunque eventualmente potresti tornare a win7 e conservare la scheda audio. Io son stato costretto a passare a win10 per via di skylake, ogni volta che facevo aggiornamenti con win7 il pc o non si spegneva o si bloccava allo spegnimento
 
Mah ci gioco da un anno senza problemi e adesso fa sta roba, comunque dai provo e ti faccio sapere, grazie...
 
Ultima modifica:
Ah comunque sono andato nel sito di creative e ho visto che c'è un driver per la build 10586 di Windows 10 uscito a febbraio!
Io avevo quella di agosto 2015 quando è uscito il nuovo Windows...
Se non l'hai fatto controlla pure per la tua scheda.
 
Eh ma io avevo inatallato proprio quello, tempo un paio di mesi e mi ha dato lo stesso tuo problema.
 
Ah niente allora quando mi arriva il nuovo ssd evito proprio di installarli...
In ogni caso mi voglio passare il piacere di contattare la creative e dirle quattro paroline.

Comunque menomale che ho beccato la tua discussione, ringrazio te e l'utente che ti ha segnalato quel programma senza la quale non ci avremmo capito un cacchio! :asd:
 
Pubblicità
Pubblicità
Indietro
Top