Showing results for 
Search instead for 
Did you mean: 

Having Problems w/ DK2? [OLD - For Runtime]

Level 15

If you recently received your DK2 and are having problems, please read below.

Before playing any DK2 games, you will need to install the Oculus Run-Time. It is available on the download page:

After installing the Run-Time, please use the Config Util to setup a profile for your DK2. This will let you set your IPD, height, and other options. You can also try the demo scene (inside the Config Util) to make sure the device is working.

In most cases, choosing "Direct Mode" for the "Oculus Display Mode" will be the easiest setting. I believe it selects this by default, but you can always change this from the Oculus icon in task manager (in the lower-right corner on Windows, right-click and choose "Oculus Display Mode"). In "Direct Mode" Windows will not detect the DK2 as a monitor, but games will still be able to work. The light on the headset will stay solid orange, and the screen black, until you play a DK2 compatible game. Once the game loads the light on the DK2 will become solid blue.

If, for whatever reason, "Direct Mode" is not working for the game you are playing, then you can try "Extended Mode". In "Extended Mode" you will need to set the Windows display to extended desktop (and NOT mirror/clone/duplicate).

You also *MUST* rotate the screen orientation for the DK2 screen. Otherwise your screen will be flipped on it's side. You can change this in the Windows display settings, or in the Nvidia/AMD control panel. In Windows you can right-click the desktop, choose "Screen resolution" and then change the "orientation" options from "landscape" to "portrait". With Nvidia, it's under "Display" -> "Rotate Display".

This may also be a good chance to make sure the DK2 is set to 1920x1080 resolution at 75Hz refresh rate.

Keep in mind that the DK2 will *ONLY* work with games and apps that are specifically coded to support the Rift. Just trying to play any old game with the Rift WILL NOT work. You can find a list of DK2 compatible demos on Oculus Share:

If you run a non-Rift game, or regular 2D application (including the Windows desktop, web browsers, etc.) then the image will look oddly overlapping or cross-eyed. This is because the Rift uses a single display panel shared between both eyes. So each eye is only seeing one side of the same panel. So if you look at normal 2D content, you will only see half in each eye, which is obviously not comfortable.

If you are experiencing choppy motion in games, also called judder, there may be different solution. The first thing to check is that your computer is fast enough to maintain at least 75fps while playing the game. If you have an older computer, the performance can be an issue. Having Aero (desktop composition) "off" can cause slow fps. Make sure Aero is "on". If you are running multiple monitors, this can also be a source of issues. Making the DK2 the primary display can help. Or you can try setting your monitor to 75Hz refresh (usually this will need to be at a lower resolution like 1280x1024). If you are playing Unity content, make sure it's running in DirectX 11 mode. You can do this by creating a shortcut and adding this to the end of the target command (after a space):


If your Rift is not being detected at all by the Config Util, then games will not work. In this case, you may want to double-check all the cables and ports. For example, switch the USB port for the Rift and camera, and also the video port on the GPU. Plugging into a powered USB hub can also help. USB 2.0 may have better support. You can also use new (3rd party) HDMI and USB cables. This cable may work as a replacement for the sync cable: ... 1&format=2

If you are having camera detection or positional tracking issues, then try plugging the sync cable directly from the camera to the headset. You can find the port on the top of the DK2 under the rubber cover. You can also try purchasing the replacement cable above.

In the event you're experiencing crashing in games, or they fail to open, it could be a few things. First, make sure your GPU (graphics card) can support DirectX 11. While older cards may work with some games, it can be a source of issues. Make sure you have the Visual C++ Redistributables installed. You will want both 2010 and 2012 versions in both x86 and x64 flavors. ... px?id=5555 ... x?id=14632 ... x?id=30679 ... x?id=40784

As of the 0.7 Runtime, you should also install the 2015 files (x86 and x64): ... x?id=48145

If you are on Windows 7, and receive exception reports when opening the Oculus Config Util, try installing this patch. ... x?id=36805

If you have a laptop, please understand that switchable graphics (i.e. Nvidia Optimus) are not well supported. In this case you will have an integrated Intel GPU working along side a more powerful Nvidia or AMD card. Unfortunately, this can be problematic and not recommended. In fact, laptop computers are not recommended at all due to lack of power and various compatibility issues. For the best experience, please use a desktop machine with a dedicated Nvidia or AMD GPU. It's hard to give an exact minimum supported spec, but please try to get a powerful, modern graphics card.

If you are using an AMD GPU, there are currently some compatibility issues with newer drivers. This may manifest has the desktop becoming a black screen, games crashing, etc. It is recommend you revert to Catalyst driver 14.4 until the problems are solved.

If you are on an Nvidia GPU and are getting a strange double-image in each eye, it is a bug with the 347.09 driver. Please update to driver 347.25 (or newer) for better compatibility (make sure to do a clean install and un-check any Nvidia 3D Vision options). Also, if you are using a G-Sync monitor, you may get strange artifacts on the left side of the screen (shifting the Rift image to the right). To work around the problem, please use Direct Mode.

