Windows 10: Sudden slow boot time on Windows Loading screen with SSD

The temperature is to high, you should clean all dust and dirt from CPU, Fan and other components. You should also clean and apply new thermal paste to CPU.

Can you please uninstall Standard PS/2 Keyboard and Microsoft PS/2 Mouse drivers from Device Manager and restart your computer.

Running the Chkdsk command in booted Windows wont always give you correct scan result. Can you please schedule a error checking at next reboot.

Fast startup (aka: hiberboot, hybrid boot, or hybrid shutdown) is turned on by default in Windows and is a setting that helps your PC start up faster after shutdown. Check to see if this feature is turn on if its turn it off and restart your computer to see issue resolves.

How to Turn On or Off Fast Startup in Windows 10

Uninstall all third part-party antivirus and firewall program to check if issue resolves.

You can also try to fix to issue doing repair install of Windows 10 without losing anything.

How to Do a Repair Install of Windows 10 with an In-place Upgrade

 

As you can see in the picture above, the temperatures are normal, I bought the MB, CPU, RAM, GPU and M.2 SSD on Black Friday and applied the Arctic MX-4 thermal paste. While gaming, which is a heavy task, the CPU hits about 57º celsius and the GPU about 68º celsius, I don't think I need to re-apply the thermal paste after such short time. About the temperature in the M.2 SSD, I've searched it about a month ago and it's normal to get 50s at idle and 70+ when using it. I've also uninstalled both keyboard and mouse ps/2 earlier and they went back after restart. About the chkdsk, I just mentioned that I did the test earlier within Windows, but as you requested to do it before boot, so I did it, and again, it reported no errors. I've also disabled/enabled fast startup yesterday before posting here and it didn't change anything. The last thing I want is to reinstall Windows completely or lose my settings, if possible.

 

BTW, it's really hot where I live. So it's normal to have high temperatures. Ultimately I do my best to control them.

 

When you do a repair install of Windows 10 you wont lose any of your personal settings, personal files and installed programs.

How to Do a Repair Install of Windows 10 with an In-place Upgrade

Lets check for malware infections.

Malwarebytes' scanner
If this program is already installed: Skip the installation and run only the scan!
Download and install: Please download Malwarebytes' scanner to your desktop.

• Double-click mb3-setup-consumer-3.x.x.xxxx and follow the prompts to install the program.
• Click Finish.
• On the Dashboard, click the 'Check for Updates' button.
• After the update completes, click the 'Scan Now' button.
• A Threat Scan will begin. Please allow it to progress through the scanning process.
• When the scan is complete, if there have been detections, click Quarantines Selected button to allow the program to clean what was detected.
• In most cases, a restart will be required.
• Wait for the prompt to restart the computer to appear, then click on Yes.

How to get logs: (Export log to save as txt)

