Yes, it's normal especially if you did not do a clean install.
I'm starting to suspect the SSD is going bad.
Sudden Shutdowns and Immediate Reboots
- Thread starter Francespo
- Start date
-
- Tags
- sudden shutdown window 11
-
Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.
Why not Click Here To Sign Up and start enjoying great FREE Tech Support.
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
- Status
I'm starting to suspect the SSD is going bad.
But why the SATA SSD too then?
It seems like they "lost" their letter path (you can see it in the previous picture I sent). I'm certain that the NVME was D, looking at the current letters the HDD has become D
Ok I'm reading the guide for a clean installation more carefully. I probably made the same mistake twice: the drive was not completely free before installing windows, the first time I deleted everything (the second time I forgot to do so) but then, before installing windows, I made another partition on the same drive.
I see from the windows guide that there must be only one "unallocated space".
I'll perform another last windows clean install, this time making sure to follow the procedure correctly
I did that! The fact that for the first time it asked me the Windows key after setup makes me think that neither of the 2 previous attempts was truly a clean install.
I'll update Windows, install drivers and then I'll send you the usual reports. Is there anything else I should do like the other commands you suggested to me before?
No, just let me know.
You've done a great job following instruction, I wanted to point that out and thank you for that.
You've done a great job following instruction, I wanted to point that out and thank you for that.
Thank you for your help first of all.
Yesterday, before going to sleep, I installed drivers and I left Windows update running with install all, then restart. When today I woke up I found my pc in sleep mode. I booted it up to check if the updates were completed but I hit another 3 "shutdown-bootup streak" even before getting to the pin screen with the same blue screen sequence I previously sent.
Now, I won't be able to access to my pc for the next 7-8 hours but I'll read whatever you write.
Note: it already happened the I left my pc in sleep mode overnight and I clearly remember that the other time as well the issue was very frequent in the first minutes after the pc awakening
The ones Windows Update prompts me to install and those that can be installed from the msi driver utility.
Ok...
Please follow these instructions carefully:
Please follow these instructions carefully:
Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista
If your BSODs are software related, Driver Verifier can help by subjecting 3rd party (non-Microsoft) drivers to a variety of stresses and tests to find improper behavior to hopefully find the rogue driver that is causing your BSODs. Driver Verifier monitors kernel-mode drivers and graphics...
www.sysnative.com
I did that and verified that it was running. How long should I keep it running?
I am sharing with you another MBT report since it now includes the event reporting the sudden shutdown, I also wanted to share the Speccy report again, but the publishing of the snapshot operation times out (a conflict with the driver verifier maybe?), anyways I didn't change anything on my config so if the only thing it does is listing computer config and peripherals it should be the same as before
BSOD or reboot?
Ok, lets turn Driver Verifier off.
Open an elevated command prompt-
Hit Start, type cmd, then CTRL+SHIFT+ENTER
An elevated prompt should open. In this prompt, copy and paste verifier /reset and hit Enter. Reboot.
Ok, lets turn Driver Verifier off.
Open an elevated command prompt-
Hit Start, type cmd, then CTRL+SHIFT+ENTER
An elevated prompt should open. In this prompt, copy and paste verifier /reset and hit Enter. Reboot.
Oh I misunderstood the "until now". Ok, well go ahead and follow the instructions above to turn verifier off please. Let me know if it reboots or BSOD's.
My bad, it wasn't clear.
I stopped the verifier and I got this response, is it normal that says no verified drivers?
Yes, normal. If any of the drivers were a problem, driver verifier would root it out, usually with a BSOD.
Use the PC as you normally do. Please don't install anything until we are finished.
If you don't have any issues by this evening, you can start installing your favorite programs. Only install one at a time, use it and let it sit for a few hours and if you don't have any issues, move onto the next program and repeat.
If you have an issue, note the last app you installed.
Use the PC as you normally do. Please don't install anything until we are finished.
If you don't have any issues by this evening, you can start installing your favorite programs. Only install one at a time, use it and let it sit for a few hours and if you don't have any issues, move onto the next program and repeat.
If you have an issue, note the last app you installed.
The thing is I have still had issues even without installing any additional program other than minitoolbox and speccy.
I am not surprised that during those 24 hours there weren't reboots since they always occur after I turn on my PC after several hours of being turned off or in sleep mode
According to you, after all those tests, how likely is it that the problem is software-related rather than hardware-related? Is there any particular component I should try to substitute and test the build without?
- Status