BSOD after booting and doing nothing, 13-15 minutes later

The desktop is a PC, built by me, in 2011. AMD FX 6-core, 16 GB RAM, 1TB Western Digital Black, regular HD (not an SSD or hybrid). Motherboard is an ASUS M5A87. This is a business/office/production machine, not a gaming machine. Previous OS was Windows 7, and upgraded to Windows 10 with the free upgrade in 2016.
First blue screen, May 27, 2018, upon replacing an AOC monitor which stopped working with a new, HP monitor. But replacing the HP monitor, subsequently, with 3 other used monitors continued to give blue screens.
The blue screens come on consistently, after 13-15 minutes of the computer not actively used for anything, after booting to the desktop and allowing to sit idle.
I tried Clean Boot, enabling 5 programs at a time and excluding all others, and also under msconfig and the services console, but didn't find any program that was responsible.
In safe mode, the desktop will go indefinitely at rest without giving any blue screen.
I tried swapping out USB hubs, keyboards, mice, sound card, speakers, power cord, video card, Ethernet cable, and monitor cables, with no success.
I physically cleaned the PC with an air blower and canned air. Running Memtest86 and Microsoft’s memory test showed no errors.
Replaced the power supply (which showed no problems with a PSU tester), with another, more powerful, power supply.
I restored from an Acronis backup to April 2018, to a spare hard drive, prior to version 1803, which stopped the blue screens for about a week, but they started up again.
The blue screens appear consistently, 13-15 minutes (timed with a timer) after booting to the desktop, if doing nothing (meaning no activity by me at the keyboard, such as browsing or using File Explorer, etc.). If I boot and then do something, including Windows updates, get a document, do a scan, etc., more than 13 minutes passes before the blue screen occurs, but eventually, it does.
So far, I’ve waited for Windows 10 updates for July, August, September, and October (but not the update to 1809) might resolve the blue screens, but they did not.
I have not tried reinstalling Windows, because I wanted to see if the dm log collector program might reveal anything first.

Hello and thanks for posting on TenForums!

To give us the most information possible for assessing what may be going on can you also run and upload the beta log collector files that are included at the end of the BSOD Posting Instructions. Thanks!

Hi, thanks for responding. I ran the beta log collector, and the output is attached.

Have you run any calculations to determine if your power supply is able to provide enough power for when all devices are running, for example if all the fans kick in and graphics card, sound card and hard disk are working at full strength? Does your system get particularly hot? What was the power of the other PSU that you tested?

The previous power supply, on which the computer ran for many years, was a 380 watt Antec Earthwatts. I only put in a 430 watt Antec Earthwatts when attempting to see if that was the source of the blue screen. I remember doing a calculation when I built the machine originally, and at that time, the PC had an AMD FX quad-core, and only two DVD RWs, and the calculation indicated the 380 watt ps would suffice. I upgraded to an AMD FX six-core, and added a DVD-RW, and the computer still ran on the 380 watt power supply for at least two or three years without problems. I could try a 500 watt power supply, but the blue screen does come on now after 13-15 minutes of my doing nothing, never when I was clearly doing a lot (prior to the blue screen problem, such as with many open windows, a video playing, and other programs running). And the blue screens only started happening in May of this year.

I don't think the computer gets hot, but I don't remember what is considered hot. The CPU just now is 30.5 C, and the mobo is 21.0 C, according to Asus' mobo monitor utility. I just ran a calculation on Cooler Master, and they suggest a wattage of 409 watts. I'd have to purchase a 500 watt power supply, and try that to see.

I located the memory.dmp file, but I get a blue screen when I try to copy it to another location after a box prompts that I need administrator permission and to click on it to proceed. I had to use Everything to locate the win32k.sys-20181010-2308.dmp file, and when I used File Explorer to navigate to its location in the c:\windows\livekernelreports folder, I got another box, prompting me to click on it to proceed for access to the folder. When I did, I got a blue screen again.

What should I do about these files, which I cannot seem to access because I'm getting blue screens? And should I proceed with steps 3) and 4) at this time?

I have an idea. I am going to remove the hard drive and connect it to my backup desktop by USB, with a hard drive dock, and try to access the files that way.

In the opening post there were no BSOD when using safe mode.
Boot into Safe Mode on Windows 10 | Windows 10 Tutorials
While using safe mode > find both files > zip > post share links into the thread
The prior steps can all be done in any order.

The memory dump will disappear and a new file created after each crash.
Unless it was saved a new dump file was created.

After every BSOD > run the beta log collector and post a new zip.
Look at the size of the memory dump.
If < 1.5 GB then zip > post a share link into the thread.

I updated the BIOS, and let the computer rest after rebooting, but got a blue screen again. I ran the beta log collector, and will share the zip now. I was able to copy the 2 files to a different location and will attempt to share a link from Dropbox, after this.