Twice today I was trying to do an FTP ramp test and the program crashed at 10m 1s.
The test had just entered the 240W interval and then crashed
Is this a known bug?
Hi Adam, welcome. There’s no reason the ramp test by itself would cause a crash. It’s more likely that you selected the same world and route on both tests, and it crashed at the same spot. If it was the same time through a set test then you’d have been in the same place.
You’ll need to provide details of your PC’s specifications if the community are going to be able to offer any suggestions.
1 Like
Thanks Dave, thats an interesting thought. I would have been on the same route, France I think. I’ll try again on a different one.
I’m on a Windows laptop, windows 10, i5 10th gen, 8gb RAM. Only about a year old by now
There’s a crashing issue with 10th and 11th gen integrated graphics. See these threads, some people have had success rolling back the Intel drivers to specific older versions: Intel integrated graphics gen 10 and 11
Zwift Crashing/Freezing Mid ride - #338 by Paul_Attard
Same issue here, but not with intel integrated graphics. I’ve tried the regular ftp test (not ramp, short program) twice as well as the ramp test light and swift crashes about 10-12 minutes into the ride. Has this been a known bug?
Same issue with an RTX 3090 and Ryzen R9 5950X. Any fix?
I’ve tested on 3 different maps, and it crashed on each. I’ve never had crashes before in Zwift before trying the ramp up test.
Check the Windows Event Viewer for clues
I only found the following:
Source
ZwiftApp.exe
Summary
Stopped responding and was closed
Date
2/27/2023 6:40 PM
Status
Not reported
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: ZwiftApp.exe
Application Version: 0.0.0.0
Application Timestamp: 63dd83d1
Hang Signature: 5b0c
Hang Type: 134217728
OS Version: 10.0.22621.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 5b0c28d489757cd7a12fc9877ec2b399
Additional Hang Signature 2: 41b5
Additional Hang Signature 3: 41b56950b4a9b249bac188c8e928c9ee
Additional Hang Signature 4: 5b0c
Additional Hang Signature 5: 5b0c28d489757cd7a12fc9877ec2b399
Additional Hang Signature 6: 41b5
Additional Hang Signature 7: 41b56950b4a9b249bac188c8e928c9ee