WHEA uncorrectable error Win 10, bugcheck 124, ASUS laptop Eee VX6S

Hi, Rich,
I've updated the drivers via AMD to latest Catalyst 15.7.1 package (also with 16.2.2 Crimson package), they both carry the latest driver for the card which is 15.301.x.x - still the same issue.
I've reset the bios to optimized defaults and it didn't help.
Now the BIOS suggestion is absolutely wrong - I've got the latest BIOS released for that laptop. What your suggestion carried was a completely different board with a completely different chipset - that just doesn't make sense. Looks like some suggestion by some strange driver software.

The following code is interesting, I couldn't see it myself when I trying using WinDbg:

Code:

BugCheck 124, {0, ffffd28d0b412028, b6000400, 4e00800}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

However it tells me (and I could be wrong) that while the Microsoft Symbols package was loaded in that WinDbg session the respective AMD symbols which probably can be obtained from AMD were not loaded, hence the message above.
Would be interesting to see this analysis when AMD symbols are loaded.

Ztruker said:

Ah, I see you attached it to your first post instead of your last one.

The latest dump shows:

Code:

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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd28d0b412028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000400, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000004e00800, Low order 32-bits of the MCi_STATUS value.

That error (BUSL0_SRC_ERR_M_NOTIMEOUT_ERR) means the processor sent out a read request to L0 cache, and there was a delay in return (either a cache miss, or invalid data in cache). Could be a hardware problem but most likely a driver problem. - Cluberti

Code:

BugCheck 124, {0, ffffd28d0b412028, b6000400, 4e00800}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

This belongs to your AMD Radeon HD 7400M Series card. The driver you have is version 8.17.0010.1433 dated 26/02/2016. That's fairly new, but need to see if there is a newer one available.

Another thing I notice is your BIOS is quite old:

Code:

BIOS Version                  VX6S.0501
  BIOS Starting Address Segment f000
  BIOS Release Date             03/05/2012

The web site for your motherboard: Access Denied
has much newer BIOS. Please download and install the latest, MAXIMUS VII HERO BIOS 3103, dated 2016/04/15.

See if that helps.

Hi, Rich,
I've already tried DDU though I went back to do a clean install of the latest AMD drivers.
That didn't help. I backed up the partition with Acronis True Image, and then tried to format the C: drive and do a clean W10 install (since this one was an upgrade).
I have to say that after numerous attempts (I had to convert the entire drive to GPT first) I still cannot install windows as this darn PC just hangs at various stages, sometimes during the installer load, sometimes somewhere after copying the files. So I have a feeling that something else is faulty here, however I need to pinpoint what.
If you can suggest a good hardware testing suit that I can run from DOS/Mini Win or etc. would be great. I already have several Multiboot repair images (DLC, MOBSCENE21's, HirenBootCD 15.2). What would be best is the latest Eurosoft PC-Check, but these guys are too damn expensive.

Ztruker said:

I don't know how I got off on that ASUS MAXIMUS VII HERO board, sorry. I do see now that you have the latest BIOS for your EeePC.

All I can suggest is to try some of the older drivers for the video card. You have already tried the latest including the Crimson and you still have the problem. Nothing newer available so the only way to go is older, at least for now.

I suggest completely uninstalling the display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then install latest driver for you card.

Then do a custom install of only the graphics driver. No Catalyst Control Center or other additions, a minimum custom install.

See if that gets rid of the problem.

Repeat for older drivers and see if you can find one that's stable for you.

Hi, Rich,
Additionally to my comment above I forgot to tell you that now during the installation when it doesn't hang on "copying files 0%", it crashes at the same stage with KMODE EXCEPTION NOT HANDLED

However there is no driver indicated in that error and the hard drive is pretty much empty.
I haven't checked the hidden partitions yet (hoping to find some dump files there), but on the partition (I repartitioned the drive) there's no dump files just 4 folders with some temp stuff.

Pretty frustrating this laptop is :)

Forgot to post an answer for this thread when I finally was able to resolve the issue.
The issue appeared to be a faulty USB3.0 ports/controller.
Once I've stopped using them and instead used the USB2.0 port I was able to use the computer normally - reinstall Windows 10, drivers, ran tests, benchmark and stress tests - all worked well.
The moment you connect a device to a USB3 port - it crashes with the WHEA error.
So my solution is to use a port replicator/USB replicator or some other USB card if more ports are needed.