Rift S issue - frequent position resetting

Game mode causes people problems in normal games too, so switching it off is definitely worth a try.

Good luck!! :)

Why don't we all get told about stuff like this?
Either from MS (who ought to know about stuff like this because they own the carbuncle of software, which has turned from a "reasonable" OS into an Apple-style Malware environment!)…
Or from gaming and software developers? In this case it could be any or all of: Frontier Developments (Elite Dangerous developer/publisher - with native/in-house VR support); AMD (graphics card supplier and publisher/owner of Radeon Wattman software); Oculus (VR third party supplier and VR/driver software owner).

Or even from knowledgeable PC suppliers?

Any one of the above could take a bit of ownership and spread the word. Instead, I found this tiny nugget in a single small thread a game forum!
 
Because in scheme of things the Game bar problem doesn't affect many people.

As for your other suggestions, that's partly my fault, you see turning off any overclock is a well known troubleshooting step. It should have been one of the first things I told you. Playing games will eventually show up an unstable overclock.
 
Because in scheme of things the Game bar problem doesn't affect many people.

As for your other suggestions, that's partly my fault, you see turning off any overclock is a well known troubleshooting step. It should have been one of the first things I told you. Playing games will eventually show up an unstable overclock.

Definitely not your fault, matey.

I've completed a fair test now with memory speed up to 900 again. No shutdown. No uncontrolled overheating of GPU components. The only significant change being the switch of Win 10 Game Mode to off.

Multiple visits to the docked station interface board and temps stabilise at around 68degC, where prior to the switch it was 80 and increasing rapidly.
I'd say that was a software environment problem - not a Wattman overclocking problem. Something in the OS creating a conflict with game code or Oculus VR code... not an unstable overclock, particularly since absolutely everything else took the profile and worked it with stability.

Of course, there is the possibility that it isn't the Game Mode switch change, but something else entirely that has changed in the background that is responsible for the recent lack of shutdowns, but for me, Win 10 Game Mode still looking like the prime suspect.

I'll keep up with further updates as I build up the Wattman profile again to what it was before.

I was also beginning to suspect a PSU issue with my 600W 80+Bronze, but happy that it might not be that, either
 
I've completed a fair test now with memory speed up to 900 again. No shutdown. No uncontrolled overheating of GPU components. The only significant change being the switch of Win 10 Game Mode to off.

I was also beginning to suspect a PSU issue with my 600W 80+Bronze, but happy that it might not be that, either

I think you have it sorted. It is unusual to see the game bar cause that big jump in performance. I wonder what caused it?

It's always a relief to find out that you don't have to replace any hardware.

How is the Vega 56 handling VR?
 
I think you have it sorted. It is unusual to see the game bar cause that big jump in performance. I wonder what caused it?

It's always a relief to find out that you don't have to replace any hardware.

How is the Vega 56 handling VR?


VR with Vega 56 is lovely.
Graphics settings in Elite Dangerous are not very special, and not as high as I'd expected after using a friends CV1 on a Ryzen3 1600/Vega 56 combination, who runs much higher settings, but I guess the Rift S higher resolution pegs things back a little for the same smoothness.

I'm planning to upgrade to RX5700XT Nitro+ around Black Friday/Cyber Monday, when I would expect VR to go from "lovely" to "VERY lovely".
 
Turns out OCUK built ny PC with an 850W PSU.

Well done to OCUK.

Sadly, all the steps I'd taken above still didn't solve my issue of shutdowns...

I was forming the conclusion that it was a power issue, anyway, since the computer simply shuts down, without writing any debug information, etc... Which is looking more and more like a power supply issue - and the computer not being served enough wattage, so falls of the cliff and shuts down. No reboot. No simple software crash. Nothing but a hard power down.

So I got into the case and checked the PSU was indeed the 850W that OCUK said they'd put in my build. Of course it was. (Kolink 80+Bronze modular.)

While I was in the case I started to get a bit suspicious of the single power cable feeding both power ports of the Veg 56. One of those cables with 2 power sockets on the end, but power coming from the one cable. I noted there was an available PCIE 8pin socket on the PSU. Which gave me an inkling of an idea. I got the PC boxes out of the loft and had a rummage around for power cables. Sure enough, there's an 8pin PCIE power lead. (Again, with 2 sockets on one end...) Did a bit of cable re-routing and installed the extra cable...

And now I've got the Vega 56 supplied by 2 discrete power cables.

After a bit of digging on t'internet I discovered that the 8 pin PCIE "standard" is to support 150W power draw. This added to my loose suspicions about it being a power supply issue?

A little bit of testing so far.
With standard default settings in Wattman - Played the game that was suffering shutdowns and went to the parts where shutdowns were most prevalent. No shutdowns so far. Max power draw reported by Radeon and HWMonitor software (both coherent) was 180W.
Decided to then push a bit by placing the power slider in Wattman up to max (+50%).
Max reported power draw 232W. No shutdowns so far.
Added a custom fan profile to Wattman, to keep the temperatures a little bit more in check. Nothing very aggressive, just to take the edge off the 70deg GPU and 76 VDDC VR maximums noted so far at sustained 180-200W+ power draw.
That didn't promote any instant shutdowns either.
Final stage so far has been to increase the memory speed to 850MHz.
No shutdowns after a couple of attempts at the high-stress environment for a couple of minutes.

