win11一天蓝屏了三次，吃不消了.

生产力建议不要win11
小米MIX2s(白)

不要用amd
虎友高配版(绿色)

正常使用没出过蓝屏，估计跟生产力某些环境冲突有关
小尾巴我就菜鸡一枚 https://18sui.net炮兵学院

dmp文件显示nwifi.sys导致的蓝屏，检查无线网卡的驱动，可能是内置，也可能是外置无线网卡
红米K30 Pro(变焦版)

@冰封，根据windbg对dmp文件的分析报告，我认为内存条有问题，可能是超频过高、时序不恰当，或者坏了。

1. 三个报告记录导致崩溃的程序分别是：svchost.exe、idea64.exe、java.exe，它们都是用户空间程序。一般来说，用户空间程序不会导致蓝屏，除非出现内存错误。

2. 082122-9187-01.dmp的末尾直接记录到了一次内存错误。

建议：

1. 如果开了XMP/DOCP，关掉试试。
2. 降低内存条频率或时序。
3. 关闭超频。
4. 如果还是无效，减少内存条数量、更换内存条。

3. 另两个分析报告中，MiBadShareCount和MiUnlinkPageFromListEx听着也像和内存紧密相关的名字。
   而且崩溃的模块是NT内核本身，不是某个驱动（.sys），这非常罕见，说明问题很可能在硬件而非软件上。
   （备注：Mi和小米无关，小米不可能出现在NT内核中）

如何得到上述分析报告

1. 从微软应用商店安装“Windbg Preview”。
   

2. 点文件>Open dump file。
   

3. 等待文件加载完成，然后点!analyze -v。
   

附完整的分析报告：

