Share via

RNDIS USB driver causing BSOD on Windows 10 Fall Creators Update (version 1709)

Anonymous
2017-12-20T10:10:44+00:00

We have had several reports from customers using our instruments that their computers blue screens when plugging in the instrument in the USB socket of the computer after they have updated to version 1709. Our instruments are running Windows Compact 7, so it is official Windows RNDIS drivers in both ends here.

How do we fix this?

EDIT:

Finally solved it!

We had to change the RNDIS driver on the device to behave as Microsoft Windows Mobile Remote Adapter, by changing the Device descriptor fields bDeviceClass = 0xEF, bDeviceSubClass = 0x01 and bDeviceProtocol = 0x01.

This are the values used by Active Sync.

We also had to install Windows Mobile Device Center on the Windows 10 PC to get the Microsoft Windows Mobile Remote Adapter driver working. This also works on the Creators Fall (1803) version of Windows 10!

No need for self-made .INF files or driver signing anymore, everything is signed by Microsoft now.

Ole J. Lium

Norsonic

www.norsonic.com

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

19 answers

Sort by: Most helpful
  1. Anonymous
    2018-06-05T12:30:26+00:00

    Finally solved it!

    We had to change the RNDIS driver on the device to behave as Microsoft Windows Mobile Remote Adapter, by changing the Device descriptor fields bDeviceClass = 0xEF, bDeviceSubClass = 0x01 and bDeviceProtocol = 0x01.

    This are the values used by Active Sync.

    We also had to install Windows Mobile Device Center on the Windows 10 PC to get the Microsoft Windows Mobile Remote Adapter driver working. This also works on the Creators Fall (1803) version of Windows 10!

    No need for self-made .INF files or driver signing anymore, everything is signed by Microsoft now.

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-02-15T10:19:31+00:00

    Hi @all,

    same behaviour here with the Motorola / Zebra MC9200 Bar-code Scanner. If we Cold Boot the Device, Windows 10 (1709) will end in a BSOD before the Device lets You align the Windows CE Screen.

    I managed to disable the USB Interface with devcon.exe by disabling the USB-Host ->

    devcon.exe disable "USB\VID_05E0&PID_200D"

    After the Cold Boot / Align Screen I just turn it ON again ->

    devcon.exe enable "USB\VID_05E0&PID_200D"

    It´s also possible to disable the RNDIS Network Interface (but iface name is generic on different machines) ->

    netsh interface set interface "Ethernet 3" disabled

    Linux / Ubuntu syslog:

    Feb  7 14:56:27 ubuntu kernel: [ 1720.624228] usb 3-1: new full-speed USB device number 2 using xhci_hcd

    Feb  7 14:56:27 ubuntu kernel: [ 1720.764649] usb 3-1: not running at top speed; connect to a high speed hub

    Feb  7 14:56:27 ubuntu kernel: [ 1720.765945] usb 3-1: New USB device found, idVendor=05e0, idProduct=200d

    Feb  7 14:56:27 ubuntu kernel: [ 1720.765949] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

    Feb  7 14:56:27 ubuntu kernel: [ 1720.765952] usb 3-1: Product: Symbol USB ActiveSync RNDIS

    Feb  7 14:56:27 ubuntu kernel: [ 1720.765954] usb 3-1: Manufacturer: Symbol Technologies, Inc.

    Feb  7 14:56:27 ubuntu kernel: [ 1720.765956] usb 3-1: SerialNumber: 765****3-4906-0801-0106-0bc*****0600

    Feb  7 14:52:17 ubuntu gnome-terminal-[2041]: message repeated 18 times: [ Allocating size to GtkBox 0x55f181ba1cd0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?]

    Feb  7 14:56:27 ubuntu mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"

    Feb  7 14:56:27 ubuntu mtp-probe: bus: 3, device: 2 was not an MTP device

    Feb  7 14:56:27 ubuntu kernel: [ 1720.820928] usbcore: registered new interface driver cdc_ether

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848354] transfer buffer not dma capable

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848370] ------------[ cut here ]------------

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848380] WARNING: CPU: 3 PID: 2252 at /build/linux-8h04gD/linux-4.13.0/drivers/usb/core/hcd.c:1595 usb_hcd_map_urb_for_dma+0x41d/0x620

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848381] Modules linked in: rndis_host(+) cdc_ether usbnet mii rfcomm cmac bnep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm arc4 iwldvm snd_hda_codec_realtek btusb snd_hda_codec_generic irqbypass mac80211 btrtl btbcm btintel crct10dif_pclmul snd_hda_intel crc32_pclmul ghash_clmulni_intel bluetooth snd_hda_codec pcbc uvcvideo aesni_intel videobuf2_vmalloc snd_hda_core aes_x86_64 joydev input_leds videobuf2_memops snd_hwdep videobuf2_v4l2 crypto_simd snd_pcm glue_helper iwlwifi serio_raw videobuf2_core cryptd intel_cstate intel_rapl_perf snd_seq_midi videodev snd_seq_midi_event wmi_bmof ecdh_generic thinkpad_acpi cfg80211 snd_rawmidi media nvram snd_seq snd_seq_device snd_timer mei_me mei snd intel_rst lpc_ich soundcore shpchp mac_hid parport_pc ppdev lp parport ip_tables

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848436]  x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid mmc_block psmouse i915 nouveau ahci libahci sdhci_pci sdhci mxm_wmi ttm e1000e i2c_algo_bit drm_kms_helper syscopyarea ptp sysfillrect sysimgblt pps_core fb_sys_fops drm wmi video

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848469] CPU: 3 PID: 2252 Comm: systemd-udevd Not tainted 4.13.0-21-generic #24-Ubuntu

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848470] Hardware name: LENOVO 23498Q0/23498Q0, BIOS G1ETB2WW (2.72 ) 01/31/2017

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848472] task: ffff939a34a145c0 task.stack: ffffb4a708440000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848474] RIP: 0010:usb_hcd_map_urb_for_dma+0x41d/0x620

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848476] RSP: 0018:ffffb4a708443778 EFLAGS: 00010286

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848477] RAX: 000000000000001f RBX: ffff939a0edbe000 RCX: 0000000000000000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848478] RDX: 0000000000000000 RSI: ffff939a7e2cdc78 RDI: ffff939a7e2cdc78

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848479] RBP: ffffb4a7084437b8 R08: 0000000000000001 R09: 00000000000003f5

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848480] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fffffff5

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848482] R13: 0000000001400000 R14: 0000000000000002 R15: ffff939a73468000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848484] FS:  00007fb17ce558c0(0000) GS:ffff939a7e2c0000(0000) knlGS:0000000000000000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848485] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848486] CR2: 000055a1a69d7e58 CR3: 00000001fe734000 CR4: 00000000001406e0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848488] Call Trace:

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848496]  ? try_to_del_timer_sync+0x53/0x80

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848499]  usb_hcd_submit_urb+0x4ab/0xb70

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848504]  ? schedule_timeout+0x18a/0x350

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848506]  ? call_timer_fn+0x130/0x130

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848509]  ? wait_for_completion_timeout+0xac/0x140

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848511]  usb_submit_urb+0x22d/0x560

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848513]  ? usb_free_urb+0x27/0x40

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848515]  usb_start_wait_urb+0x6e/0x180

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848518]  usb_bulk_msg+0xb8/0x160

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848520]  usb_interrupt_msg+0xe/0x10

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848526]  rndis_command+0x1e9/0x410 [rndis_host]

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848530]  generic_rndis_bind+0x198/0x540 [rndis_host]

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848533]  rndis_bind+0x13/0x20 [rndis_host]

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848538]  usbnet_probe+0x3cf/0xa40 [usbnet]

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848542]  usb_probe_interface+0x124/0x300

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848547]  driver_probe_device+0x2ff/0x450

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848549]  __driver_attach+0xa4/0xe0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848551]  ? driver_probe_device+0x450/0x450

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848553]  bus_for_each_dev+0x6e/0xb0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848555]  driver_attach+0x1e/0x20

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848557]  bus_add_driver+0x1c7/0x270

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848560]  driver_register+0x60/0xe0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848563]  usb_register_driver+0x81/0x150

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848565]  ? 0xffffffffc0fa6000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848568]  rndis_driver_init+0x1e/0x1000 [rndis_host]

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848572]  do_one_initcall+0x50/0x1a0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848576]  ? __vunmap+0x81/0xb0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848579]  ? kfree+0x14a/0x160

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848581]  ? kmem_cache_alloc_trace+0x150/0x1b0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848586]  ? do_init_module+0x27/0x1f9

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848588]  do_init_module+0x5f/0x1f9

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848591]  load_module+0x183b/0x1f20

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848597]  ? ima_post_read_file+0x7e/0xa0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848602]  ? security_kernel_post_read_file+0x6b/0x80

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848606]  SYSC_finit_module+0xfc/0x120

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848608]  ? SYSC_finit_module+0xfc/0x120

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848611]  SyS_finit_module+0xe/0x10

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848614]  do_syscall_64+0x5b/0xc0

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848617]  entry_SYSCALL64_slow_path+0x25/0x25

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848619] RIP: 0033:0x7fb17c75b9f9

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848620] RSP: 002b:00007ffdd527a3d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848622] RAX: ffffffffffffffda RBX: 000055a1a6ad88f0 RCX: 00007fb17c75b9f9

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848623] RDX: 0000000000000000 RSI: 00007fb17c4471c5 RDI: 0000000000000011

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848624] RBP: 00007fb17c4471c5 R08: 0000000000000000 R09: 0000000000000000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848625] R10: 0000000000000011 R11: 0000000000000246 R12: 0000000000000000

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848626] R13: 000055a1a69e4540 R14: 0000000000020000 R15: 000055a1a69f0e00

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848628] Code: 48 39 c8 73 30 80 3d e6 44 96 00 00 41 bc f5 ff ff ff 0f 85 26 ff ff ff 48 c7 c7 a0 27 93 97 c6 05 cc 44 96 00 01 e8 24 20 a3 ff <0f> ff 8b 53 64 e9 09 ff ff ff 65 48 8b 0c 25 00 d3 00 00 48 8b 

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848663] ---[ end trace fb37a795725f8547 ]---

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848668] rndis_host 3-1:1.0: RNDIS init failed, -11

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848704] rndis_host: probe of 3-1:1.0 failed with error -11

    Feb  7 14:56:27 ubuntu kernel: [ 1720.848761] usbcore: registered new interface driver rndis_host

    Feb  7 14:56:32 ubuntu kernel: [ 1725.916323] rndis_wlan 3-1:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -110

    Feb  7 14:56:32 ubuntu kernel: [ 1725.917843] usbcore: registered new interface driver rndis_wlan

    Feb  7 14:57:17 ubuntu gnome-terminal-[2041]: Allocating size to GtkBox 0x55f181ba1cd0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-12T14:44:49+00:00

    Have you checked the solution offered by Tom's Hardware?

    http://www.tomshardware.com/answers/id-1982448/ntoskrnl-exe-driver-bsod.html

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-11T07:50:06+00:00

    Hello Valdemar,

    we are already in contact with Microsoft support about this problem:

    REG:117111617169605

    Best regards

    M.Brunner

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-12-20T13:05:21+00:00

    Hi,

    Usually, you'll encounter blue screen errors when Windows encounters something that it can't process which causes it to stop or crash. We need to do further investigation on your concern so that we can identify the cause of the issue. Kindly answer the following questions for clarification:

    • What is the make and model of the computer?
    • Have you checked the manufacturer's website to determine its compatibility with Windows 10?
    • Aside from the instruments that they are using, did they also encounter the same issue with other devices that they are trying to connect in the USB socket?

    Furthermore, we suggest that they close the wizard then restart the computer if the setup does not process. You may follow the steps in this forum article made by Andre Da Costa on how to upgrade Windows 10 manually.

    We're looking forward to your response.

    0 comments No comments