8KX and Nvidia drivers issue

I posted a reply before but it got lost with the forum restore. I recently dusted off my 8KX and installed new Nvidia drivers (currently on 591.59 from 18th Dec), and not having any issues.

Could be build related I guess? My 8KX is 2075xxxxxx. 2080 Ti.

2 Likes

Might also be related to your GPU series architecture as well.

1 Like

I wish this can be fixed by next week, but still no progress.

Not sure what the point of facepalming me is, I’m simply relating my experience and as much info as possible may help to pinpoint the issue for you :wink:

It goes to show it’s not simply a “universal 8KX + latest Nvidia driver” issue, and it’s also not universal to a particular GPU series, reading previous posts.

1 Like

Indeed AMD after the r9 series GPUs architectural changes also messed up VR support in the Rx 400, &500 series and the vega series for the longest time.

So to be expected that the green team will have issues created like some of the 10serues models that were not actually VR compatible/ready, the 12v amp requirement in later GPUs where a 1000w was a no-go but a 650w was working due to snow on the 12v rail. Then the 3090ti issues requiring a repeater for high res headsets, the the melting power connector.

The good with older GPUs is that the architecture have mature driver support as the kinks have been worked out long ago

1 Like

Hi everyone, and happy new year. I can confirm that, at least, in my case, the issue was my 4080. I say “was” because i’ve changed the 4080 for the 5080 (selling the first one), and the issue there isn’t anymore. Not the ideal solution, i was hoping for a fix, but i want to enjoy and use my 8KX, and this is the only immediate solution available for me. I’m still looking and hoping for a driver solution.

Happy new year Pimax team and community.

Diego

2 Likes

Interesting. Seems Nvidia must have made some progress as iirc there are folks with 5000 series GPUs having issues as well.

yeah, but the only solution for me is the 5090 as i have a 4090.
Not downgrading just to use 1 headset(getting a 5080).
let alone pay the same $$ i paid for a 4090 for a 5080 2 years ago. :confused:

its insane on what they’re asking for a 5090 for 11-18 more FPS.
i usually skip gens anyways.

So my next card will prob be a 6090(if its priced correctly… prob wont)
then this 4090 will go to my wifes PC.

we will see next few years.

Yesterday I upgraded to a new PC with 9800X3D, 5090 etc. Can confirm my 8KX is running fine with latest Nvidia drivers 591.74 released on 5th Jan.

1 Like

Looks like the main issue is that the 8KX crashes during initialization with NVIDIA drivers newer than 566**, which** seems to affect a lot of users. I just came across a tool called the bottleneck calculator on mypcbottleneck.com that might help a bit by checking if your CPU, GPU, or RAM could be contributing to issues when using newer drivers.

Hope it provides some insight for anyone still running into this!

1 Like

i have a 9950X3D, 32GB DDR5 8000mhz cl36, ASUS 4090 TUF OC and a 4TB gen 4 nvme drive, W11 25h2.

have the same issue, even on my 10900k build.
new os does not matter.

its a 2076 8kx version with 3XXX and 4XXX Cards from everyone complaining.

2 Likes

There’s been progress and an update from the Nvidia team. They’ve started pinpointing the protocol and driver issues and are now debugging them.

4 Likes

That’s awesome to hear! :slight_smile:

1 Like

Do you have any updates?

(post deleted by author)

Is there any update on the progress?

Thanks.

1 Like

PSA! Disable onboard graphics/video in BIOS. This resolves the problem.

I upgraded my rig to a Ryzen 9800X3D and my 8KX wasn’t recognized in PiPlay. Since I was coming from a 13900KF which doesn’t have integrated graphics I thought maybe that was the issue.

And voila! Enjoy.

Wrong message board???

everyone that uses AMD needs to have IGPU disabled or pimax has issues.
(in fact any built in GPU from CPU needs to be disabled in bios)

had to do that for 5K to stop inf boot.

I’ll need to check with the dev team again, as the last update I received was that the NVIDIA team had started debugging the issue.