VBox crash -- HDMI related?

Discussions related to using VirtualBox on Windows hosts.

VBox crash -- HDMI related?

Postby abcdefgh » 24. Aug 2019, 06:48

VBox 6.0.10 r132072 (Qt5.6.2)

I experienced a VBox crash that seems to be related to a recent HDMI audio driver installation. I'm attempting to troubleshoot, but I'm having difficulty interpreting 'VBox.log'.
59:46:30.421971 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 00000000000021bc!!!

What is "59:46:30.421971"? The left side of log entries usually display time stamps of the form HH:MM:SS. What am I to make of "59:46:30.421971"?

Background:
The crash appears to be related to a Windows driver, 'LC-42LB261U (Intel(R) Display Audio)', that was loaded by Windows when I plugged in HDMI. 'LC-42LB261U' is also the model # of the Sharp TV that's on the far end of the HDMI. That common designation ('LC-42LB261U') can't simply be coincidence.

Possibly related (but probably not):
Between the computer and the TV is an HDMI Audio Extractor, a box with 'HDMI IN', 'HDMI OUT', and 6 RCA jacks (i.e., 5.1 audio) to connect to amplifiers. The Extractor's 6 RCA jacks are working only in 2.0 audio (L & R channels, only). The other channels (C, SL, SR, and LFE) are dead. The Sharp 'LC-42LB261U' TV is stereo (2.0), only. I presume that, since Windows thinks that the HDMI is plugged directly into the TV (not an Audio Extractor), it is driving only 2.0 over the HDMI.

What's important, and what I need to fix, is the crash. It has happened twice, but appears to not be reproducable.

Any assistance is greatly appreciated.

Warm Regards,
Mark.

PS: When the Linux virtual machine crashed, Windows recorded the following event (twice, 2 seconds apart):
Code: Select all   Expand viewCollapse view
Log Name:      System
Source:        Display
Date:          19-08-22 11:56:05
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      LAPTOP-FGMHQKQ8
Description:
Display driver igfx stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Display" />
    <EventID Qualifiers="0">4101</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-08-22T15:56:05.724507100Z" />
    <EventRecordID>22762</EventRecordID>
    <Channel>System</Channel>
    <Computer>LAPTOP-FGMHQKQ8</Computer>
    <Security />
  </System>
  <EventData>
    <Data>igfx</Data>
    <Data>
    </Data>
  </EventData>
</Event>
I'm actually markfilipak (which somehow became 'markfilipak2', then 'abcdefgh'). I've been here since 15 Jul 2012 but lost my name during the great shift to SSO (single sign-on) during 2017, and have not been able to recover it.
abcdefgh
 
Posts: 52
Joined: 22. Jul 2018, 03:29
Primary OS: MS Windows other
VBox Version: PUEL
Guest OSses: Linux Mint 18.3, Cinnamon

Re: VBox crash -- HDMI related?

Postby fth0 » 24. Aug 2019, 13:01

abcdefgh wrote:What is "59:46:30.421971"? The left side of log entries usually display time stamps of the form HH:MM:SS. What am I to make of "59:46:30.421971"?

A day has 24 hours, two days have 48 hours, ... SCNR ;) Seriously, the hours in the time stamps are simply counted upwards. Is it reasonable to you that the crash occurred when the VM has been running two and a half days?

Regarding your problem, posting the VBox.log file might help the forum members to help you.
fth0
Volunteer
 
Posts: 242
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: VBox crash -- HDMI related?

Postby abcdefgh » 25. Aug 2019, 01:36

fth0 wrote:
abcdefgh wrote:What is "59:46:30.421971"? The left side of log entries usually display time stamps of the form HH:MM:SS. What am I to make of "59:46:30.421971"?

A day has 24 hours, two days have 48 hours, ... SCNR ;) Seriously, the hours in the time stamps are simply counted upwards. Is it reasonable to you that the crash occurred when the VM has been running two and a half days?

Okay. That's strange, but I can live with it. So, at what time was the exception thrown? Here's another 'VBox.log' entry:
    00:00:02.899923 Log opened 2019-08-20T04:10:31.815195200Z
Code: Select all   Expand viewCollapse view
2019-08-20T04:10:31.815195200Z <-- Log opened
           59:46:30.421971 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 00000000000021bc!!!
==========================
2019-08-20T63:57:02.237166200Z

Should I add "00:00:02.899923" to "2019-08-20T04:10:31.815195200Z"? Hell, I don't know?

Now, my guess is that
Code: Select all   Expand viewCollapse view
2019-08-20 + 63:57:02.237166 = 2019-08-22 15:57:02.237166200Z <-- time of VBox exception (maybe)
                               2019-08-22 15:56:05.724507100Z <-- time of Windows event

