It really seems as if the crashes happen randomly at different points and so it is hard to impossible to try to figure out what the problem can be. Maybe i could figure out what the problem is, if i would have the whole computer here. Maybe it's the best option, if you directly contact the S397 support. EDIT Last chance. I just have seen a post on steam, where a user did have a similar problem and he could solve it by using a different wheel, as he wrote. He did use a F1 2019 wheel and replaced it with a porsche wheel. You also have 2 wheels right? Did you try out both of them?
@Bernd, I did some testing today with my second wheel and everything is working so far. But I will do some double checks, though. Thank you so much for your kind and helpful support. Stefan
@fischhaltefolie Stefan, i forgot to mention that the User, after he switched to the porsche wheel, which worked, switched back to the F1 2019 wheel and that miraculously worked too then. Please report if you get it working permanently. That will help other people that have the same problem.
@Bernd, well, it seems it doesn't depend on the rim. Game crashes again with both rims. Which of the devs should I ask for help? Thanks in advance Stefan
Sorry to hear that. You could try to report the problem in the technical & support section: https://forum.studio-397.com/index.php?forums/support-questions.211/ But i don't know how it gets handled by S397. And if you do it, i would suggest to upload a performance log file, that gets created when you are on track, press Ctrl+f and then left shift + space. The log file can be found in the folder: ..\rFactor 2\UserData\Log The file name begins with PerfLog_. And there also should be a .csv file from that session, where the file name ends with RealTimeLogging_PT, that you also should upload. I hope that you can get the problem solved! I wish you a happy new year with a fully working rFactor 2.
I don't think the performance log will help on this one, as it's not really a performance issue. @fischhaltefolie in your situation I would run with completely standard content (S397 track and car), no AI, and see if you still get a crash (I understand it won't happen every time, but just try to reproduce the crash on standard content). If so, remove all extra controllers (wheel, but also anything else that's optional) and try to get it to crash again. It really doesn't look like the game having an internal fault because the logs are ending in different ways nearly every time. I would lean towards a hardware or OS issue, but if you can eliminate possible causes it may help. The traces have lots of 'normal' error messages, but also some content related ones. I don't think they should cause those crashes, but I'd stay away from 3rd party content until you can work it out. On the hardware side get some monitoring software to check temps, and definitely consider running a memory diagnostic - there's one built into windows.
@Bernd, @Lazza, just a short overview of what I've done so far, a bit short in time today: memory diagnostic - ok downloaded cpu-z, installed, read of a malware, deinstalled, virusscan is running checked windows with dism - ok checked windows with sfc - repaired some resources USB device connected mouse, keyboard, wheelbase first test with Aston GTE on Nürburgring 24 h support without ai 50 m after 50 m leaving the garage onFatalError 11 2nd attempt no problems I've got the impression, after first loading of a track with all this rendering work to be done a crash appears more frequently. Could this be? Thanks for your support
@fischhaltefolie Sorry Stefan, i really don't have any idea anymore and i still would suggest what i had written here, even if @Lazza don't think that it is senseful. But i think that it could be a good start to solve the problem, with the help of S397.
Well, it seems every six months I gave it a try. And now i hope, it's ok (knocking on wood). I installed latest nvidia driver, unplugged all USB-devices (except mouse and keyboard), cleared all entries in device manager, also the hidden ones, deinstalled and freshly reinstalled my wheelbase, deleted userdata, abandoned RC, verified files via steam. No more logitech error, no more ctds, no more freezes. Thanks for support and advices.
Well, I made an new start for rf2. Freshly installed Windows 10 home, latest NVidia driver , latest Fanatec driver, this install has never seen anything logitech. But again logisdk appears in trace files, drivers of Fanatec Wheel Base V2 are buggy? ... and other errors? Could please somebody have a look into the trace files? Thank you Stefan
I'm not immediately seeing any major problems in the trace files. The errors all look "normal", I suspect the logisdk entries are also normal, you still have a Logitech mouse right? There have been issues with g-hub, not sure if you have that with the mouse, but that could be a common point (still looks random from the game side, so no actual game errors). Try removing anything like g-hub for the mouse. I'm assuming from previous that your wheel drivers are up to date. Did you ever try spending time with the game without your wheel plugged in, and see if any crashes happen?
@Lazza, thanks for your reply and taking your time. I replaced the logitech mouse, when these problems started with a razer. For that, I don't understand the logisdk entries. Yes, I tried without the wheel and had no issues. I reverted to driver 381 and flashed the firmware. No logisdk entries were found. But rf2 crashed anyway. See attached trace file. Verification with steam didn't show any file errors.
This happend wirh new and old ui. But thanks for your input. Will try it once more with the new install.
Status old ui: keeps crashing with wheelbase plugged and new userdata folder No crashes at the moment with wheelbase unplugged and keyboard inputs, tracefile has logisdk entries though. Slowly I'm coming to the conclusion, there is something wrong in my whellbase. Going to ask Fanatec support.
Are there any csw v2 user here experiencing similar problems? Fanatec support says, this should be a rf2 specific matter. Thanks for your answers.