Latest BSOD alerts - unrecoverable error detected
Latest BSOD alerts - unrecoverable error detected
xXWinterXx
01-01-2025, 11:39 AM #12cpu, i haven't looked at the gpu in a while, but from what i recall it stays fairly cool. I've never seen it go above 70 degrees even during a 3dmark stress test.
WHA indicates a problem with the CPU or a PCIe component. A WHEA BSOD without dump files points to an NVMe SSD as the likely culprit. When a crash occurs due to storage issues, the drive is typically disabled so it can't store data. Several factors can prevent dump file generation, such as insufficient space on the drive with the page file, or a page file size that's set too low if you've manually configured it. Encrypted drives can't be accessed during the dump process since the dump happens outside Windows. We have two options to address this: you can pursue both simultaneously. On the BSOD screen, data is written to the page file and a dump file forms afterward during the next startup. If you have multiple drives, relocating the page file to another drive might enable it to dump data and trigger the creation of dump files. NB: Avoid using external storage for the page file—these devices often shut down abruptly, causing immediate system failure. The alternative is adjusting a registry setting to display more details on the BSOD screen. If the screen remains unresponsive (you can't generate dumps), skip this step; however, if it restarts normally after a short time, proceed to the guide and uncheck the automatic restart option. To manually restart, simply press the power button. To modify the BSOD output for extra information, add a registry field under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, name it "DisplayParameters", set its value to 1 (hex or decimal), and save. Reboot to apply changes. Afterward, the next BSOD should show these additional details in the top-left corner. If Arg1 equals 0x0000000000000010, Windows attributes the issue to the NVMe SSD. Keep in mind this method works only for WHEA BSODs.
MallisTheGreat
01-01-2025, 11:39 AM #15Alright, so the first thing, have done that according to the guide, just waiting for the next bsod second bit, about that, previously when it crashed, the bsod screen was only on my screen for a half second before my computer immediately restarted, so I had to go into control panel and somewhere to disable the automatic restart after a bsod, so that's why I have to manually restart my pc (reset button on my case has finally come in handy for once), so I'll just assume that doesn't apply to my situation here...? 3rd bit, follow that, probably the most simple regedit thing I've had to change, also waiting on the next bsod for that to tell me what it is exactly as for the bsod, somehow, idk how, but I launched ETS2 a few minutes ago and when I loaded into the game my computer somehow didn't bsod, every single time I tried to load into the game for the past 30 ish hours my computer bluescreened, and now after the regedit thing (I also installed samsung's ssd utility tool off of TechPowerUp and ran that a few times, it says no issues but I haven't tried the long-term tests yet since, well, I don't have the time for that right now), and blahblahblahblahblah basically saying, this is a little update for what I've done/followed, now just waiting for when my computer decides to bsod again, and then I'll post whatever I find here. WELL, WELL, WELL. I was in the middle of editing this post when my computer decided to bsod once again (with ets2 open on my other monitor) details in a new post because this one's long enough already Edited July 11, 2024 by SergNMerp added a missed word, rewrote a thing, and new fun fact
B4nBreaker
01-01-2025, 11:39 AM #16Right, so the BSOD information at the start looks pretty much what you mentioned—exactly the 0x000...010 page file or dump file issue. The error in Event Viewer says "Dump file creation failed due to error during dump creation," event ID 161, and it points to Device\HarddiskVolume3 with a long string of numbers. I see a 2TB Seagate BarraCuda drive for general storage and backups, plus a backup drive I used after reinstalling Windows. There was a problem earlier in June 2021 when the drive wouldn’t boot and BIOS reported it as empty (about 1.81 TB free). I took it to a micro center for testing; if it worked, I’d replace the board. Instead, I swapped to a new motherboard—probably an ASRock B450 Pro4 to a Gigabyte Aorus B550 Elite V2. The issue seemed fixed then, but later I noticed the Pro4 board was fine. Eventually, I sold it on eBay. In November 2022, the drive again slowed down, so I bought a new 980 Pro. The C:/ drive was still slow even after reinstalling Windows, which led me to suspect a failure. Since the 980 Pro was on sale during Black Friday, I replaced it. Right now, it still works for everyday storage, though I’m not sure why a non-C:/ drive would cause BSOD. Maybe HarddiskVolume3 is just a generic term, but I’m keeping it safe—temporarily I’ll disconnect it while moving some data.
ForeverAthena
01-01-2025, 11:39 AM #17Microsoft recently included SATA drives in WHEA events within Event Viewer. I haven’t noticed a WHEA BSOD yet. Let’s review any WHEA events you have and see what they report. Open Event Viewer, navigate to Windows Logs → System, and choose "Filter Current Log" on the right. In the Event Sources dropdown, pick "WHEA-logger". If you see any WHEA events, highlight them, right-click and save. Please share the file here.
hmmm, alright even more suspicious of the HDD because, well, to my understanding, vol3 would be equivalent to what I see in file explorer; of which I had 3 different volumes, first one would be C:/, 2nd would be some random system reserved space I'm not sure how it got there, don't wanna delete it, and then the 3rd volume listed would be the HDD since the last bsod I unplugged the drive and now there's just one volume listed in file explorer, C:/ anyways, here's that event viewer log file thing you wanted, I selected all of em, as far as I can tell it's all of the bsods ive had since I reinstalled windows (the 2 TLD bsods, the 5 ETS2 bsods from yesterday, and then 2 more from earlier today (currently 4:43 am) all whea bsods since windows reinstall.evtx
I'm sure 'harddiskvol3' is the hard drive. I checked DiskPart and saw three volumes on the boot drive, with the third being the HDD. I plan to try some games on it to check if I get another BSD or not, since the C drive only shows 511 MB free. DiskPart has been showing this space issue for a while now. I don't really care about the numbers, my SSD is not more than half full right now—no one knows why DiskPart displays it. When I was installing a Linux ISO on a thumb drive, I used DiskPart to convert the file system and then formatted it with the right-click menu. Updated July 11, 2024 by SergNMerp added more details about the low space shown.
MilckyDreams_
01-01-2025, 11:39 AM #20WELL yeah it bsoded again, playing gta, with the hdd disconnected same info as before with the other bsods, same \Device\HarddiskVolume3 from volmgr even though there is no 3rd volume, unless it's counting volume 2 as volume 3, 0=1, 1=2, 2=3 kinda thing yeaaaaaa time to run samsung's long term ssd test while I sleep ig and maybe try to contact em idk, they say there's a 5 year warranty for the thing and I've had it for almost 2 years, black friday 2022 is when I bought it from micro center idk I'll wait for ya'lls response about it all before I go contacting samsung ig whea bsod without extra hdd connected.evtx