Nvidia profile inspector ошибка net framework

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Pick a username
Email Address
Password

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Источник

Is Nvidia Inspector Net Framework Error appearing? Would you like to safely and quickly eliminate Nvidia Inspector Net which additionally can lead to a blue screen of death?

When you manually edit your Windows Registry trying to take away the invalid keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!

Troubleshooting Windows XP, Vista, 7, 8 & 10

Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Nvidia Inspector Net Framework Error complications.

Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the Framework error) likewise as any broken hyperlinks inside of your registry.

Issue with

Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.

  • http://www.pchelpforum.com/software-support/67089-nvidia-inspector-monitoring-graphs-net-framework-unhandled-excep.html
  • http://extreme.pcgameshardware.de/windows-7-8-1-und-10-windows-allgemein/268330-nvidia-inspector-beim-runterfahren-error-net-framework.html
  • http://forums.guru3d.com/showthread.php?t=388823
  • http://forum.notebookreview.com/threads/problems-with-nvidia-inspector.707186/

Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.

Fixed:

Symptoms of Nvidia Inspector Net Framework Error
“Nvidia Inspector Net Framework Error” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Nvidia Inspector Net Framework Error when running the exact same system.
“Nvidia Inspector Net Framework Error” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.

Will cause of Nvidia Inspector Net Framework Error

Corrupt obtain or incomplete set up of Windows Operating System software program.

Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).

Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.

Another method maliciously or mistakenly deleted Windows Operating System-related files.

Mistakes this sort of as “Nvidia Inspector Net Framework Error” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.

Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your related registry entry.

Solution to your problem

There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.

Additional Measures:

One. Conduct a Thorough Malware Scan

There’s a probability the Nvidia Inspector Framework Net Error error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Nvidia Inspector Net Framework Error is actually connected to some element of that malicious plan itself.

2. Clean Disk Cleanup

The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an Nvidia error because of possible conflicts or from overloading your hard drive.

Once you clean up these types of files using Disk Cleanup it could not just remedy Nvidia Inspector Net Framework Error, but could also create a dramatic change in the computer’s efficiency.

Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up Nvidia Inspector discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.

Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any Inspector error associated with your temporary files.

How Disk Cleanup can help

1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.

How to repair

3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.

Nvidia Inspector

Manufacturer

Device

Operating System


Nvidia Inspector Net Framework Error


4 out of
5

based on
35 ratings.

 

Источник

Привет!

Когда я запускаю NVIDIA Inspector, он работает нормально, но когда я перехожу в NVIDIA Profile Inspector (встроенную программу, которая может настроить драйвер видеокарты по своему усмотрению), система выдает следующую ошибку:

Проблема Microsoft .NET Framework в NVIDIA Inspector.

Абсолютно ничего не понимаю, но при нажатии на кнопку «Продолжить» запускается NVIDIA Profile Inspector, но, к сожалению, программа полностью отказывается работать, т.е нет ничего кроме пустого экрана, что как минимум делает невозможным что-то изменить.

NVIDIA Profile Inspector с этой ошибкой:

Проблема Microsoft .NET Framework в NVIDIA Inspector.

Я долго думал, писать здесь или писать разработчику NVIDIA Inspector, но что-то мне подсказывает, что ошибка кроется в Microsoft .NET Framework.

В настоящее время у меня установлен Microsoft .NET Framework 4.6. При запуске программа просила установить Microsoft .NET Framework 4.0 или выше, что очень странно.

До свидания!

Вам необходимо обратиться в службу поддержки Nvidia.

Указанная вами программа использует компоненты Microsoft .NET Framework и, судя по ошибке, как-то некорректно обращается к ней.

Если Nvidia сообщает, что проблема в Microsoft .NET Framework, попросите четкий технический комментарий с информацией о том, что не так с Microsoft .NET Framework.

Напишите этот комментарий здесь.

—————————————————————–
Заявление об ограничении ответственности:
Мое мнение может не совпадать с официальной позицией Microsoft.

Источник: https://answers.microsoft.com/ru-ru/windows/forum/all/problem/b9208acc-665b-428b-a8ea-6cf37785da91

Источник

Help please.. I changed my GPU from RTX2060S (went into my brothers computer for Christmas) and have a GTX1060 3g while waiting for RTX3080. Now my Nvidia Profile Inspector gets this error:

«Unhandled exception has occurred in your application.»

«Index and lenght must refer to a location within the string.Parameter name: lenght.»

