send bug report to Microsoft

[Guest .rip]

Hi, experts!!

 

Windows 2003 TS reboots after BSOD sometimes. I analysed minidump using

windbg and decided to place command's output "analyze -v" here:

 

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

 

Loading Dump File [C:\Program Files\Debugging Tools for

Windows\Mini081507-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:

srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs) Free

x86 compatible

Product: Server, suite: TerminalServer

Built by: 3790.srv03_sp1_rtm.050324-1447

Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988

Debug session time: Wed Aug 15 15:08:20.085 2007 (GMT+11)

System Uptime: 23 days 2:00:47.316

Loading Kernel Symbols

...................................................................................................................

Loading User Symbols

Loading unloaded module list

..................................................

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

*

*

* Bugcheck Analysis

*

*

*

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bdfeb0a6, 0, bff6822e, 0}

 

Could not read faulting driver name

Probably caused by : RDPDD.dll ( RDPDD!SSICopyRect+13c )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

*

*

* Bugcheck Analysis

*

*

*

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

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or

it

is pointing at freed memory.

Arguments:

Arg1: bdfeb0a6, memory referenced.

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: bff6822e, If non-zero, the instruction address which referenced the

bad memory

address.

Arg4: 00000000, (reserved)

Debugging Details:

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

 

Could not read faulting driver name

READ_ADDRESS: bdfeb0a6

FAULTING_IP:

RDPDD!SSICopyRect+13c

bff6822e f3a5 rep movsd

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0x50

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from 808689ee to 8087b6be

STACK_TEXT:

f38eba18 808689ee 00000050 bdfeb0a6 00000000 nt!KeBugCheckEx+0x1b

f38eba68 80837d0a 00000000 bdfeb0a6 00000000 nt!MmAccessFault+0x813

f38eba68 bff6822e 00000000 bdfeb0a6 00000000 nt!KiTrap0E+0xdc

f38ebb0c bff67ffe bd702010 bdfeb4a6 00000000 RDPDD!SSICopyRect+0x13c

f38ebb2c bff67ee6 bc58ac58 f38ebb48 00000000 RDPDD!SSISaveBits+0xd6

f38ebb58 bf8a93e9 00000000 00000000 00000000 RDPDD!DrvSaveScreenBits+0xf0

f38ebb88 bf8a9148 bc01c008 00000000 00000000 win32k!GreSaveScreenBits+0x69

f38ebbd0 bf892f79 be62e320 00000000 03010041 win32k!CreateSpb+0x167

f38ebc38 bf891874 be4b06e8 bf9b4a40 bf9b4a40 win32k!zzzChangeStates+0x448

f38ebc80 bf891f9a bf9b4a40 00000000 be62e320 win32k!zzzBltValidBits+0xe2

f38ebcd8 bf89336c be4b06e8 00000000 f38ebd24

win32k!xxxEndDeferWindowPosEx+0x13a

f38ebcf4 bf89e854 be62e320 ffffffff 00000096 win32k!xxxSetWindowPos+0xb1

f38ebd40 80834d3f be62e320 ffffffff 00000096 win32k!NtUserSetWindowPos+0x163

f38ebd40 7c82ed54 be62e320 ffffffff 00000096 nt!KiFastCallEntry+0xfc

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

00b6f634 00000000 00000000 00000000 00000000 0x7c82ed54

 

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

RDPDD!SSICopyRect+13c

bff6822e f3a5 rep movsd

FAULTING_SOURCE_CODE:

 

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: RDPDD!SSICopyRect+13c

MODULE_NAME: RDPDD

IMAGE_NAME: RDPDD.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 424377d8

FAILURE_BUCKET_ID: 0x50_RDPDD!SSICopyRect+13c

BUCKET_ID: 0x50_RDPDD!SSICopyRect+13c

Followup: MachineOwner

---------

 

I try find similar bugs on support.microsoft.com, but unsuccessfully. I sure

- this is bug "rdpdd" or "win32k", but I can't send bug report to Microsoft

because don't know how ??? Can help me ???

[Guest Vera Noest [MVP]]

Re: send bug report to Microsoft

 

Have you searched the KB for "STOP 0x50"? A bugcheck of 0x50 is

amongst the most common, and there are numerous KB articles about

them.

 

That said: the normal way to report bugs is to call Microsoft

Support and ask them for help with your problem. If the problem

really is caused by a bug in the OS, you will not have to pay

anything for the support.

 

Note however that your server is still on SP1. The first thing that

Microsoft will do is to ask you to update to SP2. SP2 contains

numerous fixes and several of them have to do with the graphics

system.

 

Before you call them, you should also perform the troubleshooting

steps as documented on the MSDN Bug Check Code page for Bug Check

0x50, especially the hardware diagnostics tests and disabling any

anti-virus software that is installed on the Terminal Server:

http://msdn2.microsoft.com/en-us/library/ms793437.aspx

 

Here are the post-SP2 hotfixes for STOP 0x50 that I know of:

 

909445 - Error message when you start a Terminal Services session

on a Windows Server 2003-based computer: "STOP: 0x00000050

(0xffffffe8, 0x00000001, 0x8083fb88, 0x00000000)"

http://support.microsoft.com/?kbid=909445

 

926128 - You receive a "STOP 0x50" error message that is related to

win32k!HmgDecrementShareReferenceCount+0xb on a Windows Server

2003-based terminal server

http://support.microsoft.com/?kbid=926128

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?LnJpcA==?= <rip@discussions.microsoft.com> wrote on 19

aug 2007 in microsoft.public.windows.terminal_services:

