BYR Achieve · 镜像论坛

最近自己的win10台式机时不时的出现忽然卡死的情况，而且这个情景很难复现，一般来说是打游戏退出之后或者把游戏挂在后台并且进行任务切换的时候（比如切换桌面或者在从游戏切到浏览器）会卡死，卡死的时候看了一下机箱上的指示灯，磁盘读写的指示灯不闪烁，内存指示灯常亮。用windbg分析dump文件的提示信息放在最后。在此次故障发生之前已经做了如下操作： 1.重新插拔内存条并用橡皮擦了金手指。 2.更换了CPU和显卡的散热硅脂。 3.用windows自带的内存诊断工具对内存功能进行测试，没有报错。 4.用AIDA64单烤FPU15分钟温度不超过80度，用甜甜圈单烤显卡15分钟最高温度83度，FPU和显卡双烤15分钟温度也正常，也没有出现死机现象。 5.用AIDA64对内存进行15分钟压力测试，没有报错。 6.关闭内存XMP 其他可以提供的相关信息： 1.死机的时候后台通常挂有两个VMWARE虚拟机。 2.主机上插了4根内存条，其中两根是Samsung M323R2GA3BB0-CQKOL，另外两根是 Samsung M323R2GA3BB0-CQKOD。 3.显卡是淘宝买的"拆机卡"（懂的都懂）微星万图师2070S。有没有兄弟姐妹知道是哪个软件或者硬件出了问题，或者是有什么故障排除方案的，小弟在此感激不尽。下面为windows dump文件的提示信息 WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000004, PCI Express Error Arg2: ffffb38897d59028, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x124_4 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: System CURRENT_IRQL: 9 STACK_TEXT: fffff807`194b7cc8 fffff807`146b89fa : 00000000`00000124 00000000`00000004 ffffb388`97d59028 00000000`00000000 : nt!KeBugCheckEx fffff807`194b7cd0 fffff807`120815b0 : 00000000`00000000 ffffb388`97d59028 ffffb388`97e484b0 ffffb388`97d59028 : nt!HalBugCheckSystem+0xca fffff807`194b7d10 fffff807`147badbe : 00000000`00000000 fffff807`194b7db9 ffffb388`97d59028 ffffb388`97e484b0 : PSHED!PshedBugCheckSystem+0x10 fffff807`194b7d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x46e STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !PSHED fffff8071208104c-fffff8071208104d 2 bytes - PSHED!PshedRetrieveErrorInfo+3c [ 48 ff:4c 8b ] fffff80712081053-fffff80712081057 5 bytes - PSHED!PshedRetrieveErrorInfo+43 (+0x07) [ 0f 1f 44 00 00:e8 38 c8 39 02 ] fffff80712081098-fffff80712081099 2 bytes - PSHED!PshedRetrieveErrorInfo+88 (+0x45) [ 48 ff:4c 8b ] fffff8071208109f-fffff807120810a3 5 bytes - PSHED!PshedRetrieveErrorInfo+8f (+0x07) [ 0f 1f 44 00 00:e8 8c c9 39 02 ] fffff80712081604-fffff80712081605 2 bytes - PSHED!PshedGetErrorSourceInfo+44 (+0x565) [ 48 ff:4c 8b ] fffff8071208160b-fffff8071208160f 5 bytes - PSHED!PshedGetErrorSourceInfo+4b (+0x07) [ 0f 1f 44 00 00:e8 c0 bb 41 02 ] fffff80712081616-fffff80712081617 2 bytes - PSHED!PshedGetErrorSourceInfo+56 (+0x0b) [ 48 ff:4c 8b ] fffff8071208161d-fffff80712081621 5 bytes - PSHED!PshedGetErrorSourceInfo+5d (+0x07) [ 0f 1f 44 00 00:e8 6e c2 39 02 ] fffff80712081653-fffff80712081654 2 bytes - PSHED!PshedGetErrorSourceInfo+93 (+0x36) [ 48 ff:4c 8b ] fffff8071208165a-fffff8071208165e 5 bytes - PSHED!PshedGetErrorSourceInfo+9a (+0x07) [ 0f 1f 44 00 00:e8 d1 c3 39 02 ] fffff8071208169a-fffff8071208169b 2 bytes - PSHED!PshedSetErrorSourceInfo+1a (+0x40) [ 48 ff:4c 8b ] fffff807120816a1-fffff807120816a5 5 bytes - PSHED!PshedSetErrorSourceInfo+21 (+0x07) [ 0f 1f 44 00 00:e8 7a 92 73 02 ] 42 errors : !PSHED (fffff8071208104c-fffff807120816a5) 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

win10死机问题求助