Fragensteller
Bluescreen Ntfs.sys ( Ntfs+aaee1 )
Allgemeine Diskussion
-
Hallo!
Heute ist bei unserem Kunden der SBS 2008 mit untenstehenden Bluescreen ausgestiegen und wieder neugestartet.
Es handelt sich um einen physikalischen Hyper-V Server. Hat jemand eine Idee?
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini071311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* 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
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01c1b000 PsLoadedModuleList = 0xfffff800`01ddfdd0
Debug session time: Wed Jul 13 11:35:57.953 2011 (GMT+2)
System Uptime: 19 days 3:09:21.617
*********************************************************************
* 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
......
Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904aa, fffffa6009e17008, fffffa6009e169e0, fffffa60012b3ee1}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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 : Ntfs.sys ( Ntfs+aaee1 )
Followup: MachineOwner
---------- Typ geändert Raul TalmaciuMicrosoft contingent staff Montag, 1. August 2011 06:25 Warten auf Feedback
Alle Antworten
-
Hi Bastian,> Heute ist bei unserem Kunden der SBS 2008 mit untenstehenden Bluescreen> ausgestiegen und wieder neugestartet.>> Es handelt sich um einen physikalischen Hyper-V Server. Hat jemand eine> Idee?Vorab: Wurde auf dem SBS-Server die Hper-V Rolle aktiviert? Wenn ja, istdies ausdrücklich nicht supportet (*) und ein "erwartetes" Verhalten (einesSBS mit Hyper-V unter Last)Wenn nicht, wo tritt der Bluescreen auf? In der VM des SBS oder direkt aufdem Hyper-V Host?Welche Rollen bzw. Software wurden zusätzlich auf dem Hyper-V Host (*)installiert?* Technical Considerations for Using Hyper-V in a Windows Small BusinessServer 2008 Environment[..]Microsoft strongly recommends that a parent partition contain only theHypervisor. Because of this, Windows SBS 2008 does not support using theprimary server as a Hyper-V parent partition.[..]Source: http://technet.microsoft.com/en-us/library/dd239205(WS.10).aspx--Tobias RedelbergerStarNET Services (HomeOffice)Frankfurter Allee 193D-10365 BerlinTel: +49 (30) 86 87 02 678Mobil: +49 (163) 84 74 421Email: T.Redelberger@starnet-services.net
-
>>>Vorab: Wurde auf dem SBS-Server die Hper-V Rolle aktiviert? Wenn ja, ist>>>dies ausdrücklich nicht supportet (*) und ein "erwartetes" Verhalten (eines>>>SBS mit Hyper-V unter Last)Es handelt sich um einen Windows Server 2008 Standard mit Hyper-V. Dort gibt es 2x VM`s ( Terminalserver und SBS 2008)>>>Wenn nicht, wo tritt der Bluescreen auf? In der VM des SBS oder direkt auf>>>dem Hyper-V Host?In der VM des SBS>>>Welche Rollen bzw. Software wurden zusätzlich auf dem Hyper-V Host (*)>>>installiert?Nur die Hyper-V Rolle
-
Hi Bastian,>>>> Vorab: Wurde auf dem SBS-Server die Hper-V Rolle aktiviert? Wenn ja,>>>> ist dies ausdrücklich nicht supportet (*) und ein "erwartetes">>>> Verhalten (eines SBS mit Hyper-V unter Last)> Es handelt sich um einen Windows Server 2008 Standard mit Hyper-V. Dort> gibt es 2x VM`s ( Terminalserver und SBS 2008)>>>> Wenn nicht, wo tritt der Bluescreen auf? In der VM des SBS oder direkt>>>> auf dem Hyper-V Host?> In der VM des SBS>>>> Welche Rollen bzw. Software wurden zusätzlich auf dem Hyper-V Host (*)>>>> installiert?> Nur die Hyper-V RolleGrenz einmal anhand folgendem Artikel die Fehlermeldung ein und berichteuns von den neuen Ergebnisen:-> RESOLUTION...Des Weiteren nimm folgenden Artikel für eine bessere Debug-Analyse:How to Debug Kernel Mode Blue Screen Crashes (for beginners)--Tobias RedelbergerStarNET Services (HomeOffice)Frankfurter Allee 193D-10365 BerlinTel: +49 (30) 86 87 02 678Mobil: +49 (163) 84 74 421Email: T.Redelberger@starnet-services.net
