BSOD 1e with Skyrim SE, no further parameters

Hello everyone, I am new to the forums. Though I feel like this topic has been repeatedly beaten to death, I can't seem to find a solution for my own scenario. I've been using the same install of Windows 7 Ultimate x64 since 2014, and recently started receiving the good ol' BSOD 1e, specifically while playing Skyrim Special Edition.
I've had it installed and running stably since around February of 2018. Decided to pick it up again after a few months, and been getting the blue screen after it runs for an hour, maybe hour and a half.

That is the only circumstances I can duplicate the problem. I can let my system run for hours, even days, on end without failure. No other programs seem to cause any issues at all. I don't have any other graphics-intensive games or applicatins to try (besides test utilities). I also have a dual boot setup with Manjaro Linux, where I have no problems at all.

The only changes that have been made since the original build of my system back in 2014, are the SSD's that I cloned my OS onto, that was March of this year, which all went smoothly. Also mid-september I picked up a new gamepad (Logitech F310) to replace my 10 year old RumblePad 2.

I've tried to analyze the dumps myself, but can't find any further info than the blame of "ntoskrnl.exe" with extension 93c70. BlueScreenView reports nothing further; all the rest of the parameters are zeroes. Event viewer doesn't seem to have much to say, other than the kernel power failure #41.

Here's an explanation of what I've done for troubleshooting...
BlueScreenView, of course, to watch the dumps. All I got was an error regarding "ntoskrnl.exe", and one of them also contained an error with "discache.sys", but that was only once, on the 5th crash or so.
Disconnected and reconnected all of the connections on the entire system, along with removing and replacing all the PCI cards and RAM modules.
Updated Windows, updated drivers. Ran driver verifier, I did have an issue with a virtual drive from an old CloneCD version. Uninstalled that, and verifier was happy on numerous runs.
I've gone through the removal process for old USB devices (I believe it came from this forum), thinking maybe there was some conflict between my old game controller and the new one.
Have run memory tests like crazy, using Windows memory diagnostic as well as MemTest86+, both on numerous occasions for several passes. No errors.
Ran FurMark stress test for hours, no errors and temps are good. Maxes out at 75 C and stays there.
Got the latest CoreTemp to watch that as well, we run at a chilly 106~110 on all four cores under fair load.
I've done integrity checks of the game to make sure that's not the problem.
I've tried disabling (but not completely removing) a few things, such as the ASUS AI Suite that came with my motherboard, and the BlueStacks Android emulator, which seems to pose issues on newer machines.

There's probably more I can't think of, but none of the troubleshooting I've done has not had any impact on the amount or frequency of my BSOD crashes.

I am attaching a copy of the .zip file from the log collector as outlined in this forum in hopes someone would be kind enough to look at the dumps and see if there's any further info to help pinpoint the issue. Thanks for reading my lengthy post, and I appreciate any feedback I can get.

Thanks,
Chew

if you still have it, can you reinstall the old RumblePad to check if you get the same problem?

Yes, I have tried that as well. Symptoms remain the same. I even removed all the old USB devices as mentioned above.
Someone mentioned in a different thread using driver verifier on the unsigned and Microsoft drivers as well as third party. Is this process safe?

I think so.

The logs don't provide a "distinct" reason for the shutdown other than an exception wasn't handled.

The fact that it takes a while for it to happen might indicate that your CPU is overheating. You can download and run HWMonitor to check that. Make sure that your CPU fan and the vents are clean.

Is there a setting for hardware acceleration in the software. If so, you might try disabling it.

Have you considered asking here about it-

Hardware and software discussion - The Nexus Forums

I considered the possibility of CPU overheating, or perhaps a single core. I have CoreTemp running, and frequently check it. The highest I've seen it (even while playing) was 41 c. I blew all the dust out of everything in the box when I was re-seating everything. I'll check my Radeon settings for acceleration, but have no overclocking, as I'm not a believer. Will also look back at the CoreTemp logs to be sure. Air flow is no issue, it's an Antec 300 case, 2 intake fans, 2 exhaust fans, all of which I clean regularly.

I asked about hardware acceleration because I was thinking that your graphics card might be one of the legacy cards for which hardware acceleration won't work with the newest drivers. However, I did more research this morning and the card is not considered legacy and you have the latest Adrenalin driver (which is optional). It wouldn't hurt to try my suggestion (if the option is there) and change it back if it has no effect.

I'll try to give that a shot this evening and report back with that info and my temperature readings from the log. Thanks for the suggestions.

As I thought, looked back at my CoreTemp log, and through a period of about two hours, my record high temp was 108 f, and no more than 90 at idle. No time yet to try disabled acceleration, but will post back when I do.

Doesn't look like I have the ability to make any adjustments to hardware acceleration. The Windows control panel settings are inaccessible, and I can't seem to see anywhere in my Radeon settings anywhere. Unless someone knows something I don't...

I wanted you to look in the game settings.