Device Census Stopped Working Problem

I have recently noticed when viewing my reliability monitor that every day around the same time 3 am - 4 am, windows shows that a program called "devicecensus.exe" has stopped working and notes it as a "critical event". My question is should I be worried about this and if so what are the potential fixes? Also is this application an integral part of Windows and if I delete it from System32 will it have an effect on my PC in any shape or form?

Thanks in advance for the responses and here are some of the error details if it helps:

Problem signature
Problem Event Name: APPCRASH
Application Name: devicecensus.exe
Application Version: 10.0.17134.1
Application Timestamp: 79a09a4b
Fault Module Name: WaaSAssessment.dll
Fault Module Version: 10.0.17134.1
Fault Module Timestamp: b7ab6594
Exception Code: c0000005
Exception Offset: 0000000000008ee5
OS Version: 10.0.17134.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 91f2
Additional Information 2: 91f294f44a03f9fda838805399465eda
Additional Information 3: ada5
Additional Information 4: ada50e612b0ea4dc151ec1a740a42603

Files that help describe the problem
WERInternalMetadata.xml

 

Question Info


Last updated August 22, 2019 Views 3,994 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

For the above site linked:

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

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 have this same problem. It's been crashing every day when I turn on my computer.

The problem started with KB4284835, June Cumulative Update, patch level 17134.112.

Reverting to 17134.83 or lower fixes the problem on my machine, but it's only a temporary fix, because can't refuse updates and they're all roll-ups so can't refuse the one part of the update that is screwing up the machine.

Noting the date on your post, I think we may have the same problem.

I have an Nvidia 1080 GTX with the latest drivers, so if Nvidia is the problem, what do I do to fix it?

BTW, you can just disable the task in Task Scheduler. It's the task in Microsoft/Windows/Device Information

Then it won't run. I have no idea what that does to the system though. I'm trying to get the MS guy in my thread to tell me if this is necessary or not.

Here is the link to my report

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 have the same problem but it started after updating to patch level 17134.137. I upgraded my PC from Windows 10 Fall Creators Update to Windows 10 April 2018 Update two weeks ago via Windows Update. The current build after the update was 17134.112. After updating it to build 17134.137, the devicecensus.exe process with faulting module WaaSAssessment.dll crashes every morning when I boot my PC. I hope Microsoft fixes the crashing problem caused by the update in the next cumulative update which might be released on Tuesday or Wednesday next week

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've been getting this same crash daily (I shutdown at night when I'm done with my PC) since the 2018-05 Cumulative Update came on the 21st of June. The update this week didn't fix it.

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 installed the latest cumulative update that was released on Tuesday with patch level 17134.165 but the daily crash has not been fixed together with other Windows 10 April 2018 update problems such as some mkv video files cannot have their thumbnails generated in File Explorer unless a thumbnail generator like Icaros thumbnails is installed. The videos play well but most of their details are not loaded when right clicking the file and navigating to the details tab. Icaros thumbnails also loads the details in the details tab.

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 installed the latest cumulative update that was released on Tuesday with patch level 17134.165 but the daily crash has not been fixed together with other Windows 10 April 2018 update problems such as some mkv video files cannot have their thumbnails generated in File Explorer unless a thumbnail generator like Icaros thumbnails is installed. The videos play well but most of their details are not loaded when right clicking the file and navigating to the details tab. Icaros thumbnails also loads the details in the details tab.

This issue just started for me with the last cumulative update july 9 2018.

The pc gets passed the bios post test and loads to the start screen and either a failed 

load of the os with a spinning wheel or blank   screen for x minutes.

Looking at the logs from event viewer;    

Faulting application name: devicecensus.exe, version: 10.0.17673.1005, time stamp: 0x79a09a4b
Faulting module name: WaaSAssessment.dll, version: 10.0.17134.1, time stamp: 0xb7ab6594
Exception code: 0xc0000005
Fault offset: 0x0000000000008ee5
Faulting process id: 0xf44
Faulting application start time: 0x01d41bd59ade763f
Faulting application path: C:\WINDOWS\system32\devicecensus.exe
Faulting module path: C:\Windows\System32\WaaSAssessment.dll
Report Id: 006e40b8-7b2b-403a-b842-a07d3f5ed8b2

and this at the same time;

Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin
Source:        Microsoft-Windows-Kernel-EventTracing
Date:          7/14/2018 6:49:09 PM
Event ID:      2
Task Category: Session
Level:         Error
Keywords:      Session
User:          SYSTEM
Computer:      DESKTOP-SVOCV7A
Description:
Session "ECCB175F-1EB2-43DA-BFB5-A8D58A40A4D7" failed to start with the following error: 0xC0000035
So the user is not logged in but these things are trying to run before login, of course it will fail as they need to start after login.

Another fine mess from the quality team and not listening to insiders.

Going to a local account has fixed this issue on another win10 with the same build 17134.165;

may have to do the same on the other four.

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.

Getting this error on all win10 pc's running 1803, so something 6/28/2018 when it started.

Log Name:      Application
Source:        Application Error
Date:          7/22/2018 5:04:58 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-C7MSO9M
Description:
Faulting application name: devicecensus.exe, version: 10.0.17673.1005, time stamp: 0x79a09a4b
Faulting module name: WaaSAssessment.dll, version: 10.0.17134.1, time stamp: 0xb7ab6594
Exception code: 0xc0000005
Fault offset: 0x0000000000008ee5
Faulting process id: 0x2e34
Faulting application start time: 0x01d422104b581eb4
Faulting application path: C:\WINDOWS\system32\devicecensus.exe
Faulting module path: C:\Windows\System32\WaaSAssessment.dll
Report Id: 75d6d06e-0774-49ed-8713-dd95fe56a512
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-07-22T23:04:58.926384000Z" />
    <EventRecordID>3256</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-C7MSO9M</Computer>
    <Security />
  </System>
  <EventData>
    <Data>devicecensus.exe</Data>
    <Data>10.0.17673.1005</Data>
    <Data>79a09a4b</Data>
    <Data>WaaSAssessment.dll</Data>
    <Data>10.0.17134.1</Data>
    <Data>b7ab6594</Data>
    <Data>c0000005</Data>
    <Data>0000000000008ee5</Data>
    <Data>2e34</Data>
    <Data>01d422104b581eb4</Data>
    <Data>C:\WINDOWS\system32\devicecensus.exe</Data>
    <Data>C:\Windows\System32\WaaSAssessment.dll</Data>
    <Data>75d6d06e-0774-49ed-8713-dd95fe56a512</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

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.

Is this what causing device-census related errors?

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.

No. If it were, every Windows 10 computer in the world would have been affected.

I have decided to reset one of my affected devices and see if it'll fix the problem. So far, I've only seen this problem on machines that have been updated from v1709.

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.

Is device census only related with webcam or with all other devices' drivers such as, graphic, printer, or wi-fi/wired NIC, etc?

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.