Windows boots to a black screen with cursor after MBR2GPT conversion, help me solve t - Overclock.net - An Overclocking Community

Forum Jump: 

Windows boots to a black screen with cursor after MBR2GPT conversion, help me solve t

 
Thread Tools
post #1 of 1 (permalink) Old 08-21-2018, 06:09 PM - Thread Starter
Linux Lobbyist
 
Skyblaze's Avatar
 
Join Date: Sep 2016
Posts: 53
Rep: 0
Windows boots to a black screen with cursor after MBR2GPT conversion, help me solve t

Let me preface this thread by saying I know I could solve this issue by reinstalling Windows, however by doing it that way I would never find the actual cause and learn something along the way. I also have a secondary OS with a full image-backup of my main Windows 10 install so I have infinite retries, although I don't want to torture my SSD every time with 70gb writes.

My Windows 10 install is also somewhat unique, its drive letter is T: and it doesn't have a System Reserved Partition, thus the main partition is exactly at the beginning of the drive. This makes MBR2GPT fail to validate as it expects a System Reserved Partition at the beginning but this problem was easy to solve. None of this ever caused any problem before, I updated from the first Windows 10 release all the way to 1803 and never had any issue.

What I did:

- Use Partition Master to shrink my OS partition by 100mb and move the OS partition 100mb forward
- Windows is still fully operational after this
- MBR2GPT now validates and converts my drive correctly
- Going into my UEFI and disabling CSM

What happens:

- The Boot animation shows up fine
- Windows 10 boots just fine in full UEFI GPT mode
- All USB devices turn off then back on as Windows is handled control by the UEFI
- The boot animation disappears
- My screen-resolution changes to 1080p which indicates Windows booted successfully
- The boot animation reappears for one or two seconds
- Instead of the login screen I'm greeted with a black screen
- If I move the mouse I can see the mouse cursor with the "working" mouse cursor showing up randomly
- The mouse cursor jumps back to the center every few seconds which makes it seem like Windows is stuck in some loop
- Waiting up to 15 minutes shows no change and I have to hard power off the system

What I tried so far:

- Safe Mode and Low Resolution Mode make no difference
- Repeating the process two times, no change
- Doing a manual MBR to GPT conversion with Partition Master and creating the EFI System Partition and the boot-loader part myself
- This ended me up with the same behavior, Windows boots just fine but still can't reach the login screen
- Disconnecting all drives but my Win10 SDD before, during and after the process
- Booting from a Windows install USB and trying Startup Repair which couldn't fix anything but left me with a strange error in SrtTrail I can't believe

Code:
Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎8/‎12/‎2018 4:41:44 PM (GMT)
Number of repair attempts: 2

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 250 ms

Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 32 ms

Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 1594 ms

Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms

Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 390 ms

Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Root cause found: 
---------------------------
Boot critical file C:\WINDOWS\boot\resources\custom\bootres.dll is corrupt.

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 32 ms

Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 812 ms

Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 2312 ms

Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 375 ms

Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Root cause found: 
---------------------------
Boot critical file c:\windows\boot\resources\custom\bootres.dll is corrupt.

Repair action: File repair
Result: Failed. Error code =  0x57
Time taken = 921 ms

Repair action: System files integrity check and repair
Result: Failed. Error code =  0x57
Time taken = 610 ms

---------------------------
---------------------------
c:\windows\boot\resources\custom\bootres.dll doesn't exist on my MBR system and I don't see why Windows would want a custom bootres.dll file and Windows boots as far as it does if it's truly the cause

So what happens here? I'm grateful for any comment!

Skyblaze is offline  
Sponsored Links
Advertisement
 
Reply

Quick Reply
Message:
Options

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off