Reason Code: 0x805000f， 请求帮助解决。。。

系统自动重启，请求帮助。。

具体错误如下：

system failure: stop error
reason code: 0x805000f
bug id:
bugcheck string: 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)
comment: 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)

分析dump文件内容如下。
microsoft (r) windows debugger version 6.10.0003.233 x86
copyright (c) microsoft corporation. rights reserved.

loading dump file [c:\users\xhb\desktop\memory.dmp]
kernel complete dump file: full address space available

symbol search path is: *** invalid ***
****************************************************************************
* symbol loading may unreliable without symbol search path. *
* use .symfix have debugger choose symbol path. *
* after setting symbol path, use .reload refresh symbol locations. *
****************************************************************************
executable search path is:
*********************************************************************
* symbols can not loaded because symbol path not initialized. *
* *
* symbol path can set by: *
* using _nt_symbol_path environment variable. *
* using -y <symbol_path> argument when starting debugger. *
* using .sympath , .sympath+ *
*********************************************************************
*** error: symbol file not found. defaulted export symbols ntoskrnl.exe -
windows server 2003 kernel version 3790 (service pack 2) free x86 compatible
product: server, suite: terminalserver singleuserts
built by: 3790.srv03_sp2_gdr.101019-0340
machine name:
kernel base = 0x80800000 psloadedmodulelist = 0x808a8e48
debug session time: sat nov 26 21:28:57.841 2011 (gmt+8)
system uptime: 15 days 7:53:49.099
warning: process directory table base 1727f000 doesn't match cr3 00039000
warning: process directory table base 1727f000 doesn't match cr3 00039000
*********************************************************************
* symbols can not loaded because symbol path not initialized. *
* *
* symbol path can set by: *
* using _nt_symbol_path environment variable. *
* using -y <symbol_path> argument when starting debugger. *
* using .sympath , .sympath+ *
*********************************************************************
*** error: symbol file not found. defaulted export symbols ntoskrnl.exe -
loading kernel symbols
...............................................................
...............................................
loading user symbols
.............
loading unloaded module list
..........................................*** error: symbol file not found. defaulted export symbols ntdll.dll -

*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************

use !analyze -v detailed debugging information.

bugcheck 7f, {8, 80042000, 0, 0}

***** kernel symbols wrong. please fix symbols analysis.

*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!_kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!_kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!_kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!_kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!_kprcb ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: nt!_kprcb ***
*** ***
*************************************************************************
*** error: symbol file not found. defaulted export symbols kernel32.dll -
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: kernel32!pnlsuserinfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** debugger not using correct symbols ***
*** ***
*** in order command work properly, symbol path ***
*** must point .pdb files have full type information. ***
*** ***
*** .pdb files (such public os symbols) not ***
*** contain required information. contact group ***
*** provided these symbols if need command ***
*** work. ***
*** ***
*** type referenced: kernel32!pnlsuserinfo ***
*** ***
*************************************************************************
caused : ntoskrnl.exe ( nt!kei386eoihelper+16b2 )

followup: machineowner
---------

hi,

 

i sorry seems have requested support localized product.  since not familiar language, diffcult perform further troubleshooting steps, such capturing , analyzing log file.  these forums geared answer on english version of product. support localized versions request use support resources appropriate language.

 

chinese forum: http://social.microsoft.com/forums/zh-cn/windowsserversystemzhchs/threads

 

if issue urgent business, recommended contact microsoft product support services via telephone dedicated support professional can assist recover server in more efficient manner. please advised contacting phone support charged call.

 

to obtain phone numbers specific technology request please take @ web site listed below.

http://support.microsoft.com/default.aspx?scid=fh;en-us;phonenumbers

 

if outside please see http://support.microsoft.com regional support phone numbers.

 

thank understanding.

 

---

technology changes life……

Windows Server  >  Remote Desktop Services (Terminal Services)