Windows 10: I keep getting this error in the event viewer, and I think it has to do with the crashing....

submitted by /u/HMVocaloid
[link] [comments]

:)

 

Error in Event Viewer

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned, you have performed a repair installation on the computer and you see Event 508, 510 and 533 in Event Viewer.



I would like to inform that if you see any critical error in Event Viewer, please share the event logs with us to help you with the appropriate troubleshooting steps. Please follow the steps mentioned below to share the event logs:

1. Press Windows + X from the keyboard, select
   Event Viewer.
   
2. Expand Windows Logs from the left pane and select
   Applications.
   
3. Click Filter Current Log from extreme right pane. Then in the new windows check the box beside
   Error and click OK.
   
4. Now, look for a critical Error in the list and note down the message/information from the
   General Tab in the lower section.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Getting nvlddmkm error in event viewer, game crashing

Hi,

I've been getting nvlddmkm errors in event viewer every time I play the game Outlast 2 which was just released. I'm using Lenovo IdeaPad laptop, while not high specs, it can run the game at 60fps at mid-high settings with no problem so I highly doubt that it's not meeting minimum requirements. Gonna keep it point form for easy read.

Symptoms:

• Within 1-10min of gameplay, game would freeze for a few seconds then throw a "Outlast 2 has stopped working" Windows error
• Few seconds after clicking "close program" in the error, it would throw a "Rendering thread exception - fatal error"
• After closing that, it would finally throw a Microsoft Visual C++ runtime error "RUNTIME ERROR! R6025 -pure virtual function call"
• In event viewer, I get about 16 or so error events, "The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer" (screenshot)
• Also get a warning event in event viewer usually on top of error events, "Display driver nvlddmkm stopped responding and has successfully recovered"
• Only game crashes, windows not affected

Specs:

• Windows 10 64-bit with anniversary update, no creators edition
• i7-4700MQ
• 8GB RAM
• Nvidia GT750M Optimus, latest driver as of this post which is 383.22

Things already tried:

• Absolute minimum graphic settings in-game + windowed mode
• Disable hibernate/quick start in power options and restart computer
• Use DDU-safe mode to uninstall everything Nvidia related, then manually download 383.22 and reinstall it, didn't install GeForce Experience or PhysX
• Use DDU-safe mode to uninstall everything Nvidia related, then manually download 368.81 to roll back, didn't install GeForce Experience or PhysX
• Power options -> PCI Express -> maximum power settings
• Power options -> processor power management -> max processor state -> change to 99% instead of 100%
• sfc scannow in CMD (no errors)
• DISM checkhealth in CMD (no errors)
• Adding TDRDelay registry key and set it to 10
• Whitelist entire game directory in Windows Defender
• Create new windows user account and launch game from that account
• Force game to use integrated Intel HD graphics -> this would prevent any crash, but obviously be unplayable at like 5fps. So this means it's something wrong with Nvidia drivers, and not my computer?

I even chatted with service rep from Nvidia, they're out of ideas too and told me "check with Lenovo", lol.

Does anyone have any other ideas?

 

Event Viewer (MCC.exe) crashes 'System.IO.IOException'

I'm afraid this is another Windows 1903 bug (current ver 1836.175) as it is reproducible on every (?) PC.

• run Event Viewer
• click 'Create Custom View' on the right panel
• create for example a filter for System, events 6005, 6006, give it a name and save it:
  
  
• then click on the left tree "Custom Views" and an mcc.exe crash will occur *Confused reporting a IO error reading "C:\ProgramData\Microsoft\Event Viewer\Views\View_0.xml"

P.S.
To roll-back you can from an admin prompt:
Code: