techsupport

2455 readers

5 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 1 year ago

MODERATORS

[email protected]

Oculus PC app setup crashes before launching, making installation impossible (lemm.ee)

submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

(Event log details at the end) Trying to run OculusSetup.exe from the Meta website seems to be impossible on my home PC, as the installer hard crashes before any UI is even shown.

As expected, Meta support is completely and utterly fucking worthless. All they know how to do is email you the basic instructions already on their worthless ass website.

I am running Windows 10 x64 Home, and can be bothered to provide further tech specs if someone provides a specific reason for needing them. I also have Avast AV installed, but completely uninstalling and rebooting made absolutely no difference in outcome or error output.

No, I am not open to reinstalling Windows.

Running the installer results in 3 administrative error events :

.NET Runtime

spoiler

Log Name: Application Source: .NET Runtime Date: 7/2/2024 2:26:29 AM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ---- Description: Application: OculusSetup.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArithmeticException

Exception Info: System.OverflowException at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation() at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(System.Windows.Media.Imaging.BitmapSource, System.Windows.Media.ColorContext, System.Windows.Media.ColorContext, System.Windows.Media.PixelFormat) at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation() at System.Windows.Media.Imaging.BitmapImage.EndInit() at System.Windows.Media.Imaging.BitmapImage..ctor(System.Uri, System.Net.Cache.RequestCachePolicy) at Daybreak.Gooey.SleekImage..ctor(System.Uri) at Dawn.Gooey.DawnWindow.OnLoaded(System.Object, System.Windows.RoutedEventArgs) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs) at System.Windows.BroadcastEventHelper.BroadcastEvent(System.Windows.DependencyObject, System.Windows.RoutedEvent) at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(System.Object) at MS.Internal.LoadedOrUnloadedOperation.DoWork() at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Media.MediaContext.Resize(System.Windows.Media.ICompositionTarget) at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Event Xml: 1026 0 2 0 0 0x80000000000000 79576 Application ---- Application: OculusSetup.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArithmeticException

Application Error 1

spoiler spoiler Log Name: Application Source: Application Error Date: 7/2/2024 2:26:29 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: ---- Description: Faulting application name: OculusSetup.exe, version: 1.97.0.0, time stamp: 0x6632b1c5 Faulting module name: KERNELBASE.dll, version: 10.0.19041.4597, time stamp: 0xe77e2ab7 Exception code: 0xe0434352 Fault offset: 0x00140b92 Faulting process id: 0x2e28 Faulting application start time: 0x01dacc597bd3d92d Faulting application path: C:\Users---\AppData\Local\Temp\OculusSetup-4a1e1d83-cbde-43f4-b781-b2517c0be2a3\OculusSetup.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 2d236814-9329-4595-a463-331f921c2a4c Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 0 2 100 0 0x80000000000000 79577 Application ---- OculusSetup.exe 1.97.0.0 6632b1c5 KERNELBASE.dll 10.0.19041.4597 e77e2ab7 e0434352 00140b92 2e28 01dacc597bd3d92d C:\Users---\AppData\Local\Temp\OculusSetup-4a1e1d83-cbde-43f4-b781-b2517c0be2a3\OculusSetup.exe C:\WINDOWS\System32\KERNELBASE.dll 2d236814-9329-4595-a463-331f921c2a4c :::

Application Error 2

spoiler

Log Name: Application Source: Application Error Date: 7/2/2024 2:26:33 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: ---- Description: Faulting application name: OculusSetup.exe, version: 1.97.0.0, time stamp: 0x6632b1c5 Faulting module name: KERNELBASE.dll, version: 10.0.19041.4597, time stamp: 0xe77e2ab7 Exception code: 0xc000041d Fault offset: 0x00140b92 Faulting process id: 0x2e28 Faulting application start time: 0x01dacc597bd3d92d Faulting application path: C:\Users---\AppData\Local\Temp\OculusSetup-4a1e1d83-cbde-43f4-b781-b2517c0be2a3\OculusSetup.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: e9a29fe3-f6d3-4e50-afa8-56100a08f8e7 Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 0 2 100 0 0x80000000000000 79580 Application ---- OculusSetup.exe 1.97.0.0 6632b1c5 KERNELBASE.dll 10.0.19041.4597 e77e2ab7 c000041d 00140b92 2e28 01dacc597bd3d92d C:\Users---\AppData\Local\Temp\OculusSetup-4a1e1d83-cbde-43f4-b781-b2517c0be2a3\OculusSetup.exe C:\WINDOWS\System32\KERNELBASE.dll e9a29fe3-f6d3-4e50-afa8-56100a08f8e7

PS, if the only thing you can think of is "HURR JUST WIPE YOUR DRIVE AND DO A CLEAN OS INSTALL", fuck yourself with a pitchfork or I'll fucking find you and do it myself. That's reddit shit and you know it

UPDATE I'm seeing a lot of references to KERNELBASE.dll, as well as some kind of image drawing/color issue that I don't understand. If anyone has any ideas about those, I'd appreciate it

UPDATE 2 Found a log from the Oculus app its self in my appdata. Main take away so far is this line:

"System.OverflowException: The image data generated an overflow during processing. ---> System.ArithmeticException: Overflow or underflow in the arithmetic operation".

I remember looking up an exception code earlier and something came up about trying to divide by zero. Anyone have a clue here? It almost sounds to me like the Meta people just can't fucking code to save their lives (or careers, which I'm not to confident in right now).

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 4 months ago (1 children)

From the first message it sounds like it tries to load some image before it collapses. Do you have some strange color correction, monitor settings, night light? Multiple or external gpus? Variable or 60+ framerate?

Update your gpu drivers, unplug all monitors except the main one, reset any graphic related windows and driver settings youchanged to default.

[–] [email protected] 1 points 4 months ago* (last edited 4 months ago)

Interesting idea, I'm running dual monitors and higher than 60 fps on one of them only. That monitor also has g-sync and some other nvidia gimmicks, but as far as I know I don't have any of them enabled. I also keep drivers updated religiously, so we can check that box.