39 minutes ago, ErichB said:

Well, I've reinstalled W11 and MSFS.  Ran another Prime95 test with a resulting crash within seconds, so I guess it's conclusive that it is hardware.   I will set the overclock back to default and see if it behaves.  Will let you know.

thanks

I'd try the BIOS reset, if that doesn't work, then definitely seems likely a hardware fault, probably just your RAM, either way, keep us informed and hope you get it fixed!

2 hours ago, Bob Scott said:

Blowing up a few seconds into P95 is a pretty clear indication of a hardware problem.  If your system is overclocked, the silicon may have degraded over time just enough to put something on the bad side of the ragged edge of stability under load.  So re-running the overclock drill, starting at stock settings, would be in order.  That said, if you're gonna do a new build in less than a month, I'd just set things to stock and see if that works well enough to gap you to the new build.

As suggested above, a run of Memtest86+ is a good idea, as I have seen more issues with RAM than any other component over 30 years of computer building.  If it fails the test, downclocking it from XMP and/or bumping up the Vdimm voltage a hundredth of a volt or two might bring things back to stability.

 

 

6 hours ago, Brocky120 said:

Ouch thats a big problem! Ok two things:

 

1) Reset your BIOS to defaults, this will clear any potential CPU/RAM misconfigurations etc.
2) Ensure nothing is overheating (specifically the CPU) on HWINFO.

 

Failing that, check both/all RAM sticks and ensure they are exactly the same, same numbers, same version, same voltage etc on the sticker

Think I have some good news...

I ran MemTest64 to test the RAM modules. Ran for about 30 mins.  No fault.

Reduced the overclock on the CPU to 4.3 from 4.8

Loaded MSFS...default.  Took 787 from Gatwick low level over London with photogrammetry on.  Moderate settings.  No fault after 30 mins

Did the same with the Fenix ...no fault.

But...Prime95..same crash...same time.🤷‍♂️

Anyway...it seems to be doing what I need it to do, so for now I'll take it.  Will add scenery and see how I get on.

Thanks everyone for contributing assistance.   Much appreciated.

I'll add to this thread again either way (good or bad) in a couple of days.

 

Erich

 

1 hour ago, ErichB said:

 

Think I have some good news...

I ran MemTest64 to test the RAM modules. Ran for about 30 mins.  No fault.

Reduced the overclock on the CPU to 4.3 from 4.8

Loaded MSFS...default.  Took 787 from Gatwick low level over London with photogrammetry on.  Moderate settings.  No fault after 30 mins

Did the same with the Fenix ...no fault.

But...Prime95..same crash...same time.🤷‍♂️

Anyway...it seems to be doing what I need it to do, so for now I'll take it.  Will add scenery and see how I get on.

Thanks everyone for contributing assistance.   Much appreciated.

I'll add to this thread again either way (good or bad) in a couple of days.

 

Erich

 

Lovely! Glad you're having some positive results.

It has long been recommended with MSFS...No overclocking whatsoever. None.

6 hours ago, udidwht said:

It has long been recommended with MSFS...No overclocking whatsoever. None.

My machine has been overclocked since MSFS came out (the same machine that was overclocked with P3D).  No issues until last Thursday.  So, it was the least likely culprit. Still not sure if it is the culprit but seems reasonable that it could be.

Edited August 19, 20232 yr by ErichB

On 8/18/2023 at 9:11 PM, Brocky120 said:

Lovely! Glad you're having some positive results.

PC seems stable.  2 x 4 hour flights yesterday no issues.  Dialling the overclock back which I have had set for years seems to have been the issue.

Thanks again for everyone's help

2 hours ago, ErichB said:

PC seems stable.  2 x 4 hour flights yesterday no issues.  Dialling the overclock back which I have had set for years seems to have been the issue.

Thanks again for everyone's help

Just silicon hardware degradation.  It happens.  Glad you are back up and running!