Skip to main content

Windows 8.1 Causing BSOD When Creating Ramdisk

Softpedia is apparently trolling the Microsoft Community Forums looking for Windows 8.1 issues, as the site has come across another issue regarding ramdisk creation and the new Windows update. Previously,- the site discovered forum threads regarding Windows 8.1 locking up, forcing users to reboot or turn the PC off completely and restarting (to clear the memory).

"When I attempt to install Windows 8.1 on my machine from the Windows Store, on boot I receive a blue screen," reads the latest complaint on Microsoft's forum. "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."

Microsoft responded by saying the error is caused by a driver bug check during boot, and that Windows 8.1 users should make sure that all drivers have been updated. If not, users should update all drivers and then check to see if the ramdrive issue persists. But Windows 8.1 customers are flooding the thread with complaints that the provided generic solution does not work.

"I have the same issue. No partitioning, no encryption, drivers up to date, all Windows 8 Pro updates applied. The only issue I can imagine is my BIOS somehow? Updating from Windows 7 to Windows 8 was a dream, so the 8.1 install errors make no sense to me," reads one complaint.

"Checking the update log it keeps referring to this failure: 2013-10-18 23:17:24:447 524 b48 Report REPORT EVENT: {1BD27D22-671F-4B62-8D37-8965A190C2E3} 2013-10-18 23:17:24:353+0100 1 204 [AGENT_INSTALLING_FAILED_POST_REBOOT] 101 {4B0CE879-D94C-4D6D-AAEA-43CC722D6D02} 1 c1900101 WSAcquisition Failure Content Install Installation Failure Post Reboot. So I assume the update is trying to do something at reboot level and BIOS is causing a problem?" reads another.

The issue, it seems, partially revolves around the Intel Core 2 Quad Q6600 processor and Nvidia nForce-based motherboards. One user provides a list of instructions that "refreshed" his Windows 8.1 install while keeping settings and apps, but this didn't work for many still plagued with the ramdisk problem.

"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," another post reads.

One user suggests uninstalling the Rapid Storage Driver first (which is a chipset driver for the hard drive controller), then run 8.1 update again. Unfortunately, by the end of the thread, Microsoft hasn't added any additional comments or suggestions, leaving many fending for themselves or waiting for an official fix via update.

If additional information is released by Microsoft, we'll let you know.

  • killerclick
    At least it has a sad emoticon. Development time well spent.
    Reply
  • Bloob
    Win 8 also seems to have problems with dual booting.

    edit: also, I could not install 8.1 before removing my WLAN card.
    Reply
  • therogerwilco
    Zero problems here, even using a ramdisk via XfastRam with my ASrock board... otherwise 4770k and a 780..
    Reply
  • Pinhedd
    NForce motherboards... why am I not surprised in the slightest?
    Reply
  • therealduckofdeath
    These articles you're starting now, writing about single users with individual problems and actually writing messed up advice on top of that are, bizarre. I mean, this site is supposed to be somewhat for the tech savvy readers? Still you write that this odd issue that you've managed to dig up appears to affect Nvidia chipsets. Still you write about an advice to uninstall Intel chipset drivers?

    How about troubleshoot your writing first? :)
    Reply
  • Pinhedd
    NForce motherboards... why am I not surprised in the slightest?
    Reply
  • monkeycmonkeydu
    "Seems like we are in a position where for some reason Microsoft is not responding to this issue here."

    Yeah that's not unusual, us poor Windows 7 saps are still waiting on them to fix their black screen media center issue only 5 years later...
    Reply
  • nforce4max
    Just stay with 7 and be thankful that nothing needs fixing. Even vista has fewer issues despite being a hog.
    Reply
  • slyu9213
    I did a clean install of Windows 8 just for the hope that Windows 8.1 will install successfully this time around. Last time it had so many errors before the install was even successful. This time the only things installed are drivers and programs/apps that came with Windows 8. Better work or Microsoft has a ton of work to do.
    Reply
  • jimmysmitty
    11869910 said:
    NForce motherboards... why am I not surprised in the slightest?

    nForce wasn't bad but the equivalent Intel chipsets were better.

    I am not surprised its having issues either. The last time NVidia made a chipset for Intel was 2008, 5 years ago. The hardware is out of date.

    11870694 said:
    Just stay with 7 and be thankful that nothing needs fixing. Even vista has fewer issues despite being a hog.

    Yea, 7 still has a few issues. It had less than most other OSes but it still has issues, hence why there are patches still coming out fixing those issues. SP1 had issues installing for some people too.

    And Vista? Really? Vista had a lot of issues. Its not even a OS that was popular enough to matter. I had it and was fine with it but compared to 8, Vista is pretty bad.

    And I am not surprised at the issues. Most people don't maintain their systems and drivers at all.
    Reply