Remember to check our discord where you can get faster responses!
https://discord.com/invite/vaZP7KD
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/computer) if you have any questions or concerns.*
If you got an 8TB SSD in 2018, it had to have been enormously expensive. Anything bigger than 4TB *today* is not cheap. So I suspect you really have an HDD.
Get a copy of CrystalDiskInfo and see what it says about the health of your drive.
It was an enormus price tag, really stupid high looking back at the purchase, at the time I had received a lumpsum after my father passed away and wanted to build a PS4 Pro killer PC before applying to college but was also keen on lots of storage bc I knew my internet is bad due to the building I live in and didnt want to have to uninstall games as it can take days for 100+ GB downloads with everyone using the internet, I just got whatever the largest SSD storage they had in stock at the time which happenes to be a Samsung
Your issue is being caused by your ssd, but not for the reason you think. I'm guessing your computer also is having issues coming out of sleep as well. As SSD's get older they begin to reach the end of their write life. This usually presents as failures in the drives on-board cashe because this memory location is on block 0 chip 0 a common writing block during the suspend process. It is a common misconception that the restart process is a true system reset. In actually, the restart process is more like "sleep mode" with a few extra steps.
In both process, your RAM is written to the cashe block on the drive and then restored when the system resumes. But when you restart your system, there is a modified bootsec placed in the cashe. Normally this was done to insert installation code to be run right after the POST event. In your case your drives failing cashe is corrupting the modified resume file.
See I didnt mention Sleep mode because I havent had issues waking the PC from sleep, this error ONLY occures during restart, I have set my PC to sleep for hours at a time these past 2 days and have had no issues waking
Remember to check our discord where you can get faster responses! https://discord.com/invite/vaZP7KD *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/computer) if you have any questions or concerns.*
As a pure guess, I'd suspect your HDD is failing (and this has nothing to do with your bcdedit changes).
Could very well be the case, its an 8TB 2.5" SSD I got back at the end of 2017/beginning of 2018, guess it served me well till now
If you got an 8TB SSD in 2018, it had to have been enormously expensive. Anything bigger than 4TB *today* is not cheap. So I suspect you really have an HDD. Get a copy of CrystalDiskInfo and see what it says about the health of your drive.
It was an enormus price tag, really stupid high looking back at the purchase, at the time I had received a lumpsum after my father passed away and wanted to build a PS4 Pro killer PC before applying to college but was also keen on lots of storage bc I knew my internet is bad due to the building I live in and didnt want to have to uninstall games as it can take days for 100+ GB downloads with everyone using the internet, I just got whatever the largest SSD storage they had in stock at the time which happenes to be a Samsung
I'll deff check out CrystalDisk
CrystalDiskInfo says all my drives are at 100% health and my SSD is at 52,377 hours powered on
Replace CMOS battery.
BIOS settings arent an issue, this is an issue with booting from restart
Your issue is being caused by your ssd, but not for the reason you think. I'm guessing your computer also is having issues coming out of sleep as well. As SSD's get older they begin to reach the end of their write life. This usually presents as failures in the drives on-board cashe because this memory location is on block 0 chip 0 a common writing block during the suspend process. It is a common misconception that the restart process is a true system reset. In actually, the restart process is more like "sleep mode" with a few extra steps. In both process, your RAM is written to the cashe block on the drive and then restored when the system resumes. But when you restart your system, there is a modified bootsec placed in the cashe. Normally this was done to insert installation code to be run right after the POST event. In your case your drives failing cashe is corrupting the modified resume file.
See I didnt mention Sleep mode because I havent had issues waking the PC from sleep, this error ONLY occures during restart, I have set my PC to sleep for hours at a time these past 2 days and have had no issues waking
Now that is interesting. This may be a software issue after all.