- 793
- 84
- CPU
- Intel Core I7 - 2630QM - 2.0 GHZ
- Scheda Madre
- Proprietaria
- HDD
- 500GB WD 2.5"
- RAM
- 2 x 2GB Corsair
- GPU
- GeForce GT540M 1GB
- Audio
- Integrato
- OS
- Windows 10 Pro, Kali Linux 2.0
Salve a tutti e buone feste!
In questi giorni il mio portatile sta iniziando ad avere uno strano comportamento.
Si blocca improvvisamente e va in blue screen con errore DCP_WATCHDOGS_VIOLATION.
Ad ora riesco ad usare il pc solamente se disattivo la scheda video da gestione dispositivi.
Il notebook è un DELL Inspiron 15 SE con
i7 3632QM
8GB di RAM
SSD samsung 850 240GB
scheda video AMD HD 7730M
windows 10
Di seguito riporto anche il log di Whocrashed.
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 27/12/2018 17:11:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122718-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8037E959380, 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 Thu 27/12/2018 17:11:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (fltmgr!fltsendmessage+0x4f2)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8037E959380, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 27/12/2018 16:24:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122718-7234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8035FF45380, 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 Thu 27/12/2018 15:54:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122718-4062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8057CCC6380, 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.
Grazie a chiunque possa aiutarmi!
In questi giorni il mio portatile sta iniziando ad avere uno strano comportamento.
Si blocca improvvisamente e va in blue screen con errore DCP_WATCHDOGS_VIOLATION.
Ad ora riesco ad usare il pc solamente se disattivo la scheda video da gestione dispositivi.
Il notebook è un DELL Inspiron 15 SE con
i7 3632QM
8GB di RAM
SSD samsung 850 240GB
scheda video AMD HD 7730M
windows 10
Di seguito riporto anche il log di Whocrashed.
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 27/12/2018 17:11:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122718-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8037E959380, 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 Thu 27/12/2018 17:11:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (fltmgr!fltsendmessage+0x4f2)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8037E959380, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 27/12/2018 16:24:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122718-7234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8035FF45380, 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 Thu 27/12/2018 15:54:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122718-4062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8057CCC6380, 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.
Grazie a chiunque possa aiutarmi!