恩，我大陸的 問了很多人 都不知道這問題應該怎麼做）
我ram 本來就是gskill 官方標註的1.5v 1600 7-8-7-24的cl7的內存
再說我cpu很穩定，跑linx 40圈 3個小時都沒問題 linx64 設定5000m，跑遊戲5－6個小時孤島危機彈頭，也沒問題
就是待機的時候會偶爾莫名其妙的掛機（1個月出現這麽1－2次），什麽操作都沒有，屏保運行運行就當機了。
這是上個月莫名其妙的開機幾分鐘后待機的時候藍屏
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`04e5a000 PsLoadedModuleList = 0xfffff800`0509f670
Debug session time: Tue Dec 20 12:48:17.486 2011 (GMT+8)
System Uptime: 0 days 0:18:16.329
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
ERROR: FindPlugIns 80070015
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8009538b30, fffffa8009538e10, fffff800051da8b0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : wininit.exe
Followup: MachineOwner
---------
6: kd> !analyze -v
ERROR: FindPlugIns 80070015
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8009538b30, Terminating object
Arg3: fffffa8009538e10, Process image file name
Arg4: fffff800051da8b0, Explanatory message (ascii)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
DEBUG_FLR_IMAGE_TIMESTAMP: 0
PROCESS_OBJECT: fffffa8009538b30
IMAGE_NAME: wininit.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`05ef20e8 fffff800`052615e2 : 00000000`000000f4 00000000`00000003 fffffa80`09538b30 fffffa80`09538e10 : nt+0x7cc40
fffff880`05ef20f0 00000000`000000f4 : 00000000`00000003 fffffa80`09538b30 fffffa80`09538e10 fffff800`051da8b0 : nt+0x4075e2
fffff880`05ef20f8 00000000`00000003 : fffffa80`09538b30 fffffa80`09538e10 fffff800`051da8b0 fffffa80`09538bb8 : 0xf4
fffff880`05ef2100 fffffa80`09538b30 : fffffa80`09538e10 fffff800`051da8b0 fffffa80`09538bb8 fffffa80`09538b30 : 0x3
fffff880`05ef2108 fffffa80`09538e10 : fffff800`051da8b0 fffffa80`09538bb8 fffffa80`09538b30 fffff800`0520e99b : 0xfffffa80`09538b30
fffff880`05ef2110 fffff800`051da8b0 : fffffa80`09538bb8 fffffa80`09538b30 fffff800`0520e99b ffffffff`ffffffff : 0xfffffa80`09538e10
fffff880`05ef2118 fffffa80`09538bb8 : fffffa80`09538b30 fffff800`0520e99b ffffffff`ffffffff fffffa80`0a56b060 : nt+0x3808b0
fffff880`05ef2120 fffffa80`09538b30 : fffff800`0520e99b ffffffff`ffffffff fffffa80`0a56b060 fffffa80`09538b30 : 0xfffffa80`09538bb8
fffff880`05ef2128 fffff800`0520e99b : ffffffff`ffffffff fffffa80`0a56b060 fffffa80`09538b30 fffffa80`09538b30 : 0xfffffa80`09538b30
fffff880`05ef2130 ffffffff`ffffffff : fffffa80`0a56b060 fffffa80`09538b30 fffffa80`09538b30 ffffffff`ffffffff : nt+0x3b499b
fffff880`05ef2138 fffffa80`0a56b060 : fffffa80`09538b30 fffffa80`09538b30 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
fffff880`05ef2140 fffffa80`09538b30 : fffffa80`09538b30 ffffffff`ffffffff 00000000`00000008 fffffa80`09538b30 : 0xfffffa80`0a56b060
fffff880`05ef2148 fffffa80`09538b30 : ffffffff`ffffffff 00000000`00000008 fffffa80`09538b30 00000000`c0000005 : 0xfffffa80`09538b30
fffff880`05ef2150 ffffffff`ffffffff : 00000000`00000008 fffffa80`09538b30 00000000`c0000005 fffffa80`0a56b060 : 0xfffffa80`09538b30
fffff880`05ef2158 00000000`00000008 : fffffa80`09538b30 00000000`c0000005 fffffa80`0a56b060 fffff800`0518e448 : 0xffffffff`ffffffff
fffff880`05ef2160 fffffa80`09538b30 : 00000000`c0000005 fffffa80`0a56b060 fffff800`0518e448 ffffffff`ffffffff : 0x8
fffff880`05ef2168 00000000`c0000005 : fffffa80`0a56b060 fffff800`0518e448 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`09538b30
fffff880`05ef2170 fffffa80`0a56b060 : fffff800`0518e448 ffffffff`ffffffff 00000000`00000001 fffffa80`09538b30 : 0xc0000005
fffff880`05ef2178 fffff800`0518e448 : ffffffff`ffffffff 00000000`00000001 fffffa80`09538b30 00000000`00000008 : 0xfffffa80`0a56b060
fffff880`05ef2180 ffffffff`ffffffff : 00000000`00000001 fffffa80`09538b30 00000000`00000008 00000000`746c6644 : nt+0x334448
fffff880`05ef2188 00000000`00000001 : fffffa80`09538b30 00000000`00000008 00000000`746c6644 fffff880`05ef2200 : 0xffffffff`ffffffff
fffff880`05ef2190 fffffa80`09538b30 : 00000000`00000008 00000000`746c6644 fffff880`05ef2200 00000000`00000000 : 0x1
fffff880`05ef2198 00000000`00000008 : 00000000`746c6644 fffff880`05ef2200 00000000`00000000 00000000`00000000 : 0xfffffa80`09538b30
fffff880`05ef21a0 00000000`746c6644 : fffff880`05ef2200 00000000`00000000 00000000`00000000 00000000`00fa0bf0 : 0x8
fffff880`05ef21a8 fffff880`05ef2200 : 00000000`00000000 00000000`00000000 00000000`00fa0bf0 00000000`00fa0630 : 0x746c6644
fffff880`05ef21b0 00000000`00000000 : 00000000`00000000 00000000`00fa0bf0 00000000`00fa0630 00000000`0010001f : 0xfffff880`05ef2200
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
能看看到底要怎麽解決？
