crash on when i connect the USB type c device to type c port

NTDEV
1

Hi all,

My team were working on the BIOS implementation of ucsi in which they have updated the ACPI update for the type c connector in which inbox driver uses that driver(ucmucsi.sys).

case1: when i connect it run time time i got BSOD of PAGE_FAULT_IN_NONPAGED_AREA (50)
and then i got the dump file and anlyzed in windbg it shows the pdm state change but how i can resolve this error.

Windbg :

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

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: ffffe00582d01d2c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801025a3310, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffe00582d01d2c

FAULTING_IP:
UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480

STACK_TEXT:
ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050 ffffe00582d01d2c 0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx
ffffd000228cf3e0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::`string’+0x10295

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]

SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: UcmCx

IMAGE_NAME: UcmCx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec

FAILURE_BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

Followup: MachineOwner

I dont have control over the inbox driver.

Is any one help on this ?

Regards,
Prabhakar V

2

PAGE_FAULT_IN_NONPAGED_AREA(ucmcx.sys)

On Thu, Feb 23, 2017 at 5:22 PM, wrote:

> Hi all,
>
> My team were working on the BIOS implementation of ucsi in which they have
> updated the ACPI update for the type c connector in which inbox driver uses
> that driver(ucmucsi.sys).
>
> case1: when i connect it run time time i got BSOD of
> PAGE_FAULT_IN_NONPAGED_AREA (50)
> and then i got the dump file and anlyzed in windbg it shows the pdm state
> change but how i can resolve this error.
>
> Windbg :
>
>
> ****************************************
>
>
> 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: ffffe00582d01d2c, memory referenced.
> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
> Arg3: fffff801025a3310, If non-zero, the instruction address which
> referenced the bad memory
> address.
> Arg4: 0000000000000002, (reserved)
>
> Debugging Details:
> ------------------
>
>
> Could not read faulting driver name
>
> READ_ADDRESS: unable to get nt!MmSpecialPoolStart
> unable to get nt!MmSpecialPoolEnd
> unable to get nt!MmPoolCodeStart
> unable to get nt!MmPoolCodeEnd
> ffffe00582d01d2c
>
> FAULTING_IP:
> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
> fffff801025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]<br>&gt;<br>&gt; MM_INTERNAL_CODE: 2<br>&gt;<br>&gt; CUSTOMER_CRASH_COUNT: 1<br>&gt;<br>&gt; DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br>&gt;<br>&gt; BUGCHECK_STR: 0x50<br>&gt;<br>&gt; PROCESS_NAME: System<br>&gt;<br>&gt; CURRENT_IRQL: 0<br>&gt;<br>&gt; LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480<br>&gt;<br>&gt; STACK_TEXT:<br>&gt; ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050 ffffe00582d01d2c<br>&gt; 0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx<br>&gt; ffffd000228cf3e0 0000000000000000 : 0000000000000000 0000000000000000<br>&gt; 0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::string’+0x10295
>
>
> STACK_COMMAND: .bugcheck ; kb
>
> FOLLOWUP_IP:
> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
> fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax4]
>
> SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: UcmCx
>
> IMAGE_NAME: UcmCx.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec
>
> FAILURE_BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateC
> hangedInternal+17c
>
> BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateC
> hangedInternal+17c
>
> Followup: MachineOwner
> ---------
>
>
> I dont have control over the inbox driver.
>
> Is any one help on this ?
>
> Regards,
> Prabhakar V
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

3

If you revert your BIOS changes do things work again?

Have you tried using the various USB logs to see what’s going on before the
crash?

https://msdn.microsoft.com/en-us/library/windows/hardware/jj151577(v=vs.85).aspx

Does !rcdrkd.rcdrloglist show any logs available from the UCM driver? Might
be something in there that is useful.

Good luck!

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@ntdev…

Hi all,

My team were working on the BIOS implementation of ucsi in which they have
updated the ACPI update for the type c connector in which inbox driver uses
that driver(ucmucsi.sys).

case1: when i connect it run time time i got BSOD of
PAGE_FAULT_IN_NONPAGED_AREA (50)
and then i got the dump file and anlyzed in windbg it shows the pdm state
change but how i can resolve this error.

Windbg :

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

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: ffffe00582d01d2c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801025a3310, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffe00582d01d2c

FAULTING_IP:
UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480

STACK_TEXT:
ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050 ffffe00582d01d2c
0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx
ffffd000228cf3e0 0000000000000000 : 0000000000000000 0000000000000000
0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::`string’+0x10295

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]

SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: UcmCx

