Core ReactOS
  1. Core ReactOS
  2. CORE-12646

BSOD after a restart with vbox additions cd inserted

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Hello,
      I tried to install vbox additions under reactos. It works BUT after a restart, reactos gave me a bsod. I can't log vbox because I haven't got admin privileges on pc.
      Build number: 73519
      Then at the Freeloader selection, I selected ReactOS (Screen).
      Output:
      SMSS:PFILE: Open Volume ??\D:\ failed with status c0000013.
      Boot took 2342000088 Cycles
      Interrupts: 1000 System Calls: 17055 ...
      (you can find this log in image)

        Activity

        Hide
        Jared Smudde
        added a comment -

        You somehow corrupted the registry. Try reinstalling ReactOS.

        Show
        Jared Smudde
        added a comment - You somehow corrupted the registry. Try reinstalling ReactOS.
        Hide
        HBelusca
        added a comment -

        !error 0xc0000130
        <+hTechBot> 0xc0000130 is STATUS_INVALID_IMAGE_PROTECT.
        !error 0xc0000013
        <+hTechBot> 0xc0000013 is STATUS_NO_MEDIA_IN_DEVICE.

        Show
        HBelusca
        added a comment - !error 0xc0000130 <+hTechBot> 0xc0000130 is STATUS_INVALID_IMAGE_PROTECT. !error 0xc0000013 <+hTechBot> 0xc0000013 is STATUS_NO_MEDIA_IN_DEVICE.
        Hide
        Riccardo Montanari
        added a comment -

        Jared Smudde maybe the installation of Virtualbox additions corrupted registry

        Show
        Riccardo Montanari
        added a comment - Jared Smudde maybe the installation of Virtualbox additions corrupted registry
        Hide
        Jared Smudde
        added a comment -

        I doubt it. You probably just closed the vm or rebooted without using the start menu options.

        Show
        Jared Smudde
        added a comment - I doubt it. You probably just closed the vm or rebooted without using the start menu options.
        Hide
        Riccardo Montanari
        added a comment -

        Jared, you are right. I didn't reboot with using the start menu options (sometimes it worked, I think there is a bug on start menu options). Close as a Won't fix ?

        Show
        Riccardo Montanari
        added a comment - Jared, you are right. I didn't reboot with using the start menu options (sometimes it worked, I think there is a bug on start menu options). Close as a Won't fix ?

          People

          • Assignee:
            Bug Zilla
            Reporter:
            Riccardo Montanari
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: