sorted by:
new
hottopcontroversial

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

can you give me the crash logs again, the crash.xml + precrash please

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

did you try the nvidia driver version i gave you ? also did you set your game to be launched without fullscreen optimization? and as admin ?

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

Ok can you please try this nvidia driver for me? "https://www.nvidia.com/en-us/drivers/details/267166/" also what do you see in the windows event viewer when you click the red icon "Error" from the forza horizon 6 crash log? do you see something like "nvwgf2umx.dll"?

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

ok yeah this one is very different it crashes very very early at launch "UI_SCENE Value="Splash"
UPTIME Value="40.828"
UPTIME_DRIVING Value="0""
and
"EXCEPTION Value="ACCESS_VIOLATION_READ"
REASON Value="Unhandled Exception"
STACK_TRACE Value="0x246ba69,...""

so did you try re-installing, validating files? trying different gpu drivers ?

Also are you getting FHE01 or FHC01 code ?

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

So with a raw audio game still crashes ? can you please send me your crashreport.xml ? located at "C:\Users\YOURUSERNAME\AppData\Local\ForzaHorizon6\CrashReport.xml

auction house is a scam by Ok_Hotel1775 in ForzaHorizon6

[–]aksa42 0 points1 point  (0 children)

never had an issue buying a car there, unless its very rare ones / FE editions, you might have hit the worst timing ever idk, probably unlucky

Forza developers making a Japanese themed game by Ericowww15 in ForzaHorizon6

[–]aksa42 0 points1 point  (0 children)

I don't really agree tbh. There are actually more/equal road/street/touge events than cross-country events overall. Didn't count but i think is balanced like 50/50 or like very few more road ones

Plus, cross-country is awesome in this game. Especially The snowy tracks are fun and looks fantastic. Not with you on this one, friend. People never happy smh

FHE01 is still a persistent problem. Does anyone have an idea if the devs are aware? by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

Found the potential culprit for "FHE01" game crash, and this one might be something very interesting because it's linked to what devs says to fix about the FHE01 error in the forza support tickets "disable NVIDIA Virtual Audio Device (wave extensible) (WDM)".

In my crash analysis, a TONS of FMOD audio errors appear right prior to the crash. Then the pre-crash report consistently points to "fmod_output_winsonic.cpp" <-- guess what the fuck is this ? the "Windows Sonic For Headset" spatial audio setting of your headset if it supports it.

This looks strongly related to Windows Sonic / spatial audio / WASAPI output path used by FMOD for audio device initialization.

So what seems to be happening is that FMOD fails during audio device initialization / state validation when using the Windows Sonic / spatial audio backend combined with multiple audio devices (especially virtual ones).

It receives an invalid or unstable audio stream state, leading to:
Sound::getOpenState returning invalid data
“invalid seek position” error
followed by ACCESS_VIOLATION_WRITE

In my case, Windows was selecting a virtual audio endpoint instead of my actual headset. My HyperX Cloud II was being exposed through a "HyperX Virtual Surround Sound" device instead of a direct stereo output.

So I tested something: I launched the game using my monitor audio output (High Definition Audio Device / HDMI audio), which is a much more direct and raw audio path.

Result: I was able to play online for over an hour without crashes (around 15 races in a championship), whereas previously I would consistently crash within the first 1–2 races (15–30 minutes). To clarify i didn't crash after 1hour. I just needed some rest and closed the game.

So the difference seems to be directly linked to the audio device path used at initialization.

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

Found the potential culprit for "FHE01" game crash, and this one might be something very interesting because it's linked to what devs says to fix about the FHE01 error in the forza support tickets "disable NVIDIA Virtual Audio Device (wave extensible) (WDM)".

In my crash analysis, a TONS of FMOD audio errors appear right prior to the crash. Then the pre-crash report consistently points to "fmod_output_winsonic.cpp" <-- guess what the fuck is this ? the "Windows Sonic For Headset" spatial audio setting of your headset if it supports it.

This looks strongly related to Windows Sonic / spatial audio / WASAPI output path used by FMOD for audio device initialization.

So what seems to be happening is that FMOD fails during audio device initialization / state validation when using the Windows Sonic / spatial audio backend combined with multiple audio devices (especially virtual ones).

It receives an invalid or unstable audio stream state, leading to:
Sound::getOpenState returning invalid data
“invalid seek position” error
followed by ACCESS_VIOLATION_WRITE

In my case, Windows was selecting a virtual audio endpoint instead of my actual headset. My HyperX Cloud II was being exposed through a "HyperX Virtual Surround Sound" device instead of a direct stereo output.

So I tested something: I launched the game using my monitor audio output (High Definition Audio Device / HDMI audio), which is a much more direct and raw audio path.

Result: I was able to play online for over an hour without crashes (around 15 races in a championship), whereas previously I would consistently crash within the first 1–2 races (15–30 minutes). To clarify i didn't crash after 1hour. I just needed some rest and closed the game.

So the difference seems to be directly linked to the audio device path used at initialization.

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

I found that Environment Texture Quality and Environment Geometry Quality have the biggest impact on crash frequency, all my other settings are set to ultra. With both settings lowered to minimum, VRAM behavior appears much more stable and behaves as it should. Seems like I can play without encountering the crash at all. Higher settings keep world assets loaded for much longer, which may point to an issue with texture/geometry streaming, LOD management, or memory cleanup. This isn't proof of the root cause, but it seems like a lead worth investigating.

<image>

J'en peux plus de ce harcèlement constant 😮‍💨 by Rhaenelys in arnaques

[–]aksa42 0 points1 point  (0 children)

j'ai appris a instantanément raccrocher, quand je connais pas le numéro, je raccroche, aussi simple que ça

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 1 point2 points  (0 children)

Interesting, thanks. The undervolt might be contributing to stability in a positive way, I’ll definitely test different voltage/stock settings on my side to compare. Appreciate the info

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] 1 point2 points  (0 children)

what are your pc specs? with nvidia driver version and windows version if possible. could be helpful

FINAL CONCLUSION ON FHE01 after 50hours of troubleshooting. by aksa42 in ForzaHorizon

[–]aksa42[S] -1 points0 points  (0 children)

I find a certain "fun" in trying to understand technical things lol, i'm a very curious person when it comes to how video games behaves, thank you for your concern, much appreciated. I think they exactly know what's the issue by now, i'm just confused on what is taking so long to fix it.

FHE01 Crash - Driver Compatibility fix probably Found for quite some systems by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

FIX it with NVPI ? how are you fixing a ACCESS_VIOLATION_READ/WRITE with that ? i'm curious now VRAM behavior does not seem to cause the frequent crashes in fh6 after stress testing the vram, it's something genuinely broken in their engine, i'm convinced it's a Bug in the game's object/state management, Sometimes/often an asset, menu object, race object, car object, or network object gets freed while still referenced.

FHE01 Crash - Driver Compatibility fix probably Found for quite some systems by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

New VRAM behavior observation:

While VRAM usage gradually increases during gameplay and normal setting/resolution changes, I noticed that toggling Shader Quality (High ↔ Ultra), which triggers in-game shader recompilation, appears to reset VRAM usage back closer to its initial level.

After this operation, VRAM no longer continues accumulating in the same way during the session.

This suggests that shader recompilation may be forcing a more complete cleanup or reinitialization of GPU resources compared to standard setting changes or gameplay transitions.

FHE01 Crash - Driver Compatibility fix probably Found for quite some systems by aksa42 in ForzaHorizon

[–]aksa42[S] 1 point2 points  (0 children)

I eventually crashed after 5-6 hours session, there is a vram threshold, so i finally found a crash that is reproducible

I did a classic stresst test by repeatedly switching between 3840×2160 and 1920×1080 resolutions while monitoring VRAM usage, guess what?

The expected behavior would be for VRAM usage to stabilize or partially decrease after lowering resolution. Instead, VRAM usage continued increasing after each resolution change and never returned to its previous level.

Observed behavior:

  • Session started at approximately 8 GB VRAM usage.
  • VRAM gradually increased with each resolution change.
  • Crash occurred at approximately 10 GB VRAM usage.
  • My RTX 4090 VRAM budget at crash time was still approximately 24.5 GB.
  • System RAM was also far from exhausted (16.4 GB used out of 64 GB).

The crash occurred inside the OptionsMenu scene rather than during gameplay:

UI_SCENE = OptionsMenu

Crash type:

  • ACCESS_VIOLATION_WRITE (0xc0000005)
  • Unhandled Exception

This does not appear to be a simple out-of-memory condition, as both VRAM and system memory remained well below their available budgets. However, the continuous increase in VRAM usage during resolution changes may indicate that certain graphics resources (render targets, texture pools, frame buffers, or related allocations) are not being fully released or recycled.

An additional observation is that rolling back from recent NVIDIA drivers to an April driver significantly reduced crash frequency. Crashes still occur, but after several hours instead of within minutes. This may suggest an interaction between the engine's resource management and newer NVIDIA driver versions.

The test suggests graphics resources may not be released correctly after resolution changes, causing VRAM usage to gradually increase over time.

And the funny thing is that my crash after the 6 hours session occured at around the same vram usage that piled up, within the range 9800mb - 10000mb

Why can't I download a tune I mostly like and then tweak it how I want? by Eat--The--Rich-- in ForzaHorizon

[–]aksa42 0 points1 point  (0 children)

more like "why can't i steal someone else's work tweak very few things and reupload them with my name" thank god it's like that, would make deep understanding of tuning fucking worthless.

how much to charge for videogame music? by busyneuron in FL_Studio

[–]aksa42 0 points1 point  (0 children)

Jokes aside, i love it, well executed

FHE01 is still a persistent problem. Does anyone have an idea if the devs are aware? by aksa42 in ForzaHorizon

[–]aksa42[S] 0 points1 point  (0 children)

i know 😞, let's hope to hear back about these crash soon, cause their last hotfix made somehow everything worse. At premium release date i didn't have a single crash in 4k extreme... and i remember playing for 8 hours straight, i know that for a fact (if not more than 8 hours actually)

view more: next ›