Windows 10: PC crashes after gaming, have tried various fixes and fixed a lot of the errors but I am...

The server Windows.Media.Capture.Internal.AppCaptureShell did not register with DCOM within the required timeout.The server Windows.Media.Capture.Internal.AppCaptureShell did not register with DCOM within the required timeout.The previous system shutdown at 3:15:57 PM on ‎1/‎5/‎2025 was unexpected.

:)

 

I have a 0xc000007b error on multiple games. I have tried almost any fix

and thanks for reading.

First of all, i know this question of how to fix this error is asked a lot on here. I already went through most of the articles and solution and tried them out and surprisingly none of them worked.

So the game is question is Mount & Blade: Warband.

What I have tried so far:

1. Reinstall .Net Libraries (Uninstall and Install)
   
2. Reinstall Visual C++
   
3. Update the computer
   
4. Run compatibility troubleshooter
   
5. Try out all compatibility settings
   
6. Install new / repaired dll files
   
7. Run AIO
   
8. Run sfc /scannow
   
9. Reboot
   
10. Reinstall said application
    
11. Run as an Administrator
    

I really tried solving this on my own, but now I am out of ideas, since none of the methods works for the game and also any game of this series.

So my question is weather anyone has a solution for my problem, because I don't really want to reset my pc

Thank you a lot in advance

 

Explorer Crash FIX!

Our old Dell Inspiron N5110 got this problem also.
Taskbar keeps refreshing. Thanks many hints from guys above pointed me the direction to fix it.
From Reliability History Monitor I found Explorer keeps crashing because of IDTNC64.CPL (type reliability history at Start)
1. the issue was from IDTNC64.cpl, the sound driver,
but I could not successfully to uninstall it from device manager nor control panel or rename the file or the folder.
2. uninstalled High Definition Audio Device few times, problem remain
3. tried to uninstall within Control Panel > Program file, yet Control Panel only open 2, 3 seconds then closed automatically.
4. finally solved Control Panel shut down problem by going to msconfig>services>and disable Windows Error Reporting Service. see below sequence:
Click window + R keys, type msconfig, Enter to open msconfig, click Services Tag and look for Windows Error Reporting Service. Unchecked it, then apply, ok then reboot system when it suggests.
5. After this, open Control Panel by clicking Start > type Control Panel. Then my Control Panel open and stay put, won't shut down by itself.
6. In Control Panel > Programs > I found IDT Audio and successfully to uninstall it.
7. No more taskbar refresh or Windows Explore shut down after uninstalled IDT and Sound still works great!!!
8. repeat step 4 to check Windows Error Reporting Services by clicking it. OK then follow system suggestion to reboot.
9. Control Panel still able to open and remain open. Sound still works and no more refresh.
10. From Reliability History monitor found no more Windows Explorer crashing.
I am happy and hope above steps help

 

Various applications crashing, mostly from error 0xc0000005


KScorp, did you ever find any solution to this? I've been having the same problem for a while now. I too have the issue mostly when gaming (GTA5, BF4) I should try other games too. The crashing is pretty random as well. I thought I had it fixed today because I played GTA and BF4 for about 3 hours total with no crash. Then it suddenly crashed while I was in GTA5.

Things I have tried:

• Run Memtest86, for over 24 hours. (Did this twice, no errors)
• Microsoft Memory Diagnostic (No erros)
• Tested all HDD's for bad sectors (all were good)
• Uninstalled/reinstalled Nvidia drivers with DDU (still crashes)
• Uninstalled Nvidia drivers again and moved GPU, a GTX 680, to different PCIe slot (still crashes)
• Ran OCCT PSU test for 3 hours (nothing crashed)
• Ran Driver Verifier to ensure driver integrity (ran for 16+ hours, no BSOD from misbehaving driver)

Things to try still:

• Flash BIOS to updated version
• Reinstall Windows 10 (this was happening with Windows 7 before fresh install/update to Win 10 so I don't think that was the issue)
• Any other suggestions
• Smash with hammer