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: Newest
  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-06-27T13:02:38+00:00

    Dear all, thank you for sharing your experience. 

    I use the same Windows version and graphics driver as Lukas:B. Have realized that I regularly experience blue screen errors during:

    1. Two screens mode when external display is connected via usb-c plus the tablet screen on;
    2. Two external screens via surface dock v.1 (with or without tablet screen). 

    So the only way to keep away from BSOD I found is to turn off the tablet screen and to use the only one external display via usb-c.

    PS I hope the problem will be solved after the update. Actually found out that I can not update to the new Win version – have to wait.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-06-20T14:10:06+00:00

    It's the blue screen error... Eventually you will get a memory exception in the BSOD... All the other ones, are a timing issue for when the exception is thrown.... Other bad news... 1909, died by eod on me. 

    And home Edition it came with was fine for 4 weeks with updates before I upgraded to both pro and enterprise. 

    So I did a restore to factory,  the just added a pro key.  as soon as it did the first round of updates, which included drivers /firmware, I got a BSOD with a memory write error.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-06-19T13:02:24+00:00

    So we have different use case and I am sure you know more over IT than me and many from MS.

    So if you think it is a memory wirte error, what tool can I use to look into it and confirm it? 

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-06-19T12:35:47+00:00

    Yeah, I didn't but I am on the latest firmware and the drive version posted... I have been to running trading software for 24 hours now and no crashes. It was OK with one monitor on the USB c but not with the dock 2. Or via the expansion side clip.. That adds more USB 3, usbc and regular hdmi.   I am pretty sure it can't handle two usbc monitors at the same time on the current driver, and based on the private memory write errors, it makes sense.  When you have two, one is tiring to the others reserved memory space... Being a software engineer myself... That's where I would look based in the observation.  But I would try the dock 1, 2 is definitely not gonnang to work with 2 monitors until this is fixed.

    Was this answer helpful?

    0 comments No comments