Forum Discussion
Have you tried using Windows utilities to check for issues?
- System file checkl 'sfc /scannow' in the command prompt to ensure there are no corrupt files?
- Component Store corruption, again command prompt 'dism /online /cleanup-image /checkhealth'.
- Scan memory, command prompt 'mdsched'
Assuming the OS is in good shaope, I would run the following full suite of stability and bench marking tests, monitoring power and utilisation of both CPU and GPU to try and narrow it down. CineBench15, CineBench23/24, 3DMark Suite, FurMark, OCCT and Memtest64.
Good luck.
p.s. Try reseating the ram for a quick hit.
- FLYINGTOASTR10 days agoSeasoned Novice
Hello, and thank you for your response.
System file checker repaired 3 bluetooth-related files, but a cursory Google says those are often false positives. Ran the the dism command as well as a memory scan. dism didn't seem to catch anything of note, and the memory scan came back clean. Ran memtest86+ (Not memtest64 as you suggested) overnight and it also showed no issues. I'm not a fan of FurMark as a bench, as it is a pretty unrealistic test for normal usage, and every other game I mentioned running perfectly fine points to this being something specific with either BF6 or Javelin, or some sort of system file issue which is already *mostly* ruled out from me running chkdsk and now the system file checker and from my memory testing good (even with XMP enabled).
I'll report back once I have some more time to see if the steps taken with sfc and dism worked.- FLYINGTOASTR10 days agoSeasoned Novice
Follow-up on this reply which was originally to Bono8o, these steps did not resolve the issue. Thanks anyway.
- Bono8o6 days agoNew Rookie
Sounds like your PC should be as close to certified stable as possible given the results. I have only ever encountered an issue with crashing out of the game to a powered off display when the graphics options are set to max/overkill. I run a 14700k and a 5070ti (595.79 driver) both OC'd and UV'd, interestingly when the power settings are factory default for the gpu. Your situation does not sound similar to my experience, FWIW you could try updating the GPU firmware? We are really drawng at straws here.