Device Census Stopped Working Problem

On my HP laptop, the problem has disappeared. It is rather newer than my other devices, as it has a 4th-gen Intel Core i5 CPU. Also, on my company system, which is an ancient Core 2 Duo system, the crash does not happen.

But on my main desktop, which has a 3rd-gen Intel Core i7: I reset Windows 10 twice, and then nuked and reinstalled Windows with Microsoft Media Creator, but even on that naked copy of Windows 10 build 17134.191 (nothing installed, not even drivers), the problem can be reproduced as soon as Windows touches Internet. (It can be indefinitely postponed by disabling Internet connection.) It even occurs in Safe Mode.

Clearly, the problem is not caused by Windows edition, FODs, apps, third-party drivers or account type (Microsoft vs. local).

Thanks for the in depth troubleshooting and findings on this; going to test a post results.

On my HP laptop, the problem has disappeared. It is rather newer than my other devices, as it has a 4th-gen Intel Core i5 CPU. Also, on my company system, which is an ancient Core 2 Duo system, the crash does not happen.

But on my main desktop, which has a 3rd-gen Intel Core i7: I reset Windows 10 twice, and then nuked and reinstalled Windows with Microsoft Media Creator, but even on that naked copy of Windows 10 build 17134.191 (nothing installed, not even drivers), the problem can be reproduced as soon as Windows touches Internet. (It can be indefinitely postponed by disabling Internet connection.) It even occurs in Safe Mode.

Clearly, the problem is not caused by Windows edition, FODs, apps, third-party drivers or account type (Microsoft vs. local).

There is a problem with the little information that Microsoft provides about how its systems work. In my case, my hardware was already 9 years old and the memory driver seemed to be failing. This caused system reboots that curiously occurred when the computer was alone and probably about to suspend on its own.

This became fully apparent when I started testing the RAM memory with MEMTEST 5.01. Then one of the 64-bit channels of the controller failed completely and failed to recognize the inserted memory. In my case I had 16 GB of RAM configured in 4 DDR3 modules at 1600 Mhz and the two corresponding to channel A stopped working passing the configuration from dual channel (128 bits) to single channel (64 bits).

In any case, I haven't seen a clean run of Windows for a long time (no errors in the Windows event viewer). I am currently testing a new computer with a Gigabyte GA-Z270-Gamming K3 motherboard, Intel I7 7700K processor, two 8GB DDR4 2400 Mhz RAM modules, NVidia GTX 950 Graphics Card, Intel Optane 32GB Module, Samsung 850 EVO SSD and a Western Digital 2TB mechanical hard drive. The installation of the operating system has been done from zero and the system has been giving errors from the beginning, including blue screens of death when I try to suspend it. and 0xC00000000005 type errors with the Apple iCloud application, specifically, the ApplePhotoStreamsDownloader.exe photo download module, version: 69.0.0.74.

BY now Microsoft should have sufficient devicecensus.exe crash reports to be able to do some analysis.  Microsoft, what's the common factor in all this?  Is it hardware or software related?  Why is this problem not a recognised Windows update issue?

Why this problem is not listed in the known issues section on windows 10 update site?

PS: the problem persists to current build KB4340917 (17134.191)