[PC] Random (but frequent and annoying) CTDs

Hi

After a few minutes of gameplay I’m getting CTDs on my laptop. I checked event viewer and found this

CTDs usually happen while I’m browsing cars in my garage., but not always.

Please help :).

Part of dxdiag diagnostics (I have no idea how to attach files here :frowning: ).

Dude this started to happen to me today, it doesn´t matter what i do, even in online while racing it crashes. Same file name different error [Mod Edit - Abbreviated profanity, profanity and profanity that is disguised but still alludes to the words are not permitted - D]
Faulting application name: ForzaMotorsport7.exe, version: 0.0.0.0, time stamp: 0x5b06d479
Faulting module name: ForzaMotorsport7.exe, version: 0.0.0.0, time stamp: 0x5b06d479
Exception code: 0xc0000005
Fault offset: 0x000000000101e91f
Faulting process id: 0x1e10
Faulting application start time: 0x01d407ada530fb29
Faulting application path: C:\Program Files\WindowsApps\Microsoft.ApolloBaseGame_1.130.1736.2_x64__8wekyb3d8bbwe\ForzaMotorsport7.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.ApolloBaseGame_1.130.1736.2_x64__8wekyb3d8bbwe\ForzaMotorsport7.exe
Report Id: f3e7d067-3b10-46b3-919a-c472687aa229
Faulting package full name: Microsoft.ApolloBaseGame_1.130.1736.2_x64__8wekyb3d8bbwe

17 days and no response. Except for a poor guy encountering same crap. Pathetic.

Both FM7 and FH3 are unplayable for me. I’m getting CTDs even right after starting a race.

Was getting this on a freshly built machine.

One thing that helped but did not completely solve was that I rolled back to Nvidia drivers 391.35.

I had tried the latest 398.xx released on 26th of June, that is mentioned in the sticky posted 3 hours ago, but I had best results going right back to the March drivers.

Best of luck.

Thanks bro. I’ll give these drivers a try tonight.

Seems like these drivers did the trick. Wonder if nvidia knows about this bug.