Faulting module name: KERNELBASE.dll, version: 10.0.19041.3992, Faulting module name: CONCRT140_APP.dll

People are suggesting this is a hardware compatibility issue involving Intel Core 2 CPUs: https://answers.microsoft.com/en-us/windows/forum/all/microsoft-photos-file-system-error-2147219196/3bf0b7d0-4390-46f2-b948-a1e05d726e73?page=6.

Out of 5 PCs I looked at today, the one exhibiting this problem with Microsoft Calculator, Photos, Paint 3D, Feedback Hub, Film & TV, and Voice Recorder does have an Intel Core 2 Quad CPU.

The other PCs that work are all using much newer Intel CPUs.

For those that don't know how to find their processor info, run the system information app.

Type "info" in the search box on your taskbar, and then select the system information app.

For system summary, on the right hand pane, look for "Processor".

Windows 10 Pro 64 bit edition, Version 22H2 (OS Build 19045.3930) with no pending windows updates available exhibits this issue on a PC here with the following app versions:

Photos 2024.11010.1002.0

Faulting application name: PhotosApp.exe, version: 0.0.0.0, time stamp: 0x659f3d43

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979

Exception code: 0x00001007

Fault offset: 0x000000000012db22

Faulting process ID: 0x4494

Faulting application start time: 0x01da508377bd06a2

Faulting application path: C:\Program Files\WindowsApps\Microsoft.Windows.Photos_2024.11010.10002.0_x64__8wekyb3d8bbwe\PhotosApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: a7f21100-823a-43e9-a8e2-396aa00bf863

Faulting package full name: Microsoft.Windows.Photos_2024.11010.10002.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Calculator 11.2311.0.0

Faulting application name: CalculatorApp.exe, version: 11.2311.0.0, time stamp: 0x65984a23

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979

Exception code: 0x00001007

Fault offset: 0x000000000012db22

Faulting process ID: 0x3b34

Faulting application start time: 0x01da5082eae764bc

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_11.2311.0.0_x64__8wekyb3d8bbwe\CalculatorApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: a236ddf8-8e19-4900-b992-41e0f3786449

Faulting package full name: Microsoft.WindowsCalculator_11.2311.0.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Mail and Calendar 16005.14326.21786.0

Faulting application name: HxCalendarAppImm.exe, version: 16.0.14326.21786, time stamp: 0x6597575c

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x105c

Faulting application start time: 0x01da50842d5e6f54

Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_16005.14326.21786.0_x64__8wekyb3d8bbwe\HxCalendarAppImm.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: 166514ed-6118-40b8-a3e3-a6429fea7f78

Faulting package full name: microsoft.windowscommunicationsapps_16005.14326.21786.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: microsoft.windowslive.calendar

Films & TV 10.22091.10051.0

Faulting application name: Video.UI.exe, version: 10.22091.1005.0, time stamp: 0x6530e1eb

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x2760

Faulting application start time: 0x01da5084425fe2ab

Faulting application path: C:\Program Files\WindowsApps\Microsoft.ZuneVideo_10.22091.10051.0_x64__8wekyb3d8bbwe\Video.UI.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: f0c09420-d1d5-4ed4-b0ae-c313807baacb

Faulting package full name: Microsoft.ZuneVideo_10.22091.10051.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: Microsoft.ZuneVideo

Paint 3D 6.2310.24037.0

Faulting application name: PaintStudio.View.exe, version: 0.0.0.0, time stamp: 0x65387a54

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x48d8

Faulting application start time: 0x01da508453accc7b

Faulting application path: C:\Program Files\WindowsApps\Microsoft.MSPaint_6.2310.24037.0_x64__8wekyb3d8bbwe\PaintStudio.View.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: f7513880-be05-426e-acb5-a2156b2c1763

Faulting package full name: Microsoft.MSPaint_6.2310.24037.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: Microsoft.MSPaint

Feedback Hub 1.2309.12711.0

Faulting application name: PilotshubApp.exe, version: 1.2309.2309.28001, time stamp: 0x65152eaf

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979

Exception code: 0x00001007

Fault offset: 0x000000000012db22

Faulting process ID: 0x5294

Faulting application start time: 0x01da50840995bdac

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsFeedbackHub_1.2309.12711.0_x64__8wekyb3d8bbwe\PilotshubApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: 97a1d38d-96f0-447e-ab79-abe02d35564e

Faulting package full name: Microsoft.WindowsFeedbackHub_1.2309.12711.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Voice Recorder 10.2103.28.0

Faulting application name: SoundRec.exe, version: 10.2103.28.0, time stamp: 0x60622fa3

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x35a4

Faulting application start time: 0x01da5084b44889af

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsSoundRecorder_10.2103.28.0_x64__8wekyb3d8bbwe\SoundRec.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: 7d641597-feeb-4408-a5d0-134dbbde1406

Faulting package full name: Microsoft.WindowsSoundRecorder_10.2103.28.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Windows upgrade (otherwise known as in place reinstall) didn't fix the issue.

DISM /Online /Cleanup-Image /ScanHealth **** didn't help.

sfc /scannow didn't find anything wrong.

Uninstalling and reinstalling apps didn't fix anything.

Repairing apps didn't fix anything.

Resetting apps didn't fix anything.

Windows Store Apps troublesooter didn't fix anything,

Using powershell to reinstall/obtain, and register packages didn't fix anything.

Deleting and reinstalling the Microsoft Store app didn't fix anything, of course.

Creating a new local user account and signing into it doesn't change anything.

Disabling antivirus and my firewall, of course, doesn't fix anything.

Affected account is an Administrator account.

If anyone cares, there's another thread discussing the same problem over here: https://answers.microsoft.com/en-us/windows/forum/all/microsoft-photos-file-system-error-2147219196/3bf0b7d0-4390-46f2-b948-a1e05d726e73

Listen to what you are saying. People always give the same excuse about new things not supporting older hardware.

That is NOT an acceptable way to be in the world, it's just an excuse.

The fact is that People all over the world have various ages of hardware and these machines worked correctly until the last updates.

So the real issue is still that the new updates should NOT have broken existing systems.

I studied software development quite a few years ago and the first rule I was taught is that you never break older/existing systems with your changes.

You always ensure existing customers are ok (backwards compatibility).

If you need a new technology that requires newer systems, you make it available but you do NOT force an update on users that breaks existing systems. You make the workable versions available and then offer the new updates as an option, clearly saying with the new version that it will be bad for systems before 'xxxx'.

A company I worked for always maintained workable software versions for customers. New software that required new hardware was made available and BOTH or ALL versions were still available. All customers were happy and returned their business.

It CAN work if the company tries and does the right thing.

As an interesting example, look at any software installer that checks what is installed before deciding to install update version 1 or update version 2 ; x86 or 64 bit, etc. They can do it when they try.

I'm having the same issue on many computers with Windows 10. The calculator app was updated on 1/26/2024. It was work yesterday and now hundreds of our PCs the app opens and closes with the same event log shown above.

Why does the calc app need to be updated?

Do I really have to install another calculator app on 100 computers?