no its not a clean install and no oc.Did you clean install after the upgrades? Unlikely cause of WHEA but you never know, if its got all old drivers on it, its always possible.
can you go to c:/windows/minidump and copy the minidump files to another folder
upload the copies from the new folder to a file sharing website and show link here? (this stops need for step 1 of the link in PC Tailors sig)
are you overclocked as that can cause WHEA errors.
not something i want to do is there a way to sort it outI would try a clean install as when you swap CPU & Motherboard there are enough changes to warrant a new start.
dumps might include drivers for old hardware, not new.
You might get better performance out of it too
windows is still activated how do i read dump filesSee what PC finds in the dump files, you might be lucky.
swapping 10 onto new mobo/cpu likely cause it to be deactivated once the activation servers check hardware. MIght not happen right away.
whats pc tailorI would wait for PC tailor to convert them.
You can use the https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/ otherwise
the other person who replied to you in this threadwh
whats pc tailor
WHEA_UNCORRECTABLE_ERROR
"A WHEA ERROR is almost solely hardware based. It is possible in rare circumstances for this to be a driver, however it is very unlikely. It is often caused by:
- Component overheating
- Unstable overclocking or XMP profile
- Faulty hardware"
sorry for the late replyI have run the dump file(s) and you can see the full report(s) here:
https://pste.eu/p/p5Iz.html - WHEA_UNCORRECTABLE_ERROR
https://pste.eu/p/x1CK.html - WHEA_UNCORRECTABLE_ERROR
https://pste.eu/p/32Lz.html - WHEA_UNCORRECTABLE_ERROR
https://pste.eu/p/vThB.html - WHEA_UNCORRECTABLE_ERROR
Summary of findings:
Some things to consider:
- Nothing obvious at this point pulling from the dump files, and they are all WHEA 124 errors.
However I would go back to my original queries:
What is your full system spec including PSU make and model.
Some outdated BIOS issues can cause WHEA issues, but not too often. What is your BIOS version?
Are your RAM modules from the same physical pack?
As Colif has stated, you may need to clean install windows too - and unfortunately as much as you may not want to, there is a reason why clean installation is recommended after major hardware change, because Windows isn't as interchangeable as many believe it is. Would I expect it to cause WHEA? Not necessarily, but it could.
Despite that, if it has only occurred since changing CPU and MB, I would typically lean towards CPU being the problem. Even bent / damaged / contaminated pins can cause all manner of havoc.
yeah i ran the tool passedWHEA errors that survive resets aren't likely software
is ram on motherboard listing?
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Did you run Intel processor diagnostic tool as the memory controller is on the CPU and it was one of your 2 new items.
m.2 is samsungJust wondering if checking the pins on motherboard would show anything (under CPU)
WHEA errors can be any hardware, makes it a case of looking at all hardware and testing it. Its possible moving a part onto new motherboard damaged it
You run Intel tool
Try running Prime95 - it also tests ram - https://www.mersenne.org/download/
You run Memtest
what brand is m.2?= and hdd?
HD Sentinel is a general hdd test - https://www.hdsentinel.com/hard_disk_sentinel_trial.php - open disk tab and run any tests you can
only real tests for psu are:
the paper clip method - https://forums.tomshardware.com/threads/what-is-the-paperclip-method-of-testing-a-psu.1336402/
or multimeter,
or in the BIOS to check the +3.3V, +5V, and +12V. - https://www.lifewire.com/power-supply-voltage-tolerances-2624583
there are no tests for motherboard. Just a process of elimination. You check everything else first. If it gets to stage its either PSU or motherboard, I would get PC checked out by a repair store as they might be able to narrow it down further than a guess.
ok its been around 5 days since i have had a bsod but i am still getting frezzed of around 2 to 5 secs could this be caused by a faulty cpu or board