Crashing to Desktop (no error)
During my first full play-though, the only issues I had with crashing were with mods installed. Mods have been completely removed, and the game ran fine till the end, but since starting a new game (...
Forum Discussion
If you open event viewer:
C:\WINDOWS\system32\eventvwr.msc
Double click "Windows Logs" on the left hand side, and then click "Application" under it, it will come up with all the entries for your system regarding application errors and other information.
If you run Veilguard and can trigger a CTD, open the event viewer up as above and it should list exactly what happened that triggered the CTD. If you can copy and paste here what it says we might be able to help you figure out what is going on.
Nothing currently showing for Veilguard specifically around the times it's happened, though can't remember exact times or dates, so can't say whether something on a system level caused it (it ran fine yesterday).
Will keep an eye on this, though.
Yeah, it is easiest to check it right after you hit a CTD so you don't have to try searching through the logs since there are just a ridiculous amount of them that get generated on a regular basis.
Best of luck.
Just had another CTD - no events logged at all at the time of the crash.
The game just stops, and the EA app pops up as it does when I quit the game normally.
Wow, that is really strange, that means the system really is treating it like a voluntary quit to desktop. Very strange.
I've run into this type of error in the past, but it is very rare, and very hard to track down without running a debugger.
