Windows 10: Windows 10 Build 20221.1000 crash when plugin to Razer Core Chroma with Thunderbolt 3

Hi,


I previously asked a question regarding about. The problem identified was USBPCap.sys. I have uninstalled the program. Then, I plug in the Thunderbolt again. I continue to have a Green screen, this time, the dump is as following, please help.


Best regards,

Jack


___________________




4: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted i.e. double remove.Arg2: ffffc28d6cb0ea60, Address of the trap frame for the exception that caused the bugcheckArg3: ffffc28d6cb0e9b8, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10905 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on JP-X1C Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 13492 Key : Analysis.Memory.CommitPeak.Mb Value: 124 Key : Analysis.System Value: CreateObject Key : Dump.Attributes.FilterDumpFile Value: 1 Key : WER.OS.Branch Value: rs_prerelease Key : WER.OS.Timestamp Value: 2020-09-19T18:57:00Z Key : WER.OS.Version Value: 10.0.20221.1000ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202bDUMP_FILE_ATTRIBUTES: 0x1840 Filter DumpBUGCHECK_CODE: 139BUGCHECK_P1: 3BUGCHECK_P2: ffffc28d6cb0ea60BUGCHECK_P3: ffffc28d6cb0e9b8BUGCHECK_P4: 0TRAP_FRAME: ffffc28d6cb0ea60 -- .trap 0xffffc28d6cb0ea60NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffc38db93441e8 rbx=0000000000000000 rcx=0000000000000003rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000rip=fffff8050e1082f9 rsp=ffffc28d6cb0ebf0 rbp=ffffc38dc64deb18 r8=fffff8051c4e0cf0 r9=ffffc38db9344140 r10=ffffc38db8e9e098r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na pe cyWdf01000!RtlFailFast+0x5:fffff805`0e1082f9 cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffffc28d6cb0e9b8 -- .exr 0xffffc28d6cb0e9b8ExceptionAddress: fffff8050e1082f9 Wdf01000!RtlFailFast+0x0000000000000005 ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemERROR_CODE: NTSTATUS 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003EXCEPTION_STR: 0xc0000409STACK_TEXT: ffffc28d`6cb0e738 fffff805`09822ca9 : 00000000`00000139 00000000`00000003 ffffc28d`6cb0ea60 ffffc28d`6cb0e9b8 : nt!KeBugCheckExffffc28d`6cb0e740 fffff805`09823110 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69ffffc28d`6cb0e880 fffff805`09821290 : 00000000`00000000 ffffc38d`00000005 ffffc28d`6cb0ec00 00000000`00000000 : nt!KiFastFailDispatch+0xd0ffffc28d`6cb0ea60 fffff805`0e1082f9 : 00003c72`47161fd8 ffffc38d`b8e9e020 ffffc38d`b9344080 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x350ffffc28d`6cb0ebf0 fffff805`1c4e23ca : ffffc38d`c64dee10 ffffc38d`c64dee02 00000000`00000000 ffffc38d`b8e9e020 : Wdf01000!imp_WdfRequestMarkCancelableEx+0x39a49 [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 3529] ffffc28d`6cb0ec70 fffff805`1c4e1508 : 00000000`00000004 ffffc38d`c64dee10 ffffc28d`6cb0ee00 00000000`00000000 : USBXHCI!Bulk_RetrieveNextStage+0x34affffc28d`6cb0ed30 fffff805`0e0ca482 : ffffc28d`6cb0ee19 00000000`00000030 ffffc38d`b7840d70 00003c72`39b215c8 : USBXHCI!Bulk_WdfEvtIoQueueReadyNotification+0xd8ffffc28d`6cb0eda0 fffff805`0e0c88fe : ffffc38d`b8e9e000 ffffc38d`c64dea02 00000000`00000000 ffffc38d`c64dee10 : Wdf01000!FxIoQueue:ispatchEvents+0x792 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3055] ffffc28d`6cb0ee80 fffff805`0e0d4f3e : 00000000`00000602 ffffc38d`b8e9e020 00000000`00000000 ffffc28d`6cb0ef51 : Wdf01000!FxIoQueue::QueueRequest+0xae [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 2371] ffffc28d`6cb0eef0 fffff805`1c572f13 : ffffc38d`b9344080 fffff805`1c571200 ffffc38d`b9344140 00003c72`48d52338 : Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x5be [minkernel\wdf\framework\shared\core\km\fxdeviceapikm.cpp @ 494] ffffc28d`6cb0efb0 fffff805`1c5722a5 : ffffc38d`b80cc000 fffff805`0966f20f ffffffff`ffffffff ffffc38d`b9344080 : ucx01000!Urb_USBPORTStyle_ProcessURB+0x413ffffc28d`6cb0f070 fffff805`0e0c5570 : ffffc38d`b9344140 00000000`00000030 ffffc38d`b5a4fb40 00000000`00000000 : ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0xb5ffffc28d`6cb0f100 fffff805`096704f5 : 00000000`00000004 ffffc38d`b5a4fb40 00000000`00000000 ffffc38d`b9344140 : Wdf01000!FxDevice:ispatchWithLock+0xd0 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] ffffc28d`6cb0f160 fffff805`0e31af9d : ffffc38d`b5a4fb40 ffffc38d`b9344140 ffffc38d`ad606bc0 ffffc28d`00000030 : nt!IofCallDriver+0x55ffffc28d`6cb0f1a0 fffff805`0e3110d6 : ffffc38d`add0b8d0 00000000`00000007 ffffc38d`b9344600 ffffe781`43694000 : ACPI!ACPIIrpDispatchDeviceControl+0xadffffc28d`6cb0f1e0 fffff805`096704f5 : 00000000`00000007 00000000`00000000 ffffc28d`6cb0f309 fffff805`19c47310 : ACPI!ACPIDispatchIrp+0xc6ffffc28d`6cb0f260 fffff805`19bf757b : 00000000`00000001 fffff805`09e283b4 00000000`00000600 00000000`00000000 : nt!IofCallDriver+0x55ffffc28d`6cb0f2a0 fffff805`0e0c5570 : ffffc38d`b9344140 ffffc38d`b9344140 ffffc38d`b9344140 ffffc38d`b816dc70 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0x2bbffffc28d`6cb0f370 fffff805`096704f5 : 00000000`00000009 ffffc38d`b8ff0e00 00000000`00000000 ffffc38d`b9344140 : Wdf01000!FxDevice:ispatchWithLock+0xd0 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] ffffc28d`6cb0f3d0 fffff805`0e31af9d : ffffc38d`b8ff0e00 ffffc38d`b9344140 00000000`000000c0 00000000`00000000 : nt!IofCallDriver+0x55ffffc28d`6cb0f410 fffff805`0e3110d6 : ffffc38d`add0ebe0 00000000`00000007 ffffc38d`b9344648 ffffc38d`b9344080 : ACPI!ACPIIrpDispatchDeviceControl+0xadffffc28d`6cb0f450 fffff805`096704f5 : 00000000`00000007 ffffc38d`b9344140 ffffc28d`6cb0f5d9 ffffc38d`b90c41b8 : ACPI!ACPIDispatchIrp+0xc6ffffc28d`6cb0f4d0 fffff805`1a131de7 : 00000000`00000001 ffffc38d`b9344140 ffffc28d`6cb0f5d9 ffffc38d`00000000 : nt!IofCallDriver+0x55ffffc28d`6cb0f510 fffff805`1a1319aa : 00000000`00000000 ffffc38d`b90b4968 00000000`00000000 00000000`000000ff : usbccgp!DispatchPdoUrb+0x2d7ffffc28d`6cb0f640 fffff805`1a131292 : ffffc38d`b9344140 ffffc38d`b90c41b0 ffffc38d`b90c41b8 00000000`00000000 : usbccgp!DispatchPdoInternalDeviceControl+0x1caffffc28d`6cb0f6b0 fffff805`096704f5 : ffffc38d`b90c4060 00000000`00000001 00000000`00000000 00000000`00000000 : usbccgp!USBC_Dispatch+0x282ffffc28d`6cb0f780 fffff805`0e31af9d : ffffc38d`b9112d70 ffffc38d`b9344140 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55ffffc28d`6cb0f7c0 fffff805`0e3110d6 : ffffc38d`aefe3010 00000000`00000007 ffffc38d`b9344648 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xadffffc28d`6cb0f800 fffff805`096704f5 : 00000000`00000007 ffffc38d`b3fed010 fffff805`052b1100 ffffc38d`b3fed180 : ACPI!ACPIDispatchIrp+0xc6ffffc28d`6cb0f880 fffff805`05277414 : ffffc38d`b3fed180 ffffc38d`b3fed010 fffff805`052b1108 ffffc38d`b3fed010 : nt!IofCallDriver+0x55ffffc28d`6cb0f8c0 fffff805`0529ed20 : ffffc38d`b3fed010 fffff805`052b1108 ffffc38d`b3fed010 00000000`00000000 : usbvideo!RegisterInterruptHandler+0xecffffc28d`6cb0f8f0 fffff805`052764e7 : 00000000`00000000 00000000`00000000 ffffc38d`b3fed010 00000000`00000000 : usbvideo!InitializeIrpThreadAndQueue+0x88ffffc28d`6cb0f940 fffff805`0527413d : ffffc38d`b90bccb0 ffffc38d`b90bcbf8 fffff805`052b1108 00000000`00000000 : usbvideo!StartUSBVideoDevice+0x407ffffc28d`6cb0f9b0 fffff805`1d333084 : ffffc38d`b90bcb30 00000000`00000000 ffffc38d`c52ed9a0 fffff805`0a136600 : usbvideo!USBVideoSetPower+0x6dffffc28d`6cb0f9f0 fffff805`096f67cc : ffffc38d`b901a4c0 ffffc38d`c67cd040 fffff805`1d332fb0 ffffc38d`b90bced0 : ks!CKsDevice:assiveWakeDevice+0xd4ffffc28d`6cb0fa50 fffff805`096128a5 : ffffc38d`c67cd040 00000000`00000080 ffffc38d`adcec040 004fa46f`b19bbfff : nt!ExpWorkerThread+0x11cffffc28d`6cb0faf0 fffff805`09814018 : ffffe781`43780180 ffffc38d`c67cd040 fffff805`09612850 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffffc28d`6cb0fb40 00000000`00000000 : ffffc28d`6cb10000 ffffc28d`6cb09000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: USBXHCI!Bulk_RetrieveNextStage+34aMODULE_NAME: USBXHCIIMAGE_NAME: USBXHCI.SYSIMAGE_VERSION: 10.0.20221.1000STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 34aFAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_USBXHCI!Bulk_RetrieveNextStageOS_VERSION: 10.0.20221.1000BUILDLAB_STR: rs_prereleaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {7664763f-c5d4-6ecc-4463-f9090dc998a5}Followup: MachineOwner---------4: kd> lmvm USBXHCIBrowse full module liststart end module namefffff805`1c4d0000 fffff805`1c56c000 USBXHCI pdb symbols C:\ProgramData\Dbg\sym\usbxhci.pdb\41E31EDA280F55B2E12C4650836150D81\usbxhci.pdb Loaded symbol image file: USBXHCI.SYS Mapped memory image file: C:\ProgramData\Dbg\sym\USBXHCI.SYS\87B2548E9c000\USBXHCI.SYS Image path: \SystemRoot\System32\drivers\USBXHCI.SYS Image name: USBXHCI.SYS Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 87B2548E This is a reproducible build file hash, not a timestamp CheckSum: 000AA46F ImageSize: 0009C000 File version: 10.0.20221.1000 Product version: 10.0.20221.1000 File flags: 0 Mask 3F File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: usbxhci.sys OriginalFilename: usbxhci.sys ProductVersion: 10.0.20221.1000 FileVersion: 10.0.20221.1000 WinBuild.160101.0800 FileDescription: USB XHCI Driver LegalCopyright: © Microsoft Corporation. All rights reserved.

