Win build 976 onwards crashes on Windows 7 when no mic attached


#1

I had to revert to win 973, the last I had used to get it to run without crashing on Windows.

[Note, it was later established that win 975 is last working version. Fault introduced at build 976]


#2

I had the same problem when I tried win 983. Hence I uninstalled the Interface completely, and deleted the AppData folders to get things clean, and installed 983 fresh on Windows 7 SP1. Same problem it crashes. It works on a windows 8.1 system. Any thoughts on how I can unstick this and get working again?

I do have a Rift DK2 attached to the windows 7 system, but I paused the OVR service and existed the control panel just on case that might be the issue. But it still crashed.

I was again able to revert to the win 973 installer and that works fine still.

Problem signature:
Problem Event Name: APPCRASH
Application Name: interface.exe
Application Version: 0.0.0.0
Application Timestamp: 53ec1b0c
Fault Module Name: Qt5Multimedia.dll
Fault Module Version: 5.2.0.0
Fault Module Timestamp: 52a4c768
Exception Code: c0000005
Exception Offset: 0000c7d0
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


#3

@Chris and @b - Can you let me know the Win build number where the DK2 Oculus 0.4.1 SDK was first used? If it was between 973 and 979 that might be a root cause of my crashes with recent builds. It is only happening on a Windows 7 system on which the Rift DK2 and 0.4.1 SDK/Runtime is installed and not on another near identical Windows 7 system.

P.S. have you noticed (on Windows web browsers anyway) that @b with its single character name for the forums for “birada” brings up the choice of user names fine, but when in the forum post is not hyperlinked to him like username longer than 1 character are. Same for @g for “Grayson”.


#4

When using the latest Win 991, I still crash on a Windows 7 system which has Oculus Rift DK2 and the Oculus Runtime/SDK 0.4.1 installed.

I note that the crash is immediately after the console message “initializing display”.

I tried turning off the OVR service and existing the Oculus Config utility but still get the crash.

If I revert to Win 973, it works fine again.


#5

I pinned this down by going through the versions and found that Win 975 works fine, but every build from Win 976 onwards (tested to 991) crashes. So a change made at win build 976 is causing the app crash.


#6

It looks like 976 introduced audio system changes by @chansensturm not necessarily anything directly to do with the Oculus Rift… but it works on an almost identical Win 7 system without the rift installed. Something in this change set must be causing the crash?

https://jenkins.highfidelity.io/job/hifi-interface-win/976/changes


#7

Forwarding this to @leo to see if he has any insight - it’s possible the issue is that your client is trying to open one of the DK2 devices for audio purposes.

Do you have the same issue if you disconnect the DK2?


#8

This may not relate to the same problem @Be_Austin is reporting… It has been a while since I tried the Interface on my Microsoft Surface Pro (Model 1) so I updated to Win build 994 this evening as a test. It runs for a while as everything loads, but I am getting App crashes of two kinds… the BEX one being the most common… I will try to pin down which release I have to go back to to get it working when I get chance.

Win 994

Problem signature:
Problem Event Name: BEX
Application Name: interface.exe
Application Version: 0.0.0.0
Application Timestamp: 53f2576c
Fault Module Name: StackHash_5861
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_02_FROM_ntdll+0x0003D2EC
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: d1d9
Additional Information 4: d1d94a13d3609d6b740644c12508f581

Problem signature:
Problem Event Name: APPCRASH
Application Name: interface.exe
Application Version: 0.0.0.0
Application Timestamp: 53f2576c
Fault Module Name: Qt5Core.dll
Fault Module Version: 5.2.0.0
Fault Module Timestamp: 52a4bfe3
Exception Code: c0000005
Exception Offset: 0001c72a
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: d1d9
Additional Information 4: d1d94a13d3609d6b740644c12508f581


#9

Will check it out and report tomorrow @b and @leo

I can say though that the DK2 was plugged in but was turned off at its button, so it was not in orange standby or seen by the Rift Config utility.


#10

@b and @leo, I have now done some further testing… on Windows 7 SP1…

a) I unplugged the DK2 from the DVI port and unplugged the IR positional camera. I paused the OVRService and exited from the Oculus Config Utility. No difference, still crashed.

b) I uninstalled the Oculus 0.4.1 runtime with its display and positional camera drovers. Rebooted, and tried again. It still crashed.

So this time I tried to grab what was on screen in the Interface console at the time it crashes. I cannot just cut and paste this as there is the usual crash popup there. But I attach an image capture. You can see it is handling audio matters before the crash, and just before it crashes, the last line says

“Unable to set up audio input because of a problem with the input format” and then it crashes.

But before I have seen it get to “Initialized display” message just before the crash, hence my reason for suspecting the DK2 display, so I tried launching the Interface a few more times and indeed (on 2 goes out of 6) it does get a bit further on some points, e.g. to the point where it says “Initializing display” and then crashes. See this screen grab…

If I return to Win build 975, it all works fine again. Installing 976 and it fails.

Problem signature with any version from 976 to latest (1005 today) is

