询问者
windows2012R2蓝屏报告,求教

问题
-
蓝屏分析如下所示:这是因为java引起的么
Windows 8.1 Kernel Version 9600 MP (16 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 9600.20475.amd64fre.winblue_ltsb_escrow.220622-1747
Machine Name:
Kernel base = 0xfffff803`c1c86000 PsLoadedModuleList = 0xfffff803`c1f49650
Debug session time: Mon Jan 16 05:58:07.504 2023 (UTC + 8:00)
System Uptime: 0 days 23:06:43.310
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`3aae7018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
HAL_INITIALIZATION_FAILED (5c)
Arguments:
Arg1: 0000000000000110
Arg2: ffffffffffd11d98
Arg3: 0000000000000012
Arg4: ffffffffc0000001
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2687
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2688
Key : Analysis.Init.CPU.mSec
Value: 1655
Key : Analysis.Init.Elapsed.mSec
Value: 29647
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : WER.OS.Branch
Value: winblue_ltsb_escrow
Key : WER.OS.Timestamp
Value: 2022-06-22T17:47:00Z
Key : WER.OS.Version
Value: 8.1.9600.20475
FILE_IN_CAB: MEMORY.DMP
VIRTUAL_MACHINE: VMware
BUGCHECK_CODE: 5c
BUGCHECK_P1: 110
BUGCHECK_P2: ffffffffffd11d98
BUGCHECK_P3: 12
BUGCHECK_P4: ffffffffc0000001
PROCESS_NAME: java.exe
STACK_TEXT:
ffffd000`25f22f68 fffff803`c1c32e63 : 00000000`0000005c 00000000`00000110 ffffffff`ffd11d98 00000000`00000012 : nt!KeBugCheckEx
ffffd000`25f22f70 fffff803`c1d86d72 : 00000000`0002625a ffffd000`25f23101 fffff803`c1d86b00 fffff803`00000000 : hal!HalpTimerClockArm+0x16c33
ffffd000`25f22fb0 fffff803`c1d86d32 : ffffd000`25f231e0 ffffd000`25f23150 fffff803`c1d86bf0 00000000`0002625a : nt!KiSetClockTickRate+0x3a
ffffd000`25f22ff0 fffff803`c1d86c2a : ffffd000`25f231e0 ffffd000`25f23150 fffff803`c1d86bf0 00000000`00000000 : nt!KiSetClockIntervalToMinimumRequested+0x2e
ffffd000`25f23020 fffff803`c1ceef8d : fffff803`c1f65180 ffffd000`25f23150 fffff803`c1d86bf0 ffffd000`25f23200 : nt!ExpUpdateTimerConfigurationWorker+0x3a
ffffd000`25f23050 fffff803`c2129833 : ffffe001`00000003 ffffe001`26fd4060 ffffe001`2c9080c0 ffffd000`25f23328 : nt!KeGenericProcessorCallback+0xf1
ffffd000`25f231c0 fffff803`c2129697 : ffffd000`25f23302 ffffe001`2c4d88c0 ffff5e75`1cc55fdb 00000000`00000001 : nt!ExpUpdateTimerConfiguration+0xa7
ffffd000`25f232f0 fffff803`c21294b8 : ffffe001`2c4d88c0 00000000`0002625a 00000000`00000000 00000000`00002710 : nt!ExpUpdateTimerResolution+0x57
ffffd000`25f23320 fffff803`c1dd53e3 : ffffe001`2b922080 00000000`00000001 ffffd000`25f23358 ffffe001`00000000 : nt!NtSetTimerResolution+0xf8
ffffd000`25f23380 00007ffd`99731fda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`51b6f2f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`99731fda
SYMBOL_NAME: nt!KiSetClockTickRate+3a
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 3a
FAILURE_BUCKET_ID: 0x5C_HAL_TIMER_INITIALIZATION_FAILURE_nt!KiSetClockTickRate
OS_VERSION: 8.1.9600.20475
BUILDLAB_STR: winblue_ltsb_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
FAILURE_ID_HASH: {4a4947a3-a6c1-b929-d48c-3298f25c8f85}
Followup: MachineOwner
---------
全部回复
-
0: kd> lmvm nt
Browse full module list
start end module name
fffff803`c1c86000 fffff803`c23ff000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\E94865C581EC4D45820E8D5CA952D15D1\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\symbols\ntkrnlmp.exe\62B3F922779000\ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Timestamp: Thu Jun 23 13:24:50 2022 (62B3F922)
CheckSum: 007084A9
ImageSize: 00779000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
0: kd> !process
PROCESS ffffe0012c4d88c0
SessionId: 2 Cid: 3934 Peb: 7ff73aae7000 ParentCid: 3790
DirBase: 137900000 ObjectTable: ffffc0010d8e9500 HandleCount: <Data Not Accessible>
Image: java.exe
VadRoot ffffe0012bc71d40 Vads 484 Clone 0 Private 334985. Modified 10370. Locked 2.
DeviceMap ffffc0010b9a7730
Token ffffc0010c545960
ElapsedTime 22:46:06.341
UserTime 00:00:01.062
KernelTime 00:00:00.062
QuotaPoolUsage[PagedPool] 208872
QuotaPoolUsage[NonPagedPool] 75600
Working Set Sizes (now,min,max) (338071, 50, 345) (1352284KB, 200KB, 1380KB)
PeakWorkingSetSize 484656
VirtualSize 18846 Mb
PeakVirtualSize 18858 Mb
PageFaultCount 1254165
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 751509
-
您好,
从分析来看只能确定为内核错误,硬件抽象层(HAL)无法初始化,但无法确定是否跟Java有关。建议首先卸载Java程序观察BSOD是否存在。
其次建议使用 Driver Verifier 来查找导致BSOD/崩溃的具体原因:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
同时请务必打开Special pool 功能
Best Regards,
Wesley LiPlease remember to mark the replies as answersif they help.
- 已建议为答案 Wesley LW 2023年1月31日 5:12