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

Anonymous

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.

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

Anonymous

2013-10-20T04:24:12+00:00

i am also having this issue with a Q6700 processor and nvidia 750i SLI chipset (core 2 quad on asus p5n-d mobo)

also running Q6600 and nvidia 780sli....

Found the following in Windowsupdate.log

2013-10-18 20:48:31:178 904 ea4 Driver Matched driver to device PCI\VEN_10DE&DEV_0272&SUBSYS_73801462&REV_A3

2013-10-18 20:48:31:178 904 ea4 Driver Status: 0x1802000, ProblemNumber: 00000000

2013-10-18 20:48:31:178 904 ea4 Driver Matched driver to device PCI\VEN_10DE&DEV_0270&SUBSYS_73801462&REV_A2

2013-10-18 20:48:31:178 904 ea4 Driver Status: 0x1802000, ProblemNumber: 00000000

This device is the nForce Memory Controller

I checked nVidia's site...and found the following:

>>>>Driver support for NVIDIA® nForce ™ motherboard chipsets and their components have been >>>>moved to legacy support. NVIDIA nForce products will not be supported for Windows 8 and later >>>Windows operating systems.

Not a promising sign....
Was this answer helpful?

0 comments No comments
Anonymous

2013-10-19T22:35:06+00:00

i am also having this issue with a Q6700 processor and nvidia 750i SLI chipset (core 2 quad on asus p5n-d mobo)
Was this answer helpful?

0 comments No comments
Anonymous

2013-10-19T21:17:59+00:00

For what it's worth, I also run a Q6600, 4GB RAM, 64-bit OS, and an nVidia video card, although mine's much older than yours (GTX 280 running v. 327.23)

I've got 780 mobo chipset (evga ftw series). But my video card is even older - 8600gt :) (nvidia of course). I run dual monitor setup. It seems like there're many nvidia rigs here (!?).

First they eliminate start button and booting into a desktop (thank God there is classic shell ). Then they make us use their store (why isn't it a KB?) And now it doesn't work at all :( Where are you going Microsoft? I sometimes feel like in good, old times of win98 when making OS work was a bit of magic. And I thought I would have to change my job after win7. So on the other hand - thank you Microsoft :)

P.S. I can present a lot of further details concerning my rig and my software, but unless somebody from microsoft enlighten us where the problem really lies, we're like drunken kids in the fog.

edit: in the other thread i found somebody having the same problem with unspecified quad core processor. Is the quad core the cause? If only I didn't have to download again all the 3 gigs of data everytime I want to check something :(
Was this answer helpful?

0 comments No comments
Anonymous

2013-10-19T20:17:57+00:00

...Mines a Q6600 also, 3GB with a Nvidia Geforce 9600 GS card.. 327.23 driver.... common theme with the Q6600 / Nvidia kit appearing here....

Yeah, I suppose I should mention I also have the Q6600 and Nvidia nForce 680i mobo. With a GTX 460 graphics card.

Lots of Q66's with nvidia boards or GPUs.
Was this answer helpful?

0 comments No comments
Anonymous

2013-10-19T20:03:33+00:00

...Mines a Q6600 also, 3GB with a Nvidia Geforce 9600 GS card.. 327.23 driver.... common theme with the Q6600 / Nvidia kit appearing here....
Was this answer helpful?

0 comments No comments