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.
ATT Surface 3 can stay aside of this issue, since it uses its own set of drivers, different than for "Norht America, outside of US".
In one of history update description on Microsoft site i read:
In January 19 Release:
In addition to the updates list above, the following additional update is available for Surface 3 (Verizon 4G LTE):
Might be this fix is similar to my issue
ATT Surface 3 can stay aside of this issue, since it uses its own set of drivers, different than for "Norht America, outside of US".
In one of history update description on Microsoft site i read:
In January 19 Release:
In addition to the updates list above, the following additional update is available for Surface 3 (Verizon 4G LTE):
- Surface IA7260 Firmware Update (v1544.01.00.28) improves mobile broadband network stability.
Might be this fix is similar to my issue
So I have an UNLOCKED LTE for the US. I'm using it on Verizon VZW has not been offered to me. The update you refer to is specific to the dedicated VZW SKU. I have no idea of how these vendor specific updates work, but will ask.
One of the "Michaels" posting in this thread posted elsewhere that he was using Hamachi and VMware. I'd like to know if any of you folks are using anything that hooks the network stack (both of these do) and what program and version number of these programs are.
Purchased an unlocked Surface 3 LTE model (the 128GB/4GB version) last week from the Microsoft Store, and I have the same exact critical errors as Michael_A_P. However, the device does seem to eventually boot, which leads me to believe that the driver is attempting to call for a resource/library during the initial boot process that hasn't yet loaded.
These errors only occur from a cold boot, not from sleep. I have hibernate disabled.
I haven't tried a reset or to load the BMR downloaded image (off-topic -- why doesn't Microsoft provided an updated build for these devices), but I suspect it would not fix the problem as it hasn't for other users.
I've tested the LTE modem with a T-Mobile SIM card and WiFi turned off and it seems to work, but haven't used it anywhere except at my house, so I can't repro the modem crashing during use. If it would be helpful, I can take it out for a quick drive around town this week to see if I can get the modem to crash.
I am thinking about returning the device only because I don't want to wait until I'm out traveling to have the modem start crashing on me. The whole point of purchasing the LTE version was so I could use it when I was out without worrying about finding a WiFi network. I'm also having tons of COM server timeouts for about a dozen different programs, which is unsettling.
that would be a good data point to have.
>>If it would be helpful, I can take it out for a quick drive around town this week to see if I can get the modem to crash.
__________________________________________________________________________________________________
Barb
Windows Experience MVP
My Blog - http://digitalmediaphile.com/
Please mark as answered if this answers your question
