Benutzer mit den meisten Antworten
Windows 2008 R2 STOP 0x00000050 PAGE_FAULT_IN-NONPAGED_AREA after merging vhd & avhd in Hyper-V

Frage
-
Hi all
I'm having a issue which is extreme hard to resolve.
We have a virtual Windows 2008 R2 Server, which has the PDC-Role, WSUS, DNS, DHCP, Fileservice & Printservices, in our company. My boss merged an older snaphot with the vhd a few days before. After that action the server starts up as usual, but as he tried to log on, he got a 0x00000050 STOP Bluescreen "PAGE_FAULT_IN-NONPAGED_AREA".
In this situation we have no possibility to get into the OS. The strange thing is, that the server runs completely without errors or warnings, besides the missing possibility to log on to it. In safe mode I'm able to log in, but I can't find any reason for the error. CHKDSK (/f /r) runs without finding any errors. My investigation brought me to too KB articels which possible could resolve my problem. These are KB966319 and KB951418.
KB966319:
This issue occurs when the computer contains corrupted user profiles.
Windows Server 2008 and Windows Vista SP1 try to correct profiles when the profiles are corrupted. However, the registry self-correcting feature incorrectly calculates a structure size. Therefore, the system accesses an invalid memory address.
KB951418:
This issue occurs because of a timing issue in the Server service driver. This timing issue involves the operation that adds a new SMB session to the global session table and the operation that closes an SMB session. In this timing issue, the Server service driver synchronizes these operations incorrectly. When this behavior occurs, an SMB session is added to the global session table after the session is deleted. Therefore, an entry in the global session table references freed memory. When the freed memory is accessed, you receive the Stop error message that is mentioned in the "Symptoms" section.
Both hotfixes topics are fitting to the situation I have on this server. Unfortunately I don't get them installed. I tried to do this with psexec with different options. All attempts writing the whole command in one line (psexec -u <username> -p <password> wusa.exe C:\TEMP\Windows6.1-KB951418-x64.msu /quiet /log:c:\TEMP\wusa.log) are terminating with an access denied in the wusa.log and in the event viewer. If I start the command box remote with (psexec -u <LOGIN> -p <PASSWORD> \\<server> cmd.exe) and then type the wusa commands separate, get me to a frozen command box, just like that, that apears, if you get a graphical dialog. This should not be, if I start the command with the /quiet switch.
So I got no resolution out of that. If I start the server in safe mode I have no possibility to install anything with wusa.exe - the service is not running in safe mode. Unfortunately I'm not able bringing the hotfixes to the machine over import to WSUS, too. The server is the WSUS server and the wsusadmin webconsole is not found. (Don't know if this feature ever was running...?)
Our plan B is to set up a new server to get into the domain and getting the FSMO-roles transfered... but I'm still unhappy with leaving this case unsolved.
Do you have any ideas, from the point of the error message till to the point of installing the hotfixes?
I'm really thankful.
Juergen
Antworten
-
Hallo Andrei
Herzlichen Dank für Deine Ausführungen und Tips. Tatsächlich haben wir den DC nun abgelöst. Damit hat sich der Case erledigt.
Vielen Dank für die Mühe.
Gruss
Jürgen
- Als Antwort markiert Andrei TalmaciuModerator Donnerstag, 20. Januar 2011 07:07
Alle Antworten
-
Hi Juergens,
I'm having a issue which is extreme hard to resolve.
We have a virtual Windows 2008 R2 Server, which has the PDC-Role, WSUS, DNS, DHCP, Fileservice & Printservices, in our company. My boss merged an older snaphot with the vhd a few days before. After that action the server starts up as usual, but as he tried to log on, he got a 0x00000050 STOP Bluescreen "PAGE_FAULT_IN-NONPAGED_AREA".Wurde vorher kein Backup der vhd und des Systems gemacht? Kannst du den Dump auf SkyDrive <http://skydrive.live.com> hochladen und hier verlinken, damit wir diesen auswerten können?
In this situation we have no possibility to get into the OS. The strange thing is, that the server runs completely without errors or warnings, besides the missing possibility to log on to it. In safe mode I'm able to log in, but I can't find any reason for the error. CHKDSK (/f /r) runs without finding any errors. My investigation brought me to too KB articels which possible could resolve my problem. These are KB966319 and KB951418.
Hast du mal einen neuen Domainadmin zur Anmeldung genutzt oder im
abgesicherten Modus alle unnötigen Dienste deaktiviert? Was passiert, wenn du
das Profil unter C:\user einfach unbenennst?KB966319:
This issue occurs when the computer contains corrupted user profiles.
Windows Server 2008 and Windows Vista SP1 try to correct profiles when the profiles are corrupted. However, the registry self-correcting feature incorrectly calculates a structure size. Therefore, the system accesses an invalid memory address.
KB951418:
This issue occurs because of a timing issue in the Server service driver. This timing issue involves the operation that adds a new SMB session to the global session table and the operation that closes an SMB session. In this timing issue, the Server service driver synchronizes these operations incorrectly. When this behavior occurs, an SMB session is added to the global session table after the session is deleted. Therefore, an entry in the global session table references freed memory. When the freed memory is accessed, you receive the Stop error message that is mentioned in the "Symptoms" section.
Both hotfixes topics are fitting to the situation I have on this server. Unfortunately I don't get them installed. I tried to do this with psexec with different options. All attempts writing the whole command in one line (psexec -u <username> -p <password> wusa.exe C:\TEMP\Windows6.1-KB951418-x64.msu /quiet /log:c:\TEMP\wusa.log) are terminating with an access denied in the wusa.log and in the event viewer. If I start the command box remote with (psexec -u <LOGIN> -p <PASSWORD>\\<server <file://\\<server>> cmd.exe) and then type the wusa commands separate, get me to a frozen command box, just like that, that apears, if you get a graphical dialog. This should not be, if I start the command with the /quiet switch.Our plan B is to set up a new server to get into the domain and getting the FSMO-roles transfered... but I'm still unhappy with leaving this case unsolved.
Am besten wäre ein Restore und ansonsten wirst du den Weg wohl gehen müssen.
Viele Grüße
Christian -
Hallo Christian
Herzlichen Dank, dass Du Dich unseres Problems angenommen hast.
1.) Backup: "Negativ"! Bewegungsdaten wurden immer gesichert, VHD leider nicht.
2.) Crashdump: http://cid-db3bc704bb4e2fa4.office.live.com/self.aspx/Minidumps/010711-22140-01.dmp
3.) Ja, mit neuem Domänenadmin, Profilumbenennung und auch Profilspeicherortverlegung via GPO probiert. Keine Veränderung.
Nach allen Versuchen vom WE fürchte ich, dass wir den DC tatsächlich ablösen müssen. Ich würde mich aber dennoch sehr freuen, wenn Ihr aus dem Dump noch etwas Näheres, welches meinen Augen bisher vorenthalten blieb, herausfinden könntet.
Vielen, vielen Dank.
Jürgen
-
Hallo Jürgen
vroab ist das ein nicht unterstützer Zustand:
"Active Directory does not support other methods to roll back the contents of Active Directory. In particular, Active Directory does not support any method that restores a "snapshot" of the operating system or the disk volume the operating system resides on. This kind of method causes a rollback in the update sequence number (USN) used to track changes in Active Directory. When a USN rollback occurs, the contents of the Active Directory databases on the improperly restored domain controller and its replication partners may be permanently inconsistent"
http://support.microsoft.com/kb/888794
ich habe einen SEE Kollegen gebeten sich den Dump anzuschauen. Hier seine Antwort:
"In the minidump, no root cause can be determined . We crash in the ntfs filesystem.
Apply
An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010
http://support.microsoft.com/default.aspx?scid=kb;en-US;2264080if still no go reinstall or restore backup"
Gruß
Andrei -
Hallo Andrei
Herzlichen Dank für Deine Ausführungen und Tips. Tatsächlich haben wir den DC nun abgelöst. Damit hat sich der Case erledigt.
Vielen Dank für die Mühe.
Gruss
Jürgen
- Als Antwort markiert Andrei TalmaciuModerator Donnerstag, 20. Januar 2011 07:07