Daily BSOD errors [ Windows 10 - Desktop]

Maximus24

Solid State Member
Messages
8
Location
United States
This all started happening when I upgraded to the Windows 10 10130 (When it was still in beta) . I never had daily BSOD errors before, now it's become a daily routine of me getting them mid-way between doing something.

Specifications of my PC ;
http://i.imgur.com/jiS4IGW.png [ CPU - Info ]
http://i.imgur.com/isLx1EX.png [ RAM - Info]
http://i.imgur.com/QfXd6Kb.png [ Motherboard - Info ]
http://i.imgur.com/XHDWK2E.png [ Graphics - Info ]
http://i.imgur.com/5xFg8Ue.png [ Storage - Info ]

Side Note : I'll upload screenshots of BSOD when I get them.
 
Last edited by a moderator:
If you have any dump files under C:\Windows\Minidump then please upload those as well - those will be more useful than screenshots alone.

Also...for WIn10 users that are having issues after the upgrade...I'm pretty much just suggesting trying to do clean install to make sure nothing got messed up during the upgrade.
 
If you have any dump files under C:\Windows\Minidump then please upload those as well - those will be more useful than screenshots alone.

Also...for WIn10 users that are having issues after the upgrade...I'm pretty much just suggesting trying to do clean install to make sure nothing got messed up during the upgrade.

I agree, given it sounds like he upgraded from beta to release, most likely something went wrong.
 
Hi! I really like this program for BSOD! Anyone familiar with Who Crashed.
Download WhoCrashed Free Home Edition - MajorGeeks
Dump files would be good!!

WhoCrashed shows the drivers which have been crashing your computer with a single click. In most cases it can pinpoint the offending drivers which have been causing misery on your computer system in the past. It does post-mortem crashdump analysis and presents all gathered information in a comprehensible way. Normally, debugging skills and a set of debugging tools are required to do post-mortem crash dump analysis. By using this utility you do not need any debugging skills to be able to find out what drivers are causing trouble to your computer.
 
Last edited:
(Mods ignore my last post for review, this will be my new post)

I used WhoCrashed and will just show their results so you guys don't have to download anything.

Picture 1 - http://i.imgur.com/yqVJ2kA.png
Picture 2 - http://i.imgur.com/V5SMdYn.png
Picture 3 - http://i.imgur.com/nWbtuee.png

Tell me if you need anything else.

Side-note : I cleaned my computer with an air duster to blow out any dust on my parts and fans. I put my RAM module on another slot but I don't think my RAM is the problem as it seemed undamaged. I also cleaned my CPU Fan. I don't really know what to do anymore.
 
I'll analyze them with WinDbg later when I have more time, but from the looks of it, it may be because of a RAM problem.

I'd suggest burning this to a CD, and boot off of it:
Memtest86+ - Advanced Memory Diagnostic Tool

Let it run for a minimum of 4 hours (longer the better, over night is best). If you get any errors at all...then there's faulty RAM. You'll then need to test each stick individually to find out which stick (or slot) is the problematic one.
 
I agree with carnage! Here's a good read about BSOD!
Resplendence Software - WhoCrashed, automatic crash dump analyzer
PS I know carnage doesn't need me to agree, but I agree any way!!
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
A very common case of system crashes is memory corruption. Memory corruption often finds its cause in software and is caused by buggy drivers. Memory corruption may cause the wrong driver to become identified as responsible for crashing a system because drivers are privileged to access and corrupt each others memory. While more often the problem lies in software, memory corruption can also be caused by faulty or bad configured RAM modules. Most recent versions of Windows come with a memory test utility which can check your RAM modules for errors by pressing F8 during system startup. This will help you single out this problem as the possible cause.
 
Last edited:
Back
Top Bottom