今天终于抓到蓝屏信息！各位帮看看。（仍未解决！）

photoshoop

系统隔几天到一周就会卡死，鼠标一顿一顿，CPU占用呈锯齿状，有时过一阵能缓过来，今天终于抓到蓝屏信息：

MEMORY_MANAGEMENT
STOP: 0X0000001A (0x00041785,0xC0E00000,0xC07197C1,0x00000000)

机器配置：
DFI P35 + E6550 + 康舒400W + 全新西数160G（数据线都换2根了）
内存 1gx4混插，D9 + 金士顿神条，过memtest 150%。
系统 XP SP2 + 全部补丁 + 最新正式驱动。

内存开4个memtest测过N多次没问题。

各位帮看看，不知哪里的问题，没辙没辙！。。。。


——————————————————

经过长时间排查（出现频率很低，很难排查！）。。。。。已排除内存混插、硬盘、独立声卡、超频原因（拔掉2根内存，拔掉独立声卡，不超频，拔掉硬盘从U盘启动纯RAM系统仍会出现该现象。。。）


目前判断：
30%显卡，30%主板
15%IDE/SATA接口，15%网卡PCI口，10%其它问题


现在已经卸掉独立声卡、IDE设备、2根内存，换了个SATA接口，不超频。如果还有问题，只能将焦点锁定网卡PCI口、显卡、主板。。。。


____________________________________________


今天再次出现该现象，什么都不做，系统狂卡，CPU占用锯齿状，但是任务管理器中除了system idle，其它进程占用均小于1%：





_

[ 本帖最后由 photoshoop 于 2008-2-2 15:15 编辑 ]

三毛妮

偶也没辙:a)

itany

装64bit系统试试……

tedsun

感觉就是超的问题
过orthos不代表稳定。

排骨饭

请教2G要开几个MEMTEST啊？两个过500%够不够？

photoshoop

又简单测了下：



测不出什么问题，现在怀疑主板，头大。。。。。

事件查看器也没查到什么蛛丝马迹。只有一个错误：The following boot-start or system-start driver(s) failed to load: avgio，貌似无关



_

[ 本帖最后由 photoshoop 于 2008-1-4 00:33 编辑 ]

johnbean

内存至少要过1000%才行,1xx%不顶事.

ljlxl

应该是内存混插问题，谁叫你上神条:a)

firstfish

原帖由 johnbean 于 2008-1-4 01:13 发表
内存至少要过1000%才行,1xx%不顶事.

扯淡，哪来的根据？这个问题就像ORTHOS究竟过多少才算稳定，目前都还没有一个官方的明确的说法。当然，过得越多越稳定是肯定的。

unifly

强烈关注中……
降到默认频率试试？

红发IXFXI

:p 先降到默认频率在说

photoshoop

频率已经从3.5G降到3.3G，准备卸掉2根内存，SATA换条线再换个口。。。

鲁爾

先降回默认频率再说

∑阿不

靠在墙边,看完红杏看结果

ahyee

看看结果如何，我也出过蓝屏。。。

shike_cuke

原帖由 ljlxl 于 2008-1-4 08:56 发表
应该是内存混插问题，谁叫你上神条:a)

我感觉也是这样,,,LZ看看拆下2跟神条的情况是怎样的

sun_tomato

内存混插问题:rolleyes:

gz_easy

原帖由 photoshoop 于 2008-1-3 21:32 发表
系统卡死，经常出现，鼠标一顿一顿，CPU占用50%以上呈锯齿状，有时过一阵能缓过来

今天终于抓到蓝屏信息

MEMORY_MANAGEMENT

STOP: 0X0000001A (0x00041785,0xC0E00000,0xC07197C1,0x00000000)


机器配置 ...

Bug Check 0x1A: MEMORY_MANAGEMENT
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.
Parameters
The following parameters are displayed on the blue screen. Parameter 1 is the only parameter of interest; this identifies the exact violation.
Parameter 1 Cause of Error
0x1 The fork clone block reference count is corrupt. (This only occurs on checked builds of Windows.)
0x777 The caller is unlocking a system cache address that is not currently locked. (This address was either never mapped or is being unlocked twice.)
0x778 The system is using the very last system cache view address, instead of preserving it.
0x780
0x781 The PTEs mapping the argument system cache view have been corrupted.
0x1000 A caller of MmGetSystemAddressForMdl* tried to map a fully-cached physical page as non-cached. This action would cause a conflicting hardware translation buffer entry, and so it was refused by the operating system. Since the caller specified "bugcheck on failure" in the requesting MDL, the system had no choice but to bugcheck in this instance.
0x1010 The caller is unlocking a pageable section that is not currently locked. (This section was either never locked or is being unlocked twice.)
0x1234 The caller is trying lock a nonexistent pageable section.
0x1235 The caller is trying to protect an MDL with an invalid mapping.
0x3451 The PTEs of an outswapped kernel thread stack are corrupt.
0x8888
0x8889 Internal memory management structures are corrupt.
0x41283 The working set index encoded in the PTE is corrupt.
0x41284 A PTE or the working set list is corrupt.
0x41286 The caller is trying to free an invalid pool address.
0x41785 The working set list is corrupt.
0x61940 A PDE has been unexpectedly invalidated.
Other An unknown memory management error occurred.

smaller

偶尔蓝蓝貌似正常，呵呵……:lol: