Windows 10: BSOD Constantly even when idle different error messages

My computer was built my a family member out of spare parts from their previous computers. They are an IT specialist and is very smart when it comes to IT. I use my computer for gaming mainly and general use aswell, i used to constantly get BSOD and i went to my family member for help, they bought a GTX1050 graphics card from a previous AMD and the problem was solved for a month or so. Now when im gaming or even while browsing the internet it always crashes. The most common error messages are "attempted to write read only memory" and "IRQL not less or equal" ive also had "kmode exception not handled" and "system service exception". I assumed it was to do with my memory but i ran troublebooting programs to see and they came back fine.


This is the text event viewer says:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The attachment is from bluescreenview.

:)

 

BSOD same time every day BAD_POOL_HEADER

Rats! It crashed again. I put the minidump from today's BSOD into dropbox - link is in first message in this chain.

So what's different from yesterday when it didn't BSOD?

- AVG is running

- network is running

- I had some applications open (2 browsers, 2 email clients, Skype (idling) and OO Writer

Now what?

Joe

 

Too many background processes running in Windows 10

Yeah, you can't delete them. They need to know what you are doing. My hard drive is whirring constantly, even when idle. this can't be right.

 

Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffe68ed86039d0, 2, 0, fffff80354cc3614} Probably caused by : memory_corruption Followup: memory_corruption ---------[/quote] Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {ffff8fc0055eaee4, 8000000001180121, ffffbd00187a4060, a} Probably caused by : memory_corruption Followup: memory_corruption ---------[/quote] The only tool that reliably test memory is MemTest86+. You need to run 8 complete passes.

Follow this tool:
MemTest86+ - Test RAM