James_Mont

Install Error PaintDotNet.Direct2D.NoHardwareDeviceException (0x8899000B)

Recommended Posts

James_Mont    0

Hi, i never had a single issue with Paint.net in last 2 years, but after the last W10 update (the anniversary one) my Paint.net didn't work anymore.
I tried to reinstall and this error pop up after the file extraction.
I tried to reinstall video card drivers or use compatibility settings but nothing happens.
Seems it can't recognize my video card or something similar.

Here the complete error text.

Spoiler

Le informazioni su come richiamare il debug JIT (Just-In-Time) anziché questa finestra
sono riportate in fondo al messaggio.

************** Testo dell'eccezione **************
PaintDotNet.Direct2D.NoHardwareDeviceException (0x8899000B): ..\Direct2D\D2DFactory.cpp (95) : hr = m_pFactory->CreateDCRenderTarget( &NativeConversions::ToNative(renderTargetProperties), &spDCRenderTarget); (PaintDotNet.Controls.PdnBanner)
   in PaintDotNet.Interop.InteropErrorInfo.ThrowIfError() in D:\src\pdn\src\Base\Interop\InteropErrorInfo.cs:riga 89
   in PaintDotNet.SystemLayer.Native.x64.NativeUtilities.ThrowOnErrorImpl(Int32 hr, SByte* szHr, IUnknown* pFxErrorInfo)
   in PaintDotNet.SystemLayer.Native.x64.Direct2D.D2DFactory.CreateDCRenderTarget(RenderTargetProperties renderTargetProperties)
   in PaintDotNet.Direct2D.Proxies.Direct2DFactoryProxy.CreateDCRenderTarget(RenderTargetProperties renderTargetProps) in D:\src\pdn\src\Base\Direct2D\Proxies\Direct2DFactoryProxy.cs:riga 75
   in PaintDotNet.Controls.Direct2DControlHandler.RecreateRenderTarget(Boolean invalidateControl) in D:\src\pdn\src\Framework\Controls\Direct2DControlHandler.cs:riga 426
   in PaintDotNet.Controls.Direct2DControlHandler.RelayGdiPaintImpl(GdiPaintContext ctx) in D:\src\pdn\src\Framework\Controls\Direct2DControlHandler.cs:riga 500
   in PaintDotNet.Controls.Direct2DControlHandler.RelayGdiPaint(GdiPaintContext ctx) in D:\src\pdn\src\Framework\Controls\Direct2DControlHandler.cs:riga 483
   in PaintDotNet.Controls.Direct2DControl.OnGdiPaint(GdiPaintContext ctx) in D:\src\pdn\src\Framework\Controls\Direct2DControl.cs:riga 347
   in PaintDotNet.SystemLayer.GdiPaintHandler.OnWmPaint(Message& m) in D:\src\pdn\src\SystemLayer\GdiPaintHandler.cs:riga 184
   in PaintDotNet.SystemLayer.GdiPaintHandler.RelayWndProc(Message& m) in D:\src\pdn\src\SystemLayer\GdiPaintHandler.cs:riga 233
   in PaintDotNet.SystemLayer.GdiPaintControl.WndProc(Message& m) in D:\src\pdn\src\SystemLayer\GdiPaintControl.cs:riga 130
   in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Assembly caricati **************
mscorlib
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
SetupFrontEnd
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/SetupFrontEnd.exe
----------------------------------------
PaintDotNet.Core
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/PaintDotNet.Core.DLL
----------------------------------------
System.Windows.Forms
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
PaintDotNet.Base
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/PaintDotNet.Base.DLL
----------------------------------------
PaintDotNet.SystemLayer
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/PaintDotNet.SystemLayer.DLL
----------------------------------------
PaintDotNet.Framework
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/PaintDotNet.Framework.DLL
----------------------------------------
PaintDotNet
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/PaintDotNet.EXE
----------------------------------------
PaintDotNet.Resources
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/PaintDotNet.Resources.DLL
----------------------------------------
WindowsBase
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
System.Core
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
PaintDotNet.SystemLayer.Native.x64
    Versione assembly: 4.16.6315.38530
    Versione Win32: 4.16.6315.38530
    Base di codice: file:///C:/Users/monte/AppData/Local/Temp/PdnSetup/x64/PaintDotNet.SystemLayer.Native.x64.DLL
----------------------------------------
System.Configuration
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Windows.Forms.resources
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
mscorlib.resources
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2046.0 built by: NET47REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_it_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------

************** Debug JIT **************
Per abilitare il debug JIT, è necessario impostare il valore
jitDebugging nella sezione system.windows.forms del file di configurazione
dell'applicazione o del computer (machine.config).
L'applicazione inoltre deve essere compilata con il debug
abilitato.

Ad esempio:

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

Quando il debug JIT è abilitato, tutte le eccezioni non gestite
vengono inviate al debugger JIT registrato nel computer,
anziché essere gestite da questa finestra di dialogo.
 


Anyone have a solution ?

Additional information:
-Windows 10 Home Build 15063.138
-Gpu:Nvidia GT540M Driver: 381.65

PaintDotNet Error.txt

Share this post


Link to post
Share on other sites
Rick Brewster    832