• After the restart once you are back at your desktop, open Malwarebytes once more.
• Click on the Reports tab > Scan Report. (if you have done more than one scan in the past, select the most recent that shows the Date and time of the scan just performed. Press View Report button.
• Click 'Export'.
• Click 'Text file (*.txt)'
• In the Save File dialog box which appears, click on Desktop.
• In the File name: box type a name for your scan log.
• A message box named 'File Saved' should appear stating "Your file has been successfully exported".
• Click Ok
• Find the log on your Desktop and Attach that saved log to your next reply.

(Copy to clipboard for pasting into forum replies or tickets)



Download the right Windows bit version (32-bit or 64-bit) of RogueKiller

• Quit all running programs
• Once done, move the executable file to your Desktop, right-click on it and select
  
  Run as Administrator (for Windows Vista, 7, 8, 8.1 and 10 users)
• If the program is blocked, do not hesitate to try several times. If it really does not work (it could happen), rename it to winlogon.exe
• Click on the Start Scan button in the right panel, which will bring you to another tab, and click on it again (this time it'll be in the bottom right corner)
• Wait for the scan to complete
• On completion, the results will be displayed. Click on the Open Report button in the bottom left corner, followed by the Open TXT button (also in the bottom left corner)
• This will open the report in Notepad. Copy/paste its content in your next reply

 

Malwarebyteswww.malwarebytes.com-Log Details-Scan Date: 2/22/18Scan Time: 1:10 PMLog File: f0b33c60-17ea-11e8-867d-4ccc6af66280.jsonAdministrator: Yes-Software Information-Version: 3.3.1.2183Components Version: 1.0.262Update Package Version: 1.0.4052License: Free-System Information-OS: Windows 10 (Build 16299.248)CPU: x64File System: NTFSUser: CUERVOTR\thiag-Scan Summary-Scan Type: Threat ScanResult: CompletedObjects Scanned: 291045Threats Detected: 0(No malicious items detected)Threats Quarantined: 0(No malicious items detected)Time Elapsed: 1 min, 5 sec-Scan Options-Memory: EnabledStartup: EnabledFilesystem: EnabledArchives: EnabledRootkits: DisabledHeuristics: EnabledPUP: DetectPUM: Detect-Scan Details-Process: 0(No malicious items detected)Module: 0(No malicious items detected)Registry Key: 0(No malicious items detected)Registry Value: 0(No malicious items detected)Registry Data: 0(No malicious items detected)Data Stream: 0(No malicious items detected)Folder: 0(No malicious items detected)File: 0(No malicious items detected)Physical Sector: 0(No malicious items detected)(end)

RogueKiller V12.12.5.0 (x64) [Feb 19 2018] (Free) por Adlice Softwaremail : http://www.adlice.com/contact/Feedback : https://forum.adlice.comSite : Blog Articles - Adlice Software : Web Server's Default Page Operacional : Windows 10 (10.0.16299) 64 bits versionIniciou : Modo normalUsuário : thiag [Administrador]Started from : C:\Users\thiag\Desktop\RogueKiller_portable64.exeModo : Escanear -- Data : 02/22/2018 13:17:31 (Duration : 00:22:47)¤¤¤ Processos : 0 ¤¤¤¤¤¤ Registro : 8 ¤¤¤[PUP] (X64) HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce | Application Restart #1 : C:\MSI\LiveUpdate\DL_FILE\Killer_Network_Drivers_9.0.0.46\Liveinst.exe /killer /RestartByRestartManager:31896E33-0DFA-40cb-81FD-99B51239595C [x] -> Encontrado[PUP] (X86) HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce | Application Restart #1 : C:\MSI\LiveUpdate\DL_FILE\Killer_Network_Drivers_9.0.0.46\Liveinst.exe /killer /RestartByRestartManager:31896E33-0DFA-40cb-81FD-99B51239595C [x] -> Encontrado[PUP] (X64) HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\RunOnce | Application Restart #1 : C:\MSI\LiveUpdate\DL_FILE\Killer_Network_Drivers_9.0.0.46\Liveinst.exe /killer /RestartByRestartManager:31896E33-0DFA-40cb-81FD-99B51239595C [x] -> Encontrado[PUP] (X86) HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\RunOnce | Application Restart #1 : C:\MSI\LiveUpdate\DL_FILE\Killer_Network_Drivers_9.0.0.46\Liveinst.exe /killer /RestartByRestartManager:31896E33-0DFA-40cb-81FD-99B51239595C [x] -> Encontrado[PUP.HackTool|VT.Detected] (X64) HKEY_LOCAL_MACHINE\System\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRule s | {8C345444-FB41-4743-A6AF-10A52819B886} : v2.27|Action=Allow|Active=TRUE|Dir=In|Protocol=6|LPort=1688|App=C:\Windows\AutoKMS\AutoKMS.exe|Name= AutoKMS| [-] -> Encontrado[PUP.HackTool|VT.Detected] (X64) HKEY_LOCAL_MACHINE\System\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRule s | {7FF9E76D-8050-446B-8950-EF0CB72F3C92} : v2.27|Action=Allow|Active=TRUE|Dir=Out|Protocol=6|LPort=1688|App=C:\Windows\AutoKMS\AutoKMS.exe|Name =AutoKMS| [-] -> Encontrado[PUM.Policies] (X64) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System | ConsentPromptBehaviorAdmin : 0 -> Encontrado[PUM.Policies] (X86) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System | ConsentPromptBehaviorAdmin : 0 -> Encontrado¤¤¤ Tarefas : 1 ¤¤¤[PUP.HackTool|VT.Detected] \AutoKMS -- C:\Windows\AutoKMS\AutoKMS.exe -> Encontrado¤¤¤ Arquivos : 1 ¤¤¤[PUP.HackTool][Pasta] C:\Windows\AutoKMS -> Encontrado¤¤¤ WMI : 0 ¤¤¤¤¤¤ Arquivos de hosts : 0 ¤¤¤¤¤¤ Antirootkit : 0 (Driver: Carregado) ¤¤¤¤¤¤ Navegadores : 1 ¤¤¤[PUM.HomePage][Firefox:Config] 3nj6d6gf.default : user_pref("browser.startup.homepage", "moz-extension://1eda7cd8-1a10-4edf-bedd-3ea40f28870f/dashboard.html"); -> Encontrado¤¤¤ Verificação da MBR : ¤¤¤+++++ PhysicalDrive0: ST1000DM003-1CH162 +++++--- User ---[MBR] 43ac937f0b4b35fd28411e4b5f8a69b4[BSP] 5fbd3c6c8aae6c097682c79b7e13cedf : Empty|VT.Unknown MBR CodePartition table:0 - Basic data partition | Offset (sectors): 2048 | Size: 953868 MBUser = LL1 ... OKUser = LL2 ... OK+++++ PhysicalDrive1: SAMSUNG HD161HJ +++++--- User ---[MBR] 22cdc553b96df7978b88ea21813d51d1[BSP] 98c374aedf641a29bbb6aa5f5a998b95 : Empty|VT.Unknown MBR CodePartition table:0 - Basic data partition | Offset (sectors): 2048 | Size: 152626 MBUser = LL1 ... OKUser = LL2 ... OK+++++ PhysicalDrive2: WDC WDS256G1X0C-00ENX0 +++++--- User ---[MBR] 29159466cdce39be30625db92b53eb17[BSP] df4f83c1f72e36823a12b0dfc7617313 : Empty MBR CodePartition table:0 - [SYSTEM][MAN-MOUNT] Basic data partition | Offset (sectors): 2048 | Size: 499 MB1 - [MAN-MOUNT] EFI system partition | Offset (sectors): 1024000 | Size: 100 MB2 - [MAN-MOUNT] Microsoft reserved partition | Offset (sectors): 1228800 | Size: 16 MB3 - Basic data partition | Offset (sectors): 1261568 | Size: 243582 MBUser = LL1 ... OKError reading LL2 MBR! ([1] Incorrect function. )

 

Please allow RogueKiller to delete all the found infections and restart your computer to see issue resolved.

 

Deleted all files and the problem persists.

 

Check for new firmware update for your SSD drive.


Scan with Autoruns

Please download Autoruns by Sysinternals and save the file to your desktop.

• Right-click on the AutoRuns.exe icon and select Run as Administrator to start the tool.
• It is important that you do not use your machine while the tool is running.
• Wait patiently until the tool finishes its scanning. You will be notified with the Ready message in the lower left corner upon completion.
• Go to File menu and select Save.
• Make sure that the Save as type option is set to AutoRuns Data (*.arn) and the place to save will be your desktop. Name it somehow that you'll be able to identify it.

Please attach the file to your next post.
To attach it:

• After typing in your message, click More reply options instead of Post.
• below the post preview and the post editor, you should be able to see Attach files option - please click Choose file.
• in the pop-up window navigate to the desktop. Choose the one previously mentioned and attach it.

If the file will be to big to attach it (it may happen), then please host it on a Dropbox account or a site like mediafire.com, providing me the link to the uploaded file.

 

I've updated the firmware of the SSD about two weeks ago with the WD SSD Dashboard software. Here's the log Autoruns returned: autoruns log

 

Clear the check mark for all programs i have marked and point out and restart your computer to see issue resolves.
Delete all files mark with yellow color.

 

Did what you told me and the problem still exists.

 

WP 20180222 17 42 35 Pro - YouTube I've recorded a video showing the problem, as you can see, it seems that in the loading screen the SSD "turns off" and only starts about 60 seconds after, you can see by the LED that starts to blink and then shows the login screen.

 

Sorry for late reply, your problem is the BIOS boot process taking to long to boot the system. Can you boot your computer into BIOS/UEFI setup screen and reset BIOS settings to factory default.

If issue not resolved try disconnecting all hard disk drives and all externally attached devices, except for mouse and keyboard and see if the boot time speeds up.

 

I just did that, the problem persists with default BIOS setup, I'll try now with drives disconnected .

 

Surprisingly the first boot after disconnecting the other two drives was normal, it took about 3 seconds to appear the login screen, but at the second and third attempts it went back to about 60 seconds and then showing the login screen.