I have reinstalled driver with DDU, tried older drivers, updated NET Framework.. Turned off AntiVirus.. Nothing works :( Next step is to reinstall Windows 10 from scratch. Can anyone please help? I can’t figure this one out and it annoys me. I have to set Frame Rate Limiter Mode to Allow_all_maxwell for csgo.exe. Thanks alot for all help!

Here are the details:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.

Parameter name: length

at System.String.Substring(Int32 startIndex, Int32 length)

at DmW.DmWcode.NewVersion()

at DmW.DmWcode.NewVersionDownload()

at nspector.frmDrvSettings.frmDrvSettings_Load(Object sender, EventArgs e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Form.OnCreateControl()

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at nspector.frmDrvSettings.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

—————————————-

NVidiaProfileInspectorDmW

Assembly Version: 3.5.0.0

Win32 Version: 3.5.0.0

CodeBase: file:///C:/Users/AAGE/Downloads/NVidiaProfileInspectorDmW-v3.5.0.0-Windows/NVidiaProfileInspectorDmW/NVidiaProfileInspectorDmW.exe

—————————————-

System

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

—————————————-

System.Windows.Forms

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

—————————————-

System.Drawing

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4084.0 built by: NET48REL1

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

—————————————-

System.Xml

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4084.0 built by: NET48REL1

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

—————————————-

System.Configuration

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

—————————————-

System.Core

Assembly Version: 4.0.0.0

Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

—————————————-

Microsoft.GeneratedCode

Assembly Version: 1.0.0.0

Win32 Version: 4.8.4084.0 built by: NET48REL1

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

—————————————-

AutoClosingMessageBox

Assembly Version: 1.0.0.2

Win32 Version: 1.0.0.2

CodeBase: file:///C:/Users/AAGE/Downloads/NVidiaProfileInspectorDmW-v3.5.0.0-Windows/NVidiaProfileInspectorDmW/AutoClosingMessageBox.DLL

—————————————-

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging=»true» />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

  1. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    On downloading the latest version (1.9.7.2) of the inspector, I’m finding myself unable to open up the configuration menu.
    I’m running it as admin obviously, but when I click the button, I get this Unhandled Exception error:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize —> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:WindowsMicrosoft.NETFramework64v2.0.50727Configmachine.config line 134)
    at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
    at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
    at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
    — End of inner exception stack trace —
    at System.Configuration.ConfigurationManager.GetSection(String sectionName)
    at System.Xml.Serialization.XmlSerializerCompilerParameters.Create(String location)
    at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
    at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
    at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
    at ***57555;.***57346;[***57344;](String ***57344;)
    at ***57555;.***57347;[***57344;](String ***57344;)
    at ***57560;.***57384;(Object ***57344;, EventArgs ***57344;)
    at System.Windows.Forms.Form.OnLoad(EventArgs e)
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at ***57560;.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4247 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    —————————————-
    nvidiaInspector
    Assembly Version: 1.9.7.2
    Win32 Version: 1.9.7.2
    CodeBase: file:///C:/Users/Ian/Documents/Inspector/nvidiaInspector.exe
    —————————————-
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4235 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    —————————————-
    System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
    —————————————-
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4236 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    —————————————-
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4235 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    —————————————-
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4246 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    —————————————-
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4246 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    —————————————-

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging=»true» />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Sometimes the config window opens, but it doesn’t have any application profiles in it to edit, being completely blank.
    I’m currently using a GeForce GTX 650 Ti, with the 335.23 WHQL driver.
    I would greatly appreciate any help that I could get.

  2. Hmm, try update/reinstall .net?

  3. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    Right now I do have .net framework 3.5, 4 Multi-targeting pack, and 4.5.1.
    Should I get rid of the old versions and just go with 4.5.1, or what? Trying to repair 4.5.1 at the moment to see if that works.

    EDIT: Apparently I shouldn’t get rid of old versions. Currently reinstalling to try that.

  4. It is using .net 2.0, so you should reinstall that one.

  5. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    Thank you. Also a bit of an update on my issue.

    Apparently uninstalling and reinstalling the .net framework has turned into an epic quest of trying to figure out why version 3.5 won’t install through the download on Microsoft or on Windows Update. I’m halfway tempted to bring out my OS disk and repair it from there, but I’m determined to figure out what the heck’s going on.

  6. Because it is installed by Windows 7 itself, if you are using Windows 7.

    For Windows 8/8.1, the .net 2.0-3.5 can be installed by just enable it in Windows Feature, and it can be fixed by running the SFC /scannow.

    You may want to try SFC /scannow, or just un-tick the .net in Windows Feature, reboot, then tick it back to reinstall. :)

  7. Also 8/8.1 is smart enough to detect when an application needs a certain version, and should pause the application and prompt you to install the version you need automatically. Worked that way for me when I launched Inspector on Windows 8.1.

  8. Yup, this is right, anything in the Programs Feature that need to be enabled will be detected by OS, when running program that need it.

  9. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    Currently using Vista on my home machine, so yeah. I’ve already tried sfc /scannow a few times to no avail.
    Also, every time I try to install framework 3.5 from Windows update, it hits me with a WindowsUpdate_00000643 error.

  10. You just need to Google «windows update 00000643», then you will found the solution.

  11. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    On the first answer, it says to use Windows Fix-It, which also throws up an error, exits, and gives me a DIAG_MATS_NETWORK_global.DiagCab file I don’t exactly know what to do with.

  12. Strange…
    Google MY(Malaysia) give me this.
    http://answers.microsoft.com/en-us/…00000643/d45c9516-6988-4cbf-a36f-7fb12f292352

    Which is for the old MS cleanup tools.

  13. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    That’s the site I tried, and Windows Installer Cleanup Tool doesn’t see .net 3.5 anywhere.

  14. I forgot you are Windows 7 ;P

    Anyways, Method 2 don’t works too?
    How about untick .net and tick it back at the Windows Feature?

  15. Try this:
    1. Run the downloaded dotnet35setup.exe to install .NET Framework 3.5.

    2. Reboot your machine.

    3. Now run Windows Update again, to install post SP1 hotfixes.

    OR

    1. Run dotnet35setup.exe to install .NET Framework 3.5 SP1.

    2. Reboot your computer again.

    3. Now run Windows Update again, to install post SP1 hotfixes.

    Useful links:
    Microsoft .NET 3.5 Framework
    Microsoft .NET 3.5 SP1
    What happened to the Windows Installer Cleanup Utility (MSICUU2.exe)?

    Hope these help!

    Last edited: May 10, 2014

  16. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    Those don’t run, and I’ve tried many times already. They give me this set of errors:

    [05/02/14,09:55:01] Microsoft .NET Framework 3.5 (x64) ‘package’: [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) ‘package’. MSI returned error code 1603
    [05/02/14,09:55:42] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) ‘package’ is not installed.
    [05/02/14,10:25:04] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Error code 1603 for this component means «Fatal error during installation.
    «
    [05/02/14,10:25:05] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Setup Failed on component Optional Component ‘Microsoft .Net Framework 3.0 (x64)’
    [05/02/14,10:25:51] WapUI: [2] DepCheck indicates Optional Component ‘Microsoft .Net Framework 3.0 (x64)’ is not installed.
    [05/02/14,10:53:41] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Error code 3017 for this component means «The requested operation failed. A system reboot is required to roll back changes made.
    «
    [05/02/14,10:53:44] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Component Optional Component ‘Microsoft .Net Framework 3.0 (x64)’ returned an unexpected value.
    [05/02/14,10:53:44] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Return from system messaging: The requested operation failed. A system reboot is required to roll back changes made.

    [05/02/14,10:59:05] Microsoft .NET Framework 3.5 (x64) ‘package’: [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) ‘package’. MSI returned error code 1603
    [05/02/14,10:59:27] Microsoft .NET Framework 3.0SP1 (x64) (CBS): [2] CBS Component is marked to be uninstalled but CBSPackageName is not authored — CCBSComponent::SetManager()
    [05/02/14,10:59:27] Microsoft .NET Framework 3.0SP1 (x64) (CBS): [2] CBS Component can’t be uninstalled as CBSPackageName is not authored — CCBSComponent::SetManager()
    [05/02/14,10:59:38] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) ‘package’ is not installed.
    [05/02/14,12:53:51] Microsoft .NET Framework 3.5 (x64) ‘package’: [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) ‘package’. MSI returned error code 1603
    [05/02/14,12:55:08] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) ‘package’ is not installed.
    [05/02/14,17:55:14] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Error code 87 for this component means «The parameter is incorrect.
    «
    [05/02/14,17:55:15] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Setup Failed on component Optional Component ‘Microsoft .Net Framework 3.0 (x64)’
    [05/02/14,17:55:55] WapUI: [2] DepCheck indicates Optional Component ‘Microsoft .Net Framework 3.0 (x64)’ is not installed.
    [05/02/14,17:58:06] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Error code 87 for this component means «The parameter is incorrect.
    «
    [05/02/14,17:58:07] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Setup Failed on component Optional Component ‘Microsoft .Net Framework 3.0 (x64)’
    [05/02/14,17:58:43] WapUI: [2] DepCheck indicates Optional Component ‘Microsoft .Net Framework 3.0 (x64)’ is not installed.
    [05/02/14,18:01:12] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Error code 87 for this component means «The parameter is incorrect.
    «
    [05/02/14,18:01:12] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Setup Failed on component Optional Component ‘Microsoft .Net Framework 3.0 (x64)’
    [05/02/14,18:03:22] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Error code 87 for this component means «The parameter is incorrect.
    «
    [05/02/14,18:03:22] Optional Component ‘Microsoft .Net Framework 3.0 (x64)’: [2] Setup Failed on component Optional Component ‘Microsoft .Net Framework 3.0 (x64)’
    [05/02/14,18:03:53] WapUI: [2] DepCheck indicates Optional Component ‘Microsoft .Net Framework 3.0 (x64)’ is not installed.
    [05/06/14,08:42:27] Microsoft .NET Framework 3.5 (x64) ‘package’: [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) ‘package’. MSI returned error code 1603
    [05/06/14,08:43:06] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) ‘package’ is not installed.
    [05/07/14,18:57:35] Microsoft .NET Framework 3.5 (x64) ‘package’: [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) ‘package’. MSI returned error code 1603
    [05/07/14,18:58:02] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) ‘package’ is not installed.
    [05/10/14,12:32:10] Microsoft .NET Framework 3.5 (x64) ‘package’: [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) ‘package’. MSI returned error code 1603
    [05/10/14,12:32:30] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) ‘package’ is not installed.

    I’m running Vista Home Premium, not 7 or 8.
    But I’ll try those again.

  17. Yup, but it can be changed in Vista sp2, if I am right.:)

  18. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    Okay, good news bad news update.

    Good news: I managed to get .Net Framework 3.5 reinstalled! Just had to delete the Vista SP1 update, and run the Upgrade option from the CD. All my files are still in place, too.
    Bad news: Nothing changed, an error keeps coming up in the Inspector.

  20. Rekenber
    New Member

    Messages:
    9
    Likes Received:
    0
    GPU:

    GeForce GTX 650 Ti 1023mb

    Okay, sorry for neglecting this thread for so long.

    But for some reason, when I started it up today to see if some time away from the problem would work, it actually went to the profile config screen with no problems or errors.

    I wish I could say what changed with Windows Update or anything in the .NET install/uninstallation I’ve been doing, but hey it works now.

    Sorry I can’t provide a more detailed answer.

