Bsod irql_not_less_or_equal/memory_management

Hi there! Im experiencing BSOD's frome quite some time now, it doesn't really matter if im gaming (recently i started playing Watch Dogs just to do some stress tests) and it can run flawlessly for hours sometimes, other times it crashes on intro or while im browsing the net or installing new software.
System is freshly reinstalled (that's why i sent so few dumps), drivers are from the manufacturer's site, only exeption is INF driver which i installed from CD this time just to test (i have installed the latest one on my previous instance but still got BSOD's). I tried running it on single DRAM stick and had no problem for a whole day (haven't got the time to test it for a longer period of time yet). Did memtest and passed 9 stages (couldn't run it for longer cause i needed PC to work). DRAM voltage is set to 1.65V.
Im running sfc /scannow as we speak. Did intel's CPU test and it passed. I read somewhere that connecting HDD's to sata2 slots instead of sata3 might help, but not in this case

If u have the patience and would be kind enough to help me I would be forever in your debt :)
PS. Sorry if my syntax is a bit off. English is my second language.

EDIT: IT bsod'ed again while i was typing this (using browser and installing a game in background)
EDIT2: sfc scan did not find anything
EDIT3: I tried to reset CMOS, got a BSOD in a minute after booting. Now im trying with DRAM set to 1066Mhz

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap of the memtest86+ window will be nice as the reporting.
____________________________________________________

Code:

BugCheck A, {fffffa8fc1a682d0, 2, 1, fffff80002f0be74}

Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+328 )

Followup: MachineOwner
---------

Ebonshade said:

Do you know of any virtual drive programs that aren't common to cause BSOD by any chance?

No. There is no such program.

But, there is an inbuilt mount ISO option for windows 10, which is apparently safe.

Attachment 364831

With both sticks installed, I got an error after 1st pass on test 7. Can post a snap later. In on my mobile and it won't let me upload images directly for some reason. Starting a memtest on a single DRAM stick now.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.

It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.

It is a motherboard issue. The particular slot is bad.

If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.

You are welcome. Let us know for any further issue.