Wayne, it has been awhile and much has happened but still having issues. Your insight would be most welcome. You saw my prior crash reports that suggested a CPU problem. After much troubleshooting I confirmed that was the case, and sent my PC back for a new motherboard and CPU. I kept my SSDs and so have the same windows install. First couple days was fine and now I get TBird crashes later in the day and sporadic Firefox tab crashes. What is odd is that past two days I have been on a zoom call for 5 hours with multiple Adobe and Word docs open, as well as Firefox and TBird. Nothing crashed, but about 30 min after the call ended (both days) I had multiple TBird crashes and a FFox tab crash. Nothing shows up in Event Viewer or Reliability Monitor. This happened two days running. Since the PC came back I have: Checked DISM, Scannow, and Chkdsk and all OK Ran MemTest86, 4 passes, and passed Ran OCCT Mem test 20 min passed Ran OCCT CPU test and it continued to stop due to CPU overheating but exhibited no failures while running Did Samsung extended SMART and Diagnostic scans and C: Drive was OK Also, when I cop my TB Profile to my Surface GO and use it with that install of TB in the same Win11 I have on my main machine it works fine. No crashes. '''QUESTION: Any suggestions? Do you think a fresh install of TB and copy back in my Profile might be a good next step?''' Here are two recent crash signatures: bp-16f682d7-d20a-43cd-84dc-3aa8e0260224 bp-e97edd6e-62f1-4b1f-a981-8282a0260223 Here is what WhoCrashed Found: System Information (local) ________________________________________ Computer name: AVA-DESKTOP-202 Windows version: Windows 11, 10.0, version 2009, build: 26200 (x64) Windows dir: C:\WINDOWS Hardware: V370SNx, Notebook CPU: GenuineIntel Intel(R) Core(TM) i9-14900HX 8664, level: 6 Processor count: 32 logical processors, active mask: 4294967295 RAM: 32471.9MB ________________________________________ Crash Dump Analysis ________________________________________ Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Thu 2/19/2026 10:59:24 AM your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\021926-24140-01.dmp (Minidump) Bugcheck code: 0x50(0xFFFFFE7F85D59A40, 0x2, 0xFFFFF803B58A3690, 0x2) Bugcheck name: PAGE_FAULT_IN_NONPAGED_AREA Bug check description: This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component. Analysis: This is likely a software problem which means that it was probably caused by a bug in a driver. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues On Fri 12/26/2025 4:23:12 PM your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\122625-21390-01.dmp (Minidump) Bugcheck code: 0x3B(0xC0000005, 0xFFFFF80717B33D36, 0xFFFFFE86866D8860, 0x0) Bugcheck name: SYSTEM_SERVICE_EXCEPTION Driver or module in which error occurred: CI.dll (CI+83d36) File path: CI.dll Description: Code Integrity Module Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. The crash took place in a Microsoft module. Possibly this problem was caused by another driver on your system that cannot be identified at this time. On Mon 12/8/2025 4:04:42 PM your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\120825-24593-01.dmp (Minidump) Bugcheck code: 0x133(0x0, 0x500, 0x500, 0xFFFFF803A2DC43B0) Bugcheck name: DPC_WATCHDOG_VIOLATION Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. On Sat 11/8/2025 1:24:51 PM your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\110825-24578-01.dmp (Minidump) Bugcheck code: 0x133(0x0, 0x500, 0x500, 0xFFFFF80593BC43B0) Bugcheck name: DPC_WATCHDOG_VIOLATION Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. On Wed 9/10/2025 10:12:06 AM your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\091025-24250-01.dmp (Minidump) Bugcheck code: 0x133(0x0, 0x500, 0x500, 0xFFFFF807E8FC43B0) Bugcheck name: DPC_WATCHDOG_VIOLATION Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. ________________________________________ Conclusion ________________________________________ 5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the suggestions displayed in the bugcheck analysis above. The analysis process took 0:00:12 (h:mm:ss).