Background information

Born to break? Of fragile models and night tests

Martin Jud
22.7.2020
Translation: Patrik Stainbrook

When people work, mistakes happen. The same applies to computers. Sometimes there are bad consequences. Fortunately, in case of broken notebooks, only strained nerves and warranty claims follow. Or is there more to it?

Endless tests, headaches and a happy ending. This best summarises my experiences testing the Surface Book 3. But this isn't just because I'm testing three versions of Microsoft's Surface Book 3. Two of the three models run into some problems during my examinations.

In my review of the Book 3, I didn't talk about having to repeat tests due to defective devices. In truth, I actually tested five models. And rightly so.

Anything that can go wrong will go wrong

What happened?

Resetting to factory settings without data erasure took an unreasonable five hours and didn't help. I only got to grips with this device again after several days. A second reset, which normally takes a long time, seemed to have helped it. Finally, an end to my suffering – still, this thing had to be repaired. Thank god for the warranty and a replacement unit, which was then used in all tests and worked perfectly.

Here's the two results:

7000 points down. The stress test is possibly to blame for the fact that the nVidia GeForce GTX 1660 Ti Max-Q only delivers a fraction of the performance. More precisely, the software HeavyLoad and FurMark are both to blame.

Or it's my fault. There are some warning lights. For example, Chrome hasn't allowed downloads of FurMark for some time now.

FurMark itself also warns against the use of the software:

CAUTION
FurMark is a very GPU-intensive application and may cause instability or system shutdown.
PERFORM THE BURN-IN TEST AT YOUR OWN RISK.
Possible causes for instability: intense overclocking settings, insufficient PSU (power supply), problems with the VGA cooler (GPU and/or VRM)

I naturally reset the book as soon as I notice the defect. I even do it twice – but the graphics card doesn't get up to speed. I have no choice but to repeat all the tests with a night test device. Luckily, this one doesn't act up.

Looking through and comparing the results that the 15-inch book delivered before it broke down, I notice something else: with the broken device, the volume of the fan measured at maximum power from my sitting position was 42 dB. With the night test device, I got 52 dB. Where neither the stress test nor I to blame after all?

I couldn't reproduce the error

If the product has never been used before and comes delivered fresh from our warehouse, it shouldn't be suffering from any problems caused by insensitive pre-testers. And in the end, a single defective product is rarely indicative of a more wide-spread issue. Furthermore, such fragile models aren't limited to individual manufacturers.

The reason this case is noteworthy is due to the amount of devices. Two out of three «broke down» during testing. Not only is this new, but these are the first defective Microsoft devices I have come across. It's quite possible that none of this means anything. But it's still remarkable enough not to keep quiet.

77 people like this article


User Avatar
User Avatar

I find my muse in everything. When I don’t, I draw inspiration from daydreaming. After all, if you dream, you don’t sleep through life.


Computing
Follow topics and stay updated on your areas of interest

Notebooks
Follow topics and stay updated on your areas of interest

Background information

Interesting facts about products, behind-the-scenes looks at manufacturers and deep-dives on interesting people.

Show all

These articles might also interest you

  • Background information

    Cyberpunk 2077 on Mac: can Apple keep up with Nvidia?

    by Samuel Buchmann

  • Background information

    Snapdragon X Elite review – how well do the Microsoft Surface Pro and Laptop perform?

    by Martin Jud

  • Background information

    Apple Silicon in the benchmark: Will the Macbook Pro with the M1 kill the 16-inch Macbook?

    by Dominik Bärlocher