Share This Page

Инструкции

Время чтения 3 мин.Просмотры 1.4k.Опубликовано 05.03.2022

Утилита для настройки, разгона и мониторинга видеокарты Nvidia Inspector иногда не работает должным образом: не запускается, выдаёт ошибки, не отображает данные о видеокарте, не сохраняет настройки. Рассмотрим, что делать при появлении проблем в процессе эксплуатации приложения.

Содержание

  1. Ошибка «DRS_SaveSettings failed»
  2. Проблемы с сохранением настроек
  3. Программа не изменяет напряжение
  4. Не отображается информация

Ошибка «DRS_SaveSettings failed»

При нажатии кнопки «Продолжить» после внесения изменений в конфигурацию видеокарты появляется ошибка с текстом «Необрабатываемое исключение в приложении».

Решение:

  1. В каталоге «%programfiles%NVIDIA Corporation» удалите директорию «Drs». Если её нет, припустите шаг.
  2. Удалите драйвер видеокарты через Display Driver Uninstaller.
  3. После перезагрузки компьютера установите его заново вместе с PhysX, но без 3D-драйвера.
  4. Инсталлируйте свежий пакет GeForce Experience.
  5. В GeForce Experience откройте «Панель управления», в разделе «Глобальных параметров» выберите «Высокопроизводительный процессор…», после в списке укажите целевое приложение (игру).

