XR VR version, freezing (specially when undocking from station or dropping off warp

Ask here if you experience technical problems with X Rebirth.

Moderator: Moderators for English X Forum

Post Reply
User avatar
juanitierno
Posts: 435
Joined: Fri, 28. Dec 07, 18:06

XR VR version, freezing (specially when undocking from station or dropping off warp

Post by juanitierno » Sat, 17. Mar 18, 17:20

Version and language (e.g. 1.1 English, etc.).
Current VR version on steam, no "betas", english.

Whether or not your game is modified using any third party scripts or mods (see note below).
Nothing at all.

Type of game played (Campaign, Free Play etc.).
The first campaign (tutorial rebuild the ship one).

Exact nature of the problem, where and when it occurs and what you were doing at the time.
Playing in VR, leaving a station sometimes (about 60% of the time) freezes the screen, the freeze looks like rapidly blinking frozen frame.

Any possibly relevant changes you have made to your game, system, or software before the issue occurred.
I purchased last week, and started playing yesterday.
I'm launching through steam with the "start in oculus mode" as I have a rift.

Where appropriate, additional symptoms, error messages, links to screenshots and crash dump files (see this FAQ entry).
Nothing, the game freezes and I have to shut it down. If it's saving a log somewhere let me know.

Your system specifications in the form of a DXDiag report (see this FAQ entry).
https://pastebin.com/swCUWHWq

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 18308
Joined: Fri, 16. Apr 04, 19:21

Post by Alan Phipps » Sat, 17. Mar 18, 18:54

Pretty much as seen for the OP in that other thread you posted in, you do not have a WHQL-approved Oculus driver for Win10 and you have a few different sound devices and drivers on the go at the same time (some are outdated and Microsoft default sound drivers instead of the latest RealTek HD Audio Codec for your RealTek sound chipset). My comments for the OP in that thread.

You have not included the Windows Error Reports normally found at the end of your DxDiag and so I cannot see if it is indeed the Oculus driver or specific .dlls that are crashing.
A dog has a master; a cat has domestic staff.

User avatar
juanitierno
Posts: 435
Joined: Fri, 28. Dec 07, 18:06

Post by juanitierno » Sat, 17. Mar 18, 19:05

I will disable sound devices I don't use and re-test.

But how do I solve the oculus drivers thing? I'm using the oculus app that auto-updates.

I'm using the oculus home 2.0, does using the old version help with the WHQL thing?

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 18308
Joined: Fri, 16. Apr 04, 19:21

Post by Alan Phipps » Sat, 17. Mar 18, 19:18

Hi. I don't know as I am not an Oculus user.

What WHQL means is that Microsoft have tested a 3rd party driver and found it suitable for use with the relevant current version of Windows. Being non-WHQL does not mean that it won't work, only that Microsoft do not currently say that it should.

It would be good to see the Windows Error Reports part of the DxDiag to see if you are having the same problem as in the other thread.
A dog has a master; a cat has domestic staff.

User avatar
juanitierno
Posts: 435
Joined: Fri, 28. Dec 07, 18:06

Post by juanitierno » Sat, 17. Mar 18, 21:33

This is the error part (edited out the name of 3 exe's I rather don't want in a post with my real name on):


---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 144
P2: 3003
P3: ffff81098d15d808
P4: 40010000
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:


+++ WER1 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 144
P2: 3003
P3: ffff81098d15d808
P4: 40010000
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:


+++ WER2 +++:
Fault bucket 2075905804776857028, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: vrmonitor.exe
P2: 1.0.0.1
P3: 5a7e4c5e
P4: b9fc
P5: 67246080
P6:
P7:
P8:
P9:
P10:


+++ WER3 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: vrmonitor.exe
P2: 1.0.0.1
P3: 5a7e4c5e
P4: b9fc
P5: 67246080
P6:
P7:
P8:
P9:
P10:


+++ WER4 +++:
Fault bucket 1496277489265899760, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: [REDACTED].exe
P2: 4.6.2.61182
P3: 54c682bc
P4: d3d11.dll_unloaded
P5: 10.0.16299.248
P6: 8a2cd8de
P7: c00001a5
P8: 00093f70
P9:
P10:


+++ WER5 +++:
Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:
P1: [REDACTED].exe
P2: 4.6.2.61182
P3: 54c682bc
P4: unknown
P5: unknown
P6: unknown
P7: unknown
P8:
P9:
P10:


+++ WER6 +++:
Fault bucket 1675510033616301779, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: vrserver.exe
P2: 1.0.0.1
P3: 5a7e4bd9
P4: LibOVRRT64_1.dll
P5: 1.24.0.0
P6: 5aa095f8
P7: c0000005
P8: 0000000000079908
P9:
P10:


+++ WER7 +++:
Fault bucket 129596176638, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: [REDACTED].exe
P2: 5.4.1.40776
P3: 10.0.16299.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER8 +++:
Fault bucket 129577324485, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: BearIsland.exe
P2: 5.4.4.55940
P3: 10.0.16299.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER9 +++:
Fault bucket 1256307128621898961, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.248
P2: 800f081f
P3: 9B396D0C-210F-4DB6-A48A-2CE49F6DEBB8
P4: Install
P5: 1
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 18308
Joined: Fri, 16. Apr 04, 19:21

Post by Alan Phipps » Sun, 18. Mar 18, 00:24

The only errors you have in common with the previous thread OP are the LiveKernelEvent errors, but with slightly different parameters (144 rather than 117). These usually happen when issues with hardware devices on your system and/or their drivers stop Windows from working safely.

You also have AppHang errors with vrmonitor.exe and an APPCRASH error with vrserver.exe - I expect those are your XRVR freezes/crash. These are *probably* due to your graphics driver and/or Oculus driver having issues when playing XRVR. Any changes/updates you can try with those two drivers may help to isolate the issue.

You don't have quite the same issue as the previous OP's thread which was reporting errors specifically relating to Oculus and sometimes a particular Windows .dll.
A dog has a master; a cat has domestic staff.

User avatar
juanitierno
Posts: 435
Joined: Fri, 28. Dec 07, 18:06

Post by juanitierno » Sun, 18. Mar 18, 16:48

Thanks for looking into it!

I disabled unused audio devices (left the 2 I use, the rift and the "high definition audio"). I managed to play yesterday like 3 hours and had no crashes, I thought it was solved, but 5 mins ago I crashed again leaving a station (same freeze thing, just as the cockpit scene is fading in).

This is my current errors part of the dxdiag, seems windows is having some issues updating :P

I'm not sure if the vrserver.exe errors are the most recent or the oldest (don't know how they are ordered on the list)


---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1256307128621898961, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.248
P2: 800f081f
P3: 9B396D0C-210F-4DB6-A48A-2CE49F6DEBB8
P4: Install
P5: 1
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0


+++ WER1 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.248
P2: 800f081f
P3: 9B396D0C-210F-4DB6-A48A-2CE49F6DEBB8
P4: Install
P5: 1
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0


+++ WER2 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.248
P2: 800f081f
P3: 9B396D0C-210F-4DB6-A48A-2CE49F6DEBB8
P4: Install
P5: 1
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0


+++ WER3 +++:
Fault bucket 2244041626960407138, type 5
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.245
P2: Package_for_KB4090914
P3: 16299.251.1.0
P4: amd64
P5: unknown
P6: 800f081f
P7: Stage
P8: Resolved
P9: Staged
P10: UpdateAgentLCU


+++ WER4 +++:
Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.245
P2: Package_for_KB4090914
P3: 16299.251.1.0
P4: amd64
P5: unknown
P6: 800f081f
P7: Stage
P8: Resolved
P9: Staged
P10: UpdateAgentLCU


+++ WER5 +++:
Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.245
P2: Package_for_KB4090914
P3: 16299.251.1.0
P4: amd64
P5: unknown
P6: 800f081f
P7: Stage
P8: Resolved
P9: Staged
P10: UpdateAgentLCU


+++ WER6 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 144
P2: 3003
P3: ffff81098d15d808
P4: 40010000
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:


+++ WER7 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 144
P2: 3003
P3: ffff81098d15d808
P4: 40010000
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:


+++ WER8 +++:
Fault bucket 2075905804776857028, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: vrmonitor.exe
P2: 1.0.0.1
P3: 5a7e4c5e
P4: b9fc
P5: 67246080
P6:
P7:
P8:
P9:
P10:


+++ WER9 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: vrmonitor.exe
P2: 1.0.0.1
P3: 5a7e4c5e
P4: b9fc
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 18308
Joined: Fri, 16. Apr 04, 19:21

Post by Alan Phipps » Sun, 18. Mar 18, 19:50

WER 1 to 5 at the top just above are the only new errors being reported and are probably nothing to do with your VR issue. Your very latest freeze wasn't listed as an APPHANG error this time as it may have been terminated by you before Windows decided.

There's no new useful information there unfortunately. Did you try any graphics and Oculus driver changes as I suggested - newer or older versions? (I *think* one of those drivers will be where the actual problem originates.)
A dog has a master; a cat has domestic staff.

User avatar
juanitierno
Posts: 435
Joined: Fri, 28. Dec 07, 18:06

Post by juanitierno » Sun, 18. Mar 18, 20:14

Will look into it!

On the oculus side the only thing I can change is the version of the "home" app, that I assume comes with the drivers, it's a HUGE downgrade in functionality tho.

On the nvidia side, I am using an older version because newer versions don't play nice with the Rift, I heard nvidia is fixing the issue, but the fixed driver is not released yet.

Will try the oculus thing and see if it helps, if it still crashes at least I can rule out the oculus driver itself.

Thank you!

Post Reply

Return to “X Rebirth - Technical Support”