Jump to content
Kaspersky Support Forum

卡巴斯基与网易逆水寒冲突导致电脑死机重启

Foloberg

By Foloberg
in 家用产品支持

 Share

Recommended Posts

Foloberg

Foloberg

Posted
Posted

继上次网易游戏1072进不去问题解决之后，30号永劫无间（我主玩这个游戏，其他游戏暂不清楚）更新又出现了问题，我进入游戏游玩1小时左右，会出现DPC_WATCHDOG_VIOLATION (133)蓝屏，冻结画面。
以下是dump文件分析结果。（我对电脑了解甚少，以下结果在ai指导下得出）

 

0: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.........
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000000c`3b354018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff802e8fc53c8, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for klupd_K4W-21-26_arkmon.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 1625

    Key  : Analysis.Elapsed.mSec
    Value: 5699

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_ISR_klupd_K4W_21_26_arkmon!unknown_function

    Key  : Failure.Hash
    Value: {7fe1c3ad-1352-f111-1caf-f5ae8af78f90}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802e8fc53c8

BUGCHECK_P4: 0

FILE_IN_CAB:  073126-12718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff8d0254dd2080

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NeacClient.exe

STACK_TEXT:  
fffff802`7ac0bc08 fffff802`e82ab44c     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`e8fc53c8 : nt!KeBugCheckEx
fffff802`7ac0bc10 fffff802`e82aa97b     : 00000000`00000000 00000000`002fba9a 00000000`00000000 fffff802`75e3d180 : nt!KeAccumulateTicks+0x59c
fffff802`7ac0bc80 fffff802`e8319eae     : 00000000`00000000 00000071`cb6d132b fffff802`75e3d180 00000000`00000000 : nt!KiUpdateRunTime+0x9b
fffff802`7ac0be40 fffff802`e831a8ac     : fffff802`e8e10f90 fffff802`e8e11040 fffff802`e8f8f0d0 ffff9f85`0e827101 : nt!KeClockInterruptNotify+0x3ee
fffff802`7ac0bf40 fffff802`e86addde     : 00000000`00000002 fffff802`e8e10f90 00000000`00000000 ffff9f85`0e8271e0 : nt!KiCallInterruptServiceRoutine+0x32c
fffff802`7ac0bfb0 fffff802`e86ae5ec     : 00000071`cb84a128 ffff9f85`0e826f90 00000071`cb84a12c 00008521`99aa8efa : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffff9f85`0e826f10 fffff802`7b104a04     : 00000000`00000001 ffff8d02`768ec080 00000000`00000000 fffff802`7b104a52 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffff9f85`0e8270a0 00000000`00000001     : ffff8d02`768ec080 00000000`00000000 fffff802`7b104a52 fffff802`7b133b6c : klupd_K4W_21_26_arkmon+0x34a04
ffff9f85`0e8270a8 ffff8d02`768ec080     : 00000000`00000000 fffff802`7b104a52 fffff802`7b133b6c ffff9f85`0e8271d8 : 0x1
ffff9f85`0e8270b0 00000000`00000000     : fffff802`7b104a52 fffff802`7b133b6c ffff9f85`0e8271d8 ffff8d02`6a2bb600 : 0xffff8d02`768ec080


SYMBOL_NAME:  klupd_K4W_21_26_arkmon+34a04

MODULE_NAME: klupd_K4W_21_26_arkmon

IMAGE_NAME:  klupd_K4W-21-26_arkmon.sys

STACK_COMMAND: .process /r /p 0xffff8d02768ec080; .thread /r /p 0xffff8d0254dd2080 ; kb

BUCKET_ID_FUNC_OFFSET:  34a04

FAILURE_BUCKET_ID:  0x133_ISR_klupd_K4W_21_26_arkmon!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7fe1c3ad-1352-f111-1caf-f5ae8af78f90}

Followup:     MachineOwner
---------
 

TIAN

TIAN

Posted
Posted

大概在几周前就一直存在偶尔登录游戏后电脑死机重启的问题，但我也一直没怎么管，直到7月31日游戏版本更新后，游戏登录几乎必定死机，所以我重视起来开始查找原因，并发现了7月初卡巴斯基和网易反作弊冲突产生的BUG，所以我尝试了一些测试。因为我并不了解电脑，所以只能做一些基础测试。

我的WIN11系统与显卡驱动这些系统更新到了最新版本，卡巴斯基为21.25版本。

为了测试我事先准备好了额外的卡巴斯基安装程序，当我卸载了卡巴斯基后游戏确实能完全正常的运行，关闭游戏后安装卡巴斯基后也可以再次正常运行游戏。但是手动关闭游戏再重新登录游戏几分钟后就会死机了，即使关开机后游戏登录几分钟后依然死机，电脑每次死机重启后卡巴斯基会显示上一次启动失败。如此两轮下来基本可以说明确实是卡巴斯基和游戏本身/网易反作弊产生的BUG，卸载卡巴斯基后就能正常游戏。

（图片1为此游戏的图标）

image.png.62b3de177b686d9df39d7e9cdb0fcbf2.pngimage.thumb.png.1feaa3d3ed96e393c4f92d5d28d6aac5.pngQQ_1785489934722.thumb.png.acc7a7394861268daf05687210fb28cc.png

  • Like 1
MelonCook

MelonCook

Posted
Posted

从本周开始在进入逆水寒游戏后不出几分钟即遭遇DPC蓝屏，尝试升级卡巴斯基至最新版但无效

卡巴斯基版本：21.26.4.406

附上蓝屏日志： 

6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000096`4ad7a018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80349afb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for klupd_K4W-21-26_arkmon.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 1781

    Key  : Analysis.Elapsed.mSec
    Value: 3023

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x133_ISR_klupd_K4W_21_26_arkmon!unknown_function

    Key  : Failure.Hash
    Value: {7fe1c3ad-1352-f111-1caf-f5ae8af78f90}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.System.BIOSRevision
    Value: 1.20.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80349afb320

