Hi,

dell 14z 5423

windows 8.1

My laptop is not shutdown properly, getting following error driver_power_state_failure. when i check the error logs it says kernal power event id: 41 Bugcheckcode: 159 

Please help me on this issue.

Hi bulive,

Here is a link for reference of troubleshooting this issue:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012, Windows 7, or Windows Server 2008 R2
https://support.microsoft.com/en-us/kb/2028504

To troubleshoot this issue deeply, please refer to the link as Zigzag posted to upload the dump files to OneDrive and paste the link here. We will try to make an analysis for you.

Best regards

ZigZag3143x,

Sorry for my late reply.

Here is the link,

https://onedrive.live.com/redir?resid=AB5B4465139DE758%21109

MeipoXu,

Sorry for my late reply.

Here you go,

https://onedrive.live.com/redir?resid=AB5B4465139DE758%21109

Related to raspppoe.sys RAS PPPoE mini-port/call-manager driver from Microsoft Corporation  Since it is an OS driver I would run a system file check to find and fix the state of the OS

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


Loading Dump File [C:\Users\zigza\Desktop\MiniDump1\062715-5671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Error: Empty Path.
Symbol search path is:  srv*E:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff803`62e1e000 PsLoadedModuleList = 0xfffff803`630f7850
Debug session time: Sat Jun 27 11:43:35.055 2015 (UTC - 4:00)
System Uptime: 0 days 1:05:24.914
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 12c, ffffe00114bf9880, ffffd001741e9980}

Implicit thread is now ffffe001`14bf9880
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : raspppoe.sys ( raspppoe!RasPppoeCleanup+5a )

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

2: 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: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe00114bf9880, The thread currently holding on to the Pnp lock.
Arg4: ffffd001741e9980, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now ffffe001`14bf9880

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  Not Specified

BIOS_DATE:  05/18/2013

BASEBOARD_VERSION:  A13

BUGCHECK_P1: 4

BUGCHECK_P2: 12c

BUGCHECK_P3: ffffe00114bf9880

BUGCHECK_P4: ffffd001741e9980

DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  14bf9880

CPU_COUNT: 4

CPU_MHZ: 768

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 10.0.10075.9 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80362ecf1de to fffff80362f71b36

STACK_TEXT:  
ffffd001`7471cf20 fffff803`62ecf1de : ffffd001`74340180 ffffe001`14bf9880 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
ffffd001`7471d060 fffff803`62ecec59 : ffffe001`13f7d8c0 00000000`00000001 00000000`00000001 ffffd001`7471d254 : nt!KiSwapThread+0x14e
ffffd001`7471d100 fffff803`62e72e50 : ffffe001`1819c600 00000000`00000000 ffffe001`1819c558 ffffc000`4d138470 : nt!KiCommitThreadWait+0x129
ffffd001`7471d180 fffff801`71d03d0e : ffffe001`1b001608 fffff801`00000000 ffffd001`7471d200 fffff803`00000000 : nt!KeWaitForSingleObject+0x2c0
ffffd001`7471d210 fffff801`71cfc917 : 00000000`00000000 ffffe001`1b001600 ffffc000`40801a80 00000000`00000000 : ndis!KWaitEvent::Wait+0x22
ffffd001`7471d250 fffff801`71d334ca : ffffc000`41fc7c28 ffffc000`4d138a78 00000000`00060003 fffff801`71d07070 : ndis!Ndis::BindEngine::ApplyBindChanges+0xffffffff`ffffffe7
ffffd001`7471d2a0 fffff801`71d074ce : ffffc000`41fc7c78 00000000`00000000 ffffc000`4d138a78 ffffe001`1b0001a0 : ndis!<lambda_1ce06b2b40968439b229a98218e85867>::<helper_func_cdecl>+0x1b
ffffd001`7471d2d0 fffff801`71d07417 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc000`4d138a70 : ndis!NDIS_BIND_DRIVER_BASE::ForEachLink+0x9e
ffffd001`7471d320 fffff801`71d0758a : ffffc000`4d138a68 ffffe001`1515b680 ffffd001`7471d438 fffff801`71cf0cab : ndis!NDIS_BIND_DRIVER_BASE::SetRunningDriverIsReady+0x3f
ffffd001`7471d350 fffff801`71d43392 : ffffe001`1515b680 ffffe001`15101ba0 ffffd001`7471d438 ffffe001`13f7d8c0 : ndis!NDIS_BIND_PROTOCOL_DRIVER::SetRunningDriver+0x5a
ffffd001`7471d3a0 fffff801`71d26d2b : ffffe001`1515b680 00000000`00000000 00000000`00000000 fffff801`753e7200 : ndis!NdisDeregisterProtocol+0xa2
ffffd001`7471d400 fffff801`753e0262 : fffff801`753e7010 ffffe001`00000000 e00119b1`0e300000 0000001b`00000001 : ndis!NdisDeregisterProtocolDriver+0x3c
ffffd001`7471d430 fffff801`753ea8a0 : 00000000`20206f49 ffffe001`13f7d8c0 00000000`00000000 00000000`00000001 : raspppoe!RasPppoeCleanup+0x5a
ffffd001`7471d460 fffff801`71d044ea : ffffe001`15101ba0 ffffd001`7471d710 00000000`00001428 fffff803`632472e6 : raspppoe!MpUnload+0x44
ffffd001`7471d490 fffff801`71d04452 : ffffe001`19b10e60 fffff803`62f43659 00000000`00000000 ffffd001`7471d540 : ndis!ndisMInvokeDriverUnload+0x26
ffffd001`7471d4c0 fffff803`63301e4b : ffffe001`19b10e60 00000000`00000000 ffffd001`7471d710 00000000`00000000 : ndis!ndisMUnloadEx+0x56
ffffd001`7471d500 fffff803`632c470d : 00000000`65647050 ffffe001`19b10fb0 00000000`0000007c ffffc000`45609f80 : nt!IopUnloadDriver+0x23f
ffffd001`7471d6e0 fffff803`62f30a76 : ffffe001`1e4284e0 ffffdfff`39727680 ffffe001`1e4284e0 00000000`0000000a : nt!PnpUnloadAttachedDriver+0x9d
ffffd001`7471d730 fffff803`632e54f1 : ffffe001`19ad5e40 ffffe001`1e4284e0 ffffc000`41866c70 ffffc000`42189680 : nt!PnpRemoveLockedDeviceNode+0x222
ffffd001`7471d790 fffff803`632e546a : 00000000`00000000 ffffc000`41866c70 ffffe001`1e4284e0 fffff803`632e5301 : nt!PnpDeleteLockedDeviceNode+0x4d
ffffd001`7471d7d0 fffff803`632e677c : ffffe001`19c60e40 00000000`00000002 ffffe001`19ac56e0 fffff803`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a
ffffd001`7471d850 fffff803`632e668d : ffffe001`19ac56e0 00000000`00000000 00000000`00000001 ffffe001`19c60e40 : nt!PnpDelayedRemoveWorker+0xc4
ffffd001`7471d8a0 fffff803`62f307ac : 00000000`0000000a 00000000`00000008 00000000`00000000 00000000`00000007 : nt!PnpChainDereferenceComplete+0x119
ffffd001`7471d8d0 fffff803`632e4b44 : 00000000`00000000 00000000`ffffffff ffffe001`00000018 00000000`00000001 : nt!PnpIsChainDereferenced+0x10c
ffffd001`7471d950 fffff803`6329040d : ffffc000`51529700 00000000`00000008 ffffc000`00000003 fffff803`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x800
ffffd001`7471dab0 fffff803`63290853 : ffffc000`51529770 00000000`00000000 00000000`00000000 fffff803`63290534 : nt!PnpProcessTargetDeviceEvent+0x9d
ffffd001`7471daf0 fffff803`62ecb6bc : fffff803`63290534 ffffc000`52516990 ffffe001`1417e690 ffffe001`14bf9880 : nt!PnpDeviceEventWorker+0x31f
ffffd001`7471db50 fffff803`62f1e36c : 058d480e`75c084ff ffffe001`14bf9880 00000000`00000080 ffffe001`14bf9880 : nt!ExpWorkerThread+0x28c
ffffd001`7471dc00 fffff803`62f752c6 : ffffd001`7978e180 ffffe001`14bf9880 ffffe001`14090040 83485340`c35f30c4 : nt!PspSystemThreadStartup+0x58
ffffd001`7471dc60 00000000`00000000 : ffffd001`7471e000 ffffd001`74718000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xffffe00114bf9880 ; kb

