Windows 8.1 install - unable to create ramdisk - 0xc1900101-0x20017

Anonymous
2013-10-18T03:27:57+00:00

When I attempt to install Windows 8.1 on my machine from the Windows Store, on boot I receive a blue screen. The error message indicates that the system was unable to create a ramdisk and shows error number 0xc1900101.

On reboot, it restores my original installation and provides the following error code: 0xc1900101-0x20017.

In reading some other topics, it seems drivers may need to be updated, but as far as I know I am up-to-date. Is there a way to identify which driver had a failure?

Also, on other threads with this code, I see no mention of a "ramdisk". Is that a unique problem?

Thanks in advance for the help!

Edit: Let me note my system has no ramdisk software installed whatsoever.

Windows for home | Previous Windows versions | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

89 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-10-26T16:28:51+00:00

    Seems like only first posts in the thread  are answered by microsft staff on this forum. Most of them are generic as I have discovered reading many of them. "Check your antivirus, third party software blah, blah. Check your Pm" and so on.

    I'm afraid no one is investigating problem seriously. Been through this myself before: 780SLI chipset on asus deluxe board - problems with ever present blue screens, six or seven versions of bios, no support from asus (finally had to swap for evga). You have to see to believe how much hate can be poured on asus on what is basically official asus support forum :)

    Then no support for midi/game port on creative audigy. Microsoft said its creative drivers, creative... well, didn't say much  (left as is although windows keeps nagging me about unresolved problem).

    Question is where to go. Have you got any ideas? I don't want to and don't have time to go to every hardware forum on the net crying about how bad microsoft is. And on most of them you would meet folks claiming they have resolved this issue by touching their left toe while keeping the power button on and scratching their empty memory banks or erase everything and start from the point blank.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-10-26T12:53:28+00:00

    I am having same problem. SLi790 on a ROG motherboard. All drivers etc. up to date - 100gb of space on SSD and 8gb Ram. Very frustrating.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-10-26T11:45:20+00:00

    so how pervasive is this problem i wonder?  Does anyone have any information outside of this thread they can point me to?

    Seems like we are in a position where for some reason Microsoft is not responding to this issue here,

    Is there an official response that says nForce chipset based systems are no longer supported under windows 8.1 from Microsoft? I don't even know if that is the root of our issues, or if it is combined with some other factor introduced with 8.1 that we can manage somehow...

    Is there a different channel we should introduce this issue through MS?

    I am not sure many folks know about this issue. I think we all need to start posting in other non Microsoft forums and raise awareness to the larger community, and look to them for help. I think people are lumping the issues together to make it seem as if it is singular in nature, and therefore not much noise is being generated.  We need to get outside this box, and enlist the help of the community to put some pressure here...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-10-26T11:06:06+00:00

    Same issues as many above & elsewhere. if Private Message alluded to in some earlier Microsoft responses includes more tools/more info. then could this be made more generally available, Microsoft?

    MD

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-10-26T09:56:53+00:00

    Hi Termic,

     

    This is caused by a driver bug check during boot. Make sure all drivers have been updated.

     

    I would suggest you to update the all driver and check.

     

    I would also suggest you to check Private Message for more information.

     

    Hope this information is helpful. Please do let us know if you need further assistance, we’ll be glad to assist you.

    Hello Microsoft

    I am having the same issue. All drivers are up to date, any help will be grately appreciated.

    Many Thanks

    B

    Was this answer helpful?

    0 comments