Windows 10: Windows 10 won't boot - fresh install

First reinstall had drive D: connected, at least one of the subsequent ones didn't. The one I have now did't, as I decided it would be safer to install Windows with a minimal number of extras, then add things like this afterwards.

Wasn't run manually. The first time I tried to access the Downloads folder on the D: drive, File Explorer gave me an error message and offered to check the disk. I accepted its kind offer *Smile

Remember I've installed three times since Sunday, so you could be seeing a run from before the latest install.

A very good question, and one that bothers me. As I said, I've had this disk attached for some time and never had any problems. That doesn't mean to say there weren't any, but I never had any, and use the disk a lot.

It's possible that something happened to it during one of the installs, but I wouldn't like to say for sure.

It's running now, but will take some time. Will post when it's done. Got through stages 1-3 OK, just on stage 4 now.

Thanks again.

 

Hmm, chkdsk seems to have stopped. It's currently showing...

Stage 4: Looking for bad clusters in user file data ...Progress: 15641 of 776688 done; Stage: 2%; Total: 0%; ETA: 8:04:24 ..

...but it seems to have been showing the same thing since I last posted. It was certainly at 2% when I posted.

I wouldn't have expected it to take this long. Any ideas?

 

In the left lower corner search type > system > open system control panel > on the left pane click advanced system settings

> on system properties under startup and recovery click settings > post an image into the thread.
> on system properties under performance click settings > on performance options click the advanced tab > under virtual memory click > change > post an image into the thread of the virtual memory

For startup and recovery settings if automatically restart is checked > un-check automatically restart.
For write debugging information make sure it is set to automatic memory dump

Download and install Whocrashed: http://www.resplendence.com/whocrashed
Above analyze click on tools > crash dump test > type: ACCEPT
Click analyze > post an image into the thread.
Run the log collector after the above step and post a zip into the thread:
log collector v2-beta06.zip

There are many WHEA events displayed in the event logs:
Code: Event[733]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:04:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[734]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:05:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[735]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:05:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[736]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:06:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[737]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:06:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[738]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:07:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[739]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:07:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[740]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:08:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[741]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:08:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[742]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:09:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[743]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:09:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[744]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:10:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[745]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:10:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[746]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:10:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[747]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:10:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[748]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:10:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[749]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:11:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[750]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:11:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[751]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:12:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[752]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:12:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[753]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:13:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[754]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:13:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[755]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:14:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[756]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:14:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[757]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:15:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[758]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:15:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[759]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:16:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[760]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:16:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[761]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:17:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[762]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:18:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[763]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:19:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[764]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:19:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[765]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:20:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[766]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:21:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[767]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:22:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[768]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:23:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[769]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:24:48.688 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event Event[770]: Log Name: Microsoft-Windows-Kernel-WHEA/Errors Source: Microsoft-Windows-Kernel-WHEA Date: 2018-01-11T15:25:48.687 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: WHEA Error Events User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Daisy Description: WHEA Event[/quote]
Code: Event[18728]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-01-11T15:09:49.414 Event ID: 47 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Daisy Description: A corrected hardware error has occurred. Component: Memory Error Source: Corrected Machine Check The details view of this entry contains further information.[/quote]
The WHEA events started displaying Memory on 1/10/18


Open device manager > click view > show hidden devices > expand all rows > look for icons that are yellow triangles with black exclamation marks > post images into the thread.

Change power options from balanced to high performance

Code: Event[5899]: Log Name: Application Source: Microsoft-Windows-Search Date: 2018-01-10T18:18:25.569 Event ID: 7042 Task: Search service Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Daisy Description: The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt. Details: The content index catalogue is corrupt. 0xc0041801 (0xc0041801)[/quote]

 

chkdsk /x /f /r when ran requires a reboot to lock the drive.
It typically will run up to the teens and remain there displaying for example 11% until the command is completed.
It may take many hours to complete.

Which drive letter corresponds to which drive: Seagate, WDC, Samsung, etc. and which one has the Windows OS?
Which one is supposed to be GPT and which ones MBR?

 

Did both (second was set already).

This will have to wait until later, as I'm trying to get some work done!

