hvsett Posted June 28, 2014 Posted June 28, 2014 Yesterday I installed PDN 4.0 on my desktop (x64) and laptop (x86), both Win7. It works great on the desktop, but not at all on the laptop. The laptop is an ASUS, 2GB RAM, with a dual graphics card built-in: low-level ASUS software will autoswitch between standard Intel for low-energy situations, and better Nvidia for graphics-intensive work. PDN 3.5.11 worked fine here. PDN 4.0 did install without problems. But every time I try to actually start PDN 4.0 on this laptop, the borders of the main PDN window and the four tool windows will appear for a split-second on screen, and then before these outlined windows are even filled in, PDN crashes right away (I mailed a report as requested). The crash reports all note PDN addressing inaccessible memory, and suggest "corrupt memory" as a possible cause. I can't believe that, afaik there's nothing wrong with the laptop's memory. Just to make sure I ran the Windows Memory Check tool -- it reports no errors at all. Nor do I have any "weird" software running that would mess up memory allocations. My own hunch is rather there's some kind of hardware acceleration error going on here, possibly caused by the laptop's dual-graphics-card setup. Problem is, if PDN 4.0 is using HA by default (even it has an option somewhere to switch that off) I cannot change that setting, because PDN keeps crashing before I can get to any menu. Still I'd like to find out if this may indeed be the issue here. So my question is: does PDN 4.0 use HA by default when it starts up? And if so, is there a way to force PDN to start up without using any kind of hardware acceleration? By commandline option perhaps? Or by changing some registry entry? INI file? Thanks for any helpful idea! Quote
Shawnyall Posted June 28, 2014 Posted June 28, 2014 I have no real experience troubleshooting this program and its errors, but have you updated your .NET Framework to 4.5? Quote
Rick Brewster Posted June 28, 2014 Posted June 28, 2014 Can you include the crash report here? Just surround it with code tags. like this Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html
cc42 Posted June 28, 2014 Posted June 28, 2014 Just installed 4.0, Program stops working when I try to get the photo to work on. I am sorry I had to delete old Paint.net. Quote
hvsett Posted June 29, 2014 Author Posted June 29, 2014 Below is the latest crash report, identical crash. Before replicating the crash I made a new, clean install of PDN 4.0 instead of upgrading 3.5, so this eliminates any potential problems with old plugins that 3.5 had in its Effects directory. I also checked the laptop for .NET 4.5 (is installed) and just to make sure, I let Microsoft's own .NET Framework Repair Tool make a full run. To eliminate any other factors, I quit nearly all other software that ran in the background before starting PDN. As for the dual-graphics-card setup, the laptop was on AC, not on battery while replicating the crash, so it was using the Nvidia. From the crash report it looks like PDN in this situation saw just the Nvidia, no Intel graphics, so probably the dual-graphics-card thing is not the issue like I thought first. The log: This text file was created because paint.net crashed. Please e-mail this to crashlog4@getpaint.net so we can diagnose and fix the problem. Application version: paint.net 4.0 (Final 4.0.5288.36565) Time of crash: 29/06/2014 10:52:24 Application uptime: 00:00:09.9840176 Application state: Running Working set: 60,012 KiB Install directory: C:\Program Files\Paint.NET Current directory: C:\Program Files\Paint.NET OS Version: 6.1.7601.65536 Service Pack 1 Workstation x86 .NET version: CLR 4.0.30319.18444 x86, FX 4.0 4.5 Processor: 4x "Intel(R) Atom(TM) CPU D525 @ 1.80GHz" @ ~1800MHz (DEP, SSE, SSE2, SSE3, SSSE3) Physical memory: 2037 MB Hardware acceleration: True Video card: NVIDIA ION , NVIDIA ION UI animations: True UI DPI: 96.00 dpi (1.00x scale) UI theme: Aero/Aero (Aero.msstyles) Updates: False, 01/01/0001 Locale: pdnr.c: en-US, hklm: en-US, hkcu: en-US, cc: en-IE, cuic: en-US Exception details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at PaintDotNet.SystemLayer.Native.x86.Direct2D.D2DFactory.CreateHwndRenderTarget(RenderTargetProperties renderTargetProperties, HwndRenderTargetProperties hwndRenderTargetProperties) at PaintDotNet.Direct2D.Proxies.Direct2DFactoryProxy.CreateHwndRenderTarget(RenderTargetProperties renderTargetProperties, HwndRenderTargetProperties hwndRenderTargetProperties) in D:\src\pdn\paintdotnet\src\Base\Direct2D\Proxies\Direct2DFactoryProxy.cs:line 76 at PaintDotNet.Controls.Direct2DControlHandler.RecreateRenderTarget() in D:\src\pdn\paintdotnet\src\Framework\Controls\Direct2DControlHandler.cs:line 360 at PaintDotNet.Controls.Direct2DControlHandler.RelayGdiPaintImpl(GdiPaintContext ctx) in D:\src\pdn\paintdotnet\src\Framework\Controls\Direct2DControlHandler.cs:line 399 at PaintDotNet.Controls.Direct2DControlHandler.RelayGdiPaint(GdiPaintContext ctx) in D:\src\pdn\paintdotnet\src\Framework\Controls\Direct2DControlHandler.cs:line 384 at PaintDotNet.Controls.Direct2DControl.OnGdiPaint(GdiPaintContext ctx) in D:\src\pdn\paintdotnet\src\Framework\Controls\Direct2DControl.cs:line 228 at PaintDotNet.SystemLayer.GdiPaintControl.PaintDotNet.SystemLayer.IGdiPaintHost.OnGdiPaint(GdiPaintContext ctx) in D:\src\pdn\paintdotnet\src\SystemLayer\GdiPaintControl.cs:line 133 at PaintDotNet.SystemLayer.GdiPaintHandler.OnWmPaint(Message& m) in D:\src\pdn\paintdotnet\src\SystemLayer\GdiPaintHandler.cs:line 172 at PaintDotNet.SystemLayer.GdiPaintHandler.RelayWndProc(Message& m) in D:\src\pdn\paintdotnet\src\SystemLayer\GdiPaintHandler.cs:line 222 at PaintDotNet.SystemLayer.GdiPaintControl.WndProc(Message& m) in D:\src\pdn\paintdotnet\src\SystemLayer\GdiPaintControl.cs:line 113 at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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) Managed assemblies: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll PaintDotNet, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.exe PaintDotNet.Base, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.Base.dll System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.dll PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 @ C:\windows\Microsoft.Net\assembly\GAC_32\PresentationCore\v4.0_4.0.0.0__31bf3856ad364e35\PresentationCore.dll System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll PaintDotNet.Core, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.Core.dll System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll PaintDotNet.SystemLayer, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.SystemLayer.dll PaintDotNet.Framework, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.Framework.dll PaintDotNet.Resources, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.Resources.dll PaintDotNet.Data, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.Data.dll PaintDotNet.Effects, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.Effects.dll PaintDotNet.SystemLayer.Native.x86, Version=4.0.5288.36565, Culture=neutral, PublicKeyToken=null @ C:\Program Files\Paint.NET\PaintDotNet.SystemLayer.Native.x86.dll System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll Native modules: C:\Program Files\Paint.NET\PaintDotNet.exe, version=4.0.5288.36565 C:\windows\SYSTEM32\ntdll.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\SYSTEM32\MSCOREE.DLL, version=4.0.40305.0 (Main.040305-0000) C:\windows\system32\KERNEL32.dll, version=6.1.7601.18015 (win7sp1_gdr.121129-1432) C:\windows\system32\KERNELBASE.dll, version=6.1.7601.18015 (win7sp1_gdr.121129-1432) C:\windows\system32\ADVAPI32.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\msvcrt.dll, version=7.0.7601.17744 (win7sp1_gdr.111215-1535) C:\windows\SYSTEM32\sechost.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\RPCRT4.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\system32\SHLWAPI.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\GDI32.dll, version=6.1.7601.18275 (win7sp1_gdr.131002-1533) C:\windows\system32\USER32.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\LPK.dll, version=6.1.7601.18177 (win7sp1_gdr.130605-1534) C:\windows\system32\USP10.dll, version=1.0626.7601.18454 (win7sp1_gdr.140424-1533) C:\windows\system32\IMM32.DLL, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\MSCTF.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\nvinit.dll, version=8.17.12.5743 C:\Program Files\NVIDIA Corporation\CoProcManager\detoured.dll, version= C:\Program Files\NVIDIA Corporation\CoProcManager\nvd3d9wrap.dll, version=8.17.12.5743 C:\windows\system32\SETUPAPI.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\CFGMGR32.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\OLEAUT32.dll, version=6.1.7601.17676 C:\windows\system32\ole32.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\DEVOBJ.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\d3d8.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\VERSION.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\d3d8thk.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\dwmapi.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\d3d9.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\Program Files\NVIDIA Corporation\CoProcManager\nvdxgiwrap.dll, version=8.17.12.5743 C:\windows\system32\dxgi.dll, version=6.2.9200.16492 (win8_gdr_oobssr.130113-0015) C:\windows\system32\d3d10.dll, version=6.2.9200.16492 (win8_gdr_oobssr.130113-0015) C:\windows\system32\d3d10core.dll, version=6.2.9200.16492 (win8_gdr_oobssr.130113-0015) C:\windows\system32\d3d11.dll, version=6.2.9200.16570 (win8_gdr.130327-1526) C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll, version=4.0.30319.18444 built by: FX451RTMGDR C:\windows\system32\MSVCR110_CLR0400.dll, version=11.00.50938.18408 built by: FX451RTMGREL C:\windows\assembly\NativeImages_v4.0.30319_32\mscorlib\ce5f61c5754789df97be8dc991c47d07\mscorlib.ni.dll, version=4.0.30319.18444 built by: FX451RTMGDR C:\windows\system32\CRYPTBASE.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\uxtheme.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\assembly\NativeImages_v4.0.30319_32\System\ff26cc03e6d57d8abd13b990332e67c6\System.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\assembly\NativeImages_v4.0.30319_32\WindowsBase\acf97bfe2a931d4a47253b26b7218991\WindowsBase.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\system32\CRYPTSP.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\rsaenh.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\5cd2aee5e7c07227c694d89219688ab3\System.Drawing.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\assembly\NativeImages_v4.0.30319_32\PresentationCore\a74542efbeb46445949a39026c501132\PresentationCore.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\a4b45c44490c75bc2fb22780e7ef087d\PresentationFramework.ni.dll, version=4.0.30319.18408 C:\windows\assembly\NativeImages_v4.0.30319_32\System.Core\dce99d8de14d8a015313db98c72552ee\System.Core.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet.Base\a15a84296e21921f837ad98c5f65a5c4\PaintDotNet.Base.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\f4f6ee0df2aa4189bf36e6335cb92761\System.Windows.Forms.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet500b2e4f#\d8cd7d86860a05cf2b5bcf4213ef3135\PaintDotNet.SystemLayer.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet.Core\2b27eec8fdf77fbfcccebd3269149a20\PaintDotNet.Core.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet26779e70#\dbd006bc03dec21a059d623e2cd0e319\PaintDotNet.Resources.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet7afaaa15#\0a0e893a68479d531939a9f525f5bca0\PaintDotNet.Framework.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet.Data\1a9cfaf8618c058902f4621f1537188f\PaintDotNet.Data.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet.Effects\6de2ff6753a91bd6b4311b6be6ce751c\PaintDotNet.Effects.ni.dll, version=4.0.5288.36565 C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNet\6325f413fe1faf9892b470f2905b30cf\PaintDotNet.ni.exe, version=4.0.5288.36565 C:\windows\system32\dwrite.dll, version=6.2.9200.16492 (win8_gdr_oobssr.130113-0015) C:\windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\system32\shell32.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll, version=4.0.30319.18444 built by: FX451RTMGDR C:\windows\assembly\NativeImages_v4.0.30319_32\PaintDotNetc8826738#\9a78864ff4f813b702681c1d5bbf5380\PaintDotNet.SystemLayer.Native.x86.ni.dll, version=4.0 C:\Program Files\Paint.NET\PaintDotNet.SystemLayer.Native.x86.dll, version=4.0 C:\windows\system32\MSVCR100.dll, version=10.00.40219.325 C:\windows\system32\VCOMP100.DLL, version=10.00.40219.325 built by: SP1LDR C:\windows\system32\MSVCP100.dll, version=10.00.40219.325 C:\windows\system32\PROPSYS.dll, version=7.00.7600.16385 (win7_rtm.090713-1255) C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll, version=6.1.7601.18455 (win7sp1_gdr.140425-1537) C:\windows\system32\WINTRUST.dll, version=6.1.7601.18205 (win7sp1_gdr.130708-1532) C:\windows\system32\CRYPT32.dll, version=6.1.7601.18277 (win7sp1_gdr.131005-0934) C:\windows\system32\MSASN1.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\profapi.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) C:\windows\system32\CLBCatQ.DLL, version=2001.12.8530.16385 (win7_rtm.090713-1255) C:\windows\System32\UIAnimation.dll, version=6.2.9200.16492 (win8_gdr_oobssr.130113-0015) C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll, version=6.10 (win7_rtm.090713-1255) C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\comctl32.dll, version=6.10 (win7_rtm.090713-1255) C:\windows\system32\WindowsCodecs.dll, version=6.2.9200.16809 (win8_gdr.140127-1505) C:\windows\system32\d2d1.dll, version=6.2.9200.16492 (win8_gdr_oobssr.130113-0015) C:\windows\system32\wtsapi32.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\WINSTA.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\D3D10Warp.dll, version=6.2.9200.16783 (win8_gdr.131220-1803) C:\windows\assembly\NativeImages_v4.0.30319_32\System.Xaml\3fe705796c6a41d4889d9001d1c56af8\System.Xaml.ni.dll, version=4.0.30319.18408 built by: FX451RTMGREL C:\windows\system32\RpcRtRemote.dll, version=6.1.7601.17514 (win7sp1_rtm.101119-1850) C:\windows\system32\nvumdshim.dll, version=8.17.12.5743 C:\windows\system32\nvapi.dll, version=8.17.12.5743 C:\windows\system32\nvwgf2um.dll, version=8.17.12.5743 C:\windows\system32\igdumdx32.dll, version=8.14.10.2230 C:\windows\system32\igdumd32.dll, version=8.14.10.2230 C:\windows\system32\psapi.dll, version=6.1.7600.16385 (win7_rtm.090713-1255) ------------------------------------------------------------------------------ Quote
hvsett Posted July 3, 2014 Author Posted July 3, 2014 Deafening silence so far... I wonder if someone would be able to say if the above crash log does suggest any cause of why PDN 4.0 keeps crashing? Quote
DrewDale Posted July 3, 2014 Posted July 3, 2014 Perhaps this line from your crash log ? Exception details:System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Quote
Rick Brewster Posted July 3, 2014 Posted July 3, 2014 First, please do the standard troubleshooting things: get all your Windows Updates and make sure all of your drivers are up-to-date. This looks like it's caused by a serious problem in your video card driver -- the crash is internal to Direct2D, and not caused by Paint.NET. I'm working on a fix that will automatically disable hardware acceleration when this happens. For now, you can disable hardware acceleration by editing the registry. Create a string value in HKEY_CURRENT_USER \ Software \ Paint.NET called "UI/EnableHardwareAcceleration" and set it equal to "False" (without quotes). Alternately, download the attached ZIP which has a REG that you can just double click on and it'll do that for you automatically. Here's what the .REG has inside of it: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Paint.NET] "UI/EnableHardwareAcceleration"="False" PDN4_DisableHardwareAcceleration.zip Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html
hvsett Posted July 3, 2014 Author Posted July 3, 2014 Thanks people for trying to help! But... (1) I cannot believe something is wrong with my laptop's memory. As said before, I ran the memtest tool which found no errors. Besides, if something was wrong with my RAM, wouldn't this cause problems with other memory-intensive programs as well? All other software runs without any problem of this kind... (2) I successfully merged the registry line that switches off hardware acceleration. Unfortunately, after having made this change, PDN 4.0 still keeps crashing in exactly the same way, right after starting it up, with its window frames already visible but before the windows have been filled in. So, I'm afraid the problem has not been solved. Quote
Ego Eram Reputo Posted July 3, 2014 Posted July 3, 2014 This looks like it's caused by a serious problem in your video card driver -- the crash is internal to Direct2D, and not caused by Paint.NET. Try updating your video card driver. Quote ebook: Mastering Paint.NET | resources: Plugin Index | Stereogram Tut | proud supporter of Codelab plugins: EER's Plugin Pack | Planetoid | StickMan | WhichSymbol+ | Dr Scott's Markup Renderer | CSV Filetype | dwarf horde plugins: Plugin Browser | ShapeMaker
Rick Brewster Posted July 3, 2014 Posted July 3, 2014 I didn't say something was wrong with your laptop's memory. I said the video card's driver is buggy. Big difference! Can you please post the new crash log? Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html
hvsett Posted July 4, 2014 Author Posted July 4, 2014 Dear Rick, thanks for giving this your attention (btw my memory remark was not commenting to you but to the previous poster). The crashing problem has been solved now, though there still appears to be a strange HA problem. I downloaded the correct Nvidia driver installer software and just to make sure, I had it make a clean install instead of an upgrade. Your idea was right: PDN 4.0 now starts without crashing! But, when hardware acceleration is used, there still is a weird problem: trail-like artifacts. Like, when you select the paint brush and then just move the crosshair pointer across the screen (without pressing the left mouse button to actually draw) it will leave a kind of irregularly dotted black trail everywhere you move the pointer, both within the picture and outside the image canvas. This weird behavior does not happen if I switch off PDN hardware acceleration in the registry. The Nvidia control panel has an option that lets the user switch all kinds of functions on or off, individually for any specific program or process. Do I need to adjust some of the default settings specifically for PDN, to make hardware acceleration work properly? Thanks once again! Henk Quote
Rick Brewster Posted July 5, 2014 Posted July 5, 2014 The artifacts you're seeing are another known issue with various video cards. I'm not even sure if it's fixable -- it may be a serious bug in Direct2D. What happens when you switch to something like a selection tool and draw a selection? Do you still get artifacts? I had someone report that they got all the trails and stuff when they start up (and the paintbrush tool is active), but they switched to another tool and it went away ... and I think they even created a new image and the artifacts were gone then too. If you can find some situation where the artifacts aren't there, that'll help. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html
Rick Brewster Posted July 24, 2014 Posted July 24, 2014 But, when hardware acceleration is used, there still is a weird problem: trail-like artifacts. Like, when you select the paint brush and then just move the crosshair pointer across the screen (without pressing the left mouse button to actually draw) it will leave a kind of irregularly dotted black trail everywhere you move the pointer, both within the picture and outside the image canvas. BTW, this should be fixed since 4.0.1 (the latest version is now 4.0.3). Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.