More 1803 probs Page fault on video smart audio drivers

Foxconn H67 intel board with i7-2600 with Nvidia GTX560 graphics card.

Upgrade from 1709 to 1803 we now unable to boot due to page fault. Will boot into safe mode.

Chkdsk and SFC run with no solution.

Device manager shows many nvidia audio problems.

When we remove the graphics card the system boots but also shows one audio issues with the onboard audio (there is a windows update for graphics/audio, but made no difference, no other updates available).

In safe mode we upgraded the nvidia graphics driver, and rebooted. Still doesn't boot but with a different error "video scheduler internal error".

In my experience in computer repairs, Windows 10 1803 is the worst version of Windows I've had the displeasure to work with, and I'm going back to the early 1990's with Windows 1.0! So many problems (and rebuilds).

Microsoft do need to review the Windows 10 upgrade process, it isn't robust and is doing more harm than creating usable benefits.

Further info:

I should have said above the latest software for the GTX 560 ti card is for Windows 8 - however the card has worked fine after the Win 10 upgrade from Win 7/64 until 1803 that is.
I uninstalled via Device Manager (DM) the software for all items showing errors, but did not delete. System booted okay without attempting to re-install any drivers on booting. I note that DM now lists audio and graphics under "other items", but no specific mention of the graphics card, "just video controller (vga compatible)"; no info is available on properties, and if clicking on the update driver, it downloads a driver(?), and attempts to install but fails again with the same video scheduler internal error.
I then tried to to re-install the Win 8 graphics driver both in normal & compatibility mode; the first gave rise to the same video scheduler internal error, the latter just said incompatible.

We'll see if we get any suggestions - gratefully received - on this post, other wise we will revert to 1709 and ensure we get no more WI10 upgrades!!!!!

I had the same issue trying to update my Win 10 from 1703 - some days i would get at least 1 GSOD, sometimes 2 or 3. It always pointed to my graphics card, that i needed an update. Unfortunately, the integrated video card driver i had installed was the last nVidia put out for it. As it is, i have to remain on 1703 to give me the proper resolution for my 2 monitors & eliminate the GSODs. On a 2nd partition, i have 1803 installed - tried to update graphic driver hoping against hope. No go, about an hour later another GSOD with Page_Fault_In_Non-Paged_Area error. Back to MS Basic Adapter driver. But no GSOD since.

Bottom line, methinks you are stuck just like i am with whatever build works with your hardware drivers without throwing up errors. It stinks but nothing short of upgrading/replacing hardware/computer will possibly solve the issue!

Ztruker said:

The WER data in msinfo32.nfo indicates you had 20 bluescreens. Most were X119 or x50.
Looking through Eventlog.txt, I see a lot of these:

DCOM got error "1084" attempting to start the service xxxxxxxxx

Searching on this error indicates one of the causes is a corrupted video driver. If you used DDU that should have taken care of the old driver but I'm suspicious there are remnants left somewhere that are causing the problem.

If this was my computer, I would install a new hard drive large enogh for Windows 10 (80GB minimum), disconnect eh existing drives, then do a Clean Install of Windows 10 using the 1803 ISO from Microsoft and see if the problem still exists or not. If not then you know there is corruption in your existing Win 10 install on your multi-boot system and you need to reinstall it.

Curious, why do you still have XP, 7 and 8.1?

Again thank you for looking at the diagnostics - my system is multi-boot, but the system in question is a 3rd parties' which I have to repair. DDU was run successfully in as far as it went. I am coming round to thinking its either a clean install or replace video card, helpful to have your input on this.

badrobot said:

I do have multi-boot (on separate drives) on my other system and I used to have issues during updates. I resolved the issue by disconnecting the other drives before updating my system and no issues come up. I guess your multi-boot also contributes to the problem. The update process is detecting more than one system folders.

Apologies, as I said above, it is not my system that has the problem, but a third parties "single boot" win 10 pro 1803 system post the upgrade - the diagnostics are of that system NOT the multi-boot system.