Search the Community
Showing results for tags 'troubleshooting'.
Hello all , first off , I'm a vivid Vista user . But sometimes I use Windows 7 for trying out some programmes . Right now I have a fresh install of Win 7 SP1 on my spare machine with Core Quad , it is not activated and absolutely clean from everything , except Audio/Video drivers . Something weird's going on , I can't delete executables . Process explorer says that they are locked by the system itself . The only way to delete an executable - close it's folder , wait for some time and delete this closed folder , without opening it again , otherwise it locks again. Tried switching Off defender , keeping only basic services , nothing helps . All help is really appreciated , thank you.
Hello i'm new to the forum and i JUST purchased my licence not 30 minutes ago. Love the program works like a charm. However i see you give the user the ability to install custom start orbs. I copied the start orb files over to the proper folder making the assumption that the Startisback cfg program would just detect the new files in the folder. Am i mistaken? the start orbs i found were intended to be used with windows 7 i believe so maybe that's the problem? Tho i can't imagine that that would be causing any issues since all versions of windows use the same file format for the start orbs correct? so am i doing something WRONG?
I have several users connecting to our main office via Terminal Services Gateway. One user specifically is having issues daily with APPCRASH errors on mstsc.exe. She is running Windows 7 64 bit, all updates installed. Gateway is on a SBS 2008 server. No other users are having this problem. After running the crash dump, it seemed that the issue was upon auto-reconnect. Doing some research, I found that her HKEY_Local_machine\ system\currentcontrolset\control\terminal server entry fDenyTSConnections Key was set to 1. I changed to 0 with no effect. I'm not sure what the next steps to take are. Can anybody analyze this dmp file better than I have done? Application Log Event Detail: Faulting application name: mstsc.exe, version: 6.3.9600.16415, time stamp: 0x524b5b3d Faulting module name: mstscax.dll, version: 6.3.9600.16503, time stamp: 0x52c5f878 Exception code: 0xc0000005 Fault offset: 0x0000000000439b7a Faulting process id: 0x10c8 Faulting application start time: 0x01cf8fc6ce6ffa2d Faulting application path: C:\Windows\System32\mstsc.exe Faulting module path: C:\Windows\System32\mstscax.dll Report Id: 88b5f942-fbc6-11e3-8332-0023245c063b Crash Dump Detail: Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\mforsyth\Desktop\mstsc.exe.4420.dmp]User Mini Dump File with Full Memory: Only application data is available Symbol search path is: SRV*C:\SYMBOLS*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: SingleUserTSMachine Name:Debug session time: Wed Jun 25 14:54:37.000 2014 (UTC - 4:00)System Uptime: 0 days 1:13:44.347Process Uptime: 0 days 1:12:24.000...............................................................................................................Loading unloaded module list................................................................This dump file has an exception of interest stored in it.The stored exception information can be accessed via .ecxr.(1144.138c): Access violation - code c0000005 (first/second chance not available)ntdll!ZwWaitForMultipleObjects+0xa:00000000`775f186a c3 ret0:012> !analyze -v******************************************************************************** ** Exception Analysis ** ******************************************************************************** *** ERROR: Module load completed but symbols could not be loaded for mstsc.exeGetPageUrlData failed, server returned HTTP status 404URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_3_9600_16415/524b5b3d/mstscax_dll/6_3_9600_16503/52c5f878/c0000005/00439b7a.htm?Retriage=1 FAULTING_IP: mstscax!CClientProxyTransport::SetErrorStatus+a000007fe`e7e29b7a 4883b98007000000 cmp qword ptr [rcx+780h],0 EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)ExceptionAddress: 000007fee7e29b7a (mstscax!CClientProxyTransport::SetErrorStatus+0x000000000000000a) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000NumberParameters: 2 Parameter: 0000000000000000 Parameter: 0000000000000780Attempt to read from address 0000000000000780 DEFAULT_BUCKET_ID: INVALID_POINTER_READ PROCESS_NAME: mstsc.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000780 READ_ADDRESS: 0000000000000780 FOLLOWUP_IP: mstscax!CClientProxyTransport::SetErrorStatus+a000007fe`e7e29b7a 4883b98007000000 cmp qword ptr [rcx+780h],0 MOD_LIST: <ANALYSIS/> NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 FAULTING_THREAD: 000000000000138c PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ LAST_CONTROL_TRANSFER: from 000007fee7e29c46 to 000007fee7e29b7a STACK_TEXT: 00000000`0581fcb0 000007fe`e7e29c46 : 00000000`00000008 000007fe`e7bffd68 00000000`03e0c550 000007fe`e7e3169f : mstscax!CClientProxyTransport::SetErrorStatus+0xa00000000`0581fcf0 000007fe`e7e2bf85 : 00000000`03e0c550 00000000`03e0c550 00000000`0581fe30 000007fe`e7e091cc : mstscax!CClientProxyTransport::GetErrorStatus+0x2600000000`0581fd40 000007fe`e7ef3b69 : 000007fe`e7a0d150 00000000`30000055 00000000`00000000 00000000`03e0f138 : mstscax!CProxyClientSendPacket::OnComplete+0x7500000000`0581fd80 000007fe`e7e07a6b : 00000000`03da4f48 00000000`800706bf 00000000`0581fe30 00000000`72ed6872 : mstscax!CAAAsyncSend::OnComplete+0x2900000000`0581fdb0 000007fe`e7e184a4 : 00000000`00000000 00000000`0581fe30 00000000`00000000 00000000`00000000 : mstscax!CAARpcClientChannel::HandleIOCompletion+0x15b00000000`0581fde0 00000000`773959ed : 00000000`30000055 00000000`03e0f138 00000000`03da4f48 00000000`00000000 : mstscax!CAagIO::AAGIoThreadFunc+0x10000000000`0581fe50 00000000`775cc541 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd00000000`0581fe80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: mstscax!CClientProxyTransport::SetErrorStatus+a FOLLOWUP_NAME: MachineOwner MODULE_NAME: mstscax IMAGE_NAME: mstscax.dll DEBUG_FLR_IMAGE_TIMESTAMP: 52c5f878 STACK_COMMAND: ~12s; .ecxr ; kb FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_mstscax.dll!CClientProxyTransport::SetErrorStatus BUCKET_ID: X64_APPLICATION_FAULT_INVALID_POINTER_READ_mstscax!CClientProxyTransport::SetErrorStatus+a WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_3_9600_16415/524b5b3d/mstscax_dll/6_3_9600_16503/52c5f878/c0000005/00439b7a.htm?Retriage=1 Followup: MachineOwner---------