Interfering software is preventing the Rift from activating

[tozz3r]

I'm trying to run the Demo Scene in the utility with the Rift Display Mode set to Direct HMD Access.
Running Windows 8.1.
Rift Firmware 2.12
Rift Runtime 4.3

Error:
There is a problem with your Rift configuration.
Interfering software is preventing the Rift from activating. Loaded UMD is reported as 'nvwgf2um.dll'.

Anyone else?

[sixtailer]

no matter what I've tried, I can't ever get the oculus screen to show the game. I can get my main monitor to render two seperate screens side by side for days but NOTHING I do gets that over to the oculus. Not direct. Not extended. Windows 7.1, sdk 0.4.2, ED beta 3.

[tozz3r]

"cybereality" wrote:
Can you guys try disabling SLI, Surround, and unplugging any extra monitors (one monitor should be OK)?

Especially with SLI, the video ports you use on the GPUs will make a difference.

I did two things that made it work.
1. I moved the rift hdmi to card number 1. This got rid of the dll error message, but my rift would still not turn on, stayed yellow.
2. I unplugged the two other monitors, so I now have rift and one monitor in card number 1.

I did not disable SLI.

Now it works and the rift turns on in direct mode.

Edit:
I went ahead and plugged all monitors back in and now it works with the 3 monitors. The only difference I see is that the Rift is now recognized in the NVidia control panel, which it wasn't before.
RiftSetup.PNG

[keii]

Hi, I just installed the 0.4.3 SDK and I'm facing the same problem:

"There is a problem with your Rift configuration. Interfering software is preventing the Rift from activating. Loaded UMD is reported as aticfx64.dll"

Notebook: Sony VAIO™ E Series SVE14A15FGW
Graphics: AMD Radeon™ HD 7670M / Intel® HD Graphics 3000
Operating System: Windows 8.1 pro
Processor: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz 2.50GHz
Memory (RAM): 4GB DDR3 RAM
System type: 64-bit operating system, x64 based processor

The Oculus Rift is detected and the demo (from Oculus Configuration Utility) works pretty well, but I can't open any other demo, neither in extended mode nor in direct mode...
The 0.4.2 SDK works well here!

[gordonklarson]

I'm having the same issue. For me dlumd11.dll is reported as what's causing the conflict. From what I can tell that dll is used for a USB 3.0 monitor I have connected. If I disconnect the monitor and remove the associated software for it, everything runs fine. This conflict wasn't occurring with earlier versions of the SDK.

[cybereality]

@gordonklarson: I'm not surprised a USB display was causing conflict. Can I ask which brand/model you have?

[gordonklarson]

It's an Asus model MB168B+

[Exprience111]

I have the same issue!

i bought a new pc, its a beast, i7 4790k, 2x msi r9 270x 4g, 32 gb ram.asus h97M plus motherboard.

now i get that same error, AMD catalist 14.4


all the ports on the second card dont work aswell, crossfire is enabled...


when i run the demo scene the head tracking works and i see it on the mian display, but the oculus is black and that error
Please help.

edit : i fixed it , but weird.

disable crossfire, switch from Direct HMD to extend desktop. Now all the ports on card 2 work. The oculus is in de HDMI of card 2.

will disabling crossfire cost me performance?

[ctrlaltdavid]

I've encountered the problem witih dlumd11.dll interfering and preventing my DK2 from activating. My USB monitor is a Lenovo ThinkVision using DisplayLink. Disconecting the USB monitory and uninstalling DisplayLink made the problem go away.

[mdvx]

I uninstalled a DisplayLink USB driver, and that fixed it.

[sgallouet]

i got the same issue except
- when i do tasklist /m aticfx32.dll or 64.dll it said no task are running with it (after i closed explorer).
- that error only happen in direct mode.
- Rift 4.4 with windows8 on a notebook with multi gpu intel/ati.