This thread was archived. Please ask a new question if you need help.
NIS.EXE error message when Windows 7/64 is closing and Firefox already closed
When I am shutting down Windows 7, 64 I get an error message: "nis.exe - Application Error The instruction at 0x6e62872d referenced memory at 0x00000000. The memory could not be read
It's actually not causing a problem as it only happens when I'm closing Windows but it is irritating and also makes me wonder what the problem is and if it's going to cause problems.
The only thing I have a problem with in Firefox is if I minimize Firefox it loses my settings for home page and gmail that I have set as a pin. This doesn't happen if I close Firefox and then start again. Kind of strange and not sure if related to nis.exe error.
Would appreciate any help to straighten these problems out.
I am sorry to hear that it was throwing the error for so long. I will mark your post as the solution for now :-)Read this answer in context 👍 0
All Replies (6)
I am pretty sure that is a Norton error. Please also see: http://community.norton.com/forums/nisexe-error-and-manual-program-cont...
I had already seen those responses but none were applicable. The problem is gone as when Norton was doing a scan and did the corrections the problem was no longer existing on the shutdowns so I guess Norton took care of the problem themselves.
Still have the problem with Firefox losing my settings if I minimize it and then start it again so don't know how to change or fix that. May just be something that was never addressed and set up properly.
Hi lsilvest, Awesome, but as for loosing settings for the set home page and gmail you have pinned if you minimize and start over, when does it change? when you restart, or when you minimize a new tab that has not been changed?
It's when I minimize Firefox. I have the Firefox link on my taskbar and after minimizing just click on the taskbar link and my settings are gone. If I close Firefox and then restart by clicking on the taskbar link everything is just like when I closed it. Not the end of the world, but just kind of strange that it acts that way and it is a bit annoying.
It must have been a Norton error. I ran the Norton scan and the problem disappeared.
I am sorry to hear that it was throwing the error for so long. I will mark your post as the solution for now :-)