PC Graphics

[orvis25]

Hello, 
I upgraded from my vega 56 to a Rx 5700xt today. 

I had issues on the Vega 56 card in terms of not being able to run the WMR software with Super resolution enabled (caused display driver crashing, already reported it 3 months ago, AMD has still released no fix for this issue), but now i am having different issues. 

I know the Error 1-4 is a common thing with the WMR setups, but even on vega 56 I was able to get around it by un-plugging the HDMI and USB a few times, and EVENTUALLY the Windows Mixed Reality software would detect the headset and run normally. 

With my RX 5700xt though, I can not get the graphics card to pick up the headsets display cable. I know the HDMI port works since it displays out to normal monitors/Tv's, so its not that. 

I tried all the ususal reccomended things:
- Downgrading drivers

- Uninsalling drivers and reinstalling (Using DDU for complete wipe)
- Uninstalling and re-installign all the VR software 

- force uninstalling the devices in the device manager and re-installing
- trying different USB ports 

- trying to to use a DP->HDMI adapter (granted, mine was 4k*30, not 4k*60 rated, so that may be what they one failed)

I finally caved today and re-insalled my entire OS from scratch, and got everythign installed and updated. 

I still can not get the graphics card to detect the headset. 

I know the headset works, because i used it just yesterday on my vega 56 card. 

The front of the RX 5700 XT says "Radeon VR Ready Premium", yet apparently the support for VR is WORSE than my non-premium VR GPU from 4 years ago. 

What files/data do you AMD engineers/support personnel need other than DxDiag to check this out?

I am highly considering returning the 5700xt as defective since I only have 30 days to return and going back to my vega 56 given how poorly the drivers are being supported, despite me submitting data and trying to do my part, AMD seems to not be doing theirs in terms of their VR driver division (see my prior statement about reporting 3 months ago supersaturation issued with my vega 56 and using VR applications).

I am not going to keep a piece of hardware that cant utilize my VR equipment. Sorry if this statements comes across as harsh, but it is EXTREMELY frustrating to spend over $300 on 4 year newer hardware, and have it have the same and WORSE issues than the piece of prior hardware I was using. 

My rig:

- Windows 10 x64 (Build 18363.720 (1909/November 2019 Update)

- Ryzen 3600

- Asus ROG B350-f Gaming (Bios v5220)

- MSI RX 5700xt Mech OC (Software Driver v.20.4.2)

- 16GB Gddr4 ram (3600 Mhz)

- LG (Gsm5b35, DP->DP 75hz Freesync, 1080p Superresolution to 1440p)

- Asus (ACI24c4, DP->HDMI, 60hz, 1080p Superresolution to 1440p)

- Sanyo TV (San0000, 60hz, DP->HDMI, 1080p)

- Acer AH101 WMR Headset ( HDMI, 2880x1440 @ 90 Hz)

[orvis25]

Bump. 

Still seeking support. 

[Earnhardt]

You do realize this is a peer to peer forum right? Bumping a post is just poor manners,If someone has an answer,they will reply.

[orvis25]

I am aware its a non-direct AMD monitored support forum. 

I have never heard of bumping being considered rude, that's a first. I bump because my question has gone unanswered and is already not even on the primary page any longer.

Obviously i would not bump it multiple times to keep it at the top if i got no reply, but i feel 1-2 times is perfectly reasonable. 

[elstaci]

When you had the Acer VR Headset connected, Did it show up in Device Manager?

Were there any errors in Device Manager when hooked up?

Was the Acer VR Headset connected when you ran DXDIAG.exe because I don't see it listed anywhere.

Try connecting the Acer VR headset again. After connecting it, go to Device Manager and Windows Event Viewer and see if you see any errors being generated.

What happens when you connect the Acer VR Headset and you start Windows 10 Mixed Reality feature? Any errors?

Have you tried to use Acer WebVR (experimental) Chrome software to see if it recognizes your Acer Headset?

Also run Windows Mixed Reality Tool with the Acer VR headset connected and see what it shows. Any errors?

Try connecting the Acer VR Headset to different USB ports in the rear of the computer. It is possible it isn't getting power to the headset thus not being recognized by Windows.

In an elevated Command Prompt or Powershell - SFC /scannow and make sure it comes back without any errors. (just checking your Windows 10 OS for corruption or missing files).

Your Motherboard has a brand new BIOS update: ROG STRIX B350-F GAMING Driver & Tools | Motherboards | ASUS USA 

Plus recent CHIPSET Drivers:

Try connecting the Acer VR Headset using DisplayPort on the GPU card by using a DP>HDMI HD active adapter to see if it works.

[orvis25]

Q) When you had the Acer VR Headset connected, Did it show up in Device Manager?

