Danielo290881
Member
Hi,
i am using a Surface Pro 3 with Type Cover 1 and a external mouse on USB.
I recognized that sometimes, when i shut down the SP3 with the charms but, it isnt really shut down. I can track this by clicking on the start button at the Display and it vibrates. I can only start the SP3 again with holdin down the power button for about 10 seconds.
In the reliabitilty index i can see an unexpected shutdown.
Solution Center Shows there is a solution, but when i click on "Show solution" i get the following error (of course my Internet is working ....)
This solution could not be downloaded
Most likely causes:
Primary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff800`09215000 PsLoadedModuleList = 0xfffff800`094df2d0
Debug session time: Sat Aug 2 09:59:34.666 2014 (UTC - 4:00)
System Uptime: 0 days 4:38:32.613
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000b6c035c0, Physical Device Object of the stack
Arg3: ffffd001a5abe930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe000b8f231a0, The blocked IRP
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: ntkrnlmp
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: ntkrnlmp
FAULTING_MODULE: fffff800b83e5000 raspppoe
DEVICE_OBJECT: ffffe000b6c88050
DRIVER_OBJECT: ffffe000b8367290
IRP_ADDRESS: ffffe000b8f231a0
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
ffffd001`a5abe8f8 fffff800`09411c1e : 00000000`0000009f 00000000`00000003 ffffe000`b6c035c0 ffffd001`a5abe930 : nt!KeBugCheckEx
ffffd001`a5abe900 fffff800`09411b3e : ffffe000`b5a6a8f0 00000000`ffffffff 00000000`00000000 ffffffff`00000003 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`a5abe960 fffff800`0926e810 : 00000000`00000004 00000000`00252ab8 ffffd001`a5aaa180 ffffd001`a5aaa180 : nt!PopIrpWatchdog+0x32
ffffd001`a5abe9b0 fffff800`0936caea : ffffd001`a5aaa180 ffffd001`a5aaa180 ffffd001`a5ab62c0 ffffe000`b7916880 : nt!KiRetireDpcList+0x4f0
ffffd001`a5abec60 00000000`00000000 : ffffd001`a5abf000 ffffd001`a5ab9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp
BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp
Followup: MachineOwner
---------
i am using a Surface Pro 3 with Type Cover 1 and a external mouse on USB.
I recognized that sometimes, when i shut down the SP3 with the charms but, it isnt really shut down. I can track this by clicking on the start button at the Display and it vibrates. I can only start the SP3 again with holdin down the power button for about 10 seconds.
In the reliabitilty index i can see an unexpected shutdown.
Solution Center Shows there is a solution, but when i click on "Show solution" i get the following error (of course my Internet is working ....)
This solution could not be downloaded
Most likely causes:
- Your computer was unable to download the solution at this time. Check to make sure your computer is connected to the Internet, and then try to download the solution again later.
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff800`09215000 PsLoadedModuleList = 0xfffff800`094df2d0
Debug session time: Sat Aug 2 09:59:34.666 2014 (UTC - 4:00)
System Uptime: 0 days 4:38:32.613
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000b6c035c0, Physical Device Object of the stack
Arg3: ffffd001a5abe930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe000b8f231a0, The blocked IRP
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: ntkrnlmp
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: ntkrnlmp
FAULTING_MODULE: fffff800b83e5000 raspppoe
DEVICE_OBJECT: ffffe000b6c88050
DRIVER_OBJECT: ffffe000b8367290
IRP_ADDRESS: ffffe000b8f231a0
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
ffffd001`a5abe8f8 fffff800`09411c1e : 00000000`0000009f 00000000`00000003 ffffe000`b6c035c0 ffffd001`a5abe930 : nt!KeBugCheckEx
ffffd001`a5abe900 fffff800`09411b3e : ffffe000`b5a6a8f0 00000000`ffffffff 00000000`00000000 ffffffff`00000003 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`a5abe960 fffff800`0926e810 : 00000000`00000004 00000000`00252ab8 ffffd001`a5aaa180 ffffd001`a5aaa180 : nt!PopIrpWatchdog+0x32
ffffd001`a5abe9b0 fffff800`0936caea : ffffd001`a5aaa180 ffffd001`a5aaa180 ffffd001`a5ab62c0 ffffe000`b7916880 : nt!KiRetireDpcList+0x4f0
ffffd001`a5abec60 00000000`00000000 : ffffd001`a5abf000 ffffd001`a5ab9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp
BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp
Followup: MachineOwner
---------