Blue Screen of Death - WHEA_UNCORRECTABLE_ERROR

[ubuysa]

You have COMODO Internet Security and Malwarebytes Internet Security both installed. Malwarebytes is fairly tolerant of other security systems, but COMODO isn't. In addition, COMODO hasn't been updated for several years now. I used to run it myself and uninstalled it 18 months ago due to the complete lack of support.

I suggest you uninstall COMODO using their specialised tool here.

I also strongly suggest uninstalling Malwarebytes too, you really don't need either of those security products in any case.

It would be unusual for a security product conflict to cause a 0x124 BSOD, but it's not impossible. In any case you MUST uninstall one of them, and preferably both, because that's a known BSOD cause right there.

Regarding not writing dumps, bad RAM is a known reason for dump failure, so if uninstalling COMODO and Malwarebytes doesn't stop the BSODs (TBH I don't think it will, but you should still uninstall both) then we'll need to suspect RAM. Memtest is good, but no memory tester is 100% accurate, so if it's still BSODing after uninstalling COMODO and Malwarebytes, remove one stick of RAM and run with just one for a few days. Then swap sticks and run on just the other for a few days.

BTW. How full is your system drive? There needs to be enough free space for Windows to extend the pagefile to contain the dump.

 

[films&games]

Yes, it won't work from Windows, you have to use external media

I ran Startup-Repair, the computer restarted and displayed the generic message ”Startup-Repair couldn't repair your PC”

I noticed the log file was listed as being saved in D:\Windows\System32\Logfiles\Srt\SrtTrail.txt.

My system drive is C not D.

See screenshot: Startup_Repair.


Any advice or suggestions would be appreciated, please.

Thank you.

 

[SpyderTracks]

I ran Startup-Repair, the computer restarted and displayed the generic message ”Startup-Repair couldn't repair your PC”

I noticed the log file was listed as being saved in D:\Windows\System32\Logfiles\Srt\SrtTrail.txt.

My system drive is C not D.

See screenshot: Startup_Repair.


Any advice or suggestions would be appreciated, please.

Thank you.

Are you booting from external media?

 

[ubuysa]

Can you use File Explorer to display the root of both your C and D drives please?

And please confirm that you've uninstalled both COMODO and Malwarebytes.

 

[films&games]

You have COMODO Internet Security and Malwarebytes Internet Security both installed. Malwarebytes is fairly tolerant of other security systems, but COMODO isn't. In addition, COMODO hasn't been updated for several years now. I used to run it myself and uninstalled it 18 months ago due to the complete lack of support.

I suggest you uninstall COMODO using their specialised tool here.

I also strongly suggest uninstalling Malwarebytes too, you really don't need either of those security products in any case.

It would be unusual for a security product conflict to cause a 0x124 BSOD, but it's not impossible. In any case you MUST uninstall one of them, and preferably both, because that's a known BSOD cause right there.

Regarding not writing dumps, bad RAM is a known reason for dump failure, so if uninstalling COMODO and Malwarebytes doesn't stop the BSODs (TBH I don't think it will, but you should still uninstall both) then we'll need to suspect RAM. Memtest is good, but no memory tester is 100% accurate, so if it's still BSODing after uninstalling COMODO and Malwarebytes, remove one stick of RAM and run with just one for a few days. Then swap sticks and run on just the other for a few days.

BTW. How full is your system drive? There needs to be enough free space for Windows to extend the pagefile to contain the dump.

Comodo Internet Security: only the Personal Firewall component is installed.

I was not running the latest version of Malwarebytes Free. Malwarebytes 4.5.30.269 was the version that was installed and every time I checked for updates, it would just update the definitions and not the program itself.

The latest version of Malwarebyes Free using the online installed is 4.5.32.271.

The Corsair Force MP600 m.2 SSD, which is my C drive has over 750GB of free space.

I am only getting the BSOD when running Malwarebytes using a Custom scan with all scanning options “checked” No BSOD occurs when using a normal Malwarebytes scan or in general when using the machine.

The BSOD only happens when Malwarebytes is a few minutes in the “file system” scan.

 

[films&games]

Are you booting from external media?

Yes. I used the USB stick of the latest version of Windows 10 version 22H2, created using the Windows 10 Media Creation Tool to run Startup-Repair by clicking on the “Repair your computer option”.

 

[films&games]

Can you use File Explorer to display the root of both your C and D drives please?

And please confirm that you've uninstalled both COMODO and Malwarebytes.

I have attached screenshots of the root of my System/boot drive C and drive D.

Both Comodo Internet Security and Malwarebytes are uninstalled.

 

[ubuysa]

I ran Startup-Repair, the computer restarted and displayed the generic message ”Startup-Repair couldn't repair your PC”

I noticed the log file was listed as being saved in D:\Windows\System32\Logfiles\Srt\SrtTrail.txt.

Clearly it wasn't, there is no Windows folder on your D: drive.

Please run the sfc /scannow command and then reboot.

You said that the BSOD happened when you ran Malwarebytes. I suspect that COMODO and Malwarebytes were getting in each other's way and that's why you had the BSOD (yes, software can sometimes cause a 0x124 BSOD).

Out of interest, what is in the following folders on your D: drive...

• Clean_Install_Files
• Win10_21H2_Install
• Wind10_22H2_Install

Why do you need to keep these folders?

If you continue to get problems unplug the D: drive and see whether the problems cease. It appears from your log file message above that Windows thinks it's using the D:drive as well.

