Need Assistance with Blue Screen Error I can't figure out.

[MightyMulligan]

Source
Windows

Summary
Shut down unexpectedly

Date
‎5/‎10/‎2016 7:57 PM

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Extra information about the problem
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002CAB892
BCP3: FFFFF880031E06D8
BCP4: FFFFF880031DFF30
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

This is the error report I have gotten three times today while playing star wars battlefront. These blue screens are not a new occurrence as these have happened occasionally. My temps were 50ish degrees on crash and my drivers are up to date. What do?

 

[Colif]

try the suggestions here: http://www.tomshardware.com/answers/id-2329865/blue-screen-crash-1000007e.html

 

[MightyMulligan]

I attempted the first part by running a file check and the cmd system check and nothing was out of the ordinary. However, I don't quite understand what the second part is saying. I gave the verifier.exe method a go, but when I opened it, I really had no idea what I was doing. If there are some step by step instructions to go about solving this issue, I would be ecstatic.

 

[Colif]

this bit?

if all of these procedures don't turn up anything, then you want to post your actual memory dump file on a server to be looked at with a windows debugger.
a person can dump the list of drivers and sometimes we just see the same driver causing the same problem over and over and can tell you what it is.

I don't know if you want the entire memory dump as mine is 1gb, but you can set it to create minidumps instead

Follow option one here - Configure Dump File Settings in Start-up and Recovery
and then do >> Have Windows Create a Small Memory Dump (Minidump) on BSOD
From this web site: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html

The dump files can be found in c/Windows/MInidump
Copy them from here and put in my documents, and then upload that file to a cloud server and share a link here

minidump is only a few hundred kb at most, the actual dumps can be massive.

 

[MightyMulligan]

https://www.dropbox.com/s/yt5wny02bl994vh/051016-5163-01%20-%20Copy.dmp?dl=0

https://www.dropbox.com/s/7bur0i8nvorzjer/051016-7831-01%20-%20Copy.dmp?dl=0

https://www.dropbox.com/s/id249avesgw8qmy/051016-7862-01%20-%20Copy.dmp?dl=0


Here is the set of 3 mini dumps,

 

[Colif]

now I am not ignoring post, I just can't read the dumps. I will let someone who can read them for you

 

[ForensicObject446]

I have processed the dumps and it appears that ntoskrnl.sys and win32k.sys are causing the BSOD's which I believe it could be faulty RAM sticks. Have you got spare RAM sticks sitting around? If not then maybe it's time to buy new ones since these are probably starting to die out. Try to take one stick out at a time just to make sure first

 

[Colif]

use this to test ram: http://www.memtest86.com/

isn't it misleading to blame those two, they being pressured to crash by something else, ntoskrnl is always blamed for crashes as its the heart of windows and has to deal with driver requests. Not precisely sure what the other one does.

 

[MightyMulligan]

When using memtest86, what should I be looking for if it is the RAM's issue? Sorry, this is just brand new territory for me. I'm assuming I have to do the full 1-13 Tests. That will take a little while but 'll do it. I also unfortunately do not have extra RAM lying around to test.

 

[MightyMulligan]

I ran 4 passes of all 13 tests for memtest86 and it didn't find any errors.

 

[ForensicObject446]

Normally memtest wouldn't find errors, however there could be faults that programs can never find. There may be another problem though related to it.