您试试用AIDA64进行压力测试,至少持续两小时看看是否会中途崩溃。
volmgr事件 藍屏161
求問各位大神 會卡屏 藍屏 重開機 dump檔以解上面顯示未知模塊
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\User\Desktop\111922-4953-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff8034c800000 PsLoadedModuleList = 0xfffff8034d42a2f0 Debug session time: Sat Nov 19 16:15:50.833 2022 (UTC + 8:00) System Uptime: 0 days 1:10:17.625 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ........... Cannot read PEB32 from WOW64 TEB32 0000eaa8 - Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 133, {1, 1e00, fffff8034d4fb320, 0} Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 60072 instance(s) of page corruption, target is likely to have memory corruption. 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: fffff8034d4fb320 Arg4: 0000000000000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x133 PROCESS_NAME: System CURRENT_IRQL: d BAD_PAGES_DETECTED: eaa8 LAST_CONTROL_TRANSFER: from fffff8034cc5be7a to fffff8034cbf9290 STACK_TEXT: fffff80350cb3e18 fffff8034cc5be7a : 0000000000000133 0000000000000001 0000000000001e00 fffff8034d4fb320 : nt!KeBugCheckEx fffff80350cb3e20 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeAccumulateTicks+0x186c4a STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 60072 instance(s) of page corruption, target is likely to have memory corruption.
事件顯示:
電腦已經在檢查錯誤後重新啟動。檢查的錯誤是: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8034d4fb320, 0x0000000000000000)。傾印的資料已儲存於: C:\Windows\Minidump\111922-4953-01.dmp。報告識別碼: 09488c97-6d9d-4b26-a7b1-2f86f4a9f4e4。 這個是這次的 XML如下:
- <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
- <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /><EventID Qualifiers="16384">1001</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2022-11-19T08:16:26.6937617Z" /><EventRecordID>1550</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>System</Channel><Computer>DESKTOP-V9MJGE4</Computer><Security /></System>
- <EventData> <Data Name="param1">0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8034d4fb320, 0x0000000000000000)</Data><Data Name="param2">C:\Windows\Minidump\111922-4953-01.dmp</Data><Data Name="param3">09488c97-6d9d-4b26-a7b1-2f86f4a9f4e4</Data></EventData>
</Event>
上一次事件顯示 volmgr161 傾印檔案建立失敗,因為傾印期間發生錯誤。 如下XML:
- <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
- <System> <Provider Name="volmgr" /><EventID Qualifiers="49156">161</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2022-11-18T19:00:52.6507140Z" /><EventRecordID>1015</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="396" /><Channel>System</Channel><Computer>DESKTOP-V9MJGE4</Computer><Security /></System>
- <EventData> <Data>\Device\HarddiskVolume5</Data><Binary>000000000100000000000000A10004C081000200010000C000000000000000000000000000000000</Binary></EventData> </Event>
Windows for home | Windows 10 | 裝置和驅動程式
鎖定的問題。 此問題已從 Microsoft 支援服務社群移轉。 您可以對其是否有幫助進行投票,但無法對問題新增註解或回覆,或進行追蹤。