IMAGE_NAME: UcmCx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec

FAILURE_BUCKET_ID:
X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

Followup: MachineOwner

I dont have control over the inbox driver.

Is any one help on this ?

Regards,
Prabhakar V

4

>>If you revert your BIOS changes do things work again?

I have two platform where i have updated the ACPI loading for UCSI in which
USCI enumeration where proper and check with ucsicontrol.exe to check all
the command where passing. When i connect the USB type c device to USB type
c port at run time of OS where i have not faced any issues of BSOD. For
this hardware ucmucsi.sys of inbox driver is loading.

In other platform where in BIOS page we have the option for enabling the
USB type c port and driver is loaded automatically when i connect any usb
type c device to usb type c port where i got the BSOD , in wat way i can
debug this issue to resolve ?

I have checked the ucsicontrol.exe to get the log using traceview tool for
each command.

Pls help on this issue.

Regards,
Prabhakar V

On Thu, Feb 23, 2017 at 7:27 PM, Scott Noone wrote:

> If you revert your BIOS changes do things work again?
>
> Have you tried using the various USB logs to see what’s going on before
> the crash?
>
> https://msdn.microsoft.com/en-us/library/windows/hardware/jj
> 151577(v=vs.85).aspx
>
> Does !rcdrkd.rcdrloglist show any logs available from the UCM driver?
> Might be something in there that is useful.
>
> Good luck!
>
> -scott
> OSR
> @OSRDrivers
>
> wrote in message news:xxxxx@ntdev…
>
>
> Hi all,
>
> My team were working on the BIOS implementation of ucsi in which they have
> updated the ACPI update for the type c connector in which inbox driver uses
> that driver(ucmucsi.sys).
>
> case1: when i connect it run time time i got BSOD of
> PAGE_FAULT_IN_NONPAGED_AREA (50)
> and then i got the dump file and anlyzed in windbg it shows the pdm state
> change but how i can resolve this error.
>
> Windbg :
>
>
> ****************************************
>
>
> 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: ffffe00582d01d2c, memory referenced.
> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
> Arg3: fffff801025a3310, If non-zero, the instruction address which
> referenced the bad memory
> address.
> Arg4: 0000000000000002, (reserved)
>
> Debugging Details:
> ------------------
>
>
> Could not read faulting driver name
>
> READ_ADDRESS: unable to get nt!MmSpecialPoolStart
> unable to get nt!MmSpecialPoolEnd
> unable to get nt!MmPoolCodeStart
> unable to get nt!MmPoolCodeEnd
> ffffe00582d01d2c
>
> FAULTING_IP:
> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
> fffff801025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]<br>&gt;<br>&gt; MM_INTERNAL_CODE: 2<br>&gt;<br>&gt; CUSTOMER_CRASH_COUNT: 1<br>&gt;<br>&gt; DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br>&gt;<br>&gt; BUGCHECK_STR: 0x50<br>&gt;<br>&gt; PROCESS_NAME: System<br>&gt;<br>&gt; CURRENT_IRQL: 0<br>&gt;<br>&gt; LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480<br>&gt;<br>&gt; STACK_TEXT:<br>&gt; ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050 ffffe00582d01d2c<br>&gt; 0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx<br>&gt; ffffd000228cf3e0 0000000000000000 : 0000000000000000 0000000000000000<br>&gt; 0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::string’+0x10295
>
>
> STACK_COMMAND: .bugcheck ; kb
>
> FOLLOWUP_IP:
> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
> fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax4]
>
> SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: UcmCx
>
> IMAGE_NAME: UcmCx.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec
>
> FAILURE_BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdC
> onnectionStateChangedInternal+17c
>
> BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+
> 17c
>
> Followup: MachineOwner
> ---------
>
>
> I dont have control over the inbox driver.
>
> Is any one help on this ?
>
> Regards,
> Prabhakar V
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> lists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

5

USB type c support on windows 10 build 1511 version 10548

On Thu, Feb 23, 2017 at 9:31 PM, Prabhakar V wrote:

