Question How to fix this "WHEA UNCORRECTABLE ERROR" ?

Toggle sidebar Toggle sidebar
M

Miguel_85

Jul 11, 2024
23
1
15
Hello

Laptop model: ASUS X515JA - BQ1575
Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz 1.20 GHz

For some time now I sometimes get "WHEA UNCORRECTABLE ERROR".
In most cases it occurs when laptop runs on battery but it occassionally crashes when plugged in.

- I've started with MyAsus Diagnostics - result - - - > driver suggestion with no additional data so I don't now which particular driver - how to verify which driver should be updated?.
- I run CMD (administrator) and tried SFC /SCANNOW + chkdsk C: /f
- also DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH
- chdcked Display Adapters - drivers seem to be up to date
- I removed Realtek from Network Adapters
- I run WINDOWS Memory Diagnostics Tool - no errors
- in Power Options I've changed max CPU usage to 90%
- I removed laptop cover, cleaned the fan and checked if all cables stick well.

Nothing helped.
Next, I checkedCrystalDiskInfo with no errors
I've checked Display Drivers again and changed the driver.
As a last hope solution I've reinstalled Windows with BSOD crash returned after several days.

- - - - - - - - - - - - - - - - - - - - - -

So, I've analyzed dump file:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffde0cf39e2028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030019, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3343

Key : Analysis.Elapsed.mSec
Value: 4474

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 453

Key : Analysis.Init.Elapsed.mSec
Value: 3810

Key : Analysis.Memory.CommitPeak.Mb
Value: 103

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffde0cf39e2028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30019

FILE_IN_CAB: 071024-8140-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: firefox.exe

STACK_TEXT:
fffff804`25e43908 fffff804`1faffb5b : 00000000`00000124 00000000`00000000 ffffde0c`f39e2028 00000000`b2000000 : nt!KeBugCheckEx
fffff804`25e43910 fffff804`1edb10c0 : 00000000`00000000 fffff804`25e439e9 ffffde0c`f39e2028 ffffde0c`f1346d10 : nt!HalBugCheckSystem+0xeb
fffff804`25e43950 fffff804`1fc0e8df : 00000000`00000000 fffff804`25e439e9 ffffde0c`f39e2028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
fffff804`25e43980 fffff804`1fb0158a : ffffde0c`f38ae680 ffffde0c`f38ae680 ffffde0c`f1346d60 fffff804`1f9813de : nt!WheaReportHwError+0x38f
fffff804`25e43a50 fffff804`1fb019e0 : 00000000`00000000 ffffde0c`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
fffff804`25e43bc0 fffff804`1fb01874 : ffffde0c`f1343810 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0x138
fffff804`25e43c20 fffff804`1fb01b19 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff804`25e43c60 fffff804`1fb00cd2 : 00000000`00000000 00000000`00000000 fffff804`25e43ef0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff804`25e43c90 fffff804`1fb0348b : ffffde0c`f1343810 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62
fffff804`25e43cc0 fffff804`1fb69da9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
fffff804`25e43cf0 fffff804`1fa2843e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff804`25e43d20 fffff804`1fa28053 : 00000000`00000000 00000000`00000000 000001dd`e4dc4de0 fffff804`25e43ef0 : nt!KxMcheckAbort+0x7e
fffff804`25e43e60 00007ffb`28ff5324 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
0000000e`6af3ea70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`28ff5324


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner

- - - - - - - - - - - - - - - - - - - - - -


So it looks that it might be memory issues, is that correct?
 
Sort by date Sort by votes
Welcome to the forums, newcomer!

Open up Device Manager and see if there are any items flagged with a yellow exclamation mark. As for your laptop, see if you have ay BIOS updates pending. Following that, try and manually reinstall the latest chipset drivers for your laptop.
 
Upvote 0 Downvote
Hello
No flags in Device Manager.
Also I forgot to mention that I've already updated BIOS.

How can I check what is my version of Chipset Drivers?
I've looked at Device Manager/System devices but nothing looks like a version name.
Checked System Info - my Baseboard product is X515JA

I downloaded HWiNFO and it seems that my Motherbaord chipset is:
Intel 495 (Ice Lake-U PCH-LP Premium)

I can't find this on Intel Support.... Any help?
Also, I've found a supporting tool for updating drivers: Snappy Driver Installer. Can I use that or is it better to proceed with manual installation?
 
Last edited:
Upvote 0 Downvote
I'd like to see a lot more problem determination data. Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
 
Upvote 0 Downvote
Thanks for the upload. Now I can see that you have mismatched RAM. You have an 8GB stick of Samsung M471A1G44AB0-CWERAM and a 16GB stick of Lexar LD4AS016G-3200ST RAM. Whilst both are 3200MHz RAM with apparently similar latency, it's highly unlikely that the internal timings match.

Mismatched RAM is one of the biggest causes of BSODs, crashes and freezes that we see. I strongly suggest that in the first instance you remove one stick of RAM - ideally the one you added (the 16GB?) and see how it is on just the one stick.

When buying RAM one should always purchase a kit of matched sticks rather than buying individual sticks. Sometimes you can get away with adding another stick with the same part number as the existing one but there's no guarantee there either.
 
Upvote 0 Downvote
Thank You for checking this report.
When I bought this laptop I immediately had problems with BSOD and it was due to one RAM stick damaged. I've returned laptop to the seller and he replaced the RAM stick. I didn't have any issues for more than two years, so I'm surprised that the problem is with mismatched RAM sticks. Why it started to be problem now and not from the beginning?
 
Last edited:
Upvote 0 Downvote
Things wear out at different rates and failures can happen at any time. I didn't say earlier that bad RAM was definitely the cause, I suggested that you remove one stick and see how things go. If it BSODs on each RAM stick on their own then we'll know that your RAM is not the cause.

Bad RAM is a major cause of BSODs and whenever we find mismatched RAM it's always something we need to check.
 
Upvote 0 Downvote
When I removed the cover and again checked hardware I noticed one thing, just want to verify if it may be a problem with this. I noticed that my SSD drive is loose from one side, it is hold by screw but it's not tight so the left part of SSD drive wobbles when pushed by finger.
BSOD occurs when CPU works harder. At theses moments the fan works quicker so maybe it produces more vibrations that have an impact on the SSD Drive. Just guessing here....

1.png
 
Upvote 0 Downvote
''''You have an 8GB stick of Samsung M471A1G44AB0-CWERAM''''
Could You please help me with locating this RAM stick? I took a look at the insides but really can't find this stick.
I've removed Lexar 16GB stick and we will se if that will help with BSOD issue.
IMG-20240719-074151.jpg


IMG-20240719-074202.jpg


IMG-20240719-074204.jpg
IMG-20240719-074157.jpg
 
Upvote 0 Downvote
I might well be under the keyboard. It's definitely there, I can see two RAM sticks in the dumps...
Code: 
[Memory Device (Type 17) - Length 84 - Handle 0022h]
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   1ah - DDR4
  Type Detail                   0080h - Synchronous
  Speed                         3200MHz
  Manufacturer                  Samsung
  Serial Number                        
  Asset Tag Number                        
  Part Number                   M471A1G44AB0-CWE            <==== This is the Samsung
  Attributes                    1
  Extended Size                 0
  Configured Memory Speed       3200
  Minimum Voltage               1200
  Maximum Voltage               1200
  Configured Voltage            1200
  Memory Technology             3
  Memory Operating Mode Capability     8
  Firmware Version              0
  Module Manufacturer Id        52736
  Module Product Id             0
  Memory Subsystem Controller Manufacturer Id  0
  Memory Subsystem Controller Product Id       0
  Non-Volatile Size             0
  Volatile Size                 0
  Cache Size                    0
  Logical Size                  0
[Memory Device (Type 17) - Length 84 - Handle 0023h]
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          16384MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   1ah - DDR4
  Type Detail                   0080h - Synchronous
  Speed                         3200MHz
  Manufacturer                  8A76
  Serial Number                        
  Asset Tag Number                        
  Part Number                   LD4AS016G-3200ST                 <=== This is the Lexar
  Attributes                    1
  Extended Size                 0
  Configured Memory Speed       3200
  Minimum Voltage               1200
  Maximum Voltage               1200
  Configured Voltage            1200
  Memory Technology             3
  Memory Operating Mode Capability     8
  Firmware Version              0
  Module Manufacturer Id        30218
  Module Product Id             0
  Memory Subsystem Controller Manufacturer Id  0
  Memory Subsystem Controller Product Id       0
  Non-Volatile Size             0
  Volatile Size                 0
  Cache Size                    0
  Logical Size                  0
 
Upvote 0 Downvote
I see, can You help with localizing the Samsung stick - I searched for it but can't find it....? I prefer to user Lexar as it's 16GB while Samsung it's only 8GB. I will check both options though.

updated:
I've tested laptop today. Lexar 16 GB stick was removed. I've worked on battery and everything was fine. I had to re-charge laptop. When laptop was fully charged I started working on battery. After 30 minutes again BSOD WHEA_UNCORRECTABLE_ERROR....

So, I'll try and remove Samsung stick this time. But, where it is located? I only see one slot for RAM - the one from which I removed Lexar stick.
 
Last edited:
Upvote 0 Downvote
Sorry, I missed that.
Unfortunately I don't feel confident with dismantling laptops but what to do, I'll give a shot.

Is it possible to get under keyboard without removing other components first, so fan, battery, etc.?
So to get there from the above rather than from the bottom side?
 
Last edited:
Upvote 0 Downvote
I checked manual from official Asus site and unfortunately there is no data regarding RAM stick location.

Nonetheless I dismantled the laptop. Please take a look at below photos.... I removed what I could and still no clue of where to look for this Samsung stick!!!

I honestly have no idea where to look now....


https://www.transfernow.net/dl/20240724ndA5Zyhz

https://www.transfernow.net/dl/20240724wIWJA9FC

https://www.transfernow.net/dl/20240724HvKRcQVC

https://www.transfernow.net/dl/20240724ZbS0qv5S
 
Upvote 0 Downvote
I think I found it. It seems that it is soldered at the back side of this motherboard.
So now there is a problem as I can't remove it....
Is there any other way to disable this soldered RAM and work just on Lexar stick put in the RAM slot?
 
Upvote 0 Downvote
In that case remove the Lexar stick and just run on the Samsung stick. I would also suggest running Memtest86 on just the Samsung stick...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
 
Upvote 0 Downvote
After putting all parts back together after dismantling laptop during Samsung RAM search computer worked fine for nearly 4 straight days... During this time I used up the battery several times and no BSOD occurred. Unfortunately it happened again this morning (again working on battery).

I've just made a test (USB drive prepared on a different device).
Test passed - no issues found....

Should I test the Lexar stick as well? What to do next?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom