裝了破解版的zemax之后瘋狂藍屏，卸載之后藍屏依舊winDbg分析了一下
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8054ec0e676, The address that the exception occurred at
Arg3: ffff860a36faeee8, Exception Record Address
Arg4: ffff860a36fae730, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-EQNVKV7
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 59
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8054ec0e676
BUGCHECK_P3: ffff860a36faeee8
BUGCHECK_P4: ffff860a36fae730
EXCEPTION_RECORD: ffff860a36faeee8 -- (.exr 0xffff860a36faeee8)
ExceptionAddress: fffff8054ec0e676 (nt!MiReleaseSystemCacheView+0x000000000000008a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffff860a36fae730 -- (.cxr 0xffff860a36fae730)
rax=009641770096414c rbx=ffffdd8f49880000 rcx=fffff8054f066ea0
rdx=0000000000000000 rsi=ffffb6078b9d4038 rdi=0000000000000000
rip=fffff8054ec0e676 rsp=ffff860a36faf120 rbp=ffff860a36faf189
r8=ffff91c8f763d260 r9=0000000000000002 r10=8000000000000000
r11=ffff91eec7a4c400 r12=0000000000000000 r13=000000000000c4de
r14=0000000000000000 r15=ffff91eec7a4c400
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!MiReleaseSystemCacheView+0x8a:
fffff805`4ec0e676 4c8b2cd0 mov r13,qword ptr [rax+rdx*8] ds:002b:00964177`0096414c=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
READ_ADDRESS: ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p %s
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff860a`36faf120 fffff805`4ec0ee8e : 00000000`00000000 00000000`00000000 ffffb607`8b9d4038 ffffc78b`0dfd11f8 : nt!MiReleaseSystemCacheView+0x8a
ffff860a`36faf1f0 fffff805`4f1d49cf : ffffdd8f`498c0000 ffffc78b`0f66e8f0 00000000`00000000 00000000`00000000 : nt!MmUnmapViewInSystemCache+0x62e
ffff860a`36faf300 fffff805`4ec0b672 : 00000000`00800000 ffffb607`8dddcc30 ffffb607`8b9e80e8 00000000`00000000 : nt!CcUnmapVacb+0x63
ffff860a`36faf340 fffff805`4ec0773b : 00000000`00000001 00000000`00008000 00000000`00000000 ffff860a`36faf4b0 : nt!CcUnmapVacbArray+0x202
ffff860a`36faf3b0 fffff805`4ec4f1a7 : ffffb607`92711248 ffff860a`36faf6e0 ffff860a`00008000 00000000`00000000 : nt!CcFlushCachePriv+0x77b
ffff860a`36faf500 fffff805`4ec509d5 : ffffb607`8dddcc30 ffffa301`752de000 ffff860a`36faf6e0 ffffb607`00000000 : nt!CcMapAndCopyInToCache+0xba7
ffff860a`36faf680 fffff805`5153b62a : 00000000`00000000 ffffb607`942ea320 00000000`00000000 00000000`00000700 : nt!CcCopyWriteEx+0x105
ffff860a`36faf700 fffff805`5153753b : ffffb607`942ea298 fffff805`515371a0 00000000`00000000 ffffb607`942ea298 : Ntfs!NtfsCommonWrite+0x113a
ffff860a`36faf930 fffff805`4ecbd645 : ffffb607`8b8e1ab0 ffffb607`92be9040 ffffb607`8b8e1ab0 ffffb607`942ea328 : Ntfs!NtfsFspDispatch+0x39b
ffff860a`36fafa70 fffff805`4ed2a715 : ffffb607`92be9040 00000000`00000080 ffffb607`8b880380 000024ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffff860a`36fafb10 fffff805`4edc86ea : ffffa301`74100180 ffffb607`92be9040 fffff805`4ed2a6c0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff860a`36fafb60 00000000`00000000 : ffff860a`36fb0000 ffff860a`36fa9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
SYMBOL_NAME: nt!MiReleaseSystemCacheView+8a
MODULE_NAME: nt
STACK_COMMAND: .cxr 0xffff860a36fae730 ; kb
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: 8a
FAILURE_BUCKET_ID: AV_nt!MiReleaseSystemCacheView
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {69cdb875-d4fb-5f4b-841e-9c6017671ae8}
Followup: MachineOwner
---------
解決方法：
使用《sfc /scannow》和《Dism》自動掃描和修補系統檔案：
1. 右鍵點選桌面左下角Windows圖示，選擇【Microsoft Powershell(管理員)】
2. 逐一輸入以下指令：
Dism /Online /Cleanup-Image /CheckHealth，按回車
Dism /Online /Cleanup-Image /ScanHealth，按回車
Dism /Online /Cleanup-Image /RestoreHealth，按回車
sfc /scannow，按回車
3. 重啟電腦
4. 如果出現”有一些檔案無法修復“的回報，重復步驟1-3幾次
轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/56115.html
標籤：非技術區
上一篇：服務器維護怎么學
下一篇：一個網站被劫持的問題