kitty crashs by close

Michael Killing - Mon 24/09/2012 19:39:55 CEST +0200

Hi All,

after the last updates from MS (i'm a idiot.. why i click on okay...?) on my nvidia display drivers (yesterday) kitty crash by close.


Chrashreport is on the bottom.

System: Lenovo TP W520
OS: Win 7 Pro 64 bit
1. Displaychip: Intel HD Graphics (v. 8.15.10.2538)
2. Displaychip: Nvidia Quatro 2000M (v. 9.18.13.593)

Problemsignatur:
     Problemereignisname: APPCRASH
     Anwendungsname: kitty.exe
     Anwendungsversion: 0.62.0.0
     Anwendungszeitstempel: 502a18f7
     Fehlermodulname: nvinit.dll_unloaded
     Fehlermodulversion: 0.0.0.0
     Fehlermodulzeitstempel: 502ef724
     Ausnahmecode: c0000005
     Ausnahmeoffset: 7438ce39
     Betriebsystemversion: 6.1.7601.2.1.0.256.48
     Gebietsschema-ID: 1031
     Zusatzinformation 1: 0a9e
     Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
     Zusatzinformation 3: 0a9e
     Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789

Hippo - Sun 07/10/2012 19:34:50 CEST +0200

I have observed the same behavior on my system.

System: Asus N53JN
OS: Windows 7 Pro 64 bit
1. Displaychip: Intel HD Graphics
2. Displaychip: Nvidia 350M (Nvidia OPTIMUS platform)

Brad Thurber - Mon 15/10/2012 20:38:04 CEST +0200

+1

System: Lenovo W520
OS: Windows 7 Pro 64 bit
1) Displaychip Intel HD Graphics (v 9.18.13.679)
2) Displaychip: Nvidia Quadro 1000m (v 9.18.13.679)

Brad Thurber - Mon 15/10/2012 20:47:42 CEST +0200

I guessed that from the modulename of nvinit.dll_unloaded that this may have something to do with the switching between the two display adapters not working. As a workaround, I went into NVidia Control Panel/3D Settings/Manage 3D settings then for the "Base profile" Global presets, I set

Preferred graphics processor drop-down to "High-performance NVIDIA processor". It was set on "Auto-select".

I have barely tested this, but it seems to help

Robert M. - Wed 31/10/2012 10:04:40 CET +0100

I can confirm that Brad's solution works.
Maybe better solution is to keep "Base profile" untouched and define new "Program Setting" for kitty.exe on second tab of "Manage 3D settings" in NVIDIA Contol Panel.

Lenovo T520 w/ intel and nvidia chips.
Problem occured after upgrade of Nvidia drivers to version 305.93

JD - Wed 14/11/2012 00:32:17 CET +0100

Robert's solution also works, via adding KiTTY to the programs list and setting it to use the Nvidia card.

Thanks to both you and Brad.

Teamcode - Mon 19/11/2012 16:57:15 CET +0100

Yes!!! Same problem with wkhtmltopdf.exe
Windows 7 Professional 64 bit
NVS 5200M.

SOLVED.
Thank you so much!!!!!!!!!!!!!

Joris Kuipers - Thu 29/11/2012 00:10:39 CET +0100

Robert's solution is awesome tip: ran into this very problem, found this thread and solved the problem within minutes! :)

Paolo - Mon 03/12/2012 17:00:48 CET +0100

Fixed my issue too! BTW this happens only on 64-bits systems. I did set processor to integrated graphics

Dave - Tue 29/01/2013 19:07:43 CET +0100

That is not a very good solution, there is no point in using the discrete GPU just to run KiTTY.

A better solution is to use the uncompressed version of KiTTY instead. Find it on the download page.

Dublinvince - Thu 31/01/2013 21:42:29 CET +0100

Thanks Dave that's exactly it: A solution. Worked great for me.

Jimmy Merrild Krag - Fri 12/04/2013 15:29:59 CEST +0200

Seems to work with adding a profile that forces kitty to run on integrated graphics as well.

Raj - Sat 13/04/2013 06:01:33 CEST +0200

@Dave, why does using the uncompressed version of KiTTy resolve the issue?

Frank - Sun 18/08/2013 13:21:27 CEST +0200

The 0.63 beta also experiences this problem. Given that the uncompressed version (not available for the beta) does not show the error, it feels like something that can be solved. Can it?

sulisu - Sat 08/11/2014 05:27:18 CET +0100

It seems to be caused by upx compression. There is another solution on upx sourceforge page.

Compress the exe file with "upx --compress-exports=0 program.exe", http://sourceforge.net/p/upx/discussion/6806/thread/bfe3ccf6/

I have a success on one of another compressed exe by decompressing it first and then recompressing it. But the kitty.exe has some signiture protection, so I can not test it with this method.

Cyd - Mon 10/11/2014 09:11:55 CET +0100

Here is a build using the --compress-exports=0 option: https://www.9bis.net/kitty/data/beta/kitty.exe
Can you test if it works ?

sulisu - Mon 14/09/2015 07:47:56 CEST +0200

It works fine. Thank you very much.

Answer

The forum is actually closed