BSOD

Question

BSOD

Anonymous

Split from this thread.

I've just had the same. Resuming from sleep whilst inserting a bluray in the drive. Nothing else running.

Feedback submitted.

Microsoft (R) Windows Debugger Version 10.0.17074.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\042518-7937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`ed809000 PsLoadedModuleList = 0xfffff800`edbc62f0
Debug session time: Wed Apr 25 12:40:28.630 2018 (UTC + 1:00)
System Uptime: 3 days 2:07:43.559
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffb8817184e580, 0, 0, 0}

Probably caused by : psmserviceexthost.dll

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

nt!KeBugCheckEx:
fffff800`ed9a0650 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8206`4e17f840=00000000000000ef
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffb8817184e580, 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

Debugging Details:
------------------

KEY_VALUES_STRING: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.17134.1 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Acer

SYSTEM_PRODUCT_NAME:  Predator G9-791

SYSTEM_SKU:  Predator G9-791_105B_1.11

SYSTEM_VERSION:  V1.11

BIOS_VENDOR:  Acer

BIOS_VERSION:  V1.11

BIOS_DATE:  10/16/2017

BASEBOARD_MANUFACTURER:  Acer

BASEBOARD_PRODUCT:  Challenger_SLS

BASEBOARD_VERSION:  V1.11

DUMP_TYPE:  2

BUGCHECK_P1: ffffb8817184e580

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

EXCEPTION_CODE: (NTSTATUS) 0x74e64040 - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0x74e64040 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID:  {e9b83e85-fb67-4947-9c14-35ac8da49b12}

IMAGE_NAME:  psmserviceexthost.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: psmserviceexthost

FAULTING_MODULE: 0000000000000000 

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: BE'00000000 (cache) BE'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xEF

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  PREDATOR17

ANALYSIS_SESSION_TIME:  04-25-2018 12:45:03.0225

ANALYSIS_VERSION: 10.0.17074.1002 amd64fre

LAST_CONTROL_TRANSFER:  from fffff800edf98011 to fffff800ed9a0650

STACK_TEXT:  
ffff8206`4e17f838 fffff800`edf98011 : 00000000`000000ef ffffb881`7184e580 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8206`4e17f840 fffff800`ede846f7 : 00000000`00000000 fffff800`ed8ee241 ffffb881`7184e580 00000000`c0000005 : nt!PspCatchCriticalBreak+0xfd
ffff8206`4e17f8e0 fffff800`edd74144 : ffffb881`00000000 00000000`00000000 ffffb881`7184e580 ffffb881`7184e858 : nt!PspTerminateAllThreads+0x1c0b9b
ffff8206`4e17f950 fffff800`edd73f05 : ffffffff`ffffffff ffff8206`4e17fa80 ffffb881`7184e580 fffff800`edd4bf01 : nt!PspTerminateProcess+0xe0
ffff8206`4e17f990 fffff800`ed9b2f13 : ffffb881`00000054 ffffb881`74e64040 ffffb881`7184e580 00000090`82fff90c : nt!NtTerminateProcess+0xa9
ffff8206`4e17fa00 00007ffd`2fb8a514 : 00007ffd`2fbf9043 00000000`00000000 00007ffd`2fc24754 00000090`82fff90c : nt!KiSystemServiceCopyEnd+0x13
00000090`82ffd5b8 00007ffd`2fbf9043 : 00000000`00000000 00007ffd`2fc24754 00000090`82fff90c 00000090`82ffd660 : 0x00007ffd`2fb8a514
00000090`82ffd5c0 00000000`00000000 : 00007ffd`2fc24754 00000090`82fff90c 00000090`82ffd660 00000000`00000002 : 0x00007ffd`2fbf9043

THREAD_SHA1_HASH_MOD_FUNC:  042a2b51772309c39e12d732cc93cacf0af3064e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9fd40ed8852f8717f13ce860d4315ce597598c47

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_NAME:  MachineOwner

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_74e64040_psmserviceexthost.dll!?HampHostComputeStaticEnforcementSettings@@YAXPEAU_RM_HAM_ACTIVITY_HOST@@PEAU_RM_ENFORCEMENT_SETTINGS@@PEAU_RM_COMMIT_THRESHOLDS@@2PEAPEAU_HAM_ACTIVITY@@@Z_IMAGE_psmserviceexthost.dll

BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_74e64040_psmserviceexthost.dll!?HampHostComputeStaticEnforcementSettings@@YAXPEAU_RM_HAM_ACTIVITY_HOST@@PEAU_RM_ENFORCEMENT_SETTINGS@@PEAU_RM_COMMIT_THRESHOLDS@@2PEAPEAU_HAM_ACTIVITY@@@Z_IMAGE_psmserviceexthost.dll

