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

Warning!  VERY LONG

I hope this helps someone.  I successfully updated a DELL XPS12 without issue other than it needing a new touchpad driver to restore touchpad operation.  I then updated my secondary computer, a dual boot Win7/Win 8 machine based upon an Intel 6 series chipset motherboard with an AMD graphics card.  Smooth upgrade no issue. 

My third machine has failed to update despite 15-20 different attempts based upon answers in this forum and others.  While I have not resolved the issue, I do have some new data.  Here are the most relevant hardware items in my system:

·         Intel DX79SR motherboard

·         Samsung 840 pro 500 GB SSD Boot drive

·         Dual Nvidia 660 GT graphics cards

·         Two secondary HDD, but all O/S files and folders are on the SSD (“C:” drive)

I started with the error 0xC1900101 - 0x20017on October 17.  Each successive try resulted in the same pattern – the Windows 8 update would download from the store or already have been downloaded.  It would go through all the primary steps to the point where it asks to restart the system, followed by an immediate BSOD, restart and the message:

"Couldn't update to Windows 8.1

Sorry, we couldn't complete the update to Windows 8.1. We've restored your previous version of Windows to this PC.

0xC1900101 - 0x20017"

This message would always be immediately after the first reboot.

The steps I tried and sometimes retried:

·         Cleaned out the store cache

·         Ran DISM to repair system files that were listed as corrupted after running sfc /scannow

·         Removed Nvidia drivers and tried the install without reboot

·         Removed or disabled network devices just prior to reboot

·         Ran chkdsk /r

·         Removed Intel Desktop utilities

·         Removed Intel Rapid Storage Technology drivers

·         Physically removed all hard drives other than the system drive

·         Physically removed one of the two Nvidia cards and again uninstalled the driver

·         Removed all peripheral USB devices and used only a generic USB keyboard and mouse

·         Installed the newest Nvidia graphics drivers as of 10/23/13 (331.58)

None of these things changed the pattern of failure at all.

Today I attempted a couple of other things I had discovered.  I found a firmware update for the Samsung SSD dated last May.  When trying to update the firmware through the Samsung Magician software it would fail.  To resolve that issue I found I needed to check that the IDE ATA/ATAPI driver was the generic Microsoft SATA ACHI driver.  What was there was the Intel drivers installed by the Rapid Storage Technology installation, despite the fact that it was uninstalled.  I reverted to the Microsoft Standard drivers and was able to successfully update the SSD firmware.  I also found some new (beta) Nvidia graphics drivers released yesterday.  After updating those drivers I deleted the $Windows~BT folder and ran WSReset.exe.  I rebooted the computer and began the update again.  This time the results were significantly different.  After rebooting the machine it actually began the full update process without the BSOD.  It:

• Setting up to 100%
• Restart
• Getting Devices ready to 100%
• Getting Ready to 100%
• Applying PC Settings to 100%
• Restart
• Then BSOD
• Attempting to Recover
• BSOD
• Restoring your Previous
• Restart

 Then got the blue bar stating:

"Couldn't update to Windows 8.1

Sorry, we couldn't complete the update to Windows 8.1. We've restored your previous version of Windows to this PC.

0xC1900101 - 0x40017"

Note that the error code is now different and it made it trough a lot more steps and restarts than it had prior to today.  Additionally the memory dump file was completely different than it had been each time before.  Please note that this is the last of three memory dump files – I don’t know what the first two were. 

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

*                                                                                                                     *

*                        Bugcheck Analysis                                                                *

*                                                                                                                      *

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

KERNEL_DATA_INPAGE_ERROR (7a)

The requested page of kernel data could not be read in.  Typically caused by

a bad block in the paging file or disk controller error. Also see

KERNEL_STACK_INPAGE_ERROR.

If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,

it means the disk subsystem has experienced a failure.

If the error status is 0xC000009A, then it means the request failed because

a filesystem failed to make forward progress.

Arguments:

Arg1: fffff6fc500834b0, lock type that was held (value 1,2,3, or PTE address)

Arg2: ffffffffc0000010, error status (normally i/o status code)

Arg3: 0000000198eb6880, current process (virtual address for lock type 3, or PTE)

Arg4: fffff8a010696000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:

---

ERROR_CODE: (NTSTATUS) 0xc0000010 - The specified request is not a valid operation for the target device.

BUGCHECK_STR:  0x7a_c0000010

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff803203861d6 to fffff803202cb440

……..

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+24e14

fffff803`203861d6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+24e14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd

IMAGE_VERSION:  6.2.9200.16628

BUCKET_ID_FUNC_OFFSET:  24e14

FAILURE_BUCKET_ID:  0x7a_c0000010_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x7a_c0000010_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_c0000010_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {a752d1bb-6e8d-ecad-e2a8-47b334636a53}

This dump now indicated it might be due to “a bad block in the paging file or disk controller”, which had never been shown before.  The only relevant change I made was going to the Microsoft Standard ACHI driver. 

I’m still unable to update, but took three or four steps forward before reverting to Win 8.  This attempt was made with all video cards, hard drives, peripherals and network drivers installed with their proper drivers.  Perhaps this failure is either the disc controller driver or related to the SSD.

Typo error.

I am now back on 8.0

There is no way that I will risk trying 8.1 again as I thought that the upgrade had killed by SSM (256GB and only a few months old).

Very clearly this upgrade is not yet ready for release.

Bill

I will report on my call tomorrow from level II MS tech rep... I simply worry that the SSD may be damaged in the update process... oooppps MS may say, Intel could care less, and I'm out the replacement for the SSD which was MUCH faster at booting / restarting the machine.

Thanks for the reply... but, I don't quite understand your status... operating on 8.0 or 8.1 now?

Thanks for the tip... I have the Paragon Alignment tool installed and just spoke with their tech guy who urged me to buy the HD Mgr Suite for $50 rather than the migrate tool only... they do offer a 30 day guarantee.

I suspect I must prep the SSD in order for the migrate software to clone over the now operating 8.1 OS from my HDD.  I have wiped the SSD 3x but the Intel software refuses to "secure erase" the SSD which is the step the Intel tech rep said was necessary for their software to function.  He referred me to:  http://www.hdat2.com/  and said that was all Intel could do for me... I attempted to understand how to install/operate their program, which requires creating a disc to boot to DOS and run the program from DOS...  beyond my skill level...

The Paragon tech rep said that their suite will prep and clone the OS and I expect I will spend the extra $30 to give it a whirl... thanks Micros...s

Hi Dave

Well in the end I gave up with 8.1

It was necessary to re-format the SSD.  That was not very easy as the Samsung software would no longer access the drive to re-format it.  I had to use Ubuntu (or something like that) to boot the PC and re-partition the SSD.

Now at least I am back to W 8.1 and as I keep almost all my data on a NAS, I really just lost time.

Do I now try upgrading to 8.1 again - I don't think so.

Bill