 |
|
Ошибка при подключение по RDP
Вложений: 1
Форумчане, прошу помощи.
Клиент RDP (W10) при подключении к серверу терминалов W2012R2 работает секунд 10 и закрывается. В логах на клиенте ошибка: http://forum.oszone.net/attachment.p...1&d=1583152111
При помощи ProcDump сделан дамп - https://yadi.sk/d/3qUMgY79xCSzKA
Анализ Windows Debugger:
Код:
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Andrew\Desktop\mstsc.exe_200228_130329.dmp]
Comment: '
*** C:\ProcDump\procdump.exe -accepteula -e -w mstsc.exe C:\ProcDump
*** Unhandled exception: C000000D'
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 18363 MP (2 procs) Free x64
Product: WinNt, suite: SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Debug session time: Fri Feb 28 13:03:29.000 2020 (UTC + 3:00)
System Uptime: not available
Process Uptime: 0 days 0:00:17.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.
(2624.10d0): Unknown exception - code c000000d (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!TppRaiseInvalidParameter+0x48:
00007ffb`915af260 eb00 jmp ntdll!TppRaiseInvalidParameter+0x4a (00007ffb`915af262)
0:006> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify timestamp for atidxx64.dll
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ANDREWDELL
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 763
Key : Analysis.Memory.CommitPeak.Mb
Value: 125
Key : Analysis.System
Value: CreateObject
Key : Timeline.Process.Start.DeltaSec
Value: 17
ADDITIONAL_XML: 1
COMMENT:
*** C:\ProcDump\procdump.exe -accepteula -e -w mstsc.exe C:\ProcDump
*** Unhandled exception: C000000D
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
rax=0000000000000000 rbx=000000c19fb7dd30 rcx=0000000000000000
rdx=0000000000000000 rsi=000000c19fb7d840 rdi=000000c19fb7d840
rip=00007ffb915af260 rsp=000000c19fb7df60 rbp=000000c19fb7e1e0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000004 r13=000002759411dae0
r14=000002759411d7e0 r15=0000027592d95160
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000204
ntdll!TppRaiseInvalidParameter+0x48:
00007ffb`915af260 eb00 jmp ntdll!TppRaiseInvalidParameter+0x4a (00007ffb`915af262)
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffb915af260 (ntdll!TppRaiseInvalidParameter+0x0000000000000048)
ExceptionCode: c000000d
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: mstsc.exe
ERROR_CODE: (NTSTATUS) 0xc000000d - .
EXCEPTION_CODE_STR: c000000d
STACK_TEXT:
000000c1`9fb7df60 00007ffb`9155e00b : 00000275`92d95160 00000275`9411d7e0 00000275`9411dae0 00000000`00000004 : ntdll!TppRaiseInvalidParameter+0x48
000000c1`9fb7e040 00007ffb`91502059 : 00000000`00000000 00000275`912f0000 000000c1`9fb7e1e0 00000000`00000000 : ntdll!TppIopValidateIo+0x5bc9b
000000c1`9fb7e070 00007ffb`5854d09a : 00000275`92d95160 00007ffb`587015d0 00007ffb`587015d0 00007ffb`5884ab08 : ntdll!TpWaitForIoCompletion+0x19
000000c1`9fb7e0b0 00007ffb`5812cc9f : 00000000`80004005 000000c1`00000000 00000275`93e42620 00000275`93f65000 : mstscax!CAAUDPClientRawTransport::Terminate+0x42
000000c1`9fb7e0e0 00007ffb`5854a213 : 00000275`94b37608 000000c1`0000001c 00000000`00000104 000000c1`9fb7e440 : mstscax!CAAUDPClientRawTransport::ConnectToServer+0x5cf
000000c1`9fb7e3d0 00007ffb`58545249 : 00000000`00000001 00000275`94b375e8 00000000`00000000 00000275`94b37350 : mstscax!CAAUDPClientChannel::SecureTunnel+0x6df
000000c1`9fb7f6f0 00007ffb`5854470f : 00000000`00000000 00000000`00000000 00000275`9411c580 00007ffb`58100000 : mstscax!CAAUDPClientChannel::HandleChannelConnect+0x2ad
000000c1`9fb7f790 00007ffb`914cf6d5 : 00000275`9411c580 00000000`00000000 00000275`91325ae0 00000000`7ffe0386 : mstscax!CAAUDPClientChannel::CallHandleChannelConnect+0xf
000000c1`9fb7f7c0 00007ffb`914d4634 : 00000000`00000000 00000275`9408e040 00007ffb`58544700 00000000`00000000 : ntdll!RtlpTpWorkCallback+0x165
000000c1`9fb7f8a0 00007ffb`8fb07bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x8d4
000000c1`9fb7fc60 00007ffb`9150ced1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000c1`9fb7fc90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
SYMBOL_NAME: mstscax!CAAUDPClientRawTransport::Terminate+42
MODULE_NAME: mstscax
IMAGE_NAME: mstscax.dll
STACK_COMMAND: ~6s ; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_PARAMETER_c000000d_mstscax.dll!CAAUDPClientRawTransport::Terminate
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e1210d23-ff0f-3cce-8a61-26fc99562625}
Followup: MachineOwner
---------
Подскажите, куда копать дальше?
|
PS. sfc /scannow результата не дает
|
Petya V4sechkin |
02-03-2020 20:44 2911782 |
Q-post, по дампу не удалось выяснить причину, под подозрением сторонние модули: - C:\Windows\System32\spool\drivers\x64\3\SD3BU.DLL (относится к принтеру Sharp)
- C:\Program Files (x86)\TeamViewer\tv_x64.dll
- C:\Windows\System32\DriverStore\FileRepository\c0312549.inf_amd64_d0c053e57e0c1fd8\atidxx64.dll (относится к драйверу видеокарты)
Можете сделать лог Process Monitor следующим образом: - запустите Process Monitor;
- спровоцируйте сбой mstsc.exe;
- сохраните лог: меню File -> Save -> PML-формат;
- заархивируйте и выложите на файлообменник.
|
Petya V4sechkin |
03-03-2020 11:29 2911840 |
|
Время: 16:22.
© OSzone.net 2001-