ChrisERAU

Ever since the last big update to Paint.net (v4.0?) sometime last year, Paint.net has been crashing somewhat randomly when I try to load it. It's gotten so bad now that I can't get it to stay open without getting a "Paint.net has stopped working" error message. I'm on Windows 7 64 bit, by the way. Here's what I do: Click Paint.net shortcut Paint.net programs opens Immediately upon opening, the "paint.net has stopped working" error box pops up I'm forced to click "close" on the error message, and paint.net closes When I try to open paint.net by right-clicking on a picture and selecting Open with... > paint.net, paint.net won't even come up. Nothing happens. I ran the .NET framework repair process, updated the nvidia drivers, uninstalled and reinstalled paint.net (v4.05), restarted roughly 10 million times, but none of this solved the issue. Obviously I can't get a bug report from paint.net itself, but I saw what's going on in Windows' Event Viewer: Faulting application name: PaintDotNet.exe, version: 4.5.5454.39504, time stamp: 0x5484cd44 Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24 Exception code: 0xc0000005 Fault offset: 0x00000000000508c5 Faulting process id: 0x140c Faulting application start time: 0x01d05959751f5948 Faulting application path: C:\Program Files\Paint.NET\PaintDotNet.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: b2dc8dca-c54c-11e4-9762-b888e305d191 It's the same error 100% of the time. Is the ntdll.dll corrupt? Please help!

4.0.1 crashed upon opening after a fresh install. Kept crashing every time I tried to start afterwards. I kept trying, and I somehow managed to click settings before the crash dialog appeared, and so here are the diagnostics that were copied: Application paint.net 4.0.1 (Final 4.1.5306.43142) Build Date Saturday, July 12, 2014 Hardware accelerated rendering (GPU) True Animations True DPI 96.00 (1.00x scale) Language en-US OS Windows 7 Service Pack 1 (6.1.7601.65536) .NET Runtime 4.0.30319.18444 Physical Memory 5,982 MB CPU Intel® Core i7-3610QM CPU @ 2.30GHz Architecture x64 (64-bit) Process Mode 64-bit Speed ~2294 MHz Cores / Threads 8 Features DEP, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, XSAVE Video Card Intel® HD Graphics 4000 Dedicated Video RAM 128 MB Dedicated System RAM 0 MB Shared System RAM 1,632 MB Vendor ID 0x8086 Device ID 0x0166 Subsystem ID 0x06471025 Revision 9 LUID 0x00008D15 Flags None Outputs 2 Video Card NVIDIA GeForce GT 640M Dedicated Video RAM 1,990 MB Dedicated System RAM 0 MB Shared System RAM 2,048 MB Vendor ID 0x10DE Device ID 0x0FD2 Subsystem ID 0x06481025 Revision 161 LUID 0x000097AF Flags None Outputs 0 Crash Logs folder was empty... Not sure why.

Good to know that I'm not alone. Usually (but not every time... ?), Paint.net crashes if I close out and try to reopen it later. Can't open it after restarting the computer, either. I have to reinstall Paint.net every time.

After updating to 4.0, paint.net keeps crashing. Earlier versions have never had a problem. In Windows Event Viewer, it reports that mscoreei.dll is having issues. I went through the .NET framework repairs a few times, and while that fixes paint.net for a while, it starts crashing again (randomly?). Here's the error log: Faulting application name: PaintDotNet.exe, version: 4.0.5288.36565, time stamp: 0x53a9dd51 Faulting module name: mscoreei.dll, version: 4.0.30319.18408, time stamp: 0x523104b9 Exception code: 0xc0000005 Fault offset: 0x0000000000008089 Faulting process id: 0x1900 Faulting application start time: 0x01cf9b06d83030e4 Faulting application path: C:\Program Files\paint.net\PaintDotNet.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll Report Id: 164c57bf-06fa-11e4-9ef6-b888e305d191 In the meantime, I'll probably have to use the previous release of paint.net. The improvements of 4.0 are irrelevant if I can't use it in the first place. Has anyone else had these issues? I googled it and couldn't find much. EDIT: Just tried reinstalling it, and it is fortunately working again. Fingers crossed, but I dare not close it for the time being.