CP210x resolving / preventing repeated bugcheck in serial driver silabser.sys
02/38/2019 | 01:14 PM
Hi ,
I'm running into multiple bluescreens a day that appear to be caused by sending data over usb/serial via the CP201x driver, and flushing the serial buffer repeatedly.
Who can help look into this and hopefully resolve this ?
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 000000000000000a, A fatal error has occurred while processing a request on the
queue.
Arg2: ffff858f487d77c0, Pointer to a WDF_QUEUE_FATAL_ERROR_DATA structure.
Arg3: 0000000000000000, Reserved.
Arg4: ffff96896c662de0, Reserved.
Debugging Details:
------------------
...
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: Code.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: YEP
ANALYSIS_SESSION_TIME: 02-07-2019 13:29:55.0941
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff8081e32b407 to fffff80761649b40
STACK_TEXT:
ffff858f`487d7758 fffff808`1e32b407 : 00000000`0000010d 00000000`0000000a ffff858f`487d77c0 00000000`00000000 : nt!KeBugCheckEx
ffff858f`487d7760 fffff808`1e3486cf : 00000000`00000800 ffffdb81`b81c0000 ffff9689`5b402340 00000000`00000000 : Wdf01000!FxVerifierBugCheckWorker+0x1f [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
ffff858f`487d77a0 fffff808`1e3469cb : 00006976`9c51cfd8 00000000`00000009 ffff9689`76c8e010 00000000`00000019 : Wdf01000!FxIoQueue::FatalError+0x3b [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 6375]
ffff858f`487d77f0 fffff807`797d607e : ffff9689`63e766f0 fffff807`617e106d 00000000`00000200 00006976`9c51cfd8 : Wdf01000!imp_WdfIoQueueStopSynchronously+0x4b [minkernel\wdf\framework\shared\irphandlers\io\fxioqueueapi.cpp @ 482]
ffff858f`487d7820 fffff808`1e2d1c4e : ffff9689`76c8e010 00000000`000000d8 ffff9689`5fe41080 00000000`00000000 : silabser+0x1607e
ffff858f`487d7860 fffff807`61556819 : ffff9689`7fb44be0 00000000`00000000 00000000`00000000 00000000`00000002 : Wdf01000!FxDevice::DispatchWithLock+0x1ee [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
ffff858f`487d78c0 fffff807`61b135e1 : ffff9689`76c8e010 00000000`00000000 00000000`00000000 ffff9689`7fb44be0 : nt!IofCallDriver+0x59
ffff858f`487d7900 fffff807`61ae918f : ffff9689`00000000 ffff9689`7fb44be0 ffff858f`487d7b00 ffff858f`487d7b00 : nt!IopSynchronousServiceTail+0x1b1
ffff858f`487d79b0 fffff807`61ae8fb6 : ffff9689`5fe41080 000001ff`3115f070 ffff9689`6c607df0 00000000`00000000 : nt!NtFlushBuffersFileEx+0x1bf
ffff858f`487d7a40 fffff807`6165ad85 : ffff9689`00000000 00000000`00000001 00000000`00000000 ffff858f`487d7b00 : nt!NtFlushBuffersFile+0x16
ffff858f`487d7a80 00007ffb`e934ffc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000f7`48fff6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`e934ffc4
THREAD_SHA1_HASH_MOD_FUNC: 2e8fde283ffdc87ab0b7781e10de2006667f3353
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ef1447556fa65d3a43d1fb703cf867e3ddb6d64e
THREAD_SHA1_HASH_MOD: a8ce1afcbc58f7569c1ac51f81bbb437c60da567
FOLLOWUP_IP:
silabser+1607e
fffff807`797d607e 488b05d3a0ffff mov rax,qword ptr [silabser+0x10158 (fffff807`797d0158)]
FAULT_INSTR_CODE: d3058b48
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: silabser+1607e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: silabser
IMAGE_NAME: silabser.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5bfc4daf
STACK_COMMAND: .thread ; .cxr ; kb
Discussion Forums
Interface
Unanswered
Hi,
1. Can you report the date and time of the VCP failure?
2. Can you attach a complete memory dump? The smaller "Kernel Memory Dump" or "Small Memory Dump" crash dump files might be useful, but invariably we need the Complete one. During a system crash, Windows queries the crash dump settings to determine whether a dump file will be created, and if so, what size the dump file will be. Please refer to the Microsoft webpages on how to configure these crash dump settings (https://msdn.microsoft.com/en-us/library/windows/hardware/ff542953(v=vs.85).aspx). Basically: go to Control Panel > System and Security > System. Click Advanced system settings. Under Startup and Recovery, click Settings.
3. Please provide the Windows System Event Viewer Event Logs (use Windows Explorer to navigate to %SystemRoot%\System32\Winevt\Logs (provide at least Application.evtx, Setup.evtx, and System.evtx)).
4. Describe in as much detail as you can the steps to reproduce the crash.
5. Attach any custom software for us to reproduce it in-house.
6. Describe any steps to lead to the crash.
7. List Silicon Labs devices plugged in at the time of the crash.
8. Does this happen on all/any machines, or just one? If just one, what is "special" about it?
9. Does this happen on all Windows OS versions, or just a particular version (I.e. is it Windows 10 only, or Windows 7 and 10 and 8.1? (if you know))
10. Is there a particular action that your environment performs that causes the crash?
11. Is it "immediate"? Occasional? Or simply "once in a while", "randomly"?
12. Does it require an application to be executed? If so, what action (system call or otherwise) is the application performing that leads to the crash? Does performing that action always cause a crash?
13. Did the crash occur coincident with a power-state change (hibernate? wake-up? shutdown? machine boot-up? Or a device insert or removal?
Thanks!
0
OP,
Can you send me Code.exe? Is that the process you run to create this system crash? And a description of how/what set up I need to repro?
If not, can you get me a MEMORY.DMP file? (I have one or two from other infrequent reports of same 10D crash).
Not that it helps you, but I do already have this as an issue: dev Jira ticket# MCUSW-429.
CP210x resolving / preventing repeated bugcheck in serial driver silabser.sys
Hi ,
Who can help look into this and hopefully resolve this ?
Package version: 10.1.4
Release date: 2018-12-07
Hi,
1. Can you report the date and time of the VCP failure?
2. Can you attach a complete memory dump? The smaller "Kernel Memory Dump" or "Small Memory Dump" crash dump files might be useful, but invariably we need the Complete one. During a system crash, Windows queries the crash dump settings to determine whether a dump file will be created, and if so, what size the dump file will be. Please refer to the Microsoft webpages on how to configure these crash dump settings (https://msdn.microsoft.com/en-us/library/windows/hardware/ff542953(v=vs.85).aspx). Basically: go to Control Panel > System and Security > System. Click Advanced system settings. Under Startup and Recovery, click Settings.
3. Please provide the Windows System Event Viewer Event Logs (use Windows Explorer to navigate to %SystemRoot%\System32\Winevt\Logs (provide at least Application.evtx, Setup.evtx, and System.evtx)).
4. Describe in as much detail as you can the steps to reproduce the crash.
5. Attach any custom software for us to reproduce it in-house.
6. Describe any steps to lead to the crash.
7. List Silicon Labs devices plugged in at the time of the crash.
8. Does this happen on all/any machines, or just one? If just one, what is "special" about it?
9. Does this happen on all Windows OS versions, or just a particular version (I.e. is it Windows 10 only, or Windows 7 and 10 and 8.1? (if you know))
10. Is there a particular action that your environment performs that causes the crash?
11. Is it "immediate"? Occasional? Or simply "once in a while", "randomly"?
12. Does it require an application to be executed? If so, what action (system call or otherwise) is the application performing that leads to the crash? Does performing that action always cause a crash?
13. Did the crash occur coincident with a power-state change (hibernate? wake-up? shutdown? machine boot-up? Or a device insert or removal?
Thanks!
OP,
Can you send me Code.exe? Is that the process you run to create this system crash? And a description of how/what set up I need to repro?
If not, can you get me a MEMORY.DMP file? (I have one or two from other infrequent reports of same 10D crash).
Not that it helps you, but I do already have this as an issue: dev Jira ticket# MCUSW-429.