Search results

I have a 2014 Surface pro 3 which I used to use very heavily up to 2018 when I got myself a new Pro 5. I kept on using the pro 3 until a year or two ago when it developed a boot loop which turned out to be something to do with an SD card I had in the slot, it seemed to be working Ok after that...

I sorted it out finally at the weekend. Tried every kind of recover didn't work...tried Linux boot from USB and it worked fine. Retried windows from USB and it looped again....in the end the culprit was an SD card in the slot!! I'd forgotten about it. It only contained music but it stopped...

As title says I've got a well used Surface pro 3 which was working perfectly fine until yesterday when I came down in the morning to see the above message on the screen. I left it to do it's thing came down at lunchtime (from working from home upstairs) to find it still saying the same, then...

It's fine, like new as far as I can see. It's supposed to be a refurb, but I can't see any issues with it. It came in a generic box with no accessories.

The PC world I went to was in Enfield.

Update. I've had the replacement Surface about a month now. First day in it was on duty for my MSc course and since then it's been hammered with connecting to a dock with two monitors and used for programming in Python with PyCharm . No issues whatsoever, it must have been a hardware glitch on...

Well that worked... lol Actually without prompting I have to send my surface in and they're sending me a "high quality refurbished unit" in return... I should have said "don't know you who I am!! I'm a mod on Surface Forums.net and general surface evangelist!! "ha ha ha. Actually i was in a...

Ok well I ended up recovering from a USB stick. I didnt' install anything else just in case and... 2 BSOD. Not sure that I can do anything more now so waiting for MS support to get back to me. Now back on my trusty SP3 for a while. Not sure if I've ever had a BSOD on this device...!

It is now saying it' was scanning drive C and then Windows failed to start which gave me the option to run off a recovery USB, so I've done that. Its not looking terribly good however.

Sadly, today I have had two different blue screens after resetting the device. One Memory_Management blue screen while using the MS store and one Service Exception while browsing using Edge - incidentally I was also downloading the recovery image from the MS site to try that next. Currently...

Still happening so I've reset the device and reinstalled what I need....let's see if it still happens now.

Yeah. I think I might have to reset it. Though so far I've been using it for a few hours since it crashed this morning. I did get some weird pop up about a dll for dropbox being incompatible or something so I'll try installing drop box first and see if that's the issue.

I already did that and it didn't find anything. But I'm running it again.

They are all saying they're on "the best driver". I did have a BSOD while running the ubuntu app once, that's not to say it wasn't trying to do something on wifi at the same time but I wasn't especially running anything at that point.

Ok I've got quite a few Intel Audio Service errors too, Microsoft edge content process stopped, and then going back in time a bit more is where the windows store install process stopped. they all seem a bit random!

Ok so I can see that today's crash might have been caused by a failed WindowsSkype update. But there's a variety of things. Most worrying is this - however when I ran the trouble shooter it tested hardware and found no issues.

Hmm not great.

It's not a year old yet. I have contacted support, I tried the Surface troubleshooter which doesn't find anything. I'll look at reliability monitor... didn't know that existed.

I got the original BSOD's in Oct. since then I updated twice but it happened again this morning - currently I'm on 17134.471

My SP has become virtually unusable due to frequent BSOD errors. I'm getting the windows store exception I had before but also now System_service_exception and once a critical stop exception. I ran the surface troubleshooter which found nothing, but the device is doing it so frequently now I...