Windows 10: Windows Boot up Issue

Hi Kev/Ess , Just so you are both aware that command will only tell if the OS has Trim enabled , it won't tell you if the Controller is actually receiving those Commands , there has been numerous Intel RST Drivers with Trim disabled , especially in Raid0.

So I use a small program called TrimCheck for that if I have doubts....

Solid State Drives Easy TRIM test methods

But the Trimcheck Files are here:

Index of /trimcheck

just place the file on the Drive you want to test and run it ,(double click it) close the window and re-run it 2-3 mins later

and more info here on github

GitHub - CyberShadow/trimcheck: SSD TRIM check tool for Windows


Oh and more info on Ess. Command too by Brink here on Ten.

TRIM Support for Solid State Drives - Enable or Disable in Windows 10 - Windows 10 Forums


KB.

 

Hi Kbird/essenbe

I checked C drive using essenbe suggestion and trim is on and I double checked with your suggestion Kbird using TrimCheck and that also came up with trim is on.

The old SSD that is now drive E, does that need to have the trim on, it only has a few programs on it for now.

I am currently still monitoring the system with the Logik Hub (USB2) removed, to see if it stops the boot sequence.

Kevin

 

Ok good news....

Yes all SSD's need trim on whether they are the OS Drive or not....

If the SSD is recognised properly in windows , the Defrag tool will only allow you to "Optimise" that Drive not defrag it , it is actually "trimming" the drive when it optimises.

KB

 

I'm glad you have verified that trim is working. With my recommended command prompt I said that the results will show that the OS is sending trim commands to the SSD Controller. The rest is up to the SSD. With Kbird's suggested program it verifies that the controller is doing it's job. So, it seems all is well on that front.

Earlier in the thread I saw where it was suggested you run sfc /scannow and you received errors. Did you run it 3 times with reboots in between each time? I don't see where you answered that. The repairs are actually carried out during a reboot. Sometimes it can't repair all errors at the same time, or some repairs can't be done until other errors are fixed first. So, 3 times is recommended.

Failing a clean sfc, did you run from an elevated command prompt
Dism /Online /Cleanup-Image /StartComponentCleanup
Then run
Dism /Online /Cleanup-Image /RestoreHealth
They will appear to be doing nothing but will give you a successful or failure report eventually. If you get a failure report, please let us know the error.

Assuming you get a successful report, run sfc /scannow again.

Also I noticed you were running BIOS version 3301. That is for the new Broadwell chips. For the chips we are running the latest bios is 2101. I would suggest flashing the bios back to 2101 as Kbird suggested. I don't see where you responded to that recommendation.

A weak PSU could cause the problems you are experiencing. Not a diagnosis, but a possibility. Could you go into BIOS and on the monitoring section of BIOS tell us the MB Temps, CPU Temps, the values of the +12V, +5V and +3.3V please. While in bios, I would suggest to set optimized defaults (F5).

If I was having your problems, I would disconnect all hard drives except the OS drive. Also disconnect everything connected to the computer except mouse, keyboard and monitor. I would also use a USB mouse and keyboard and remove any wireless USB dongles or devices. If you have SD cards or USB drives, remove all of them. In other words, I would remove everything from the system not necessary for the computer to run. Test and see if the problem persists.

The BSOD Posting instructions I asked about will give us a lot of info about your system even though you aren't experiencing BSOD issues. Also a list of programs you have installed could help. You can get those easily from Control Panel > Uninstall a program, or if you have CCleaner installed, go to tools then in the bottom right click save to text file.

I know you guys have had issues with your motherboards, but I am not convinced it is a MB issue. The Motherboard is Posting correctly, as I understand it. Once it passes post, everything is handed off to the OS. When you see the spinning circles, that is when the OS is beginning to boot and load drivers. That seems to be the point where you are having your main problem. These are just some of my thoughts, observations and opinions.

 

essenbe

The reason I did not post results for scannow, I was going to reinstall Windows and if I had the same issue I was going to put a new SSD in. Which is what I currently have now and the old drive I am using for programs.

I am currently still monitoring the system with the Logik Hub (USB2) removed.

I will look into the your last post at the weekend and carry out scannow, BIOS 2101 etc.

Kevin

 

OK, thanks Kevin. Those were just some of my suggestions. FWIW, and I admit to being somewhat OCD, even on a clean install I always run the DISM and sfc /scannow on them just to be assured that everything is right and set up correctly.

 

Certainly the other guy I mentioned is happy to be back on 2101 , not sure if that is your issue ? though the "latest isn't always the greatest" , I am thinking something got messed up with the Broadwell E Code getting added ,which you don't need at this time.

This Post is now 5 Pages long and a week or two long as well, I was going to ask you to recap and see where we are at now actually , as it seems we have gone through a few things, some resolved , some not? ...

I have not found anything conclusive on SD Errors or a way to eliminate them or what causes them ,except that it was an issue in XP and 2K that M$ issued a hotfix for. Perhaps the Win10 Update on Aug 30th had a fix?, as I saw it included fixes for the NTFS File System too amongst others. ( Au V.105)

KB.

 

Hi essenbe

Trying to work my way through your suggestions. It seems that each time one runs CHKDSK there is SD errors? I have run the CHKDSK again then I ran sfc /scannow, each time sfc /scannow came back with "Widows resource protection did not find any integrity violations." What I did notice on one of the CHKDSK runs was 3 errors with the same Event ID "1001", probably nothing.

Attached are the CHKDSK, Errors and the sfc /scannow logs.

Kbird/essenbe
As I mentioned earlier, I am currently still monitoring the system with the Logik Hub (USB2) removed. I have not experienced any boot issues lately. Probably spoke to soon?

 

My USB2 hub was stopping and causing boot issues for me too on my X99 board , so hopefully that is one thing sorted out.

More info on the 1001 event but maybe you saw this? Have seen 1001 errors as having to do with Memory management before though.
Event ID 1001: Windows Error Reporting - TechNet Articles - United States (English) - TechNet Wiki


Try downloading Anvil Storage Utilites , it has an option to Trigger TRIM , do that and then run CHKDSK immediately and see if there are SD Errors , perhaps it is just that TRIM is acting slowly and not cleaning up the drive or only doing it a Boot or shutdown etc? I don't know the exact mechanics of how TRIM works or when , but haae seen reports that SD Errors maybe caused by TRIM not working properly.

Anvil's Storage Utilities Download Version 1.1 2014

 

Kbird

Thanks for the info, hopefully it is all down to this rogue USB2 Logik Hub. I am going to mark this thread solved.

Kevin

 

Good news. I'm glad you have it fixed, and it was something that simple.

 

Thanks for the Update Kevin , let us know if we can help at all.

PS did you check for a newer firmware on the HUB ? my Vantec HUB had one available... my Monitor one didn't

KB