FOLLOWUP_IP: 
raspppoe!RasPppoeCleanup+5a
fffff801`753e0262 488325ee6d000000 and     qword ptr [raspppoe!gl_NdisProtocolDriverHandle (fffff801`753e7058)],0

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  raspppoe!RasPppoeCleanup+5a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: raspppoe

IMAGE_NAME:  raspppoe.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5215f7c5

IMAGE_VERSION:  6.3.9600.16384

BUCKET_ID_FUNC_OFFSET:  5a

FAILURE_BUCKET_ID:  0x9F_4_raspppoe!RasPppoeCleanup

BUCKET_ID:  0x9F_4_raspppoe!RasPppoeCleanup

PRIMARY_PROBLEM_CLASS:  0x9F_4_raspppoe!RasPppoeCleanup

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_4_raspppoe!raspppoecleanup

FAILURE_ID_HASH:  {e9804e85-a9ce-852f-0dee-ef9be593a2a4}

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

2: kd> lmvm raspppoe
Browse full module list
start             end                 module name
fffff801`753dd000 fffff801`753f8000   raspppoe   (pdb symbols)          e:\symbols\raspppoe.pdb\87B7487710BA4E1EAFED868839725F982\raspppoe.pdb
    Loaded symbol image file: raspppoe.sys
    Mapped memory image file: e:\symbols\raspppoe.sys\5215F7C51b000\raspppoe.sys
    Image path: \SystemRoot\system32\DRIVERS\raspppoe.sys
    Image name: raspppoe.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Aug 22 07:36:37 2013 (5215F7C5)
    CheckSum:         0001CDE4
    ImageSize:        0001B000
    File version:     6.3.9600.16384
    Product version:  6.3.9600.16384
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     raspppoe.sys
    OriginalFilename: raspppoe.sys
    ProductVersion:   6.3.9600.16384
    FileVersion:      6.3.9600.16384 (winblue_rtm.130821-1623)
    FileDescription:  RAS PPPoE mini-port/call-manager driver
    LegalCopyright:    Microsoft Corporation. All rights reserved.

I did run system file check (sfc) for 3 times but i don't see any issue/error.

I'm getting the following message once the scan has been completed,

"windows resource protection did not find any integrity violation"

Please let me know how to proceed further.

Thanks!

Let try something else.  Please run driver verifier