It can happen unfortunately.It crashed this evening (Blue screen with message) after just 10 minutes of browsing. I went into the BIOS and the XMP had gone back to Auto.
No worries GunRunner - glad it appears to have all worked out for you.>snip<.
Eventually I went for a 32" Benq BL3200PT 32" WQHD
https://www.overclockers.co.uk/benq...lim-bezel-flicker-free-monitor-mo-099-bq.html
Hey Gun Runner
Sounds like you've self navigated yourself to the right areas.
You can manipulate the memory as much as you like voltages/frequency/timings - as you've found out. I've been fortunate but used different branded memory in the builds I did and they have proved very resilient. Others haven't had the same luck so it really is a lottery.
I would have thought 2666MHz at 1.35 with XMP timings would/should run - especially with F6 BIOS or later (I tend to avoid setting like 'Ultra Fast Boot' as I've found features like this can kneecap clocked settings before they start - memory included).
Hope your tinkering has led to some success...
That's unfortunate - as it should hit 2667MHz at stock at 1.35V with your motherboard (it's not classed as an OC) - but different users/members have had different experiences and 2400MHz is still their only option. :/Update. Nope.....this RAM seems to have a problem at 2666Mhz as well with repeated crashes. I put it back to default and it has been working fine after 3 crashes in quick succession. I will have to try it again at higher frequencies once a later more stable BIOS has been released.
I downloaded the latest version of Chrome and so far so good. This latest version has controls and buttons as per Windows 10 and I can now run the context menu from the right mouse button. 
Sadly, i do - although my first built PC was a mighty P75.It is as though I am running a 286 or a 386 (you remember those).
I wouldn't completely discount the memory.Just wondering if this all to do with the RAM. Perhaps not.
Have you looked at Event Viewer after these problems occur?>Annoying issues<
There are known issues with HWMonitor and the AM4 platform.I am now running CPUID HWMonitor
There are known issues with HWMonitor and the AM4 platform.
It may have been patched - but would consider uninstalling if you start getting other strange anomalies.
It's not been updated - but not all users have experienced problems. Plus, i get the impression you're not a heavy gamer so you may be unlikely to have any issues. Worth keeping an eye out...No errors. Using latest version:
Version 1.31
Have you flashed to the latest Official F7 BIOS?I am currently running RAM at 2666Mhz. So far nice and stable. Next frequency?
Have you flashed to the latest Official F7 BIOS?
If not i would try that before attempting 2933MHz.
Hopefully, this will remain stable.Yes. Now running the F7 at 2933Mhz
Hopefully, this will remain stable.
Again, look out for cold boot issues even if on the surface it appears stable (may only show itself as a problem 1 in 5 boots).
If you run into problems you could bump up the memory voltage to 1.32V/1.35 (incremental bumps) or/combined with slightly looser timings.
Suspect, you're getting used to the environment now - not that it was alien to you anyway with your experience.
It did give me a problem with not booting the second time after BIOS replacement. Will have to test more to see if it manifests itself. I do not have a problem if it does it 1 in 5 anyway.Yes, my bad, I had another person in mind when typing that - he started at 1.3V - different memory.I have started off with 1.35v.
The 1 in 5 has a habit of developing into other issues for some users - like looping. But if it stays consistent then as you say - not really a major problem.I do not have a problem if it does it 1 in 5 anyway.