Hello, I've been experiencing some crashes in R3E lately (crashes to the Windows desktop with an indication of a crash log). In past days, it had happen when I tried a single player, single event, and went from pratice to race. I could pratice all the time but would crash almost instantly when entering the race (crash logs from day 15/Jun and 20/Jun). Track was Silverstone and car I think it was an Audi R8 Today, I had one when I entered a multiplayer race, when leaving the pits. Now, I had just started a multiplayer game but still managed to run for a few minutes before crashing. (crash logs from today). Track was the Nordschleife, and the car was a Porsche GT3 R (which I coincidently bought today). I'm using 64-bit version of Raceroom My system is: Windows 10 Pro 64-bit (build 1803) Intel i5-3570K, 16GB RAM Nvidia 660Ti (latest driver, 398.11) Logitech DFGT wheel with latest drivers I've also check file integrity using Steam and games files were ok. Do you have any ideia of what might this be? Raceroom has always ran ok on my system before. I've attached all the crash dumps (in the zip file) Edit: edited thread title to reflect crash exception number 0xC0000005
Today I had another crash. I tried to use the 32-bit version of Raceroom to see if I could avoid crashes, but I guess not. It happened on Silverstone in a single event race, when I ended the pratice session to go onto the qualy. I've attached a screenshot and the crash dump. If anyone has any ideia on why is this happening I would glady appreciate it.
I was getting crashes...reinstalled and the crashing is gone but problem is with VLN or 24 Hr Nordscheife and the 2 new cars I bought...M235i and 911 Cup...game runs like a slide show. Unplayable for those combos.Any other combo is fine. Very Strange.
I'm going to reinstall it and see if it can solve the crashes. Unfortunately I don't have either of those cars, but I can try with the 911 GT3 R in Nordschleife to see if I also get low framerate. Btw, what graphics card do you have?
Old Quadro 2000...but it runs RRE great most of the time. Regular Nurburgring OK, as well as Tourist and standard Nordschliefe, it's only VLN and 24 Hr that go nuts.
Nope, full reinstall (also deleted SimBin's folder in Documents\My games) but still had a crash with code 0xC0000005, when going from qualy (didn't do a qualy lap, just ended session) to race. Here's a new crash dump for the S3 team, if needed. I just bought a new car in this summer sale, but I'm unable to race with it as this keeps crashing almost always when going to race. Could someone from S3 give me a clue of what might it be from looking in the crash dump?
Hi Alex, sorry for the belated response. Seems I wasn't around when you originally posted this and your report got burried somehow. Are you still using the 398.11 driver? Cause that was causing some issues. There is a new version by now, so maybe updating the gpu driver would already solve those issues. Anyhow, I'll open a report with your dump files and have sb take a look at them asap. Will return to you once I know more. Best regards Christian
Hi Christian, No, I already have the 398.36 driver, but I'm still having the issue (had one today). Thank you for helping
Hi Alex, could you please provide the game and MWTransport log files of a session that crashed, ideally one that you've posted a dump file from? F.e. that last crash dump is from 3.7.2018, 23:33, so navigate to ...Documents\My Games\SimBin\RaceRoom Racing Experience\UserData\Log and find the log files with the same timestamp, or the ones that are closest to that.
@Christian Göpfert I might found the problem. I was testing yesterday's update and I had a new crash. I then checked out Windows event viewer, and noticed I got a few warnings from WHEA-Logger (event Id 19) and that triggered me to check my systems CPU, which I had overclocked since March last year (and played Raceroom and other games long before that without any issues). Initially I thought that it might be instability from the Spectre and Meltdown mitigations that Microsoft release in Windows updates (a lot of pages point these WHEA-Logger errors there), since only a couple of months ago I started to have crashes in Raceroom, but even after disabling these mitigations system instability continued (checked with Prime95). I've now removed the overclock completely and reenabled those mitigations, and it seems everything is back to normal (Prime runs fine) Later in the day or tomorrow I'll try to have a race session in Raceroom, but this one might be "case closed" soon. Thanks and I'm really sorry for the trouble, since it's probably all on my end.
I also have this error but nothing to do with overclocking, each time I exit to windows it crashes. dmp file attached
likewise, i just sent in my plea for help as well. the same error code. updated everything, including wheel firmware, reinstalled the game, worked for a coupel of laps and then crashed again.
Well, I took a quick look at your dump file. A classic case of a null pointer being dereferenced. It got caught on a call to WaitForSingleobject from RaceRoom. Since I don't have symbols for these programs and the dump is not a full memory dump, there is not much more I can tell you. Here is the active stack at the time of the crash: # Child-SP RetAddr : Args to Child : Call Site 00 00000000`00bad938 00007ff9`be6d8b03 : 00007ff6`444224b0 00000000`00bae0c0 00000000`00000000 00000000`00badac0 : ntdll!NtWaitForSingleObject+0x14 *** WARNING: Unable to verify timestamp for RRRE64.exe *** ERROR: Module load completed but symbols could not be loaded for RRRE64.exe 01 00000000`00bad940 00007ff6`432eea4a : 00007ff6`444234d0 00007ff6`00000001 00007ff6`00000000 00000000`00000340 : KERNELBASE!WaitForSingleObjectEx+0x93 02 00000000`00bad9e0 00007ff6`444234d0 : 00007ff6`00000001 00007ff6`00000000 00000000`00000340 00000000`00000002 : RRRE64+0xb1ea4a 03 00000000`00bad9e8 00007ff6`00000001 : 00007ff6`00000000 00000000`00000340 00000000`00000002 00007ff9`00000080 : RRRE64+0x1c534d0 04 00000000`00bad9f0 00007ff6`00000000 : 00000000`00000340 00000000`00000002 00007ff9`00000080 00000000`00000000 : 0x00007ff6`00000001 05 00000000`00bad9f8 00000000`00000340 : 00000000`00000002 00007ff9`00000080 00000000`00000000 00000000`00000000 : 0x00007ff6`00000000 06 00000000`00bada00 00000000`00000002 : 00007ff9`00000080 00000000`00000000 00000000`00000000 00090000`000807e4 : 0x340 07 00000000`00bada08 00007ff9`00000080 : 00000000`00000000 00000000`00000000 00090000`000807e4 03130007`000c000b : 0x2 08 00000000`00bada10 00000000`00000000 : 00000000`00000000 00090000`000807e4 03130007`000c000b 00007ff6`427d0000 : 0x00007ff9`00000080 From my perspective it does indeed look like a RaceRoom bug, but this is based on very little information.
Thanks for this but how do you re-enable those mitigations? sad to say my knowlegde of what you are talking about is not limited, but non-existent.
I don't quite remember how I did it, but it should have been something involving registry keys using Microsoft's documentation. But it should be enabled by default, so I would advise you not to change it as those mitigations are there for your system's security. In my case, it was my system's (bad) overclock triggering all of those WHEA logger errors. I currently have my system overclocked (but on lower settings and thoroughly tested), and I never got the WHEA logger errors again neither as raceroom crashed on me again with this error. Is your system overclocked?
hey, best thanks for yer reply. no, its not overclocked. I checked all the settings again last nite and found something i overlooked and dunno how the values got to be so high - the collission effect in the advanced settings was set to 200%. Must have happened after the reinstall. i lowered them to 10% and tried again, hit the gravel and the game did not crash. My FFB gain are at 75% to avoid clipping - anyway I will check again today and report in. thanks again