Yes (see attached photo)

Q) Were there any errors in Device Manager when hooked up?

No

Q) Was the Acer VR Headset connected when you ran DXDIAG.exe because I don't see it listed anywhere.

No, i am attaching a new one with the Dxdiag run with the headset plugged in and recognized (but not working)

Q) Try connecting the Acer VR headset again. After connecting it, go to Device Manager and Windows Event Viewer and see if you see any errors being generated.

No errors

Q) What happens when you connect the Acer VR Headset and you start Windows 10 Mixed Reality feature? Any errors?

No errors, launches fine. Software (MRP) Does gives no connection Error 1-4 for the HDMI cable if i plug it into the HDMI port, but if i use the DP->HDMI adapter it is detected but displays a black screen (Headset LED's do not turn on)

Q) Also run Windows Mixed Reality Tool with the Acer VR headset connected and see what it shows. Any errors?

Same as prior 

Q) Have you tried to use Acer WebVR (experimental) Chrome software to see if it recognizes your Acer Headset?

No, do not plan to, i know the headset works, and its detected by the software (with the DP adapter) but it displays no image. 

Q) Try connecting the Acer VR Headset to different USB ports in the rear of the computer. It is possible it isn't getting power to the headset thus not being recognized by Windows.

Tried that, including my USB 3.1 port, and a independently powered 3.0 HUB, no dice. 

Q) In an elevated Command Prompt or Powershell - SFC /scannow and make sure it comes back without any errors. (just checking your Windows 10 OS for corruption or missing files).

no errors (Just looked) + this is a fresh install of windows. 

_____________________________

- I did update the bios firmware (thanks for that, released last week when i started messing with this issue, so i have not checked since)

No dice on having that fix the issue

- I bought a DP->HDMI adapter, see my OP. It allows the headset to be "detected" unlike directly hooking it up with HDMI, but it displays no image (black screen)  

- My PC very easily meets the high end requirements for the vr headset, 

[elstaci]

is the DP-HDMI "ACTIVE" and for High Definition? That might make a difference in getting an image.

I suggest you open a Acer Support ticket and ask them what their opinion is.

Also open an AMD Service Request (Official AMD SUPPORT) and let them know that is going on from here: https://www.amd.com/en/support/contact-email-form 

NOTE: The DXDIAG does show several times your Acer VR Headset (I would upload this DXDIAG.txt when you contact AMD Support):

Holographic Devices
------------------
      Device Type: Spatial Graph
      Device Name: HoloLens Sensors
     Manufacturer: Acer
   Driver Version: 10.0.18362.1162
      Driver Date: 6/20/2006 7:00:00 PM
  Driver Provider: Microsoft
    Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
   Device Problem: No Problem
   Driver Problem: Not Available
      Device Path: \\?\usb#vid_045e&pid_0659&mi_04#8&56de018&0&0004#{43f57110-467b-47d9-9c4b-264af0b54cfa}

      Device Type: Holographic Display
      Device Name: HoloLens Sensors
     Manufacturer: Acer
   Driver Version: 10.0.18362.1162
      Driver Date: 6/20/2006 7:00:00 PM
  Driver Provider: Microsoft
    Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
   Device Problem: No Problem
   Driver Problem: Not Available
      Device Path: \\?\usb#vid_045e&pid_0659&mi_04#8&56de018&0&0004#{deac60ab-66e2-42a4-ad9b-557ee33ae2d5}\holographicdisplay

      Device Type: Head Mounted Display
      Device Name: Not Available
     Manufacturer: Not Available
Parent Device Key: Enum\PCI\VEN_1002&DEV_731F&SUBSYS_38101462&REV_C1
     Power Status: On
   Preferred Mode: 2880 x 1440(p) (90.000Hz)
 Pref Desktop Mic: No
Pref Desktop Spkr: No
   Driver Version: Not Available
      Driver Date: Not Available
  Driver Provider: Not Available
    Device Status: Not Available
   Device Problem: Not Available
   Driver Problem: Not Available
      Device Path: Not Available