4: kd> lmDvstart end module nameffff8697`aaa00000 ffff8697`aacf2000 win32kbase deferred Image path: \SystemRoot\System32\win32kbase.sys Image name: win32kbase.sys Browse all global symbols functions data Timestamp: Thu Jul 24 01:48:57 2025 68812089 CheckSum: 002F25B2 ImageSize: 002F2000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:ffff8697`aad00000 ffff8697`ab0b2000 win32kfull deferred Image path: \SystemRoot\System32\win32kfull.sys Image name: win32kfull.sys Browse all global symbols functions data Timestamp: Wed Jan 21 22:40:12 1976 0B63B2CC CheckSum: 003AF62A ImageSize: 003B2000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:ffff8697`ab0c0000 ffff8697`ab103000 cdd deferred Image path: \SystemRoot\System32\cdd.dll Image name: cdd.dll Browse all global symbols functions data Timestamp: ***** Invalid FC20B247 CheckSum: 00042AB0 ImageSize: 00043000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:-- there are more, but I chop it off...

:)

 

Razer Launches Value-Oriented Cynosa Chroma Keyboards

Razer, the leading global lifestyle brand for gamers, today announced two new additions to the Razer Cynosa Chroma line, a feature-packed but value-priced family of gaming keyboards complete with the personalization and immersion factors that gamers need. Each Cynosa Chroma keyboard sports soft-cushioned keys for a comfortable and responsive touch experience and a spill-resistant design for durability. It also features individually-backlit RGB keys for a colorfully immersive gaming experience driven by Razer Chroma technology.

