Persistent BSOD


  1. Posts : 3
    Windows 10
       #1

    Persistent BSOD


    First my apologies for not providing a log file with my post.

    I'm unable to run the tool that is provided in the Posting Instructions thread on the affected machine, because I can't get it to boot regularly, into safe mode or even into the recovery partition of the hard drive.

    The computer is a Toshiba Sattelite C850 running Windows 10 x64.

    I've made a recovery disk, and that has given me some options but the computers owner did not set any restore points, the tool to fix the drive fails returning the message that the "drive is locked" and when the computer tries to load normally it either attempts to run chkdsk and stalls halfway through or returns a BSOD with the error code 0xc0000001. It seems the only option on the recovery disk that currently works properly is the command prompt.

    Through the command prompt I've tried using fixboot to solve the problem but the BSOD persists.

    If anyone has any suggestions on how to fix the issue or how to get a log file from the command prompt for more information I'd greatly appreciate it.
      My Computer


  2. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #2

    As far as I can remember right now, two bugchecks result the error code 0xc0000001. One is INTERNAL_POWER_ERROR (0xA0)and the other is WINLOGON_FATAL_ERROR (0xC000021A).

    Your case matches with Stop 0xC000021A bugcheck; but we need to be sure. Please take a camera snap of the BSOD screen and let us see it.

    The bugcheck (stop) code will be more important than the error code.
    FlashyG said:
    the computers owner did not set any restore points,
    So you are not the owner of the computer. Asking out of curiosity, who are you then?
    Please dont take it otherwise, I am just curious.
      My Computer


  3. Posts : 3
    Windows 10
    Thread Starter
       #3

    Arc said:
    As far as I can remember right now, two bugchecks result the error code 0xc0000001. One is INTERNAL_POWER_ERROR (0xA0)and the other is WINLOGON_FATAL_ERROR (0xC000021A).

    Your case matches with Stop 0xC000021A bugcheck; but we need to be sure. Please take a camera snap of the BSOD screen and let us see it.

    The bugcheck (stop) code will be more important than the error code.
    So you are not the owner of the computer. Asking out of curiosity, who are you then?
    Please dont take it otherwise, I am just curious.
    I'm her next door neighbor. She can't afford to have the computer fixed in a shop so she asked if I would take a look at it for her.

    Normally her issues are simple but this one has been far more problematic for me.

    I managed to get it to boot. I found a utility called Farbar's recovery scan tool that ran from a USB stick in command prompt. It seemed to fix some of the problems, enough so that the recovery disk could finally run the start-up repair without crashing.

    Now that Windows is loaded I've only had minor issues like the mouse no longer being recognized as being compatible with Windows 10, and with programs like Google Chrome not loading, uninstalling or allowing me to run the installer.

    It also won't allow me to install and run the DM Log collector tool, it attempts to install then says "dm_log_collector.exe has stopped working" a problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
      My Computer


  4. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #4

    FRST might have deleted some registries which is causing the issues now.

    A clean install will be the easiest solution there.
      My Computer


 

  Related Discussions
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 22:55.
Find Us




Windows 10 Forums