Video Capture Devices
Number of Devices: 2
---------------------
           FriendlyName: Acer AH101
               Category: Camera,Sensor
           SymbolicLink: \\?\usb#vid_045e&pid_0659&mi_04#8&56de018&0&0004#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\passthroughcamerasource
               Location: n/a
               Rotation: n/a
           Manufacturer: Acer
             HardwareID: USB\VID_045E&PID_0659&REV_0000&MI_04,USB\VID_045E&PID_0659&MI_04
             DriverDesc: HoloLens Sensors
         DriverProvider: Microsoft
          DriverVersion: 10.0.18362.1162
      DriverDateEnglish: 6/21/2006 00:00:00
    DriverDateLocalized: 6/21/2006 12:00:00 AM
                Service: WUDFRd
                  Class: Holographic
          DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
            ContainerId: {6DB6662B-0B75-5BE1-8CE8-A92A47F7755D}
            ProblemCode: No Problem
  BusReportedDeviceDesc: HoloLens Sensors
                 Parent: USB\VID_045E&PID_0659\fdfb4207-a6ac-48d2-a325-0479333b02a3
      DriverProblemDesc: n/a
           UpperFilters: n/a
           LowerFilters: vhf
                  Stack: \FileSystem\avgSnx,\Driver\SpatialGraphFilter,\Driver\WudfRd,\Driver\vhf,\Driver\usbccgp
      ContainerCategory: n/a
          SensorGroupID: n/a
                   MFT0: n/a
                   DMFT: n/a
    CustomCaptureSource: {4505a358-cac8-4ce9-9e31-9219318a5fb5}
  DependentStillCapture: n/a
     EnablePlatformDMFT: n/a
              DMFTChain: n/a
 EnableDshowRedirection: n/a
     FrameServerEnabled: n/a
        AnalogProviders: n/a
             ProfileIDs: n/a

           FriendlyName: Acer AH101
               Category: Sensor
           SymbolicLink: \\?\usb#vid_045e&pid_0659&mi_04#8&56de018&0&0004#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\passthroughcamerasource
               Location: n/a
               Rotation: n/a
           Manufacturer: Acer
             HardwareID: USB\VID_045E&PID_0659&REV_0000&MI_04,USB\VID_045E&PID_0659&MI_04
             DriverDesc: HoloLens Sensors
         DriverProvider: Microsoft
          DriverVersion: 10.0.18362.1162
      DriverDateEnglish: 6/21/2006 00:00:00
    DriverDateLocalized: 6/21/2006 12:00:00 AM
                Service: WUDFRd
                  Class: Holographic
          DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
            ContainerId: {6DB6662B-0B75-5BE1-8CE8-A92A47F7755D}
            ProblemCode: No Problem
  BusReportedDeviceDesc: HoloLens Sensors
                 Parent: USB\VID_045E&PID_0659\fdfb4207-a6ac-48d2-a325-0479333b02a3
      DriverProblemDesc: n/a
           UpperFilters: n/a
           LowerFilters: vhf
                  Stack: \FileSystem\avgSnx,\Driver\SpatialGraphFilter,\Driver\WudfRd,\Driver\vhf,\Driver\usbccgp
      ContainerCategory: n/a
          SensorGroupID: n/a
                   MFT0: n/a
                   DMFT: n/a
    CustomCaptureSource: {4505a358-cac8-4ce9-9e31-9219318a5fb5}
  DependentStillCapture: n/a
     EnablePlatformDMFT: n/a
              DMFTChain: n/a
 EnableDshowRedirection: n/a
     FrameServerEnabled: n/a
        AnalogProviders: n/a
             ProfileIDs: n/a

Device Name: HoloLens Sensors
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0659
        FF Driver: n/a

Video Capture Sources:
Acer AH101,0x00000000,0,0,,

Card name: Virtual Display Adapter
        Manufacturer: Microsoft
           Chip type: Unknown
            DAC type: Unknown
         Device Type: Display-Only Device
          Device Key: Enum\SWD\VIRTUALDISPLAYADAPTER
       Device Status: 4180600A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_REMOVABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER|DN_NO_SHOW_IN_DM]
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 8160 MB
    Dedicated Memory: 0 MB
       Shared Memory: 8160 MB
        Current Mode: 1920 x 1080 (32 bit) (90Hz)
         HDR Support: Not Supported
    Display Topology: Extend
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.000000,0.000000), Green(0.000000,0.000000), Blue(0.000000,0.000000), White Point(0.000000,0.000000)
   Display Luminance: Min Luminance = 0.000000, Max Luminance = 0.000000, MaxFullFrameLuminance = 0.000000
        Monitor Name: Generic Non-PnP Monitor
       Monitor Model: unknown
          Monitor Id:
         Native Mode: unknown
         Output Type: HDMI
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: c:\windows\system32\drivers\indirectkmd.sys
 Driver File Version: 10.00.18362.0001 (English)
      Driver Version: 10.0.18362.1
         DDI Version: 12
      Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 1.3
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported
      Detachable GPU: No
 Hybrid Graphics GPU: Not Supported
      Power P-states: Not Supported
      Virtualization: Not Supported
          Block List: No Blocks
  Catalog Attributes: N/A
   Driver Attributes: Final Retail
    Driver Date/Size: 6/20/2006 7:00:00 PM, 46592 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B71EE2-305F-11CF-5A1E-A5227AC2D735}
           Vendor ID: 0x1414
           Device ID: 0x008C
           SubSys ID: 0x00000000
         Revision ID: 0x0000
  Driver Strong Name: virtualdisplayadapter.inf:c14ce8840c48fa1f:VirtualDisplayAdapter_Install:10.0.18362.1:VirtualDisplayAdapter_DisplayDevice
      Rank Of Driver: 00FF2000
         Video Accel: 

