Random Blue screen..

[76561198814108747]

Soo I built my PC a year ago... and never had any issues with it... but just a minute ago I got a blue screen and the error code was "WHEA_UNCORRECTABLE_ERROR" Restarted my system.. and it's running fine. I've changed nothing in my PC recently... no new programs... my CPU is sitting at around 30 - 38 celsius.. GPU is at 30 celsius... no idea... lol but it's been running fine just wondering if anyone knows what could've caused that crash.

[Carlsberg]

hardware error, file corruption, heat, driver conflict or psu voltage, if it happens again i guess you got some troubleshooting to do, start with event logs. I am sure the more knowledgeable here will chime in and assist.

[76561198814108747]

Originally posted by Carlsberg:

hardware error, file corruption, heat, driver conflict or psu voltage, if it happens again i guess you got some troubleshooting to do, start with event logs. I am sure the more knowledgeable here will chime in and assist.

Yeah, I figure it might be because I haven't dusted my PC in 6 months lol and its pretty dusty so and maybe something is loose... so tomorrow I'm gonna grab a can of air duster and take it apart and give it a good cleaning. but I also ran CHKDSK and it showed 0 errors.. and also tried to open windows minidump logs but wouldn't let me.. but idk.. I also have a bad habit of leaving my PC running 24/7 so maybe that's why idk

[chiefputsilao✖️ping]

if those are idle temperatures and at load near those temps, then overheating is not the culprit.

[_I_]

alt+tab takes long enough for temps to drop 20+c
use hwmonitor to log min/max temps

and specs are useful

post a cpuz validation link
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here

[Bad 💀 Motha]

That's why I got a handheld 120V air blower because it will save money in the long run and desktops/laptops will always require blowing the dust out every few months.

[76561198814108747]

Originally posted by Bad 💀 Motha:

That's why I got a handheld 120V air blower because it will save money in the long run and desktops/laptops will always require blowing the dust out every few months.

Damn true... good idea.. I've got a shop vac I could use lmao didn't even think about it

[Bad 💀 Motha]

Vacuums don't do much though, but most should be reversable. Just be sure that if you configure a shop vac for blowing outward that the inner can is clean before hand. Also they are very strong so be careful with your case/cpu/gpu fans. Blowing at a distance so as not to put too much force on fan blades, to avoid breaking them. Then just be prepared to vacuum up the mess afterwards

[plat]

I had WHEA Logger corrected errors and so I can give some info to try if it's Intel. Open the Event Viewer app, click on Windows Logs on right side, wait a bit, ,then System. Scroll until you find a yellow triangle warning in the log list and double click on it, check if the text says WHEA..... Now click the Details tab. Somewhat down the page, you'll see a Vendor ID. If it's.8086, that's Intel. Now the device id could be anything so to find the offending component, keep the Event Viewer WHEA log open and open Control Panel, then open Device Manager. Click the "down" arrow by System devices to expand the list. Then highlight the device that was listed in the event log by clicking once on it. For example, my device was A118. Click "View" at the top of the Device Manager page and tick "Devices by connection." Now there should be a little "down" arrow by the highlighted system device that will tell you what component is at fault. So, in my case, A118 corresponded to the PCIExpress root port 9, the nvm-e slot. I updated the Samsung firmware and the warning was gone. If this seems confusing, it is. That's Windows for you.

[Bad 💀 Motha]

But logs may often point to hardware as an issue when it's the connected driver that failed.

[plat]

That's quite true, for drivers. Sometimes one has to update the chipset, maybe you forgot or something. This is usually the case behind corrected warnings. Not to be mean or anything but an uncorrected error is usually more serious. When I had uncorrected WHEA Loggers (just once) my motherboard died the next day. Not trying to be dramatic, just stating the facts.

[76561198814108747]

Here are the errors I see at around the time it happened...

"WARNING: The driver \Driver\WudfRd failed to load for the device HID\VID_B58E&PID_9E84&MI_03&Col02\7&1344f0d8&0&0001."

"ERROR: The previous system shutdown at 8:11:06 PM on ‎1/‎26/‎2020 was unexpected."

"ERROR The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffb20ff7781028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\WINDOWS\Minidump\012620-8468-01.dmp. Report Id: fc1eabd1-adb4-4d39-a944-12440c5a698a."

"Error: Dump file creation failed due to error during dump creation."

"CRITICAL: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

[Bad 💀 Motha]

Most folks seem to only grab gpu driver and never install all the rest.

[76561198814108747]

A friend told me the crash was caused by memory corruption-probably by an unnamed driver.

Anndd it's probably my mouse lol.. I have a wireless razer mamba, and I've had problems with razer synapse 3 forever... yestersay i went to charge it, but everytime synapse 3 wouldnt recognize the device and crash.. I have to unplug the wireless receiver and plug it back in multiple times before synapse will recognize it. I've always had nothing but trouble from synapse 3.. pos software man... but idk if that's the problem.. I've ran multiple health checks, update drivers, etc and found a couple errors but it corrected them so... idk maybe it's fine now... no problems since yesterday

[plat]

Well, that's "good." Maybe you can still check Device Manager under "Mice and other pointing devices" if there's some sort of warning there. Like I said, an Uncorrected Warning is definitely something to be concerned about, and it seemed you really investigated it thoroughly.