I've been getting a few reports of this "NoHardwareDeviceException" error. The weird thing is that it's happening on code paths which are using Direct2D's software rendering facilities.

 

I honestly have no idea right now, but I'll keep gathering the crash logs to build a pile of evidence and I'll see what I can do from there.

Share this post


Link to post
Share on other sites
James_Mont    0
On 21/4/2017 at 7:03 PM, Rick Brewster said:

I've been getting a few reports of this "NoHardwareDeviceException" error. The weird thing is that it's happening on code paths which are using Direct2D's software rendering facilities.

 

I honestly have no idea right now, but I'll keep gathering the crash logs to build a pile of evidence and I'll see what I can do from there.

Thx for the answer !
I hope u'll find a solution as far as possible !
I'll wait for the next update ;)

Regards James

Share this post


Link to post
Share on other sites
Danialr    0

I ran into the same error after a clean install of Windows 10 and upgrade to Creators Update.

 

Some other problems led me to believe there was a video issue.

 

Error was on a Dell Precision M4600 laptop with Intel HD 3000 and NVidia Quadro 2000M w/Optimus switchable graphics.  NVidia driver 377.11

 

In the NVidia Control Panel --> Set PhysX configuration screen 

     Changed Select a PhysX processor to Auto-select.  (was set to Quadro 2000M)

 

Problem resolved.

 

 

Share this post


Link to post
Share on other sites
James_Mont    0
On 24/4/2017 at 8:48 AM, Danialr said:

I ran into the same error after a clean install of Windows 10 and upgrade to Creators Update.

 

Some other problems led me to believe there was a video issue.

 

Error was on a Dell Precision M4600 laptop with Intel HD 3000 and NVidia Quadro 2000M w/Optimus switchable graphics.  NVidia driver 377.11

 

In the NVidia Control Panel --> Set PhysX configuration screen 

     Changed Select a PhysX processor to Auto-select.  (was set to Quadro 2000M)

 

Problem resolved.

 

 

I tried with every physics settings (it was already on auto-select) but won't work for me :/

Share this post


Link to post
Share on other sites
JNP    0

Nope, didn't work.

Tried to install recommended ver. 368.39.

It started to check system comparability and gave me the message "This NVidia graphics driver is not compatible with this version of windows".

Also made sure  NVidia Control Panel --> Set PhysX configuration screen was set to "Auto-select".

I'm running Lenovo W520 w/Nvidia Quadro 1000M, 64 bit Windows 10 Creator ver. 1703

Edited by JNP

Share this post


Link to post
Share on other sites
Aceos    0

Same issue here.

 

Interestingly, I'm also on a W520 with a Quadro 2000m with Win10 Creators Update.

 

Did a completely clean install of Windows to see if that would help. Nothing. 

 

Any hope of a fix for this? 

 

Cheers,

A

Share this post


Link to post
Share on other sites
James_Mont    0
On 17/6/2017 at 6:48 PM, Rick Brewster said:

Did you install the latest drivers for your Quadro 2000m? From nvidia.com?

any news ?
rolling back the drivers no longer works, idk why...
 

Share this post


Link to post
Share on other sites
Rick Brewster    832

I received this e-mail about this, perhaps someone can give another verification if this works?

 

After upgrading to Windows 10 Creator (over the Education version), Paint.Net stopped working.
I tried many things amongst removing all traces of Paint.Net and PaintDotNet from the registry.
I ended up with no Paint.Net at all. Installation of version 4.0.16 halted on some 'unexpected exception'.
This looks like a message from deep throat MS .Net Framework. I checked the registry and found version 4.7 (460798).

I read numerous mails, questions and post. Some mentioned a NVIDIA issue.
My configuration: a Lenovo W520 with also a NVDIA Quadro 2000M.

==> My work around (after many hours):
- Deactivate the NVIDIA adapter
- Install Paint.Net
- Reactivate NVIDIA
- Run Paint on the Integrated Graphics (Intel HD Graphics 3000)
Hope this can be of help for some of the 'tormented' Paint.Net-lovers.

Who is when going to give a thorough solution and PUBLISH it loud and clear?

Kind regards, Frans

Share this post


Link to post
Share on other sites
Rick Brewster    832

I'm betting that telling the NVIDIA driver to "Run this app on the Integrated Graphs" is the key. This can be done via right-clicking on the Paint.NET shortcut, or through the NVIDIA control panel.

  • Upvote 1

Share this post


Link to post
Share on other sites
mozzis    0
On 7/11/2017 at 10:17 AM, Rick Brewster said:

I'm betting that telling the NVIDIA driver to "Run this app on the Integrated Graphs" is the key. This can be done via right-clicking on the Paint.NET shortcut, or through the NVIDIA control panel.

I tried that as well, it did not work. Where "this app" was the installer program "paint.net.4.0.16.install.exe".

I next ran the installer from the command line with the "/createMSI" option. It runs for awhile before trying to display the stupid banner in the dialog. It will crash there as usual, but by then the MSI files have been created (look for a PaintDotNetMsi folder under the directory where you ran the installer.)

I then installed the MSI using msiexec like:

msiexec /qn /i PaintDotNet_x64.msi. This runs the installer with no user interface.

When this was done, I then went and assigned the Paint.Net application to the integrated graphics card (Intel 400 series I believe)

Now Paint.Net will start.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now