BUGCHECK_P4: 0

FILE_IN_CAB:  080126-10000-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc6044cfe6080

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
ffff9680`8d6bee18 fffff803`49226bfe     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`49afb320 : nt!KeBugCheckEx
ffff9680`8d6bee20 fffff803`49021a53     : 000013f7`c5808c2e ffff9680`8d6a5180 00000000`00000000 ffff9680`8d6a5180 : nt!KeAccumulateTicks+0x20282e
ffff9680`8d6bee80 fffff803`4902153a     : ffffc604`2d331260 ffffec0d`037fe740 fffff803`4d448600 00000000`00000001 : nt!KeClockInterruptNotify+0x453
ffff9680`8d6bef30 fffff803`49143a65     : ffffc604`2d331260 fffff803`4911d4c7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9680`8d6bef60 fffff803`491ff5fa     : ffffec0d`037fe740 ffffc604`2d331260 ffffec0d`037fead8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9680`8d6befb0 fffff803`491ffe27     : ffffc604`4c969dc0 fffff803`491ffeaf ffffc604`577828e0 00000000`5d2e9301 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffec0d`037fe6c0 fffff803`4d422867     : fffff803`491106b6 fffff803`4d463bc0 ffffec0d`037fe9b0 ffffc604`4c969de8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffec0d`037fe858 fffff803`491106b6     : fffff803`4d463bc0 ffffec0d`037fe9b0 ffffc604`4c969de8 00000000`00000200 : klupd_K4W_21_26_arkmon+0x22867
ffffec0d`037fe860 fffff803`4911052e     : ffffec0d`037fe910 fffff803`4d463bc0 ffffec0d`037fe9b0 00000000`00000058 : nt!FindNodeOrParent+0x42
ffffec0d`037fe890 fffff803`4d422ba7     : ffffec0d`037fe9b0 ffffec0d`037fe900 ffffec0d`037fead8 ffffec0d`037fead8 : nt!RtlInsertElementGenericTable+0x2e
ffffec0d`037fe8e0 ffffec0d`037fe9b0     : ffffec0d`037fe900 ffffec0d`037fead8 ffffec0d`037fead8 00000000`000000d4 : klupd_K4W_21_26_arkmon+0x22ba7
ffffec0d`037fe8e8 ffffec0d`037fe900     : ffffec0d`037fead8 ffffec0d`037fead8 00000000`000000d4 00000000`00000000 : 0xffffec0d`037fe9b0
ffffec0d`037fe8f0 ffffec0d`037fead8     : ffffec0d`037fead8 00000000`000000d4 00000000`00000000 00000000`4c444c00 : 0xffffec0d`037fe900
ffffec0d`037fe8f8 ffffec0d`037fead8     : 00000000`000000d4 00000000`00000000 00000000`4c444c00 ffff9708`f8d0c083 : 0xffffec0d`037fead8
ffffec0d`037fe900 00000000`000000d4     : 00000000`00000000 00000000`4c444c00 ffff9708`f8d0c083 ffffc604`51a55080 : 0xffffec0d`037fead8
ffffec0d`037fe908 00000000`00000000     : 00000000`4c444c00 ffff9708`f8d0c083 ffffc604`51a55080 ffffec0d`037feaa0 : 0xd4


SYMBOL_NAME:  klupd_K4W_21_26_arkmon+22867

MODULE_NAME: klupd_K4W_21_26_arkmon

IMAGE_NAME:  klupd_K4W-21-26_arkmon.sys

STACK_COMMAND: .process /r /p 0xffffc60451a55080; .thread /r /p 0xffffc6044cfe6080 ; kb

BUCKET_ID_FUNC_OFFSET:  22867

FAILURE_BUCKET_ID:  0x133_ISR_klupd_K4W_21_26_arkmon!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7fe1c3ad-1352-f111-1caf-f5ae8af78f90}

Followup:     MachineOwner
---------

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing


×
×
  • Create New...