PC crashing daily

Question

PC crashing daily

Aaron 20

Hello,

my PC has been crashing daily and its making it super annoying to use.

I have the minidump files here: https://1drv.ms/u/c/cbe42d931af4b952/IQCOzUSfo1B2T6Wtby8xan7YAT-fioclF7T8hdVestDM9ew?e=iAmvSg

GPU MSI RTX 2070 Super

RAM 2x8GB Crucial
MB B450 Tomahawk

Thanks for the help in advance

0 comments

2 answers

Your answer

Answer 1

David-M 127.7K Independent Advisor

Hi. I'm David, and I'm happy to help you.

I analyzed the minidumps you shared. The minidumps do not mention any drivers, only a generic system file.

To be able to proceed, I need some information about your system. I usually get this information from minidumps, but yours does not contain it.

Please share a screenshot of your system information.

(You've already provided some of your PC's specifications. However, some details were not covered.)

Press "Windows + R", type msinfo32 and press Enter.

Maximize the window and use the shortcut "Windows + Shift + S" to use the screenshot tool.

Looking forward to your reply.

Aaron 20 Reputation points

2026-10-08T16:54:17.3333333+00:00

@David-M
David-M 127.7K Reputation points Independent Advisor

2026-10-08T17:17:45.25+00:00

Thanks for the screenshot.

I suggest doing the following:

Go to the MSI website using the link below, download the latest Chipset driver, and install it.

https://www.msi.com/Motherboard/B450-TOMAHAWK/support#driver

Driver name: AMD Chipset Driver

Version: 8.03.25.247

(Extract the ZIP file, run the file AMD_Chipset_Software, and follow the on-screen instructions to install the driver.)

Then, restart (not shutdown) your PC and see if the system works stably.

If the crash occurs again after doing this, please share the minidump it created.

Feel free to ask any questions you may have.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
Aaron 20 Reputation points

2026-10-08T18:32:38.5066667+00:00

@David-M I have the suggested chipset drivers already installed. And my PC just crashed twice within 2 minutes. I have been seeing this BSOD message "attempted_write_to_readonly_memory" several times now.

Here are the most recent dumpfiles: https://1drv.ms/u/c/cbe42d931af4b952/IQAzlbDKQQIBTrwF0vaY4d6uAV-3ssZ29LcF5IfxJA9Aan8?e=UhAFAK
David-M 127.7K Reputation points Independent Advisor

2026-10-08T18:43:10.6466667+00:00

Thanks for the update.

These minidumps don't mention drivers either, only a generic system file.

In this case, I suggest doing the following:

Go to the motherboard BIOS and check if you have configured any XMP / A-XMP (RAM overclock) profile. Disable it, and leave it as default.

Then, start Windows normally and see if the system runs stably.

If the crash occurs again after doing this, please share the minidump it created.

Feel free to ask any questions you may have.
Aaron 20 Reputation points

2026-10-08T18:56:57.32+00:00

@David-M Thanks for the help, but I checked that too and it was already disabled.
David-M 127.7K Reputation points Independent Advisor

2026-10-08T19:08:54.8533333+00:00
Thanks for the update.

In this case, I have 2 suspicions about the cause of this problem.

Severe corruption of Windows.

A hardware problem.

It is possible to test some hardware components using software, but unfortunately, not all of them.

Before running any tests, make sure your two RAM sticks are physically installed in the correct slots on your motherboard. For your B450 Tomahawk, two modules must be installed in slots 2 and 4 (A2 and B2), counting from left to right. Running them in slots 1 and 3 can cause memory controller instability and blue/black screens, even with XMP disabled.

Next, I suggest you use the free MemTest86 tool for a deep check of your RAM.

https://www.memtest86.com/download.htm

The deep scan can take a long time, depending on how much RAM you have. So do it at a time that suits you.

Feel free to share a photo of the test result.

Also, check the health of your HD/SSD using Crystal Disk Info.

https://crystalmark.info/en/download/#CrystalDiskInfo

(On this same page, there is the download of another app. The "Crystal Mark". Do not download Crystal Mark. Download only the "Crystal Disk Info".)

Download the "Standard Edition" by clicking on the "ZIP" button.

Extract the ZIP and run the file "DiskInfo64.exe".

The health result of your HD/SSD will be displayed. See if there are any alerts.

Feel free to share a screenshot if you want. Use the shortcut "Windows + Shift + S" to use the screenshot tool.

Feel free to ask any questions you may have.

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
Aaron 20 Reputation points

2026-10-08T19:40:35.0933333+00:00

@David-M and the PC just crashed again. I found this in the event history: cldflt.sys and here is the minidump: https://1drv.ms/u/c/cbe42d931af4b952/IQCzhGBxyYk2R7oIR67EMDvxAd0_AfMhACllox7AHjG0TYQ?e=gkEwt2
Aaron 20 Reputation points

2026-10-08T19:46:03.97+00:00
David-M 127.7K Reputation points Independent Advisor

2026-10-08T19:53:20.1033333+00:00

Thanks for the update.

In this minidump, cldflt.sys (Windows Cloud Files Filter Driver) is mentioned, but the exception code is 0xC0000005 (Access Violation). This means the system tried to read an invalid memory address while the Search Indexer was running.

Having three different bug check codes across three different processes confirms that cldflt.sys is not the cause of the issue, but rather another victim of memory data corruption.

Crystal Disk Info did not detect any problems with your drives.

Please proceed with the other steps outlined in my previous reply. Verify the RAM slots, and run MemTest86.

Feel free to ask any questions you may have.
Aaron 20 Reputation points

