BSODs on a brand new windows install

1. According to the logs the SSD drive is this
Crucial MX500 1TB 3D NAND SATA 2.5 inch 7mm (with 9.5mm adapter) Internal SSD | CT1000MX500SSD1 | Crucial UK

2. and it is NOT partitioned GPT.
It is partitioned MBR
Name : CT1000MX500SSD1
Model : CT1000MX500SSD1
Manufacturer :
PartNumber :
SerialNumber : 2052E4E17CD2
MediaType : SSD
BusType : ATA
BootDrive : True
PartitionStyle : MBR
FirmwareVersion : M3CR033
Size(GB) :
GUID :
Health Status : Healthy
Wear : 0
Temperature : 33
TemperatureMax : 0
PowerOnHours : 75
ReadErrorsUncorrected : 0
ReadErrorsCorrected : 0

3. Quite apart from that it will be most unlikely to be an issue of the drive controller set IDE rather than AHCI
https://download1.gigabyte.com/Files...v.6.0_e_04.pdf
see page 25
OnChip SATA Type (SATA2 0~SATA2 3 connectors)
Configures the operating mode of the integrated SATA controller.
Native IDE Allows the SATA controllers to operate in Native IDE mode. Enable Native IDE mode
if you wish to install operating systems that support Native mode. (Default)
RAID Enables RAID for the SATA controller.
AHCI Configures the SATA controllers to AHCI mode. Advanced Host Controller Interface
(AHCI) is an interface specification that allows the storage driver to enable advanced
Serial ATA features such as Native Command Queuing and hot plug.

4. Do not change it now to AHCI - as I said that setting is not the cause of the problem

5. You have
Advanced SystemCare. 14.1.0 IObit

UNINSTALL it - it is not required on windows 10. It will very likely cause problems and may indeed be the cause of some of the crashes you have.

6. When you have uninstalled it shut down reboot and re-run
system file check and if necessary DISM restore health.
Run SFC Command in Windows 10

follow instructions please at option3 cmd prompt as in yellow background on option 3 point 4.
Do not proceed beyond the DISM
follow the guide EXACTLY please.
I do not need the logs - only the results eg - no errors, errors found and fixed etc.
==========================================
7. I will post further when you reply and please include how the system is now running

While waiting for a reply here, we went ahead and reinstalled windows as AHCI

Its not windows install that is AHCI - windows is installed either with the drive in MBR - master boot record and the firmware in legacy - BIOS or the drive partitioned GPT and the firmware UEFI-
As I said I do not think the IDE or AHCI was the cause of the problem

Re this

We won't add IObit programs for a long time, if this is suspected, despite no issues with them previously for years.

It is of course a matter of your choosing. It is not IOBIt in itself, it is any similar program that purports to manage your windows 10 system - especially with the use of a registry cleaner
https://answers.microsoft.com/en-us/...7-1a424658609b


I suggest you ensure firmware is UEFI and follow this to delete all partitions and then the install media should create the necessary partitions
Please see this
Clean Install Windows 10

3 Boot to the UEFI firmware settings for your motherboard, and enable or disable UEFI or Legacy BIOS (CSM) mode for how you want to install Windows 10.

see sections 14 and 15.


That said the error report may suggest that there is either a bad connection to the drive - power or data
OR you did not delete all partitions on the drive as in the link.

It could if it was not new, be a failing drive OR indeed as you state that the previous drive failed

Last SSD crashed a week ago

there could possibly be another hardware defect.

Your first approach is to follow the guide for the clean install using UEFI and delete all partitions.
Previously your OS was installed MBR legacy BIOS
BIOS Mode Legacy

Having examined more of the logs I suspect the issue is as indicated in your post 3 event viewer error and as I said - bad connection/bad sata cable from sata port to drive.
I doubt it is the new drive itself.
What were the circumstances of the old drive failing - do you have evidence as to how it failed - from for instance a chkdsk on it.

Some of the dumps also suggest a read error on the drive.
Check those connections
Try another sata data cable if you have one available
It could possibly be ram - we can check that if need be after you reply.

Where is the reinstall from - are you referring to a clean install of windows 10 from the created media using this link
https://www.microsoft.com/en-gb/soft...load/windows10

That would be my recommendation to eliminate any errors in your existing install media

1. If that chkdsk showed bad clusters, on an SSD drive that is more or less new, then it is likely to be

1. Repeated failures of writes to the drive, caused by unexpected shutdowns
2. Bad power connection to the drive from the PSU
3. Defective PSU
4. Defective ram
OR of course the board or CPU

2. As I asked before

What were the circumstances of the old drive failing - do you have evidence as to how it failed - from for instance a chkdsk on it.

3. That said send please the event log showing the opened disk error on the 19/2 event 154 and the WHEA event that is hidden here by the second part of the screenshot

Open event viewer as you have
open that event and then when the window opens as per your partial showing of event 140
click copy
open notepad right click and click paste
save and attach the two please.

4. You must have that person run memtest it is vital that we certify there are no ram errors

5. My APOLOGIES regarding my misleading information re UEFI install - did not realise that the board was NOT UEFI firmware but traditional BIOS with Hybrid EFI - which is not the same as true UEFI

6. Please do not attempt to run that tweaker
winaero tweaker.
mentioned by my colleague PP78X
while I am trying to sort out the problem.
Using that could change various settings that would make it too difficult for me to make further determinations as to what may be the problem.
It is only my opinion, but I do not think you should run that whilst we have an unstable system.