win10 蓝屏 *** warning: unable to verify timestamp for win32k.sys

      Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [G:\蓝屏故障3\072121-12531-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`0a600000 PsLoadedModuleList = 0xfffff806`0b22a1d0 Debug session time: Wed Jul 21 01:47:54.050 2021 (UTC + 8:00) System Uptime: 6 days 16:42:54.157 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................... Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck D1, {ffffe00d51200000, 2, 0, fffff8060df71083}  *** 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 ---------  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: ffffe00d51200000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8060df71083, address which referenced memory  Debugging Details: ------------------   READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd  ffffe00d51200000   CURRENT_IRQL:  2  FAULTING_IP:  tcpip!TcpEnqueueTcbSack+9e20f fffff806`0df71083 448b54c806      mov     r10d,dword ptr [rax+rcx*8+6]  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  CODE_CORRUPTION  BUGCHECK_STR:  0xD1  PROCESS_NAME:  System  LAST_CONTROL_TRANSFER:  from fffff8060aa08e69 to fffff8060a9f6f20  STACK_TEXT:   ffffa509`0ac4da48 fffff806`0aa08e69 : 00000000`0000000a ffffe00d`51200000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffa509`0ac4da50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69   STACK_COMMAND:  .bugcheck ; kb  CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndisuio     fffff80606802477-fffff80606802478  2 bytes - ndisuio!NdisuioStatus+67     [ 48 ff:4c 8b ]     fffff8060680247e-fffff80606802482  5 bytes - ndisuio!NdisuioStatus+6e (+0x07)     [ 0f 1f 44 00 00:e8 8d 54 0d 04 ]     fffff80606802504-fffff80606802505  2 bytes - ndisuio!NdisuioStatus+f4 (+0x86)     [ 48 ff:4c 8b ]     fffff8060680250b-fffff8060680250f  5 bytes - ndisuio!NdisuioStatus+fb (+0x07)     [ 0f 1f 44 00 00:e8 d0 76 48 07 ] 14 errors : !ndisuio (fffff80606802477-fffff8060680250f)  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 ---------  0: kd> k :  Numeric expression missing from ': ' 0: kd> k Child-SP          RetAddr           Call Site ffffa509`0ac4da48 fffff806`0aa08e69 nt!KeBugCheckEx ffffa509`0ac4da50 00000000`00000000 nt!KiBugCheckDispatch+0x69 0: kd> lmvm memory_corruption start             end                 module name 0: kd> lmvm memory_corruption start             end                 module name 0: kd> lmvm memory_corruption start             end                 module name      Hi,I'mPaul,anIndependentAdvisor.IhopeIcanhelpyouwithyourconcern.Thedumpfilereportindicates"MEMORY_CORRUPTION".ThisissuemightbecausedbyfaultyRAM/Memory.IrecommendthatyoutesttheRAMusingMEMTest86.Makesuretohaveatleast8fullpassesforanearconclusiveresult.Followtheguidefromthelinkbelow.https://www.tenforums.com/tutorials/14201-memte.Letmeknowtheresult.Thanks.