Should you decide at some point to reinstall Windows (and I'm not yet suggesting that you should) please disconnect the D: drive whilst you do the install.

 

[films&games]

Clearly it wasn't, there is no Windows folder on your D: drive.

Please run the sfc /scannow command and then reboot.

You said that the BSOD happened when you ran Malwarebytes. I suspect that COMODO and Malwarebytes were getting in each other's way and that's why you had the BSOD (yes, software can sometimes cause a 0x124 BSOD).

Out of interest, what is in the following folders on your D: drive...

• Clean_Install_Files
• Win10_21H2_Install
• Wind10_22H2_Install

Why do you need to keep these folders?

If you continue to get problems unplug the D: drive and see whether the problems cease. It appears from your log file message above that Windows thinks it's using the D:drive as well.

Should you decide at some point to reinstall Windows (and I'm not yet suggesting that you should) please disconnect the D: drive whilst you do the install.

I have run sfc /scannow via an elevated command prompt and the following message was displayed, “Windows Resource Protection did not find any integrity violations.”.

The Win10_21H2_Install and Win10_22H2 folders on my D drive contain any new program versions available at the time that I use, e.g. web browsers, office applications.

The Clean_Install_Files contains any files that I might need to copy back to the C drive, e.g. files that I have downloaded but don't need to be stored on my C drive.

I will see how the machine performs over the next few days or so to see if I get any further problems.

When I did clean, install, i.e. Windows 10 22H2 I created a an updated install using the Media Creation Tool, booted from the USB stick and clicked on custom install, deleted all of the partitions on the C drive and installed on the “unallocated space”.

If/when I need to do a clean install of Windows 10 I will look and see if there are any problems with drive D.

Just out of interest I did run Crystal Disk Info and I have attached screenshots of the C and D drives.

 

[ubuysa]

The Win10_21H2_Install and Win10_22H2 folders on my D drive contain any new program versions available at the time that I use, e.g. web browsers, office applications.

I don't understand what you mean? Why not just update to new versions when they are available? Or, do you mean this contains the installation files for apps you have installed?

The Clean_Install_Files contains any files that I might need to copy back to the C drive, e.g. files that I have downloaded but don't need to be stored on my C drive.

Such as? Directly copying files to and from the system drive could be dangerous. You'd be better of moving your Users folders to the D: drive permanently so that the C: drive isn't polluted.

If/when I need to do a clean install of Windows 10 I will look and see if there are any problems with drive D.

I really would suggest disconnecting the D: drive when/if you reinstall to be certain that the installer can't see or use it.

 

[films&games]

I don't understand what you mean? Why not just update to new versions when they are available? Or, do you mean this contains the installation files for apps you have installed?

Such as? Directly copying files to and from the system drive could be dangerous. You'd be better of moving your Users folders to the D: drive permanently so that the C: drive isn't polluted.

I really would suggest disconnecting the D: drive when/if you reinstall to be certain that the installer can't see or use it.

I update to a new version of Windows by doing a clean install using the Media Creation tool to create an updated USB stick. I just do not update straight away.

There are no programs installed on my D drive. I just keep installation files (latest program versions at the relevant time of each Windows installation) for the different programs that I want to install again, once Windows has been clean installed.

What files/folders should be on C drive, except installed programs?

In relation to downloading programs, would it be okay to download them directly to the D drive and then run the install from the D drive to install them on the C drive? This would mean that I would not have to copy back any of the installation files first.

Okay. I will do that when if/when I need to reinstall Windows.

 

[ubuysa]

I update to a new version of Windows by doing a clean install using the Media Creation tool to create an updated USB stick. I just do not update straight away.

I'm in complete support of this very wise approach. However, they can (and probably do) update that tool if something significant changes in the installation files, so you're much better off waiting to download it until you're ready to install.

There are no programs installed on my D drive. I just keep installation files (latest program versions at the relevant time of each Windows installation) for the different programs that I want to install again, once Windows has been clean installed.

Again, I'm in complete agreement here. This is what I do, although my folder is called 'Program Installation Files' which is more descriptive of what's in there!

What files/folders should be on C drive, except installed programs?

None, except for Windows, installed programs, and anything else that installed programs place on C: (some apps require data files to be on C:. Specifically you should move the folders under C:\Users (Documents, Pictures, etc.) to another drive.

In relation to downloading programs, would it be okay to download them directly to the D drive and then run the install from the D drive to install them on the C drive? This would mean that I would not have to copy back any of the installation files first.

Yes, not only is it OK it's wise (it's what I do). The installation file can be anywhere.

BTW. In post #22 where you said this...

I ran Startup-Repair, the computer restarted and displayed the generic message ”Startup-Repair couldn't repair your PC”

I noticed the log file was listed as being saved in D:\Windows\System32\Logfiles\Srt\SrtTrail.txt.

...if you'd booted the Windows installation media to run Startup Repair the use of the D: drive is not unusual. The Windows installation media sometimes enumerates your drives in a different order to Windows itself. This can result in your system drive (normally C being given the volume label D (or indeed anything else). My concern that WIndows itself was trying to use your D drive was...ummmm.... (I hate admitting to being wrong)....errrm......a temporary factual inaccuracy! Ok then, I was wrong and the use of the D drive was not unusual at all.

You seem to be well setup, and well organised. Assuming there have been no more BSODs I think the problem was a Malwarebytes/COMODO conflict - it's not the first time.