D3D9 Overlay: Not Supported
             DXVA-HD: Not Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 0
            MPO Caps: Not Supported
         MPO Stretch: Not Supported
     MPO Media Hints: Not Supported
         MPO Formats: Not Supported
    PanelFitter Caps: Not Supported
 PanelFitter Stretch: Not Supported

Card name: Virtual Display Adapter
        Manufacturer: Microsoft
           Chip type: Unknown
            DAC type: Unknown
         Device Type: Display-Only Device
          Device Key: Enum\SWD\VIRTUALDISPLAYADAPTER
       Device Status: 4180600A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_REMOVABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER|DN_NO_SHOW_IN_DM]
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 16311 MB
    Dedicated Memory: 8151 MB
       Shared Memory: 8160 MB
        Current Mode: 1920 x 1080 (32 bit) (90Hz)
         HDR Support: Not Supported
    Display Topology: Extend
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.000000,0.000000), Green(0.000000,0.000000), Blue(0.000000,0.000000), White Point(0.000000,0.000000)
   Display Luminance: Min Luminance = 0.000000, Max Luminance = 0.000000, MaxFullFrameLuminance = 0.000000
        Monitor Name: Generic Non-PnP Monitor
       Monitor Model: unknown
          Monitor Id:
         Native Mode: unknown
         Output Type: HDMI
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: c:\windows\system32\drivers\indirectkmd.sys
 Driver File Version: 10.00.18362.0001 (English)
      Driver Version: 10.0.18362.1
         DDI Version: 12
      Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 1.3
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported
      Detachable GPU: No
 Hybrid Graphics GPU: Not Supported
      Power P-states: Not Supported
      Virtualization: Not Supported
          Block List: No Blocks
  Catalog Attributes: N/A
   Driver Attributes: Final Retail
    Driver Date/Size: 6/20/2006 7:00:00 PM, 46592 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B71EE2-305F-11CF-5A1E-A5227AC2D735}
           Vendor ID: 0x1414
           Device ID: 0x008C
           SubSys ID: 0x00000000
         Revision ID: 0x0000
  Driver Strong Name: virtualdisplayadapter.inf:c14ce8840c48fa1f:VirtualDisplayAdapter_Install:10.0.18362.1:VirtualDisplayAdapter_DisplayDevice
      Rank Of Driver: 00FF2000
         Video Accel:

D3D9 Overlay: Not Supported
             DXVA-HD: Not Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 1
            MPO Caps: Not Supported
         MPO Stretch: Not Supported
     MPO Media Hints: Not Supported
         MPO Formats: Not Supported
    PanelFitter Caps: Not Supported
 PanelFitter Stretch: Not Supported

Card name: Virtual Display Adapter
        Manufacturer: Microsoft
           Chip type: Unknown
            DAC type: Unknown
         Device Type: Display-Only Device
          Device Key: Enum\SWD\VIRTUALDISPLAYADAPTER
       Device Status: 4180600A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_REMOVABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER|DN_NO_SHOW_IN_DM]
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 16311 MB
    Dedicated Memory: 8151 MB
       Shared Memory: 8160 MB
        Current Mode: 1920 x 1080 (32 bit) (90Hz)
         HDR Support: Not Supported
    Display Topology: Extend
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.000000,0.000000), Green(0.000000,0.000000), Blue(0.000000,0.000000), White Point(0.000000,0.000000)
   Display Luminance: Min Luminance = 0.000000, Max Luminance = 0.000000, MaxFullFrameLuminance = 0.000000
        Monitor Name: Generic Non-PnP Monitor
       Monitor Model: unknown
          Monitor Id:
         Native Mode: unknown
         Output Type: HDMI
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: c:\windows\system32\drivers\indirectkmd.sys
 Driver File Version: 10.00.18362.0001 (English)
      Driver Version: 10.0.18362.1
         DDI Version: 12
      Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 1.3
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported
      Detachable GPU: No
 Hybrid Graphics GPU: Not Supported
      Power P-states: Not Supported
      Virtualization: Not Supported
          Block List: No Blocks
  Catalog Attributes: N/A
   Driver Attributes: Final Retail
    Driver Date/Size: 6/20/2006 7:00:00 PM, 46592 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B71EE2-305F-11CF-5A1E-A5227AC2D735}
           Vendor ID: 0x1414
           Device ID: 0x008C
           SubSys ID: 0x00000000
         Revision ID: 0x0000
  Driver Strong Name: virtualdisplayadapter.inf:c14ce8840c48fa1f:VirtualDisplayAdapter_Install:10.0.18362.1:VirtualDisplayAdapter_DisplayDevice
      Rank Of Driver: 00FF2000
         Video Accel:

