先拜谢各位大能好汉！有四次的蓝屏日志。（一）
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\123124-17734-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
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`44200000 PsLoadedModuleList = 0xfffff806`44e2a900
Debug session time: Tue Dec 31 22:36:30.218 2024 (UTC + 8:00)
System Uptime: 0 days 0:10:55.062
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff80644efb320}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
10: 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: fffff80644efb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff8064464174a to fffff806445fe580
STACK_TEXT:
ffffce80`5bfbfe18 fffff806`4464174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffce80`5bfbfe20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8064459ae7e-fffff8064459ae81 4 bytes - nt!MiFreeUltraMapping+32
[ a0 7d fb f6:40 a4 48 91 ]
4 errors : !nt (fffff8064459ae7e-fffff8064459ae81)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
图片作为分隔
（二）
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\122824-12171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`6da00000 PsLoadedModuleList = 0xfffff804`6e62a900
Debug session time: Sat Dec 28 11:13:16.405 2024 (UTC + 8:00)
System Uptime: 0 days 0:10:51.250
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff8046e6fb320}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
*** Memory manager detected 1313447 instance(s) of page corruption, target is likely to have memory corruption.
4: 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: fffff8046e6fb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: yysls_1.9.30_n
CURRENT_IRQL: d
BAD_PAGES_DETECTED: 140aa7
LAST_CONTROL_TRANSFER: from fffff8046de4174a to fffff8046ddfe580
STACK_TEXT:
ffff9480`6d2e4e18 fffff804`6de4174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9480`6d2e4e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
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 1313447 instance(s) of page corruption, target is likely to have memory corruption.
图片分割！！
（三）
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\010225-14468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`44600000 PsLoadedModuleList = 0xfffff807`4522a900
Debug session time: Thu Jan 2 22:41:06.672 2025 (UTC + 8:00)
System Uptime: 0 days 4:55:55.516
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff807452fb320}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
5: 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: fffff807452fb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff80744a4174a to fffff807449fe580
STACK_TEXT:
ffffa101`33be0c88 fffff807`44a4174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffa101`33be0c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !FLTMGR
fffff807419e5ed3-fffff807419e5ed4 2 bytes - FLTMGR!DeleteFileListCtrlCallback+43
[ 48 ff:4c 8b ]
fffff807419e5eda-fffff807419e5ede 5 bytes - FLTMGR!DeleteFileListCtrlCallback+4a (+0x07)
[ 0f 1f 44 00 00:e8 11 4d f4 02 ]
fffff807419e5eeb-fffff807419e5eec 2 bytes - FLTMGR!DeleteFileListCtrlCallback+5b (+0x11)
[ 48 ff:4c 8b ]
fffff807419e5ef2-fffff807419e5ef6 5 bytes - FLTMGR!DeleteFileListCtrlCallback+62 (+0x07)
[ 0f 1f 44 00 00:e8 49 4c e7 02 ]
fffff807419e5f33-fffff807419e5f34 2 bytes - FLTMGR!DeleteFileListCtrlCallback+a3 (+0x41)
[ 48 ff:4c 8b ]
fffff807419e5f3a-fffff807419e5f3b 2 bytes - FLTMGR!DeleteFileListCtrlCallback+aa (+0x07)
[ 0f 1f:e8 51 ]
fffff807419e5f3d-fffff807419e5f40 4 bytes - FLTMGR!DeleteFileListCtrlCallback+ad (+0x03)
[ 00 00 48 ff:e7 02 4c 8b ]
fffff807419e5f46-fffff807419e5f4a 5 bytes - FLTMGR!DeleteFileListCtrlCallback+b6 (+0x09)
[ 0f 1f 44 00 00:e8 a5 88 f3 02 ]
fffff807419ec015-fffff807419ec016 2 bytes - FLTMGR!DeleteStreamListCtrlCallback+35 (+0x60cf)
[ 48 ff:4c 8b ]
fffff807419ec01c-fffff807419ec020 5 bytes - FLTMGR!DeleteStreamListCtrlCallback+3c (+0x07)
[ 0f 1f 44 00 00:e8 cf eb f3 02 ]
fffff807419ec02a-fffff807419ec02b 2 bytes - FLTMGR!DeleteStreamListCtrlCallback+4a (+0x0e)
[ 48 ff:4c 8b ]
fffff807419ec031-fffff807419ec035 5 bytes - FLTMGR!DeleteStreamListCtrlCallback+51 (+0x07)
[ 0f 1f 44 00 00:e8 0a eb e6 02 ]
fffff807419ec07a-fffff807419ec07b 2 bytes - FLTMGR!DeleteStreamListCtrlCallback+9a (+0x49)
[ 48 ff:4c 8b ]
fffff807419ec081-fffff807419ec087 7 bytes - FLTMGR!DeleteStreamListCtrlCallback+a1 (+0x07)
[ 0f 1f 44 00 00 48 ff:e8 0a e3 e6 02 4c 8b ]
fffff807419ec08d-fffff807419ec091 5 bytes - FLTMGR!DeleteStreamListCtrlCallback+ad (+0x0c)
[ 0f 1f 44 00 00:e8 5e 27 f3 02 ]
55 errors : !FLTMGR (fffff807419e5ed3-fffff807419ec091)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
图片分割！！！
（四）
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\123024-12828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`4c800000 PsLoadedModuleList = 0xfffff800`4d42a900
Debug session time: Mon Dec 30 19:15:11.218 2024 (UTC + 8:00)
System Uptime: 0 days 1:06:54.062
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff8004d4fb320}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
6: 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: fffff8004d4fb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff8004cc4174a to fffff8004cbfe580
STACK_TEXT:
ffffa481`8849be18 fffff800`4cc4174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffa481`8849be20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8004cb9ae7e-fffff8004cb9ae81 4 bytes - nt!MiFreeUltraMapping+32
[ a0 7d fb f6:40 b2 64 c9 ]
4 errors : !nt (fffff8004cb9ae7e-fffff8004cb9ae81)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\123124-17734-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
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`44200000 PsLoadedModuleList = 0xfffff806`44e2a900
Debug session time: Tue Dec 31 22:36:30.218 2024 (UTC + 8:00)
System Uptime: 0 days 0:10:55.062
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff80644efb320}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
10: 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: fffff80644efb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff8064464174a to fffff806445fe580
STACK_TEXT:
ffffce80`5bfbfe18 fffff806`4464174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffce80`5bfbfe20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8064459ae7e-fffff8064459ae81 4 bytes - nt!MiFreeUltraMapping+32
[ a0 7d fb f6:40 a4 48 91 ]
4 errors : !nt (fffff8064459ae7e-fffff8064459ae81)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
图片作为分隔
（二）Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\122824-12171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`6da00000 PsLoadedModuleList = 0xfffff804`6e62a900
Debug session time: Sat Dec 28 11:13:16.405 2024 (UTC + 8:00)
System Uptime: 0 days 0:10:51.250
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff8046e6fb320}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
*** Memory manager detected 1313447 instance(s) of page corruption, target is likely to have memory corruption.
4: 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: fffff8046e6fb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: yysls_1.9.30_n
CURRENT_IRQL: d
BAD_PAGES_DETECTED: 140aa7
LAST_CONTROL_TRANSFER: from fffff8046de4174a to fffff8046ddfe580
STACK_TEXT:
ffff9480`6d2e4e18 fffff804`6de4174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9480`6d2e4e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
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 1313447 instance(s) of page corruption, target is likely to have memory corruption.
图片分割！！
（三）Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\010225-14468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`44600000 PsLoadedModuleList = 0xfffff807`4522a900
Debug session time: Thu Jan 2 22:41:06.672 2025 (UTC + 8:00)
System Uptime: 0 days 4:55:55.516
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff807452fb320}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
5: 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: fffff807452fb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff80744a4174a to fffff807449fe580
STACK_TEXT:
ffffa101`33be0c88 fffff807`44a4174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffa101`33be0c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !FLTMGR
fffff807419e5ed3-fffff807419e5ed4 2 bytes - FLTMGR!DeleteFileListCtrlCallback+43
[ 48 ff:4c 8b ]
fffff807419e5eda-fffff807419e5ede 5 bytes - FLTMGR!DeleteFileListCtrlCallback+4a (+0x07)
[ 0f 1f 44 00 00:e8 11 4d f4 02 ]
fffff807419e5eeb-fffff807419e5eec 2 bytes - FLTMGR!DeleteFileListCtrlCallback+5b (+0x11)
[ 48 ff:4c 8b ]
fffff807419e5ef2-fffff807419e5ef6 5 bytes - FLTMGR!DeleteFileListCtrlCallback+62 (+0x07)
[ 0f 1f 44 00 00:e8 49 4c e7 02 ]
fffff807419e5f33-fffff807419e5f34 2 bytes - FLTMGR!DeleteFileListCtrlCallback+a3 (+0x41)
[ 48 ff:4c 8b ]
fffff807419e5f3a-fffff807419e5f3b 2 bytes - FLTMGR!DeleteFileListCtrlCallback+aa (+0x07)
[ 0f 1f:e8 51 ]
fffff807419e5f3d-fffff807419e5f40 4 bytes - FLTMGR!DeleteFileListCtrlCallback+ad (+0x03)
[ 00 00 48 ff:e7 02 4c 8b ]
fffff807419e5f46-fffff807419e5f4a 5 bytes - FLTMGR!DeleteFileListCtrlCallback+b6 (+0x09)
[ 0f 1f 44 00 00:e8 a5 88 f3 02 ]
fffff807419ec015-fffff807419ec016 2 bytes - FLTMGR!DeleteStreamListCtrlCallback+35 (+0x60cf)
[ 48 ff:4c 8b ]
fffff807419ec01c-fffff807419ec020 5 bytes - FLTMGR!DeleteStreamListCtrlCallback+3c (+0x07)
[ 0f 1f 44 00 00:e8 cf eb f3 02 ]
fffff807419ec02a-fffff807419ec02b 2 bytes - FLTMGR!DeleteStreamListCtrlCallback+4a (+0x0e)
[ 48 ff:4c 8b ]
fffff807419ec031-fffff807419ec035 5 bytes - FLTMGR!DeleteStreamListCtrlCallback+51 (+0x07)
[ 0f 1f 44 00 00:e8 0a eb e6 02 ]
fffff807419ec07a-fffff807419ec07b 2 bytes - FLTMGR!DeleteStreamListCtrlCallback+9a (+0x49)
[ 48 ff:4c 8b ]
fffff807419ec081-fffff807419ec087 7 bytes - FLTMGR!DeleteStreamListCtrlCallback+a1 (+0x07)
[ 0f 1f 44 00 00 48 ff:e8 0a e3 e6 02 4c 8b ]
fffff807419ec08d-fffff807419ec091 5 bytes - FLTMGR!DeleteStreamListCtrlCallback+ad (+0x0c)
[ 0f 1f 44 00 00:e8 5e 27 f3 02 ]
55 errors : !FLTMGR (fffff807419e5ed3-fffff807419ec091)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
图片分割！！！
（四）
Loading Dump File [C:\Users\yzs\Desktop\四次蓝屏日志\123024-12828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`4c800000 PsLoadedModuleList = 0xfffff800`4d42a900
Debug session time: Mon Dec 30 19:15:11.218 2024 (UTC + 8:00)
System Uptime: 0 days 1:06:54.062
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff8004d4fb320}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
6: 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: fffff8004d4fb320
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff8004cc4174a to fffff8004cbfe580
STACK_TEXT:
ffffa481`8849be18 fffff800`4cc4174a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffa481`8849be20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x1d6f9a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8004cb9ae7e-fffff8004cb9ae81 4 bytes - nt!MiFreeUltraMapping+32
[ a0 7d fb f6:40 b2 64 c9 ]
4 errors : !nt (fffff8004cb9ae7e-fffff8004cb9ae81)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