Если не поможет:

  • Увеличьте размер файла подкачки до 5 – 8 ГБ.
  • Обновите Visual C++ и DirectX.

Проблемы с сохранением настроек

Иногда после клика по кнопке «Apply Clocks & Voltage» Нвидиа Инспектор не сохраняет изменения.

Откройте свойства ярлыка или исполняемого файла для запуска игры, во вкладке «Совместимость» активируйте опцию «Запускать/Выполнять эту программу от имени…», нажмите «ОК». То же проделайте для файла «nvcplui.exe», расположенного в каталоге «%Programfiles%NVIDIA CorporationControl Panel Client».

совместимость

После этого, как правило, Нвидиа Инспектор больше не сбрасывает настройки.

Программа не изменяет напряжение

Если приложение не меняет вольтаж через графический интерфейс, воспользуйтесь командной строкой. Запустите её от имени администратора в каталоге с исполняемым файлом программы (через правый клик по папке) и выполните команду:

nvidiaInspector.exe -lockVoltagePoint:0,850000

Командную строку можно запустит через Win + X или иным способом, тогда укажите полный путь к файлу «nvidiaInspector.exe». После двоеточия введите напряжение в вольтах.

командная строка

Для изменения вольтажа при каждом запуске компьютера нужно создать bat-файл и поместить его в папку «Автозапуск».

