询问者
vista 无故蓝屏,管理器停止工作等情况,忘高手解决!

问题
-
前几天才安装的vista sp2 版本 没多就就出现了资源管理器停止工作,ie8 停止工作, 并且一直不断出现 点了停止重新打开后
不一会又出现了 此时如果不重新启动就会出现蓝屏, 具体蓝屏代码经我多次观察 后 发现每次都不一样 看来并不是一个固定的
问题所导致的. 并说下我没装vista sp2 之前使用的是xp sp3 那时候也有一种毛病( 第一次开机后开启程序必定会出现故障,然后
导致程序停止, 特别是ie浏览网页最容易引起 一般打开大型网站 pconline.com等不一会就开始停止工作了 , windows此时就处于
不稳定状态 但是重启一次之后便可以 稳定运行了 难道是硬件故障? 搞的我每天开机后都开网页让机器死掉一次,然后重启让机器
稳定运行). 现在这个vista也出现了这种趋势了 每天第一次开机就出现上面所说的情况 搞的我痛苦不已! 希望高手解答!
注:所有windows补丁以及病毒因素都已经排除(我已经打上全部补丁,并且杀毒n次) 就不用提杀毒,重装系统的建议了 这些早已试过!
每天第一次开启后使程序出现故障的代码:
1.错误应用程序 iexplore.exe,版本 8.0.6001.18702,时间戳 0x49b3ad2e,错误模块 mshtml.dll,版本 8.0.6001.18783,时间戳 0x4a05170b,异常代码 0xc0000005,错误偏移量 0x00109362, 进程 ID 0xfcc,应用程序启动时间 0x01c9f3a80f55f5f2。
2.错误应用程序 sidebar.exe,版本 6.0.6002.18005,时间戳 0x49e02551,错误模块 gdiplus.dll,版本 5.2.6002.18005,时间戳 0x49e036f1,异常代码 0xc0000005,错误偏移量 0x00006f20, 进程 ID 0xdd0,应用程序启动时间 0x01c9f3a804200132。
3.错误应用程序 iexplore.exe,版本 8.0.6001.18702,时间戳 0x49b3ad2e,错误模块 unknown,版本 0.0.0.0,时间戳 0x00000000,异常代码 0xc0000005,错误偏移量 0x004060d8, 进程 ID 0x1094,应用程序启动时间 0x01c9f3a8b5b5a118。
4.错误应用程序 sidebar.exe,版本 6.0.6002.18005,时间戳 0x49e02551,错误模块 ntdll.dll,版本 6.0.6002.18005,时间戳 0x49e03821,异常代码 0xc0000005,错误偏移量 0x00067631, 进程 ID 0x17d4,应用程序启动时间 0x01c9f3a8e7b75d37。
5.错误应用程序 iexplore.exe,版本 8.0.6001.18702,时间戳 0x49b3ad2e,错误模块 GDI32.dll,版本 6.0.6002.18005,时间戳 0x49e03728,异常代码 0xc0000005,错误偏移量 0x00009444, 进程 ID 0xb78,应用程序启动时间 0x01c9f3a92e7a5fb2。
6.错误应用程序 Dwm.exe,版本 6.0.6002.18005,时间戳 0x49e01b94,错误模块 milcore.dll,版本 6.0.6002.18005,时间戳 0x49e03751,异常代码 0xc0000005,错误偏移量 0x0000535e, 进程 ID 0x12e0,应用程序启动时间 0x01c9f2f03f0ce0a2。
7.错误应用程序 svchost.exe_WinDefend,版本 6.0.6001.18000,时间戳 0x47918b89,错误模块 mpengine.dll,版本 1.1.4701.0,时间戳 0x4a01cc9d,异常代码 0xc0000005,错误偏移量 0x0031139e, 进程 ID 0x3b0,应用程序启动时间 0x01c9f2289205853e。
系统相关的错误信息:
1.上一次系统的 10:21:21 在 2009/6/23 上的关闭是意外的。Keywords 0x80000000000000
2.上一次系统的 19:47:13 在 2009/6/22 上的关闭是意外的。
Keywords 0x80000000000000
3.问题事件名称: BlueScreen
OS 版本: 6.0.6002.2.2.0.256.1
区域设置 ID: 2052
BCCode: a
BCP1: 00000000
BCP2: 00000002
BCP3: 00000001
BCP4: 818E2033
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
服务器信息: ce42595c-32b6-4a3a-98dc-1e71cda353d4
4.问题签名
问题事件名称: BlueScreen
OS 版本: 6.0.6002.2.2.0.256.1
区域设置 ID: 2052
BCCode: be
BCP1: 8282C714
BCP2: 047CD121
BCP3: 81D3DA68
BCP4: 0000000A
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
服务器信息: afc6d40f-6577-4410-b090-98337e037d2c
5.问题事件名称: BlueScreen
OS 版本: 6.0.6002.2.2.0.256.1
区域设置 ID: 2052
BCCode: 76
BCP1: 00000000
BCP2: 84ECD558
BCP3: 00C00000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
服务器信息: 46f5f6e0-4b64-49a9-938e-7587b272357d
6.windows资源管理器停止工作:
问题事件名称: APPCRASH
应用程序名: Explorer.EXE
应用程序版本: 6.0.6002.18005
应用程序时间戳: 49e01da5
故障模块名称: rarext.dll
故障模块版本: 3.80.0.0
故障模块时间戳: 00000000
异常代码: c0000005
异常偏移量: 00001b0b
OS 版本: 6.0.6002.2.2.0.256.1
区域设置 ID: 2052
其他信息 1: fd00
其他信息 2: ea6f5fe8924aaa756324d57f87834160
其他信息 3: fd00
其他信息 4: ea6f5fe8924aaa756324d57f87834160
程序考虑过是否内存出现问题, 但是使用memTest 测试到200%都无错 并且声,显卡驱动也更新到了最新版本
下面是我的本机硬件情况:
cpu: intel t2130
内存: 三星512M原装 + 自己购买的pny 2g内存 (刚插上去的所有并没有上述问题,运行了半年多才有上述问题的 也多次考虑过内存兼容问题)
显卡:ati x2300 主板是sis的681x
最新收到的一个windows解决方案:
解决 a video device driver 错误消息:STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER (Q293078) 提示安装新驱动 也装过了
全部回复
-
這樣你先閱讀一下這兩篇文章, 試試用裏面的方法進行分析和測試.
如何獲取轉儲文件詳細診斷信息:
http://social.microsoft.com/Forums/zh-CN/windowsserversystemzhchs/thread/48d50269-adb8-43b9-a74d-ccf1914eb72f
如何解决 Windows Vista 中执行干净启动的问题
http://support.microsoft.com/kb/929135/zh-cn
Folding@Home -
你好 根据你提供的方法我分析的结果如下:
1.09/6/23日的dmp文件如下:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up completely after an I/O.
Issue a !search over all of physical memory for the current process pointer.
This will yield at least one MDL which points to it. Then do another !search
for each MDL found, this will yield the irp(s) that point to it, revealing
which driver is leaking the pages.
Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\TrackLockedPages to a DWORD 1 value and reboot. Then the system
will save stack traces so the guilty driver can be easily identified.
When you enable this flag, if the driver commits the error again you will
see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
which can identify the offending driver(s).
Note that on newer versions of Windows (XPSP2 or WS03 and above), if you hit a
breakpoint in MmCleanProcessAddressSpace indicating the process is leaking
pages, after you press 'g', memory management will automatically enable locked
page tracking (like the registry key description above) until the system is
rebooted in order to help find the culprit.
Arguments:
Arg1: 00000000, 0
Arg2: 84ecd558, process address
Arg3: 00c00000, number of locked pages
Arg4: 00000000, pointer to driver stacks (if enabled) or 0 if not.
Debugging Details:
------------------
PROCESS_OBJECT: 84ecd558
DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x76
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81c98a4e to 81cd3b0d
STACK_TEXT:
977b6bac 81c98a4e 00000076 00000000 84ecd558 nt!KeBugCheckEx+0x1e
977b6c04 81df79cf 84ecd558 00000000 00000000 nt!MmDeleteProcessAddressSpace+0x52
977b6c3c 81e33e84 84ecd558 81fc626c 84ecd540 nt!PspProcessDelete+0x158
977b6c58 81c4adcc 84ecd558 00000000 0f90d0f1 nt!ObpRemoveObjectRoutine+0x13d
977b6c80 81cbeebc 00000002 977b6ce8 81e49f34 nt!ObfDereferenceObject+0xa1
977b6c8c 81e49f34 00000000 c000009a 81d05080 nt!MmFreeAccessPfnBuffer+0x27
977b6ce8 81e49c12 00000000 86d00630 00000000 nt!PfpFlushBuffers+0x291
977b6d7c 81ddbc42 81d05080 c6ede53d 00000000 nt!PfTLoggingWorker+0xaa
977b6dc0 81c44efe 81e49b62 81d05080 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmDeleteProcessAddressSpace+52
81c98a4e cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
SYMBOL_NAME: nt!MmDeleteProcessAddressSpace+52
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x76_System_nt!MmDeleteProcessAddressSpace+52
BUCKET_ID: 0x76_System_nt!MmDeleteProcessAddressSpace+52
Followup: MachineOwner
---------
2.09/6/21 日dmp文件信息如下:
*******************************************************************************
* *
* 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: 8282c714, Virtual address for the attempted write.
Arg2: 047cd121, PTE contents.
Arg3: 81d3da68, (reserved)
Arg4: 0000000a, (reserved)
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'crcdisk' and 'Unknown_Module_00000000' overlap
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_RC
BUGCHECK_STR: 0xBE
PROCESS_NAME: System
CURRENT_IRQL: 2
TRAP_FRAME: 81d3da68 -- (.trap ffffffff81d3da68)
ErrCode = 00000003
eax=81d3dae8 ebx=85d92f88 ecx=81d3dae8 edx=8282c714 esi=8282c360 edi=86c7c260
eip=81ceeb75 esp=81d3dadc ebp=81d3daf4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeAcquireQueuedSpinLockAtDpcLevel+0x5:
81ceeb75 8702 xchg eax,dword ptr [edx] ds:0023:8282c714=e8458d00
Resetting default scope
LAST_CONTROL_TRANSFER: from 81c95db4 to 81ce036d
STACK_TEXT:
81d3da50 81c95db4 00000001 8282c714 00000000 nt!MmAccessFault+0x10a
81d3da50 81ceeb75 00000001 8282c714 00000000 nt!KiTrap0E+0xdc
81d3dbb0 81c8ce91 00000000 81d3dc08 8d52b746 nt!KeAcquireQueuedSpinLockAtDpcLevel+0x5
81d3dbb4 00000000 81d3dc08 8d52b746 86824000 nt!EtwpGetPerfCounter+0x8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+dc
81c95db4 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+dc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
FAILURE_BUCKET_ID: 0xBE_nt!KiTrap0E+dc
BUCKET_ID: 0xBE_nt!KiTrap0E+dc
Followup: MachineOwner
---------
3.09/6/20日分析文件如下:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 818e2033}
Unable to load image \SystemRoot\system32\DRIVERS\SiSGB6.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for SiSGB6.sys
*** ERROR: Module load completed but symbols could not be loaded for SiSGB6.sys
Probably caused by : SiSGB6.sys ( SiSGB6+7373 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 818e2033, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81970868
Unable to read MiSystemVaType memory at 81950420
00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!memcpy+33
818e2033 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_RC
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 8192e174 -- (.trap ffffffff8192e174)
ErrCode = 00000002
eax=863257a4 ebx=00000042 ecx=0000000d edx=00000002 esi=8632576e edi=00000000
eip=818e2033 esp=8192e1e8 ebp=8192e1f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x33:
818e2033 f3a5 rep movs dword ptr es:[edi],dword ptr [esi] es:0023:00000000=???????? ds:0023:8632576e=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 818e2033 to 81886fb9
STACK_TEXT:
8192e174 818e2033 badb0d00 00000002 00000078 nt!KiTrap0E+0x2e1
8192e1f0 82793373 00000000 8632576e 00000036 nt!memcpy+0x33
WARNING: Stack unwind information not available. Following frames may be wrong.
8192e218 82794e43 00001068 85b26ce0 859ef598 SiSGB6+0x7373
8192e43c 8180b1f4 85b1f030 00000000 85bec430 SiSGB6+0x8e43
8192e468 8247e554 85bec430 85b1f030 859ef578 hal!HalBuildScatterGatherList+0x1ba
8192e4ac 82793222 000010e0 8632572c 85b260c8 ndis!NdisMAllocateNetBufferSGList+0x94
8192e4e0 8278d814 00000021 86325618 00000000 SiSGB6+0x7222
8192e508 8254949e 02b29228 00000000 00000000 SiSGB6+0x1814
8192e530 8247e7d7 85b1f0e8 86325618 00000000 ndis!ndisMSendNBLToMiniport+0xb4
8192e550 8247e720 86325618 86325618 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
8192e568 8d5cd4a3 85bc22d0 86325618 00000000 ndis!NdisFSendNetBufferLists+0x18
8192e5e4 8247e869 85f02910 86325618 00000000 pacer!PcFilterSendNetBufferLists+0x233
8192e600 825493b5 86325618 86325618 00000000 ndis!ndisSendNBLToFilter+0x87
8192e624 82624153 85ef9c50 86325618 00000000 ndis!NdisSendNetBufferLists+0x4f
8192e64c 8264aac2 86325618 00000001 8192e66c tcpip!FlFastSendPackets+0xc1
8192e6ac 82664a8c 00e68250 00000001 8192e744 tcpip!IpNlpFastSendDatagram+0x410
8192e7a0 82679d50 00000000 00000002 85d63632 tcpip!TcpTcbSend+0x4ac
8192e7dc 82666d9a 00000002 00000000 8192e8b8 tcpip!TcpFlushDelay+0x152
8192e80c 82666df6 84e79c40 84e6e000 84e6e018 tcpip!TcpPreValidatedReceive+0x2bf
8192e828 8266576f 84e79c40 84e6e000 8192e864 tcpip!TcpReceive+0x32
8192e838 8267d6e3 8192e84c c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
8192e864 8267d110 826d2e7c 8192e8b8 c000023e tcpip!IppDeliverListToProtocol+0x49
8192e884 8267d560 826d2c90 00000006 8192e8b8 tcpip!IppProcessDeliverList+0x2a
8192e8dc 8267ed85 826d2c90 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1eb
8192e96c 8267b280 85eba358 00000000 8191c801 tcpip!IpFlcReceivePackets+0xbe1
8192e9e8 8267ab91 85ef7920 85d89e18 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6e3
8192ea10 825490b0 85ef7920 85d89e18 00000000 tcpip!FlReceiveNetBufferListChain+0x104
8192ea44 8253bd25 00ef9c50 85d89e18 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
8192ea6c 8253bc9c 00000000 85b2933c 85b29228 ndis!ndisIndicateSortedNetBufferLists+0x4a
8192ebe8 8247c57f 85b1f0e8 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
8192ec04 8253b8f9 85b1f0e8 85d89e18 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2c
8192ec20 8247c54a 85b1f0e8 85d89e18 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x27
8192ec3c 82794737 85b1f0e8 85d89e18 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x20
8192ec88 8278dc42 00000001 00000000 85db4008 SiSGB6+0x8737
8192eca0 8253b204 85b29228 00000000 00000000 SiSGB6+0x1c42
8192ecc4 8247c468 85db401c 00000000 00000000 ndis!ndisMiniportDpc+0x81
8192ece8 818e36a2 85db401c 85b1f0e8 00000000 ndis!ndisInterruptDpc+0xc4
8192ed50 818e187d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
8192ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
SiSGB6+7373
82793373 ?? ???
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SiSGB6
IMAGE_NAME: SiSGB6.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 471469c2
SYMBOL_NAME: SiSGB6+7373
FAILURE_BUCKET_ID: 0xA_W_SiSGB6+7373
BUCKET_ID: 0xA_W_SiSGB6+7373
Followup: MachineOwner
---------
其中
*** WARNING: Unable to verify timestamp for SiSGB6.sys
*** ERROR: Module load completed but symbols could not be loaded for SiSGB6.sys
Probably caused by : SiSGB6.sys ( SiSGB6+7373 )
比较诡异 与我主板的驱动程序有关? -
你好,进入安全模式并没有蓝屏情况(我进安全模式只待了一会)
今天蓝屏的dump信息:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 8ceea5aa, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 8ceea5aa, address which referenced memoryDebugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81f45868
Unable to read MiSystemVaType memory at 81f25420
8ceea5aaCURRENT_IRQL: 2
FAULTING_IP:
+ffffffff8ceea5aa
8ceea5aa ?? ???CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_RC
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 81f03ab8 -- (.trap ffffffff81f03ab8)
ErrCode = 00000010
eax=00000000 ebx=86379c24 ecx=86379c02 edx=00000000 esi=86379aa4 edi=00002000
eip=8ceea5aa esp=81f03b2c ebp=81f03b68 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
8ceea5aa ?? ???
Resetting default scopeLAST_CONTROL_TRANSFER: from 8ceea5aa to 81e5bfb9
STACK_TEXT:
81f03ab8 8ceea5aa badb0d00 00000000 863790e0 nt!KiTrap0E+0x2e1
WARNING: Frame IP not in any known module. Following frames may be wrong.
81f03b28 8caea136 86379aa4 86379028 00000000 0x8ceea5aa
81f03b68 81eb82eb 86379c3c 86379028 6722b185 usbhub!UsbhDmTimerDpc+0x102
81f03c88 81eb7eab 81f03cd0 00000002 81f03cd8 nt!KiTimerListExpire+0x367
81f03ce8 81eb8615 00000000 00000000 0000985a nt!KiTimerExpiration+0x22a
81f03d50 81eb687d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81f03d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kbFOLLOWUP_IP:
usbhub!UsbhDmTimerDpc+102
8caea136 8b4e10 mov ecx,dword ptr [esi+10h]SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbhub
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49e01fe2
SYMBOL_NAME: usbhub!UsbhDmTimerDpc+102
FAILURE_BUCKET_ID: 0xD1_W_usbhub!UsbhDmTimerDpc+102
BUCKET_ID: 0xD1_W_usbhub!UsbhDmTimerDpc+102
Followup: MachineOwner
---------
昨天刚升级了sis最新的sql207网卡驱动 没出现SiSGB6.sys问题了 但是现在又来一个usbhub.sys
并且程序开始崩溃的时候老师提示windows数据执行保护为了保护计算机关闭了xx程序! -
ntkrpamp.exe - What is ntkrpamp.exe?
http://www.processlibrary.com/directory/files/ntkrpamp/
Folding@Home -
Description
ntkrpamp.exe is a process associated with Microsoft® Windows® Operating System from Microsoft Corporation.
Recommendation
ntkrpamp.exe should not be disabled, required for essential applications to work properly.. It is highly recommended to Run a Free Performance Scan to automatically optimize memory, CPU and Internet Settings.
看来只是个过客程序 和我的问题关联大吗? 这个好像是自动运行扫描的程序
我出现的问题和它关系不大吧? -
兩個建議:
1. 禁用 DEP 試試.
參考 nx [Optin |OptOut | AlwaysOn |AlwaysOff] 節
BCDEdit /set
http://msdn.microsoft.com/en-us/library/aa906211.aspx
2. 升級主板驅動, 如你覺得必要也包括 BIOS.
Folding@Home