Constant BSOD since 2 days after installing new Hardware

Okay, so here comes 9 BSODs minidumps + the logs from the app you made me install.

All my drivers are updated except my old printer driver and my Realtek drivers.

Computer specs are in my info but, since I know what kind of people we are, I'll put them here anyway:

CPU: AMD A10-7890k (New) (Before : AMD A6-6400k)
GPU: Sapphire Radeon R7 240 2Gb DDR3
Motherboard: Asus A88XM-A
RAM: F3-2133C9D-16GXH
OS: Windows 10 Pro, upgraded from Windows 7 Ultimate
PSU: Extreme 2 525W

On the 12/06/2016, I switched my CPU, booted up the PC and all was working. Up to 14/06/2016, when the BSODs started.
I've used Driver Verifier and thought I found the culprit and uninstalled it. The logs from the 15th and 16th aren't included since I rolled back the Pc to the restore point on the 14th and kinda forgot to backup them.

I've ran RAM tests and HDD test to find if there was any corruption in it, both came up negative. The GPU shouldn't be the issue, since I haven't touched it since I built the Pc 2 years ago, apart from when I last cleaned the inside of the PC 3 weeks ago.

Symptoms: Random BSODs at totally random times. I can use the Pc for 5 hours and it won't crash, or I use it for 15 minutes then it could crash after reboot. Also, it seems the PC get stuck on the BSOD screen and doesn't auto-restart, sometimes staying there for 40 minutes before I lose patience and manually restart with the power button. It BSOD'd when idled, when playing games or even when browsing Internet, while I was searching for ways to see how I can fix the PC. Or on Facebook. It crashed on Chrome / Firefox.

I've just updated my AMD catalyst to a beta release about 2 mins ago, I'll keep you posted if the BSODs stopped.

With respect,
Morduparlevent

Edit: Well, scratch the 9 minidumps, they now are 11. Uploaded the new version of the files. And the updated AMD Catalyst didn't fix the issues I'm having.

Have you touched the RAM when you changed the CPU?

You need to set the RAM as dual channel. Put the RAM sticks in the slots of the same color. Either Black or Yellow.

Attachment 90736

Different channel number, same DIMM number for dual channel, which, theoretically gives you the real full bandwidth of the RAM.

If the issue persists, do some hardware tests:

► Test your RAM modules for possible errors.

MemTest86+ - Test RAM

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.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

► Stress test the Graphics Card using Furmark.

FurMark - GPU Stress Test

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

► Stress test the CPU.

Prime95 - Stress Test Your CPU

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Let us know the results.

morduparlevent said:

Ehrm. Quick question, would it be possible that a BIOS update would be required?

If yes, then how do I update a A88XM-A bios?

Your Installed BIOS:

Code:

BiosVersion = 0603
BiosReleaseDate = 10/16/2013

The latest BIOS available for your motherboard is Version 3001 dated 2016/04/08.

Yes, BIOS update does some good there.

As you are asking me "how to update the BIOS", it gives me a clear idea that you are unaware of the process. In that case I would request you to not do it yourself. Because BIOS update is very risky. If a little mistake takes place there, that may damage the motherboard permanently and render it totally useless.

If you want to update the BIOS, get some real help. See if any of your friends or family can do it. If nobody is available, ask a professional to do it for you.

Not seeing any obvious BSOD during furmark running. Did you face it actually? Please let us know.

And, please consider the memtest+ test. It seems that it would be necessary.
____________________________________________________________________________________________________ _______

Code:

BugCheck 4E, {9a, 19106f, 2, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+359e5 )

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

Code:

BugCheck BE, {fffff9618dcb669c, 49c000010b21e021, ffffd000fcef1750, b}

Probably caused by : win32kfull.sys ( win32kfull!TimersProc+17f )

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

Code:

BugCheck 139, {3, ffffd001039127c0, ffffd00103912718, 0}

Probably caused by : cdd.dll ( cdd!CStagingPoolBase::AllocateRect+230 )

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