BSODs on huawei laptop

Turok123

Turok123

Member
Joined
Mar 22, 2018
Posts
22
Location
Russia
Hi,
1-2 times a day the system crashes with different BSOD, the browser was always open when crashing. I reinstalled the network drivers from the official huawei website, it did't help.

These are the Dump Files: dumps
 
Sorry for my long absence in the forum. I've made several attempts to collect information through BSOD Collection Application, but they all ended with the blue extern of death. Today the blue screen of death did not appear while BSOD Collection Application is running.
Since my last message, BSOD has appeared several times.
Here are the answers to the questions:
  • Laptop or Desktop?
Laptop;
  • Exact model number
HUAWEI MateBook D16;
  • OS
Windows 10 Home x64;
  • What was original installed OS on system?
Windows 10 Home x64;
  • Have you re-installed the OS?
Yes. I re-installed OS before I went to the forum for help.
  • CPU
AMD Ryzen 5 4600H;
  • Are you using proxy, vpn, ipfilters or similar software?
No;
  • Are you using Disk Image tools?
No.
 

Attachments

It's concerning that you get BSODs running the data collector app, so I think the first thing we should do is test your RAM.

To do this you need to download the Memtest86 tool from here: MemTest86 - Official Site of the x86 Memory Testing Tool. The free version should be fine. DO NOT USE THE HUAWEI LAPTOP TO DO THIS, USE A DIFFERENT PC.

You will need to make a bootable USB drive using the Memtest86 tool you downloaded. There are instructions on how to do this at: MemTest86 - Creating a MemTest86 boot disk in Windows. The USB drive doesn't need to be large, 1GB will be fine, but all data on the USB drive will be erased! DO NOT USE THE HUAWEI LAPTOP TO DO THIS, USE A DIFFERENT PC.

Plug the Memtest86 bootable USB drive into the Huawei laptop and boot from it. You may need to enter the BIOS setup to change the boot order so that the USB drive is booted first.

Once the USB drive has booted leave the laptop alone. Do not move the mouse and do not press any keys, Memtest86 will start as soon as it boots.

Memtes86 will take several hours to run on your 16GB of RAM but you must leave it alone until it stops on its own. It will complete 4 iterations of the 13 memory tests.

When it ends you will see a display of the results, if even a single error is found then you have a RAM problem. In that case I would suggest removing one stick of RAM and reboot Memtest86 to test just the one stick. If that passes then swap the sticks and test the other one. That should tell you which stick is faulty.

Let's see how that RAM test goes before we look at any further troubleshooting.

BTW. I only read English I'm afraid, so if you could change your system language to English (temporarily) before you upload another data collector output. Thanks!
 
The Memtest results are good, but I still think this is a RAM issue. All the dumps have the look and feel of RAM errors, and the address where the bugcheck happened is in user-mode code in three of them. User mode errors shouldn't cause bugchecks, but since they do then RAM must be suspect.

Memtest isn't perfect (no RAM tester can be) so I would suggest you remove on stick of RAM and see whether it BSODs on a single stick. Give it plenty of time to BSOD, you say it crashes onnce or twice a day, so leave it running on one stick for at least 24 hours. Then swap sticks and run only on the other stick for 24 hours.
 
Ah, so even if the problem turns out to be faulty RAM there nothing you can really do about it. I've gone back and looked more closely at the dumps you uploaded, none of them show any calls to third-party drivers in the call stack, this is a strong suggestion that the problem was hardware related. There is nothing obvious in your System log (even though I can't read it fully). I can see the BSODs but there don't seem to be any other worrying error messages.

I would suggest that the next troubleshooting step is to start Windows in Safe Mode with Networking. In this mode only Windows drivers are loaded, so if it BSODs in Safe Mode it's almost certainly a hardware problem. Because no third-party drivers are loaded in Safe Mode you'll find that many devices don't work as expected, or even at all. Your display for example, will be very low resolution because you'll be using the Windows basic display driver. Despite these restrictions this is an extremely useful test and I urge you to run it for as long as you can in Safe Mode to see whether it BSODs.
 
ubuysa said:
In this mode only Windows drivers are loaded, so if it BSODs in Safe Mode it's almost certainly a hardware problem. Because no third-party drivers are loaded in Safe Mode
Click to expand...
That's not strictly the case, Windows will load any drivers which are specified under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network which is usually just Microsoft drivers so we tend to ask the users to boot into Safe Mode when we suspect there is a hardware issue.
 
x BlueRobot said:
That's not strictly the case, Windows will load any drivers which are specified under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network which is usually just Microsoft drivers so we tend to ask the users to boot into Safe Mode when we suspect there is a hardware issue.
Click to expand...
So does this mean that the system in Safe Mode with Networking can load third-party driver of my WiFi adapter - Netwtw10.sys ?
And if BSOD appears in Safe Mode with Networking, can it still indicate both hardware and software problems ?
 
Last edited:
That’s what I mean. BSODs appear when surfing the Internet and when online games are launched or during the game process. And also, as we found earlier, when running DirectX Diagnostic Tool and other system utilities run by the BSOD Collection Application.
Back to the network issues. Let’s say I start OS in Safe Mode with Networking and it will load my third-party driver of my Wi-Fi adapter. In this mode, I can try to cause a BSOD just by surfing the Internet. If BSOD appears, it can still be caused by a software (third-party driver -> Netwtw10.sys) or hardware problem ?
 
You can check which drivers are going to be loaded in Safe Mode with Networking but querying the registry key I mentioned:

Code: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network
 
There seem to be no third-party drivers.
Code: 
reg query "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network" /s > "%userprofile%\desktop\SafeNet.txt"
command output:
 

Attachments

Which means that if it BSODs in Safe Mode there is a high probability of it being a hardware issue.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top