New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

For Users w/ Black Screen on Rift, Post Logs Here

1457910

Comments

  • EBMoreauEBMoreau Posts: 1
    NerveGear
    edited April 2018
    Hello all,

    I also have a problem with a new machine.

    My machine is a brand new HP laptop ZBook G4 with a NVidia P4000. Fully certified with that Oculus tool.

    My Oculus is working on another machine, but when I try to make it run on that laptop, it shows that all USB and HDMI connections are good (green dot). I set up the controlers properly and I skip the Guardian. Then I get to the install step where you put on the HMD but all I see is a black screen. The orange light is on (and shuts off when I put mt glasses on ) but I see nothing.

    At this point of the Oculus update, once the Sensors are setup, I can skip the setup and the Oculus desktop is available. I try launching Google Maps VR. The applications starts properly , I see the desktop as if the googles were working properly, the application properly detects the movement of the HMD, but still not image , only blank screen!!

    I've changed the Bios to make the video card in Discreet mode (to disable the Intel).

    I've tried with different version of NVidia drivers without any change.

    I've rolled back Windows 10 to an earlier version 1703 without any change.

    I've uninstalled many times the Oculus Setup (with deleting setup files) without any change.

    With the Port Replicator (similar to a docking station), I have access to 2 DisplayPorts , but the result with those ports and some adaptors are even worst than HDMI.

    I'm trying the normal version and the 2.0 Beta of Oculus  without success.

    Please take a look at my logs once I rebooted and started Google Earth VR...

    I don't know what to try next!!
  • PeleousPeleous Posts: 5
    NerveGear
    Still having problems here. Tried rolling back nvidia drivers, and tried reinstalling without any USB devices plugged in. Still gettting audio, but no video at all. Restarting doesn't help (even temporarily) just flat out no video. Any help would be very much appreciated. I think this is the right file; OculusSetup. (Couldn't find anything called OculusSetup.log)
  • PIXELATEDPIXELATED Posts: 242
    Nexus 6
    edited April 2018
    @Peleous
    Yesterday I received a brand new replacement headset as the the two previous refurbished ones sent had various issues - long story... but when I came to plug in the new one I got the Black screen issue. After about 8 hours trying everything (esp from lordhelmos) on this thread.... latest usb drivers, Nvidia, swapping and changing everything etc etc  I tried one last thing; I removed my USB and HDMI extension cable for the headset and hey presto it worked! 
    So strange as the extension cable had worked for all the headsets I've had and haven't been touched while i was waiting for the new headset to arrive.
    The PC I made is purpose built for the Rift so no other use, no email no web, nothing apart from Elite Dangerous and Rift. Win 10 pro on an Asus Z170 deluxe, SSD and GTX1080 so no tweaking or other programs running - go figure?? Tho i suspect headsets have been updated since launch and it just depends if it likes you using it (-:

    PS - I tested my hdmi extension cable (that i previously used on Rift since launch) and it works perfect on a 4k tv/ Denon Amp ARC (audio return)... but I've been reminded that Oculus do not support extension cables

    Good luck Peleous
    Win 10 Pro, GTX 1080, Asus Z170 Deluxe, Nvidia 391.35
  • PeleousPeleous Posts: 5
    NerveGear
    @PIXELATED
    Thanks for the help! Unfortunately, I'm not using extension cables, so I don't think that's the problem. However, I am thinking the standard headset cable is in the running for being the issue. I've tried the headset on 2 desktops and a laptop (all meet system requirements), and having the same issue across the board. Definitely a problem with the Rift. It's just weird because everything is showing up green on the devices tab... if it were a cable issue, I wouldn't think they'd show up green. I think that's probably my next step.

    At any rate, I appreciate the help. Still no word from Oculus, so good thing the community is lookin out;)
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Can you install the latest Nvidia driver and try again? Same with anyone else in the thread, as the Nvidia specific bug should be resolved according to Nvidia. The log file we need is the zip file created by LogGatherer.exe. See here for how to obtain that file. 
    https://forums.oculusvr.com/community/discussion/33792/how-to-get-logs-for-bug-reports-for-consumer-rift-1-3/p1
    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
  • PeleousPeleous Posts: 5
    NerveGear
    Thanks for the reply cybereality. Currently running the latest driver of Geforce Experience - Driver 391.35 and having the same issue. I hear audio, but no video. Unlike some of the other posters, I do not get any video at all, even after a restart. It sounds like other posters lose video after it going idle for a little while, for me I get no video at all.

    I think I pulled the logs correctly this time. Please take a look and let me know if you see anything that stands out. Really appreciate the help.
  • douggyvegasdouggyvegas Posts: 7
    NerveGear
    edited April 2018
    hi,I got the black screen problem since I have the rift,the only thing I can do is when a black screen occures ,I unplugg the usb of the rift and re plugg after few seconds without reboot the computer,and usually I have no more black screen or sometimes after more than 2 hours...dont know what is the problem but that can help someone...

  • icuurd12b42icuurd12b42 Posts: 14
    NerveGear
    edited April 2018
    I see all them driver related issues, here something mechanical that I experienced...

    I played 5 minutes after the initial setup. I then put the headset down to browse for games... Then I put the headset back on and I had a black screen...

    Turns out the cable from inside the headset had disconnected. I fiddled with the wire where it goes inside on the headset casing and heard/felt a tiny "click" and I was up and running again...
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    @Peleous It appears the Rift display driver is not installed on your system. Can you see if you can install it manually?

    You can check this folder:
    C:\Program Files\Oculus VR Runtime Drivers\Drivers\Monitor
    And right-click "RiftDisplay.inf" and choose Install. If that folder isn't there, see the attachment.

    Or go here:
    C:\Program Files\Oculus\Support\oculus-drivers
    And double-click "oculus-driver.exe"
    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
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Also, can you make sure you're on the latest Nvidia driver, 391.35
    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
  • PeleousPeleous Posts: 5
    NerveGear
    @cybereality
    No luck.

    I don't have the pathway C:\Program Files\Oculus VR Runtime Drivers\Drivers\Monitor. No Oculus VR Runtime file, so I'm not able to install "RiftDisplay.inf"..Also, Because I don't have these folders, I'm not sure where to put the file you attached. Is there somewhere else I can put these files?

    I do have the pathway C:\Program Files\Oculus\Support\oculus-drivers. When I double click "Oculus-driver.exe" it doesn't seem like anything is happening. I get an authorization request pop-up from windows, and when I click yes I get a circle pop up on my mouse cursor like something is going to happen, but then it goes away and nothing happens and I still have the same problem when I launch Oculus - I hear audio, but no video at all. (One thing I did notice, when I tried opening Oculus immediately after doing trying to install the drivers, I got an error message saying "Oculus can't open - it may be updating. try again in a few minutes". So something is going on behind the scenes, but there's no install bar or any other type of indication. not sure if this means anything.)

    I double-checked and I am running the latest Nvidia drivers 391.35. I reinstalled them just to be safe, but still the same problem.

    Please keep in mind that I'm having this problem across multiple computers (my old desktop that was previously working with Oculus, my new desktop - a Corsair One with GTX1080ti, and my laptop - ROG Zephyrus with 1080). Not having the display driver would definitely cause the kind of a problem I'm having, but it's strange that it would be happening across 3 different systems (all running Windows 10 64-bit, and all running the latest Nvidia drivers).

    Any other suggestions? and thanks again for the help.
  • koffein77koffein77 Posts: 1
    NerveGear
    edited April 2018
    Having same problem any solution ?
  • chatbottechatbotte Posts: 1
    NerveGear
    I have nvidia gtx 980 latest driver 391.35, with dash 2.0 , I had to rollback the nvidia driver to 388.59.
  • MontoMontoMontoMonto Posts: 2
    NerveGear
    VR Gamers, greetings from Mexico.
    First... let me tell you about the main components of my PC:
    - Intel Core i7 5690X
    - 32 GB DDR4 2666 MHz
    - MoBo ASUS Rampage V Extreme
    - 2x Geforce GTX 980Ti in SLI
    - Oculus Rift, 3-sensor array with 2 touch controllers and a XBOX One Elite Gamepad.

    I was desperate because my Rift was crashing randomly, and with the Core 1.0 usually the device restarted and I was able to continue my game. However, this was not happening with Core 2.0.
    This issue about the black screen with the game totally frozen was a constant for me, and with Core 2.0, although is remarkable and beautiful, with the chance of customization of your virtual loft, the message of Error: "Guardian system isn't working correctly" appeared almost in every session, and oh Lord I've tried everything:
    - Disable the power management of USB ports and devices
    - Install an update for Windows 10
    - Re-arrangement of the sensor setup/positioning
    - Disable or re-setting up the Guardian Sytem
    - Repair the installation of Oculus Core software, etc.

    I've corrected this issue with an indirect hint from another user with the same problem as mine.
    I've realized that you can't connect all the Oculus Rift components to USB 3.0 ports. I am not an engineer or a computer professional, so I apologize for the nonsense that I could write down in this post, these are only my observations.
    In my configuration (1x OR, 3x S and 2x TC) you need to connect everything to USB 3.0 with the exception of one sensor (and touch controllers, of course), that must be in a USB 2.0 port, in order to get everything functioning. However, I've noticed that the recognition of the USB devices is random, at least in my PC, and the connection between the Oculus system components can be changed from USB 3.0 to USB 2.0. You can notice this in the "devices" tab, clicking once in every device and watching in the USB line. 
    It seems also that the Oculus Rift VR visor MUST BE always connected to (or recognizing) a USB 3.0 port. It seems also that the sensors could work in USB 2.0 with only one connected to USB 3.0.
    I disconnected EVERY device from all the USB ports from the back of my rig and tried in a proof/error way in order to get ALWAYS the VR visor in a USB 3.0. It's very important that the visor is connected (and recognized) in a USB 3.0 port.
    I have now almost 3 weeks, happily playing VR games without any "Guardian system isn't working correctly" error and/or black screen/game freezing issues.
    If you have this problem, this may work for you.
  • DonutMakerDonutMaker Posts: 2
    NerveGear
    Peleous said:
    @cybereality
    No luck.
    Any other suggestions? and thanks again for the help.

    After having these issues, I rolled back to the recommended NVidia drivers and have had zero issues since.  I haven't even attempted to update to the new drivers since people are reporting the same issues with the new drivers.   In fact, I'm not sure I've even seen a post reporting that their problems were fixed with the newest drivers, so I'm very hesitant to install the latest NVidia drivers for fear of the problems coming back.  

  • PIXELATEDPIXELATED Posts: 242
    Nexus 6
    edited April 2018
    chatbotte said:
    I have nvidia gtx 980 latest driver 391.35, with dash 2.0 , I had to rollback the nvidia driver to 388.59.
    I Have Win 10, GTX 1080, Asus Z170 Deluxe with Nvidia 391.35 driver!!! dash2 and all ASUS 's latest usb drivers and my newly replaced Rift works... all be it without extension cables...
    I can't understand why these Nvidia drivers are causing issues for so many... Maybe wipe clean using 'DDU driver uninstall' program, search on web for walk through.
    Good luck
    Win 10 Pro, GTX 1080, Asus Z170 Deluxe, Nvidia 391.35
  • ZachAttack420ZachAttack420 Posts: 3
    NerveGear
    edited April 2018
    I have a Asus Rog GL703VM gaming laptop, windows 10, GTX 1060 6gb and I'm using driver version 388.59 (also tried latest version). Windows is updated. Everything checks out with the oculus compatibility check tool. I've been getting the black screen issue since I first tried to set the oculus up. The best I've been able to get is the menu screen working perfectly for about a minute or two before it started to flicker black, getting worse over 30 seconds before going black for good. I feel like I've tried everything (changing windows settings, reinstalling oculus app, restarting computer several times, driver updates/rollbacks, checked both ends of HDMI and re seated, switched USB ports ( I have 3 3.0 and 1 2.0), manually updated oculus drivers)ect.. I'm using the classic version of rift core (although I tried 2.0 once and it didn't work either) and have been disabling guardian on my recent attempts. I've been trying to set this up all week with no luck so any help would be much appreciated, thanks.
    Edit: changed a few setting on nvidia control panel and also bought a mini displayport to hdmi adapter. Not sure what did the trick but works perfectly now.. took a while to get it going but no complaints yet. Skyrim VR is great. 
  • wardzackwardzack Posts: 9
    NerveGear
    I am fairly confident this is oculus driver related. There was a new update about 2 hours ago and ever since the update, my screen turns off after about 5 minutes. It used to turn off after about 10-20 minutes prior to this update.
  • uzul81uzul81 Posts: 4
    NerveGear
    edited April 2018
    I have this issue with two devices (Win10 x64 both):
    - Laptop i7 7700HQ 16Gb 1060 6Gb
    - Desktop i7 8700K 32Gb 1080Ti

    with latest driver 391.35, also try with 388.59 - no hdmi and yellow light. Reinstall oculus app, drivers, change USB ports, re-seat HDMI etc - nothing help...

    I tried plug in headset into pci-e USB 3.0 card (it worked with this oculus on my old desktop) - no result.
    I plan to try DPORT to HDMI converter next.
  • uzul81uzul81 Posts: 4
    NerveGear
    Display port to HDMI or DVI to HDMI - helmet still not working... Next try - install 1060 into desktop (i have one) and test it.
  • DaWeeeedDaWeeeed Posts: 1
    NerveGear
    Guys, my patience is slowly running out... Bought completely new gaming PC with 1080Ti, primary to enjoy the Oculus, which costs me something 2500+eur plus the price of oculus...  Everything was running fine and smooth but as I updated the nvidia drivers all went black... I read all the posts, said, ok, sh.t happens and was waiting to get this fixed... Now, I spend 2 hours trying to do all the clean driver reinstall with the DDU, clean reinstall of the oculus app, everything I was able to find about how to bring it back to life.  Sadly, no success at all.  Please, since it is already more than a month, I would really like to hear a feasible solution HOW I CAN BRING THE OCULUS BACK TO LIFE as this is definitely NOT what I was opting for.  Its a HUGE shame on nVidia and you too, that you guys are releasing updates that F..K everything that was working and now, you cannot bring that back to life in more than one month time! Looking for a solution from you asap, otherwise I will have to think of money reclaim as you are selling something that is not working and will have to move to HTC...  Dont want to do that, just want my oculus back working...
  • john.zigmontjohn.zigmont Posts: 115
    Art3mis
    edited April 2018
    I have advise on the current problem which could help some user's.
    When everything is working correctly create a system image. Before updating your NVidia or AMD drivers create a system image. If the new video drivers cause a problem submit a ticket and roll back to working system image if Oculus pushes a new update and your system stops roll back to working image. I been using this system for years with software and drivers to avoid hours of troubleshooting the worst case is I have had to wait till my system image is restored which is 9 minutes. My system image is 37GB.
    This way you always have a system image which works with the Oculus.

  • blacky75blacky75 Posts: 27
    Brain Burst
    edited April 2018
    I'm racing alot under iRacing... since a week now I'm experiencing VERY unconvenient short time 1-2 sec blackouts... until my last race ended up with never coming up again :(  What's going on?! I reverted back to the old nvidia driver, didn't changed the issue... what's the problem?
    specs: MB-Asus P9X79, CPU-i7 4820K (not OC'ed) Watercooled, RAM-64Gb, SSDs, GC-Zotac AmpExtreme 2080ti, Oculus Rift S, 3x32Samsung Screen
  • GregTampaGregTampa Posts: 20
    Brain Burst
    logs too big to attach, but im having this issue.. and even sometimes one side will go dark. or both.
  • darklink11darklink11 Posts: 2
    NerveGear
    edited April 2018
    well my oculus app work one time after i close it and want to relog i  just get a black square and dont see anything on my pc screen  FIX IT!!!!!!!! if i want to start repair i get cant connect and i should check my Internet well if my Internet isnt working how can i Post a Comment with my Pc OCULUS -.- well i can't attach my log either
  • dombom88dombom88 Posts: 4
    NerveGear
    I have the same problem. First when I installed the Oculus I had screen on my headset, but it wasn't detected by HDMI. I reinstalled the RiftDisplay.Inf and now my Oculus stays black and the orange light is on. I'm trying since 10hours to fix it, but no chance so far. Rolled back my NVidia drivers to 388.59, but it doesn't help.
    I attached the log file. Maybe someone has an idea whats wrong.
    Maybe its the denied access from windows? No fckn idea...
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Did you maybe install the Oculus setup with Run as Admin? If you do that, it will mess up the permissions, Please uninstall Oculus completely and install normally (NOT Run as Admin). Also, it's having trouble finding your headset, that may be a USB issues so try different USB ports for the headset cable (USB 2.0 works as well) and/or update your USB drivers.
    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
  • Crespo80Crespo80 Posts: 604
    Art3mis
    MB ASRock Z170 gaming-ITX/AC,
    CPU Intel Core i7 6700,
    RAM 2x8GB DDR4 Corsair Vengeance LPX 3000 MHz,
    SSD Samsung 850EVO 500GB
    GPU MSI Geforce GTX1070 armor.
    Windows 10 PRO 64bit

    I also have the problem on latest drivers 391.35: sometimes Windows says there's a problem with the USB controller, sometimes the rift doesn't detect a sensor or says there's a problem, when I play a game the screens starts juddering badly, then it goes black for good.
    I had a fresh install of Windows and the problem persisted.
    I reverted from core 2.0 to old Oculus mode, then reverted the Nvidia drivers to 387.92 and the problems changed: after a few minutes the frame-rate drops and the screen of the rift starts juddering badly, but the screen doesn't become black. The image on the monitor is OK and it doesn't seem to suffer low frame rate.

    For other reasons I'm in the process of switching platform, I'm moving to Ryzen (I will also change the PSU), but I'm keeping the GTX1070 for now, I'll report to you if the problem persists.
  • MAC_MAN86MAC_MAN86 Posts: 2,262
    Wintermute
    edited April 2018
    OK I finally fixed my Judder problems which began around 4th April. There was no Driver Update to cause it but something triggered it, possibly Renesas USB3 Driver Update (Microsoft) or a Mediatech Update which installed a driver for Andoid Phones knowing you connected one already. Plus the Oculus Firmware and generally things expanding and using more system memory.

    *Used latest DDU Driver Uninstall in Safe Mode - although about 7 ways to get in Safe Mode it for Win10 was not so simple when it tries to find ISO of OS to revert to as 1st auto step! I used HOLD SHIFT whilst selecting RESTART in START MENU to get there. Cancalled the ISO search, Advanced, it reboots, gives you several options, Select Safe Mode number 4. Use DDU (not connected to net & not to install driver upon boot). From here I found the Driver 384.94 also on the DDU website and installed using Microsoft method of Updating Driver in Device Panel rather than using the daft package with Experience. 
    *It went well but there was no Nvidia Panel on Right-Click until I rebooted yet again as is normal for drivers to work properly. Then to config the FULL DYNAMIC RANGE as this gets your black the most black. I also altered DSR=ON and checked all boxes just in case it required this. (???)
    *E:D running Max but Shadows to High as a compromise and OculusDebugTool PD= 1.85 and it runs fine. On 1.9 I get slight stutters. On 2 I get it ok everywhere except in Stations at times it goes crazy so I take it that is bottlenecking, heat, and memory all at once. My EVGA Precision-X fan control & overclock takes 44MB and I maybe better without it (???). Otherwise, I got it working fine and super smooth on PD=1.85 and happy.
    *It also installed the daft 3D Driver so I removed that and I already Disable the standard driver for my Monitor so it didn't put Nvidia Audio on either. It did put on PhysX which hardly any games use now plus VulkanRT (excellent) and this I read made LONE ECHO work again for one user so I may try this again. Although I had many hard crashes when I tried it last time to no avail and it could have been the cause. That is severely bad of them to add SSE4.2 check in a game. It installs but can not run past the menu.


    *I had a few occasions with a black screen whilst it had Judders. One time when I selected through alias in E:D it just went black when I selected FXAA. However, in Nvidia Global Settings this is set OFF as default yet it has always worked before plus it does again now fixed. Although I really prefer SMAA and ignore the slightest of jitter around the screen edges for big objects e.g. a Station when rolling fast. Another time when I played with e OculusDebugTool Sensor ON/OFF and it too just went black but cam back on again.
    *I must also add that it took quite some time for the PC files to settle as it performs some filing processes in the background. This is due to the files now being spread out from previous installs. I think this is called "INDEXING". Loading times are longer initially but that maybe partly pre-warmup shaders calculations.
    CHECK THIS OUThttps://forums.oculusvr.com/community/discussion/62663/how-nvidia-ruins-the-oculus-rift-experience#latest
  • wardzackwardzack Posts: 9
    NerveGear
    Anyone have any success with the latest oculus update?
Sign In or Register to comment.