Yeah, the 2 button restart does not apply to the Surface 3. What problem is causing you to want to do this?
Surface 3 4G LTE: "critical" events logged for IA7260 Firmware Update
![](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)
Anonymous
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!
Surface | Surface Duo | Mobile connectivity
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.
47 answers
Sort by: Most helpful
-
Anonymous
2015-12-30T20:57:29+00:00 -
Anonymous
2015-12-30T19:13:33+00:00 Hello - I have been trying to apply a two-button shutdown to a Surface 3, using the standard procedure (1 - normal shutdown; 2 - press and hold power and volume-up buttons for at least 15 seconds; 3 - release buttons and wait 10 seconds; 4 - press and release power button to turn on again). However, I am finding this does not lead to shutdown: instead, it opens the UEFI/BIOS screen (AMI version 2.17.1246). I am not releasing the power or volume-up button early, as in the standard procedure to access the UEFI/BIOS. Can anyone suggest what might be going wrong here, or suggest any other way of performing a hard "battery out" reset? Thanks!
-
Anonymous
2015-12-10T23:26:53+00:00 Mike_P_416 - Yes, I just removed it completely, so there's an empty SIM slot. (Initially done as part of preparations to return the device for repair/exchange - but I'm still fiddling with it, still faintly hoping for software/firmware remedy from MS. Have also disabled touchscreen to work round "phantom touches": so, with no touchscreen and no SIM, my Surface LTE is just fine. Sort of.)
-
Anonymous
2015-12-10T18:59:10+00:00 Michael_A_P,
Thanks for replay.
What do you mean "removed the SIM"? Just removed at all or replaced with a new one ?
-
Anonymous
2015-12-10T18:46:33+00:00 Thanks, Mike_P_416 - Unfortunately I can't comment on these connection issues, but just a couple of other points: (i) I reset my device again, this time (as suggested by John1F) from a downloaded image (Surface3_BMR_20_10.34.0) - again with no effect on either "critical error" or "phantom touch"; (ii) I removed the SIM (Hutchison 3, not tested elsewhere but no reason to doubt it, and it is working) - no more "critical errors"!