*******************************************************************************
* *
* 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: fffff8800551d210, Virtual address for the attempted write.
Arg2: 000000028b837161, PTE contents.
Arg3: fffff8800265af70, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
Page 24a69f not present in the dump file. Type ".hh dbgerr004" for details
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: INVALID_KERNEL_CONTEXT
Followup: MachineOwner
---------
uj5u.com熱心網友回復：
除非你是做驅動開發，否則分析藍屏沒有任何意義，藍屏無非只有兩個可能，硬體本身壞了，或者安裝了劣質的殺毒軟體不兼容。uj5u.com熱心網友回復：
做虛擬化，虛擬機藍屏了。但這個藍屏資訊沒有明確指向是哪個模塊的問題，有途徑能分析到更明確的資訊不？
轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/94102.html
標籤：安全技術/病毒
上一篇：大神，移動硬碟出故障了，你懂嗎？