CCCONE.EXE持续崩溃问题排查建议请求

Hey there, let's tackle this persistent CCCONE.exe crash issue with your body shop client head-on. First, let's start with the error details you shared to ground our troubleshooting:

Name: Application Error
Error Message: Faulting application name: CCCONE.exe, version: 35.0.0.5080, time stamp: 0x645969af
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2965, time stamp: 0xf18c1c30
Exception code: 0xe0434352
Fault offset: 0x0013d6c2
Faulting process id: 0x413c
Faulting application start time: 0x01d99d541dbdafc2
Faulting application path: C:\ProgramData\CCCIS\CCCONE\v2453\CCCONE.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: fcd37a9b-4086-4378-8a87-953e89103e41
Faulting package full name:
Faulting package-relative application ID:
TimeWritten: 6/12/2023 1:34:24 PM
ComputerName: GPAB-GIL-SHOP01
Category: 100
Type: Error

Now, based on this log, here are targeted recommendations tailored to your setup (since you already have an RMM-managed updater):

• Zero in on the exception code first: The 0xe0434352 code is a dead giveaway for an unhandled .NET runtime exception. Even though the fault points to KERNELBASE.dll, the root cause is almost always in CCCONE's .NET code or its dependent .NET framework version. Since your updater keeps apps current, double-check that the client's machine has the exact .NET framework version recommended by CCC's documentation for v35.0.0.5080—sometimes auto-updating to the latest .NET version can break compatibility with older enterprise apps like CCC One.
• Verify CCCONE update compatibility: Your updater pushed v35.0.0.5080, but this version might have known conflicts with the client's Windows 10 21H2 build (19041.2965). Try rolling back to the previous stable version of CCCONE on the affected machine and see if crashes stop. Also, reach out directly to CCC's support team to confirm if this specific CCCONE version is certified for Win10 21H2.
• Fix potential system file corruption: Since KERNELBASE.dll is a core Windows component, run these commands on the client machine to rule out corrupted system files:
  • Open Command Prompt as admin and run sfc /scannow
  • Follow up with DISM /Online /Cleanup-Image /RestoreHealth
• Dig into CCCONE's internal logs: Windows Event Log only gives high-level info—check CCCONE's native logs (usually in C:\ProgramData\CCCIS\CCCONE\Logs or a subfolder under the app path) for details on what the app was doing right before the crash (e.g., processing a repair estimate, uploading photos, syncing data). This can pinpoint a specific trigger action.
• Check RMM alert scope: Is this crash happening on just the one machine (GPAB-GIL-SHOP01) or multiple client machines? If it's single-machine, focus on local config issues (like corrupted app cache, user profile problems). If it's widespread, the issue is likely with the updated CCCONE version itself, so prioritize escalating to CCC support.

备注：内容来源于stack exchange，提问作者Joshua Jimenez