What an insane way to make log entries: from the start of the VM instead of from system time.

So, assuming that "200Z" & "100Z" mean something and that they deduct 2 & 1 minute respectively (why?), the exception & the event are within 3 & 1/2 seconds of each other, and that the VBox exception caused the Windows event. So, if all that deduction on my part is true, then it appears that VBox provoked "Display driver igfx stopped responding and has successfully recovered".

So, what do I conclude? ...that the Linux guest additions have a bug? Your guess is as good as mine.

Regarding your problem, posting the VBox.log file might help the forum members to help you.

Here ya go:
...and thanks for looking at it (I think).

...Well, I attempted to paste 'VBox.log' into this message and I got this:
    Your message contains 271758 characters. The maximum number of allowed characters is 60000.
so I'm going to try to attach 'VBox.log' instead.

...Well, I attempted ot attach 'VBox.log' and got this:
    The file is too big, maximum allowed size is 128 KiB.

Giving up.

PS: I did search for a Windows application event that correlated with the VBox exception, but apparently, VBox doesn't record events in Windows Event logs. Wonderful. So, what have I learned? Not a damn thing.

PPS: Here's my best guess: When I plug and unplug the HDMI, VBox doesn't properly handle the video driver change. (I'm guessing that 'igfx' is a video driver, though Windows doesn't provide a clue.)
I'm actually markfilipak (which somehow became 'markfilipak2', then 'abcdefgh'). I've been here since 15 Jul 2012 but lost my name during the great shift to SSO (single sign-on) during 2017, and have not been able to recover it.
abcdefgh
 
Posts: 52
Joined: 22. Jul 2018, 03:29
Primary OS: MS Windows other
VBox Version: PUEL
Guest OSses: Linux Mint 18.3, Cinnamon

Re: VBox crash -- HDMI related?

Postby fth0 » 25. Aug 2019, 04:01

You seem to be struggling with the international time format (ISO 8601), let me explain the missing bits first:

The Windows event was created at
Code: Select all   Expand viewCollapse view
Date:          19-08-22 11:56:05
    <TimeCreated SystemTime="2019-08-22T15:56:05.724507100Z" />

The fractional seconds are simply nanoseconds, and they seem to have an accuracy of 100 ns. The 'Z' stands for Zulu (UTC), so you have to adjust the time to your local timezone, which seems to be UTC-4 or EDT. Regarding the exception, you got the math right, so it happened about one minute later; if you add the nearly 3 seconds (I'm not sure about this either), then you have approximately 60 seconds between the two events.

Regarding the VBox.log file, you should zip the file before attaching it.
fth0
Volunteer
 
Posts: 242
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: VBox crash -- HDMI related?

Postby abcdefgh » 25. Aug 2019, 06:22

fth0 wrote:You seem to be struggling with the international time format (ISO 8601), let me explain the missing bits first:

The Windows event was created at
Code: Select all   Expand viewCollapse view
Date:          19-08-22 11:56:05
    <TimeCreated SystemTime="2019-08-22T15:56:05.724507100Z" />

The fractional seconds are simply nanoseconds, and they seem to have an accuracy of 100 ns. The 'Z' stands for Zulu (UTC), so you have to adjust the time to your local timezone, which seems to be UTC-4 or EDT. Regarding the exception, you got the math right, so it happened about one minute later; if you add the nearly 3 seconds (I'm not sure about this either), then you have approximately 60 seconds between the two events.

Thank you for that. Yeah, I knew all that stuff (though the timezones are usually indicated as "-4" for US East Coast, etc.) but "100Z"? "200Z"? That's the middle of the Atlantic! (Or maybe the middle of Europe -- I always thought that having a sign (+/-) preceeding a timezone was a bad idea, that the timezone suffix should have been 0,1,2,...23.)
Regarding the VBox.log file, you should zip the file before attaching it.

Now that you've helped work out the times and I can confidently cull 'VBox.log' to just this stuff, I'll cull it, zip it, and attach. Thanks. I look forward to your analysis. I hope it profits the VBox developers.
Attachments
`19-08-22 115710 culled version of VBox.log.zip
(25.01 KiB) Downloaded 11 times
I'm actually markfilipak (which somehow became 'markfilipak2', then 'abcdefgh'). I've been here since 15 Jul 2012 but lost my name during the great shift to SSO (single sign-on) during 2017, and have not been able to recover it.
abcdefgh
 
Posts: 52
Joined: 22. Jul 2018, 03:29
Primary OS: MS Windows other
VBox Version: PUEL
Guest OSses: Linux Mint 18.3, Cinnamon

Re: VBox crash -- HDMI related?

Postby Martin » 25. Aug 2019, 10:32

We need the complete log file because there is other necessary information like configuration settings and detected enviornment in other parts of the log.

My crystal ball guesses that your problem is the audio device "disappearing" while the VM is using it.
This has probably a similar effect to a PC where you pull out the audio card while it is running.
The HDMI connection to your TV adds an additional video device and an additional audio device. When you get a connection problem these device are not there anymore

Some time ago I also had the desktop environment of a Linux PC (without Vbox) crashing when the TV connected as display went into power saving mode.
Martin
Volunteer
 
Posts: 2251
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Linux, OS/2

Re: VBox crash -- HDMI related?

Postby abcdefgh » 25. Aug 2019, 11:12

Martin wrote:We need the complete log file...

Oh, sorry. I'll try to attach the whole thing.

My crystal ball guesses that your problem is the audio device "disappearing" while the VM is using it.

My thought exactly. I've posted a query to Microsoft Technet inquiring how I can force the HDMI to always be present and driven, even with the TV off. There's no response yet.
This has probably a similar effect to a PC where you pull out the audio card while it is running.

I can't comment on that because I've never been that crazy.
The HDMI connection to your TV adds an additional video device and an additional audio device. When you get a connection problem these device are not there anymore.

There's no connection problem, at least, not in Windows. The driver is there all the time (according to Control Panel, Device Manager). Oddly, the device driver has the same name as the model number of the Sharp TV.
Some time ago I also had the desktop environment of a Linux PC (without Vbox) crashing when the TV connected as display went into power saving mode.

Now, that's a good clue. The VM guest is Linux.
Attachments
`19-08-22 115710 VBox.log.zip
(49.1 KiB) Downloaded 11 times
I'm actually markfilipak (which somehow became 'markfilipak2', then 'abcdefgh'). I've been here since 15 Jul 2012 but lost my name during the great shift to SSO (single sign-on) during 2017, and have not been able to recover it.
abcdefgh
 
Posts: 52
Joined: 22. Jul 2018, 03:29
Primary OS: MS Windows other
VBox Version: PUEL
Guest OSses: Linux Mint 18.3, Cinnamon

Re: VBox crash -- HDMI related?

Postby fth0 » 25. Aug 2019, 15:19

abcdefgh wrote:Yeah, I knew all that stuff (though the timezones are usually indicated as "-4" for US East Coast, etc.) but "100Z"?

I'm still not convinced. ;) Nanoseconds are 10^-9 seconds (e.g. 724507100 ns), and 'Z' equals '+0000'. You may read https://en.wikipedia.org/wiki/ISO_8601 for clarification, if you're interested.
fth0
Volunteer
 
Posts: 242
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: VBox crash -- HDMI related?

Postby fth0 » 25. Aug 2019, 17:04

After reading the VBox.log file, I learned a lot about your configuration, but I still cannot provide you with a solution. But I can point you in some directions for investigating further (e.g. via Google):

  1. The exception occurred in a thread named ShCrOpenGL. There are several search results in the VirtualBox forums for this name.
  2. The exception occurred at an address in C:\WINDOWS\System32\ig9icd64.dll. There are several search results in the Internet for this name combined with 'access violation' or 'unhandled exception'.
fth0
Volunteer
 
Posts: 242
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: VBox crash -- HDMI related?

Postby abcdefgh » 25. Aug 2019, 20:06

Thank you for your excellent assistance. I endeavor to learn how to interpret logs as a form of self-help. I assume you have access to VBox developers. If I may comment...

1. As the time base, use the same time as is used by Windows Event Viewer. Also, make the event a Windows event and the log a Windows event log so that it & any related Windows events can be correlated.

2. Call the fault an "error" rather than an "exception". You & I know what an exception is & what it indicates, but most users won't.

3. Instead of long-distance, indirect reference:
Code: Select all   Expand viewCollapse view
59:46:30.421971 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 00000000000021bc!!!
... 1085 lines
59:46:30.423936 Thread ID:   00000000000021bc
59:46:30.423940 Thread name: ShCrOpenGL

directly reporting the same thing:
Code: Select all   Expand viewCollapse view
2019-08-22T15:57:02.237166 ERROR: uncaught exception, in C:\WINDOWS\System32\ig9icd64.dll

produces something I can more easily find & copy into a search box.
Last edited by socratis on 25. Aug 2019, 20:26, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
I'm actually markfilipak (which somehow became 'markfilipak2', then 'abcdefgh'). I've been here since 15 Jul 2012 but lost my name during the great shift to SSO (single sign-on) during 2017, and have not been able to recover it.
abcdefgh
 
Posts: 52
Joined: 22. Jul 2018, 03:29
Primary OS: MS Windows other
VBox Version: PUEL
Guest OSses: Linux Mint 18.3, Cinnamon


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Google [Bot] and 71 guests