I have HP ProBook 450 G2 Laptop, i got blue screen which is annoying, so can you please help me to read the DMP File
http://s000.tinyupload.com/?file_id=80130938295828665899
Here is the Dmp file
Can you please advice.
Technology Tips and News
I have HP ProBook 450 G2 Laptop, i got blue screen which is annoying, so can you please help me to read the DMP File
http://s000.tinyupload.com/?file_id=80130938295828665899
Here is the Dmp file
Can you please advice.
Your link sets off my malware app. Please fix it or move the files elsewhere
Sorry to hear that, ok here is another link
http://www.megafileupload.com/4Gme/Blue_Screen.rar
Microsoft (R) Windows Debugger Version 10.0.10069.9 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\zigza\Desktop\Blue Screen\062515-32339-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`03c15000 PsLoadedModuleList = 0xfffff800`03e5ae90 Debug session time: Thu Jun 25 04:04:11.403 2015 (UTC - 4:00) System Uptime: 0 days 0:00:31.746 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver 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 117, {fffffa800717d010, fffff88004529ecc, 0, 0} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+becc ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for a real bugcheck.) Arguments: Arg1: fffffa800717d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004529ecc, The pointer into responsible device driver module (e.g owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000000, Optional internal context dependent data. Debugging Details: ------------------ BUGCHECK_P1: fffffa800717d010 BUGCHECK_P2: fffff88004529ecc BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_IP: atikmpag+becc fffff880`04529ecc ?? ??? DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b CPU_COUNT: 4 CPU_MHZ: 95a CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 45 CPU_STEPPING: 1 BUGCHECK_STR: 0x117 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10069.9 amd64fre STACK_TEXT: fffff880`03cbf0d0 fffff880`049555f7 : fffffa80`0717d010 fffff880`049553d8 fffffa80`0977cd50 fffff880`04955061 : watchdog!WdDbgReportRecreate+0xa3 fffff880`03cbf5f0 fffff880`04956c87 : fffffa80`0717d010 fffffa80`0717d010 fffffa80`0977cd50 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb fffff880`03cbf640 fffff880`0480ff07 : fffffa80`0717d010 00000000`000007f0 fffffa80`0977cd50 fffffa80`096d7410 : dxgkrnl!TdrIsRecoveryRequired+0x11f fffff880`03cbf670 fffff880`0483dd5a : fffffa80`ffffffff 00000000`0000076f fffff880`03cbf7c0 00000000`0000000e : dxgmms1!VidSchiReportHwHang+0x40b fffff880`03cbf750 fffff880`04823bb1 : fffffa80`0978d000 ffffffff`feced300 00000000`0000000e fffffa80`0978dd98 : dxgmms1!VidSchWaitForCompletionEvent+0x196 fffff880`03cbf790 fffff880`048263f5 : 00000000`00000001 fffffa80`0978d000 fffff880`03cbfab0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9 fffff880`03cbf890 fffff880`0481f38f : fffff880`03cbfb38 fffffa80`08f78d50 fffffa80`095c9af0 fffff880`03cbfb48 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x1cd fffff880`03cbf900 fffff880`04839231 : 00000001`00000000 fffff8a0`01368000 fffffa80`08f78d50 fffffa80`05b2eec8 : dxgmms1!VidMmiProcessSystemCommand+0x23 fffff880`03cbf930 fffff880`048383bc : fffff880`03cbfa90 00000000`00000000 fffffa80`05b2eec0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39 fffff880`03cbf960 fffff880`0480a77a : 00000000`00000000 fffffa80`08f78d50 fffffa80`05b2eec0 fffffa80`05b2eec0 : dxgmms1!VidSchiSubmitQueueCommand+0x74 fffff880`03cbf990 fffff880`0483a927 : fffffa80`095c9af0 fffffa80`096fb000 fffffa80`05b2eec0 6d4d6956`0490282c : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6 fffff880`03cbfa20 fffff880`0481f4b9 : fffffa80`00000001 fffffa80`096d7410 fffffa80`0978d000 fffff880`03cbfb38 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f fffff880`03cbfa90 fffff880`0481f8dc : fffff880`03cbfbf0 fffff8a0`013697b0 fffff880`03cbfbf0 fffff8a0`013697b0 : dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9 fffff880`03cbfb00 fffff880`0481afaa : 00000000`00000000 00000000`00000000 fffffa80`0978d000 fffff8a0`01280b70 : dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x4c fffff880`03cbfb70 fffff880`04801aa7 : fffff8a0`01366ce0 fffff8a0`013402f0 fffff880`03cbfce0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x2da fffff880`03cbfc50 fffff880`0493b469 : 00000000`00000000 fffff880`03cc0120 00000000`00000000 fffff8a0`013667e0 : dxgmms1!VidMmOpenAllocation+0xeb fffff880`03cbfca0 fffff880`04934610 : fffff880`03cbff08 fffff8a0`00b64680 fffff880`03cc00e0 fffff880`03cc00e0 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291 fffff880`03cbfd30 fffff880`049362ef : fffff8a0`01368000 fffff880`03cc0390 00000000`00000000 fffff8a0`01368000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8 fffff880`03cc0330 fffff880`0493c9e0 : 00000000`00010000 fffff900`c00c079c 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateStandardAllocation+0x367 fffff880`03cc0490 fffff960`0076682d : fffff900`c00c0020 00000000`00000000 fffff880`03cc0b90 00000000`00000000 : dxgkrnl!DxgkCddEnable+0x904 fffff880`03cc07e0 fffff960`00765ce1 : 00000000`00000004 ffffffff`fffd74ff 00000000`00000002 fffffa80`00000000 : cdd!CreateAndEnableDevice+0x1e1 fffff880`03cc0870 fffff800`03f32cce : 00000000`043304a9 fffffa80`097b2760 00000000`00000080 fffffa80`097c8b30 : cdd!PresentWorkerThread+0x975 fffff880`03cc0c00 fffff800`03c86fe6 : fffff880`02fd7180 fffffa80`097b2760 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03cc0c40 00000000`00000000 : fffff880`03cc1000 fffff880`03cbb000 fffff880`03cbe490 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: atikmpag+becc fffff880`04529ecc ?? ??? SYMBOL_NAME: atikmpag+becc FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5341fff0 FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys PRIMARY_PROBLEM_CLASS: X64_0x117_IMAGE_atikmpag.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x117_image_atikmpag.sys FAILURE_ID_HASH: {fa4b6286-8c4a-e9c2-c89f-5612619e000e} Followup: MachineOwner --------- 3: kd> lmvm atikmpag Browse full module list start end module name fffff880`0451e000 fffff880`045be000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: atikmpag.sys Image name: atikmpag.sys Browse all global symbols functions data Timestamp: Sun Apr 06 21:31:28 2014 (5341FFF0) CheckSum: 000A31BB ImageSize: 000A0000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Mini Kernel Dump does not contain unloaded driver list
Hi Mr-Exlans,
So did your issue resolve? If no, please let us know the current situation in order to provide the further help.
In addition, please refer to this reference:
Bug Check 0x117: VIDEO_TDR_TIMEOUT_DETECTED
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557271(v=vs.85).aspx