Win 10 BSOD multiple causes

#1
Hi this is my first post here so please let me know if I left anything out. Since upgrading to windows 10 my computer has crashed with the blue screen. Every time I try and game I get the CRITICAL_PROCESS_DIED BSOD. I turned the graphics down on Diablo 3 and was able to run it for about an hour before inevitably the BSOD, anything else brings the crash almost instantly. Also just seemingly random it will give an UNEXPECTED_STORE_EXCEPTION. I have run the WF7 Diagnostic Tool and uploaded my results. Any help is greatly appreciated, Thanks!
 


Attachments

Neemobeer

Windows Forum Team
Staff member
#2
Did you run that as admin, it failed to get your DriverList.txt. Also looking at the dumps, most of them point to ntkrnlmp.exe and specifically csrss.exe with a bugcheck of EF
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffe0019e50f200, 0, 0, 0}

ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )

Followup:     MachineOwner
---------

0: kd> !analyze -show EF
CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: 0000000000000000, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_a07c6080_nt!PspCatchCriticalBreak
You may want to try running from an elevated command prompt
sfc /scannow

and

dism /online /cleanup-image /restorehealth

Also try to re-run the diag tool and upload the DriverList.txt file
 


Neemobeer

Windows Forum Team
Staff member
#3
The other driver failure I saw was srv.sys. This is the terminal services driver that allows people to connect to shares on your computer.

The bugcheck code 7A is KERNEL_DATA_INPAGE_ERROR, looking at the comments from !analyze -show 7A is states of you get a error_status 0xC000000E that there may be a failure with the disk subsystem. So your problems might be from the disk. Try to repair the OS with the above mentioned commands and you may also what to update your disk controller drivers and test your hard drive with a tool like Seagate SeaTools for failures.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {ffffc00021759e40, ffffffffc000000e, 1f54bb860, fffff8014185400e}

Probably caused by : srv.sys ( srv!TerminateServer+5d6 )

Followup:     MachineOwner
---------

3: kd> !analyze -show 7A
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#4
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffe0005a1de540, 0, 0, 0}

----- ETW minidump data unavailable-----
Probably caused by : svchost.exe

Followup: MachineOwner
Hi,
of the dump files sent you had two bugchecks 7F and the above. The above means, for whatever reason, a critical process died. Bugcheck 7F can have a number of causes ranging from mismatched or faulty hardware to driver issues.
Looking over the dumps nothing driver wise is mentioned although I notice your running Norton AV. This can always cause suspicion especially if it was installed at the time of upgrade.
Please uninstall Norton using the Norton removal Tool and just use the onboard Defender for now. You can always re-install later.
Uninstall your Norton product using Norton Removal Tool

You also need to update some drivers:
bcmwlhigh664.sys Fri Nov 06 00:27:07 2009: Broadcom 802.11 USB Network Adapter Driver please update:
NETGEAR Support | Downloads

HECIx64.sys Wed Oct 20 00:33:43 2010: Intel engine management driver. I checked your motherboard support page and they do have drivers for Windows 10 :
GIGABYTE - Motherboard - Socket 1155 - GA-Z68X-UD3H-B3 (rev. 1.0) (please ensure I have the correct revision number for your board)
Update the 'Inf' too.
Run the scans as advised by Neemobeer above.

If the above changes nothing then we could try the driver verifier but first you'll need to make a recovery disk/USB. You'll need that in case the verifier causes a bsod on start up. If it does you then use the recovery disk/usb to boot into safe mode and turn the verifier off.
Recovery
Creating a recovery drive - Windows Help -
Verifier
How do I fix a Blue Screen in Windows using Driver Verifier?

If the verifier does cause a bsod then the culprit will hopefully be caught on the dump file. There is also a slight chance that your issue might be RAM related but we'll cross that bridge if the above comes to nothing.

Post any new dump files.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.