Currently there are conflicts with certain anti-virus and security programs (like ZoneAlarm or Comodo) that may cause the installation of the run-time and drivers to fail. They can also affect running of the service. Unfortunately they may have to be uninstalled, just disabling may not always work.

In addition, USB display hardware or some virtual display/overlay software may cause issues. Known problematic hardware includes DisplayLink, Dell SuperSpeed, and Asus USB displays. Software such as TeamViewer or Origin in-game-overlay may also cause issues.

Finally, if you receive and error that looks something like this "57493-Public TCID:158609 is not responding" it probably means you have the Rift plugged into the wrong video port. This can typically happen when you have multiple GPUs (for example SLI/Crossfire or integrated) and plug the Rift into the wrong video card. Ideally, the Rift should be plugged into the primary video card via HDMI.

For 0.7 specific issues, including supported GPUs and Windows 10 instructions, see here: viewtopic.php?f=34&t=26029

Hopefully this covers the main issues. If you have any common questions, please feel free to reply here. If you have a really strange or unique issue, then creating a new thread in the "Reporting Issues" section may be the better option. Thanks.

// cybereality
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
473 REPLIES 473

Level 2
I need some quick love, I'm in the middle of a hackathon. The is the second hackathon I've been at in a row where the DK2 has sh!t the bed on me. Last time was on windows 8. This time I'm having issues on both win7 and osx 10.10.

Anyway my issue this time is suddenly any rift apps would exit and produce a crash report, the notable line is "ACCESS_VIOLATION writing address 0x00000000". Any fixes/help I've seen online don't work and I didnt' expect them too because they imply that they fix and issue that always existed. In my case my DK2 was working fine and suddenly after compiling a new build of my game and going to run it stand alone, it crashed and hasn't been right ever since.

I brought this up at this link here and said the following:

viewtopic.php?f=34&t=18001&start=20 [Exception encountered in RiftConfigUtil]

"For the record (if it helps future investigation) my rift was working just fine until I went to play a game I was working on in unity. I just dropped dk2 support in, tested it in unity, worked fine. Built the binary, when to play it and now I get crashed with this exception: ACCESS_VIOLATION writing address 0x00000000."

Level 2
My DK2 no longer works on my PC. fresh install of Windows and cannot get it to connect. Weird. Never been a stable experience anyway.
Intel i920@4ghz, 12gb ram, Windows 7 Nvidia GTX 970 4gb, 120gb SSD, OR Dev Kit 1&2

Level 15
@13thFloor: Can you be more specific about your particular problem?

If it seems like a hardware failure, I would contact Oculus support.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

Level 2
Hello there. Can you help me?
I have a problem with sync cable of DK2. When I connect Cable of DK2 to usb (this problem with any USB-port on PC), I cannot boot an OS Windows 7 (x64), because an error is displayed.
Error: "USB device over current status detected will shut down in 15 seconds".
What I can do with this problem?
Best regards!

Level 15
Can you try getting a powered USB 2.0 hub and plugging the Rift and camera into that instead?
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

Level 2
Hello everyone, just wanted to put this info out there in case anyone is having issues. I managed to get the DK2 working on an Alienware 17 by using the Mini Display Port ( instead of the HDMI port. Then use the Extended Desktop to the HMD mode in the OculusConfiguration app. To mirror the display I use OBS ( as described here:

Level 2
"cybereality" wrote:
@13thFloor: Can you be more specific about your particular problem?

If it seems like a hardware failure, I would contact Oculus support.

I've done a fresh install of Window recently, updated all drivers and firmwares. I'm going to try tomorrow if I get a chance and I'll log a few things down and throw it supports way. Frustrating as by now quite a few apps should have been updated but just gave up on it.

Thanks for replying.
Intel i920@4ghz, 12gb ram, Windows 7 Nvidia GTX 970 4gb, 120gb SSD, OR Dev Kit 1&2

Level 4
please guys someone help me please or (Cybereality) please help, i Got my Oculus Rift today , I Setup everything and installed the Run time software before connecting the Rift just as directed here, I tried all the demo they work perfect , i also tried a game called Affected and its working great . My problem is DCS i followed all the steps mentioned for getting DCS to work , Rift is in extended mode, trun on DCS , it shows up on my main screen , when i( ALT +TAB) to put the Rift on primary it goes Black Screen.
I have an ATI card ( 6900 ) , i revert back to driver 14.4 NOTHING SOLVED and still black screen not fixed.
I downloaded a game called War thunder, its a native support for oculus , the game works in Extended mode .
Only DCS turns black screen i dont know why , all my friend they have the rift and they got it working with DCS but they all have nividia .

Level 2
HI guys, i can't seem to make my own post so il have to post here, I really want to buy an oculus DK2, I've downloaded a couple of demos to look at on screen just to see if my iMac is up to it and they look pretty laggy, jerky in places. Is this normal on screen without the headset? i haven't installed any SDKs or anything I've literally just downloaded the demos and pressed play.

Level 15
If it seems jerky (stutter or judder) on a monitor, then it will likely look worse on the headset. It probably means your computer or video card is not powerful enough to run at game at 1080p stereo 75Hz.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV