3 crashes in the last days thats more then last year dont know why or how it just happens on the track pretty randomly r7 3800x rx 6750 xt latest driver win10 32gb 3200mhz game is on nvme ssd
Also add Game_xxx.log and MWTransport_xxx.log from the same sessions as crashes. You can find them here: Documents\My games\SimBin\RaceRoom Racing Experience\UserData\Log
i remember that i changed a option about replay saving, before didnt saved replays, now it does, maybe maybe, this is the only thing i changed a few weeks ago
I already seen few instances where enabling replay saving caused crashes so that may be the case sadly hard to say why it happens for some people and for some doesn't one of my friends also had crashes when he had plenty of replays in the folder and after he deleted them it was fine other people had crashes till they disabled replay saving which is hard to do if u race in leagues or something like that having option to SAVE it after the race instead automatic save would be so much better option imo
Can you add few details? Like what you did when it crashed, was it sp or mp? Maybe with session switch? Anything you remember Also, theres gonna be an update in few days with more changes/fixes
multiplayer on the freetrack all cars one, raceroomraceway bridge, training session, was on track driving, probably something happens somewhere else, everytime i was driving x-17 and it happend on different locations
i deleted the raceroomfolder and made a fresh start and still crashes again once it crashe on joining a server i was not even on the track
still crashing with the update mw is to big https://drive.google.com/file/d/17oQDvWmMyHuNVFAozy9gIR-xMddpttE8/view?usp=drive_link
I had a 05 error back in 2023 i think, don't remember. I looked into windows event viewer to see what was going on, system-wise. and it told me i had not enough virtual memory or something. so a bit back and forth and nothing helped. and in the end, resetting windows fixed it for me since then Anyway what i want to say is: look into windows event viewer, system tab and then look for errors at the time of the game crashes. Find out what it was. Windows reinstall is the last straw ever in any case.
Hijacking another thread I have done that in the past but really have no idea what any of the stuff in there means or how to do anything about it. If i were to post a screenshot next time i have a crash and check that stuff, do you think you could tell me what to do about it?
Well, i also just googled back then and then clicking through all the results you get. Yes, it takes time, but if you can play afterwards, spending an hour or 2 is definitly worth it But sure, people may see the shot and the wording and may direct you to a specific topic. you never know
I also googled a bit and the general issue didnt seem uncommon but i didnt really find any solutions (certainly none that i felt comfortable doing when not knowing what im doing ). But that was before chatgpt, maybe i could also ask him next time
I'm getting the error over and over and over again even after re install renaming graphic files and it always crashes on startup.
Hi everyone, After extensive troubleshooting, I pinpointed the cause of the frequent RaceRoom Racing Experience crashes to Logitech G Hub, specifically the logi_steering_wheel_x64.dll plugin. Once I uninstalled G Hub the crashes completely stopped. Unfortunately, without G Hub installed the Logitech wheel doesn’t work correctly, but with G Hub (especially version 2025.5), the game crashes consistently. So if you’re using a Logitech wheel and experiencing crashes, this could be the root cause. If you’re comfortable analyzing crash dumps, I recommend trying WinDbg (available from the Microsoft Store). It was instrumental in confirming that the crash originated from Logitech’s plugin. Other debugging tools might report this differently, but WinDbg gave me clear insights about the root cause/but may not be the cause for you. This seems like an issue Logitech will need to address, but it might also be helpful to notify KW Studios so they’re aware of the conflict. Hopefully, an upcoming G Hub update will fix this. Let me know if you want me to share the crash dump or logs.
Hi, I reviewed your crash dump and the error is caused by an access violation exception with code 0xc0000005. The game tries to read from an invalid memory address which means there is an invalid pointer being accessed inside the RaceRoom executable. This usually points to a bug in the game code where a pointer is uninitialized or corrupted during gameplay. Since the crash happens inside the game’s own module and not an external driver or plugin, it suggests an internal issue with how the game handles memory or logic. Sharing this information with the developers can help them find and fix the problem. It would also help to provide details about when the crash happens and any other logs you have for a better diagnosis. If you want to reach out for further help or discuss this, you can contact me on Discord: Desirexy.
(UPDATE POTENTIAL FIX) If RaceRoom Racing Experience (RRRE) crashes on start up and you use a Logitech wheel, the problem is often caused by the logi_steering_wheel_x64.dll (or logi_steering_wheel_x86.dll) files from Logitech’s software. To fix this, first fully exit Logitech G HUB and close all Logitech-related processes in Task Manager. Then navigate to this folder on your PC: C:\Program Files\Logi\wheel_sdk\ In that folder, rename logi_steering_wheel_x64.dll to logi_steering_wheel_x64.dll.bak. If you also see logi_steering_wheel_x86.dll, rename it the same way. This stops the problematic plugin from loading and should prevent RRRE from crashing. It worked for me personally, so if you’re experiencing the same crash on startup or related errors, this fix should help you too. Keep in mind that some wheel features might not work until Logitech releases an official fix.