> Hi, experts!!

>

> Windows 2003 TS reboots after BSOD sometimes. I analysed

> minidump using windbg and decided to place command's output

> "analyze -v" here:

>

> Microsoft ® Windows Debugger Version 6.6.0003.5

> Copyright © Microsoft Corporation. All rights reserved.

>

> Loading Dump File [C:\Program Files\Debugging Tools for

> Windows\Mini081507-01.dmp]

> Mini Kernel Dump File: Only registers and stack trace are

> available Symbol search path is:

> srv*c:\symbols*http://msdl.microsoft.com/download/symbols

> Executable search path is:

> Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4

> procs) Free x86 compatible

> Product: Server, suite: TerminalServer

> Built by: 3790.srv03_sp1_rtm.050324-1447

> Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988

> Debug session time: Wed Aug 15 15:08:20.085 2007 (GMT+11)

> System Uptime: 23 days 2:00:47.316

> Loading Kernel Symbols

> .................................................................

> ................................................. Loading User

> Symbols Loading unloaded module list

> .................................................

> *****************************************************************

> ************** *

>

> *

> * Bugcheck Analysis

>

> *

> *

>

> *

> *****************************************************************

> ************** Use !analyze -v to get detailed debugging

> information. BugCheck 50, {bdfeb0a6, 0, bff6822e, 0}

>

> Could not read faulting driver name

> Probably caused by : RDPDD.dll ( RDPDD!SSICopyRect+13c )

> Followup: MachineOwner

> ---------

> 0: kd> !analyze -v

> *****************************************************************

> ************** *

>

> *

> * Bugcheck Analysis

>

> *

> *

>

> *

> *****************************************************************

> ************** PAGE_FAULT_IN_NONPAGED_AREA (50)

> Invalid system memory was referenced. This cannot be protected

> by try-except, it must be protected by a Probe. Typically the

> address is just plain bad or it

> is pointing at freed memory.

> Arguments:

> Arg1: bdfeb0a6, memory referenced.

> Arg2: 00000000, value 0 = read operation, 1 = write operation.

> Arg3: bff6822e, If non-zero, the instruction address which

> referenced the bad memory

> address.

> Arg4: 00000000, (reserved)

> Debugging Details:

> ------------------

>

> Could not read faulting driver name

> READ_ADDRESS: bdfeb0a6

> FAULTING_IP:

> RDPDD!SSICopyRect+13c

> bff6822e f3a5 rep movsd

> MM_INTERNAL_CODE: 0

> CUSTOMER_CRASH_COUNT: 1

> DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

> BUGCHECK_STR: 0x50

> CURRENT_IRQL: 1

> LAST_CONTROL_TRANSFER: from 808689ee to 8087b6be

> STACK_TEXT:

> f38eba18 808689ee 00000050 bdfeb0a6 00000000

> nt!KeBugCheckEx+0x1b f38eba68 80837d0a 00000000 bdfeb0a6

> 00000000 nt!MmAccessFault+0x813 f38eba68 bff6822e 00000000

> bdfeb0a6 00000000 nt!KiTrap0E+0xdc f38ebb0c bff67ffe bd702010

> bdfeb4a6 00000000 RDPDD!SSICopyRect+0x13c f38ebb2c bff67ee6

> bc58ac58 f38ebb48 00000000 RDPDD!SSISaveBits+0xd6 f38ebb58

> bf8a93e9 00000000 00000000 00000000 RDPDD!DrvSaveScreenBits+0xf0

> f38ebb88 bf8a9148 bc01c008 00000000 00000000

> win32k!GreSaveScreenBits+0x69 f38ebbd0 bf892f79 be62e320

> 00000000 03010041 win32k!CreateSpb+0x167 f38ebc38 bf891874

> be4b06e8 bf9b4a40 bf9b4a40 win32k!zzzChangeStates+0x448 f38ebc80

> bf891f9a bf9b4a40 00000000 be62e320 win32k!zzzBltValidBits+0xe2

> f38ebcd8 bf89336c be4b06e8 00000000 f38ebd24

> win32k!xxxEndDeferWindowPosEx+0x13a

> f38ebcf4 bf89e854 be62e320 ffffffff 00000096

> win32k!xxxSetWindowPos+0xb1 f38ebd40 80834d3f be62e320 ffffffff

> 00000096 win32k!NtUserSetWindowPos+0x163 f38ebd40 7c82ed54

> be62e320 ffffffff 00000096 nt!KiFastCallEntry+0xfc WARNING:

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

> 00b6f634 00000000 00000000 00000000 00000000 0x7c82ed54

>

> STACK_COMMAND: .bugcheck ; kb

> FOLLOWUP_IP:

> RDPDD!SSICopyRect+13c

> bff6822e f3a5 rep movsd

> FAULTING_SOURCE_CODE:

>

> SYMBOL_STACK_INDEX: 3

> FOLLOWUP_NAME: MachineOwner

> SYMBOL_NAME: RDPDD!SSICopyRect+13c

> MODULE_NAME: RDPDD

> IMAGE_NAME: RDPDD.dll

> DEBUG_FLR_IMAGE_TIMESTAMP: 424377d8

> FAILURE_BUCKET_ID: 0x50_RDPDD!SSICopyRect+13c

> BUCKET_ID: 0x50_RDPDD!SSICopyRect+13c

> Followup: MachineOwner

> ---------

>

> I try find similar bugs on support.microsoft.com, but

> unsuccessfully. I sure - this is bug "rdpdd" or "win32k", but I

> can't send bug report to Microsoft because don't know how ???

> Can help me ???