电脑性能正常。 甚至什么都没动，就打开个网易云音乐听歌也会死机，毫无征兆死机，有几次自动重启电脑几分钟后又死机重启。几年前也出现过类似情况，但忘记怎么解决的了。     蓝屏的分析内容 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the BugCheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff80531c00000, Virtual address for the attempted write. Arg2: 8a000000038000a1, PTE contents. Arg3: ffff890f6003f360, (reserved) Arg4: 000000000000000f, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3061 Key : Analysis.Elapsed.mSec Value: 8350 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 530 Key : Analysis.Init.Elapsed.mSec Value: 5963 Key : Analysis.Memory.CommitPeak.Mb Value: 84 Key : Bugcheck.Code.LegacyAPI Value: 0xbe Key : Bugcheck.Code.TargetModel Value: 0xbe Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: AV_nt!MiRaisedIrqlFault Key : Failure.Hash Value: {3b24175f-7f5b-9c9f-8aaf-822c248bf0f5} BUGCHECK_CODE: be BUGCHECK_P1: fffff80531c00000 BUGCHECK_P2: 8a000000038000a1 BUGCHECK_P3: ffff890f6003f360 BUGCHECK_P4: f FILE_IN_CAB: 101924-11156-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump FAULTING_THREAD: ffffb58005b2b340 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffff890f6003f360 -- (.trap 0xffff890f6003f360) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff80531c00000 rbx=0000000000000000 rcx=0000000000000008 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff805321208d3 rsp=ffff890f6003f4f0 rbp=ffff890f6003f559 r8=0000000000000000 r9=0000000000000000 r10=0000000000000003 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiHeteroChooseTargetProcessor+0x83: fffff805`321208d3 488d45cf lea rax,[rbp-31h] Resetting default scope STACK_TEXT: ffff890f`6003f168 fffff805`3206e6c2 : 00000000`000000be fffff805`31c00000 8a000000`038000a1 ffff890f`6003f360 : nt!KeBugCheckEx ffff890f`6003f170 fffff805`31e3987f : ffff890f`6003f2d0 00000000`00000003 ffff890f`6003f3e0 00000000`00000000 : nt!MiRaisedIrqlFault+0x165562 ffff890f`6003f1c0 fffff805`3200e46d : 00000000`00000fff 00000004`063c0180 00000000`00000246 fffff805`31ef91e0 : nt!MmAccessFault+0x4ef ffff890f`6003f360 fffff805`321208d3 : ffffcc0b`48e5e210 fffff805`00000001 00000033`00015f90 ffffb580`534f5248 : nt!KiPageFault+0x36d ffff890f`6003f4f0 fffff805`32039212 : ffffb580`05b20180 ffffcc0b`48e15000 ffffb580`00000000 ffff890f`6003f5fc : nt!KiHeteroChooseTargetProcessor+0x83 ffff890f`6003f5c0 fffff805`31e2159d : 00000000`000ccdd9 ffff890f`6003fa10 00000000`00000080 ffffb580`05b20180 : nt!KiDeferredReadySingleThread+0x1e5ca2 ffff890f`6003f7b0 fffff805`31e1fc50 : ffffb580`05b20180 00000000`00000000 ffffcc0b`5808e1f0 00000000`00000000 : nt!KiReadyThread+0x4d ffff890f`6003f7e0 fffff805`31e1efa9 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`000ccdd9 : nt!KiProcessExpiredTimerList+0x290 ffff890f`6003f8d0 fffff805`32002e0e : ffffffff`00000000 ffffb580`05b20180 ffffb580`05b2b340 ffffcc0b`50132040 : nt!KiRetireDpcList+0x9d9 ffff890f`6003fb60 00000000`00000000 : ffff890f`60040000 ffff890f`60039000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e SYMBOL_NAME: nt!MiRaisedIrqlFault+165562 MODULE_NAME: nt IMAGE_VERSION: 10.0.19041.5007 STACK_COMMAND: .process /r /p 0xfffff80532924a00; .thread 0xffffb58005b2b340 ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 165562 FAILURE_BUCKET_ID: AV_nt!MiRaisedIrqlFault OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3b24175f-7f5b-9c9f-8aaf-822c248bf0f5} Followup: MachineOwner ---------    

本机CPU是i7-9750h  显卡2070  19年6月份入手的。 测试了一款名叫《SUCCUBUS:Prologue》较多敌人npc的第一人称动作游戏，开始游戏还没进入关卡前，并无大问题，fps稳定在120左右，没有卡顿。之后进竞技场后，敌人多起来了，画面特效也更花里胡哨，这时候fps还处于100左右，但是跳帧非常频繁，有时跳到50，甚至20，每次击中敌人时都会卡顿，游戏体验极其糟糕。   用ETU降了0.110v的电压，没啥大变化，纯小白不懂如何找出卡顿的原因，随意试了一下3Dmark基准测试的Night Raid，分数非常高，无异常，压力测试的Time Spy结果通过，98%，也无异常。似乎和显卡没太大关系。   另外，几个月前玩文明6烧了主板，拿去保修换了主板。一个月前换了暴力熊硅脂且不太仔细地清了灰，温度降了7 8度吧？   玩刺客信条英灵殿、赛博朋克2077等大型游戏都会出现玩久了卡顿的情况。   卡顿这个问题困扰我了好长时间了，希望大佬们能帮忙解决一下问题吧，我一个2070的游戏本居然比不过隔壁某想的1660ti，哭死。。。 暂时只想到这些了，如有什么问题我可以补充的，谢谢啦。   电脑配置