BSOD's in windows 10 help

Samantha_10

Reputable
Jan 9, 2016
5
0
4,510
Hi, ive been having bsod's once or twice a day with various different messeges, which i believe its a driver problem, at first thought it was nvidia so reinstalled nvidia drivers, then even reverted to older nvidia driver, nothing helped, then reinstalled windows 10 cleanly, still bsod, then swapped the ram, nothing then swapped power supply, so far nothing i do seems to fix it. i just cant pin it down, and i dont know how to read minidump files, ill link the ones i have, maybe you all can find something im missing, also ive reset bios, ive reset overclocks back to normal, this started happening like 1-2 weeks ago.

heres a link to a folder with a few minidumps, hopefully with a few minidumps can pin down the culprit

https://www.dropbox.com/sh/qn936vzlntss124/AADaYVZDkl3Q7gYyDbA_bLW1a?dl=0

Sys Specs

I5 - 4670K
16 GB DDR 3 1600
GTX 780
256 samsung evo 840 OS Drive
500gb HDD
Asus Z87-A
 
Solution
You're right about it being a driver issue as one of the culprits to pop up is FLTMGR.SYS. Though I'd ask you to perform a system restore to a point prior to when the issue cropped up likewise you could try and perform a repair install. It may be possible that the automatic device driver updates might have been broken. Have you made sure your BIOS and remaining device drivers(excluding graphics card) are up to date?

With Bluescreenview, all I can see is ntoskrnl.exe and FLTMGR.SYS as your culprits though the former is not the origin of the issue.

Lutfij

Titan
Moderator
You're right about it being a driver issue as one of the culprits to pop up is FLTMGR.SYS. Though I'd ask you to perform a system restore to a point prior to when the issue cropped up likewise you could try and perform a repair install. It may be possible that the automatic device driver updates might have been broken. Have you made sure your BIOS and remaining device drivers(excluding graphics card) are up to date?

With Bluescreenview, all I can see is ntoskrnl.exe and FLTMGR.SYS as your culprits though the former is not the origin of the issue.
 
Solution