BSOD every day every time ...

Plenty of dumps here including 0x1A, 0x1000007E and 0x34. To me that looks like everything is pointing to RAM. Let's rule that out first.

Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Code:

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000b0

Code:

BugCheck 1A, {41790, fffffa80064b2d60, ffff, 0}

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

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80064b2d60
Arg3: 000000000000ffff
Arg4: 0000000000000000

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800f168ffd, fffff88002907218, fffff88002906a70}

Probably caused by : atikmdag.sys ( atikmdag+139ffd )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f168ffd, The address that the exception occurred at
Arg3: fffff88002907218, Exception Record Address
Arg4: fffff88002906a70, Context Record Address

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'mouhid' and 'crashdmp.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

The ATI driver has been flagged. Download the latest driver from here and save it to your desktop. Download DDU and follow Display Driver Uninstaller: How to use to remove all traces of your current driver. Reboot and install the downloaded driver.

Code:

fffff880`02906918  fffff880`042d9fe8
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0xbfe8


2: kd> lmvm atikmpag
start             end                 module name
fffff880`042ce000 fffff880`04376000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Jun 23 02:10:51 2015 (5588B21B)
    CheckSum:         000AA93B
    ImageSize:        000A8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

In short, yes. Your RAM stick is faulty and needs replacing. I'd recommend buying a 2x4GB kit, at least that way in future if one stick goes bad you can always fall back on the other stick in the interim.

It's not an ideal situation obviously but at least the culprit has been identified.

You shouldn't have to no, the tests you've run seem conclusive enough to blame the RAM stick itself. If you really want to you can just to prove the DIMM slots on the motherboard are OK.