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.
-
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. -
Hmm, try update/reinstall .net?
-
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.
-
It is using .net 2.0, so you should reinstall that one.
-
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.
-
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.
-
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.
-
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.
-
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. -
You just need to Google «windows update 00000643», then you will found the solution.
-
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.
-
Strange…
Google MY(Malaysia) give me this.
http://answers.microsoft.com/en-us/…00000643/d45c9516-6988-4cbf-a36f-7fb12f292352Which is for the old MS cleanup tools.
-
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.
-
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? -
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
-
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. -
Yup, but it can be changed in Vista sp2, if I am right.
-
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. -
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 иногда не работает должным образом: не запускается, выдаёт ошибки, не отображает данные о видеокарте, не сохраняет настройки. Рассмотрим, что делать при появлении проблем в процессе эксплуатации приложения.
Содержание
- Ошибка «DRS_SaveSettings failed»
- Проблемы с сохранением настроек
- Программа не изменяет напряжение
- Не отображается информация
Ошибка «DRS_SaveSettings failed»
При нажатии кнопки «Продолжить» после внесения изменений в конфигурацию видеокарты появляется ошибка с текстом «Необрабатываемое исключение в приложении».
Решение:
- В каталоге «%programfiles%NVIDIA Corporation» удалите директорию «Drs». Если её нет, припустите шаг.
- Удалите драйвер видеокарты через Display Driver Uninstaller.
- После перезагрузки компьютера установите его заново вместе с PhysX, но без 3D-драйвера.
- Инсталлируйте свежий пакет GeForce Experience.
- В 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
Сохраните изменения и переместите файл в каталог «shell:startup».
Также способ выручит, если в Nvidia Inspector недоступен voltage при условии, что устройство поддерживает управление напряжением. В ином случае воспользуйтесь аналогом, например, MSI Afterburner.
Не отображается информация
Иногда программа не показывает данные о видеокарте.
Убедитесь, что у вас графический чип от 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, зарегистрированному на данном компьютере,
вместо того чтобы обрабатываться данным диалоговым окном.