I have found a lot of threads that concern the KB3197954 update, and most of those problems were addressed with another game throwing in the same error.
The difference is what fixed it was through updating Java which I don't think helps here, since osu! Doesn't heavily rely on Java.
I have also taken note that there isn't a really definitive fix for this, since it's really specific in a certain degree.
OBDavid wrote:
Maybe this update could be the problem
Translation: Update Installed Successfully
I have found articles that relate to updating of drivers obtained through Windows Update and the error appearing.
Yet it was for a failed update, and the articles are really old.
https://m.reddit.com/r/vaio/comments/3y ... iver_help/average_mitch wrote:
I factory reset my computer because it just wasn't up to snuff and I wanted to make sure everything had been properly installed, etc. Anyway, I bought it with Windows 8, so a few updates were required (23). After successfully installing 22 of the 23 updates, one would not install...
- Intel HD Graphics Family / 4400 Update, Version 10.18.10.3316
A message appeared with the title:
"Can't find the name of Intel ICD OpenGL driver"
Followed by the message:
"Intel HD Graphics Family / 4400 Update, Version 10.18.10.3316 did not update"
https://github.com/LWJGL/lwjgl/issues/1194rz0 wrote:
I can confirm Case 2.
Specs:- Windows 10 Pro release, most recent (10.0.10240)
- JRE 1.8.60 x64
- Intel HD Graphics 3000
- Intel drivers from May 2015, obtained trough Windows Update (9.17.10.4229)
Take note that they are really old articles, with the case of updates being the sole cause. Since they're old, you can't say that the problems caused in the links are the same exact here. However, I have reason to believe it
could have caused it again.
t/518686cherrypie01 wrote:
I have tried everything there but those didn't help. It seems for some reason my Intel graphics driver deleted itself or something. I recovered to a week ago and the problem seems solved. Maybe a Windows update caused it? Anyway thanks for your help.
The cases above and the circumstances are very close, with the same OS version and with Intel HD
feedthebeast wrote:
I took a stab in the dark and shut off the Xbox Game bar integration by turning off the DVR options completely. Low and behold, it worked. It seems that there may be an issue for some people that when the DVR is enabled (which it is by default)
NeVe12p4wNeD wrote:
Kao wrote:
See if this thread helps
t/518686
Are you serious? Really?
You wanted me to start another thread only to be redirected to the same one I was on? REALLY??????
Please go away. You're not helping at all.
This link was for OBDavid, sorry if that looked like I was tricking you. But the log shown was same of that thread.
His problem is the same now in that thread. With the problem caused by an update.
Pawsu wrote:
SPOILERHuh. This seems to be an occurring error lately.
Hold shift while opening osu!, and when the recovery dialog opens, try enabling the option "compatibility mode". This do anything? If not, try switching to Stable(Fallback). Any luck there?
OBDavid wrote:
Same problem
Processor: Intel i5 6300HQ
Graphiccard: Nvidia Gtx 970M
Windows 10
I don't think this is the same problem. I'd make a new thread for your problem.
I think they're the same
t/518686 this thread where OP first posted and the OP from that link itself throw in the same error, in which OBDavid had the same log.
Could NeVe12p4wNeD post their crash log (if any) here aswell?
Within said thread, the log means this
The runtime throwing a NullReferenceException always means the same thing: you are trying to use a reference. The reference is not initialized (or it was initialized, but is no longer initialized).
This means the reference is null, and you cannot access members through a null reference.
This could be referenced to the ICD Driver not being found.
Bottom line?
I really can't pinpoint a real fix to this anymore. But since it's caused by updates, rolling back updates until new updates that (hopefully) fixes these are addressed.
This has been spreading suddenly, and they're always concerned with a recent update.
Try restoring to a previous version or update.