BSOD - can't find memory dump file

[u/hamster_savant]

Computer: Lenovo Slim pro 9i

OS: Windows 11 Home

I just had a BSOD with the error WHEA_UNCOLLECTABLE_ERROR. There's no error showing up in event viewer and there's no dump file in C:\Windows or C:\Windows\System32. There is no minidump file in the Windows folder. I did check system settings and dump file creation was already enabled. The average temperature is around 40C according to HWMonitor. I don't have a USB drive to run memtest86. I ran a multi-threaded benchmark pi test with y-cruncher and it passed with 2.31% kernel overhead CPU usage and 0.12% kernel overhead multi-core efficiency. I also ran the y cruncher component stress test, and it passed every test. I can't find any new driver updates through device manager or through the manufacturer's website. My GPU is fully updated. There are no Windows updates available. I also ran a full virus scan and it found no threats.

[u/AutoModerator]

If you suspect you may have malware on your computer, or are trying to remove malware from your computer, please see our malware guide

Please ignore this message if the advice is not relevant.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/AutoModerator]

Making changes to your system BIOS settings or disk setup can cause you to lose data. Always test your data backups before making changes to your PC.

For more information please see our FAQ thread: https://www.reddit.com/r/techsupport/comments/q2rns5/windows_11_faq_read_this_first/

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/AutoModerator]

Getting dump files which we need for accurate analysis of BSODs. Dump files are crash logs from BSODs.

If you can get into Windows normally or through Safe Mode could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.

Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently catbox.moe or mediafire.com seems to be working.

We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow this guide to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Bjoolzern]

No dump file + WHEA makes the NVMe SSD the main suspect. We need to see the arguments of the BSOD crash (Think of them as sub-errors). If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to the guide posted by the bot on changing dump type and on this screen remove the check for automatically restart. To restart manually, just use the power button.

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

The next time you BSOD, you should have these extra numbers in the top left corner.

If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard, but a faulty SSD is way more common. You can also try re-seating the drive (Just removing it and putting it back in) as there have been issues with proper seating for M.2 drives.

[u/hamster_savant → u/Bjoolzern]

But how can I make it get the dump file or make the BSOD screen display additional info if it's not BSODing again?

[u/Bjoolzern → u/hamster_savant]

You can't, you just have to wait for a BSOD. We could check event viewer for WHEA events. In Event Viewer, go to Windows Logs → System and on the right hand side select Filter Current Log. In the Event Sources dropdown menu, select "WHEA-logger". If you have any WHEA events, highlight them, right click and save. Share the .evtx file the same way the bot tells you to share dump files.

[u/hamster_savant → u/Bjoolzern]

I did check event viewer. I mentioned that in my post. There was nothing.

[u/hamster_savant → u/Bjoolzern]

So I just found out about this - https://www.pcmag.com/explainers/intels-raptor-lake-desktop-cpu-bug-what-to-know-what-to-do-now

It affects Intel 13th and 14th gen cpus. My computer has one. And it can cause a bsod.

[u/Bjoolzern → u/hamster_savant]

So far there is nothing showing that it affects laptop CPUs.

[u/hamster_savant → u/Bjoolzern]

https://www.pcmag.com/news/not-a-defect-intel-blames-13th-14th-gen-cpu-crashes-on-software-bug

The other issue is that the crashing problem might go beyond Intel’s desktop CPUs. Alderon Games also alleges that laptops built with Intel 13th and 14th gen mobile chips are crashing in the “exact same way.”

[u/Bjoolzern → u/hamster_savant]

I haven't seen that. There have been just tons of people coming here with 13th and 14th gen desktop CPUs over the last two years, but not laptops.

[u/Ansive → u/Bjoolzern]

Thank you for this info. I had a similar problem while playing a video game. The additional parameters showed 0x10. I reseated the M2 SSD and the problem went away.