Wireless Communication Library Support Forum
Frameworks => Bluetooth Framework => Topic started by: TonyJuurlink on January 15, 2016, 09:25:26 PM
-
Hello,
I am getting the following error at "wclServer.Listen()", reproducible the BlueChatServer demo application:
(blue screen)
page fault in nonpaged area (tosrfcom.sys)
The hardware is a Getac V110, windows 8.1 Pro.
Toshiba bluetooth driver tosfusb.sys v8.1.3109.0
Our product uses the .net edition wcl version 6.12.6.0, but I did download your 6.14.8 demo and it is experiencing the same crash.
Do you have any thoughts, or is there any other information you would need to diagnose?
Thanks,
Tony
-
Hello,
Thank you for your report.
I will check it today and back to you with more information about fixes.
-
Hello,
We have been testing it all the day today and finally reproduced the problem. Now we are going to try to fix it. I will update you with result.
-
Thanks for looking at this so promptly Mike
-
Ok, we have been working on this issue and found that:
1. Use the latest WCL availbale on our site. Make sure that after build wcl.dll placed in Build folder has latest WCL version/
2. Update Toshiba drivers to at least 9.x.x.x
Should work. Let me know if it does not and I will continue working on this.
P.S. The problem appeared in Toshiba kernel driver. After update to the 9.x and higher it works as expected.
-
Hi Mike,
I have installed Toshiba Stack v9.10.15 and am still getting the blue screen. I have attached a screenshot of the Programs and Features window with the relevant Toshiba Stack details and Intel bluetooth installs.
Is there anything else that could help troubleshoot?
Thanks,
Tony
[attachment deleted by admin]
-
Do you use the latest WCL version? Whe you build yhe project Visual Studio may still use old one. Please make sure that wcl.dll used by your application has latest version.
Also please trh BluetoothOPPServer demo. Does it crash too?
Do you use 32 or 64 bit wcl.dll?
-
Hi Mike,
I am using the most recent wcl version (trial version download), and reproducing with the chat server demo application. 32bit wcl components. I am out of the office now, but I will try the BluetoothOPPServer demo tomorrow.
Thanks,
Tony
-
Hi Mike,
I've tried the following:
BlueChatServer x86 .Net4 - crashes on Listen
BluetoothOPPServer x86 .Net4 - crashes on Listen
BlueChatServer x64 .Net4 - crashes on Listen
BluetoothOPPServer x64 .Net4 - crashes on Listen
-
Ok, thank you a lot. I am continue working on this matter and will update you as soon as possible with my result.
-
Hello,
Please, try to run the attached application.
After you start it select RFCOMM->RFCOMM Test..
Then click "Assign", then "Create". Let me know if it crashes or no.
[attachment deleted by admin]
-
Mike,
There has been some progress on this end. Our customer has sent us one of their Getac devices, where we were encountering/reproducing the crash. After wiping the device and re-installed Windows 8.1Pro and the toshiba stack (same version as they initially had installed), the crash no longer occurs. We are hoping to get detailed install/update/versioning steps on how they setup their tablets to determine what is being introduced that is causing the crash. If we can isolate the issue, we'll let you know.
We will send our customer the test application you provided and ask that they test following your instructions.
Thanks,
Tony
-
In fact it happens with Toshib asometimes. But that would be really nice if your customer may run the test app. Thank you.
-
Hello Mike,
Our customer has sent us the results. Screenshot attached.
This was their response:
----
We got another tablet with a Bluetooth issue so I did the Toshiba Bluetooth Diagnostic Test. I attached a screenshots of the diagnostic window. I selected the RFCOMM tab, clicked RFCOMM Test, clicked Assign, and clicked Create. One thing I noticed is that the
[attachment deleted by admin]
-
Hello,
Thank you a lot. I continue working on this.
-
Hello,
We executed more tests. It looks that there is something wrong when Toshiba can not initialize its COM port as server (when it says error in test tool). I am not sure yet about the problem place. But I think it is something in WCL, not in Toshiba itself (because test tool does not crash).
Unfortunately it takes some time to fix cause when it works it simple works but when it crashes (not always on our test systems) it is very hard to locate the place.
Any way, we will do all our best to fix it as soon as possible. I will be in touch.
-
Thanks Mike, we appreciate your looking int this. If there is anything we can do to help, let us know.
-
Thank you for your help. I will let you know when will have test version. So I just ask you to test it then.
-
Hey Mike,
Any luck with this?
-
Hello,
Please, try this attached version.
[attachment deleted by admin]
-
Mike,
Has the wclBluetoothDevice.Pair signature changed? Our original code was using
"wcl.wclBluetoothDevice.Pair(wclBluetoothRadio, string)", but I don't see an overload for that now.
-
Hello,
Yes, it has been changed 2 years ago (http://forum.btframework.com/index.php/topic,3215.0.html) in 6.13.4.0
-
Hello Mike,
Using that attached version, I provided our client with a copy of the demo BlueChatServer, and they are still getting the crash when clicking on the "Listen" button.
-
Ok, thank you. I keep working on this.
-
Hey Mike, any luck with this, or is there any sort of diagnostics application our customer could run on an affected tablet?
-
Hello,
Unfortunately no. As I wrote the issue is reproducable but very randomly. We also was able to reproduce it with Toshiba app I sent you (very very randomly). And I think I know why it happens.
The problem with Toshiba is that is uses Windows messages inside kernel mode to notify high-level application about driver events. If window registered for notifications destroyed during or immediately before Toshiba driver (kernel) sends a notification the A/V (BSOD) appears. But that appears not always but only if other window got the same HWND in this time or WndProc code has already removed from memory. Even if app closed but WndProc code are still available and not released for other tasks the BSOD will not appear. That is why it is very hard to fix.
In fact we are trying to solve this somehow but still no luck.
-
Thanks for clarifying.
The behavior in our customer's environment is such that when they re-image a machine from their base snapshot, they do not encounter the issue. According to them, after a period of time of use, the application consistently crashes - not random in their environment. We could reproduce the consistency as they sent us their hardware, and narrowed it down to the Listen() method call.
Would the Toshiba Windows Messaging issue still account for that scenario?
-
Would the Toshiba Windows Messaging issue still account for that scenario?
Probably yes as there is no other reason of crash and also kernel debugging shows exactly this problem.
-
Hey Mike, some minidumps attached in case you have a use for them.
-
Hi,
Thank you a lot. We are working on big WCL update (the first one should be with WiFi Part reworked) which should (as we hope) solve the toshiba issue. But any way, your dump will really help to solve it.
-
Thanks. Any ETA on the release date?
-
Also, we have access to devices which consistently reproduce the bsod, so if you need us to test anything on this end, just let me know.
-
Thanks. Any ETA on the release date?
Unfortunately I can not say exactly. WiFi is planned to release for about 2 weeks or so.
-
Also, we have access to devices which consistently reproduce the bsod, so if you need us to test anything on this end, just let me know.
Thank you a lot. I will let you know in case I need it.
-
Hi Mike, do you know if the WCL 6.15.0.0 release will resolve this issue?
-
Hi,
Unfortunately no, it still may cause the crash with Toshiba. All I can recomend for now is use latest Toshiba driver.