DK2 no longer detected + other strange issues.

[mrcrisp]

I Powered on the DK2 today to continue working in Unity and now the DK2 no longer gets picked up by the Oculus config tool, just a nice "No device attached" message and greyed out boxes.

Now- It is not a cable issue, as the DK2 is detected by Windows by giving me the "USB connected chime" but is not detected in the config tool.

I uninstalled Oculus software, removed the appropriate USB drivers, rebooted between, cleaned the registry and moved the DK2 to another USB port- still nothing.

Now this is the strange bit: If I change the DK2 to Direct Display Mode- the device is detected in the Oculus config tool and the boxes are no longer greyed out- but Direct Mode still does not work for me, even in the Desk Demo- all I get is a blank screen and the DK2 does not even turn on- no problem for me as I always use extended mode fine.

But if I switch to Extended Mode- The boxes grey out but the Oculus is detected in the config tool but if I minimize the tool it goes back to "No Device Attached".

The DK2 is working as an extended monitor fine- just the config tool is not detecting the DK2 and no head tracking in anything.

Here is the config tool debug log:

{
	"Time":	"2014-09-09_13:58:08",
	"System Specifications":	{
		"Operating System":	"Microsoft Windows 7 Home Premium ",
		"Processor":	"AMD FX(tm)-8350 Eight-Core Processor           ",
		"Video Controller Name":	"AMD Radeon HD 7900 Series",
		"Video Controller RAM (MB)":	3072,
		"Total RAM (GB)":	16
	},
	"Drivers":	[{
			"Path":	"\\system32\\OVRDisplay64.dll",
			"Version":	"1.0.25.0"
		}, {
			"Path":	"\\system32\\OVRDisplayRT64.dll",
			"Version":	"1.0.25.0"
		}, {
			"Path":	"\\syswow64\\OVRDisplay32.dll",
			"Version":	"1.0.25.0"
		}, {
			"Path":	"\\syswow64\\OVRDisplayRT32.dll",
			"Version":	"1.0.25.0"
		}, {
			"Path":	"\\system32\\drivers\\RiftEnabler.sys",
			"Version":	"1.0.24.0"
		}, {
			"Path":	"\\system32\\OVRDisplay32.dll",
			"Version":	"1.0.25.0"
		}, {
			"Path":	"\\system32\\OVRDisplayRT32.dll",
			"Version":	"1.0.25.0"
		}, {
			"Path":	"\\system32\\drivers\\RiftEnabler32.sys",
			"Version":	"File not found"
		}, {
			"Path":	"\\system32\\drivers\\OCUSBVID.sys",
			"Version":	"0.0.1.6"
		}],
	"Devices":	[],
	"LocalProtocolVersion":	{
		"Major":	1,
		"Minor":	1,
		"Patch":	0
	},
	"RemoteProtocolVersion":	{
		"Major":	1,
		"Minor":	1,
		"Patch":	0
	}
}

I also see in Windows Event Viewer the following:

The description for Event ID 0 from source OculusVR cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Error: {ERR-023} [TrackingManager] Unable to create detected HMD sensor device

And that is after a fully clean uninstall/reinstall reboot etc.

I have also attached Direct X Diagnostics info to.

Someone please help- this is getting frustrating not being able to jump right into Unity and carry on the VR projects.

[mrcrisp]

Update: I removed the DVI>HDMI converter and moved the DK2 direct to the HDMI port on the HD7950 card- and bingo- back to normal.

Strange- as the DVI>HDMI converter worked before- but as I have added 2 additional (but not now connected) monitors, I did move some connections around.

The DVI>HDMI adaptor is not broken as I have tested it with a standard monitor- so I have no idea why it is being a pain in the backside.

Perhaps my logs can get to the bottom of why its a pain in my arse...

[SharpShark]

Any news about what caused this issue?

I got the same issue. Some weeks ago, I fixed it by uninstalling Teamviewer, but now the issue is back and I don't know how to fix it. Like you, Direct Mode seems to work and the device is detected, but as soon as I change it to Extended Mode, it ceases to be detected, although the display seems to work.