
Enable or Disable Windows Error Reporting in Windows 10
Apr 12, 2022 · This tutorial will show you how to enable or disable Windows Error Reporting for your account, specific users, or all users in Windows 10.
Change Windows Error Problem Reporting Settings in Windows 10
May 21, 2021 · Problem Reporting Settings: Always ask before sending data (Each time a problem occurs, ask me before checking for solutions) - Windows prompts users for consent to …
Microsoft Community
Microsoft Community
How to reset Windows error reporting back to default?
Aug 18, 2024 · In the past I had attempted to stop the collection and sending of these reports. I would now like get it all working again. I noticed the "Problem report settings" screen doesn't …
Hardware Error - LiveKernelEvent (Code 141). Computer Crashes
Jul 24, 2024 · Description A problem with your hardware caused Windows to stop working correctly. Problem signature Problem Event Name: LiveKernelEvent Code: 141 Parameter 1: …
Random Freezing from hardware error, event name LiveKernelEvent
Dec 6, 2017 · Error: MANUALLY_INITIATED_CRASH1 file path: C:\WINDOWS\system32\drivers\rspcrash64.sys product: WhoCrashed company: …
RADAR_PRE_LEAK_64 reports in event viewer. - Windows 10 Forums
Jul 17, 2016 · But on event viewer i get : RADAR_PRE_LEAK_64 error. Application is opening fine but windows 10 reporting this as RADAR_PRE_LEAK_64. Where is the problem? …
Redirecting application crash dumps to another folder Solved
Apr 13, 2024 · Redirecting application crash dumps to another folder Running Windows 10-64 22H2. I'm running an application that has a new feature I like; unfortunately, this feature …
Start menu experience host issue Solved - Windows 10 Forums
Apr 9, 2024 · Hey all I don't know if this is a major problem or not but since updating to 19045.4291 i've having this come up in reliability history: Source …
StoreAgentScanForUpdatesFailure0 Event ID: 1001 - Windows 10 …
Sep 15, 2020 · The last informational error posted had a fault bucked of 2171225445541773434, type 5 but the first two informational errors had the same info as below but the Fault Bucket …