FYI - Win10 Sept 2016 / Oct 2016 Cumulative Update Fix

[Dahak]

If anyone is having issues with installing the KB 3194496(Sept) or the latest KB3192440 (Oct) cumulative updates MS has released a fix for it https://www.microsoft.com/en-us/download/details.aspx?id=53942

What happens is after the reboot it will get to about 30% or so and then roll back.
The issue seems to affect primarily people who where on a Insider Build and then reverted back to the production build when Anniversary Update(1607) was released

But if someone is having the issue could not hurt to try it


source: https://www.thurrott.com/windows/windows-10/82741/microsoft-fixes-borked-windows-10-update

 

[BonzaiDuck]

If anyone is having issues with installing the KB 3194496(Sept) or the latest KB3192440 (Oct) cumulative updates MS has released a fix for it https://www.microsoft.com/en-us/download/details.aspx?id=53942

What happens is after the reboot it will get to about 30% or so and then roll back.
The issue seems to affect primarily people who where on a Insider Build and then reverted back to the production build when Anniversary Update(1607) was released

But if someone is having the issue could not hurt to try it


source: https://www.thurrott.com/windows/windows-10/82741/microsoft-fixes-borked-windows-10-update

I'm about to post a new thread concerning a very solid running-gaming-working-sleeping-hibernating-waking system with 2x GTX 970 in SLI. And it was overclocked -- the 2700K in my sig well-within the best wisdom of the SB enthusiast community for voltage and speed. The RAM -- 20 GB G.SKILL DDR3-1866 9-10-9-28 -- was run at spec, had all passed 500% HCI Memtest64 when I augmented the 16GB 2x8 kit about three months ago. It's now running at stock speeds, and I'm running HCI Memtest again -- just to rule out hardware.

Suddenly, and at first with the Win 7 system only, it acted as if the boot disk was corrupted. But the boot disk, for the testing, seems to be stellar.

I restored the entire system from the October 4 nightly WHS-2011 backup. The system was "solid" again. I ran Steam games, watched encrypted TV from my SillyDust tuners, poked around. Ran IntelBurnTest through 20 iterations, OCCT Linpack for a half hour. Rock solid. I might have run a graphics stressor, but the gaming would have seemed enough.

Then, the notice under Windows Updates reminded me that I had to do them over because this was the October 4 backup of the OS.

Suddenly, after they completed, my misery returned. I suspect an "optional" update as the cause.

Let me know if there seems to be any connection with between your Windows 10 problem and my Windows 7 problem. I'll probably paste some of this in the new thread, because someone else may know something, too.

 

[Dahak]

Let me know if there seems to be any connection with between your Windows 10 problem and my Windows 7 problem. I'll probably paste some of this in the new thread, because someone else may know something, too.

I have no problem myself, but this was more an FYI in case someone came across this issue with either of the last two cumulative updates for Win10

But they did start to do a monthly rollup for Win 7 and Win 8 as well now too, it could be that there is an update in there that could be causing the issue
Best to start a new post as your issue does not seem to be related to this topic

 

[Puffnstuff]

All of my pc's were able to apply the update without issue.

 

[mike8675309]

Whatever update Windows 10 applied to my Dell Latitude E6500 2 days ago has essentially bricked it. Granted this is a pretty old machine, but I was not happy when that happened. The update did not create a restore point so I couldn't revert. Each startup gets the screen "Your PC ran into a problem and needs to restart.
Sometimes issue is
Stop Code : DRIVER IRQL NOT LESS OR EQUAL
What Failed iaStoreA.sys
or it will be
Stop Code: ATTEMPTED EXECUTE OF NOEXECUTE MEMORY

Can't get past that and don't know what update it was. Windows 10 said it was going to install an update, next morning machine is sitting at one of the two screens above.

 

[mike8675309]

I have been able to verify that the problem is Cumulative Update for Windows 10 Version 1607 (KB3194798).
Applying update gets through all the steps up to like 30% after which it reboots. Then when it reboots it throws the stop code DRIVER IRQL NOT LESS OR EQUAL

I've reverted the machine multiple times and the problem persists.

 

[Dahak]

@mike8675309 after you reverted, did you apply the Microsoft fix before installing the update again? as that is suppose to fix this issue with this particular update

 

[mike8675309]

No, I did not apply any fix.
Thus far after the last failure of update application (Saturday Night) I reverted Sunday morning again. Then later Sunday my machine woke up and started installing the update once again. This time it completed and did not throw any errors.

I haven't messed with it to see if it is now reliable as I have replaced that machine already. But I would like to get it stable so I can give it to a family member.

 

[Bubbaleone]

Whatever update Windows 10 applied to my Dell Latitude E6500 2 days ago has essentially bricked it. Granted this is a pretty old machine, but I was not happy when that happened. The update did not create a restore point so I couldn't revert. Each startup gets the screen "Your PC ran into a problem and needs to restart.
Sometimes issue is
Stop Code : DRIVER IRQL NOT LESS OR EQUAL
What Failed iaStoreA.sys
or it will be
Stop Code: ATTEMPTED EXECUTE OF NOEXECUTE MEMORY

Can't get past that and don't know what update it was. Windows 10 said it was going to install an update, next morning machine is sitting at one of the two screens above.

Since iaStorA.sys is the Intel RST (Rapid Storage Technology) driver, I'd suggest first updating to Intel's latest offering and then run Windows update again. Intel RST drivers written for Vista and 7 won't run on Windows 10.

.

 

[Puffnstuff]

Since applying that update I've moved my desktop and tablet to the preview ring and my laptop to the slow ring so I can get updates sooner.

 

[Puffnstuff]

Looks like build 14393.351 has been released to everyone.

 

[suklee]

Built a few rigs - with 6 cards connected I see this BSOD on boot: attempted execute of noexecute memory

5 cards: mining smoothly and hasn't crashed after 1 hour
6 cards: BSOD on start up

I'm really hoping this is not a PSU issue.

Rig specs:

Intel G3260
AsRock H81 BTC Pro 2.0
4GB DDR3-1600
120GB SSD
6x Sapphire RX470 Nitro with 6-pin PCI-e powered USB risers
Corsair RM1000i
Windows 10 OEM

Any ideas?

PS. Same issue being discussed at https://bitcointalk.org/index.php?topic=1825977.msg18179525#msg18179525. OP has the same issue on AsRock H81 Pro BTC as well as Biostar TB85

 

[Dahak]

if you turn on the memory dump options and run whocrashed or bluescreenview to view the memory might tell you something, or at least maybe point to if its a driver issue or not