【蓝屏故障】为什么人工服务分析不出蓝屏原因_360社区

360fans_38398206 发表于 2023-12-29 17:11

怎么解决？

360fans_38398206 发表于 2023-12-29 17:11

怎么解决？

360fans_27156444 发表于 2023-12-30 08:43

我的也是直接蓝屏了

360fans_53072718 发表于 2023-12-30 09:38

我用的笔记本电脑，经常出现蓝屏，合上电脑再打开，电脑就是黑屏，怎么也打不开，只能重启，如何解决这个问题？

360fans_56020504 发表于 2024-1-2 08:22

频繁发生蓝屏，谁来帮我解决？

360fans_56023282 发表于 2024-1-2 15:10

，Windows系统不可能做到【每次出现蓝屏，都能完美的记录上“罪魁祸首”】，

360fans_55004413 发表于 2024-1-3 23:53

SYSTEM THREAD EXCEPTION NOT HANDLED

微笑如墨 发表于 2024-1-4 14:38

本来想问怎么上传dump结果打开文件夹突然发现没了,系统内设定是开机一段时间后自动删除是吗?只能等下次备份一下dump了.或者加微信CPC1065

360fans_18645700 发表于 2024-1-9 10:05

插优盘，切换打印机就会蓝屏

360fans_56077432 发表于 2024-1-11 11:54

经常蓝屏再查不出问题，就卸载360了

360fans_34534759 发表于 2024-1-24 12:00

我的电脑最近也总是蓝屏，我记得前些日子系统提示Windows7微软不再支持，我也没放在心上，以为不再更新系统就没事了，是否是因为微软不再支持该系统而频繁出现蓝屏的，怎么想都是有可能的！

360fans_55409050 发表于 2024-1-24 16:25

为什么经常出现蓝屏，而且解决不好，提交不了呢

360fans_56159241 发表于 2024-1-25 08:50

360fans_56168774 发表于 2024-1-30 18:39

Windows系统不可能做到【每次出现蓝屏，都能完美的记录上“罪魁祸首

360fans_56168774 发表于 2024-1-30 18:40

为什么人工服务分析不出蓝屏原因

360fans_56203551 发表于 2024-2-2 22:37

为什么我的机子时不时开机时就出现蓝屏？

360fans_56048102 发表于 2024-2-3 08:28

电脑经常出现蓝屏，最近是每天都蓝屏一次，请问怎么解决

360fans_36106467 发表于 2024-2-16 14:15

我的电脑出现兰平，主要是我在打开图片6里图片时便出现兰平。期待回复。

360fans_56333812 发表于 2024-2-25 16:32

我的电脑有蓝屏故障，请帮我修复下

360fans_56333812 发表于 2024-2-25 16:33

我电脑出现蓝屏故障

360fans_56369704 发表于 2024-3-1 18:53

无法修复蓝屏求解决

360fans_53333692 发表于 2024-3-5 05:26

经常蓝屏老也i没给修服

360fans_39450483 发表于 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
---------

360fans_55129872 发表于 2024-3-14 11:47

经常出现蓝屏

360fans_2490941 发表于 2024-3-21 11:52

360真好！很给力!

360fans_42488826 发表于 2024-3-26 20:21

朋友们你们可以帮助吧我电脑的顽固木马处理掉吗？先谢谢了

360fans_42488826 发表于 2024-3-26 20:22

有没有朋友帮助解除我电脑的顽固木马吗？先谢谢了

360fans_50078709 发表于 2024-3-29 10:42

我的电脑老是出现蓝屏是怎么回事？求大神，联系QQ1301990377

360fans_50078709 发表于 2024-3-29 10:43

我的电脑为什么老是出现蓝屏求大神，联系QQ1301990377

360fans_56581969 发表于 2024-4-5 00:17

系统环境比较特殊是什么意思

页: 36 37 38 39 40 41 42 43 44 45 [46] 47 48

360社区's Archiver