Question Windows WHEA Uncorrectable Error - Whats next?

Apr 17, 2019
7
0
10
Hey guys,

I will add myself to the row of people, that ran into an WHEA Bluescreen error. I already studied a lot of Threads regarding that topic, but found nothing that helpes me out. Maybe you have more ides to try.

My system:
MSI Mortar B250M Micro ATX Mainboard
i7 7700k
1TB m2 Samsung Evo SSD 960 Pro
64GB Corsair Dominator DDR4 2666 RAM
3TB Data HD
Palit GeForce RTX 2070
Be Quiet Dark Power Pro 650W Gold Power Supply
Fractal Define Tower
Windows 10 Professional

My system was runing stable for some month (last update with the RTX) and before also without any problems. Suddenly the crashes appeared to happen more and more often. Right now, I am falling into them even after Minutes. It does not depend on high load, sometimes also crashes while idle.

What have I tried so far:
  • Installing drivers from Chipset, via, Graphic Cards
  • Removed all unecessary Software
  • Did a windows Repair
  • Cleaned all the hardware
  • Run a Memtest and intel CPU test, all passed
  • Removed Memory and tested single modules
  • Removed RTX graphics card and tested only with onboard
  • Installed Windows on a USB Stick to exclude SSD as System
  • Removed all my system from case, cleaned, reassemblied
  • Installed Windows on SSD completely new
  • BIOS Reset and tried to optimize, reset again
  • No Overclocking @any time
  • Watched Temperatures - all good for CPU, GPU, Memory, Disks, Case
I don`t know what to do anymore. I uploaded my Windows Dump Files here. I am not a professional in analysing these things. The DLLs listed last were all connected to system run in general and did not point to any hardware failure as far as i know.

Maybe you can read more out of it or have any other suggestions? IMHO only Board, CPU (even if test passed) and power supply are remaining as an error source IMHO.

Appreciate your help.

https://drive.google.com/drive/folders/1WR1KRizGxzQ8rsc9GNSY4VQvzij4DClY?usp=sharing

THX Jens

___
Edit for people als experiencing this WHEA problem - it is solved now: in my case the CPU was broken even if Intel Test Tool reported PASS in every test, temperatures were OK. (Maybe not your personal 100% solution if you find this thread with search, but consider it to be an option.)
 
Last edited:

Colif

Win 11 Master
Moderator
i can't read dumps but I will get @gardenman to convert them for me and I will see what they show

remove any overclocks
remove any overclocking software - so MSI afterburner

Do you still get bsod with gpu not attached? since you tested it like that?

Any extra PCI devices attached? What USB devices?

WhEA errors can be any hardware, and sometimes drivers.
 
Apr 17, 2019
7
0
10
remove any overclocks
remove any overclocking software - so MSI afterburner

-> No overclocking at any time, no overclocking software, BIOS is reset and tried several tweaks, reset again, new heatsink on CPU

Do you still get bsod with gpu not attached? since you tested it like that?

->Yes I removed dedicated graphics card and used onboard - crashes too

Any extra PCI devices attached? What USB devices?

->Only PCI device was GPU, was removed, M2 SATA, USB only Keyboard and mouse, LAN @network slot

WhEA errors can be any hardware, and sometimes drivers.

-> Tried to update all to latest and also older revisions to be sure latest are not making these problems, Clean Windows Installation
 

Colif

Win 11 Master
Moderator
motherboard and PSU are two hardest things to test, hence normally check everything else 1st

Only real way to confirm it is either is with spares.. there is PSU testing equipment but most people don't have it.

You seem to have done everything I would suggest hardware wise. I will see if anyone else has any smart ideas

Could run Prime95 to double check CPU but it is rarely the CPU to blame here.
 

gardenman

Splendid
Moderator
The forum decided not to notify me of this thread for some reason. I looked in Alerts / Show All also and it's not listed. Oh well, I stumbled into it anyway.

I ran the dump files through the debugger and got the following information: https://pste.eu/p/pvlS.html
File information:041719-4234-01.dmp (Apr 16 2019 - 14:57:29)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Driver warnings:*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Probably caused by:? (Process: ?)
Uptime:0 Day(s), 0 Hour(s), 18 Min(s), and 29 Sec(s)

File information:041719-3984-01.dmp (Apr 17 2019 - 11:34:16)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Driver warnings:*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Probably caused by:? (Process: ?)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 45 Sec(s)

File information:041719-3968-01.dmp (Apr 17 2019 - 11:51:05)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 23 Sec(s)

File information:041719-3953-01.dmp (Apr 17 2019 - 11:32:06)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: BlueScreenView.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 06 Sec(s)

File information:041719-3921-01.dmp (Apr 17 2019 - 11:28:34)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: MicrosoftEdgeCP.exe)
Uptime:0 Day(s), 0 Hour(s), 40 Min(s), and 14 Sec(s)
Possible Motherboard page: https://www.msi.com/Motherboard/Z270M-MORTAR.html
It appears you have the latest BIOS already installed (v1.6).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
  • Like
Reactions: Trashing

Colif

Win 11 Master
Moderator
is your ram on this list?

https://www.msi.com/Motherboard/support/B250M-MORTAR#support-mem-5

bios isn't showing what ram is installed so I cannot check if the codes are listed or not. Just curious if its a voltage thing, but that isn't a strong point of mine.

otherwise I would contact MSI and see what they suggest, as it looks like its either motherboard or PSU at this point.
 
  • Like
Reactions: Trashing
Apr 17, 2019
7
0
10
THX for the additional hints! So RAM seems to fit in list. Also would have wondered, because it was runnung 100% stable for more than a year.

I wanted to buy a new mainboard today, but all stores were closed or had none fitting.

Maybe I can lend a Power Supply somewhere in the neighbourhood... Update: just used another PSU and crashes again.

I will report later whenever I have progress. But sunday and holidays in monday will delay it for sure. These things always seem to happen when it is hard to replace.
 
Last edited:

Colif

Win 11 Master
Moderator
New Mainboard arrived, I built it up and.... Same Crash F%$&^*%$@#

I am sorry that didn't fix it...

DId you ever run prime95 on CPU?

Have you tried to breadboard it? only have absolute minimum attached, 1 stick of ram, 1 ssd, no GPU,

its not motherboard (or unlikely after getting a new one)
Its not PSU (since you swapped in another and same thing happens)
Its not ram
errors happen with/without gpu
If prime 95 works, its unlikely CPU

what is left?

I will ask for help as I am clearly missing something.
 
Apr 17, 2019
7
0
10
Just downsized the system:
New Mainboard
Attached to PSU
CPU
1 RAM module (switched different modules)
SSD or Win on Stick
Keyboard and Mouse USB
Start with screwdriver

Result crash and crash and crash...

Did intel CPU test, no prime tests because most times crashes before able to do so right now.

Still RAM no special profiles and no overclocking. God damn...
 
Apr 17, 2019
7
0
10
Hey guys, first I want to thank you for all of your help, suggestions and problem solvers.

After everything failed, I now ordered a cheap i5 to replace my old i7 temporarily (die not want to buy an overpriced 7th genration CPU - now waiting for Zen 2 and Intel reaction to replace board and CPU) and it finally seems to work! I am posting right now from this system and it is runnig stable now for ~45min. This is 45min more than it did before lately.

So even if it seemed to be unlikely after testing it with intel CPU Tool and passing, temperatures were OK, something inside the CPU was "damaged" somehow. So it still was working, but not properly as it should. There was no optical hint, the old CPU still looks like day 1.

So problem solved - CPU running but dead for use!

Thank you once more.
Cheers Jens
 

TRENDING THREADS