Создайте текстовый файл через правый клик по пустому месту в окне Проводника либо на Рабочем столе, измените его расширение на «bat», откройте для редактирования через Блокнот, вставьте команду вида:

start c:nvidiainspectornvidiaInspector.exe -lockVoltagePoint:0,850000

файл bat

Сохраните изменения и переместите файл в каталог «shell:startup».

shell:startup

Также способ выручит, если в Nvidia Inspector недоступен voltage при условии, что устройство поддерживает управление напряжением. В ином случае воспользуйтесь аналогом, например, MSI Afterburner.

Не отображается информация

Иногда программа не показывает данные о видеокарте.

нет данных о видеокарте

Убедитесь, что у вас графический чип от Nvidia, для него установлена последняя версия драйвера. На ноутбуке с двумя видеокартами нужно активировать устройство от Нвидиа в панели управления видеочипом. Часто это «Высокопроизводительный процессор Nvidia».

Высокопроизводительный процессор Nvidia

Подробная информация об использовании оперативной
(JIT) отладки вместо данного диалогового
окна содержится в конце этого сообщения.

************** Текст исключения **************
System.InvalidOperationException: В документе XML (0, 0) присутствует ошибка. —> System.Xml.XmlException: Отсутствует корневой элемент.
в System.Xml.XmlTextReaderImpl.Throw(Exception e)
в System.Xml.XmlTextReaderImpl.ParseDocumentContent()
в System.Xml.XmlReader.MoveToContent()
в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderUserSettings.Read4_UserSettings()
— Конец трассировки внутреннего стека исключений —
в System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
в System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
в nspector.Common.Helper.XMLHelper1.DeserializeFromXmlString(String xml) в nspector.Common.Helper.XMLHelper1.DeserializeFromXMLFile(String filename)
в nspector.Common.Helper.UserSettings.LoadSettings()
в nspector.frmDrvSettings.LoadSettings()
в nspector.frmDrvSettings.frmDrvSettings_Load(Object sender, EventArgs e)
в System.Windows.Forms.Form.OnLoad(EventArgs e)
в System.Windows.Forms.Form.OnCreateControl()
в System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
в System.Windows.Forms.Control.CreateControl()
в System.Windows.Forms.Control.WmShowWindow(Message& m)
в System.Windows.Forms.Control.WndProc(Message& m)
в System.Windows.Forms.Form.WmShowWindow(Message& m)
в nspector.frmDrvSettings.WndProc(Message& m)
в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Загруженные сборки **************
mscorlib
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

nvidiaProfileInspector
Версия сборки: 2.3.0.13
Версия Win32: 2.3.0.13
CodeBase: file:///C:/Users/gstru/Downloads/programm/nvidiaProfileInspector/nvidiaProfileInspector.exe

System
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Windows.Forms
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Xml
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Configuration
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4320.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

Microsoft.GeneratedCode
Версия сборки: 1.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Версия сборки: 1.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.xml.resources
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.resources/v4.0_4.0.0.0_ru_b77a5c561934e089/System.Xml.resources.dll

mscorlib.resources
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_ru_b77a5c561934e089/mscorlib.resources.dll

System.Windows.Forms.resources
Версия сборки: 4.0.0.0
Версия Win32: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_ru_b77a5c561934e089/System.Windows.Forms.resources.dll

************** Оперативная отладка (JIT) **************
Для подключения оперативной (JIT) отладки файл .config данного
приложения или компьютера (machine.config) должен иметь
значение jitDebugging, установленное в секции system.windows.forms.
Приложение также должно быть скомпилировано с включенной
отладкой.

Например:

При включенной отладке JIT любое необрабатываемое исключение
пересылается отладчику JIT, зарегистрированному на данном компьютере,
вместо того чтобы обрабатываться данным диалоговым окном.

Источник

Понравилась статья? Поделить с друзьями:
  • Nvidia nodejs share windows ошибка
  • Nvidia profile inspector выдает ошибку
  • Nvidia geforce experience произошла ошибка при установке драйвера
  • Nvidia platform controller and framework ошибка 31
  • Nvidia geforce experience произошла ошибка попробуйте перезагрузить компьютер