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

61 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-05-06T13:43:18+00:00

    Dear all, I use surface pro 7 i5-256-16 for 1 year and 4 months (12 hours a day on average). I often got a BSOD problem with it.

    I finally realized that the reason is SSD in my case. Every time from the fresh reinstalled system, I have almost no BSODs, but more and more after some time of using. Finally, I experience BSOD nearly every half an hour under any load (like OCR tasks or file copy).

    What helped me to reduce the problem significantly is the manual launch of checking the disk. I run “cmd” as an administrator, then use “chkdsk C: /f /r /x” command and answer “Yes” to plan the check after a restart. It resolved the problem (at least for some time).

    I hope that can help somebody.

    Was this answer helpful?

    0 comments