Random BSOD with different error codes on ASUS UX303UB

Hello,

friend of mine has problem with his new ASUS UX303UB with Windows 10. He is getting random BSOD, usually it happens when he leaves PC for a while and it goes to sleep, but also there are BSODs when he is typing something into Word, surfing the net ...

I have no idea what can be problem, I've tried to update drivers from ASUS web page, but it seems to be even worse

I attached logs from DM Log Collector tool and also from BlueScreenView.

Pls, can someone help me? Thank you very much in advance

• DESKTOP-Q0N5KJ4-21_10_2016__95824,71.zip (5.09 MB, 1 views)
• peter all.txt (93.2 KB, 0 views)

All the dumps I looked at indicate memory_corruption_large. This can be RAM, other hardware or a driver problem.

You're running mixed memory which is know to cause weird problems like this. Remove the 4GB module and run with just the 8GB module. Re-seat it to make sure it's firmly inserted and seated. See if that helps. If it does get another 8GB the same as the one you have or replace both with an identical pair.

Hi, Ztruker, thank you for your help. This computer is few weeks old came with 12 GB from factory, so don't know how it is with warranty if I try to open that. Anyway thank you very much for help, will post new info

All the memory should have been matching is that is how it came from the factory.

This is what the dump shows:

Code:

[Memory Device (Type 17) - Length 40 - Handle 0013h]   Physical Memory Array Handle  0012h   Memory Error Info Handle      [Not Provided]   Total Width                   64 bits   Data Width                    64 bits   Size                          4096MBForm Factor                   0dh - SODIMM   Device Set                    [None]   Device Locator                ChannelA-DIMM0   Bank Locator                  BANK 0   Memory Type                   18h - Specification Reserved   Type Detail                   0080h - Synchronous   Speed                         1600MHzManufacturer                  SK Hynix   Serial Number                            Asset Tag Number                           Part Number                   HMT451S6BFR8A-PB [Memory Device (Type 17) - Length 40 - Handle 0014h]   Physical Memory Array Handle  0012h   Memory Error Info Handle      [Not Provided]   Total Width                   64 bits   Data Width                    64 bits   Size                          8192MBForm Factor                   0dh - SODIMM   Device Set                    [None]   Device Locator                ChannelB-DIMM0   Bank Locator                  BANK 2   Memory Type                   18h - Specification Reserved   Type Detail                   0080h - Synchronous   Speed                         1600MHzManufacturer                  Samsung   Serial Number                            Asset Tag Number                           Part Number                   M471B1G73EB0-YK0 

Adding or removing memory will not void the warranty. If it was my laptop, I'd replace the 4GB memory modulr with another 8GB module identical to the one already installed. For the time being, just remove the $GB module and see if that helps. It may not but it's an easy test to make.

If it doesn't help then I suggest enabling Driver Verifier and see if that shows us anything.

===================================================
Driver Verifieris a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier'sverification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifierwill run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to
PART TWO
and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifierfor more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Alwayscreate a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.