Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Repeated crashes after working fine for weeks
#1
Windows 10 Pro 20H2 build 19042.804 64 bit, 8 core Xeon, 32 GB RAM.  GIMP 2.10.22   GIMP has been working flawlessly for weeks - the only thing I did yesterday was to use the portable version of MOUSECONTROLLER to make repetitive editing easier.  But MC has to be manually started and I'm not doing that.  Unable to open a file - just crashes out with  dump file.

1) over install - N/C
2) uninstall thru control panel, reboot, reinstall as administrator so all users work - N/C
3) uninstall thru control panel, no GIMP folder in program files,  if search with hidden files on find lots in C:\Users\Me\AppData\Roaming\GIMP\2.10 - so I'm posting before I just start mass deletes - has 66 files totaling about 475K.  Haven't had to resort to this for a long time.  Dump file available.

Next - this?  Just delete every piece of GIMP I can find on the "C" drive.  Note that I keep all my files on other logical/physical drives so my "C" is only about 70GB of data.
Reply
#2
MOUSECONTROLLER may have installed some library that gets in the way and isn't too compatible with Gimp. Did you try to uninstall it?
Reply
#3
It's not installed - it's the portable version - which is normally my choice for software that has the option. I also started GIMP several times after starting MC and had no problems. There also weren't any updates listed in the history.

I'd install on my cracking Xeon but software that crashes is a concern. I did look at the .wer file which is something I haven't had to do since "retiring".

This is the most likely relevant info:
Sig[0].Name=Application Name
Sig[0].Value=gimp-2.10.exe
Sig[1].Name=Application Version
Sig[1].Value=2.10.22.0
Sig[2].Name=Application Timestamp
Sig[2].Value=00000000
Sig[3].Name=Fault Module Name
Sig[3].Value=nViewH64.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.14.10.14847
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58524e98
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000098c31
Reply
#4
I uninstalled GIMP and renamed the GIMP folders under \Roaming and \Local. Rebooted and ran a chkdsk which was clean. Applications such as OpenShot and LibreOffice work fine. Huh?
Reply
#5
Where does the nViewH64.dll come from? Seems a bit old (2016-12-15)
Reply
#6
Interesting. The nViewH64.dll file located in C:\Program Files\NVIDIA Corporation\nview has these dates:
Created: 6/15/2020 {I bought this Z620 PC used last year}
Modified: 2/15/2017
Access: 2/25/2021 (today)
Signatures from NIVDIA and Microsoft Win Hdwe Comp Pub

File version: 6.14.10.14847

All application packages have read and read&execute permissions.

Running an old NVIDIA Quadro 4000 video card and the available driver files from Nvidia are all old. I'm actually ready to upgrade to a GTX 1050 Ti but I'm waiting for prices to get back to reasonable for video cards.

On a side note I installed GIMP on a stable Oracle VM VirtualBox machine Win 10 Ent. After a GIMP install the system gets a VM exception integer division by zero. I'll discard the machine and try it as a VM on my fast system if that would help.
Reply
#7
Totally weird. Late yesterday I went on a different Z620 and installed GIMP on a VirtualBox Win machine. No problems.

This morning I was going to try a restore point and if that didn't work I'd do a system backup from 2/18/2021 (yes - I actually do system backups to a USB drive). But I thought let's try GIMP one more time after an AppData rename for roaming and local and a reinstall. Now it's working. The VirtualBox machine also doesn't error out any more and GIMP works on it. Even the MC works although it seems to have a hiccup with one of the mouse clicks - I'll just record another file. I doubled checked the "C" drive with sfc and a complete "C" drive WinDef scan - nothing of note. In an eyeball comparison the old and new roaming look the same.

Since the VB machine works obviously something that it was pointing to was also "busted" just like the native hardware.

If this happens again I'll uninstall NVIDIA nView because I don't really use it as my U3011 monitor is all I need. If still "busted" then uninstall, do the AppData renames or deletes and then see what happens.

Windows - do I "love to hate it" or "hate to love it"?
Reply
#8
I've been working on other projects for a few days. Went to edit with GIMP and got an error. Looked at the .wer file and it was nViewH64.dll - so I just uninstalled NVIDIA nView 148.47 through the control panel. Immediately began working correctly. I'm going to need to bite the bullet and get the last driver package, uninstall and delete all the NVIDIA files, reboot with crossed fingers and install the latest driver.
Reply


Forum Jump: