两条8G内存,已经用WINDOWS自带的内存诊断工具测试过标准测试没有问题。
*******************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 133, {1, 1e00, fffff8003fe8f370, 0}Probably caused by : memory_corruptionFollowup: memory_corruption
--------- *** Memory manager detected 60132 instance(s) of page corruption, target is likely to have memory corruption.0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8003fe8f370
Arg4: 0000000000000000Debugging Details:
------------------
*******************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 133, {1, 1e00, fffff8003fe8f370, 0}Probably caused by : memory_corruptionFollowup: memory_corruption
--------- *** Memory manager detected 60132 instance(s) of page corruption, target is likely to have memory corruption.0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8003fe8f370
Arg4: 0000000000000000Debugging Details:
------------------