Search results

  1. DigitalPig

    W10 Pro: Initially BSOD, now won't load at all

    SrtTrail.txt does indeed list System Disk as empty, and the root cause as: A harddisk could not be found.
  2. DigitalPig

    W10 Pro: Initially BSOD, now won't load at all

    Can't specify /f without /s, and unfortunately that didn't work. When I use bcdboot the response is: Boot files successfully created, but then on reboot I find myself back at the same screen which states something along the lines of: Device or resource is not found or not accessible. Whatever...
  3. DigitalPig

    W10 Pro: Initially BSOD, now won't load at all

    Boot Manager does not show a drive assignment, but does show a device of HarddiskVolume5, which I'm sure is F. Boot Loader does show as F. Should I make that assumption or should I check some other way? Image attached showing values.
  4. DigitalPig

    W10 Pro: Initially BSOD, now won't load at all

    Thanks, I do have a UEFI boot system. If I run bcdedit /enum ACTIVE it returns with Windows Boot Manager and Windows Boot Loader. However, when I run bootrec /rebuildbcd it doesn't find any Windows installations.
  5. DigitalPig

    W10 Pro: Initially BSOD, now won't load at all

    So if I boot into the repair procedure and get to a command prompt, then check out the C drive, it is actually my D drive, and all my other drives are mislabeled, with my C drive actually listed as my F drive. I'm not sure if that's really even an issue or just because it's in the repair...
  6. DigitalPig

    W10 Pro: Initially BSOD, now won't load at all

    Hey guys, First of all, thanks for any help that you may send my way...it's been a very frustrating day. Everything was fine with my PC until last night when it suddenly crashed with BSOD. After a restart all was fine but it was running really slow on start, ten another BSOD. It was dinner time...
Top