Surface Pro7 Frequent Errors and Blue Screen Problems

Anonymous
2019-12-16T11:47:56+00:00

Dear Microsoft Community,

A week ago I bought a brand-new Surface Pro 7. I am a big Surface fan and was very excited to use my new device for the purpose of my studies.

My system configuration is a Surface Pro 7 with an Intel® Core™ i5 – 1034G4 CPU, 8 GB of RAM and a 256 GB SSD.

I updated Windows 10 to the most recent version and, so far, did not install third-party software on the device. I connected an original Microsoft Surface Pen and a Microsoft Surface Type Cover. No other hardware was connected.

During the usage I soon experienced very frequent Blue Screens and restarts as a result. These Blue Screens happened in tablet mode as well as in desktop mode. As the problems with Blue Screens became so frequent that I was unable to use the device for my everyday work, and their stop codes did not even allow me to trace back the actual error, I became very frustrated.

In the attached pictures I documented a use scenario, where I used my Surface Pro 7 with normal (office and Microsoft Edge surfing) workload. Within this 45 minutes use case scenario, I encountered 6 Blue Screens (1:01; 1:05; 1:11; 1:23; 1:26; and 1:38 pm), all with different stop codes.

Could you please help me resolve this issue?

Tim

Surface | Surface Pro | Install and update

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.

0 comments No comments

61 answers

Sort by: Oldest
  1. Anonymous
    2020-06-27T14:54:27+00:00

    Okay so here's what I ended up finding out after giving up on the unit which was a home addition unit. I ordered a  Windows 10 Pro  Surface Pro 7 for business directly from Microsoft, connected it to dock v1, and tested with up to 4 monitors plus surface screen. I repeated the following test for each added monitor starting with no external monitor. 

    USBc monitor connection tests resulted as described in the other post... 2 usbc monitors seems to not be supported. But no blue screen. Removing the pluggable, still doesn't allow for the USBc port to be used, registered but doesn't receive signal. I hypothesize that at least one more plugiable could be added on the basis that each one is another graphics card.

    Each related  updated increased stability and in one case an additional monitor.  In the end, with all updates upto win 10 pro v1909. It is capable of 3 external monitors using the dock v1, 2 x mini display ports, Plugables 1 x USB 3.1 to hdmi adapter, the surface screen. The portable adapter works because it's adding an additional graphics device.

    The on board gpu/chipset will not support more than 2 external plus surface screen. The Plugable adapter integrates via a new registered graphic device. However using the USB-c side jack allows a 4th monitor to be registered but it will not get signal.

    The repeatable test I used was a graphics bench mark. I was able to run one instance per monitor. The blue screen would occur whenever these were shutdown. So it was trying to clean up memory when it would BSOD. On the business unit, when shutting these down, I would have to close it twice before they would shutdown after stability update, they would shut down after showing the credits on a 5 seconds delay.

    So on the new unit I wasn't  able to repro the issue. 

    Either their is a patch on the business unit and not on the home Edition or there is a memory or controller hardware issue on these units. I am leaning toward the latter.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-07-02T14:54:10+00:00

    Either their is a patch on the business unit and not on the home Edition or there is a memory or controller hardware issue on these units. I am leaning toward the latter.

    I would also think it is the later, but we can not be sure but in combination how brocken 2004 is on the Surface Pro 7 it could be true.

    For me it looks like we will be stuck on 1909 untiled the next version of 20.. or even 21... , when the support for 1909 goes untie 22.

    Version Servicing option Availability date OS build Latest revision date End of service: Home, Pro, Pro Education, Pro for Workstations and IoT Core End of service: Enterprise, Education and IoT Enterprise
    2004 Semi-Annual Channel 2020-05-27 19041.331 2020-06-18 2021-12-14 2021-12-14
    1909 Semi-Annual Channel 2019-11-12 18363.904 2020-06-16 2021-05-11 2022-05-10

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-07-15T16:00:44+00:00

    many threads have been started about this issue. Got mine in november, problems started in december (probably after updates) couldnt fix it no matter what troubleshooting they had me try. ended up sending for a replacement in Feb, but since my mailing address is an APO, my brother back stateside had to be the "middle man" to send it back to me. just got it back today and its working so far with no blue screens. we'll see after updates.

    long story short, to fix this problem, just get it replaced.

    @Edridge De Castro - I had almost the identical issues and time frames as you. I got mine replaced - rec'd in February - but the replacement has started doing the same thing. I have been in touch with their CS again, and again they said I could have it replaced. I use this for work, so being without a computer is not an option and at this point I don't want to have them charge my CC for a new one while I get the old one back to them - as I don't really think it's going to solve the problem. I am really frustrated

    • I'm a Samsung customer and thought this product looked awesome - but Microsoft has failed and in the process lost my business - I'm going back to Samsung.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-07-20T00:34:45+00:00

    Hi together,

    I've had the same issue for about a week with my Surface Pro 7 i5-1035G4, 8 GB Ram, 256 GB SSD, Windows 10 1909 Build 18363.959. I had Bluescreens with random errors.

    This is what helped solve this issue:

    1. I made sure that Windows 10 had every available update except from the Mai 2020 Update which is not yet available.
    2. Remove graphic card driver via device manager.
    3. Reboot
    4. Use Intel Driver and Support Assistant to update intel drivers for Graphic Card, Audio, Bluetooth and WIFI. (I just let Intel update everything it found)

    Intel auto detection

    1. Don't give up until you ran the intel updates and try it again if there are BSOD's in the process.

    I did the following steps before, but they could not prevent the surface from giving BSOD's:

    1. sfc /scannow in command window
    2. cleanup of system drive "c:" including windows update files
    3. Installation of the surface pro driver package from here: Surface Pro Drivers
    4. Windows Memory Check
    5. Run Surface Diagnostic Kit (failed each time with BSOD ;-))

    My theory is, that the device was overheating due to corrupt display drivers. This was causing memory errors and resulted in random error messages. Since I am using intel drivers, it is running significantly cooler. I've been power using my surface for two days now and no BSOD yet.

    Please share this if my method helped you. I know how frustrating it is to have an unreliable device.

    Edit 2020-07-21: Oh no, still having problems!

    • Office and Browsing: no BSOD
    • Videos: still random BSOD'S

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-07-28T14:56:20+00:00

    I purchased my Pro 7 back in May.  Had an unrelated issue regarding dropping wifi signal randomly.  Contacted CS, they couldn't resolve, so authorized a replacement.  I got the replacement and in under 2 weeks, I start having this issue.  I too NEED mine for work and cannot tolerate these poor reliability issues.  I'm not sure what my options are.  If there was an option to get a refund, at this point I'd do this.  Incredibly frustrating and costing me revenue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments