If you installed 8.1, did you do so using the UEFI configuration?
Are you running any other OSes in a Dual Boot configuration?
The bios on your system may have some settings regarding hardware startup with might be involved, since such things as some USB ports may not be started until after boot.
But, as ussnorway mentions, it appears something is keeping your system from setting itself up during the shutdown so the start is effected.
How old is this machine, since we have no information on it?
So far it could be anything from faulty ram (that error says that point was not there) to a simple case of some power setting is incorrect or even programs like a Nortains anti-virus getting delusions of grandeur.
1. Is there any consistency to the slow boots i.e. a certain time of day or every 3rd one will always fail?
2. To track it down we need to see the error reports + a lot of general info like posts of your start-up page and to be blunt… if the end result is just an extra minute or two every couple times you boot then perhaps it isn't worth it?
So the SSD is internal and the RAID is an external set? Have you pinned the problem down to one or the other of those?
I would think the HDD RAID would be fairly slow compared to the mSATA. You might check to see if they might be asleep when you shutdown but I don't know of a way to disconnect the RAID prior to shutting down except manually. I am running a Dell using the mSATA as the primary drive and a 1 TB data drive and seem to have no problem with the Fast Startup.
You might try turning off the Fast Startup and see if anything changes. You might also check the drive where the hibernation file is being written. If it was close to being full, the system might be having a hard time writing the data necessary quickly enough to allow a clean shutdown.
The external headset may be involved also, but the Logitech mouse may have some software related to it being part of the problem. I have seen an Event Manager utility causing some shutdown messages on Windows 7 but my Windows 8 install seems to be OK with no Fast Startup problems.
- I just figured it out right now, I went to the bios and disabled all the hdd drives that I have which are:
1- 2 x 2tb in RAID0
2- 1 x 750gb sshd
- And after that I was just left with my msata ssd which had windows 8.1 installed in it and then I did about 10 shutdows and startups and yes the problem is gone and it's starting up and shuting down even faster than before.
- Right now I can assure that this problem is caused by the other HDD's which are installed in the laptop.
- Also I think that according to the error I mentioned before which says (The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly) it means that when the system shuts down it dosen't close and shut down everything properly including programs and HDD and which in the long run could affect HDD.
So any suggestions on how I can overcome this problem with offcourse enabling back my HDD.
Maybe someone else will know better since I don't have much experience with RAID configurations. But how is the RAID setup as far as connections and power supply? Are the drives matched?
Since you are using RAID 0, I suppose you are not able to replace the problem drive? There may be another reason the one drive is showing some problems, so use your best judgment on troubleshooting the RAID.
Yes you can force it but thats a VERY bad thing to do with RAID...snip...
So is there any way that could force the windows to close this RAID0 drive properly without issues like a program or a bios configuration.
Yes you can force it but thats a VERY bad thing to do with RAID...
1. go to the download page for your machine and see if they offer a newer raid driver than the one you have.
2 the next step is a bios flash and to be very clear, this always iffy... I wouldn't do this on a machine that otherwise works so I don't recomend it!
Before doing a bios flash that may kill your machine, ask yourself;
why do you need them to be in a raid... and can they be moved to an external system to solve the driver issue?