Bluescreen WHEA_UNCORRECTABLE_ERROR hal.dll+37203 0x00000124

Issue solved, link to thread

I have gotten this bluescreen WHEA_UNCORRECTABLE_ERROR (Windows 8.1) 2-3 times now the last 4-5 days.

My cpu temp (40 idle) and gpu temps are fine (gpu may be little high idle, 55 Celsius, but should not be a problem)

The bluescreens happened while surfing the web and watching a youtube clip so my load temps are not any problem.

CPU overclock is stable at 4.0 Ghz have ran this for quite a while without any problem, GPU is running on stock clocks.

This problem started after i switched ram sticks, but i now changed them back to my old ram, but i still got the bluescreen. May i have damaged my motherboard while changing the ram sticks?

specs:


Bluescreen file:

Hello and welcome Mattrix mate it is possible you have damaged the board either physically or otherwise by reseating those sticks try this before anything else.

SLOTCLEANING

Now as for the slotsto clean them use a strip of old credit card about 1/2 inch wide nip thecorners off one end - preferably round them offhold a piece of thin lint free clothover the end dab on some form of alcohol - iso propyl alcohol (what we swab theskin with before an injection) is good and GENTLYswipe along the slots.

This can also be donefor the GPU slot/s.

Thedoctor44 said:

As you haven't tried it yet I suggest Memtest86 as you could have damaged the RAM modules or the motherboard DIMM slots.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

i ran this memtest for 11.5 hours on my new ram without any errors.

Just my 2 cents, I see you have overclocked your cpu and 0x00000124 can be due to too little v-core. You could either try raising the v-core or lower your cpu oc and see how that goes.

Hum I only just noticed too that this is an 8.1 problem may be worth posting in that forum Mattrix just join up with the button at the top run by the same folks and a lot of us "locals" are in there too.

Myself I ma but am not real sure of the OS yet.:)

Prime95 after 2 hours without any errors:


i ran disk check without any errors

i ran sfc /scannow without any errors:


i ran the basic test and the on seatools without any errors:


I will run OCCT instead of Furmark for GPU testing because it tells you if there was any errors. I will do this later today. I will let prime95 run for a couple of more hours. If there is any reason to run Furmark instead of OCCT please say so.

EDIT: The weirdest thing just happened, either i hallucinated hard or something is messed up. Right before a new bluescreen the Realtemp monitor was showing that my cpu was running at 208*20 (4.160ghz). but after the bluescreen i went into the bios and as the first image shows its set to 200*20 (4.0ghz)

the new bluescreen looks like a GPU driver problem that i have had before, not the same bluescreen error but i have had problems with the amd driver (thread link)

bluescreen file: