STOP: 0x000000C4 after installing KB4056894 - 2018-01 Security Monthly Quality Rollup for WIndows 7 for x64

After installing the latest Windows updates and rebooting, I got the following error:

*** STOP: 0x000000C4 (0X0000000000000091, 0x0000000000000000, 0xFFFFFF80002C4EFC0, 0x0000000000000000)

I could not boot into Safe Mode. I was able to boot into the Recover Console and uninstall the latest update that was still in the "Install Pending" state by doing this:

Determine what drive letter has your windows install. There's a good chance when in you are in the Recover Console command prompt that the Windows drive letter isn't your regular "C:\". Enter a drive letter to change to that drive, could be c:, d:, e: etc. Run "dir" to check what is in that drive. Note, the recover console environment, which might be "c:" also looks like a Windows install, but it isn't your regular install. It's a special Windows image for the Recover Console. Also try checking the "Users" directory contents to see if the users in it look correct.

d:

dir

cd Users

dir

The above should list contents that look like your regular Windows root. If so then use "d:" below, if not keep checking other drive letters. Once you've found the right drive letter replace "d:" in the commands below with that drive letter.

Next, make sure you have a "temp" directory or create one with:

d:

mkdir temp

Now uninstall the bad update. Note, this works for 64 bit Windows. Run this all on one line, replacing with the correct drive letter:

dism /image:d:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24002.1.4 /norestart /scratchdir:d:\temp

Same line as above with different formatting if it's easier to read:

dism /image:d:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24002.1.4 /norestart /scratchdir:d:\temp

Reported that the 32 bit package name is: Package_for_RollupFix~31bf3856ad364e35~x86~~7601.24002.1.4

Now reboot the computer and it should boot normally.

I do not know if that RollupFix is the same a KB4056894, but after removing that package the system booted successfully. The KB4056894 update is now listed as available in Windows Update again. I'm going to avoid installing that update, but it includes the fix for the latest Spectre and Meltdown security vulnerabilities. 

The STOP code appears to match this KB2816159, but when I tried to apply the hotfix, it says:

The update is not applicable to your computer.

Is KB4056894 causing this STOP: 0x000000C4 error?

Other reports have been able to use System Restore to restore to an earlier restore point successfully, but that might fail. Just because the recovery/repair disk says a restore doesn't work does not mean that it did not work. Some users receive an error message, 0x80070002, but when they tried to boot Windows again it worked and the KB5046894 was showing as a failed update. 

For me the CPU is a dual socket motherboard with two Dual Core AMD Opteron 285 chips. 

Based on other reports, this is effecting Windows 10, Windows 7, Windows Server 2008 R2, 32-bit and 64-bit installs for all older AMD CPUs. It is not related to the anti-virus registry key issue. Many reports are running standard Microsoft Security Essentials. AMD CPUs effected include Athlon, Sempron, Opteron and Turion:

  • AMD Athlon X2 6000+
  • AMD Athlon X2 5600+
  • AMD Athlon X2 5400+
  • AMD Athlon X2 5200+
  • AMD Athlon X2 5050e
  • AMD Athlon X2 4800+
  • AMD Athlon X2 4600+
  • AMD Athlon X2 4200+
  • AMD Athlon X2 3800+
  • AMD Athlon X2 BE-2400
  • AMD Opteron 285
  • AMD Opteron 2218
  • AMD Opteron 2220
  • AMD Semprom 3400+
  • AMD Turion X

UPDATE: 2018-01-08

It's been three days now and still not knowledgement from Microsoft that this is an bug. This post has Views: 15014, Replies (56), I have the same question (445). This same error has been mentioned at the following sites:

TechNet: Blue Screen after KB4056894

Overclockers UK: Warning on KB4056894 (Intel/AMD) Fix caused Operton Bluescreen/STOP
AskWoody: Multiple reports of blue screens (BSODs) 0X000000C4 when installing the January Win7 Monthly Rollup KB 4056894

Reddit: Problems with Windows 7 Quality Rollup (KB4056894)

SevenForums: Windows 7 won't start after update on 5 Jan 2018

UPDATE: 2018-01-09

It's been four days and Microsoft has knowledged this is an bug and blocked the update for older AMD systems.

See Microsoft's official response here: 

Windows operating system security update block for some AMD based devices

Note: I unhid the update to see if it was blocked. After running "Check for updates", it is no longer showing up as a pending update for me.

 

Question Info


Last updated October 3, 2018 Views 63,283 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Glad I am not the only one seeing this issue. Spent 6 hours trying different scenarios to get this update installed on an AMD6000+ running WIndows7 x64 Ultimate.  The error message I received was the same as yours except 

*** STOP: 0x000000C4 (0X0000000000000091, 0x0000000000000000, 0xFFFFFF8000360AFCO, 0x0000000000000000)

On some of these scenarios simply  booting with Windows7 recovery disc rolled back the update. Sometimes I had to restore restore points. On the last attempt I had to restore an image backup as the system would not boot up properly.

I have Intel based systems here take this update with no issues. The antivirus on the problem system is NOD32 Endpoint Antivirus 6.6.2052.0:

Detection Engine: 16689 (20180105)
Rapid Response module: 11375 (20180105)
Update module: 1010 (20170621)
Antivirus and antispyware scanner module: 1533.3 (20180104)
Advanced heuristics module: 1184.1 (20171212)
Archive support module: 1270 (20171113)
Cleaner module: 1152 (20171127)
Anti-Stealth support module: 1118 (20171108)
ESET SysInspector module: 1270 (20170808)
Translation support module: 1638 (20171018)
HIPS support module: 1309 (20171229)
Internet protection module: 1315.1 (20171214)
Database module: 1095 (20171206)
Configuration module (33): 1525.5 (20170904)
LiveGrid communication module: 1041 (20171107)
Specialized cleaner module: 1012 (20160405)
Rootkit detection and cleaning module: 1019 (20170825)
Network protection module: 1585 (20180105)
Script scanner module: 1027 (20171227)
Cryptographic protocol support module: 1025 (20171106)

According to Eset the highlighted line is what supposedly has been tested against this update and is deemed compatible,

P.S. I also tried applying that hotfix as well and like you I was told it was not applicable.

11 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same issue for me on HP DL385G2 running Windows 2008R2 (otherwise fully patched) and with 2 x AMD Operton CPUs

Wish I'd found your cmd line sooner as took me 2 to 3 hours at recovery command console to work that out after Safe Mode, DSRM, Last Known Good Configuration all failed to get the DC/Exchange server back online

In my case the Windows drive was e: when in recovery console command prompt

dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24002.1.4 /scratchdir:e:\temp

Microsoft, I think you need to withdraw this update for AMD Opertons as clearly its not tested properly

27 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I agree more testing is required when applying this update to systems with AMD CPUs. 

There is a thread on Reddit regarding this issue https://www.reddit.com/r/sysadmin/comments/7ode4s/problems_with_windows_7_quality_rollup_kb4056894/

9 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Lost my whole morning this this one. Glad I'm not the only one. Looks like it's not just Opterons, but also older Athlons too:

Windows 7 Update of 1/5/2018 fails w/ AMD Athlon X2

5 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

the athlon 64 x2 4600+ processor. I tried to fix the error with the update. in the end I decided not to install it. (I'm sorry, I was from Russia.) I translated Google as an interpreter)

5 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

5 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same problem as noted above on a family PC with AMD Athlon Dual Core 4400+ chip. BSOD Stop error 0x000000c4....   

Got lucky however.   I booted into System Recovery and tried a System Restore.  Chose a restore point of 1/1/2018.  Restore failed for "unknown reason".  However, I then rebooted and hit F8 and chose "Last Known Good Configuration" and successfully booted.  It appears that doing this forced the System Restore to take.  Thus I suspect the initial Restore failure is due to some kind of permissions issue.

At any rate, KB4056894 is hereby BANNED.  Microsoft, get your s***t together.

28 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Seeing a similar problem on my Athlon X2 3800+ machine.  Instead of a bluescreen, on reboot after the update installs, I see the normal "starting Windows" screen.  However, instead of seeing the morphing Windows flag in the center of the screen after a few seconds, nothing happens.  Waited 20 minutes, saw no video or hard drive activity.  Pressing the reset button on my PC allowed me to do the repair option and go back to the last restore point.

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same problem with AMD Turion x2 Dual-Core Mobile

Was able to recover by using System Restore and restore point just prior to KB4056894 install.

Hid KB4056894 and will wait for Microsoft solution to problem.

9 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I got the same error on my PC with AMD Athlon 64 X2 5600+

Recovery to previous restore point performs succesfully, but  KB4056894 still wants to come again (

So, its temporary disabled.

7 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.