Device Census Stopped Working Problem

Anonymous
2018-06-22T23:16:47+00:00

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

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

45 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-08-20T08:02:31+00:00

    The latest update OS Build 17134.228 fixed the problem on my PC. The file that was modified was the faulting module file WaaSAssessment.dll, which was modified of 3rd August 2018.

    Yes, has fixed it for me too.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-08-20T05:52:33+00:00

    The latest update OS Build 17134.228 fixed the problem on my PC. The file that was modified was the faulting module file WaaSAssessment.dll, which was modified of 3rd August 2018.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-07-15T01:43:32+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. DaveM121 936.1K Reputation points Independent Advisor
    2018-06-23T08:49:30+00:00

    Hi Kalzz18,

    Windows 10 contains a Telemetry service that reports back to Microsoft on hardware usage/errors etc.

    Device Census is part of that Telemetry Framework and the process is only gathering data on your usage of the webcam

    If you want restrict this access to your webcam, go to Settings - Privacy - Camera and uncheck the option 'Let apps use my camera hardware'

    Or to specifically restrict this process scroll down the "Choose apps that can use my camera' list and uncheck "Feedback' hub', this will limit the data being sent back to MS Community and should free up your Webcam . . .

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2018-06-23T00:02:30+00:00

    Wow indeed it is installed! I will remove it now and see if this fixes the problem tommorow! Thanks for the quick response. :)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments