BSOD при перезагрузке (на горячую) / DPC WATCHDOG VIOLATION

Question

Добрый день, прошу вашей помощи в сложившейся ситуации. Проблема возникла в следующем.

Я купил новую материнскую плату (Gigabyte B760 Gaming X Rev 1.0) и также ЦП - Intel Core i5 12400f
После установки всех компонентов компьютер был успешно запущен, но в последствии была обнаружена проблема возникновения синих экранов смерти при перезагрузке, но это происходит именно "на горячую". То есть - если компьютер стоит в выключенном состоянии хотя-бы около 10 минут - он запускается без проблем и работает без сбоев, но если с включенного компьютера сделать перезагрузку - то в 90% вероятности появляется синий экран с ошибкой DPC_WATCHDOG_VIOLATION , который перед своим возникновением сопровождается зависанием загрузки (прогрессбар запуска виндовс, кольцо крутящееся на логотипе логотипа биоса).

Дамп одного из последних BSOD из WinDbg: Microsoft (R) Windows Debugger Version 10.0.22621.3233 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\phenya\Desktop\032024-5500-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\symbol_cache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\symbol_cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80065400000 PsLoadedModuleList = 0xfffff8006602a730 Debug session time: Wed Mar 20 02:57:45.500 2024 (UTC + 5:00) System Uptime: 0 days 0:06:03.212 Loading Kernel Symbols ............................................................... ................................................................ ........... Loading User Symbols Loading unloaded module list .. For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff800660fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000

Debugging Details:

************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** *************************************************************************

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1827

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 6646

Key  : Analysis.Init.CPU.mSec
Value: 468

Key  : Analysis.Init.Elapsed.mSec
Value: 7999

Key  : Analysis.Memory.CommitPeak.Mb
Value: 90

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 032024-5500-01.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff800660fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff8006a684d00 -- (.trap 0xfffff8006a684d00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000360 rbx=0000000000000000 rcx=ffffb30e12d9d200 rdx=00000000000003fd rsi=0000000000000000 rdi=0000000000000000 rip=fffff8008a982fa6 rsp=fffff8006a684e90 rbp=ffffb30e12e4ed01 r8=0000000000000000 r9=ffffb30e116ec330 r10=fffff8008a9729e0 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc serial!SerialProcessLSR+0x36: fffff800`8a982fa6 408af0 mov sil,al Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Registry

STACK_TEXT:
fffff8006a684988 fffff80065837d96 : 0000000000000133 0000000000000001 0000000000001e00 fffff800660fb320 : nt!KeBugCheckEx fffff8006a684990 fffff8006565937d : 000000e8ae01df12 fffff800624b2180 0000000000000246 0000000000005acd : nt!KeAccumulateTicks+0x1e1c36 fffff8006a6849f0 fffff800656518d1 : fffff800624b2180 000000000000361f fffff800624b2180 0000000000000001 : nt!KiUpdateRunTime+0x5d fffff8006a684a40 fffff80065653793 : fffff800624b2180 0000000000000000 fffff80066031968 0000000000000000 : nt!KiUpdateTime+0x4a1 fffff8006a684b80 fffff800656509a2 : fffff8006a684d00 fffff8006a684d80 fffff8006a684d00 0000000000000009 : nt!KeClockInterruptNotify+0x2e3 fffff8006a684c30 fffff80065700805 : 00000000d894d593 fffff800660f3ae0 fffff800660f3b90 0000000000000009 : nt!HalpTimerClockInterrupt+0xe2 fffff8006a684c60 fffff800657ff8ca : fffff8006a684d80 fffff800660f3ae0 00000000000000c0 fffff800657251da : nt!KiCallInterruptServiceRoutine+0xa5 fffff8006a684cb0 fffff800658000f7 : fffff8006a684d90 fffff8006561544d ffffb30e0c1dd6c0 fffff8006561540d : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff8006a684d00 fffff8008a982fa6 : 00400a0200000014 000000e8ae00e976 0000000000000001 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff8006a684e90 fffff8008a972e74 : ffffb30e12d9d200 ffff9e002edc1bf0 fffff800624b2180 6894da36aba1739d : serial!SerialProcessLSR+0x36 fffff8006a684ec0 fffff8008a9729f1 : ffff9e002edc1b40 ffffb30e12e4ed20 ffff9e002edc1bf0 0000000000000002 : serial!SerialISR+0x284 fffff8006a684f10 fffff80065700805 : fffff8008a9729e0 0000000000009001 fffff800624b2180 fffff8006a684fc0 : serial!SerialCIsrSw+0x11 fffff8006a684f40 fffff800657ff64f : fffff8006a68a7f0 ffff9e002edc1b40 fffff8006a67da40 fffff800657ff8ca : nt!KiCallInterruptServiceRoutine+0xa5 fffff8006a684f90 fffff800657ff917 : 0000000000002e99 fffff800657ff924 0000000000000000 0000000000000001 : nt!KiInterruptSubDispatch+0x11f fffff8006a68a770 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatch+0x37

SYMBOL_NAME: serial!SerialProcessLSR+36

MODULE_NAME: serial

IMAGE_NAME: serial.sys

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 36

FAILURE_BUCKET_ID: 0x133_ISR_serial!SerialProcessLSR

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b2f33c4f-2dcd-653c-df81-26f09391738c}

Followup: MachineOwner

Также BlueScreenView ругается на другой файл, а именно: ntoskrnl.exe

Answer 1

Проблема решена. Вероятнее всего была аппаратная проблема с материнской платой.
Приобрел AsRock B760 Pro RS/D4 - проблема более не повторяется

Answer 2

Изначально, как установил новые комплектующие данная проблема возникла на еще старой ОС.
После этого было принято решение отформатировать SSD и повторно переустановить систему.

На свеже-установленной ОС проблема также повторялась.
Драйвера устанавливались автоматически с помощью ОС + через Gigabyte Control Center (официальная программа материнской платы, которая доступна для установки после запуска материнской платы).

Answer 3

Анализ файлов дампов показал очень высокую вероятность проблем с драйверами, хотя нельзя полностью исключить и наличие аппаратных проблем:

On Wed 20.03.2024 0:57:45 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032024-5500-01.dmp (Minidump)

Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF800660FB320, 0x0)

Bugcheck name: DPC_WATCHDOG_VIOLATION

Driver or module in which error occurred: (0xfffff800`657fd890)

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).

Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.

