Blue screen when copying files over RDP connection

[Guest Ingi]

Hi.

 

I experienced an odd behavior on two servers recently (Windows 2003 Standard

SP2).

I connected to the server using MS terminal client and chose to connect the

c: drive to copy files from my local computer to the server.

On the server in remote desktop I located the file on my computer and chose

copy and when I tried to paste I lost the connection. I then realized that

the server had rebooted!

I found the following error in the Event Log:

 

Event ID: 1003

Source: System Error

Category: 102

Error code 1000007e, parameter1 c0000005, parameter2 00000000, parameter3

ba1bf17c, parameter4 ba1bee78.

 

Below is the information from the minidump:

 

***********************************************************

*

*

* Bugcheck Analysis

*

*

*

***********************************************************

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: c0000005, The exception code that was not handled

Arg2: 00000000, The address that the exception occurred at

Arg3: ba1bf17c, Exception Record Address

Arg4: ba1bee78, Context Record Address

 

Debugging Details:

------------------

 

 

 

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"

referenced memory at "0x%08lx". The memory could not be "%s".

 

FAULTING_IP:

+0

00000000 0000 add byte ptr [eax],al

 

EXCEPTION_RECORD: ba1bf17c -- (.exr 0xffffffffba1bf17c)

Cannot read Exception record @ ba1bf17c

 

CONTEXT: ba1bee78 -- (.cxr 0xffffffffba1bee78)

Unable to read context, Win32 error 0n30

 

CUSTOMER_CRASH_COUNT: 5

 

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

 

BUGCHECK_STR: 0x7E

 

CURRENT_IRQL: 0

 

EXCEPTION_STR: 0x0

 

LAST_CONTROL_TRANSFER: from ba823c93 to 00000000

 

STACK_TEXT:

WARNING: Frame IP not in any known module. Following frames may be wrong.

ba1bf240 ba823c93 89c49728 89c49728 89c49728 0x0

ba1bf258 ba823d45 89c49728 ba82a410 8a1adba0 rdpdr!RxLowIoCompletionTail+0x33

ba1bf26c ba81df22 89c49728 ba1bf29c ba81e291 rdpdr!RxLowIoCompletion+0x3f

ba1bf278 ba81e291 89c49728 00000000 00000016

rdpdr!DrDevice::CompleteRxContext+0x2a

ba1bf29c ba814ff7 ba1bf2e0 00000000 00000016

rdpdr!DrDevice::CompleteBusyExchange+0x4d

ba1bf2cc ba81f36d e2cc8000 8915a658 ba1bf344

rdpdr!DrDrive::OnQueryFileInfoCompletion+0x2a5

ba1bf2f0 ba81b69d e2cc8000 0000002a ba1bf344

rdpdr!DrDevice::OnDeviceIoCompletion+0xa9

ba1bf310 ba81b85a e2cc8000 0000002a ba1bf344

rdpdr!DrExchangeManager::OnDeviceIoCompletion+0x55

ba1bf324 ba81c51f e2cc8000 0000002a ba1bf344

rdpdr!DrExchangeManager::HandlePacket+0x26

ba1bf350 ba81be34 00000000 89f5a493 89f5a420

rdpdr!DrSession::ReadCompletion+0xc5

ba1bf368 8083ffb5 00000000 89f5a420 8a147210

rdpdr!DrSession::ReadCompletionRoutine+0x38

ba1bf398 baa275d8 89f82508 00000000 e1028000 nt!IopfCompleteRequest+0xcd

ba1bf3d4 baa280d2 89f82508 00000005 00000000

termdd!IcaChannelInputInternal+0x1f0

ba1bf3fc b8c3c6e1 88d23cfc 00000005 00000000 termdd!IcaChannelInput+0x3c

ba1bf430 b8c363c1 e1028000 00bc316e 00000032 RDPWD!WDW_OnDataReceived+0x181

ba1bf458 b8c361b9 e1028c00 e3725150 ba1bf400

RDPWD!SM_MCSSendDataCallback+0x159

ba1bf4c0 b8c35fe0 00000045 ba1bf4f8 0000004c RDPWD!HandleAllSendDataPDUs+0x155

ba1bf4dc b8c53ba4 00000045 ba1bf4f8 e1028000 RDPWD!RecognizeMCSFrame+0x32

ba1bf504 b8c3506b e1028000 00000000 88bc31a0 RDPWD!MCSIcaRawInputWorker+0x346

ba1bf52c baa2b194 e1028000 00000000 88bc3154 RDPWD!MCSIcaRawInput+0x65

ba1bf550 b8d69fcb 89fff3a4 00000000 88bc3154 termdd!IcaRawInput+0x58

ba1bfd90 baa2a265 88bc3008 00000000 89c00418 TDTCP!TdInputThread+0x371

ba1bfdac 80920833 88cea008 00000000 00000000 termdd!_IcaDriverThread+0x4d

ba1bfddc 8083fe9f baa2a218 89cc9508 00000000 nt!PspSystemThreadStartup+0x2e

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

 

 

FOLLOWUP_IP:

rdpdr!RxLowIoCompletionTail+33

ba823c93 8bd8 mov ebx,eax

 

SYMBOL_STACK_INDEX: 1

 

SYMBOL_NAME: rdpdr!RxLowIoCompletionTail+33

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: rdpdr

 

IMAGE_NAME: rdpdr.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 45d697c4

 

STACK_COMMAND: .cxr 0xffffffffba1bee78 ; kb

 

FAILURE_BUCKET_ID: 0x7E_rdpdr!RxLowIoCompletionTail+33

 

BUCKET_ID: 0x7E_rdpdr!RxLowIoCompletionTail+33

 

Followup: MachineOwner

 

******************** End of Minidump info ***********************

 

I connected to a 2003 server SP1 and copied a file and that worked without

an error.

 

On the SP2 server rdpdr.sys version is:

5.2.3790.3959 (srv03_sp2_rtm.070216-1710)

 

On the SP1 server rdpdr.sys version is:

5.2.3790.1830 (srv03_sp1_rtm.050324-1447)

 

Any idea what can be wrong?

 

Regards, Ingi.

[Guest michal]

RE: Blue screen when copying files over RDP connection

 

Hi

 

I'm facing exactly the same problem.

Unfortunatley I have no Win2003Srv SP1 I could grab the file from.

 

Have you got any idea what could I do else about that?

Where can I obtain older (or newer) rdpdr.sys file?

 

Thanks in advance

michal