Administrator client hangs

Hi,
On my windows seven 64 bit machine, Notes and designer works fine but Domino administrator hangs every time it starts. After a clean installation,the problem persists. In the nsd log, I found a panic thread and the following stack message in that thread.
@[10] 0x5f3b56a3 nnotes.Panic@4+883 (528ae404)
00178050 48901700 7B1DD151 04E48A52 45125676 | H… {…Q …R E.Vv |
00178060 22125676 0000C351 416E2065 72726F72 | ".Vv …Q An e rror |
00178070 20776173 20656E63 6F756E74 65726564 | was enc ount ered |
00178080 20776869 6C65206F 70656E69 6E672061 | whi le o peni ng a |
00178090 2077696E 646F7700 1F5AE074 00000000 | win dow. .Z.t …

I searched web but the solutions of others facing the issue doesn’t work for me e.g. disabling anti-virus software, adjusting the display options.
Can anyone helps me? Thanks.
This is the complete log: https://www.dropbox.com/s/aj12w9ezyzopyil/nsd_W32I_STARROW-PC_2015_12_16%4017_34_39.log?dl=0 https://www.dropbox.com/s/aj12w9ezyzopyil/nsd_W32I_STARROW-PC_2015_12_16%4017_34_39.log?dl=0

Subject: The pid.nbf in nsd shows two NLNOTES.EXE processes

<@@ ------ System Data → Environment → pid.nbf (Time 17:34:49) ------ @@>

1 [D:\Lotus\Notes\NLNOTES.EXE: 1a8c]
1 [D:\Lotus\Notes\nEvent.EXE: 1ae4] [D:\Lotus\Notes\NLNOTES.EXE: 1a8c]
1 [D:\Lotus\Notes\NLNOTES.EXE: 1a7c]

I’m guessing you did not have a clean shutdown of a previous version of Notes running…

From

d:\Lotes\Notes> nsd.exe -kill

Then restart notes and try to launch the Admin Client…

Still some type of bug that is preventing Notes from exiting cleanly…

jpaganet@us.ibm.com

Subject: I know once I have a crash, certain local dbs need to be checked/fixup

I know bookmark.nsf always needs a fixup, then names.nsf, and desktop.dsk.

If there’s a DB that Administrator uses exclusively I’d check it as well. I remember there was one when Admin first came out, but I don’t remember its name.

Subject: Re: The pid.nbf in nsd shows two NLNOTES.EXE processes

@John,

Thanks but after I close all notes processes or even start administrator just after the machine starts the problem still appears.