> >>If you revert your BIOS changes do things work again?
>
> I have two platform where i have updated the ACPI loading for UCSI in
> which USCI enumeration where proper and check with ucsicontrol.exe to check
> all the command where passing. When i connect the USB type c device to USB
> type c port at run time of OS where i have not faced any issues of BSOD.
> For this hardware ucmucsi.sys of inbox driver is loading.
>
> In other platform where in BIOS page we have the option for enabling the
> USB type c port and driver is loaded automatically when i connect any usb
> type c device to usb type c port where i got the BSOD , in wat way i can
> debug this issue to resolve ?
>
> I have checked the ucsicontrol.exe to get the log using traceview tool for
> each command.
>
> Pls help on this issue.
>
> Regards,
> Prabhakar V
>
> On Thu, Feb 23, 2017 at 7:27 PM, Scott Noone wrote:
>
>> If you revert your BIOS changes do things work again?
>>
>> Have you tried using the various USB logs to see what’s going on before
>> the crash?
>>
>> https://msdn.microsoft.com/en-us/library/windows/hardware/jj
>> 151577(v=vs.85).aspx
>>
>> Does !rcdrkd.rcdrloglist show any logs available from the UCM driver?
>> Might be something in there that is useful.
>>
>> Good luck!
>>
>> -scott
>> OSR
>> @OSRDrivers
>>
>> wrote in message news:xxxxx@ntdev…
>>
>>
>> Hi all,
>>
>> My team were working on the BIOS implementation of ucsi in which they
>> have updated the ACPI update for the type c connector in which inbox driver
>> uses that driver(ucmucsi.sys).
>>
>> case1: when i connect it run time time i got BSOD of
>> PAGE_FAULT_IN_NONPAGED_AREA (50)
>> and then i got the dump file and anlyzed in windbg it shows the pdm state
>> change but how i can resolve this error.
>>
>> Windbg :
>>
>>
>> ****************************************
>>
>>
>> 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: ffffe00582d01d2c, memory referenced.
>> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
>> Arg3: fffff801025a3310, If non-zero, the instruction address which
>> referenced the bad memory
>> address.
>> Arg4: 0000000000000002, (reserved)
>>
>> Debugging Details:
>> ------------------
>>
>>
>> Could not read faulting driver name
>>
>> READ_ADDRESS: unable to get nt!MmSpecialPoolStart
>> unable to get nt!MmSpecialPoolEnd
>> unable to get nt!MmPoolCodeStart
>> unable to get nt!MmPoolCodeEnd
>> ffffe00582d01d2c
>>
>> FAULTING_IP:
>> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>> fffff801025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]<br>&gt;&gt;<br>&gt;&gt; MM_INTERNAL_CODE: 2<br>&gt;&gt;<br>&gt;&gt; CUSTOMER_CRASH_COUNT: 1<br>&gt;&gt;<br>&gt;&gt; DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br>&gt;&gt;<br>&gt;&gt; BUGCHECK_STR: 0x50<br>&gt;&gt;<br>&gt;&gt; PROCESS_NAME: System<br>&gt;&gt;<br>&gt;&gt; CURRENT_IRQL: 0<br>&gt;&gt;<br>&gt;&gt; LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480<br>&gt;&gt;<br>&gt;&gt; STACK_TEXT:<br>&gt;&gt; ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050 ffffe00582d01d2c<br>&gt;&gt; 0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx<br>&gt;&gt; ffffd000228cf3e0 0000000000000000 : 0000000000000000 0000000000000000<br>&gt;&gt; 0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::string’+0x10295
>>
>>
>> STACK_COMMAND: .bugcheck ; kb
>>
>> FOLLOWUP_IP:
>> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>> fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax4]
>>
>> SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>>
>> FOLLOWUP_NAME: MachineOwner
>>
>> MODULE_NAME: UcmCx
>>
>> IMAGE_NAME: UcmCx.sys
>>
>> DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec
>>
>> FAILURE_BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdC
>> onnectionStateChangedInternal+17c
>>
>> BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+
>> 17c
>>
>> Followup: MachineOwner
>> ---------
>>
>>
>> I dont have control over the inbox driver.
>>
>> Is any one help on this ?
>>
>> Regards,
>> Prabhakar V
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list online at: http:>> lists.cfm?list=ntdev>
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at http:
>>
>> To unsubscribe, visit the List Server section of OSR Online at <
>> http://www.osronline.com/page.cfm?name=ListServer&gt;
>>
>
></http:></http:>

6

ACPI table we have updated the PDO od :ACPI\VEN_USB&DEV_c000 ,ACPI\USBC000
,*USBC000 in which inbox driver (ucmucsi.sys) is loaded.

When i connect the UCSI device to this port im getting the BSOD of
PAGE_FAULT_IN_NONPAGED_AREA
(50)
in ucmcx.sys of connection manager.

My firmware team were updating the firmware for this chip and doing the
BIOS implementation of UCSI.

Is any one help on how to resolve the issue ?

On Thu, Feb 23, 2017 at 9:33 PM, Prabhakar V wrote:

