BSOD only when PC in Sleep Mode or just after waking up

Hi all, thank you for coming to have a look at my issue! I'm absolutely lost after trying to figure this out for a very long time, so I can use some help.

Summary of the issue:
My PC crashes only when in sleep mode or when just having woken up from sleep mode.
Before this crash started happening, my PC had Sleep greyed out from the options in the 'power options' menu, and had 'Hibernate' as an option instead. All was fine, I maybe had one BSOD once in the year and half of owning my custom built PC. Then, after performing a series of Windows 7 updates that I'd left to sit, the Sleep option was no longer greyed out and Hibernate was gone from my 'power option' menu. Huh. This seemed fine, until I noticed that my PC started crashing when in sleep mode or when waking up from sleep mode. It doesn't do this 100% of the time, but very frequently, probably around 80% of the time. When analysing crash logs it appeared to be a memory issue. But even after trying many solutions, it still does this.

So, this has in fact been an issue for over a year now. I have previous attempted to solve it using various BSOD tools but with no luck. So, for lack of an explanation, I left it (I know, bad, but I was out of ideas).

Yesterday, I discovered to my utter shock that my graphics card (an AMD Radeon 390) had stopped working completely. It seems to have blown (I attempted switching PCI slots, reinstalling drivers, see if the BIOS would recognise it, etc. but no luck). This may just be coincidence, but I want to solve my BSOD issue before introducing a new GPU to my PC.

I completely reinstalled Windows 7 from the original installation disk I had bought 3 years ago. I have disconnected my secondary HDD and my PC is currently running off only my SSD where Windows has been reinstalled. The SSD was formatted during the reinstall.

I was hoping a fresh install would solve my issue, and I left it nearly untouched - I only installed my driver for my new (bought a month ago) wifi adapter and drivers suggested with Windows update. No other drivers are installed at any point. And yet, my issue continues.

Because of this, I fear that it may be a hardware problem, but I can't figure out what piece of hardware may be causing the issue.

This is where I hope someone can give me some additional answers about my issue. I have attached my zipped up log of the one BSOD I had since my fresh install yesterday, and am happy to attach more info if needed.

It happened again today, unfortunately.

This was after removing one of my 2 RAM modules, so that RAM module was not the culprit. I updated and installed any drivers to any parts of the system that had drivers available (monitor/keyboard/mouse/intel graphics/etc.). All updates seem to be installed. Still no luck unfortunately.

I will be swapping for my other RAM module now to see if maybe that one is faulty.

It did manage to successfully wake up from Sleep after having been in Sleep mode all night (no programs running). It also didn't crash two times after. Then the second time I tested, I clicked my mouse to wake it up (as I always do) and immediately noticed my monitor would not wake up successfully, nor would my keyboard. Then I heard my PC 'stopping' it's usual wake up noises as it seemed to crash and restart.

I may attempt to install windows 10 if the problem persists and see if that makes any difference, as so far none of the solutions I have tried have worked.

A WhoCrashed report of the dump files:
Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 20/05/2018 14:30:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052018-4664-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA4470)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 20/05/2018 14:30:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KiCpuId+0xE1E)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 19/05/2018 11:00:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051918-7472-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4261)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002F95578, 0xFFFFF88002F94DE0, 0xFFFFF80002AB8E5C)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.