Critical error during WIndows update installation (#17714)

Discussions about using Windows guests in VirtualBox.
Post Reply
MJN
Posts: 5
Joined: 26. Apr 2018, 23:33

Critical error during WIndows update installation (#17714)

Post by MJN »


[ModEdit; related ticket: #17714: Ciritical Error during Windows Update (possibly VERR_PAGE_TABLE_NOT_PRESENT related)]
Host: Ubuntu 16.04.4 LTS (Xenial)
Guest: Windows 7 Professional 32-bit
Virtualbox: Version 5.2.10 r122088 (Qt5.6.1) (Installed from the virtualbox repository) with Windows Guest Additions v5.0.36

Hi,

I am getting a 'Critical Error' when booting my Win 7 OS and it occurs when attempting to install a Windows update during boot time. I have a log and screenshot but they are too big to upload (even zipped). Being a new member I can't post hyperlinks either but if you can reconstruct the link they can be downloaded from www [dot] newtonnet [dot] co [dot] uk /temp/vbox.log.zip.

I have narrowed the offending update down to '2018-04 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4093118)' which is, presumably, ideally not something I want to disable.

Does anyone have any advice as to what the problem might be and how to fix it?

Mathew
Last edited by socratis on 27. Apr 2018, 10:20, edited 2 times in total.
Reason: Added ticket related information.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error during WIndows update installation

Post by socratis »

We're going to need to see a VM log from a complete VM run:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
That ZIPPED VBox.log can't be that big if you crash at startup...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
MJN
Posts: 5
Joined: 26. Apr 2018, 23:33

Re: Critical error during WIndows update installation

Post by MJN »

Hi Socratis,

Thank you for the reply.

The log of a full VM run was in the link however if I leave the screenshot out I can now upload it here.
Attachments
vboxlog.zip
(58.28 KiB) Downloaded 136 times
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error during WIndows update installation

Post by socratis »

00:00:01.512397 GUI: 2D video acceleration is disabled
And so is the 3D acceleration. Shutdown the VM and enable them in the VM settings » Display. Then re-install the GAs in the guest.
00:00:00.893764 VRamSize <integer> = 0x0000000001500000 (22 020 096, 21 MB)
You should increase the VRAM, to 128 of 256 MB.

Those are the two minor configuration issues that I found, I don't think your setup has anything to do with:
00:01:58.440822 !! VCPU1: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
A triple fault is an unrecoverable error. Not so easy to analyze. The guest did something really nasty, it's just not easy for us users to debug.

As a reference for the developers, I believe the error to be:
00:01:58.445246 CPUM0: 0008:950f15d6 c3                      retn
00:01:58.445273 CPUM1: Disas -> VERR_PAGE_TABLE_NOT_PRESENT
but, I could be way, way off...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
MJN
Posts: 5
Joined: 26. Apr 2018, 23:33

Re: Critical error during WIndows update installation

Post by MJN »

Appreciate your time to look into this Socratis.

I have raised a ticket (#17714) with the developers and will report back if they can get me anywhere.

I also increased the VRamSize to 128MB and enabled 2D/3D Hardware Acceleration but to no avail (as you suspected).
Last edited by MJN on 27. Apr 2018, 10:22, edited 1 time in total.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error during WIndows update installation (#17714)

Post by socratis »

Thanks for posting the ticket info. I've updated your first post and the title of the thread to reflect that fact.

And yes, I suspected that the VRAM had nothing to do with it... :?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
led
Posts: 3
Joined: 29. Apr 2018, 08:52

Windows 7 critical error on startup.

Post by led »

I have 3 systems with Winndows 7 VMs that have been running quite a while. Recently they all started giving a critical error and going into guru meditation on starting, I suspect a windows update happened. The only post that I found on the subject indicated NX had to be enabled but it is. The error appears to be VINF_EM_TRIPLE_FAULT, log attached. I have tried updating VirtualBox but got no change in behaviour.

The host systems are all running Ubuntu linux, all Intel processors. Any help would be appreciated.

TIA,
Len
Attachments
vbox.log.zip
(79.54 KiB) Downloaded 155 times
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Windows 7 critical error on startup.

Post by socratis »

00:00:00.587747 [/Devices/lsilogicsas/] (level 2)
Can someone explain to me why everybody these days chooses to deviate from the defaults proposed by the template? Maybe I'm missing something...
00:00:00.587825 [/Devices/sb16/] (level 2)
And this is the perfect manifestation of a big "WHY?!?!?" case of the above problem. Sound Blaster? For a Win7 installation??? By Toutatis... :shock:
00:00:06.756249 LsiLogic#0: 0/0 (Bus/Target) doesn't exist
00:00:06.756270 LsiLogic#0: Guest issued CDB {0xa0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x10, 0x0, 0x0}
00:00:06.756702 LsiLogic#0: 0/0 (Bus/Target) doesn't exist
00:00:06.756713 LsiLogic#0: Guest issued CDB {0x12, 0x0, 0x0, 0x0, 0x24, 0x0}
... (about 2000 lines later)
00:00:06.978321 LsiLogic#0: 127/3 (Bus/Target) doesn't exist
00:00:06.978323 LsiLogic#0: Guest issued CDB {0xa0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x10, 0x0, 0x0}
00:00:06.978787 LsiLogic#0: 127/3 (Bus/Target) doesn't exist
00:00:06.978792 LsiLogic#0: Guest issued CDB {0x12, 0x0, 0x0, 0x0, 0x24, 0x0}
And that's what choosing non-default options might lead to...
VirtualBox VM 5.2.10 r122088 linux.amd64 (Apr 13 2018 21:14:36) release log
00:00:07.125950 VMMDev: Guest Additions information report: Version 4.3.28 r100309 '4.3.28'
You need to update the Guest Additions (GAs) in your guest, they're seriously outdated.
00:00:12.806559 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=2938x1187, Sending to async-handler
That's a mighty big screen. Could you take down to 1280x1024, or a "standard" size? Not full-screen, not seamless, but a normal windowed VM.
00:00:23.455093 !!         VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:23.459798 CPUM0: Disas -> VERR_PAGE_TABLE_NOT_PRESENT
There are good news and bad news. The bad news is that you're crashing (obviously). The good news is that you're not alone, which means that others are seeing the problem.

User "MJN" first reported the issue in viewtopic.php?f=7&t=87736, which is why I'm merging your thread with that one, to keep similar reports about the same issue together.

MJN also opened ticket #17714. I'd suggest that you subscribe to the ticket by posting your ZIPPED log in the ticket as well...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
led
Posts: 3
Joined: 29. Apr 2018, 08:52

Re: Critical error during WIndows update installation (#17714)

Post by led »

Here's my zipped log as requested
Attachments
vbox.log.zip
(79.54 KiB) Downloaded 127 times
led
Posts: 3
Joined: 29. Apr 2018, 08:52

Re: Critical error during WIndows update installation (#17714)

Post by led »

Sorry, uploaded the log to the wrong place. It's now attached to the ticket. I'd be happy to change the setting that resulted in [/Devices/lsilogicsas/] if you'll help me out as to which setting that might be... The SB16 dates back to a long-ago linux release that didn't like my on-board audio. I grabbed a card out of the cabinet and have never changed it. Some problem with using a card that's probably older than you are? :). At least the driver's mature. I guess I can't update my GAs until I can get it to boot...

Thanks for your help.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error during WIndows update installation (#17714)

Post by socratis »

led wrote:I'd be happy to change the setting that resulted in [/Devices/lsilogicsas/] if you'll help me out as to which setting that might be...
  1. Take a snapshot in case something goes horribly wrong, so that you can always revert to this point.
  2. In the VM Settings » Storage » you should have a couple of controllers. If you don't have a SATA controller (I don't remember the VBox.log contents), add one.
  3. Boot the VM, login, let it find the drivers for the "new" SATA controller.
  4. Shut down the VM, remove the VDI from the SCSI/LSILogic controller. Add a HD to the SATA controller, select "Choose existing disk", point it to the VDI that you just removed from the SCSI controller.
  5. Start the VM. If everything goes well, delete the snapshot from step 1.
For your sound card, simply switch from "SoundBlaster 16" to "Intel HD Audio". Drivers are there by default in a Win7 installation. Right now you shouldn't have any sound in your VM (if it didn't crash), because Win7 doesn't support an SB16 card by default; no drivers.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
MJN
Posts: 5
Joined: 26. Apr 2018, 23:33

Re: Critical error during WIndows update installation (#17714)

Post by MJN »

led wrote:I guess I can't update my GAs until I can get it to boot...
Does yours fail at the 'Preparing to configure Windows' part of the boot process as per mine? If so, try starting in Safe Mode - I did that (a couple of times I think?) and it said something to the effect of 'Reverting failed updates' and left me with a working system once more. Once (re)booted you can then disable the offending patch in Windows Update if you want to keep things working whilst a fix is (hopefully) found.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error during WIndows update installation (#17714)

Post by socratis »

Hey, that's a nice idea MJN.

But I didn't post about that. I posted because I realized that this topic doesn't belong in the "Linux Hosts" section, it belongs in the "Windows Guests" section. Moving accordingly...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
MJN
Posts: 5
Joined: 26. Apr 2018, 23:33

Re: Critical error during WIndows update installation (#17714)

Post by MJN »

A quick update on this: I am still suffering with this issue and seemingly unable to install all subsequent security updates (some have been fine). My bug report hasn't been picked up and with it being 4 months ago I am assuming it might not now be.

Anyone any ideas?

Edit: Updated to point out that some security updates have installed successfully; I am in the process of working which out of two are causing Virtualbox problems.
dhkorman
Posts: 14
Joined: 12. Aug 2009, 10:19
Primary OS: Ubuntu 8.04
VBox Version: OSE Debian
Guest OSses: Win XP, Win 7 RC1

Re: Critical error during WIndows update installation (#17714)

Post by dhkorman »

I seem to have the exact same problem. I rebooted and put it into safe mode and eventually the screen popped up "Failure configuring WIndows updates. Reverting changes. Do not turn off your computer.

I've not compared my logfile entries with those noted in this thread, but will do so shortly....

Now I have, it seems to be exactly the same problem.
Attachments
VBox.log.zip
(77.1 KiB) Downloaded 118 times
Post Reply