Hier die Analyse:
-----------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Downloads\MEMORY\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred symsrv*symsrv.dll*C:\Programdata\Microsoft\Localsymbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: symsrv*symsrv.dll*C:\Programdata\Microsoft\Localsymbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff800`75e1c000 PsLoadedModuleList = 0xfffff800`760e0990
Debug session time: Thu Apr 10 13:02:46.258 2014 (UTC + 2:00)
System Uptime: 0 days 0:23:03.231
Loading Kernel Symbols
...............................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe0000fff2c40, ffffd000207b9840, ffffe00001b29510}
*** ERROR: Module load completed but symbols could not be loaded for ew_jubusenum.sys
Probably caused by :
ew_jubusenum.sys
Followup: MachineOwner
1: 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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0000fff2c40, Physical Device Object of the stack
Arg3: ffffd000207b9840, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00001b29510, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME:
ew_jubusenum.sys -->
Der auslösende Treiber
DEBUG_FLR_IMAGE_TIMESTAMP: 4e698d25
MODULE_NAME:
ew_jubusenum
FAULTING_MODULE: fffff80002200000
ew_jubusenum
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
STACK_TEXT:
ffffd000`207b9808 fffff800`760131a6 : 00000000`0000009f 00000000`00000003 ffffe000`0fff2c40 ffffd000`207b9840 : nt!KeBugCheckEx
ffffd000`207b9810 fffff800`760130c6 : ffffe000`0ff68950 ffff3b20`fb15be0f 00000000`00000046 fffff800`75e78a04 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`207b9870 fffff800`75ec9f64 : ffffe000`0ff68988 ffffd000`207b9939 ffffe000`0ff689c8 00000000`00000000 : nt!PopIrpWatchdog+0x32
ffffd000`207b98c0 fffff800`75eca478 : 00000000`00000002 ffffe000`023453f0 ffffd000`207a4180 fffff800`7610d840 : nt!KiProcessExpiredTimerList+0x1d8
ffffd000`207b99a0 fffff800`75f26478 : ffffd000`207a4180 00000000`0022318a 00000000`0000ce1e 00000000`0000ce36 : nt!KiExpireTimerTable+0x218
ffffd000`207b9a40 fffff800`75e76abc : ffffe000`00000000 00001f80`00000001 00000003`387ac737 00000000`00000002 : nt!KiTimerExpiration+0x148
ffffd000`207b9af0 fffff800`75f6d7ea : ffffd000`207a4180 ffffd000`207a4180 00000000`00000000 ffffd000`207b0240 : nt!KiRetireDpcList+0x19c
ffffd000`207b9c60 00000000`00000000 : ffffd000`207ba000 ffffd000`207b4000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ew_juwwanecm_IMAGE_ew_jubusenum.sys
BUCKET_ID:
0x9F_3_POWER_DOWN_ew_juwwanecm_IMAGE_ew_jubusenum.sys -->
Der Treiber macht Probleme beim einleiten des Standby Betriebes
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_ew_juwwanecm_image_ew_jubusenum.sys
FAILURE_ID_HASH: {9f4e6a4f-547c-1456-f228-1a73b111c8f5}
Followup: MachineOwner
1: kd> lmvm ew_jubusenum
start end module name
fffff800`02200000 fffff800`0221b000 ew_jubusenum (no symbols)
Loaded symbol image file: ew_jubusenum.sys
Image path: \SystemRoot\System32\drivers\ew_jubusenum.sys
Image name: ew_jubusenum.sys
Timestamp: Fri Sep 09 05:51:01 2011 (4E698D25)
CheckSum: 00016AB3
ImageSize: 0001B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmvm ew_jubusenum
start end module name
fffff800`02200000 fffff800`0221b000 ew_jubusenum (no symbols)
Loaded symbol image file: ew_jubusenum.sys
Image path: \SystemRoot\System32\drivers\ew_jubusenum.sys
Image name: ew_jubusenum.sys
Timestamp: Fri Sep 09 05:51:01 2011 (4E698D25)
CheckSum: 00016AB3
ImageSize: 0001B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
-----------------------------------------------------------------------
Der Treiber
ew_jubusenum.sys gehört zu einem Huawei Gerät. Also solltest Du schauen, dass Du einen aktuelleren Treiber bekommst oder (falls kein aktuellerer Treiber verfügbar ist) probeweise eine ältere Version installierst.