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

Medium crash on start [solved] !!!

CptnjarheadCptnjarhead Posts: 13
NerveGear
edited January 1 in Oculus Medium
Event log:
Faulting application name: OculusMedium.exe, version: 0.0.0.0, time stamp: 0x5a039de0
Faulting module name: ucrtbase.dll, version: 10.0.16299.98, time stamp: 0x70f70cc4
Exception code: 0xc0000409
Fault offset: 0x000000000006b70e
Faulting process id: 0x4fc
Faulting application start time: 0x01d36d6a0b5d2cbd
Faulting application path: C:\Program Files (x86)\Oculus\Software\Software\oculus-oculus-medium-retail\bin\OculusMedium.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 80c0cec6-8f95-4baa-a3cf-40b8f814fc3f
Faulting package full name:
Faulting package-relative application ID: 

I have latest NVidia drivers
windows 10 home
everything else works... games quill.. just not medium.

Answers

  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    I have reinstalled... same thing. 
  • MattHickmanMattHickman Posts: 359 Oculus Staff
    Could you post the Medium specific log found at: C:\Users\*username*\AppData\LocalLow\Oculus\Medium\log
    Are you a new user or previously using medium and an update broke for you? 

    Please also try ensuring you don't have GPU tuners or anything like that running and all ad/malware scanners are turned off. Attempting to boot disconnected from the internet also usually works for working around the malware scanners.

  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    ok, i will post the medium log. I just did a clean install of windows 10... already tried disabling avast, and i dont have any gpu tuners running. I will try rebooting without internet. I'm a new user. Thank you for the response.
  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    1 file in C:\Users\*username*\AppData\LocalLow\Oculus\Medium\. Oculus_Medium.log - here are the contents:

    12/06/17 21:02:33 [I]: C:\Program Files (x86)\Oculus\Software\Software\oculus-oculus-medium-retail\bin\OculusMedium.exe startup:
  • MattHickmanMattHickman Posts: 359 Oculus Staff
    Is that the entire contents of the medium log? 

    Do you happen to be running on ReVive? 

    If not could you also post your dxdiag so we can see if perhaps it's hardware related?
  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    that is all i can see of the log when i open it. I thought that was strange. I dont know what ReVive is.. so that would be a no. Sure. will post this weekend. I appreciate your help. Thank you.
  • MattHickmanMattHickman Posts: 359 Oculus Staff
    We have some folks that use an HTC Vive and there's a program that lets you spoof Oculus into thinking it's a Rift called ReVive and everytime we update our app it breaks Revive and we get a bunch of crash complaints :) 

    We'll keep digging. Another helpful thing for us is if you record the time/timezone of a crash sometimes we can pull info from our online crash reporting system, but if it's not even writing things to the log it's not getting very far into the boot sequence.
  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    System Information
    ------------------
          Time of this report: 12/9/2017, 07:02:40
                 Machine name: DAMON-VR-PC
                   Machine Id: {0B4B0A6F-676A-404A-BE16-489EC5529311}
             Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
                     Language: English (Regional Setting: English)
          System Manufacturer: System manufacturer
                 System Model: System Product Name
                         BIOS: BIOS Date: 03/08/11 10:42:32 Ver: 08.00.15
                    Processor: AMD Phenom(tm) II X6 1100T Processor (6 CPUs), ~3.3GHz
                       Memory: 12288MB RAM
          Available OS Memory: 12278MB RAM
                    Page File: 6727MB used, 7407MB available
                  Windows Dir: C:\WINDOWS
              DirectX Version: DirectX 12
          DX Setup Parameters: Not found
             User DPI Setting: 96 DPI (100 percent)
           System DPI Setting: 96 DPI (100 percent)
              DWM DPI Scaling: Disabled
                     Miracast: Available, with HDCP
    Microsoft Graphics Hybrid: Not Supported
               DxDiag Version: 10.00.16299.0015 64bit Unicode


  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    [Deleted]
  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    [Deleted]
  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    [Deleted]
  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    [Deleted]
       


  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    [Deleted]


  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    edited January 1
    [Deleted]


  • CptnjarheadCptnjarhead Posts: 13
    NerveGear
    We have some folks that use an HTC Vive and there's a program that lets you spoof Oculus into thinking it's a Rift called ReVive and everytime we update our app it breaks Revive and we get a bunch of crash complaints :) 

    We'll keep digging. Another helpful thing for us is if you record the time/timezone of a crash sometimes we can pull info from our online crash reporting system, but if it's not even writing things to the log it's not getting very far into the boot sequence.

    so.. as it turns out.. my problem was the AMD 1100t CPU.. lack of SSE 4.x instruction I would guess. Found a mother board and cpu combo on ebay.. FX 8350 reinstalled windows and BAM!.. works like a charm. I did have to use an older version of the oculus software to make it work on the 1100t so... There was a warning about hardware not being supported. Thanks for the help. Love my Rift.. and Medium is Amazing!
Sign In or Register to comment.