Quick report back, almost three hours online Fire Team, only three crashes, so yay!
Seems, detuning my RAM and setting screen resolutions to match was the ticket?
Dunno, but you've got my ID, and a bunch of data, crash reports and meanderings, so hope it helps things moving forward.
Unless something else pops up, Filed.Teeth, USMC, Retired, out!
I hope game crashes is the priority
-
filed.teeth
- Posts: 70
- Joined: Mon Jul 17, 2023 8:27 am
- Has thanked: 29 times
- Been thanked: 78 times
-
AmperCamper
- Community Manager
- Posts: 1016
- Joined: Fri Jan 29, 2021 5:02 pm
- Has thanked: 1185 times
- Been thanked: 2256 times
- Contact:
Re: I hope game crashes is the priority
Thanks for taking the time to keep this thread updated for us! Glad to see you've been able to play normally, despite experiencing some hiccups there and there. We'll continue to monitor and improve crashes on our end.filed.teeth wrote: ↑Sat Sep 30, 2023 6:54 am Quick report back, almost three hours online Fire Team, only three crashes, so yay!
Seems, detuning my RAM and setting screen resolutions to match was the ticket?
Dunno, but you've got my ID, and a bunch of data, crash reports and meanderings, so hope it helps things moving forward.
Unless something else pops up, Filed.Teeth, USMC, Retired, out!
-
filed.teeth
- Posts: 70
- Joined: Mon Jul 17, 2023 8:27 am
- Has thanked: 29 times
- Been thanked: 78 times
Re: I hope game crashes is the priority
Postscript: Went back to BIOS, set it to default, then adjusted a few things to my liking.
I'd gone to the BIOS before, but didn't see anything out of the ordinary, but figured "what the hell," and just reset it since I still had the occasional crash.
One of those settings must have been wacky after all.
Haven't crashed once since.
Not sure what was out of kilter, but it wasn't just the memory speed, I guess....
Time for me to post a dozen "embarrassed" icons again, and this time won't be walking it back....
I'd gone to the BIOS before, but didn't see anything out of the ordinary, but figured "what the hell," and just reset it since I still had the occasional crash.
One of those settings must have been wacky after all.
Haven't crashed once since.
Not sure what was out of kilter, but it wasn't just the memory speed, I guess....
Time for me to post a dozen "embarrassed" icons again, and this time won't be walking it back....
-
filed.teeth
- Posts: 70
- Joined: Mon Jul 17, 2023 8:27 am
- Has thanked: 29 times
- Been thanked: 78 times
Re: I hope game crashes is the priority
Long time coming but I finally found a problem that started plaguing EVERY thing, not just this game, but since at the time this was the only game I was playing and I was on it any time I wasn't at work or asleep...
Win 22H2 affected the CPU chip series of 13900k and kf's and caused random/increasing problems in a large percentage of the folks owning those chips. An arcane thing, to be sure, but just last night googled the right keywords and found it.
Yes I've been chasing my tail on this since the original entry, got a couple hundred hours of troubleshooting, changing memory chips (it really does present as a memory problem) and detailing every mem freq combo possible resulting in about three pages of closely written notes etc., etc..
Elusive and arbitrary, not sure why it hasn't gotten bigger press, but guess there's not enough of this chip owner population out there for it to have gotten widespread attention, since it's only the k and kf series that it messed with.
To make it worse, all the troubleshooting tools always said everything, including windows, was just fine, or they threw an error/CTD/BSOD with no log to show why, which didn't help with progress...
Plus most of the tools don't create the condition that would throw it, only games, lol.
Anyway, passing on for clarity's sake. My fix was setting all cores to 54 via Intel XTU. So simple after months of bruised forehead...
https://www.reddit.com/r/intel/comments ... ith_intel/
Win 22H2 affected the CPU chip series of 13900k and kf's and caused random/increasing problems in a large percentage of the folks owning those chips. An arcane thing, to be sure, but just last night googled the right keywords and found it.
Yes I've been chasing my tail on this since the original entry, got a couple hundred hours of troubleshooting, changing memory chips (it really does present as a memory problem) and detailing every mem freq combo possible resulting in about three pages of closely written notes etc., etc..
Elusive and arbitrary, not sure why it hasn't gotten bigger press, but guess there's not enough of this chip owner population out there for it to have gotten widespread attention, since it's only the k and kf series that it messed with.
To make it worse, all the troubleshooting tools always said everything, including windows, was just fine, or they threw an error/CTD/BSOD with no log to show why, which didn't help with progress...
Plus most of the tools don't create the condition that would throw it, only games, lol.
Anyway, passing on for clarity's sake. My fix was setting all cores to 54 via Intel XTU. So simple after months of bruised forehead...
https://www.reddit.com/r/intel/comments ... ith_intel/