Hyper-V Servers Blue Screening stop error 0x20001
my server 2008 r2 + hyper-v
hardware:
acer r720 m2
cpu xeon e5530 x2
ram 48g adata 4g x12
bccode: 20001
bcp1: 0000000000000011
i install update http://support.microsoft.com/kb/2550569. it's still happen .
and that's crash memory.dmp below
microsoft (r) windows debugger version 6.11.0001.404 amd64
copyright (c) microsoft corporation. rights reserved.
loading dump file [c:\windows\memory.dmp]
kernel summary dump file: kernel 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 ntkrnlmp.exe -
windows 7 kernel version 7601 (service pack 1) mp (16 procs) free x64
product: server, suite: enterprise terminalserver singleuserts
built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
machine name:
kernel base = 0xfffff800`01617000 psloadedmodulelist = 0xfffff800`0185c670
debug session time: fri sep 30 19:17:24.294 2011 (gmt+8)
system uptime: 5 days 3:22:49.037
*********************************************************************
* 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 ntkrnlmp.exe -
loading kernel symbols
...............................................................
................................................................
.........
loading user symbols
loading unloaded module list
........................
*** error: module load completed symbols not loaded hvboot.sys
*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************
use !analyze -v detailed debugging information.
bugcheck 20001, {11, 5ef50df, 1005, fffff8838024de90}
***** kernel symbols wrong. please fix symbols analysis.
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
probably caused : hvboot.sys ( hvboot+27fa )
followup: machineowner
---------
please help thanks.
could please provide additional information regarding environment can of assistance , insight?
a bug check summary means little without additional information.
is hyper-v server blue screening or vms?
do have sp1 installed?
have tested hardware components (ram, cpu) faulty or failing or mismatch (specifically ram).
have added any drivers did not install base installation of windows server / hyper-v?
if so, have behavior without these third-party drivers? (drivers biggest pain point)
brian ehlert (hopefully have found useful) http://itproctology.blogspot.com
learn. apply. repeat.
Windows Server > Hyper-V
Comments
Post a Comment