NVSlimmer - NVIDIA driver slimming utility

Utter bullshit. He just has a corporative directive to defend data mining GF Experience probably. There is no way a driver can "mess up your card" permanently, let alone official but just cut down driver, no way.

 

bullshit from him

 

Whether the driver is slimmed or not doesn’t change the fact it’s still the same driver being installed.

What’s slimmed you could say are the utilities/apps that are normally installed together with the driver.

One could also unpack the driver file and point to the driver folder from device manager and install the driver by hand …

 

Of course it can. For example, if it prevents the fans from functioning correctly and the card overheats due to it (there was an infamous Nvidia driver in the past that actually managed to kill cards this way, although it was a couple of generations back). It isn't very likely, though.

 

and maybe meteorit hit me...still bullshit
and be honest normaly hot GK just start thermal throtling and at the end going to OFF without any damage
everything its possible but still some thing is bullshit
simple is more filosoficaly like IRL posible
even meteorit possible hit my GK and destroy her

 

A driver can and could, but when there’s no driver override then card controls itself, the fans especially.

The slimmed driver is the same driver, it’s the same files, signed and verified, nothing changes.

The only reason I would ever see a point of failure was if there were calls outside the driver to something installed by the package that was no longer installed. I hope they don’t do anything like that.

 

13900k is crashing out with NVSlimmer

8P 8HT 16E = Crash
8P 8HT 11E = Fine
8P 8HT 12E = Crash
8P 8HT 8E = Fine
8P 8HT 9E = Fine
8P 0HT 16E = Fine
8P 3Ghz 8HT 16E 3Ghz = Crash

27 Threads = Fine
28 Threads+ = Crash

Win10 22H2

It has taken me hours to narrow this down
and about 250GB of writes to my SSD.. unpacking drivers and trying to repack
thinking i was unstable

It crashes in the repack process

Code:

Application: NVSlimmer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception

Server stack trace:
   at NVSlimmer.DriverManager.Repackage(String fileName)
   at NVSlimmer.Form1.RepackageAsync(String fileName)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(System.Runtime.Remoting.Messaging.Message, Boolean)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(System.Object, System.Runtime.Remoting.Proxies.MessageData ByRef)
   at NVSlimmer.Form1+DlgRepackageAsync.EndInvoke(System.IAsyncResult)
   at NVSlimmer.Form1.RepackageCallback(System.IAsyncResult)
   at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
   at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall()
   at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Code:

Faulting application name: NVSlimmer.exe, version: 0.13.0.0, time stamp: 0x6234167a
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2193, time stamp: 0xba4cdd4a
Exception code: 0xe0434352
Fault offset: 0x0012e022
Faulting process ID: 0x19c8
Faulting application start time: 0x01d8ef9101cf1376
Faulting application path: D:\NVSlimmer_v0.13\NVSlimmer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: e7dd49b7-5399-423e-8fab-9b4d80bdd99d
Faulting package full name:
Faulting package-relative application ID: 

 

Your cpu is plain unstable, nvslimmer is fine on 32 thread ryzens.

 

its not its either an nvslimmer bug or .net bug or Win10 22H2 bug

I can run all cores at 800mhz and the ram at 2166 it still does it

It has passed 30000% karhu memory test
and is linpack stable

 

you understand that clock speeds are just one of many area's a cpu can demonstrate silicon flaws?

theres hundreds of points of failure in a modern cpu.

 

its a bug my guy

i would bet its 7Zsfxmm last fixed by chrislake thats causing it

as thats what nvslimmer uses

https://github.com/chrislake/7zsfxmm/releases/tag/1.7.1.3901

 

I was just going to add this ... @Astyanax

I think you're trigger happy to point to flaws in silicone when it could be other issues, such as simple software bugs

Remember that idle TDR I had,- well MSI worked with NVIDIA and the 526.47 fixed the issues.
It was an issue that was there pretty much since 472.xx drivers so for almost a year.

I think it related to this bug in the end, but it didn't matter if the HDMI was secondary monitor off,
or simply the primary and single monitor but the input was switched to another source:

[RTX 30 series] PC monitor may not wake from display sleep when GPU is also connected to an HDMI 2.1 TV, and the TV is powered off. [3645633]

 

except the 7zsfxmm being blamed has no issues with 32 and 64 thread processors.

fix the cpu.

 

I didn't say the issue was with 7zsfxmm, I would check and verify .NET installation as well as Visual C++ libraries ...
https://www.majorgeeks.com/content/...n_the_application_at_location_0x77312c1a.html

I guess one could always stress test CPU and run a RAM test, but I'm guessing there would be other issues if that was the case.

 

Try:

https://www.majorgeeks.com/content/...n_the_application_at_location_0x77312c1a.html

Also, what version of .NET framework are you using ?
Could be too old ...

 

For reference I think these are the newest versions, well might not be, but that's what I have installed



Note: I also always remove any duplicates that are older than the newest, I've never run into any issues by doing that.

 

Could be as simple as Windows 10 + E cores. Windows 10 thread director is not exactly working as intended for all workloads when you add E cores to the mix. You should run Windows 11 with Intel cpus with P+E cores, sadly.

Same here. Never had any issues removing the older duplicates. You can find visual c++ redist all in one compilations at TPU. They seem to be updated a few times a year.

I have the same versions installed as your screenshot btw.

 

All the cores have the same architectural capabilities right down to instruction sets, all thats efficient about e cores is they are lower clocked.

Remember that these are hyperthreaded processes sharing multiple levels of cache, silicon flaws can exist (and be worked around) that contribute to certain processing patterns when under high load, Zen 1 had the segfault bug that affected chips now experience as windows 10 bsods, skylake had the hyperthreading crashes.

underclocking the smt/alu cores is one thing, what about the ringbus and uncores?

 

I have fixed it thanks for the suggestions escape75
Astyanax thanks for nothing your an ass hat btw, shouldnt you be on reddit

Replaced 7zip with 22.1.0.0
7za.dll
7za.exe
7zxa.dll

Uninstalled
Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.31.31103
Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.31.31103
Rebooted
Installed
Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.32.31332
Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.32.31332

One of them fixed it

 

Thread director works just fine its all FUD from youtubers

My foreground processes goto the P cores and background goto the E cores
Super fine by me

Game is on the P
OS is on the E..