New To The Forum? Click Here To Read The How To Guide. -- Developers Click Here.

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

cyberealitycybereality Posts: 25,798 Oculus Staff
edited March 16 in Support
If you are still experiencing issues with black screens on Rift, please share your log files here. Usually with this issue, Rift will work the first time after a reboot, and then after removing the headset or going idle for a while, the screen in Rift will become black. Restarting your computer or the Oculus service can sometimes temporarily work around this issue. Some users have also had some success with rolling back their video card drivers (for example, to 388.59 on Nvidia). It would be helpful to know if you installed the latest Fall Creators Update, for Windows 10 users. It would also help to know if you are on Rift Core 2.0 or are still using the classic version. Also please note if you have Guardian enabled or disabled. 

See this thread for how to get your LogGatherer zip file.
https://forums.oculusvr.com/community/discussion/33792/how-to-get-logs-for-bug-reports-for-consumer-rift-1-3/p1

Note, the file may be too big to attach to the forum, so you may want to use a hosting service like GoogleDrive, etc.

Your help here will assist us in getting to the bottom of this issue. Thanks a bunch.

EDIT: If you're using an Nvida GPU and are having the black screen issue, it may help to send some files to Nvidia as well. See this thread for details.
https://forums.geforce.com/default/topic/1039358/geforce-drivers/requesting-end-user-assistance-with-vr-black-screen-issue-after-pc-has-been-on-for-extended-period-/
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
«13456710

