Windows 10: Help fixing BSOD possibly caused by memory corruption or bad drivers?

I have recently started getting a bunch of BSOD, and at first, when I went to go check why they happened in the system services, it said it had something to do with my Nvidia drivers. I was told to uninstall my drivers with DDU, and I did that. I thought that would be the end of this issue, but last night the computer crashed again, and the event viewer read:The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 0xffffd28173b3a010, 0xfffff803574c0790, 0xffffffffc000009a, 0x0000000000000004. A dump was saved in: C:\WINDOWS\Minidump\021825-99703-01.dmp. Report Id: 980016bd-d82

:)

 

BSOD - I'm very frustrated


Memory corruption doesn't necessarily mean hardware, it is more often caused by drivers passing data to the wrong memory address but a memory test is still suggested to ensure it is not the cause.

With memory corruption the most occuring causes are:

• Drivers,
• Memory,
• SSD (firmware more often than the SSD itself bad),
• HDD,
• GPU, in this case we should see some DirectX stuff back in the stacks or similar drivers.

Then there is also the possibility that the

• CPU,
• SATA/IDE controller,
• mainboard &
• PSU,

can cause memory corruption, though most of these are pretty rare occuring when we see memory corruption.
I've seen only once the PSU causing memory corruption because of a loose cable, a few times the CPU and a few times the mainboard.

 

BSODs with corrupt pagefile - Is That Possible?

Past couple of days I have been having random BSODS. A few examples of the messages was - Memory management / IRQL less than or equal to/ Thread could not be activated/ Page Pool something or other.

First BSODS I have had on this relatively new system so decided to take everything back to stock and test each part. I'm on Windows 7 Ultimate 64bit BTW.

HDtune error check - fine
Memtest86 - 10 passes fine
Prime 95 - 7hrs overnight fine
Graphics card - furmark/3DMark fine

Go to play a bit of WOW last night and it locks up straight away with memory management issue. So I looked into it a bit and read that it could possibly be a virtual memory/pagefile issue and that if it is corrupted it may cause these issues.

I then set the pagefile to zero and enabled clear pagefile on shutdown in the registry. When it rebooted I let the amount be set by Windows and disabled the registry entry for clearing it on shutdown and will see how it goes.

I had never heard of this issue before causing BSODS, is it common and what should be the next step if I get another one today with the new pagefile in place?

 

BSODs trying to update graphics driver

That it is a hardware error is clear and good to know that you've found the cause, but why did you enable driver verifier?
Code:

Nope, it is saying something caused memory corruption. Memory corruption isn't specific RAM:

From BSOD to Windows Crash