D3D9 Overlay: Not Supported
             DXVA-HD: Not Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 1
            MPO Caps: Not Supported
         MPO Stretch: Not Supported
     MPO Media Hints: Not Supported
         MPO Formats: Not Supported
    PanelFitter Caps: Not Supported
 PanelFitter Stretch: Not Supported

------------------
Holographic Devices
------------------
      Device Type: Spatial Graph
      Device Name: HoloLens Sensors
     Manufacturer: Acer
   Driver Version: 10.0.18362.1162
      Driver Date: 6/20/2006 7:00:00 PM
  Driver Provider: Microsoft
    Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
   Device Problem: No Problem
   Driver Problem: Not Available
      Device Path: \\?\usb#vid_045e&pid_0659&mi_04#8&56de018&0&0004#{43f57110-467b-47d9-9c4b-264af0b54cfa}

      Device Type: Holographic Display
      Device Name: HoloLens Sensors
     Manufacturer: Acer
   Driver Version: 10.0.18362.1162
      Driver Date: 6/20/2006 7:00:00 PM
  Driver Provider: Microsoft
    Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
   Device Problem: No Problem
   Driver Problem: Not Available
      Device Path: \\?\usb#vid_045e&pid_0659&mi_04#8&56de018&0&0004#{deac60ab-66e2-42a4-ad9b-557ee33ae2d5}\holographicdisplay

      Device Type: Head Mounted Display
      Device Name: Not Available
     Manufacturer: Not Available
Parent Device Key: Enum\PCI\VEN_1002&DEV_731F&SUBSYS_38101462&REV_C1
     Power Status: On
   Preferred Mode: 2880 x 1440(p) (90.000Hz)
 Pref Desktop Mic: No
Pref Desktop Spkr: No
   Driver Version: Not Available
      Driver Date: Not Available
  Driver Provider: Not Available
    Device Status: Not Available
   Device Problem: Not Available
   Driver Problem: Not Available
      Device Path: Not Available

[orvis25]

OK, 
I managed to get it working with a handful of things done, so I am not particularly sure which one ultimately bypassed the issue, but here it is. 

1) go into device manager, and on every usb device plunged in, go to the USB controller section, right click on every device there, go to power management, and un-check the "allow computer to turn this device off to save power" box

2) Buy a Plugable brand Display port -> HDMI 2.0 Active adapter to get the GPU to recognize the headset

(since Directly plugging the headset HDMI into the gpu's HDMI results in it it never being recognized)

3) Disable super resolution on your monitors

(Causes display driver crashes on WMR software launch)

4) Disable Freesync on all displays

(Also causes crashing) 

5) Set all monitors to 60 hz, even if they can go higher

6) go into the Windows mixed reality portal setting, change the headsets HZ from automatic/90hz to 60 hz

Those are all the major steps i had to do to get the headset to actually "boot up" and display an image, instead of a black screen. #6 was actually what finally did it, but step 1-5 where things i had already done prior, so it may also be necessary to do all those too, which i suggest since #3 & 4 are repeatable and priory reported bugs still not fixed since October 2019 (looking back at prior posts on forums, including the bug report i made over a month ago on #3, which is still not even listed as a known bug)

Unfortunately not i can only run the headset in 60hz mode (which increases eye strain and chance of motion sickness due to a lower refresh rate) but at least i got the thing working, instead of it being a desk paper wight. 

TLDR:

- AMD fix your drivers for # 3, 4 (and maybe 5/6)

- Windows Fix your firmware/software for # 1, 2, 5, and 6 

PS: Others please go report this via a  AMD Service Request (Official AMD SUPPORT) and report this so they haev more pressure on them to actually fix the issue: https://www.amd.com/en/support/contact-email-form

PSS: if it helps, give a thumbs up and a helpful