Laptop would power down after shutdown.Sometimes 0x9f BSOD

edmondhk · Jul 28, 2015

My laptop is Lenovo E440 which come with 8.1.

The symptom is when I shutdown the computer, it do all the process seems normal, except the power light won't goes off. I have to long press the power button to force shutdown. If I ignore it for a few minutes, it suddenly wake up and give me a BSOD then restart.

The BSOD also do the minidump. I also attached the dump by the collector tools.
I have try update the latest BIOS/Driver to lenovo recommendation.

I have try to debug with Windbg, which have following result. But I have no idea what I can do with ACPI driver.
BugCheck 9F, {3, ffffe000139d47f0, fffff8024874b960, ffffe0001e709c30}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !irp ffffe000`1e709c30
Irp is active with 3 stacks 2 is current (= 0xffffe0001e709d48)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 ffffe00014549040 00000000 fffff80246e03b3c-ffffe0001c6cc940 Success Error Cancel pending
\Driver\ACPI nt!PopSystemIrpCompletion
Args: 00014400 00000000 00000004 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-ffffe0001c6cc940

Args: 00000000 00000000 00000000 00000000
0: kd> !irp ffffe0001e709c30
Irp is active with 3 stacks 2 is current (= 0xffffe0001e709d48)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 ffffe00014549040 00000000 fffff80246e03b3c-ffffe0001c6cc940 Success Error Cancel pending
\Driver\ACPI nt!PopSystemIrpCompletion
Args: 00014400 00000000 00000004 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-ffffe0001c6cc940

Args: 00000000 00000000 00000000 00000000
0: kd> lmvm ACPI
start end module name
fffff801`4f647000 fffff801`4f6cf000 ACPI (pdb symbols) c:\windows\symbols\acpi.pdb\276228AA42904C96B46A37C6C1872D8C2\acpi.pdb
Loaded symbol image file: ACPI.sys
Mapped memory image file: c:\windows\symbols\ACPI.sys\54335E2E88000\ACPI.sys
Image path: \SystemRoot\System32\drivers\ACPI.sys
Image name: ACPI.sys
Timestamp: Tue Oct 07 11:29:50 2014 (54335E2E)
CheckSum: 0008D868
ImageSize: 00088000
File version: 6.3.9600.17393
Product version: 6.3.9600.17393
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ACPI.sys
OriginalFilename: ACPI.sys
ProductVersion: 6.3.9600.17393
FileVersion: 6.3.9600.17393 (winblue_r4.141006-1627)
FileDescription: ACPI Driver for NT
LegalCopyright: © Microsoft Corporation. All rights reserved.

Can anyone please help me?

blueelvis · Jul 28, 2015

Hi edmondhk & welcome to the forums ^_^,

I have analysed your dump files (The one which you have analysed is 4 months old) and below has been provided an analysis of the same for informative purposes :-

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.

Let's see the stack and determine what caused the DPC Watchdog to crash the system -

Code:

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`90830c88 fffff801`39776f7e nt!KeBugCheckEx
01 ffffd000`90830c90 fffff801`39647f67 nt! ?? ::FNODOBFM::`string'+0xadbe
02 ffffd000`90830d20 fffff801`39da767f nt!KeClockInterruptNotify+0x787
03 ffffd000`90830f40 fffff801`396e2143 hal!HalpTimerClockInterrupt+0x4f
04 ffffd000`90830f70 fffff801`3975d12a nt!KiCallInterruptServiceRoutine+0xa3
05 ffffd000`90830fb0 fffff801`3975d50f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
06 ffffd000`22866570 fffff801`396e3113 nt!KiInterruptDispatchLBControl+0x11f
07 ffffd000`22866700 fffff801`396e30e2 nt!KxWaitForSpinLockAndAcquire+0x17
08 ffffd000`22866730 fffff801`c0ea265c nt!KeAcquireSpinLockRaiseToDpc+0x32
09 ffffd000`22866760 ffffe001`e73141c0 [COLOR=#ff0000][B][U]ftser2k[/U][/B][/COLOR]+0x1165c
0a ffffd000`22866768 ffffe001`e73141c0 0xffffe001`e73141c0
0b ffffd000`22866770 ffffd000`90800180 0xffffe001`e73141c0
0c ffffd000`22866778 00000000`00000000 0xffffd000`90800180

Seems like the FTDI USB To Serial Adapter's USB Driver is causing the problem.

Below is a list of 3rd party drivers present on your system -

Code:

**************************Mon Jul 13 12:52:14.562 2015 (UTC + 5:30)**************************
afcdp.sys                   Wed Jul 20 20:16:03 2011 (4E26EA2B)
ftser2k.sys                 Fri Apr 13 15:34:59 2012 (4F87FA4B)
HECIx64.sys                 Tue Dec 18 01:02:21 2012 (50CF7345)
tib_mounter.sys             Thu Dec 27 18:55:05 2012 (50DC4C31)
snapman.sys                 Wed Jan 16 19:14:06 2013 (50F6AEA6)
fltsrv.sys                  Fri Mar  1 19:23:39 2013 (5130B2E3)
tib.sys                     Wed Mar 20 14:30:38 2013 (51497AB6)
Tppwr64v.sys                Wed Apr 17 17:44:17 2013 (516E9219)
IntelPcc.sys                Thu Apr 25 03:17:43 2013 (517852FF)
ApsHM64.sys                 Wed Jun 12 11:03:33 2013 (51B8082D)
Apsx64.sys                  Wed Jun 12 11:06:52 2013 (51B808F4)
RtsPer.sys                  Mon Jun 24 08:04:50 2013 (51C7B04A)
CHDRT64.sys                 Wed Jul  3 11:42:51 2013 (51D3C0E3)
SynTP.sys                   Wed Jul 10 01:21:12 2013 (51DC69B0)
Smb_driver_Intel.sys        Wed Jul 10 01:22:16 2013 (51DC69F0)
Rt630x64.sys                Fri Jul 26 12:31:35 2013 (51F21ECF)
btmhsf.sys                  Thu Aug  1 19:48:23 2013 (51FA6E2F)
iaStorA.sys                 Fri Aug  2 07:09:52 2013 (51FB0DE8)
vm331avs.sys                Fri Aug  2 12:16:44 2013 (51FB55D4)
ibtusb.sys                  Wed Aug  7 21:36:12 2013 (52027074)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
NETwbw02.sys                Thu Sep 19 13:10:12 2013 (523AAA5C)
iwdbus.sys                  Fri Sep 27 03:08:04 2013 (5244A93C)
aksdf.sys                   Thu Oct 17 14:17:38 2013 (525FA42A)
igdkmd64.sys                Thu Dec 19 02:19:12 2013 (52B20A48)
ftdibus.sys                 Mon Jan 27 19:29:57 2014 (52E6665D)
nvlddmkm.sys                Thu Feb 20 06:48:31 2014 (530557E7)
nvpciflt.sys                Thu Feb 20 06:49:01 2014 (53055805)
LnvHIDHW.sys                Mon Apr  7 13:07:52 2014 (534255D0)
silabser.sys                Thu Apr 10 02:06:11 2014 (5345AF3B)
silabenm.sys                Thu Apr 10 02:06:13 2014 (5345AF3D)
aksfridge.sys               Tue Jun 24 15:14:36 2014 (53A94884)
tap0901.sys                 Wed Nov  5 18:46:32 2014 (545A2330)
ibmpmdrv.sys                Fri Nov  7 14:08:44 2014 (545C8514)
smi.sys                     Tue Mar  3 19:46:44 2015 (54F5C24C)
hardlock.sys                Mon Mar 23 22:49:26 2015 (55104B1E)

Update the culprit driver from **this** link.
Update Acronis as well.

Let me know how it goes ^_^

-Pranav

edmondhk · Jul 30, 2015

No, sir. I tried update the FTDI driver and I tried remove the entire device from the device manager with remove driver option.
But the problem still the same. What information should I provide to ask your further help?
Thank you

blueelvis · Aug 5, 2015

Hi Edmondhk ^_^,

Have you tried physically removing the device? (It seems like it is some sort of cable). Also, once you remove the driver (Or Device) from the Device Manager, does it spawn back after a restart? Could you please re-run the utility again and upload the fresh dumps after you remove the driver?

What was the result of updating the driver from the link which I gave you?

-Pranav

edmondhk · Aug 6, 2015

blueelvis said:
Hi Edmondhk ^_^,

Have you tried physically removing the device? (It seems like it is some sort of cable). Also, once you remove the driver (Or Device) from the Device Manager, does it spawn back after a restart? Could you please re-run the utility again and upload the fresh dumps after you remove the driver?

What was the result of updating the driver from the link which I gave you?

-Pranav

Thank you for your reply.

Yes, I do sir. In fact, I didn't connect that device for quite a while (atleast months). I will upload the fresh dump again tomorrow.
Thank you again for your kindly help.

blueelvis · Aug 9, 2015

edmondhk said:
Thank you for your reply.

Yes, I do sir. In fact, I didn't connect that device for quite a while (atleast months). I will upload the fresh dump again tomorrow.
Thank you again for your kindly help.

Hi Edmondhk ^_^,

If you are still not using the device then I would suggest you to remove the driver. But, before doing this, I would like to take a look at the fresh dump files. Kindly re-run the diagnostic utility and upload the ZIP file with your next post so that I can analyze it

Let me know how it goes ^_^.

-Pranav

edmondhk · Aug 16, 2015

blueelvis said:
edmondhk said:

Thank you for your reply.

Yes, I do sir. In fact, I didn't connect that device for quite a while (atleast months). I will upload the fresh dump again tomorrow.
Thank you again for your kindly help.

Click to expand...

Hi Edmondhk ^_^,

If you are still not using the device then I would suggest you to remove the driver. But, before doing this, I would like to take a look at the fresh dump files. Kindly re-run the diagnostic utility and upload the ZIP file with your next post so that I can analyze it

Let me know how it goes ^_^.

-Pranav

Dear Sir,

Sorry for such a late reply. I have another try on it but it still give me the same error.
Attached the fresh dump.

Laptop would power down after shutdown.Sometimes 0x9f BSOD

edmondhk

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

edmondhk

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

edmondhk

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

edmondhk

New Member

My Computer

System One