2026-10-09T11:21:52.7733333+00:00

@David-M Hi David, I left memtest running and it didnt detect any errors. And I reinstalled windows a couple of months ago.
David-M 127.7K Reputation points Independent Advisor

2026-10-09T12:08:31.5633333+00:00
Thanks for the update.

Were you able to confirm whether your two RAM sticks are installed in slots 2 and 4 (A2 and B2)? Even though the RAM modules passed the MemTest86 test, this could still be a factor.

Also, try adjusting a CPU power setting in your BIOS. Your first minidump crashed while the processor was entering a low-power idle state.

(I put these steps together based on what I found online. However, some options might differ slightly on your motherboard. Please let me know if you come across any discrepancies.)

Restart your PC and press "Del" to enter BIOS;

Press "F7" to enter "Advanced Mode", then go to "OC" (or "Overclocking") > "CPU Features";

Locate "Power Supply Idle Control" and change it from "Auto" to "Typical Current Idle";

Press "F10" to save and exit.

Please let me know how it goes.

Feel free to ask any questions you may have.
Aaron 20 Reputation points

2026-10-09T12:31:01.04+00:00

@David-M Thanks for the help.
Yes, the RAM sticks are in the correct placement for dual channel.
I changed the settings now to Typical Current Idle.
I'll test it out today and let you know if I crash again.
David-M 127.7K Reputation points Independent Advisor

2026-10-09T12:56:34.99+00:00

Thanks for the clarification.

If you have any questions, don't hesitate to ask.
Aaron 20 Reputation points

2026-10-09T17:18:04.7066667+00:00

@David-M sadly it crashed again.
minidump: https://1drv.ms/u/c/2c0d7294ec101b5a/IQD6bxo-C27tTrchAmAcUQBSAYiqQnIqsqyfwL63ZjzF5BI?e=g9qppQ
David-M 127.7K Reputation points Independent Advisor

2026-10-09T18:08:21.1466667+00:00
Thanks for the update.

In this case, try resetting the BIOS settings to default.

Restart your PC and press "Del" to enter the BIOS;

Press "F6" (or look for the option) to "Load Optimized Defaults";

Save and exit by pressing F10.

Also, check your CPU temperature. Several tools allow you to monitor the temperature of your CPU. I recommend the free version of HWMonitor.

https://www.cpuid.com/softwares/hwmonitor.html

With temperatures slightly above 95°C, you can start to have problems.

The CPU temperature only increases when used. So do something on your PC so that your CPU is used to the point that its temperature increases.

Just open HWMonitor for the information to be displayed. There is no need to set anything.

Please let me know how it goes.

Feel free to ask any questions you may have.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
Aaron 20 Reputation points

2026-10-09T18:47:22.1833333+00:00

@David-M someone on reddit told me that the minidump contains Kernel security check failure caused by League of legends's Riot vanguard.
What do you think?
David-M 127.7K Reputation points Independent Advisor

2026-10-09T19:01:34.5833333+00:00
In the last minidump you shared, the "LeagueClientUx" process is indeed mentioned, but I don't see any mention of Riot Vanguard.

Out of all 7 minidumps provided so far, only 2 mention "LeagueClientUx", while the remaining 5 crashed under completely unrelated Windows processes (such as System, svchost.exe, msedge.exe and SearchIndexer.exe). If all the minidumps had pointed to the same process, then I would have suspected it right away.

In the minidump, PROCESS_NAME indicates which application was actively running when the Windows kernel detected a corrupted memory block. When crashes occur across multiple completely different processes, it confirms a systemic/hardware memory corruption issue rather than a bug caused by a single application or anti-cheat driver.

At this point, I think it's a good idea to proceed with what I suggested in the previous reply.

Have you tried loading BIOS "Optimized Defaults" yet?

Were you able to check CPU temperatures under load with HWMonitor?

Please let me know how it goes.

Feel free to ask any questions you may have.

Answer 2

To troubleshoot daily crashes, first make sure Windows is saving usable dump files, then inspect them with WinDbg.

Configure memory dump collection:
- Open Advanced system settings.
- On the Advanced tab, under Startup and Recovery, select Settings.
- Under Write debugging information, select Automatic memory dump.
- Select OK, then restart the PC.
- Dump files are typically saved in:
  - %SystemRoot%\MEMORY.DMP for automatic, kernel, complete, and active dumps
  - %SystemRoot%\Minidump for small memory dumps
Verify the dump files exist after the next crash:
- Small memory dumps are stored in %SystemRoot%\Minidump.
- A small memory dump contains the stop message, parameters, loaded drivers, processor context, process and thread information, and the kernel-mode call stack.
Analyze the dump with WinDbg:
- Copy the dump file to another PC if needed.
- Download the Windows 10 SDK.
- During setup, choose Debugging Tools for Windows.
- Open WinDbg.
- Go to File > Symbol File Path.
- If internet access is available, set the symbol path to: https://msdl.microsoft.com/download/symbols
- Select Open Crash Dump and open the .dmp file.
If the crashes continue and only small dumps are being created, keep them all:
- Windows stores multiple small dump files with distinct date-based names in %SystemRoot%\Minidump.
- This helps compare repeated crashes over time.
If a dump file appears unreadable or analysis fails:
- Use DumpChk to verify the dump file is valid and not corrupted.
For general isolation steps while collecting dumps:
- Consider a clean boot to rule out background software.
- Consider rolling back a device driver if crashes started after a driver change.
- A problematic driver can also be temporarily disabled in some cases.

The most useful next step is to open one of the minidumps in WinDbg and identify whether the crash points to a driver, memory corruption, or another component.