360fans_vNpvm3
发表于 2024-3-1 18:53
无法修复蓝屏求解决
王卧冰
发表于 2024-3-5 05:26
经常 蓝 屏老也i没 给 修服
360fans_tkBD7D
发表于 2024-3-8 18:39
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41
Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`7d400000 PsLoadedModuleList = 0xfffff804`7e0298a0
Debug session time: Fri Mar8 18:18:56.306 2024 (UTC + 8:00)
System Uptime: 0 days 10:19:44.016
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`7d81d780 48894c2408 mov qword ptr ,rcx ss:0018:fffff804`814eade0=0000000000000133
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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8047e105330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for 360AntiHijack64.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: 2000
Key: Analysis.Elapsed.mSec
Value: 4243
Key: Analysis.IO.Other.Mb
Value: 13
Key: Analysis.IO.Read.Mb
Value: 0
Key: Analysis.IO.Write.Mb
Value: 29
Key: Analysis.Init.CPU.mSec
Value: 530
Key: Analysis.Init.Elapsed.mSec
Value: 365151
Key: Analysis.Memory.CommitPeak.Mb
Value: 96
Key: Bugcheck.Code.LegacyAPI
Value: 0x133
Key: Bugcheck.Code.TargetModel
Value: 0x133
Key: Dump.Attributes.AsUlong
Value: 1808
Key: Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key: Dump.Attributes.ErrorCode
Value: 0
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_DPC_360AntiHijack64!unknown_function
Key: Failure.Hash
Value: {3d292812-d066-4428-9960-436e5bab49f1}
Key: Hypervisor.Enlightenments.Value
Value: 68669340
Key: Hypervisor.Enlightenments.ValueHex
Value: 417cf9c
Key: Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key: Hypervisor.Flags.ApicEnlightened
Value: 1
Key: Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key: Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key: Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key: Hypervisor.Flags.CpuManager
Value: 1
Key: Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key: Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key: Hypervisor.Flags.Epf
Value: 0
Key: Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key: Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key: Hypervisor.Flags.MaxBankNumber
Value: 0
Key: Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key: Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key: Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key: Hypervisor.Flags.Phase0InitDone
Value: 1
Key: Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key: Hypervisor.Flags.RootScheduler
Value: 0
Key: Hypervisor.Flags.SynicAvailable
Value: 1
Key: Hypervisor.Flags.UseQpcBias
Value: 0
Key: Hypervisor.Flags.Value
Value: 4853999
Key: Hypervisor.Flags.ValueHex
Value: 4a10ef
Key: Hypervisor.Flags.VpAssistPage
Value: 1
Key: Hypervisor.Flags.VsmAvailable
Value: 1
Key: Hypervisor.RootFlags.AccessStats
Value: 1
Key: Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key: Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key: Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key: Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key: Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key: Hypervisor.RootFlags.IsHyperV
Value: 1
Key: Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key: Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key: Hypervisor.RootFlags.MceEnlightened
Value: 1
Key: Hypervisor.RootFlags.Nested
Value: 0
Key: Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key: Hypervisor.RootFlags.Value
Value: 1015
Key: Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE:133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8047e105330
FILE_IN_CAB:030824-8015-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
DPC_TIMEOUT_TYPE:SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:1
PROCESS_NAME:System
STACK_TEXT:
fffff804`814eadd8 fffff804`7d72d6be : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`814eade0 fffff804`7d72d141 : 000066e8`c1379f7e fffff804`00000500 00000000`00000002 fffff804`7d7282d8 : nt!KeAccumulateTicks+0x39e
fffff804`814eae50 fffff804`7d72b32a : fffff804`79a47200 fffff804`814d8f40 fffff804`79a47478 00000000`00000a20 : nt!KiUpdateRunTime+0x61
fffff804`814eaeb0 fffff804`7d72b116 : fffff804`7e0f7ed0 fffff804`7e0f7f80 ffffe600`00000000 fffff804`814eafc0 : nt!KeClockInterruptNotify+0x11a
fffff804`814eaf40 fffff804`7d715e40 : 00000000`00000010 ffff0d70`da3669a7 fffff804`98b24fc0 fffff804`7d81f66b : nt!HalpTimerClockIpiRoutine+0x16
fffff804`814eaf70 fffff804`7d81f8ca : fffff804`814d8fc0 fffff804`7e0f7ed0 000066e8`ae938294 ffff9702`e1e74850 : nt!KiCallInterruptServiceRoutine+0xa0
fffff804`814eafb0 fffff804`7d820137 : 00000000`00000001 00000000`00000038 fffff804`814d9180 fffff804`7d820144 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`814d8f40 fffff804`7d65c58c : 00000000`00000010 00000000`00000202 fffff804`814d90f8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`814d90d0 fffff804`7d646eda : 00000000`00000000 fffff804`8259d670 00000000`00000002 fffff804`814da1d0 : nt!KeYieldProcessorEx+0x1c
fffff804`814d9100 fffff804`7d646c25 : ffff9702`258a7af7 ffff9702`dac0f280 00000285`c47a30c1 00000000`ec29521e : nt!KxWaitForLockOwnerShip+0x2a
fffff804`814d9130 fffff804`98b17fba : 00000000`00000000 00000000`00000000 ffff9702`e5d5cb30 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLock+0xb5
fffff804`814d9160 00000000`00000000 : 00000000`00000000 ffff9702`e5d5cb30 00000000`00000000 ffffc20a`75dad080 : 360AntiHijack64+0x7fba
SYMBOL_NAME:360AntiHijack64+7fba
MODULE_NAME: 360AntiHijack64
IMAGE_NAME:360AntiHijack64.sys
STACK_COMMAND:.cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET:7fba
FAILURE_BUCKET_ID:0x133_DPC_360AntiHijack64!unknown_function
OSPLATFORM_TYPE:x64
OSNAME:Windows 10
FAILURE_ID_HASH:{3d292812-d066-4428-9960-436e5bab49f1}
Followup: MachineOwner
---------
发表于 1970-1-1 08:00
360fans_CLAqCN
发表于 2024-3-14 11:47
经常出现蓝屏
360fans_uid2490941
发表于 2024-3-21 11:52
360真好!很给力!
360fans_eKfJdg
发表于 2024-3-26 20:21
朋友们你们可以帮助吧我电脑的顽固木马处理掉吗?先谢谢了
360fans_eKfJdg
发表于 2024-3-26 20:22
有没有朋友帮助解除我电脑的顽固木马吗?先谢谢了
360fans_u50078709
发表于 2024-3-29 10:42
我的电脑老是出现蓝屏是怎么回事?求大神,联系QQ1301990377
360fans_u50078709
发表于 2024-3-29 10:43
我的电脑为什么老是出现蓝屏求大神,联系QQ1301990377
GU58125867
发表于 2024-4-5 00:17
系统环境比较特殊是什么意思
360fans430312442
发表于 2024-4-5 11:44
蓝屏为什么每次修复都修复不了,要是不能修复你们设置这个软件有什么用,都是他妈骗人的
360fans_uid5201653
发表于 2024-4-6 13:29
方式蓝屏如何修复
360fans_xsNTLH
发表于 2024-4-11 16:01
为什么每个星期每个月都会突然出现蓝屏呢???而且分析不出来是什么原因鸭??杀毒后也会出现蓝屏系统提示说没有发现有病毒。。。。老板到底是什么原因鸭???
360fans_u48768775
发表于 2024-4-15 22:42
UNEXPECTED
360fans_srBs1W
发表于 2024-4-16 08:20
各位大神们,电脑又蓝屏了,win10LTSC 版本,日常操作好好地,突然卡在蓝屏,最近出现好几次了 。麻烦大神们帮我看看{:15_457:}
终止代码: DPC WATCHDOG VIOLATION
360fans_iMiPsu
发表于 2024-4-16 15:27
还是不行
360fans_ihPdKE
发表于 2024-4-16 18:43
多次蓝屏
360fans_hXJOlv
发表于 2024-4-17 22:44
我的电脑经常出现蓝屏
360fans_nmIB6M
发表于 2024-4-20 10:56
蓝屏修复不了
360fans_Fvs1eC
发表于 2024-5-5 10:35
藍屏己发生多次均分析不出原因
360fans_OAAEFQ
发表于 2024-5-11 00:56
终上代码:KERNEL DATA INPAGE ERROR
每次都出现这个蓝屏 360蓝屏修复器也是找不出原因
内存条 硬盘全部重新插了一遍也没用 这是什么原因啊?可以加我Q帮忙一下吗:1844504332 谢谢。
360fans_1RX1LF
发表于 2024-5-13 11:09
求解决蓝屏问题,有偿,谢谢{:15_457:}
360fans76106356
发表于 2024-5-13 17:18
各位大神帮忙看下电脑蓝屏一直无法修复,要怎么处理,万分感谢!
用电脑36蓝屏修复检查不出来
360报的代码是项目:
蓝屏报错
近期经常蓝屏死机、蓝屏重启
类别:系统性能
近期经常蓝屏死机、蓝屏重启
相关文件:
C:\Windows\Minidump\040624-13640-01.dmp
C:\Windows\Minidump\042324-9593-01.dmp
C:\Windows\Minidump\042524-9625-01.dmp
C:\Windows\Minidump\051024-12453-01.dmp
C:\Windows\Minidump\051124-9890-01.dmp
360fans_DSb3px
发表于 2024-5-14 01:30
我的电脑就是一直蓝屏,cpu换了,硬盘换了,主板换了,还是一直蓝屏
CHANGXE_083
发表于 2024-5-21 22:28
您好。为什么昨天(2024.5.20)更新了QQ后电脑开机后就蓝屏,只得重新启动。
CHANGXE_083
发表于 2024-5-21 22:30
您好。为什么昨天(2024.5.20日18点余)更新了QQ后电脑开机后就蓝屏,只得重新启动。
360fans_sAkaWF
发表于 2024-5-22 11:01
我的电脑不停要求自启。369检查有蓝屏,但无法修复。
360fans_py20DG
发表于 2024-5-25 01:59
为什么分析蓝原因
360fans_YeKMMh
发表于 2024-5-30 12:00
一台主机两个显示器,一个显示器蓝屏死机,一个画面卡死不动,以前是两个卡死不动,鼠标和键盘和前两次装系统前一样直接动不了,有没有大神指导下,修电脑的师傅都说没见过这种情况