> USB type c support on windows 10 build 1511 version 10548
>
> On Thu, Feb 23, 2017 at 9:31 PM, Prabhakar V
> wrote:
>
>> >>If you revert your BIOS changes do things work again?
>>
>> I have two platform where i have updated the ACPI loading for UCSI in
>> which USCI enumeration where proper and check with ucsicontrol.exe to check
>> all the command where passing. When i connect the USB type c device to USB
>> type c port at run time of OS where i have not faced any issues of BSOD.
>> For this hardware ucmucsi.sys of inbox driver is loading.
>>
>> In other platform where in BIOS page we have the option for enabling the
>> USB type c port and driver is loaded automatically when i connect any usb
>> type c device to usb type c port where i got the BSOD , in wat way i can
>> debug this issue to resolve ?
>>
>> I have checked the ucsicontrol.exe to get the log using traceview tool
>> for each command.
>>
>> Pls help on this issue.
>>
>> Regards,
>> Prabhakar V
>>
>> On Thu, Feb 23, 2017 at 7:27 PM, Scott Noone wrote:
>>
>>> If you revert your BIOS changes do things work again?
>>>
>>> Have you tried using the various USB logs to see what’s going on before
>>> the crash?
>>>
>>> https://msdn.microsoft.com/en-us/library/windows/hardware/jj
>>> 151577(v=vs.85).aspx
>>>
>>> Does !rcdrkd.rcdrloglist show any logs available from the UCM driver?
>>> Might be something in there that is useful.
>>>
>>> Good luck!
>>>
>>> -scott
>>> OSR
>>> @OSRDrivers
>>>
>>> wrote in message news:xxxxx@ntdev…
>>>
>>>
>>> Hi all,
>>>
>>> My team were working on the BIOS implementation of ucsi in which they
>>> have updated the ACPI update for the type c connector in which inbox driver
>>> uses that driver(ucmucsi.sys).
>>>
>>> case1: when i connect it run time time i got BSOD of
>>> PAGE_FAULT_IN_NONPAGED_AREA (50)
>>> and then i got the dump file and anlyzed in windbg it shows the pdm
>>> state change but how i can resolve this error.
>>>
>>> Windbg :
>>>
>>>
>>> ****************************************
>>>
>>>
>>> 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: ffffe00582d01d2c, memory referenced.
>>> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
>>> Arg3: fffff801025a3310, If non-zero, the instruction address which
>>> referenced the bad memory
>>> address.
>>> Arg4: 0000000000000002, (reserved)
>>>
>>> Debugging Details:
>>> ------------------
>>>
>>>
>>> Could not read faulting driver name
>>>
>>> READ_ADDRESS: unable to get nt!MmSpecialPoolStart
>>> unable to get nt!MmSpecialPoolEnd
>>> unable to get nt!MmPoolCodeStart
>>> unable to get nt!MmPoolCodeEnd
>>> ffffe00582d01d2c
>>>
>>> FAULTING_IP:
>>> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>>> fffff801025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; MM_INTERNAL_CODE: 2<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; CUSTOMER_CRASH_COUNT: 1<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; BUGCHECK_STR: 0x50<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; PROCESS_NAME: System<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; CURRENT_IRQL: 0<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; STACK_TEXT:<br>&gt;&gt;&gt; ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050
>>> ffffe00582d01d2c 0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx<br>&gt;&gt;&gt; ffffd000228cf3e0 0000000000000000 : 0000000000000000
>>> 0000000000000000 0000000000000000 0000000000000000 : nt! ??<br>&gt;&gt;&gt; ::FNODOBFM::string’+0x10295
>>>
>>>
>>> STACK_COMMAND: .bugcheck ; kb
>>>
>>> FOLLOWUP_IP:
>>> UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>>> fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax4]
>>>
>>> SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
>>>
>>> FOLLOWUP_NAME: MachineOwner
>>>
>>> MODULE_NAME: UcmCx
>>>
>>> IMAGE_NAME: UcmCx.sys
>>>
>>> DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec
>>>
>>> FAILURE_BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdC
>>> onnectionStateChangedInternal+17c
>>>
>>> BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+
>>> 17c
>>>
>>> Followup: MachineOwner
>>> ---------
>>>
>>>
>>> I dont have control over the inbox driver.
>>>
>>> Is any one help on this ?
>>>
>>> Regards,
>>> Prabhakar V
>>>
>>> —
>>> NTDEV is sponsored by OSR
>>>
>>> Visit the list online at: http:>>> lists.cfm?list=ntdev>
>>>
>>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>>> software drivers!
>>> Details at http:
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at <
>>> http://www.osronline.com/page.cfm?name=ListServer&gt;
>>>
>>
>>
></http:></http:>