For those who want a step up in aesthetics, the Cynosa Chroma Pro keyboard features 24 customizable lighting zones underneath the base of the keyboard. This "underglow" lighting effect is the first for a Razer keyboard and provides an added dimension of visual feedback and game integration.









"Razer Chroma is a crucial technology for creating the most immersive gaming experience possible," says Min-Liang Tan, Razer co-founder and CEO. "With the Razer Cynosa and Cynosa Pro keyboards, more gamers will have access to this experience. Cynosa is the most full-featured entry-level keyboard for gamers today."

Unlike other value keyboards, each key on the Cynosa Chroma and Cynosa Chroma Pro is customizable and individually backlit with 16.8 million color options. Officially integrated lighting profiles that change dynamically during gameplay can be activated upon installation for "Overwatch," "Quake Champions," "Diablo" and other popular games.

The Razer Cynosa Chroma and Cynosa Chroma Pro are the first Razer keyboards interfacing with Razer Synapse 3 (Beta) software. Synapse allows users to choose lighting and performance parameters, including their own macros and key binds, and it can be accessed from any computer. The newest version of the cloud-based configurator allows more customization than ever before, with new lighting effects, settings and more.

For more information about Razer Synapse 3, Razerzone.com/synapse-3.

Razer Cynosa Chroma

