F5F Stay Refreshed Software Operating Systems : Event ID 131 Device Setup Manager?

: Event ID 131 Device Setup Manager?

: Event ID 131 Device Setup Manager?

M
MinecraftMegan
Member
Find
89
04-17-2025, 07:11 PM
#1
The system experienced a crash due to DbxSvc 281 running alongside Event 41. During a review of event IDs, I found the DeviceSetupManager event occurred 84 times in the last hour, 904 times in the past day, and 7 days ago. It’s unusual for this PC to be powered off since March 28th, yet events were still being logged. Online sources suggest many devices can trigger such issues. Could you share a method to identify potential causes within the event viewer?
Reply
Reply
M
MinecraftMegan
04-17-2025, 07:11 PM #1

The system experienced a crash due to DbxSvc 281 running alongside Event 41. During a review of event IDs, I found the DeviceSetupManager event occurred 84 times in the last hour, 904 times in the past day, and 7 days ago. It’s unusual for this PC to be powered off since March 28th, yet events were still being logged. Online sources suggest many devices can trigger such issues. Could you share a method to identify potential causes within the event viewer?

Reply
Reply
Y
yalo29
Senior Member
Find
641
04-17-2025, 08:43 PM
#2
Hey, I'm not sure if Event 41 is a shutdown or restart. That kind of thing usually happens. Also, capturing telemetry when the system isn't powered on seems unusual.
Reply
Reply
Y
yalo29
04-17-2025, 08:43 PM #2

Hey, I'm not sure if Event 41 is a shutdown or restart. That kind of thing usually happens. Also, capturing telemetry when the system isn't powered on seems unusual.

Reply
Reply
R
Rlenger
Junior Member
Find
49
04-24-2025, 04:49 PM
#3
Check the Reliability History/Monitor section. It offers a more user-friendly interface, and the timeline view could be useful. Verify if the system time and date are accurate. If needed, run "dism" and "sfc /scannow" to locate and repair any faulty or corrupted files. Refer to the provided links for guidance on using the DISM command-line tool and fixing Windows system files.
Reply
Reply
R
Rlenger
04-24-2025, 04:49 PM #3

Check the Reliability History/Monitor section. It offers a more user-friendly interface, and the timeline view could be useful. Verify if the system time and date are accurate. If needed, run "dism" and "sfc /scannow" to locate and repair any faulty or corrupted files. Refer to the provided links for guidance on using the DISM command-line tool and fixing Windows system files.

Reply
Reply
A
Alansote03
Member
Find
92
04-25-2025, 07:27 PM
#4
Investigating this appears to be a recurring problem among other Windows users, often linked to an update. What caught my attention was how the system recorded the Event ID when the PC was turned off during our absence.
Reply
Reply
A
Alansote03
04-25-2025, 07:27 PM #4

Investigating this appears to be a recurring problem among other Windows users, often linked to an update. What caught my attention was how the system recorded the Event ID when the PC was turned off during our absence.

Reply
Reply