Repeated BSOD after firmware update - Surface pro 3, Windows 10

Did your Surface Pro 3 originally come with 8.1 or 10? If 8.1, you will not be able to download a 10 recovery image. 

http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/downloadablerecoveryimage

I can boot from usb but not restore from a point it says i cannot etc. Called microsoft and they never heard of it . If i buy a car i can also go back now microsoft does not have a centre to go to....

Where can I download fresh win 10 image with drivers ?

Thanks ! Frustrated because i also loose office from the license of a relative which is now already given out...

What a frustration

I really don't want to spend a day or more trying to fix a bungled update; to top it off, my machine is a couple of weeks out of warranty, so the replies in the thread about "happily it's under warranty and they're sending me a new one" are more irritating than anything...if their update bricks my machine, is it going to be "sorry, out of warranty..."?

I'm with you on this, and i asked about this earlier today..

This should serve as a perfect example of why NOT to limit user choices.  In the Win7 that I'm typing this from, I can disable whatever updates I want, simply and quickly, yet the best I can try here is delaying driver updates and "MAYBE" it will prevent the issue.  Mabye.  That's wonderful.

You are preaching to the choir.

Considering the number of posts within the last day on this issue, shouldn't MS have immediately pulled this update?  I really don't have days to waste trying to get something working that was working fine, and that I didn't break, the forced update did.

I asked them to pull the update when I first saw the trending here. I can only ASK. They have undisclosed criteria for making decisions like this. I don't work for Microsoft. Community Moderator's and MVP's are unpaid volunteers. I'm on YOUR side.

Perhaps I'm being paranoid, as the update must have worked for some, but there's nothing worse than being on the road with your laptop and finding it won't boot no matter what you do, and you don't have backup machines with you to cover the time until you can get it working.

I get this, I really do. I feel the same way. I was luckier than folks reporting problems here. No BSOD and successful install. I have other issues which MS says are specific to the router I use, so I rolled back the driver (not the firmware) by force installing the older .193 driver.

So my real questions are, 1) how long before I can safely boot up my SP3 and not have a significant risk of having it bricked the next time I restart it?, and 2) warranty or no warranty, if an update damages something to where it needs to be sent in, is this going to be something they expect ME to pay for?  If so, why?  It would have been done without me having any say so or control over it, since they've eliminated the method that could have been used, to simply disable the update.

If I were in your position, I'd do a manualy system restore point immediately. Then,  I'd disable device driver updates (unplug your router so you don't have an Internet connection while you boot up to do this) and hope this works. I've asked about #2. I don't know if I will get an answer.

What a nightmare!  My SP3 hasn't been used in a week, so I was about to fire it up in preparation for a trip (so it could update etc. before I leave).  Fortunately I happened across this thread in pure coincidence...cleaning up some desktop links.

Now I'm afraid to fire this thing up, in fear it's going to d/l the update and brick itself with me not being able to stop it (guess I can disconnect from wifi, but what good does that do me for actually being able to use it?

I really don't want to spend a day or more trying to fix a bungled update; to top it off, my machine is a couple of weeks out of warranty, so the replies in the thread about "happily it's under warranty and they're sending me a new one" are more irritating than anything...if their update bricks my machine, is it going to be "sorry, out of warranty..."?

This should serve as a perfect example of why NOT to limit user choices.  In the Win7 that I'm typing this from, I can disable whatever updates I want, simply and quickly, yet the best I can try here is delaying driver updates and "MAYBE" it will prevent the issue.  Mabye.  That's wonderful.

Considering the number of posts within the last day on this issue, shouldn't MS have immediately pulled this update?  I really don't have days to waste trying to get something working that was working fine, and that I didn't break, the forced update did.

Perhaps I'm being paranoid, as the update must have worked for some, but there's nothing worse than being on the road with your laptop and finding it won't boot no matter what you do, and you don't have backup machines with you to cover the time until you can get it working.

So my real questions are, 1) how long before I can safely boot up my SP3 and not have a significant risk of having it bricked the next time I restart it?, and 2) warranty or no warranty, if an update damages something to where it needs to be sent in, is this going to be something they expect ME to pay for?  If so, why?  It would have been done without me having any say so or control over it, since they've eliminated the method that could have been used, to simply disable the update.

Or do I need to lug along my faithful-but-large Toshiba Win7 16" laptop that I fortunately kept and is in great working order, with the Win10 update disabled?  We're leaving in a couple of days, and I'm not bringing along a machine that I'm afraid to boot up within range of an internet connection.  Please, MS, disable this update before it does more damage, and think again about restoring user control for those of us who are savvy enough to understand the situation and want to make our own decisions on our own equipment.