Windows Server 2012 Standard R2 VM has blackscreen after Windows Update while same VM on Hyper-V NO

[jmar83_the2nd]

Hi there

As title describes... but when i send Ctrl-Alt-Del the that VM, i see that blue screen (not "crash" blue screen) with options like logout etc...

IP is also stilll reachable - seems to be a gui problem only...

Here:

Unbenannt.jpg (79.79 KiB) Viewed 4996 times

That's really rally strage i.m.o... VirtualBox is v6.1.22...


Thank you very much for your feedbacks! :-)

[jmar83_the2nd]

logs here...

Neuer Ordner (2).zip

(108.1 KiB) Downloaded 7 times

[scottgus1]

The most recent log is not finished, meaning that the VM was still running.

There are four logs in the folder, besides the hardening log. Please send us one log that shows the problem happening, so we don't have to waste our volunteer time hunting in logs that may not contain useful circumstances.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[jmar83_the2nd]

thx, will look on it ASAP!

[jmar83_the2nd]

OK...

"Start the VM from full normal shutdown, not save-state."

I never started it from a save-state...

" If not possible, close the Virtualbox window for the VM with the Power Off option set."

There was no problem with shutdown via ACPI event... after i clicked "Shutdown by ACPI", the shut down and showed the dark-blue screen with white font "Windows will shut down ... " (it's a Windows Server 2012 Standard x64 R2 installation)

Seems to be a GUI problem only (that happened suddenly after last updates for my windows server 2012 installation...!?)

I use it as a file server, and i'm also able to use that file server... on other computers (clients, most with Win10 pro x64), i'm also still able wor with with that network share... hmmm..?

[jmar83_the2nd]

Here are the logs, copied after shutting down...

Neuer Ordner (4).zip

(133.07 KiB) Downloaded 5 times

[jmar83_the2nd]

Does nobody knows what the problem is...?

[scottgus1]

Sorry, Jan, I forgot about this topic.

But It seems you missed something too:

Code: Select all

Contents of "Neuer Ordner (4).zip": 
vbox.txt 
vboxhard.txt 
1.txt 
2.txt 
3.txt

Please send us one log that shows the problem happening, so we don't have to waste our volunteer time hunting in logs that may not contain useful circumstances.

Save the far left tab's log,

Salah, that's seven camels! I said no camels! Can't you count?"

Seriously, though, one log only which demonstrates the problem, please, not all logs available. I looked at 'vbox.txt'.

The 'vbox.txt' log shows no VM 'hardware' problems that I can see. The VM OS appears to run correctly. Meaning that this problem lies inside the VM OS, not in Virtualbox.

The only possibility I can think of is to try the old-school VboxVGA video card. (The VM is using the new VboxSVGA card now, note the S.)

[jmar83_the2nd]

I tried almost everything regarding VM setting... maybe the reason was a dying HDD in a RAID10 array (which should not cause problems like that, now i need to investigate closer). Or it was only a Windows problem. Or a combination of both.

Now i removed the HDD in a physical way from the RAID array and re-installed Windows Server 2012 Standard R2... seems to work again.

[scottgus1]

re-installed Windows Server 2012 Standard R2... seems to work again.

Reinstalls often fix problems. This was probably what fixed your VM.

[jmar83_the2nd]

Will better go back to Debian 11 with Samba for a fileserver - no M$ anymore!!