"Couldn't update to Windows 8.1 - 0xC1900101 - 0x40017"

OK after trying with the new update, I tried this process a second time, still no joy, same failure, same error code and a virtually identical memory dump.

My thoughts are also that it is a driver problem, but I think Microsoft could design the system to recover from the failure with less obscure reporting of the cause.   It should report which driver caused the problem.  Further I am a little confused as to how an incremental upgrade could render a previously working driver so "buggy" that it throws a BSOD.  While the problem might be 3rd party vendors, the OS should be able to handle errors in such a fashion as to allow the user to pursue solutions instead of throwing obscure error codes with no reference as to whet they really are reporting.

I also found a new update, labeled as "important", installed it but no joy.  Same failure as before with the same error code.  I installed the MS SDK do I could read the memory dump from the BSOD - following is that dump.

Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Only kernel address space is available

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 8 Kernel Version 9200 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9200.16628.amd64fre.win8_gdr.130531-1504

Machine Name:

Kernel base = 0xfffff8011126d000 PsLoadedModuleList = 0xfffff80111539a20

Debug session time: Thu Aug  1 10:16:59.067 2013 (UTC - 6:00)

System Uptime: 2 days 15:09:44.429

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.......

Loading User Symbols

Loading unloaded module list

..................................................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61946, fffffa80414c9ce0, 1bf8be, 0}

*** ERROR: Module load completed but symbols could not be loaded for VClone.sys

Page f5926b not present in the dump file. Type ".hh dbgerr004" for details

Probably caused by : rdbss.sys ( rdbss!RxLockUserBuffer+64 )

Followup: MachineOwner

---

1: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

    # Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000061946, The subtype of the bugcheck.

Arg2: fffffa80414c9ce0

Arg3: 00000000001bf8be

Arg4: 0000000000000000

Debugging Details:

---

Page f5926b not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR:  0x1a_61946

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from fffff8011144ed7d to fffff801112c7440

STACK_TEXT: 

fffff8800ca13f08 fffff8011144ed7d : 000000000000001a 0000000000061946 fffffa80414c9ce0 00000000001bf8be : nt!KeBugCheckEx

