BSOD when restarting Host machine

-

hi, posting hyper-v forum think issue have hyper-v related.

i have member server running windows server 2008 sp2 x64. it’s new install , luckily it’s not live. it’s going database server. has sql server 2008 installed on , because part of application not supported on 64bit or windows 2008 running 32bit windows 2003 sp2 vm under hyper-v on same box.

now reason when boot bsod, restart smn restart , boots windows. if shutdown bsod if pause vm stop vm or shut down , let hyper-v save machine state. system logs not reveal much, warning:

the virtual storage filter driver disabled through registry. inactive disk drives.

when server running has not blue screened far. @ moment it’s not live environment , cannot until stable. have enabled virtualization support in bios, has latest updates on both guest , host os.

spec is:

host - windows 2008 sp2 dell pe410 2.4ghz quad core, 6gb ram, 3 x sas 146gb disks raid5

guest - windows 2003 sp2, 2gb ram, 2 cores, 80gb vhd

any ideas great, bsod follows. have analysed using sdk not appear show anything, @ least not me.

microsoft (r) windows debugger version 6.12.0002.633 amd64
copyright (c) microsoft corporation. rights reserved.


loading dump file [c:\users\bob\desktop\bsod\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 server 2008/windows vista kernel version 6002 (service pack 2) mp (8 procs) free x64
product: server, suite: terminalserver singleuserts
built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
machine name:
kernel base = 0xfffff800`01807000 psloadedmodulelist = 0xfffff800`019cbdd0
debug session time: mon feb 28 08:23:56.928 2011 (utc + 0:00)
system uptime: 0 days 0:00:26.786
*********************************************************************
* 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
..
*******************************************************************************
*                                                                             *
*                        bugcheck analysis                                    *
*                                                                             *
*******************************************************************************

use !analyze -v detailed debugging information.

bugcheck 1e, {ffffffffc0000096, fffff8000186f5b9, 0, 0}

*** error: module load completed symbols not loaded mssmbios.sys
*** error: symbol file not found.  defaulted export symbols hal.dll -
***** 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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    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 that      ***
***    provided these symbols if need command to    ***
***    work.                                                          ***
***                                                                   ***
***    type referenced: nt!_kprcb                                     ***
***                                                                   ***
*************************************************************************
caused : ntkrnlmp.exe ( nt!fsrtlresetbasemcb+819 )

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

 

 

hi,

 

first of all, general speaking, not recommend install other roles/applications on hyper-v host machine.

 

by way, according description, find seems system crash issue , need analyze crash dump file narrow down root cause of issue. unfortunately, not effective debug crash dump file here in forum. therefore, suggest contact microsoft customer service , support (css) via telephone dedicated support professional can assist request.

 

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

 

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

 

hope issue resolved soon.

 

 

best regards,

vincent hu

 



Windows Server  >  Hyper-V



Comments

Post a Comment

Popular posts from this blog

2008 Windows Deployment Server Properties Error

-
currently wading through setup , configuration of wds on 2008 server. have captured xp sp2 image , purposes of testing not prestaging. pxe response settings have been set "respond (known & unknown) client computers" leaving "for unknown clients, notify administrator etc" unchecked when ok properties sheet error "server properties error" "the system cannot find file specified" when attempting use command "wdsutil /approve-autoadddevices /requestid:1" in response pending devices within gui "an error occurred while trying execute command. error code: 0x6 error description: access denied" surely if not attempting add workstations domain (no prestaging) there shouldn't problem. any appreciated  answering part of own question although if can explain reason appreciated. server properties error occurs when launching windows deployment services using start>all programs>administrative tools. if access via server manager...
Read more

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

-
hi, i'm new server 2003.  installed it.  removed enhanced ie security.  proceed download , install windows server 2003 sp1, of dot net (1.1, 2.0, 3.0, 3.5, , updates), , sp2. after downloaded , installed of above, tried windows update menu option in ie.  (ie 8 windows server 2003) , sits there "done" in lower left hand corner.  never brings in window. so try www.microsoft.com -> download , trails -> update.  received error message "files required use microsoft update no longer registered or installed on computer".  click on register or reinstall files me now.  window changes , "check latest version of windows updating software .... ".   sits there (last time sat there on hour). i went on internet , found instructions: regsvr32 wuapi.dll regsvr32 wups.dll regsvr32 wuaueng.dll regsvr32 wucltui.dll regsvr32 atl.dll regsvr32 msxml3.dll did not work either.  have other suggestions?...
Read more

How do a find data in one file, search for it in another file and if not found, write a custom message to another file

-
in file if.txt, starting on 2nd line of file, data formatted follows: ah10551,a10551,cn=a10551,a10551@qts.com ah10600,a10600,cn=a10600,a10600@qts.com ah10608,a10608,cn=a10608,a10608@qts.com in file sf.txt, data formatted follows: 2011-02-16 17:26:44 sid acme\ah10551 added sid history of qts\a10551 2011-02-16 17:26:44 sid acme\ah10244 added sid history of qts\a10244 2011-02-16 17:26:45 sid acme\ah10425 added sid history of qts\a10425 please provide suggestions on how following: 1. in if.txt file, read first field first ',' , store in variable called $if1 2. in sf.txt file, search for the value stored in $if1 , if found, ignore.  if not found, write custom message in another file such as: $if1 sidhistory not migrated. these files wont large.  im trying build 'exception file' of items in if.txt file not occurring in sf.txt file. thanks in advance ideas. mtv99 many ways that... here's one... (using example data) [array]$if1=@() gc d:\if.txt...
Read more