• Soft cushioned gaming-grade keys
• Individually customizable backlit keys
• Spill-resistant durable design
• 10 key rollover with anti-ghosting
• Chroma backlighting and underglow with 16.8 million customizable color options
• Razer Synapse enabled
• Fully programmable keys with on-the-fly macro recording
• Gaming mode option
• 1000 Hz Ultrapolling

Pricing and Availability

• U.S. $59.99 / EU €69.99
• Razerzone.com - Available Now
• Worldwide -Q4 2017

Razer Cynosa Chroma Pro

• Soft cushioned gaming-grade keys
• Individually customizable backlit keys
• Spill-resistant durable design
• 10 key rollover with anti-ghosting
• Chroma backlighting with 16.8 million customizable color options
• Razer Chroma Underglow with 24 customization zones
• Razer Synapse enabled
• Fully programmable keys with on-the-fly macro recording
• Gaming mode option
• 1000 Hz Ultrapolling

Pricing and Availability

• U.S. $79.99 / EU €89.99
• Razerzone.com - Razerstore Exclusive - Available Now

For more information about the Razer Cynosa Chroma and Razer Cynosa Chroma Pro, please visit www.razerzone.com/gaming-keyboards-keypads/razer-cynosa-chroma

 

thunderbolt 3 to displayport adapter

Hi John,



Thank you for writing to Microsoft Community Forums.



I understand that inconvenience you are facing when the things may not work as expected.

1. What is the make and model of the computer?
   
   
   

When the Thunderbolt 3 is used with certain eighth generation Intel processor-based Windows 10 systems, there is a possibility that the two USB 3.0 ports on the back of the dock (closest to the Ethernet port)
may not be recognized properly by the operating system.





However, I would suggest you to follow the steps mentioned below and let us know if that helps.

1. Disconnect the pluggable Thunderbolt 3 dock from the system and remove its power cable to turn off completely.
   
2. Uninstall the Intel ‘Thunderbolt Software’ present on your system via the Control Panel ->
   Programs and Features and restart the device once.
   
3. Download and install the latest version of the Intel Thunderbolt Software published by your system manufacturer. If you are unable to obtain this download from your system manufacturer, you can download a version directly from Intel
   here -> https://downloadcenter.intel.com/do...-Driver-for-Intel-NUC-Kit-NUC8i7HNK-NUC8i7HVK
   
4. Restart the system once again.
   
5. Reconnect the power cable to the pluggable Thunderbolt 3 dock, and then reconnect the Thunderbolt 3 cable from the dock to your system.
   
6. You should be prompted to authenticate/approve the dock. Follow the onscreen prompts for the completion of the process and check the status of the issue.
   

If the issue still persists I suggest you to get in touch with the
Thunderbolt support for the further assistance.





Hope it helps.



Muralidhar

Microsoft Community Moderator

 

Razer Goes Full Spectrum Color With All-New Chroma Feature

• Razer. Continue Shopping. Razer BlackWidow Ultimate Chroma. Your Price: US$179.99. Currently unavailable. Available on September 2014.