fffff8800ca13f10 fffff80111326d51 : 0000000000000000 fffff8800ca13fc9 fffffa803951bb00 fffffa80414c9d10 : nt! ?? ::FNODOBFM::`string'+0x1ee9f

fffff8800ca13f70 fffff8800af1d0e8 : fffffa8039adb3d8 fffffa803cecbc00 fffffa8039adb2c0 0000000000001000 : nt!MmProbeAndLockPages+0x161

fffff8800ca14030 fffff8800af1cc1f : fffffa803cecbcb0 fffffa8039adb2c0 fffffa803cecbcb0 fffff801112f8ee0 : rdbss!RxLockUserBuffer+0x64

fffff8800ca14090 fffff8800af21809 : fffffa803cecbcb0 fffffa8041dc0070 fffffa8039adb2c0 fffff8a018deaa10 : rdbss!RxLowIoSubmit+0xaf

fffff8800ca14100 fffff8800aede662 : fffffa803cecbcb0 fffffa804013d3a0 fffffa803cecbcb0 0000000000000000 : rdbss!RxCommonRead+0x4b9

fffff8800ca14230 fffff8800af1059b : fffffa803c2eee28 fffffa803c2eee90 fffff88004c591c8 fffffa803c2eee70 : rdbss!RxFsdCommonDispatch+0x522

fffff8800ca14390 fffff8802465c09c : 0000000000000000 fffffa8039adb2c0 fffffa804013d3a0 0000000000000000 : rdbss!RxFsdDispatch+0xcb

fffff8800ca143f0 fffff88004c5b1ef : fffffa803c2eedf0 fffffa8039adb2c0 fffffa8041dc0070 00000000c0000016 : mrxsmb!MRxSmbFsdDispatch+0x8c

fffff8800ca14430 fffff880047214ee : 0000000000000000 fffff88004720a00 fffff8a0003c65a0 0000000000000003 : mup!MupFsdIrpPassThrough+0x1df

fffff8800ca144a0 fffff8800471f0b6 : fffffa80337ae9c0 fffffa8041dc0070 fffffa8039adb2c0 fffffa803951bed0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25e

fffff8800ca14540 fffff801116d8868 : 0000000000000000 fffff8800ca14621 fffffa8041dc0070 fffff80100000003 : fltmgr!FltpDispatch+0xb6

fffff8800ca145a0 fffff80111708513 : fffffa8041dc0004 fffffa8041dc00c0 000000000000002f fffffa8041dc0070 : nt!IopSynchronousServiceTail+0x158

fffff8800ca14670 fffff801112c6453 : fffff88005d54f00 0000000000000000 0000000000000000 0000000000000000 : nt!NtReadFile+0x661

fffff8800ca14770 fffff801112cb630 : fffff8800c754637 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13

fffff8800ca14978 fffff8800c754637 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiServiceLinkage

fffff8800ca14980 fffff8800c754c53 : 0000000000090000 fffff8800ca14ac0 fffff8800ca14b30 0000000000000000 : VClone+0x4637

fffff8800ca14a10 fffff8800c754ee7 : fffff8802994aa10 0000000000000002 fffffa803076a100 0000000000000001 : VClone+0x4c53

fffff8800ca14a50 fffff8800c75343e : fffff8802994aa03 fffff8011130960f fffffa803076a1b8 fffffa803076a160 : VClone+0x4ee7

fffff8800ca14ac0 fffff8800c7542b4 : fffffa8000000000 fffffa803076a100 0000000000000000 fffffa803076a100 : VClone+0x343e

fffff8800ca14b30 fffff8800c75197a : fffff8802994aa10 fffffa8030618f40 fffffa803076a208 fffffa803076a100 : VClone+0x42b4

fffff8800ca14b60 fffff80111299fd9 : fffff80111565180 fffff801112c1605 fffffa803951bb00 00000000022bbef5 : VClone+0x197a

fffff8800ca14c10 fffff8011134e7e6 : fffff80111565180 fffffa803951bb00 fffff801115bf880 fffffa80304c9940 : nt!PspSystemThreadStartup+0x59

fffff8800ca14c60 0000000000000000 : fffff8800ca15000 fffff8800ca0f000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

FOLLOWUP_IP:

rdbss!RxLockUserBuffer+64

fffff8800af1d0e8 eb46            jmp     rdbss!RxLockUserBuffer+0xa9 (fffff8800af1d130)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  rdbss!RxLockUserBuffer+64

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdbss

IMAGE_NAME:  rdbss.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  518492c4

BUCKET_ID_FUNC_OFFSET:  64

FAILURE_BUCKET_ID:  0x1a_61946_rdbss!RxLockUserBuffer

BUCKET_ID:  0x1a_61946_rdbss!RxLockUserBuffer

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_61946_rdbss!rxlockuserbuffer

FAILURE_ID_HASH:  {e4c8e040-8113-e4f7-985d-1d2a2c676607}

Followup: MachineOwner

---

In the last try, I removed all graphic card drivers (intel and nvidia) and the related software,  before reboot, I start upgrade windows 8.1, as soon as the system finished downloading from windows store and in the 'gather info' stage, I quickly removed the entire software and driver for network ( I can't do this before upgrade cuz I need it to connect to windows store), and the rest of upgrade went through without any issue.

With much credit to homerli's comments, I was able to get 8.1 installed on my machine last night.  I followed the steps he described but with a slight modification, likely due to specifics of my computer.

First, I uninstalled my graphics drivers.  I have an AMD and Intel card for switchable graphics, but only the Intel card has been functioning.  I disabled the Intel card and rebooted, into the generic Microsoft display drivers.  The resolution was poor, but sufficient for what I was trying to do.

Next, I started the 8.1 Pro install.  From previous tries, I didn't have to wait for the download again and it went straight into installation.  From homerli's experience he removed his network drivers at the "Gathering Info" stage, but on my machine, doing that paused the install since it cuts off my internet connection.  So I waited until it was ready to restart before uninstalling network drivers. 

Upon reboot, it got through the initial setup stage, and the second reboot at Getting Devices Ready was usually the end of my install in the past.  This time, it went all the way through, and a few minutes later I had a working install of 8.1 Pro.  My Intel graphics driver was still the only one active, and my AMD driver was replaced in Device Manager with a Microsoft Display Driver which was inactive, but no matter.  Only hiccup left was my network card, which I had seen from other commenters in this thread was an issue.  I went to HP to download the drivers they provided for my card, to no avail.  I had to go to Intel's site to get the latest 8.1 drivers for my card, which upon installing, connected me to the Web.  SUCCESS!

I'll echo other's comments by saying this is a painstakingly ridiculous trial and error process when it shouldn't be.  Microsoft providing a compatibility tool prior to install would probably alleviate many of these problems.  The "Checking compatibility" step in the install clearly isn't checking for the things that caused mine or other problems.  In the end, I still don't know if it was the network or graphics drivers which was the problem, but uninstalling both, at the right time, seemed to do the trick.  Additionally, I don't know what to expect from Microsoft as far as a fix for this.  I might be of a minority opinion here, but perhaps the blame should be on OEMs and driver manufacturers for not pushing updates to drivers through Windows Update in time for the 8.1 launch.  If the install worked on my two other desktops without an issue, and then worked on mine after disabling drivers, clearly the problem isn't in the 8.1 code, but in the hardware drivers.  But again, my opinion is my own.  I still think it's ridiculous I had to spend the better part of a week, not to mention nuking my Windows install, to get this far. 

Best of luck to the rest of you still trying.

I have quite similiar issue but a little different.

I tried to upgrade my father's laptop which was originally intended for Windows 7. The laptop is old - it is Asus K72JK-TY001V. Yes, I know, Microsoft and Asus will tell me the eight is not for this device and go away. Well, from my short experience Windows 8 works flawless anyway.

When I tried to upgrade to 8.1 - I admit, I didn't install all drivers and not even one update from Windows Updates - I'll try that today. Coming back to the topic - installation goes veeery smoothly until last part -> "Preparing PC" (it may say something else, I have polish language pack). It's after devices and all. I get no bluescreen, it just freezes after a minute and that's it. After restart it goes back to previous Windows Version and shows me same error screen as everybody's here. I don't get blue screen though.

If Windows Update and drivers won't help, I might as well buy Macbook next time, seeing how even 2007 devices get newest OS (it's like Vista for us) and for free.

Just today tried to upgrade from Win 8 to 8.1 and encountered the same error everyone else is. Looks as though nobody has it figured out though. The above "Announcement" seems only relevant to Windows RT devices. Where's the workable update for the desk/laptop users? It HAS been a few days...