Win10 crashes when connecting Xbox Wireless dongle on SteamLink

Submitted by Agh42 on #1

Hi,

 

this used to work fine for years now, but now whenever I plug in Xbox wireless dongle into the Steamlink, there is a hard crash on my Windows10 machine connected via Virtualhere.

I tried reinstalling the driver, the Virtualhere (via Steam) server etc. nothing helped.

Some entries I'm seing in the Windows event log around the time of the crash are:

 

  • The SecDrv service failed to start due to the following error: 
  • This driver has been blocked from loading
  • The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffff80000003, 0xfffff8050d6427ff, 0x0000000000000000, 0xfffff8050d6682a0). A dump was saved in: C:\WINDOWS\Minidumps\123122-15015-01.dmp. Report Id: 5af0dd09-fe4e-43b4-9d2b-a1fbf12d6671.
  • The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
  • The driver \Driver\WudfRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&0.

I would be immensely grateful for any advice so we can continue playing PC games in the living room together again...

 

 

Submitted by Agh42 on Sat, 2022/12/31 - 22:36

#2

I have some more info from analyzing the dumpfile with windbg:

The hard crash seems to apear in vhui64.exe:

 

  • CUSTOMER_CRASH_COUNT: 1

  • PROCESS_NAME: vhui64.exe

  • STACK_TEXT:

  • ffffa381`f593f158 fffff802`1eef83fe : 00000000`0000001e ffffffff`80000003 fffff805`0d6427ff 00000000`00000000 : nt!KeBugCheckEx

  • ffffa381`f593f160 fffff802`1ee03992 : fffff802`1eef83dc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22

  • ffffa381`f593f1a0 fffff802`1ec77ad7 : ffffa381`f593f710 00000000`00000000 ffffa285`3e676fb0 fffff802`1ee01795 : nt!RtlpExecuteHandlerForException+0x12

  • ffffa381`f593f1d0 fffff802`1ec766d6 : ffffa285`3e676388 ffffa381`f593fe20 ffffa285`3e676388 ffff9204`72a4aa08 : nt!RtlDispatchException+0x297 ffffa381`f593f8f0

  • fffff802`1edfa3b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186

  • ffffa381`f593ffb0 fffff802`1edfa380 : fffff802`1ee0d465 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12

  • ffffa285`3e676248 fffff802`1ee0d465 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue

  • ffffa285`3e676250 fffff802`1ee064d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125

  • ffffa285`3e676430 fffff805`0d642800 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBreakpointTrap+0x310

  • ffffa285`3e6765c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00001000 : mt7612US+0x32800

  • SYMBOL_NAME: mt7612US+327ff

  • MODULE_NAME: mt7612US

  • IMAGE_NAME: mt7612US.sys

  • STACK_COMMAND: .cxr; .ecxr ; kb

  • BUCKET_ID_FUNC_OFFSET: 327ff

  • FAILURE_BUCKET_ID: 0x1E_80000003_mt7612US!unknown_function

  • OSPLATFORM_TYPE: x64

  • OSNAME: Windows 10

  • FAILURE_ID_HASH: {fe997aa6-f285-1270-4766-4777d99498f1}

 

 

Any idea what I could try here?

Submitted by Michael on Sat, 2022/12/31 - 22:55

#3

Its crashing inside the xbox driver. The mt7612US is the mediatek driver for the wireless chip inside the dongle.

Unfortunately since its not inside the virtualhere driver its not fixable by me.  Microsoft regularly changes this driver for some reason. And i have seen it crash and then be fixed in the past. At this point you will need to either make sure you have the very latest xbox driver and firmware or rollback the xbox driver to something previous, there is a button to do that in Windows device manager.

Submitted by Agh42 on Tue, 2023/01/03 - 03:55

#5

Ok, I checked and there seems to be no newer driver available - and I can't roll back either. The button to "Roll Back Driver" is greyed out. Apparently there is no previous version ony my system. I must have been on the following version of this driver for a long time now without changes:

  • device: xbox wireless adapter for windows

  • driver date 12/8/2015

  • driver version 21.50.45.656

  • driver details:

  • mt7612US.sys

  •   mediatek inc

  •     file version 1.0.24.0 (th2_xbox_rel_1602.151208-2018)

  •     copyright 2013 mediatek inc

  • xboxgip.sys

  •     microsoft corporation

  •     file version 10.0.19041.1566 Winbuild 160101.0800

 

So it's weird that this stopped working. I noticed there was an update of Virtualhere recently. Right now I'm on the (Steam) version AppId: 440520/BuildID 4947822 installed on Dec 4 2022.

Is this the up-to-date version of VirtualHere? Could I try up- or downgrading VirtualHere somehow?

(Steam doesn't seem to have a rollback-option...)

 

Thanks in advance for any assistance you might be able to give!

Submitted by Michael on Tue, 2023/01/03 - 05:39

#6

If you are using virtualhere from steam, i havent updated that virtualhere version for about a year. Its an older version than the version on this website.

You could try the new version on this website, just download vhui64.exe from this website. And overwrite the vhui64.exe version from steam which is should be in a subdirectory of C:\Program Files (x86)\Steam\steamapps\common\appid or something similar

Copy the steam version to another name e.g vhui64.bak beforehand to save the original.

See if that makes a difference

Submitted by Agh42 on Mon, 2023/02/13 - 18:03

#7

I did as you said and replaced the Steam version with the one from the website. I can happily report that my Xbox controllers are now working again flawlessly on my Steam Link! Thank you for this great piece of software!