BSOD issue, crashes during shut down...

sno543 · 18 Sep 2015

cannot do a full system scan without it crashing and restarting. This is the error I get...

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

Additional information about the problem:
BCCode: 9f
BCP1: 00000004
BCP2: 00000258
BCP3: 8479B798
BCP4: 82F3AB24
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I have had problems installing Windows Updates but have managed to finally get everything updated. I have also updated the drivers on this pc.

I have installed and ran Microsoft Security Essentials. I could only do a quick scan because running the full scan, the computer would crash and restart in the middle. I tried 3 times.

I ran the anti-root utility, nothing found.

I ran the system file checker, everything ok.

I also ran a disk check.

According to WhoCrashed, these are my issues.

On Fri 9/18/2015 12:29:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091715-31090-01.dmp
This was probably caused by the following module: wwanusbmp.sys (WwanUsbMp+0x22FAD)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF84D9A020, 0xFFFFFFFF82F39B24)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\drivers\wwanusbmp.sys
product: Ericsson Mobile Broadband Module
company: Ericsson AB
description: Ericsson WWAN Wireless Module Device Driver
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: wwanusbmp.sys (Ericsson WWAN Wireless Module Device Driver, Ericsson AB).
Google query: Ericsson AB DRIVER_POWER_STATE_FAILURE

On Fri 9/18/2015 12:29:44 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0xDFB84)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF84D9A020, 0xFFFFFFFF82F39B24)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe DRIVER_POWER_STATE_FAILURE

On Thu 9/17/2015 9:25:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091715-25833-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x775C6)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF8479B020, 0xFFFFFFFF8078ADF4)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 9/17/2015 11:52:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091715-25552-01.dmp
This was probably caused by the following module: wwanusbmp.sys (WwanUsbMp+0x22FAD)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF8479C4C0, 0xFFFFFFFF8078ADF4)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\drivers\wwanusbmp.sys
product: Ericsson Mobile Broadband Module
company: Ericsson AB
description: Ericsson WWAN Wireless Module Device Driver
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: wwanusbmp.sys (Ericsson WWAN Wireless Module Device Driver, Ericsson AB).
Google query: Ericsson AB DRIVER_POWER_STATE_FAILURE

On Thu 9/17/2015 7:56:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091715-23602-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x775C6)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF8479BD48, 0xFFFFFFFF82F36B24)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I'm not sure what else to do. I got the computer through AT&T with a data plan which I do not have anymore. I would like to update this and be able to upgrade it to Windows 10. I mainly want to use it over wifi to watch Netflix. As it is now, Netflix runs very choppy. Plus Windows 10 says EMSC is not compatable with it. I don't know what that is and do I need it?

Thanks in advance.

koolkat77 · 19 Sep 2015

Any idea what software this driver belongs to?

Code:

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


Loading Dump File [C:\Users\KOOLKAT77\Downloads\SHERRI-PC-Thu_09_17_2015_234127_24\091015-120183-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18933.x86fre.win7sp1_gdr.150715-0600
Machine Name:
Kernel base = 0x82e1a000 PsLoadedModuleList = 0x82f65e30
Debug session time: Thu Sep 10 15:07:28.170 2015 (UTC + 6:00)
System Uptime: 0 days 3:24:46.433
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 8479da70, 82f43b24}

*** WARNING: Unable to verify timestamp for WwanUsbMp.sys
*** ERROR: Module load completed but symbols could not be loaded for WwanUsbMp.sys
Implicit thread is now 8479da70
Probably caused by : WwanUsbMp.sys ( WwanUsbMp+22fad )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 00000258, Timeout in seconds.
Arg3: 8479da70, The thread currently holding on to the Pnp lock.
Arg4: 82f43b24, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now 8479da70

DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  8479da70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LOCK_ADDRESS:  82f83540 -- (!locks 82f83540)

Resource @ nt!PiEngineLock (0x82f83540)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0x82f83540
	Thread Count  : 0
	Thread address: 0x00000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82e9888d to 82e915c6

STACK_TEXT:  
89517390 82e9888d 8479da70 00000000 82f46e20 nt!KiSwapContext+0x26
895173c8 82e976eb 8479db30 8479da70 89517488 nt!KiSwapThread+0x266
895173f0 82e90f1f 8479da70 8479db30 00000000 nt!KiCommitThreadWait+0x1df
89517468 8768def5 89517488 00000000 00000000 nt!KeWaitForSingleObject+0x393
895174b0 97100fad 000003e8 971100a0 c0000001 ndis!NdisMSleep+0x55
WARNING: Stack unwind information not available. Following frames may be wrong.
895174c8 971150bd 00133211 00000005 895176a8 WwanUsbMp+0x22fad
89517628 87690cf2 868d90e0 00000000 89517680 WwanUsbMp+0x370bd
895178f4 87690474 8607c5e8 868d90e0 8604f2f0 ndis!ndisMInitializeAdapter+0x76b
8951792c 876902ed 8607c5e8 868d9028 85e3bde0 ndis!ndisInitializeAdapter+0x10a
89517954 87695dbb 868d9028 85f33734 85f33758 ndis!ndisPnPStartDevice+0x130
89517998 82e50d7d 868d9028 85f33538 89517a20 ndis!ndisPnPDispatch+0x6c7
895179b0 82fdb652 00000000 8561d258 88adc788 nt!IofCallDriver+0x63
895179cc 82e2c39c 895179fc 82e2f18b 88adc788 nt!PnpAsynchronousCall+0x92
89517a30 82fd24cf 82e2f18b 88adc788 86adbb70 nt!PnpStartDevice+0xe1
89517a8c 82fd2398 88adc788 00000032 00000000 nt!PnpStartDeviceNode+0x12c
89517aa8 82fd9d9a 00000000 00000000 86ea02e0 nt!PipProcessStartPhase1+0x62
89517ca4 82fdad01 863047c8 86ea02e0 89517cd0 nt!PipProcessDevNodeTree+0x188
89517cd8 82e2edfc 82f81460 8479da70 82f574bc nt!PiProcessReenumeration+0x74
89517d00 82e97c9b 00000000 00000000 8479da70 nt!PnpDeviceActionWorker+0x224
89517d50 8302611f 00000001 90ba39b5 00000000 nt!ExpWorkerThread+0x10d
89517d90 82ecb439 82e97b8e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .thread 0xffffffff8479da70 ; kb

FOLLOWUP_IP: 
WwanUsbMp+22fad
97100fad ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  WwanUsbMp+22fad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WwanUsbMp

IMAGE_NAME:  WwanUsbMp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  528dd1e6

FAILURE_BUCKET_ID:  0x9F_4_WwanUsbMp+22fad

BUCKET_ID:  0x9F_4_WwanUsbMp+22fad

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_4_wwanusbmp+22fad

FAILURE_ID_HASH:  {a072eca6-20d1-492a-5f65-264fca8cbb5d}

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

0: kd> lmvm WwanUsbMp
start    end        module name
970de000 9711c000   WwanUsbMp T (no symbols)           
    Loaded symbol image file: WwanUsbMp.sys
    Image path: \SystemRoot\system32\DRIVERS\WwanUsbMp.sys
    Image name: WwanUsbMp.sys
    Timestamp:        Thu Nov 21 15:27:02 2013 (528DD1E6)
    CheckSum:         00049C01
    ImageSize:        0003E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try uninstalling it or updating it to a newer version.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Clean boot

Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

How to Change, Add, or Remove Startup Programs in Windows 7

Temp Monitoring

Check for heating issues using Speccy or HWMonitor.

Upload a screen shot with either of the tools: Screenshots and Files - Upload and Post in Seven Forums