Windows 7: SF Diagnostic Tool fails to copy .dmp file

jrodriguez · 13 Apr 2010

Good Morning,

This SF Diagnostic tool is very useful, but failed to copy the .dmp file from the workstation with the issue. At first I thought that it could have been because I was running the tool remotely, so I proceeded to ask a person in the office to run it for me and we got the same outcome. SF Tool failed to copy the .dmp file. I found this strange so I went ahead and ran it on my own work laptop running windows 7 pro 64 and it completed as expected. Any ideas why this is failing?

I have attached the .zip file to see where to go from here...

Jonathan_King · 13 Apr 2010

Make sure you are running the program from an Administrator account. You may also try right-clicking on it and selecting "Run as Administrator".

jrodriguez · 13 Apr 2010

I made sure that when I ran the tool, it was copied in to the c:\Temp directory and right clicked and ran it as the Aministrator. Both times First time around I remoted via RDP. Second time I had a person go in front of the station and log in as local administrator, and do the same. thinking that maybe rdp was the reason why it failed to copy the .dmp file. Some how it errors out while compyling results.

Jonathan_King · 13 Apr 2010

Try taking ownership of the Minidump folder.

Also make sure the dump settings are configured as below:

Capt.Jack Sparrow · 13 Apr 2010

Hello !!

Glad that you find the Tool helpful. Does it have DMP files under C:\Windows\Minidump folder ?? Because i have created to look for both MiniDump from C:\Windows\Minidump and C:\Windows for Memory Dump. But we need to Right Click and run as administrator in-order to copy the files over due to UAC. If you don't have follow Jonathan's steps and enable the small dump option.

Hope this helps,
Captain

jrodriguez · 13 Apr 2010

I went back in again and revised rights for the Minidump folder and found the the administrator needed explicit rights. once those were added in, I ran the tool again and I was able to complete without any error. I also made sure to check the current path for the Minidump folder... c:\Windows\Minidump made adjustments for the small memory dump as well. I have included two screen shots in the .zip file.

Thanks,....I will be uploading the detailed systems specs from this system as I have about 7 of these stations that I just built on AMD Phenom II platform. I have another group of PC's running Intel Quad Core's these were rebuild and upgraded to Windows 7pro64.

jrodriguez · 13 Apr 2010

Ups forgot to include the attachment, Sorry

Capt.Jack Sparrow · 13 Apr 2010

Quote: Originally Posted by jrodriguez

Ups forgot to include the attachment, Sorry

Hello !!

I ran your Dump files. Seems like its an issue with your Video Card. Its pointing to the atikmpag.sys. I would recommend to remove the drivers completely and download a fresh copy and reinstall it. Please don't use Windows Update to update the drivers.

Follow this link for more information on the Bugcheck http://www.sevenforums.com/crash-loc...eshooting.html

Lot of crashes happened for Vdeck.exe

The following is the available information on VDeck.exe:

Code:

The following is the available information on VDeck.exe:
Product name: HDAudioCPL 
Company name: VIA 
File description: VIA HD Audio CPL
Internal name: HDAudioCPL.exe
Original filenameHDAudioCPL.exe

Old Drivers

Code:

ino_fltr.sys Fri Oct 19 01:25:51 2007
adfs.SYS     Fri Jun 27 02:22:37 2008

Bugcheck Analysis

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8006c9d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003fd2c6c, 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:
------------------
 
FAULTING_IP: 
atikmpag+5c6c
fffff880`03fd2c6c ??              ???
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
 
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x117
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`05246400 fffff880`0485b2b3 : fffffa80`06c9d010 00000000`00000024 fffffa80`06c9d010 fffff880`0485af54 : watchdog!WdDbgReportRecreate+0xa3
fffff880`05246920 fffff880`0485b6ea : 00000000`00001000 fffff8a0`04451270 00000000`00000008 00000000`00003800 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`05246970 fffff880`0485c99e : fffffa80`06c9d010 fffffa80`06c9d010 fffffa80`08d93d50 fffffa80`08bdc410 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
fffff880`05246a10 fffff880`04f4bf07 : fffffa80`06c9d010 00000000`00000000 fffffa80`08d93d50 fffffa80`08bdc410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`05246a40 fffff880`04f75b75 : 00000000`ffffffff 00000000`0003c247 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05246b20 fffff880`04f742bb : 00000000`00000102 00000000`00000000 00000000`0003c247 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05246b50 fffff880`04f472c6 : ffffffff`ff676980 fffffa80`08bdc410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05246bf0 fffff880`04f73e7a : 00000000`00000000 fffffa80`08d93d50 00000000`00000080 fffffa80`08bdc410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05246d00 fffff800`02d60166 : 00000000`0212eaad fffffa80`08bde2f0 fffffa80`06a28b30 fffffa80`08bde2f0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05246d40 fffff800`02a9b486 : fffff800`02c35e80 fffffa80`08bde2f0 fffff800`02c43c40 fffff880`0121c534 : nt!PspSystemThreadStartup+0x5a
fffff880`05246d80 00000000`00000000 : fffff880`05247000 fffff880`05241000 fffff880`06e918a0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+5c6c
fffff880`03fd2c6c ??              ???
SYMBOL_NAME:  atikmpag+5c6c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4b22a2ac
FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

Hope this helps,
Captain

SIW2 · 13 Apr 2010

Which SF Diagnostic Tool?

Capt.Jack Sparrow · 13 Apr 2010

Quote: Originally Posted by SIW2

Which SF Diagnostic Tool?

This one SF Diagnostic Tool

- Captain

Windows 7: SF Diagnostic Tool fails to copy .dmp file

SF Diagnostic Tool fails to copy .dmp file problems?