Got rid of blue screens, getting them again 10 days later

ZStevens · 31 Jan 2016

I was having BSODs all throughout December then I came here for help. The problem seemed to be fixed when I didn't have a crash for 10 days, and now it crashes frequently. I'm worried there might be a new issue.

My previous post is here for a little more information: SYSTEM_SERVICE_EXCEPTION (win32kfull.sys), atikmdag.sys, etc - Windows 10 Forums

And the new debug file: Attachment 61797

axe0 · 01 Feb 2016

Please remove Esupport software, it is the same as with DriverAssist...
If any driver is installed with this scam program, remove them.
When the drivers are removed, if any is installed, and you're still experiencing problems run driver verifier

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

ZStevens · 02 Feb 2016

I have no idea if I installed a driver with that program. Is there a way for me to find out?

axe0 · 03 Feb 2016

Check the restore points in recovery in control panel.
If there is 1 (or more) created by the program (as they usually create restore points) then there are drivers installed from that program.

ZStevens · 05 Feb 2016

All right, I found and deleted two drivers that were both hidden so I had no idea they existed (Intel graphics (ew?) and some Microsoft 2006 port (EW?). Ran Driver Verifier for 48 hours and had no blue screens.

Is there anything else I should do or am I probably totally done with this problem for now?

axe0 · 05 Feb 2016

Currently you need to test your system and repot any bluescreen (hope none)

ZStevens · 05 Feb 2016

axe0 said:

test your system

I'm not really sure what you mean by that. I tried searching around and found nothing.

Edit: Oh, do you literally mean just continue to use it and see if it crashes on me? Okay, sounds easy enough

axe0 · 06 Feb 2016

That is what I meant yes, just use the system and see if it crashes

ZStevens · 06 Feb 2016

Crashed again on me last night while playing a game

Attachment 62835

axe0 · 07 Feb 2016

Just to be sure the memory is NOT the cause.

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck A, {a, 2, 1, fffff800ddedf9c4}


Probably caused by : memory_corruption


Followup: memory_corruption