8K X Occasionally Blacks out for a few seconds (Potentially Solved, EMI Ground Loop/ Interference likely the cause)

Im just using the per eye brightness levels… It may have been that both the HMD and per eye brightness levels were too much. Still not sure if that’s the cause.

1 Like

Might be an idea to test the brightness slider again once you receive that Y power cable from Amazon. As this maybe just power related.

I cancelled the y-splitter order. I use the optical cable so it wont work anyway you said.

The Y cable would still work on the usb3 to add power. As it is a hybrid cable. The power from usb is still copper from what I read so to speak.

The quest usb-c optical cable is a hybrid cable as well for power delivery.

I am not sure if the pimax cable is fiber on the usb side at all.

2 Likes

I’ve got 5-6 blackouts during playing Beat Saber right now at 90Hz mode. I can play a few songs without problem and get two blackouts in 30 sec in one song. Tracking and sounds still work during it. It seems fully random. I didn’t get any problems at 75Hz or at upscaled mode 114Hz (used it for playing BS before, 75hz is not enough for smooth gameplay at expert+ maps).
I’ve watched anime in the HMD at 90hz and get only one blackout in about 24 hours(4 sessions for 5-8 hours). So BS triggers blackouts a lot more, I have no idea why. I think that a problem may be in Display Stream Compression (DSC).
My rig: Gigabyte GA-Z370 HD3P / Intel Core i5-8600k/ 32 Gb DDR4@3200 MHz / MSI Suprim RTX 3090 / ASUS Xonar D2 / Seasonic 750W / Win10x64 LTSC
Driver version: DCH 461.09

2 Likes

While the 8K X is being used, monitoring/usage software should be running in the background to catch the point where the “blackouts” happen. It might show the issues and let Pimax and Nvidia work on a solution hopefully. Lots of things could trigger it, I don’t know and I don’t have a 30 series gpu, so I can’t run 90hz.

1 Like

PimaxUSA said that he’s been working on getting them to do active datalogging… Except I already saw that there is an option for it right in the help tab on pitool. You can start and stop logging… Kevin said that it doesnt narrow down the issue enough so he’s been trying to get them to add in a better active datalogging feature that can show where the trouble area is… I just havent turned it on to use while using the headset to see how extensive these logs are.

I dont want the logging going on while in game just in case it causes an issue during a race. If the blackouts reoccur, thats one of the things i was going to try also to see if it can tell us anything.

1 Like

There is game software logs and Steamvr logs that may contain crash info. Some gpu utilities like msi afterburner or gpuz might also be able to log gpu as well.

Have you had a peak at iracing and steamvr logs for possible crash info?

In theory logging shouldn’t have much of an impact if any

Ye ill be trying logging to see if it comes up with anything

Anyone that’s having these blackouts should do the same. Turn on the logging in pitool, and check steamVR logs, etc… When it happens stop and save the logs and check what happened at that time and see if anything shows up

1 Like

Kevin has mentioned that the Blackout issue should be coming up in the next pimax update notice being sent out and that they’re investigating it.

Also, Gary T messaged me earlier and said he took off his GPU overclock and was able to run a full session in iRacing at 90hz without a blackout, whereas previously at 90hz he was getting constant blackouts happening and was only able to use 75hz safely…

Looks like we’re getting closer to the issue at hand possibly and i THINK the brightness slider may have been trying to push too much current through an already overclocked gpu on my behalf, and that was causing the random blackouts for me also…

4 days (about 10hrs) later - so far so good.

2 Likes

Do you know if any of these users having blackouts have Factory Overclocked cards?

Well Ive been posting my results everywhere so hopefully others that have these blackouts are reading it and they can try what I’ve done to experiment for themselves. I know only Gary Tall reported back to me and said he turned off his overclock and yesterday it ran fine at 90hz, which didnt work for him before without at least a blackout happening.

1 Like

@PimaxUSA @Heliosurge - i just had a blackout again. No good. I also had a blue screen mid-practice. Today steamVR beta updated so im going to the main steamVR branch and see if that helps next.

1 Like

@chiagod have you had any of these experiences? Just curious as your reddit post looked like it said is working on some amd gpus. If so and your not getting blackouts; might be an Nvidia related issue.

This is a slow and painful process because I never know when it’ll occur…
I went with SteamVR main branch now to see if that helps. If it happens again, the only step i have to try is nvidia driver 461.33 and if it happens again, ill update to the newest driver and go back to 75hz and see if it happens with 75hz again as well.

1 Like

Yeah this bug really needs to be resolved.

I started to turn on logging but it didnt happen after… So i just have to keep remembering to turn on the pitool logging to see if it catches anything when it happens.

1 Like

I set the brightness to default, and it happened the next time I used the headset… Haven’t turned off the light OC yet. That’ll be the next thing I try.

1 Like

Well i thought brightness and/or the OC on the GPU worked for me but 4 days later i got a blackout. So i dont know any more. Will be trying driver updates and logging as i mentioned to see if i can find anything else out.

1 Like

So far I’ve changed SteamVR to the regular branch instead of using SteamVR Beta… 3 days so far and no blackouts… No other changes made so we’ll see if this change has any effect on the blackouts.

My next step would be the nvidia drivers if it happens again I’ll be going up to 461.33 from 461.09 - that’s when Nvidia created a hotfix for SteamVR but no gpu monitoring apps are allowed to run with 461.33 or the newer drivers. At 461.33 I am still able to test with 90hz but if it happens on that one, I’ll upgrade to the newest drivers which i believe is 465.89 and go back down to 75hz and continue testing… unless someone at pimax figures out the root cause it’ll be a slow and painstaking process for me but i’m also trying to turn on the pitool logging each time i run (assuming i dont forget to do it each time).

i Will report back any findings…

3 Likes