This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have a new Surface 3 4G LTE with Windows 10 pre-installed (purchased 28/10/15 from UK Microsoft Store). It appears to be working smoothly, including the mobile broadband, but from day one Event Viewer has been showing a dozen or so DriverFrameworks-UserMode "critical" events per day, both Event ID 10110 "A problem has occurred with one or more user-mode drivers..." and 10111 "The device Surface IA7260 Firmware Update... is offline due to a user-mode driver crash. Windows will attempt to restart the driver 5 more times..." There's also an associated Application Error ID 1000 for faulting WUDFHost.exe (faulting module ntdll.dll). Despite this, the IA7260 Firmware Update appears in Device Manager (as a hidden device) connected and working under the Surface 3 Modem Device . Presumably the driver is eventually starting so all is more or less well, but it is rather alarming to see the log filling with "critical" errors, and of course the Reliability History rating is pretty much rock bottom. The other (likely) side effect is that Update History shows numerous instances of installing "System Firmware Update - 18/09/2015" - supposedly successfully in each case - presumably this update contains the IA7260 firmware update.
Does anyone else see this issue on the 4G LTE model? And/or any suggestions for remedy? Thanks!
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.
I have an ATT surface that I've used on Amtrak between Central CA and Los Angeles and honestly haven't seen that problem (admittedly not since the recent firmware update). I'll try this weekend to drive around with it on and running and see if I can repro.
I am sure issue is not related to Mobile Provider. I purchased all devices unlocked in Microsoft store and added to Bell's network. Bell even agreed to replace a SIM card, to check, if it can resolve the problem - but result is still the same.
Same card, inserted to Surface 2 (with adapter), works excellent in the same conditions. With no single stop responding.
The reality of fixing something is this: Microsoft - or someone like the Cell vendor - has to repro it. I understand the issue, but this isn't going to be easy to get fixed without the problem being reported from Bell. Mere events posted in a forum won't cut it. Someone has to get live dumps from it happening.
In the meantime I'll try to see if I can repro/search around on cell device forums to see if there are other reports.
Follow up question - does Bell sell this device or did you take an unlocked device and add it to Bell's network?
The main idea is as follows: Old devices - Ipad LTE (2012), Surface 2 (2014) work great at the same conditions, at the same route, but new Surface 3 devices have issue (3rd item in a rows! has identical issue) regardless of Windows 8.1 or Windows 10. BTW, 02/04/2016 Firmware update was installed on both Windows.
Here's another idea for a repro - can you drive around to see if it repros on towers in other areas.
I have used a Surface3 on a train between my City and Los Angeles - about a five hour train/bus ride.
I would see if there are any reports on the Bell forums as well.
