Anyone ever seen this error when starting NV Inspector?

[Caveman]

This is very annoying... Doesn't seem to be anyone else with the issue... Any ideas on how to resolve?

nvidiaInspector.exe - Assert Failure

Expression: [mscorlib recursive resource lookup bug]
Description: Infinite recursion during resource lookup within mscorlib. This may be in mscorlib, or potentially in certain extensibility points such as assembly resolve agents or CultureInfo names. Resource name: Argument_StreamNptReadable

 

[Caveman]

Ok peeps... $10 to the person that can solve this... Really, I'll make good on a PM...

 

[Elixer]

Ok peeps... $10 to the person that can solve this... Really, I'll make good on a PM...

That just means that the program ran into an issue it wasn't expecting.
So, the fix is to wait for them to update the program, or for you to revert the newer drivers to something older.

 

[Caveman]

That just means that the program ran into an issue it wasn't expecting.
So, the fix is to wait for them to update the program, or for you to revert the newer drivers to something older.

Makes sense in the context of the little I could find out there about it... Others who had the issue were programmers who got that same errors on their programs.

That said, I am using the latest nvidia drivers but one would think there would be thousands? of others with the issue who are using NV inspector.

I'd really love to be able to tweak with it... It appears the last version was released about 1 year ago so I'm not terribly hopeful this will be fixed anytime soon. I was also wondering if something on my machine (or lack thereof) was causing the issue...

 

[stahlhart]

What version of Inspector are you running?

358.91 drivers here, 64-bit Windows 10 (latest 10586 Update), and Inspector 1.9.6.3; the application launches fine.

 

[FFL]

Ok, i give it a shot: Why don't you try to update your current version of the MS .NET Framework, of which mscorlib is a part of. I believe the newest version supported by Windows XP (if you are really still using it) is 4.0. Just search the mircosoft.com homepage for the redistributable setup.

 

[stahlhart]

OP: is the build in question the one in your signature? The latest supported drivers for Windows XP for that hardware is 307.83, either 32 or 64 bit. Is this what you mean by the "latest" drivers in this context?

 

[Caveman]

First, thanks for helping!

My sig rig is ancient... Sorry for misleading. I need to update it with my new machine specs that I just completed building (the one I have the problem with): 4770k, 970 GTX FTW+, a few SSDs, Win 7 64bit, etc...

Vid driver is 358.50
NV inspector is 1.9.7.3 posted on Guru3D, etc...

Ok, i give it a shot: Why don't you try to update your current version of the MS .NET Framework, of which mscorlib is a part of. I believe the newest version supported by Windows XP (if you are really still using it) is 4.0. Just search the mircosoft.com homepage for the redistributable setup.

I verified that on 28Oct, I must have installed Microsoft .NET Framework 4.5.2 because it shows up in "uninstall programs" (though I don't specifically recall doing so) - maybe a Win update?... I then downloaded a "repair" for 4.5.2 (and it really looked like it was doing something as it loaded). But alas, I still get the same issue.

OP: is the build in question the one in your signature? The latest supported drivers for Windows XP for that hardware is 307.83, either 32 or 64 bit. Is this what you mean by the "latest" drivers in this context?

Sorry, using Win7 64bit; sig is old rig.

What version of Inspector are you running?

NV inspector is 1.9.7.3 posted on Guru3D, etc...

358.91 drivers here, 64-bit Windows 10 (latest 10586 Update), and Inspector 1.9.6.3; the application launches fine.

Oh, to be you... This is a rather elusive, irritating issue.

 

[Caveman]

Eureka! It worked!!!!

I noticed the .NET 4.5.2 installed 28Oct was only 38MB as reported by Control Panel/Uninstall Programs. This did not match the download size on the MS website (68MB).

So... I set a restore point and uninstalled it. Then downloaded a fresh copy of the 68MB .NET 4.5.2 (latest) and installed it, rebooted and now Nvidia Inspector opens!!!

Okay, again... Thanks to all who helped out. I should have been a bit more tenacious in solving this one as it wasn't "too hard"... Wondering how I got a corrupt in stall of 4.5.2 though that read like a real install in the control panel... And then did a "repair" to fix it but to no avail. I had some issues earlier on getting Win Updates installed so this looks like it may have been related to that.

I did make an offer and a deal is a deal so... If you think YOU were the one that helped me then send a PM and we can Paypal or something... There appears to be one person that "got the closest"...

Thanks again all.

 

[FFL]

Hey, nice to hear that it was indeed .NET.
Seriously, keep your cash, it was my pleasure