• 082122-9484-01.dmp

  文本框
  Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Downloads\082122-9484-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff806`50200000 PsLoadedModuleList = 0xfffff806`50e29730 Debug session time: Sun Aug 21 11:52:05.490 2022 (UTC + 8:00) System Uptime: 0 days 21:00:27.406 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: fffff806`50617d20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8684`82d5e260=000000000000004e 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 0000000000087499, page frame number Arg3: 0000000000000002, current page state Arg4: 2238843ffffff7fe, 0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2233 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 18689 Key : Analysis.Init.CPU.mSec Value: 1014 Key : Analysis.Init.Elapsed.mSec Value: 366572 Key : Analysis.Memory.CommitPeak.Mb Value: 109 FILE_IN_CAB: 082122-9484-01.dmp DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 4e BUGCHECK_P1: 99 BUGCHECK_P2: 87499 BUGCHECK_P3: 2 BUGCHECK_P4: 2238843ffffff7fe BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: java.exe STACK_TEXT: ffff8684`82d5e258 fffff806`507a9adb : 00000000`0000004e 00000000`00000099 00000000`00087499 00000000`00000002 : nt!KeBugCheckEx ffff8684`82d5e260 fffff806`5041bb87 : 00000000`00000040 00000000`00000040 00000000`00000000 00000000`00000038 : nt!MiBadShareCount+0x4f ffff8684`82d5e2a0 fffff806`504c8899 : 00000000`00094198 00000000`00000038 ffff8684`82d5e3d0 00000000`00087499 : nt!MiDecrementShareCount+0x57 ffff8684`82d5e2d0 fffff806`508ea197 : ffffa106`572c0000 ffff8f89`8d1a0040 00000000`00000000 00000000`00000000 : nt!MmUnmapViewInSystemCache+0x999 ffff8684`82d5e480 fffff806`504c3a04 : 00000000`00400000 00000000`00000001 ffffc58b`a703daa0 ffffc58b`ae82fb48 : nt!CcUnmapVacb+0x63 ffff8684`82d5e4c0 fffff806`5045b0aa : 00000000`00000001 00000000`00500000 00000000`00400000 ffffc58b`a1d439e0 : nt!CcUnmapVacbArray+0x1d4 ffff8684`82d5e540 fffff806`50991501 : 00000000`00000000 00000000`00000001 ffff8684`82d5e640 ffff8684`82d5e658 : nt!CcGetVirtualAddress+0x29a ffff8684`82d5e5d0 fffff806`5052dc29 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000011 : nt!CcMapDataCommon+0x6d ffff8684`82d5e640 fffff806`50991337 : ffffc58b`a68ff7a0 00000000`0000000e ffffc58b`a702ed01 ffff8f89`ca67bbe0 : nt!CcMapDataForOverwrite+0xcd ffff8684`82d5e6f0 fffff806`5259864e : ffff8f89`8d0b4d00 fffff806`00040000 00000000`00000000 00000000`00040000 : nt!CcPreparePinWrite+0x77 ffff8684`82d5e7a0 fffff806`525ab27a : ffff8f89`8d0b4d90 00000000`00000088 ffff8f89`8d0b4d90 00000000`00000000 : Ntfs!LfsAllocateLbcb+0x13e ffff8684`82d5e810 fffff806`525aa6eb : 00000000`00000000 ffff8f89`8d15b1f0 00000000`00000000 00000000`00000000 : Ntfs!LfsWriteLogRecordIntoLogPage+0x7ea ffff8684`82d5e8b0 fffff806`525a9b8e : ffff8684`82d5f3e0 ffffc58b`a6fdf1b0 00000000`00000068 00000000`82d5f300 : Ntfs!LfsWrite+0x13b ffff8684`82d5e990 fffff806`525ad380 : 00000000`00000000 00000000`16940000 00000001`00000400 ffff8684`82d5ee70 : Ntfs!NtfsWriteLog+0x5ee ffff8684`82d5ebd0 fffff806`525af258 : ffff8f89`a894a010 00000000`00000000 ffff8f89`a894a018 ffff8f89`9fcbe660 : Ntfs!NtfsChangeAttributeValue+0x340 ffff8684`82d5edc0 fffff806`525b7544 : ffff8684`82d5f3e0 00000000`00000000 00000000`00000098 00000000`00000000 : Ntfs!NtfsUpdateStandardInformation+0x378 ffff8684`82d5ef00 fffff806`5256363c : 00000000`00000000 ffff8684`82d5f3b8 00000000`00000000 ffffc58b`b7ade010 : Ntfs!NtfsCommonCleanup+0x44e4 ffff8684`82d5f350 fffff806`504504a5 : ffffc58b`b6f61010 00000000`00000000 00000000`00000000 ffffc58b`b7ade518 : Ntfs!NtfsFsdCleanup+0x1ec ffff8684`82d5f6b0 fffff806`4be47bb5 : ffff8684`82d60000 ffff8684`82d59000 ffffc58b`b7ade010 ffff8684`82d5f790 : nt!IofCallDriver+0x55 ffff8684`82d5f6f0 fffff806`4be45853 : ffff8684`82d5f780 00000000`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2b5 ffff8684`82d5f760 fffff806`504504a5 : ffffc58b`bc4bbe30 fffff806`504899c8 00000000`00000000 00000000`00000000 : FLTMGR!FltpDispatch+0xa3 ffff8684`82d5f7c0 fffff806`508a7499 : ffffc58b`a6e1ed60 ffffc58b`bc4bbe30 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55 ffff8684`82d5f800 fffff806`5089002f : ffffc58b`a1d650c0 00000000`00000001 ffffc58b`bc4bbe00 00000000`00000001 : nt!IopCloseFile+0x189 ffff8684`82d5f890 fffff806`5088e839 : 00000000`00000000 00000000`00000000 00000000`000004c0 00000000`00000000 : nt!ObpCloseHandle+0x29f ffff8684`82d5f9b0 fffff806`5062a375 : ffffc58b`af448080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtClose+0x39 ffff8684`82d5f9e0 00007fff`2e024214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 00000026`169fedf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`2e024214 SYMBOL_NAME: nt!MiBadShareCount+4f MODULE_NAME: nt IMAGE_VERSION: 10.0.22000.832 STACK_COMMAND: .cxr; .ecxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 4f FAILURE_BUCKET_ID: 0x4E_99_nt!MiBadShareCount OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {60e553e9-e4c5-ed08-9be6-c353e0011003} Followup: MachineOwner ---------

• 082122-9187-01.dmp

  文本框
  Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Downloads\082122-9187-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff806`6e800000 PsLoadedModuleList = 0xfffff806`6f4296b0 Debug session time: Sun Aug 21 21:08:50.306 2022 (UTC + 8:00) System Uptime: 0 days 5:08:46.223 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: fffff806`6ec17d40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa986`f80af280=000000000000003b 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 0000000080000003, Exception code that caused the BugCheck Arg2: fffff8069f0e90e2, Address of the instruction which caused the BugCheck Arg3: ffffa986f80afbc0, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2453 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 13144 Key : Analysis.Init.CPU.mSec Value: 686 Key : Analysis.Init.Elapsed.mSec Value: 117633 Key : Analysis.Memory.CommitPeak.Mb Value: 109 FILE_IN_CAB: 082122-9187-01.dmp DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 3b BUGCHECK_P1: 80000003 BUGCHECK_P2: fffff8069f0e90e2 BUGCHECK_P3: ffffa986f80afbc0 BUGCHECK_P4: 0 CONTEXT: ffffa986f80afbc0 -- (.cxr 0xffffa986f80afbc0) rax=000000009716d568 rbx=0000000000000001 rcx=ffffe50b2a9c7010 rdx=ffffe50b3072c960 rsi=ffffe50b3072c960 rdi=ffffe50b2a9c0010 rip=fffff8069f0e90e2 rsp=ffffa986f80b05e8 rbp=ffffe50b2a9c1c28 r8=ffffe50b34296500 r9=0000000000000060 r10=fffff8066ea7d460 r11=0000000000000001 r12=ffffe50b3072c970 r13=ffffe50b2a9c87b0 r14=0000000000000060 r15=fffff806736015b8 iopl=0 nv up ei ng nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040283 nwifi!guard_dispatch_icall_nop+0x2: fffff806`9f0e90e2 cc int 3 Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe STACK_TEXT: ffffa986`f80b05e8 fffff806`9f06e818 : ffffe50b`2a9c1c28 ffffe50b`2a9c1c28 00000000`05380500 ffffa986`f80b0600 : nwifi!guard_dispatch_icall_nop+0x2 ffffa986`f80b05f0 fffff806`9f079bf2 : 00000000`00000004 00000000`00000000 fffff806`7361b050 ffffa986`f80b06c0 : nwifi!IoctlScan+0x13c ffffa986`f80b0650 fffff806`73538030 : ffffe50b`2a9c8900 fffff806`00000000 ffffe50b`2a9c87b0 ffffe50b`3072c960 : nwifi!Dot11DispatchDevCtrl+0xf2 ffffa986`f80b0690 fffff806`6ea504a5 : ffffe50b`3072c960 ffffa986`f80b0781 00000000`00000002 00000000`00000001 : ndis!ndisDummyIrpHandler+0x100 ffffa986`f80b06e0 fffff806`6ee8e7a2 : ffffe50b`3072c960 00000000`00000002 ffffe50b`3072c960 ffffe50b`2630e630 : nt!IofCallDriver+0x55 ffffa986`f80b0720 fffff806`6ee8e582 : 00000000`00000000 ffffa986`f80b0a60 00000000`00128005 ffffe50b`3072c960 : nt!IopSynchronousServiceTail+0x1d2 ffffa986`f80b07d0 fffff806`6ee8d8e6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000261`5a8ba460 : nt!IopXxxControlFile+0xc82 ffffa986`f80b0900 fffff806`6ec2a375 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`6ef88660 : nt!NtDeviceIoControlFile+0x56 ffffa986`f80b0970 00007fff`94504114 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 000000dc`419ff3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`94504114 CHKIMG_EXTENSION: !chkimg -lo 50 -db !nwifi 41 errors : !nwifi (fffff8069f0e9080-fffff8069f0e94f8) fffff8069f0e9080 *0b 42 c8 89 4c 24 08 89 *50 24 0c 41 0f ba e2 14 .B..L$..P$.A.... fffff8069f0e9090 *52 26 41 0f ba e2 1b 73 *0a 41 0f ba e2 1c 73 18 R&A....s.A....s. fffff8069f0e90a0 *13 c9 0f 01 d0 48 c1 e2 *00 48 0b d0 80 e2 06 80 .....H...H...... fffff8069f0e90b0 *d0 06 75 04 41 80 c9 04 *40 80 c9 01 44 88 0d 7d ..u.A...@...D..} fffff8069f0e90c0 *01 00 00 33 c0 48 83 c4 *00 5b c3 cc cc cc cc cc ...3.H...[...... fffff8069f0e90d0 *00 cc cc cc cc cc 66 66 *01 1f 84 00 00 00 00 00 ......ff........ fffff8069f0e90e0 01 e0 cc cc cc cc cc cc *00 cc cc cc cc cc cc cc ................ fffff8069f0e90f0 *80 cc cc cc cc cc 66 66 *03 1f 84 00 00 00 00 00 ......ff........ ... fffff8069f0e9380 *00 10 4c 11 f0 0f 10 54 *10 e0 0f 10 5c 11 d0 0f ..L....T....\... fffff8069f0e9390 10 64 11 c0 0f 29 01 48 *00 e9 40 49 ff c9 0f 29 .d...).H..@I...) fffff8069f0e93a0 *40 30 0f 29 51 20 0f 29 *50 10 0f 28 c4 75 d1 4d @0.)Q .)P..(.u.M fffff8069f0e93b0 *08 c8 49 c1 e9 04 74 19 *08 1f 84 00 00 00 00 00 ..I...t......... fffff8069f0e93c0 *05 29 01 0f 10 44 11 f0 *00 83 e9 10 49 ff c9 75 .)...D......I..u fffff8069f0e93d0 *21 49 83 e0 0f 74 0f 4c *81 d9 4d 2b d8 41 0f 10 !I...t.L..M+.A.. fffff8069f0e93e0 *00 13 41 0f 11 0b 0f 29 01 c3 cc cc cc cc cc cc ..A....)........ fffff8069f0e93f0 *84 cc cc cc cc cc cc cc *84 cc cc cc cc cc cc cc ................ ... fffff8069f0e9480 *01 10 41 0f 29 41 20 0f 11 02 c3 0f 1f 44 00 00 ..A.)A ......D.. fffff8069f0e9490 *01 83 f8 10 72 2a 4d 8d *04 08 f0 49 83 e0 20 0f ....r*M....I.. . ... fffff8069f0e94b0 *98 43 0f 11 04 01 c3 66 *0d 1f 84 00 00 00 00 00 .C.....f........ fffff8069f0e94c0 *41 83 f8 04 72 2a 4d 8d *40 08 fc 49 83 e0 08 89 A...r*M.@..I.... fffff8069f0e94d0 11 49 d1 e8 41 89 11 42 *81 14 01 49 f7 d8 43 89 .I..A..B...I..C. fffff8069f0e94e0 *10 01 c3 66 66 66 66 66 *00 1f 84 00 00 00 00 00 ...fffff........ fffff8069f0e94f0 *48 85 c0 74 11 88 11 4e *88 4c 01 fe 49 83 f8 01 H..t...N.L..I... MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xffffa986f80afbc0 ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511} Followup: memory_corruption ---------

• 082122-9484-01.dmp

  文本框
  Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Downloads\082122-9171-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff803`17800000 PsLoadedModuleList = 0xfffff803`184296b0 Debug session time: Sun Aug 21 15:59:30.971 2022 (UTC + 8:00) System Uptime: 0 days 2:53:48.887 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: fffff803`17c17d40 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffec05`254573d0=000000000000004e 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000002, A list entry was corrupt Arg2: 000000000038e623, entry in list being removed Arg3: 000000000085f7ff, highest physical page number Arg4: 0000000000000001, reference count of entry being removed Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1531 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 3643 Key : Analysis.Init.CPU.mSec Value: 624 Key : Analysis.Init.Elapsed.mSec Value: 85284 Key : Analysis.Memory.CommitPeak.Mb Value: 97 FILE_IN_CAB: 082122-9171-01.dmp DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 4e BUGCHECK_P1: 2 BUGCHECK_P2: 38e623 BUGCHECK_P3: 85f7ff BUGCHECK_P4: 1 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: idea64.exe STACK_TEXT: ffffec05`254573c8 fffff803`17c74cb7 : 00000000`0000004e 00000000`00000002 00000000`0038e623 00000000`0085f7ff : nt!KeBugCheckEx ffffec05`254573d0 fffff803`17a59361 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnlinkPageFromListEx+0x21b7b7 ffffec05`254575b0 fffff803`17a58935 : fffff379`bcde6000 fffff300`00175138 00000000`00000000 00000000`00000000 : nt!MiHandleTransitionFault+0x121 ffffec05`25457630 fffff803`17a778d9 : ffffec05`25457760 ffffc80a`447d4700 00000000`00000000 00000000`00000000 : nt!MiResolveTransitionFault+0x175 ffffec05`25457700 fffff803`17a75ba2 : ffffec05`254578e0 fffff803`00000001 00000000`c0000016 00000000`00000006 : nt!MiDispatchFault+0x4e9 ffffec05`25457840 fffff803`17c269f5 : ffffc80a`502e90c0 00000000`00000000 00000000`00000000 ffffc80a`00000000 : nt!MmAccessFault+0x152 ffffec05`254579e0 00007ffe`ee38b4e7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x335 00000000`581ffce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`ee38b4e7 SYMBOL_NAME: nt!MiUnlinkPageFromListEx+21b7b7 MODULE_NAME: nt IMAGE_VERSION: 10.0.22000.856 STACK_COMMAND: .cxr; .ecxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 21b7b7 FAILURE_BUCKET_ID: 0x4E_2_nt!MiUnlinkPageFromListEx OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ac440f38-61f7-1e91-d444-bdc71249d092} Followup: MachineOwner ---------

@老虎会游泳，你们都拿这个调试过内核啥的？好厉害

我看都看不懂

换任何系统都有问题就肯定是硬件问题
小米8(白)

@冰封，对了，最好不要混用不同容量和品牌的内存，这会带来两个问题：

1. 性能下降，时序等参数就低不就高，配置更高的内存性能发挥不出来。

2. 不同型号的内存参数（时序等）可能互不兼容，导致其中一根出现数据可靠性问题。

不过，一般来说混用不会导致内存损坏，除非你手动提升了电压。