电脑随机蓝屏，无语中
以下为dump代码，望哪位大大能看看……谢过*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 7e806d32, The address that the exception occurred at
Arg3: f78fac38, Exception Record Address
Arg4: f78fa934, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
+16
7e806d32 ?? ???
EXCEPTION_RECORD:f78fac38 -- (.exr 0xfffffffff78fac38)
Cannot read Exception record @ f78fac38
CONTEXT:f78fa934 -- (.cxr 0xfffffffff78fa934)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT:1
DEFAULT_BUCKET_ID:DRIVER_FAULT
BUGCHECK_STR:0x7E
EXCEPTION_STR:0x0
LAST_CONTROL_TRANSFER:from 80517a9d to 7e806d32
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78facfc 80517a9d 00000000 00000000 00000000 0x7e806d32
f78fad38 8053d2b2 00000000 82e03da8 00000000 nt!MmWorkingSetManager+0x51
f78fadac 805c71ec 00000000 00000000 00000000 nt!KeBalanceSetManager+0x92
f78faddc 80542de2 8053d220 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!MmWorkingSetManager+51
80517a9d 8b3570965580 mov esi,dword ptr
SYMBOL_STACK_INDEX:1
SYMBOL_NAME:nt!MmWorkingSetManager+51
FOLLOWUP_NAME:MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:48a3fbd8
STACK_COMMAND:.cxr 0xfffffffff78fa934 ; kb
IMAGE_NAME:memory_corruption
FAILURE_BUCKET_ID:0x7E_nt!MmWorkingSetManager+51
BUCKET_ID:0x7E_nt!MmWorkingSetManager+51
Followup: MachineOwner
[ 本帖最后由 seabeam 于 2009-6-2 10:03 编辑 ] 看不懂代码的路过，一般这种问题首先是排查内存，电源和主板，用替换法一一换一下试试看 你给蓝屏图好了
DUMP代码貌似太少人研究了 你发卡饭去吧，最近流行分析这个-_- 囧，蓝屏的图么……每次都不一样 看样子发生在换页动作上
将虚拟内存设置到其它磁盘上试试 原帖由 seabeam 于 2009-6-2 10:01 发表 http://bbs.saraba1st.com/images/common/back.gif
囧，蓝屏的图么……每次都不一样
最小内存转储，直接发dump文件。 随即自动关机的路过
页:
[1]