Forever boot Spinning white dots with black screen no logo 0x80000003

Page 2 of 3 FirstFirst 123 LastLast
  1.    1 Week Ago #11

    philc43 said: View Post
    I did wonder if you had specific programs that you could not reinstall. I quite understand. It is possible the OS is stuck in the middle of trying to upgrade to a newer version of W10. You are way behind for some reason.

    Can you run the SFC and DISM commands from the rescue disk to scan the problem drive? If you want to post the logs from these operations we can check them.

    I also think you would be better posting this in the general forum since this sub-forum is for BSOD problems only.
    Caledon Ken said: View Post
    Maybe you could explain the two windows disks and the actual number of storage disks you have. I would use Kyhi's recovery disk and then post a screen shot.

    Disk Management - How to Post a Screenshot of

    Please disconnect drives not needed for boot to simplify story.

    Your external boot media seems to be from 1607 and if I read right you are running DISM on 1803 (17134). Believe they have to the same version.
    zbook said: View Post
    Using Kyhi boot rescue open administrative command prompt and copy and paste:

    Code:
    bcdedit /enum
    bcdedit | find "osdevice"
    diskpart
    list disk
    list volume
    select disk 0
    detail disk
    list partition
    select partition 1
    detail partition
    select partition 2
    detail partition
    select partition 3
    detail partition
    select partition 4
    detail partition
    select disk 1
    detail disk
    list partition
    select partition 1
    detail partition
    select partition 2
    detail partition
    select partition 3
    detail partition
    select partition 4
    detail partition
    select disk 2
    detail disk
    list partition
    select partition 1
    detail partition
    select partition 2
    detail partition
    select partition 3
    detail partition
    select partition 4
    detail partition
    select disk 3
    detail disk
    list partition
    select disk 4
    detail disk
    list partition
    exit
    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    Copy and paste:

    Code:
    c:
    dir
    d:
    dir
    e:
    dir
    f:
    dir
    g:
    dir
    h:
    dir
    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    Bastet said: View Post
    If you can access safe mode & gain access to Windows then you can try turning off fast startup & ‘allow Windows to use my sign in information to fishing setting up this pc after an update’.

    • Hold down the power button for 10 seconds to turn off your device.
    • Press the power button again to turn on your device.
    • On the first sign that Windows has started (for example, some devices show the manufacturer’s logo when restarting) hold down the power button for 10 seconds to turn off your device.
    • Press the power button again to turn on your device.
    • When Windows restarts, hold down the power button for 10 seconds to turn off your device.
    • Press the power button again to turn on your device.
    • Allow your device to fully restart. You will enter winRE.

    Now that you are in winRE, you will follow these steps to take you to safe mode:

    • On the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.




    • After your device restarts, you'll see a list of options. Select option 5 from the list or press F5 for Safe Mode with Networking.
    RingTailCoon said: View Post
    Well? How did it go? Just curious too, and I really consider wiping the drive and start clean, really! :)
    Okay guys, did everything. Hope you will have some kind of magic commands to execute. Let's Start.

    I removed all drives, left the C: drive or the 460gb one - target in this topic.

    Philc32 I posted logs for DISM and SFC. Not sure about SFC logs. I dont know where they are in Kayhi. Took them from C drive. Anyway. If it happens to be stuck in the middle of trying to upgrade, what to do then? Is there some kind of possibility to kill it trying to stop? Or maybe replace windows system files with exact version of windows? I suppose it is 10.0.14393. Just where do I get one and how to do that magic correctly (if it is the case though)? I very likely on this drive disabled windows updates, because I'm not keen of them as they usually break my software.. I also provided image for sfc and dism errors.

    Caledon Ken - I provided the drive screenshot. C drive is the one. I unplugged one second windows drive (ssd) and one 1tb SSD.

    Zbook - I provided logs from your commands

    Bastet - I cannot enter safe mode. I get black screen after entering safe networking (or any other mode i think) and it just stays there.

    RingTailCoon - Still unsolved. Still hoping for the best. I don't even imagine what kind of headache I will have of restoring all the audio plugins to work correctly if I happen to install everything again. That is why I wanna at least boot this disk so I can open everything. Probably if we get it to start I will just start new disk and not touch/upgrade anything on this one haha.

    P.S. I did even clear my CMOS.
    Attached Thumbnails Attached Thumbnails diskScreenShot.PNG   dism.jpg   sfc.jpg  
    Forever boot Spinning white dots with black screen no logo 0x80000003 Attached Files
      My ComputerSystem Spec

  2. Caledon Ken's Avatar
    Posts : 12,768
    Windows 10 Pro x64 Build 1809
       1 Week Ago #12

    Have you tried running DISM from an external source (the external source having V1803 on it).

    Item 6 or 7 in this tutorial

    Use DISM to Repair Windows 10 Image

    If you need 1803 boot media

    https://www.heidoc.net/joomla/techno...-download-tool
      My ComputerSystem Spec


  3. Posts : 23,878
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #13

    The driver letters may change when comparing Windows to Widows RE.
    There was one disk removed that was in the opening post.
    Many of the drive letters have disappeared.
    The drive letters may have changed again in Windows RE after the removal of this drive/disk)

    1) Using the Kyhi boot rescue:
    2) Test the drive using HD Tune > post images into the thread for results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan


    3) Run the log collectors: DM and BETA and post zips into this thread:
    BSOD Crashes and Debugging - Windows 10 Forums

    4) There used to be more recovery options in earlier versions of Windows 10.
    One method that worked for windows 1511, 1607, and 1703 was regback.
    This method is no longer available unless the end user created the file for recovery.

    5) End users are encouraged to use Microsoft feedback so that this feature is restored:
    https://support.microsoft.com/en-us/...nd-us-feedback

    6) For these steps use a camera or smartphone camera to take pictures and post images into the thread

    7) Using a bootable windows 10 iso > open troubleshooting
    Download Windows 10 ISO File | Tutorials
    Download Windows 10

    Some of these steps may have already been performed.
    The steps should be repeated to see the commands and the results.

    8) perform a startup repair > if there is a srttrail.txt > post a share link into the thread

    9) attempt system restore > start with the oldest restore point and keep repeating up to the newest restore point > if there are no restore points or if system restore fails advance to the next step

    10) Open command prompt > Administrator: X:\Windows\system32.cmd.exe > with prompt: X:\Sources>

    Type these commands. (Comments will be in parenthesis)

    diskpart
    list disk
    list volume
    select disk 0
    detail disk
    list partition
    select partition 1
    detail partition
    select partition 2
    detail partition
    select partition 3
    detail partition
    exit

    11) bcdedit /enum
    12) bcdedit | find "osdevice"
    (note the partition drive letter in the result for later use)
    (for all future steps change the drive letter W: to the partition drive letter displayed in this command result)

    13) dism /image:W:\ /cleanup-image /revertpendingactions
    (change the drive letter W: to the partition drive letter displayed in step #12)
    (reboot and reopen command prompt)

    14) dism /Image:W:\ /Get-Packages
    (change the drive letter W: to the drive partition letter displayed in step #12)
    (Find the package(s) that were just installed by date.
    Run the following command on the last installed package:
    example: dism.exe /image:W:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0
    Reboot.)

    15) chkdsk /r /v W:
    (change the drive letter W: to the drive partition letter displayed in step #12)
    (This may take many hours and typically displays ETA)
    (reboot to run the command)
    (after the command has completed reboot as necessary to open command prompt)

    16) sfc /scannow /offbootdir=W:\ /offwindir=W:\windows
    (change the drive letters W: to the partition drive letter displayed in step #12)
    (this may take a while to run)

    17) bootrec /fixmbr
    18) bootrec /fixboot
    19) bootrec /scanos
    20) bootrec /rebuildbcd
      My ComputerSystem Spec

  4.    1 Week Ago #14

    Here's more logs


    Caledon Ken said: View Post
    Have you tried running DISM from an external source (the external source having V1803 on it).

    Item 6 or 7 in this tutorial

    Use DISM to Repair Windows 10 Image

    If you need 1803 boot media

    https://www.heidoc.net/joomla/techno...-download-tool
    zbook said: View Post
    The driver letters may change when comparing Windows to Widows RE.
    There was one disk removed that was in the opening post.
    Many of the drive letters have disappeared.
    The drive letters may have changed again in Windows RE after the removal of this drive/disk)

    1) Using the Kyhi boot rescue:
    2) Test the drive using HD Tune > post images into the thread for results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan


    3) Run the log collectors: DM and BETA and post zips into this thread:
    BSOD Crashes and Debugging - Windows 10 Forums

    4) There used to be more recovery options in earlier versions of Windows 10.
    One method that worked for windows 1511, 1607, and 1703 was regback.
    This method is no longer available unless the end user created the file for recovery.

    5) End users are encouraged to use Microsoft feedback so that this feature is restored:
    https://support.microsoft.com/en-us/...nd-us-feedback

    6) For these steps use a camera or smartphone camera to take pictures and post images into the thread

    7) Using a bootable windows 10 iso > open troubleshooting
    Download Windows 10 ISO File | Tutorials
    Download Windows 10

    Some of these steps may have already been performed.
    The steps should be repeated to see the commands and the results.

    8) perform a startup repair > if there is a srttrail.txt > post a share link into the thread

    9) attempt system restore > start with the oldest restore point and keep repeating up to the newest restore point > if there are no restore points or if system restore fails advance to the next step

    10) Open command prompt > Administrator: X:\Windows\system32.cmd.exe > with prompt: X:\Sources>

    Type these commands. (Comments will be in parenthesis)

    diskpart
    list disk
    list volume
    select disk 0
    detail disk
    list partition
    select partition 1
    detail partition
    select partition 2
    detail partition
    select partition 3
    detail partition
    exit

    11) bcdedit /enum
    12) bcdedit | find "osdevice"
    (note the partition drive letter in the result for later use)
    (for all future steps change the drive letter W: to the partition drive letter displayed in this command result)

    13) dism /image:W:\ /cleanup-image /revertpendingactions
    (change the drive letter W: to the partition drive letter displayed in step #12)
    (reboot and reopen command prompt)

    14) dism /Image:W:\ /Get-Packages
    (change the drive letter W: to the drive partition letter displayed in step #12)
    (Find the package(s) that were just installed by date.
    Run the following command on the last installed package:
    example: dism.exe /image:W:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0
    Reboot.)

    15) chkdsk /r /v W:
    (change the drive letter W: to the drive partition letter displayed in step #12)
    (This may take many hours and typically displays ETA)
    (reboot to run the command)
    (after the command has completed reboot as necessary to open command prompt)

    16) sfc /scannow /offbootdir=W:\ /offwindir=W:\windows
    (change the drive letters W: to the partition drive letter displayed in step #12)
    (this may take a while to run)

    17) bootrec /fixmbr
    18) bootrec /fixboot
    19) bootrec /scanos
    20) bootrec /rebuildbcd
    Okay I start to loose my hope. I probably will loose a lot of projects which i will not be able to open if i reinstall. Not even counting that i have no installations for many of the programs installed..

    Anyway. Here's logs with a lot of pictures you asked. I executed from kys enviroment the bsod logs as u asked. I suppose it's not correct? Because how can i execute it from winpe to different disk which i cannot boot? Also pictures provided for most of the commands listed and dism log provided again.

    And what is the version really for my windows on that 460gb drive? I downloaded 1803 version and tried to dism it with source. Is it okay that mounted wim is from neewer windows vers anyway?

    Also. Please take a look at logs and pictures, i specifically marked out i think the last update packages. Do they not let me boot and mark my system as forever booting? I still highly suspect that if dism and sfc gets sorted out, it should be okay, because i literally previously fixed it with just some of those commands.

    I provided all i could. Now I will just listen to Journey - believe and hope you guys can help me, thank you alot!!
    Forever boot Spinning white dots with black screen no logo 0x80000003 Attached Files
      My ComputerSystem Spec

  5. Caledon Ken's Avatar
    Posts : 12,768
    Windows 10 Pro x64 Build 1809
       1 Week Ago #15

    Did you run DISM from the external 1803 source?
      My ComputerSystem Spec

  6.    1 Week Ago #16

    Caledon Ken said: View Post
    Did you run DISM from the external 1803 source?
    Yes i downloaded 1803 to a flash drive and in kyhi cmd entered dism commands. Specified it's install.wim as source.
      My ComputerSystem Spec

  7. Caledon Ken's Avatar
    Posts : 12,768
    Windows 10 Pro x64 Build 1809
       1 Week Ago #17

    Did it finish successfully?
      My ComputerSystem Spec


  8. Posts : 23,878
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #18

    The images displayed the last successful Windows update 11/2018

    There was a pending update from 12/2018
    KB4100347
    https://support.microsoft.com/en-us/...windows-server

    revertpendingactions failed with error 0x000f082f
    Code:
    DISM   DISM Package Manager: PID=3584 TID=4024 The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB - CPackageManagerCLIHandler::ExecuteCmdLine
    Code:
    DISM   DISM OS Provider: PID=3584 TID=4024 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
    Code:
    DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE
    DISM   DISM Manager: PID=3908 TID=3852 Failed to get the IDismImage instance from the image session - CDISMManager::CloseImageSession(hr:0x800706ba)
    DISM   DISM.EXE:  - CDismWrapper::CloseSession(hr:0x800706ba)
    bcdedit /enum displayed: The boot configuration store could not be opened. The requested system device could not be found.
    KB4477029 installed in November failed to uninstall using remove-package error 0x800f082f
    KB4100347 installed in December was pending and had not had an attempted remove-package
    HD Tune Health (SMART) was not able to be performed on the Samsung drive
    Scannow the operation could not be performed

    Disk 0 Samsung SSD 960 EVO 500 GB is MBR

    Partition 1 Volume 0 letter E: 100 MB System reserved
    Partition 2 Volume 1 letter C: 464 GB Active
    Partition 3 Volume 4 letter F: 879 MB Hidden


    See if it is possible to uninstall the KB pending update in December, 2018.
    If this is successful then attempt again each of these steps:
    revert pending actions and scannow

    Run these commands using the Windows 10 iso and display results into the thread:
    bcdedit
    bcdedit /enum
    bcdedit /enum all
    bcdedit | find "osdevice"

    When available please display the progress with steps 8, 9, 15, 17 - 20
    Last edited by zbook; 1 Week Ago at 19:39.
      My ComputerSystem Spec

  9.    1 Week Ago #19

    Caledon Ken said: View Post
    Did it finish successfully?
    zbook said: View Post
    The images displayed the last successful Windows update 11/2018

    There was a pending update from 12/2018
    KB4100347
    https://support.microsoft.com/en-us/...windows-server

    revertpendingactions failed with error 0x000f082f
    Code:
    DISM   DISM Package Manager: PID=3584 TID=4024 The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB - CPackageManagerCLIHandler::ExecuteCmdLine
    Code:
    DISM   DISM OS Provider: PID=3584 TID=4024 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
    Code:
    DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE
    DISM   DISM Manager: PID=3908 TID=3852 Failed to get the IDismImage instance from the image session - CDISMManager::CloseImageSession(hr:0x800706ba)
    DISM   DISM.EXE:  - CDismWrapper::CloseSession(hr:0x800706ba)
    bcdedit /enum displayed: The boot configuration store could not be opened. The requested system device could not be found.
    KB4477029 installed in November failed to uninstall using remove-package error 0x800f082f
    KB4100347 installed in December was pending and had not had an attempted remove-package
    HD Tune Health (SMART) was not able to be performed on the Samsung drive
    Scannow the operation could not be performed

    Disk 0 Samsung SSD 960 EVO 500 GB is MBR

    Partition 1 Volume 0 letter E: 100 MB System reserved
    Partition 2 Volume 1 letter C: 464 GB Active
    Partition 3 Volume 4 letter F: 879 MB Hidden


    See if it is possible to uninstall the KB pending update in December, 2018.
    If this is successful then attempt again each of these steps:
    revert pending actions and scannow

    Run these commands using the Windows 10 iso and display results into the thread:
    bcdedit
    bcdedit /enum
    bcdedit /enum all
    bcdedit | find "osdevice"

    When available please display the progress with steps 8, 9, 15, 17 - 20
    Caledon ken - No. It fails. See previous details.

    Okay. So. I tried everything from rescue 1803 windows flash cmd. I suppose we need to focus on removing the pending update.

    If i try to remove pending update - i get error code 0x800f082f. This error is pritty common for most of failed dism commands i type. Pending error package name: Package_for_KB4100347-31bf3856ad364e35~amd64~~10.0.3.0

    Click image for larger version. 