This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.

Read this article on thermal issues

A full memory dump will likely provide more useful information on the cause of this particular bugcheck.

Процесс: Registry, вероятно вызвано: serial.sys

FAILURE_BUCKET_ID: 0x133_ISR_serial!SerialProcessLSR

On Tue 19.03.2024 21:57:01 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032024-11828-01.dmp (Minidump)

Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF80162CFB320, 0x0)

Bugcheck name: DPC_WATCHDOG_VIOLATION

Driver or module in which error occurred: (0xfffff801`623fd890)

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).

Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.

This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.

Read this article on thermal issues

A full memory dump will likely provide more useful information on the cause of this particular bugcheck.

Процесс: System, вероятно вызвано: memory_corruption

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

On Mon 18.03.2024 21:53:32 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\031924-5937-01.dmp (Minidump)

Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF807032FB320, 0x0)

Bugcheck name: DPC_WATCHDOG_VIOLATION

Driver or module in which error occurred: (0xfffff807`029fd890)

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).

Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.

This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.

Read this article on thermal issues

A full memory dump will likely provide more useful information on the cause of this particular bugcheck.

Процесс: System, вероятно вызвано: memory_corruption

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

On Tue 19.03.2024 14:33:27 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\031924-5890-01.dmp (Minidump)

Bugcheck code: 0x1E(0xFFFFFFFFC0000005, 0xFFFFF80223B92D78, 0x0, 0xFFFFFFFFFFFFFFFF)

Bugcheck name: KMODE_EXCEPTION_NOT_HANDLED

Driver or module in which error occurred: ACPI.sys (ACPI+0x62D78)

File path: C:\WINDOWS\System32\drivers\ACPI.sys

Description: ACPI драйвер для NT

Product: Операционная система Microsoft:registered: Windows:registered:

Company: Microsoft Corporation

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Analysis: This could be caused by either a software or hardware problem.

Hardware failure is often caused by overheating. Read this article on thermal issues

The crash took place in a Microsoft module. Possibly this problem was caused by another driver on your system that cannot be identified at this time.

Процесс: System, вероятно вызвано: memory_corruption

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

On Mon 18.03.2024 15:41:51 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\031824-6703-01.dmp (Minidump)

Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF8044DCFB320, 0x0)

Bugcheck name: DPC_WATCHDOG_VIOLATION

Driver or module in which error occurred: (0xfffff804`4d3fd890)

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).

Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.

This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.

Read this article on thermal issues

A full memory dump will likely provide more useful information on the cause of this particular bugcheck.

Процесс: System, вероятно вызвано: serial.sys

FAILURE_BUCKET_ID: 0x133_ISR_serial!SerialISR

Скажите пожалуйста, Вы переустанавливали систему после замены материнской платы?

Драйвера для материнки загружали и устанавливали отсюда?

https://www.gigabyte.com/Motherboard/B760-GAMIN...

Answer 4

К сожалению на OneDrive залить дампы не получилось, загрузил в другое облако, доступно по ссылке

Answer 5

Здравствуйте.

Разместите пожалуйста в OneDrive последние пять дампов памяти, записанных при сбоях, предоставьте к ним доступ и опубликуйте здесь на них ссылку, чтобы мы могли попытаться проанализировать происходящее на Вашей машине.