7

Have you hooked up a hardware analyzer? Check traces between a working
platform and your platform. Enable Verifier on the relevant drivers and see
if you get an easier crash to deal with. Dump the recorder logs as I
previously mentioned.

In parallel you probably also want to open a support ticket with Microsoft,
they’ll be able to definitively tell you what the inbox driver is doing.

-scott
OSR
@OSRDrivers

“Prabhakar V” wrote in message news:xxxxx@ntdev…
ACPI table we have updated the PDO od :ACPI\VEN_USB&DEV_c000 ,ACPI\USBC000
,USBC000 in which inbox driver (ucmucsi.sys) is loaded.

When i connect the UCSI device to this port im getting the BSOD of
PAGE_FAULT_IN_NONPAGED_AREA (50)

in ucmcx.sys of connection manager.

My firmware team were updating the firmware for this chip and doing the BIOS
implementation of UCSI.

Is any one help on how to resolve the issue ?

On Thu, Feb 23, 2017 at 9:33 PM, Prabhakar V wrote:

USB type c support on windows 10 build 1511 version 10548

On Thu, Feb 23, 2017 at 9:31 PM, Prabhakar V wrote:

>>If you revert your BIOS changes do things work again?

I have two platform where i have updated the ACPI loading for UCSI in which
USCI enumeration where proper and check with ucsicontrol.exe to check all
the command where passing. When i connect the USB type c device to USB type
c port at run time of OS where i have not faced any issues of BSOD. For this
hardware ucmucsi.sys of inbox driver is loading.

In other platform where in BIOS page we have the option for enabling the USB
type c port and driver is loaded automatically when i connect any usb type c
device to usb type c port where i got the BSOD , in wat way i can debug this
issue to resolve ?

I have checked the ucsicontrol.exe to get the log using traceview tool for
each command.

Pls help on this issue.

Regards,
Prabhakar V

On Thu, Feb 23, 2017 at 7:27 PM, Scott Noone wrote:
If you revert your BIOS changes do things work again?

Have you tried using the various USB logs to see what’s going on before the
crash?

https://msdn.microsoft.com/en-us/library/windows/hardware/jj151577(v=vs.85).aspx

Does !rcdrkd.rcdrloglist show any logs available from the UCM driver? Might
be something in there that is useful.

Good luck!

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@ntdev…

Hi all,

My team were working on the BIOS implementation of ucsi in which they have
updated the ACPI update for the type c connector in which inbox driver uses
that driver(ucmucsi.sys).

case1: when i connect it run time time i got BSOD of
PAGE_FAULT_IN_NONPAGED_AREA (50)
and then i got the dump file and anlyzed in windbg it shows the pdm state
change but how i can resolve this error.

Windbg :

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

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: ffffe00582d01d2c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801025a3310, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------

Could not read faulting driver name

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffe00582d01d2c

FAULTING_IP:
UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
fffff801025a3310 418b2c81 mov ebp,dword ptr [r9+rax*4]<br><br>MM_INTERNAL_CODE: 2<br><br>CUSTOMER_CRASH_COUNT: 1<br><br>DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br><br>BUGCHECK_STR: 0x50<br><br>PROCESS_NAME: System<br><br>CURRENT_IRQL: 0<br><br>LAST_CONTROL_TRANSFER: from fffff80058d7b095 to fffff80058d5c480<br><br>STACK_TEXT:<br>ffffd000228cf3d8 fffff80058d7b095 : 0000000000000050 ffffe00582d01d2c <br>0000000000000000 ffffd000228cf630 : nt!KeBugCheckEx<br>ffffd000228cf3e0 0000000000000000 : 0000000000000000 0000000000000000 <br>0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::string’+0x10295

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c
fffff801`025a3310 418b2c81 mov ebp,dword ptr [r9+rax4]

SYMBOL_NAME: UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: UcmCx

IMAGE_NAME: UcmCx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d8ec

FAILURE_BUCKET_ID:
X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

BUCKET_ID: X64_0x50_UcmCx!UcmConnectorPdConnectionStateChangedInternal+17c

Followup: MachineOwner
---------

I dont have control over the inbox driver.

Is any one help on this ?

Regards,
Prabhakar V

—
NTDEV is sponsored by OSR

Visit the list online at:
http:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
drivers!
Details at http:

To unsubscribe, visit the List Server section of OSR Online at
http:</http:></http:></http:>