Different BSOD each day

[icewolf461]

Hi. I just installed a fresh copy of Windows 10 on a new PC build and I've been having some blue screens. I have attached the minidumps and specs below. Any help is appreciated. Thanks!

Specs:

OS: Windows 10 64 Bit
RAM: 4GB DDR4
GPU: MSI GT 710 2GB
CPU: Intel G4560
PSU: EVGA 500W
HDD: 1TB WD 7200RPM

All parts are new except one secondary HDD 250 GB HDD that was reused.

Minidumps: https://drive.google.com/open?id=1Af1b4RTq8yzny8h_fJXZYyLcc43uMlTk

EDIT: I used WhoCrashed and pasted the analysis below:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Tue 5/8/2018 7:10:36 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050818-20437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803DC5FB971, 0xFFFF9A8066BA2520, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5/8/2018 7:10:36 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8529)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803DC5FB971, 0xFFFF9A8066BA2520, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 5/7/2018 3:30:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050718-22187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x1A (0x3F, 0x67836, 0xB53A6C5D, 0xB63A6C5D)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/6/2018 4:42:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050618-18015-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x3CCEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800250A7813, 0xFFFF8086F303E4A8, 0xFFFF8086F303DCF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

 

[DeadRam]

I think the memory is causing the blue screens. I've seen it before. I would disconnect the secondary hard drive and remove the video card if your MB has video. Try another stick of memory if you continue to get blue screens. Remove your memory when testing another memory stick.

 

[scout_03]

memtest ram i module at the time and check if you have all the latest driver for your system but would mostly go for a bad ram .