So this time I'm tentatively hopeful that in providing a two cable power supply I might be on to something?

Hopeful.
 
sounds like you may have sorted it, but i had the resetting issue using the rift s, where i'd get a grey out/ wash out and then it would reset. I did some profiling and found out my cpu was bottle necking, was running an i3 81000 and upgraded to i5 9400f and have not had any problems since
 
sounds like you may have sorted it, but i had the resetting issue using the rift s, where i'd get a grey out/ wash out and then it would reset. I did some profiling and found out my cpu was bottle necking, was running an i3 81000 and upgraded to i5 9400f and have not had any problems since

Thanks

I'm still not sure it's sorted. Had another shutdown this morning, in exactly the same place in the game that has caused these issues. Seems less prevalent, but still not there yet...

The trial continues.
 
Thanks

I'm still not sure it's sorted. Had another shutdown this morning, in exactly the same place in the game that has caused these issues. Seems less prevalent, but still not there yet...

The trial continues.

You need to go back to running everything at stock and then work from there. Have you tried playing the game in Pancake mode to see if it crashes?
 
:D:D Sorry dude!! It's a term that has come in since the arrival of VR. It means normal gaming on a monitor. You know on the flatscreen? Flat = Pancake :p

HaHa lol yes. Apologies for being slow on the uptake.

I haven't tried this particular game in pancake mode, but yesterday tried the pancake game Shadow of War, and you guessed it - it performed shutdowns. Twice. Not long after starting into the game. Everything is set to defaults.

Today's endeavour did the following:

CCleaner - full registry clean out.

Sought out AMD Ryzen chipset drivers - my god they're not easy to find on the internet and no way could I find them on AMD sites. Eventually discovered the install files on guru3D. All installed. Tried the Rift game. Accessed the particular area that is prevalent of shutdowns - with the HMD perched on the top of my head so I could monitor the pancake projection and HWMonitor and Radeon monitor all at the same time. Whereas previously this game selection had the GPU drawing over 170Watts of power (up to max 181/182Watts in default trims) this time it was drawing a lot less power - between 80 and 130 Watts on average...

I've also used some powershell commands to check my windows system files and all appears fine.
 
Still having shutdown issues - and every time it's associated with high levels of system power draw during gaming.

Can't even run fully though the Benchmark in Shadow of War - got a shutdown just as frame rate dropped from initial numbers of 120fps down through 90-ish, indicating that it's in the high-GPU-load scenes at the end of the benchmark that's causing the hard shutdown. No BSOD and no restart - just a simple abrupt power-down.

So today I bit the bullet and contacted OCUK for an RMA. It gets picked up on Tue next week.

Because it is hard shutdowns I'm experiencing, it really all points toward a failing PSU that isn't able to deliver the required power to the system. It might not be that, but that's gotta be the prime contender. It may well be some other component, such as GPU itself or even MB or CPU, but at least it's going back for a proper tech inspection.

Fingers crossed it's something simples.
 
Sorry for the late reply, I wasn't around yesterday.

You are returning the PSU?

I hope it's faulty!! It would be great to finally get a resolution for your shutdown problem.
 
News update

I've installed a new Corsair 850W PSU in the PC.

It *appears* to be playing high stress games without shutting down...

So now I have a quandary about what to do with the RMA to OCUK.
Do I reinstall the original goosed PSU and send it back in toto for them to diagnose the issue?
Do I send just the removed PSU back and ask them to check that it's goosed and let me know what their desired course of action is?

I'll give them a call on Monday to find out their preference.

Meanwhile - I'll give the new PSU a good workout tomorrow to see if it will keep the PC from shutting down.


Thanks for the support, chaps. Appreciate it
 
I grow more and more confident that the new PSU has totally resolved all the problems I was experiencing with (my system) mainly manifested by problems with the Rift S.

OCUK have been brilliant with me and worth a hearty thank you and congratulations.


When I called on Monday (the day prior to the pre-arranged RMA collection...) and said that I'd identified the problem by purchasing and fitting a new Corsair RM850 PSU, they listened to my story, thought about how to resolve it and came back with their plant to:

1. Send a Corsair RM850, so I could return the one I had for a refund ;)
2. Wouldn't take the difference in price to upgrade to more expensive 80+ Gold PSU (difference I offered to pay was equal to the price difference on their wbsite = £25).
3. Not interested in taking the old PSU back for testing to ensure I was correct, or even just telling the truth.

I got the new PSU the next day - and the package included some free Haribo.


Altogether, and amazing Customer Care response by OCUK - I am very grateful.
 
Fair dues to Overclockers support. They really do go that extra mile.

I hope that's the issue solved once and for all. :)

Thanks for all the help, dude. Certainly hope so too. At first glance it's looking very, very positive. Got a bit of WattMan 950MHz memory overclock going on with the Vega56, 50% extra power enabled, custom fan (with auto stop) and a tad of undervolt on the GPU. Giving it some serious gaming stress and WattMan reports max power draw spikes of over 250Watts, with sustained draws of 220W. Nothing else has been changed since it kept shutting down. Couldn't even run the Shadow of War Benchmark beforehand, and now I'm gaming for good length of time and no sign of shutdowns.
Time will tell whether this PSU is robust enough - if not, I'm guessing it might be something going on with my system that's causing PSUs to expire quickly.
 
Back
Top Bottom