New Custom Built PC BSOD- IRQL_NOT_LESS_OR_EQUAL

[theblueyowie]

Hi everyone,
Recently I built a new PC for gaming, however since then I have found that one of my RAM sticks was faulty so I removed it but now I've been getting BSOD's every day or so.
I'm running Windows 7 Ultimate 64bit and the majority of my BSODs have the 'IRQL_NOT_LESS_OR_EQUAL' error. The latest BSOD has also identified atikmdag.sys but the others just refer to ntoskrnl.exe
I'm currently running the 15.4 Beta version of AMD Catalyst, but I have tried about 4 other versions including the current stable release.
Any help would be appreciated.
Thanks.
EDIT: I have run memtest on my current 4gb RAM stick and it has shown no error

 

[Arc]

22 bytes is the folder header only, the upload is empty.

Follow Blue Screen of Death (BSOD) Posting Instructions once again and attach the resulting zip with your reply post.

 

[GokAy]

(If applicable in UEFI) Did you load defaults in BIOS, or optimized settings if there is one? Clear CMOS?

 

[theblueyowie]

Apologies I didn't even think think to check that the program had worked properly. Attached is the correct dump files now.

 

[Arc]

There is a chance that the display driver is contributing to the BSOD, but all the crash dumps are steadily reporting a memory corruption.

BugCheck A, {fffffa8c018ca1ea, 2, 0, fffff800032866f7}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiPfnShareCountIsZero+77 )

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

In that case testing the RAM modules would be the first thing. I noticed what you stated there ....

EDIT: I have run memtest on my current 4gb RAM stick and it has shown no error

.... but do it again, right just as suggested .....

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. The best way of reporting the result would be a camera snap of the memtest86+ window before closing the program.

 

[theblueyowie]

I've reset the CMOS and I'll run a mem test and post an image of the results tomorrow

EDIT: Overnight Memtest completed 11 passes with no errors, what else could be causing the memory corruption?