Frequent BSODs, suspecting ssd Huawei Matebook X pro

Oct 24, 2018
2
0
10
Hi everyone,

So as title says, im having 3-7 BSOD every day. The errors are

CRITICAL_PROCESS_DIED, UNEXPECTED_STORE_EXCEPTION and SYSTEM_SERVICE_EXCEPTION.

This is on a Huawei Matebook X pro i7 model. The ssd is a LITE-ON 512GB CA3-8D512.

I havent been able to find an nvme driver for this laptop (maybe anyone can help on that?). The driver installed when the laptop shipped was the microsoft default driver.

Problem is i brought this laptop over from the US and it will be a pain to send back and im looking for a solution. Even if that is to replace the ssd.

Most of the BSODs are throwing the 3 errors i listed above, one however, just one was MEMORY_MANAGEMENT. That set my alarm bells off and i run memtest86+ which passed with flying colors. So i guess that was coincidental?

Nevertheless, there are more instances of the same issue and one guy replaced his SSD with a samsung evo 970 and never had BSODs again. Link to that story here https://www.reddit.com/r/MatebookXPro/comments/94mh0r/matebook_x_pro_bsod_suspecting_its_the_liteon_ssd/

Any help appreciated since everything else is great with this thing. I basically want to ensure its the particular SSD or the fact that it doesnt have an nvme driver in order to proceed with a replacement and not go through returning this overseas.

Thanks in adavnce!!

Oh i completely forgot to add that theres no dump created. For some reason theres never a dump where it should be saved after a crash.
 
memory management includes a lot of components that do not actually refer to physical ram. it means the data in the RAM was not expected. for example virtual memory problems with your storage of your virtual memory file c:\pagefiles.sys will call a bugcheck in memory management but could be caused by your storage device.

so, you should provide the actual memory dump from c:\windows\minidump directory
so the info can be read with a windows debugger.
or look up the error code from the memory management bugcheck (generally parameter 1)

the bugcheck for the store exception could indicate a old driver or malware attempting to modify a windows data structure. in windows 7 days you could do this but now these are compress in memory so a program that hooks into these tend to corrupt the memory. Windows detects the corruption and calls a bugcheck.
it can also happen with bad memory setting, or bugs in your motherboard sata chipset drivers.
it is hard to tell without looking at a memory dump and turning on debug flags.

you can run memtest86 on its own boot image to check to see that your bios memory timings are ok.
you can run cmd.exe or powershell as an admin then run
dism.exe /online /cleanup-image /restorehealth
(to help remove modified windows core files)
run malwarebytes to remove some viruses and malware that hack into your files.

i would also recommend that your turn off virtual memory to delete the hidden c:\pagefile.sys
then reboot and turn it back on and another one will be created. it help dump malware that infects the pagefile.sys and can fix issues where the pagefile.sys is on a bad place on the harddrive.





 
Hi and thanks for the reply!

Unfortunately there was no dump written! I dont know why and im not sure how to tshoot that. Any ideas?

I already ran memtest86+ which passed, are you suggesting some other test?

Also regarding malware, i would say its highly unlikely since i have the laptop for 4 days and i had BSODs from day one, actually within the first hour.

I will be running cleanup as well now.




 
the next time you get a bugcheck, be sure to note parameter 1s value. then you can look it up here:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management

sometimes you can also download and run whocrashed.exe or bluescreenview.exe and it will read memory dumps.

generally, you may not get a memory dump written if the problem is with the storage subsystem. IE if for some reason the drive can not be accessed. some power conditions will just reboot your machine and also not create a memory dump.