Comments

  • KlodsBrikKlodsBrik Posts: 705
    3Jane
    You probably already know cyber. But it´s definately NOT a rift only problem.
    Latest windows insider preview seems to take a step towards what @LZoltowski "fast boot" help thread was about.
     http://www.tomshardware.com/news/windows-10-insider-preview-17107,36577.html

    There is probably more to it than this. It´s all so confusing these days for the people who dont have a functioning system. Mine is still working like a charm. Makes its even harder to help out when one haven´t had any issues oneself.
    Be good, die great !
  • XelsoXelso Posts: 12
    NerveGear
    Rift work the first time after a reboot, and then after removing the headset or going idle for a while, the screen in Rift will become black. Restarting your computer temporarily work around this issue.

    https://drive.google.com/drive/folders/1uTsB_DTW8AuwYjg62x7jM5AkZEI321Ov?usp=sharing

  • LZoltowskiLZoltowski Posts: 6,222 Volunteer Moderator
    Xelso said:
    Rift work the first time after a reboot, and then after removing the headset or going idle for a while, the screen in Rift will become black. Restarting your computer temporarily work around this issue.

    https://drive.google.com/drive/folders/1uTsB_DTW8AuwYjg62x7jM5AkZEI321Ov?usp=sharing

    Have a look at this thread for a possible temporary fix: https://forums.oculusvr.com/community/discussion/62269/possible-fix-for-hdmi-sensor-issues-after-pc-wakes-from-sleep-or-hmd-goes-black-after-idling#latest
    Core i7-7700k @ 4.9 Ghz | 32 GB DDR4 Corsair Vengeance @ 3000Mhz | 2x 1TB Samsung Evo | 2x 4GB WD Black
    ASUS MAXIMUS IX HERO | MSI AERO GTX 1080 OC @ 2000Mhz | Corsair Carbide Series 400C White (RGB FTW!) 

    Be kind to one another :)
  • doehla256doehla256 Posts: 1
    NerveGear
    edited February 24
    Hello,

    got the problems as described above. Attached my logfile. Would appreciate your help

    Thanks
  • TikitenTikiten Posts: 1
    NerveGear
    edited February 24
    Hi,

    Experiencing this problem. 
    Have used the Rift with another computer and works fine
    Trying on an Asus ROG G752VT
    Set up goes perfectly until putting on the headset in the configuration setup
    Green lights on USBs and HDMI connection during config

    Understanding that the 970m isn't powerful enough to run it great, I'm not able to get any video
    Get the Orange light with no video but audio works with Nvidia drivers 390.XX
    White light with no video but working audio with Nivida drivers 388.XX   - have tried .43, .59, and .71
    With Nvidia drivers 388.XX   and Rift 2.0  it quickly locks up goes into 1 frame per 20 seconds, then locks up completely after a few minutes
    With Nvidia drivers 388.XX and non-beta  it freezes every 5-10 seconds for approximately 3 seconds with no video but white light on headset
    Despite closing Oculus in this instance - it continues to lag, lower 1/4 of screen flickers, restarting Oculus service and app is not running - computer lags severely. 
    Restarting computer fixes this.  Starting Oculus app with 1 sensor and HDMI-Mini Dp adapter plugged in works fine.  Immediately on plugging in Headset it locks up and begins to chug.

    Plugged into USB 3.0 slots on right using 'Amazon Basics' HDMI-Mini DP adapter  -  Without adapter it shows only orange light and any settings
    Attempted to use USB 3.0 hub with external power no change

    Hoping for any assistance,
    Thanks
  • AekeroAekero Posts: 86
    Hiro Protagonist
    edited February 25
    Wow, so I came on here looking for a solution to almost _exactly_ this problem, glad it's not just me. this is possibly the first time I've ever had issues since launch.

    Using core 2.0 beta, guardian on, windows 10, gtx1080. Was able to get oculus home picture, but trying to launch elite just kept me at loading within oculus home. I could see elite come up on desktop, and head tracking was working, but never got past that point.

    Rebooted, was able to get picture, played for an hour or so (elite dangerous), took off headset for a minute, now I'm unable to get picture back. I can hear sound, but no picture again. 

    Restarted service, was able to get oculus home picture again, but back to not being able to get elite dangerous to run (same behavior as the very beginning)

    cleared service logs and logged from point of launching elite again to black screen in hmd (filename servicelogatlaunch)
  • karrtoonkarrtoon Posts: 116
    Art3mis
    edited February 25
    Here is my log http://www.mediafire.com/file/m6phsmhx46mnipf/Oculus_Logs_DESKTOPNEW_20180224_092902.zip

    I notice it happens when the HMD goes to sleep a bit like Cyberrealty mention, then when you put the headset on the Oculus logo comes up for a split second on the screen, then it goes black. I usually have to completely reboot to fix the issue. I'm on the Core 2.0 beta but I also had this issue on the regular branch.  Sometimes if I go to settings, beta, restart oculus it will work sometimes not, a reboot always works. I have a 1080ti and running the older Nvidia driver from 12/5/17 but it didn't help, none of the older driver recommendations did.

    PS. I have guardian enabled.

    I am on windows 10 fallcreators update, an overall fresh install. Never had the issue a few weeks ago.

  • karrtoonkarrtoon Posts: 116
    Art3mis
    Okay so restarts were not working anymore either today. I could get the Oculus logo then a black screen in the rift, and on both of my monitors. I opted out of the public test channel just now and everyhting appears to be working for now.
  • TylerCodeTylerCode Posts: 2
    NerveGear
    I am having the same issue.
    Windows 10 Fall Creator's update is installed, Guardian is enabled (although sometimes it states that it has to be turned off due to an error, usually right before the screen goes black.) Using Rift 2.0 Core. Version 390.77 Drivers for GeForce.

    I have attached the log files requested.



  • datacidedatacide Posts: 2
    NerveGear
    edited March 13
    Been getting this since I updated to the latest Nvidia Drivers (390.77) in the last week. Will be playing for hours without problems but sometimes, randomly when putting the headset on (headset in sleep mode), it will flash then go to black.  I can hear the oculus home music but image is black.  Moving the touch controllers around I can hear they are interacting with the menus but no image still. Reboots did nothing.  The only thing that brings it back is a display driver repair (through Geforce experience).  Running Windows 10 Fall creator's update, Asus 1070GTX Strix gpu. On Rift Core 2.0, guardian is enabled and using 3 sensors. I'll try to find my log file.

    edit: finally got my log file.  Yes its still doing the black screen thing.  Windows fast start is disabled.

  • MartronicMartronic Posts: 2
    NerveGear
    edited February 25
    i was using it about 2 weeks ago and i kept the hmd in a case. i set it up today (2/25/2018) and all i get is audio and a pitch black screen... no backlight or anything. 

    i am up running the fall creators update and i had the guardian system enabled... i tend to reset up the sensors each time i use it cause i am on a laptop and the sensors are moved sometimes... 
    i rebooted and restarted the service and even shutdown and unplugged everything... no luck i dont want to reinstall so i havent done that yet... but i dont think thats the issue
    i have uploaded 2 log zip files... the 7 mb one is the 24 hour logs and the 8 mb one is all logs

    i  have oculus app version 1.23.0.527813 (1.23.0.5.528114).... so i dont think it i rift core 2.0

    please help... i spent 480 on this setup... (i got an extra sensor for out and about, i dont have the space but when i finally take it out at college ill be able to have decent 360 tracking with the 3rd sensor, but its not attached in my current setup that was used for the logs)

    update 9:50 pm 2/25/2018 cst:

    well i even rolled back my driver and even reinstalled it with the version 388.59 or whatever is recommended. but still no luck. still a pitch black screen with audio and touch controllers working. i am going to submit a support ticket... as i have done what eveyone has said here multiple times! 
  • ericzhuVRericzhuVR Posts: 9
    NerveGear
    I am a new user and have not been able to initiate Oculus sign in successfully.  I typed in my email and pw and hit enter, but then I get a black screen on PC.  My Rift headset has flashing red and blue bars with nothing else on it.  I've reinstalled the OculusSetup.exe and did the repair but same outcome occurs. My windows updates are all up to date as well as checked that I have enough memory on my PC.  Could this be the same Nvidia Drivers issue some users are having?  Any suggestions to resolved this is much appreciated! 
  • cyberealitycybereality Posts: 25,798 Oculus Staff
    Thanks for all the logs. We are looking into this now.
    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
  • kyle_cassidykyle_cassidy Posts: 2
    NerveGear
    My HMD is completely black, though I get audio. NVIDA 1080, I rolled back the drivers & restarted, re-seated all the cables. Still black. I get nothing.  Glad to discover it's not just me. I will now invoke Plan B, which is go to the bar & wait for the Oculus engineers to fix it.
  • SoenSonOfCerberusSoenSonOfCerberus Posts: 3
    NerveGear
    Moved my head around, rift was working fine, then craps out on me. Keeps disconnecting randomly and I was stuck in the floor of my beta home environment. Please help. https://puu.sh/zwm5h.zip

  • SoenSonOfCerberusSoenSonOfCerberus Posts: 3
    NerveGear
    Moved my head around, rift was working fine, then craps out on me. Keeps disconnecting randomly and I was stuck in the floor of my beta home environment. Please help. https://puu.sh/zwm5h.zip

    Okay Update to this. I tried keeping my head still, and the rift went black after five seconds. So, I turned off the beta. Repeated this, in non beta mode, five seconds of visuals, then black. This happened 3 more times until the rift had stopped responding. This is rather frustrating, as I really enjoy my rift, and I don't want to have to send it back.
  • LZoltowskiLZoltowski Posts: 6,222 Volunteer Moderator
    Have you tried re-seating the HDMI cable? Also, can you gather your logs and attach them here?
    Core i7-7700k @ 4.9 Ghz | 32 GB DDR4 Corsair Vengeance @ 3000Mhz | 2x 1TB Samsung Evo | 2x 4GB WD Black
    ASUS MAXIMUS IX HERO | MSI AERO GTX 1080 OC @ 2000Mhz | Corsair Carbide Series 400C White (RGB FTW!) 

    Be kind to one another :)
  • rgrleergrlee Posts: 13
    NerveGear
    I'm having a different problem with the Rift that I assumed was a bad cable.  I can get into games, but the screen randomly cuts out for a few seconds and then comes back with slightly different Gamma.  Every now and then while playing it also goes to a white background with what looks like a noise filter.  It also happens for just a few seconds.

    I'm waiting on a cable replacement from Oculus, but I have not had the continuous solid black screen problem others describe here.  Here are my specs to help you collate data.

    I7 6700K @ 4.0 GHZ
    GTX 1070 ( with latest drivers )
    Windows 10 Pro ( with creators update )
    RIFT 2.0 Beta ( was having these problems before updating to the beta )

  • SoenSonOfCerberusSoenSonOfCerberus Posts: 3
    NerveGear
    Moved my head around, rift was working fine, then craps out on me. Keeps disconnecting randomly and I was stuck in the floor of my beta home environment. Please help. https://puu.sh/zwm5h.zip

    Okay Update to this. I tried keeping my head still, and the rift went black after five seconds. So, I turned off the beta. Repeated this, in non beta mode, five seconds of visuals, then black. This happened 3 more times until the rift had stopped responding. This is rather frustrating, as I really enjoy my rift, and I don't want to have to send it back.
    It appears it was the Nvidia Driver... Well then... I feel like an idiot.
  • hkarrsonhkarrson Posts: 5 Oculus Start Member
    Just so you know, I have Nvidia Geforce Experience on my PC, which I use to install game-ready drivers for my GTX 1050 TI. Also, I'm not sure if this is related, but I am a developer, so I have Unity, UE4, and VS2017. Also, I have Steam, Epic Games Launcher, and I also have Fraps. And, I have a KVM switch, but I don't think that should matter. I run Windows 10, I have both an SSD and a HDD, and unfortunately opting out of Rift Core 2.0 doesn't switch back to the original desktop application and still has black screens, even if I repair the Oculus Software. However, restarting does fix it for a short period of time.
  • magnus.fosdalmagnus.fosdal Posts: 2
    NerveGear
    i had the same issue until i took and used DDU (display driver uninstaller) in safemode and rolled back to 388.59 and it fixed the problem for me but hopefully this will get fixed soon so i can update my drivers again without the fear of it happening again.

    The issues i had with the latest nvidia driver was the following:
    • blackouts used to happen after i played a game and let the headset idle for 10-15 min, reboots often fixed it until you played a game again and let it idle again.
    • software began forgetting devices connected randomly.
    • touch controllers unpaired from the software
    • had to go trough setup each time i rebooted
    then i read the 388.59 driver was the recommended driver to use for now wich made me use the ddu software as mentioned above and it completely fixed my problems.
    i sadly forgot to gather the logs before doing this as i was pretty frustrated and wanted to temp fix it asap.
  • harperhendeeharperhendee Posts: 5
    NerveGear
    I see definite issues with signal integrity leading to intermittent sparkles, flashing frames, or black screen.  I have a pretty monstrous rig, running with 2 MSI 1070 Quicksilvers that I operate either in SLI mode or individually.  
    I originally had this rig set up as multi-Virtual Machine VR server, with both Oculus Rift and Vive running simultaneously.  I have since moved the Vive to another rig and boot on single system.  This is all to say that I have played on this HW with both Rift and Vive.  Here's a table of findings:
    Rift direct: Pass
    Vive direct: Pass
    Rift with 10ft 4k rated extender(s) : Intermittent fail going to solid fail over time
    Vive with 10ft 4k rated extenders(s): Pass
    Rift with 1 foot HDMI cable to 4k HDMI repeater: Pass
    Rift with 6 foot HDMI cable to 4k HDMI repeater: Intermittent fail going to solid fail over time
    Rift with 12ft Ultra Premium certified HDMI cable to 4k HDMI repeater: Intermittent fail going to solid fail over time

    I tested several variables as not affecting results:
    1) HDMI source : Used both GVX 1 and 2, identical results
    2) HDMI port: Used HDMI, DisplayPort (with adapter), and DVI (with adapter).  No difference
    3) Mechanical stress: I worked hard to minimize this issue

    Some variables that still need further testing:
    1) EMI and crosstalk.  I have a lot of cables, including some power cords running along same route as extender cables.  There could be some cross talk, especially since I was able to run with the 12 foot extender when it was still coiled up.  When I routed it and reconnected, I got intermittent fails.
    2) USB3 power.  When I use an extender cable, I also use a USB3 extender cable.  I haven't had any USB3 errors, but there may be some marginality with VBUS.

    So if we look at the system, it is like this:
    GFX => Port => cable => [repeater] => cable => rift

    There are two kinds of failures when I go to black screen:
    1) Detected by Oculus SW
    2) Not detected by Oculus SW
    I think that failure failure #1 occurs when Oculus SW loses I2C connection to the Rift headset.  Failure #2 occurs most often.  The only resolution I have for #2 is to plug cycle.  This pushes the failure into bin 1, then the headset is detected again.  

    When I have failures, they may be thermal or power related.  This is because I only have issues when I'm actually playing in-game.  I've used Rec Room Jumbotron as a testbed.  I found that the failures always occured in more graphically intense scenes (like a firefight).  I don't have data to back this up  yet--need to take some graphs on power and temperature.  

    I have several theories about the root cause:
    1) Failures occur due to voltage droop from GFX card when under load
    2) Failures occur due to marginal performance of Rift cable
    3) Failures occur due to marginal performance of HDMI repeater (I can feel it warming up over time)

    It could very well be due to all of these issues.  Voltage droop could affect the HDMI repeater or the Rift HMD.  I'm not sure.  But it is incredibly frustrating to have this many phantom issues.  My play space is really limited if I don't have some sort of extender.  
  • drowhunterdrowhunter Posts: 12
    NerveGear
    The issue with the black screen is happening to me as well, i rolled back to the 388 drivers and it seemed to fix the issue but then the other day the rift kept connecting and disconnecting without me even wearing it.  So i opted out of the beta and the dash and now everything seems to work

    here are my log files

    https://drive.google.com/file/d/1hQ0Wjur9vxlfeHCIyFRoPE_akbXqx_uJ/view?usp=sharing
  • Duncan_DisorderlyDuncan_Disorderly Posts: 53
    Hiro Protagonist
    Yesterday, I downloaded the latest NVidea driver (391.01). This is new and not to be confused with 390.77. 

    The latest driver appears to have solved my black screen issues when trying to boot my Oculus. Both my Oculus and monitor would go black and I'd have to use the reset button on my pc. But, this is no issue now that I've downloaded the new driver.

    Hope this helps. 
  • RahotepRahotep Posts: 25
    Brain Burst
    Yesterday, I downloaded the latest NVidea driver (391.01). This is new and not to be confused with 390.77. 

    The latest driver appears to have solved my black screen issues when trying to boot my Oculus. Both my Oculus and monitor would go black and I'd have to use the reset button on my pc. But, this is no issue now that I've downloaded the new driver.

    Hope this helps. 
    I have 390.77. I will give the new driver a try tonight. Thanks for the feedback
  • Duncan_DisorderlyDuncan_Disorderly Posts: 53
    Hiro Protagonist
    Rahotep said:
    Yesterday, I downloaded the latest NVidea driver (391.01). This is new and not to be confused with 390.77. 

    The latest driver appears to have solved my black screen issues when trying to boot my Oculus. Both my Oculus and monitor would go black and I'd have to use the reset button on my pc. But, this is no issue now that I've downloaded the new driver.

    Hope this helps. 
    I have 390.77. I will give the new driver a try tonight. Thanks for the feedback

    You're not going to believe this. AFTER I posted yesterday my Oculus prompted me for an update. I updated. When my visor rebooted, same bloody problem all over again, black monitor screen and black Rift screen. I've noticed even my keyboard doesn't respond, as none of the lights, like caps lock, num lock don't light on or off when you press the appropriate key. I've tried unplugging and plugging my keyboard via the usb, the same with the Rift's usb and HDMI, my monitor shares the graphics board and I tried that. I know it isn't in conflict. Nothing I do helps. I must reset the PC. AGAIN! Recently, I'm apprehensive about using my Rift and have hardly played with it. Now, I don't know what to do. Nothing works. 
  • Pic0oPic0o Posts: 15
    NerveGear
    I have the same issues with black flashing and then clipping below the floor.
    Microsoft Windows [Version 10.0.16299.125] (1709) running Nvidia Driver 390.77 (getting ready to downgrade driver).
    I have guardian disabled and am in the Rift Core 2.0 beta.

    I can send logs but is there a semi-private way to do so? They contain quite a bit of machine information I would rather not openly share.

    I am seeing some Windows Event log errors kick out with an EventID of 0 for OVRServiceLauncher.
    Error 01:
    "[ProcessWatcher] Unable to create ACL for redist launch event. LastError = 0x0 (0): The operation completed successfully."

    Error 02:
    "[LauncherService] Could not stop 'C:\Program Files\Oculus\Support\oculus-runtime\OVRRedir.exe' because process handle (00000000000003CC) did not become signaled. Result = 258. LastError = 0x0 (0): The operation completed successfully.

    Assuming process is stuck and killing it forcibly..."

    I can also get the hard-black screen by removing my headset and putting it back on. Audio will play but no video will display.
  • Pic0oPic0o Posts: 15
    NerveGear
    My last post got eaten, but yes I rolled back from Nvidia driver 390.77 back to 388.31 and the floor clipping issue and black screen went away.

    I am on Creators update 1709 (Microsoft Windows [Version 10.0.16299.125]) with Guardian Disabled and running Rift Core 2.0 Beta.

    I have some windows error logs from the application section that were popping up before I rolled my drivers back.
    [first log item]
    Source: OVRServiceLauncher
    EventID: 0
    '[LauncherService] Could not stop 'C:\Program Files\Oculus\Support\oculus-runtime\OVRRedir.exe' because process handle (00000000000003CC) did not become signaled. Result = 258. LastError = 0x0 (0): The operation completed successfully.

    Assuming process is stuck and killing it forcibly...'

    [second log item]
    Source: OVRServiceLauncher
    EventID: 0
    'The following information was included with the event:

    [ProcessWatcher] Unable to create ACL for redist launch event. LastError = 0x0 (0): The operation completed successfully.'

    I'm sorted again with older drivers. Hopefully the windows logs help, as I didn't want to publicly share the debug logs as they have lots of system information in them, I'd rather share semi-privately.
  • GabkicksGabkicks Posts: 24
    Brain Burst
    i have 391.01 nvidia drivers and latest oculus beta software and still have trouble. If i put my headset on, i will get video and audio for a few seconds, but it stutters every 2 seconds or so a few times, then the screen goes black.,
    Oculus rift DK2, 4790k, R9 290 crossfire disabled, 16gb DDR3 1866, Windows 10 64-bit, 2 monitors.
  • shadowrydrshadowrydr Posts: 108
    Art3mis
    I get that black screen, But if I go back to the old home and out of the Beta, the unit works again. So I believe it is something between the new Dash 2.0 and possibly the Nivida newer drivers.
    Win10 64bit
    Intel 6 Core i7 5930 3.5GZ-Water cooled/GA-X99 UD4-/HX1000W PS/32GB DDR4 2400MHz
    Nvidia 1080 FE 8GB / 840 GB-SSD-/ 2TB HDD-
«13456710
Sign In or Register to comment.