Problem signature:
Problem Event Name: APPCRASH
Application Name: interface.exe
Application Version: 0.0.0.0
Application Timestamp: 53e919a4
Fault Module Name: Qt5Multimedia.dll
Fault Module Version: 5.2.0.0
Fault Module Timestamp: 52a4c768
Exception Code: c0000005
Exception Offset: 0000c7d0
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


#11

I looked in more detail at the Interface console trace for the working win build 975 the parts around the place it crashes in 976 and se that just after the log lines where it crashes, the Interface is doing things with OVR :: DeviceManager… so it could still be that some changes made to the Windows 7 system with Oculus Rift Runtime 0.4.1 installed (and even after uninstalling and rebooting) is the root of the problem. But it must be a change made between 975 and 976, so that is the place to look. I do see an “Audio Error: device not found” in this trace for 975 which still works…

Creating buckyballs…
NodeList getInstance called before call to createInstance. Returning NULL pointer.
QObject::connect: invalid null parameter
[Info] Cara Face Tracker Socket: QAbstractSocket::BoundState
[Info] DDE Face Tracker Socket: QAbstractSocket::BoundState
[VERSION] Build sequence:
Node’s local address is 129.215.219.52
[2014-08-20T10:11:55] First call to Menu::getInstance() - initing menu.
[2014-08-20T10:11:56] QFileSystemWatcher::addPath: path is empty
[2014-08-20T10:11:56] NodeList socket is listening on 61082
[2014-08-20T10:11:56] Changed socket send buffer size from 8192 to 1048576 bytes

[2014-08-20T10:11:56] URL for node authentication has been changed to https://data.highfidelity.io

[2014-08-20T10:11:56] Re-setting authentication flow.
Audio Error: device not found
[2014-08-20T10:11:56] Found a data-server access token for https://data.highfidelity.io

[2014-08-20T10:11:56] Logging activity “launch”
[2014-08-20T10:11:56] DEBUG [ “NONE” ] [ “” ]
[2014-08-20T10:11:56] The default audio input device is “”
[2014-08-20T10:11:56] output device: “Speakers (Realtek High Definiti”
[2014-08-20T10:11:56] “Speakers (Realtek High Definiti” “Speakers (Realtek High Definiti”
[2014-08-20T10:11:56] “Realtek Digital Output (Realtek” “Speakers (Realtek High Definiti”
[2014-08-20T10:11:56] DEBUG [ “Speakers (Realtek High Definiti” ] [ “Speakers (Realtek High Definiti” ]
[2014-08-20T10:11:56] “Speakers (Realtek High Definiti” “Speakers (Realtek High Definiti”
[2014-08-20T10:11:56] “Realtek Digital Output (Realtek” “Speakers (Realtek High Definiti”
[2014-08-20T10:11:56] The default audio output device is “Speakers (Realtek High Definiti”
[2014-08-20T10:11:56] The audio output device “Speakers (Realtek High Definiti” is available.
[2014-08-20T10:11:56] The desired format for audio I/O is QAudioFormat(24000Hz,
16bit, channelCount=2, sampleType=SignedInt, byteOrder=LittleEndian, codec=“audio/pcm”)
[2014-08-20T10:11:56] The desired audio format is not supported by this device
[2014-08-20T10:11:56] The format to be used for audio output is QAudioFormat(48000Hz, 16bit, channelCount=2, sampleType=SignedInt, byteOrder=LittleEndian, codec=“audio/pcm”)
[2014-08-20T10:11:56] Ring Buffer capacity in frames: 3
[2014-08-20T10:11:56] Unable to set up audio input because of a problem with input format.
[2014-08-20T10:11:56] Created Display Window.
[2014-08-20T10:11:56] Status: Using GLEW 1.10.0

[2014-08-20T10:11:56] Initialized Display.
OVR :: DeviceManager - initialized.
OVR :: DeviceManagerThread - running (ThreadId=0x14E0).
OVR :: DeviceManager - shutting down.
OVR :: DeviceManagerThread - exiting (ThreadId=0x14E0).
[2014-08-20T10:11:56] QFileSystemWatcher :: removePath: path is empty
[2014-08-20T10:11:56] QFileSystemWatcher : :addPath: path is empty


#12

As noted in other threads this is a problem on having no microphone connected and the crash is in Qt5Multimedia.dll. This issue doe snot arise at builds up to 975. This started at build 976 and continues to latest version at time of writing (10015).


#13

I now have experimented more with the crashing windows 7 system.

With mic plugged in I can start the Interface up. The Audio Filter Bank menu item was unticked. but I tried it ticked and unticked explicitly several times, restarting between each, and in all cases the system crashes if a mic is not plugged in and works if one is (any one of USB headset, on web came or 3.5mm analogue).

Noting the audio crash fix at win built 1028 I tried that explicitly and that still fails the same way.

I also tested up to the latest version 1036 and ditto., Crash is still there is a mic is not plugged in on this win 7 setup.

I have an essentially identical (bought within 4 weeks) setup at home also on Win 7 and that works even without plugging in a mic. That home system never had the DK2 or Oculus runtime installed… that’s the only possibly relevant difference I can think of.