Name:	error dism.jpg 
Views:	2 
Size:	2.77 MB 
ID:	223729

    Any suggestions how to remove this thing? It could be the main cause because the date is i think correct when my boot stopped.

    P.S. BCD is not recognized as i stated in previous answers.
    P.S.S. Here's a log from c: drives srttrail.txt(attachments). If it gives you some info..
    Forever boot Spinning white dots with black screen no logo 0x80000003 Attached Files
      My ComputerSystem Spec

  10. RingTailCoon's Avatar
    Posts : 706
    Windows 10 PRO
       1 Week Ago #20

    Still a-heap 'o trouble but we'll gettin' there, Sunny Jim! I'll think you're outta the woods now... Keep on pushing pushing pushing and show that PC who's boss! :)

    Or just.... well..... Throw CHROME OS or LINUX on it as a veeeeeeeery last resort. Atleast THEN you have a cooperative machine. Just my 2 cents.
      My ComputerSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast

Related Threads
When booting into Windows 10 it takes around 30-40 seconds on the Windows logo with the spinning dots loading screen. I have tried everything I know to solve these issues: Turned off fast start up Ran CCleaner Ran Diskclean up Turned off...
I just upgraded my desktop and laptop to the Windows 10 Creators Update. Everything went well and worked properly, until I installed a cumulative update and tried to reboot... Now all I get is a black screen and the spinning dots (like it's...
okay so I'm probably not posting this in the right area so I apologize if I'm not (i got a BSOD but it ain't a blue screen lol). UPDATE PT.2: ignore the first update because that didn't work. i tried resetting my computer completely, and from a...
Hello all, My computer just started doing a very weird thing. I've had Windows 10 on a Dell XPS 8100 for about 3 months now. Just recently, after it sits idle for about an hour or so, it will shut down and reboot on its own. It will go to the...
Hi guys, I know there's many threads on this subject but none seem to answer it for me. System: i7 950 X58A-UD3R Rev 2.0 16gb Ram GTX760. Pretty sure it's a Samsung 250gb SSD. So I upgraded W7 to W10 via iso. Install made it all the way.

Tags for this Thread

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:22.
Find Us