PRIMARY_PROBLEM_CLASS:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_74e64040_psmserviceexthost.dll!?HampHostComputeStaticEnforcementSettings@@YAXPEAU_RM_HAM_ACTIVITY_HOST@@PEAU_RM_ENFORCEMENT_SETTINGS@@PEAU_RM_COMMIT_THRESHOLDS@@2PEAPEAU_HAM_ACTIVITY@@@Z_IMAGE_psmserviceexthost.dll

TARGET_TIME:  2018-04-25T11:40:28.000Z

OSBUILD:  17134

OSSERVICEPACK:  1

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-04-11 05:04:54

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.1

ANALYSIS_SESSION_ELAPSED_TIME:  12cb

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xef_svchost.exe_bugcheck_critical_process_74e64040_psmserviceexthost.dll!?hamphostcomputestaticenforcementsettings@@yaxpeau_rm_ham_activity_host@@peau_rm_enforcement_settings@@peau_rm_commit_thresholds@@2peapeau_ham_activity@@@z_image_psmserviceexthost.dll

FAILURE_ID_HASH:  {c30f3604-c38a-9859-0cd4-4fcdad702e38}

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Answer 1

Anonymous

Sorry, the system deleted my minidump. Hasn't occurred again though. Will update here if it does. Thanks, Andy.

0 comments

Answer 2

Anonymous

Hi,

Were you able to resolve the BSOD issue.

Hope this helps.

Rob Brown - Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

0 comments

Answer 3

Hi,

We do need the actual minidump files to analyze, see below.

Remove ALL power then reseat the cards, memory, and cables (on both ends when possible).

How To Reseat Expansion Cards

http://pcsupport.about.com/od/fixtheproblem/ss/reseat-excards.htm

How to Reseat a Desktop Memory Module

http://pcsupport.about.com/od/fixtheproblem/ss/reseat\_memory.htm

How to Reseat Internal Data and Power Cables

http://pcsupport.about.com/od/fixtheproblem/ss/reseat-power-cables-data-cables.htm

Reseating your RAM, Video Card, and Hard Drive

http://www.youtube.com/watch?v=DLxNPBQBfT8

Troubleshoot blue screen errors <-- read this link ****http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Keep in mind that the odds are hardware is involved and you can't fix hardware with software. **We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire).**If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.

Adding files to your OneDrive

http://windows.microsoft.com/en-us/windows-8/getting-started-onedrive-tutorial

Upload photos and files

http://windows.microsoft.com/en-us/onedrive/add-photos-filesOne-Drive - Share files and folders and change permissions

http://windows.microsoft.com/en-us/onedrive/share-file-folder

Zip or upload the contents of C:\Windows\minidump

Use OneDrive to upload collected files

http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

**** BCCode: EF 0x0000000EF <-- read this link

http://www.faultwire.com/solutions-fatal\_error/The-kernel-attempted-to-ready-a-thread-that-was-in-an-0x000000EF-\*1237.html?order=date

==================================================

This utility makes it easy to see which versions are loaded :

Run DriverView - set VIEW to Hide Microsoft drivers - update those without

Dump in their names (and update BIOS and chipset drivers).

DriverView - Free - utility displays the list of all device drivers currently loaded

on your system. For each driver in the list, additional useful information is

displayed: load address of the driver, description, version, product name,

company that created the driver, and more.

http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the

most current. Right Click the Start Button - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's

tab - write down the version info. Now click UPdate Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard

if 3rd party with their own software and drivers and any other major device drivers

you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and

then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their

latest versions. (Look for BIOS, Chipset, and software updates at System Maker's

site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AS ADMIN -

REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are

installing actually shows up. This is because some drivers rollback before the

latest is installed (sound drivers particularly do this) so install a driver - reboot

check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -

check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

====================================================

Memory tests do not catch all errors such as mismatched memory (possible even

for sticks that appear to be identical) and when faster memory is placed in system

behind slower memory. So it is best to also swap sticks in and out to check for

those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so. <-- best methodwww.memtest.org

MemTestX86 - Test RAM With

http://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

For the Windows Memory Diagnostic Tool.

Type in Cortana's search box -> Windows Memory Diagnostics

at top of list - click it. in Windows 8/8.1/10 the name is "Windows MemoryDiagnostic".

================================================

After doing ALL the updates you can, and if the issue continues, then run

DriverVerifier.

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users

http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

are essentially the same).

http://www.winvistaclub.com/t79.html

Using Driver Verifier

https://msdn.microsoft.com/en-us/library/windows/hardware/ff545448%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

Use BlueScreenView to see if there is a driver specified in the error message.

Also check with MyEventViewer at the time of the BlueScreen.

If DriverVerifier creates a minidump upload it and post the link here so we can

analyze it.

Hope this helps.

Rob Brown - Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

Share via

BSOD

3 answers