Something I forgot to mention before. When I got the machine, it had 8Gb of Dell memory (that was the smallest they would sell me). I don't trust Dell memory, as it's cheap stuff, so I added 32Gb of either Crucial or Kingston memory, which I was advised were the best. I put the new memory in the first two slots, and moved the Dell stuff to the 3rd and 4th slots. I wonder if it's the Dell stuff that's causing the errors.


I might take those two out and see if I still get so many errors. Worth a quick check.

None at all *Smile

Done.

[/quote] Yeah, I saw that, but didn't think it was that important in the scheme of things.

Overall, this PC is in a mess! I really don't know where to start with it. It's only 18 months old.

Thanks again. Does any of what I posted help?

 

Sorry, you lost me a bit there. Do you mean I need to reboot before running it, or after? Either way, how does that explain the fact that the display hasn't changed for ages. I can't hear any drive activity.

C: drive is the SDD, on which is installed Windows

D: drive is the HDD, which is a data drive

F: is an external HDD which is used for backups.

Sorry, no idea about GPT and MBR, you're well outside my area of knowledge!

Thanks again

 

Each of the drives has a manufacturer and on the computer there are 3 different companies.
Is it possible to identify the drive manufacturer to the drive letter?

Samsung SSD 850 PRO 1TB
Seagate Backup+ Hub BK
WDC WD10EALX-759BA1

This is what is seen when using chkdsk /x /f /r as compared to chkdsk /scan


C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.


Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

type: Y
reboot

 

The Samsung SSD is my C: drive

The WDC is my D: drive (data)

The Seagate is my F: drive (external backup)

Not sure about the bit about running chkdsk when the PC restarts. how did you get that?

Thanks

 

When the chkdsk command is used there are multiple switch commands/ switch options:
scan
spotfix
f
r
x
etc.

Some of the command when ran properly will require a reboot. Others can be run without a reboot.
To get the best scan it requires locking the drive and a reboot to run the chkdsk on the next boot when the computer is not in use.

In an early post Tony K had commented about using UEFI instead of Legacy.
The UEFI provides faster boot times and better security.
When using Legacy BIOS the drive is MBR.
When using UEFI BIOS the drive is GPT.

With the information that you posted on the drive letters:

Please verify the size and the drive:.......................size...............free
Samsung SSD 850 PRO 1TB > MBR >............ C: 953.33 ........761.09 \Device\HarddiskVolume2
Seagate Backup+ Hub BK > ...GPT >............. F: 5588.9 ........3286.99 \Device\HarddiskVolume5
WDC WD10EALX-759BA1 > ...MBR> ..............D: 931.49 ........228.26 \Device\HarddiskVolume3

Please open disk managerment > widen the status and volume columns so that the contents of the rows are in full view and nothing is cutoff > post an image into the thread

 

To eliminate the D: drive as a source of error, would it help if I unplugged it and see if the machine is OK when I restart? If I get the same issue, then it would imply it's nothing to do with the D: drive.

As for UEFI, we tried that and it caused all sorts of problems. I was advised to switch back to the defaults (Legacy) and reinstall.

However, I'm out of my depth here (trying hard to concentrate through flu!), so feel free to correct me if I'm wrong.

Thanks

 

If you have the time the best for long term is the following:
1) Remove or disconnect all drives except 1 drive
2) Change the BIOS to UEFI
3) Perform another clean install windows 10 and only install computer manufacturer drivers (don't install applications, files, images etc.
4) Check the hardware after the clean install (CPU, GPU, RAM, Drive, etc.)
5) Once hardware problems are ruled in / ruled out then restore image.

 

Uh oh! I may be in deep doodoo here. I assumed that choosing BIOS defaults as I instructed you to do would've placed it in UEFI mode. That is not true or is default legacy MBR scheme?

Windows 10 won't boot - fresh install - Page 2 - Windows 10 Forums

 

Don't know. If you look at the picture I posted earlier, you'll see it only offers Legacy (which it was set to) and UEFI. We tried setting it to EFI, and it caused problems.

 

That's pretty much what I did the reinstall before last. Was a disaster!

 

By the way, please could you confirm that I was using the memory checker correctly. I just booted from the USB and let it run. This is what it looked like after a few hours...





Do I just leave it like that? I made a mistake and thought I had to press Esc to continue to the next test, and it ended the test.

Please advise, as I'd like to set it off again tonight.