Unsolved
This post is more than 5 years old
6 Posts
0
2743
January 2nd, 2017 10:00
Driver crashing issue
My computer has been having a consistent problem with crashing and needing to reboot. The computer will suddenly have crackling sound and slowdown, the sound will break, and then the computer will black out for a moment or freeze, needing to restart. The event logs say that:
Display driver nvlddmkm stopped responding and has successfully recovered.
and
The description for Event ID 263 from source Win32k 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.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The specified resource type cannot be found in the image file
Is the driver corrupted? How do I remove it?


dbrewster
3 Novice
•
237 Posts
•
852 Points
0
January 2nd, 2017 13:00
IF u use LocalNetwork Throttling with a program like KILLER, make sure your NVID Backend is set to level like kernel system, local service etc.
E2Alien
6 Posts
0
January 2nd, 2017 15:00
What do you mean by this?
dbrewster
3 Novice
•
237 Posts
•
852 Points
0
January 3rd, 2017 10:00
I HAVE experienced a situation with Network Application controls where Your bandwith/network priorities are controlled with a ProgramApp like Killer Networking. If U have a Killer Network Program it may have an options for Local network Priorities and the ability to allow LAN exceptions or disallow LAN exceptions. which means your Local APPS are controlled as well. Seems too simple but I had a crash with Nvidia b4 and noticed the app list in KILLER. AND NVid backend and a few others like LocalServices where a low priority by default, and the computer crashed while I was using it. ALSO if anything in your color formatting and depth have been changed,, reset these back to default in NV control panel. Also if it repeats sometimes reinstall the Graphics driver.. (usually check 'custom' , 'clean')
And that can fixit too. Worked for me.