T-RHex

Member
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

2 Neutral

About T-RHex

  • Rank
    Member
  1. Sorry for the delay in responding ... I do have MBAM Pro 2.2 installed but not running; I do not have the Real-Time protection enabled. I think you may just have been lucky. But it looks like Emsisoft has a patch deployed now and so far after a few reboots it appears to be working okay for me. Most programs cannot detect whether or not there is a connection, they rely on timeouts: if there is no response from the server in a set time, then they assume there is no connection. But, they don't know that until they try to connect...
  2. Sorry for the delay in responding ... I did not try disabling self-protection, but it looks like Emsisoft has put out a patch as I'm now able to boot properly without debug logging enabled. (a few reboots so far, that is) Kudos to Emsisoft support for being very responsive.
  3. For me, if debug logging is enabled the problem does not occur on startup. With debug logging disabled, it takes a few minutes for the Windows logon screen to appear (seems to be frozen, but just wait 2-3 long minutes) and EIS does not start properly. To workaround, I wait for Windows to startup, then kill the a2service.exe process, and then EIS either restarts on its own or I start it manually; after, it seems to function fine. As debug logging shouldn't stay on for long periods of time, I turn it off while working, then turn it back on before shutting down. I've been able to repeat this reliably quite a few times (especially when I forget to turn on logging before shutting down). I have submitted this information to support. Edit: to give credit where it's due, I got the idea of killing a2service.exe from this topic. I also see the difference in memory usage (around 44mb when hung, around 260mb when running). (Win7 Pro x64)
  4. I'm guessing it will come back. For me, if debug logging is enabled the problem does not occur on startup. With debug logging disabled, it takes a few minutes for the Windows logon screen to appear (seems to be frozen, but just wait 2-3 long minutes) and EIS does not start properly. To workaround, I wait for Windows to startup, then kill the a2service.exe process, and then EIS either restarts on its own or I start it manually; after, it seems to function fine. As debug logging shouldn't stay on for long periods of time, I turn it off while working, then turn it back on before shutting down. I've been able to repeat this reliably quite a few times (especially when I forget to turn on logging before shutting down). I have submitted this information to support. Edit: to give credit where it's due, I got the idea of killing a2service.exe from this topic. I also see the difference in memory usage (around 44mb when hung, around 260mb when running). (Win7 Pro x64)
  5. Thanks, Lynx, I appreciate the assistance and I've entered a bug ticket. Something I've now noticed which is kinda funny: though the hot key seems to stop working, it looks like it queues up the switch-screen requests, and now my browser window is switching screens at random and unexpected times. Thanks very much! tr
  6. (I was away for the past week, it wasn't that I gave up...) I have upgraded my nVidia drivers to the latest version from the nVidia support site. WinXP Pro 32-bit SP3 DirectX: 9.0 GeForce 8600 GT nVidia Driver version: 258.96 nVidia Components: 6.14.12.5896 nVidia Desktop Manager: 135.27 (6.14.10.13527) I cannot enable the desktop manager with EAM guard running. I shutdown the guard, enabled the desktop manager, and reboot the PC. I now have desktop manager enabled along with EAM guard. My assigned hotkey (Alt+Home) wasn't working for switching a window between monitors, so I reassigned the hotkey and tried several different ones (finally using Alt+H to keep it simple). The hotkey works once on a window, then stops working. If I shut down the guard, the hotkey works fine. If I then re-enable the guard, the hotkey works one more time, then stops working. As a software developer, I am constantly switching windows from one screen to the other so this hotkey for nVidia's Desktop Manager is very useful. Any suggestions on how to proceed?
  7. Latest efforts ... I'm no longer getting errors on shutdown! That's progress. However, I've been running the last few days with nView Desktop Manager disabled. If I try to enable it, the hourglass comes up for a min or two, then goes away and nothing changes in the Desktop Manager console. I cancelled the dialog, disabled EAM protection from the right-click menu on the systray icon, and opened nView Desktop Manager again. It was enabled, and all tabs were enabled now without doing anything further! I then re-enabled EAM, checked the nView console again and saw everything was still enabled. So far so good. Reboot. The Desktop Manager is disabled again. There's definitely some conflict between EAM and nView Desktop Manager. Next I will try disabling EAM first, enabling nView, and see what happens. Note: I am using the nVidia driver from MS update (as mentioned above) and not the latest one that Lynx had mentioned.
  8. (another update) The first shutdown after the above had no errors, but did not shutdown either. The only entry in the System log was this: Another attempt to shutdown actually shutdown the computer without further delay or any errors. I then turned the computer on, did some "light" use (email, browsing), and then shutdown: no errors, no delays, no problems. It shutdown the way I would hope or expect. So there may be some difference in the above two scenarios: the first usage was "typical" for me, the second was "light". "Typical usage" for me involves software development, VMWare, a lot of browsing/email/IM, and I wonder if something in that usage is causing the shutdown problem. Then I noticed another thing: the nView Desktop Manager is disabled! It must have been changed when I updated the driver. I tried to enable it; it didn't respond for a while (hourglass) then became responsive but was still disabled. No Event log messages, no errors thrown, no EAM or OA alerts. So now I cannot enable the nView Desktop Manager. I will try again later with EAM disabled.
  9. (double post) Okay, that went well (or not)... I had an opportunity to reboot, so: I used Windows Update to update the nVidia driver; that went fine (I didn't look at nVidia's support site for the update file since Windows Update picked it up) before rebooting, I thought "just to avoid the previous problem, I will exit EAM", so I chose "Shut down Guard" from the systray icon right-click menu. I manually exited all applications and dismounted all TrueCrypt volumes. I shut Windows down (not reboot) Three error windows popped up: - TrueCrypt application error - Explorer.exe application error - "End Program: Media Center" (could not shutdown) I clicked on the "close" for Explorer.exe and it kept coming back. Eventually (after much clicking), everything then shutdown normally. Windows restarted fine (no errors) and I checked the Event logs. There's nothing of note in the Application log, but in the System log I see: On startup, everything looks fine, and nVidia/nView is now updated to 197.45 (all the components in the nVidia Control Panel are 6.14.11.9745). I see my nView.dll is only 6.14.10.12561, a little behind the version you have. All the versions shown in the nView Desktop Manager are 6.14.10.12561. I'll see how the next boot goes when I have a chance. I will also play a bit with shutting down EAM before shutting down Windows and see if I can reproduce the application errors.
  10. True. I had no issues with just OA installed and using ESET Nod32; it wasn't until I installed EAM that the problem came up. However, now that I recall, those entries from the EventLog came on a day when it seemed "everything" was going wrong; I had several apps crash on shutting down the system, including TrueCrypt -- and I've never before had TrueCrypt crash. Maybe I should've mentioned that previously, but I didn't think it pertinent to this topic of nVidia. as a support ticket to Emsisoft developers irrespectively in case that will persist. They may ask you for additional info I will do that when time permits. Sorry, I forgot to respond to that previously. I had tried updating my nVidia driver a few months ago, and found some other issues with it (repositioning windows to the other screen actually left them in the middle of the two screens). After restoring a prior system image (something I do occasionally to get back to a clean system), I did not update the nVidia driver. I will try that just to see if it resolves the shutdown issue. Not sure I follow you there. Are you just saying EAM has the best service recovery ability you've seen? Haha. Don't worry, computers have given me far too many undesireable thoughts over the years, so I'm used to them and won't get distracted. Oh, as a test, I had added nvsvc32.exe to the Guard's Application Rules as "always allow". It was the only nVidia .exe I could find that was running (as opposed to .dlls) but it had no effect. Today I will try a few other options (it's just a pain, because to try each option requires rebooting the machine and unfortunately I have work to do ). Thanks again, much appreciated. 0xtr
  11. Good call on the Event Viewer; sometimes I focus on the problem of the "new" thing and forget the basics. There's a whole bunch (page fulls) of the following error in my Application log: The 16th was probably the day I had the most trouble. However, I haven't had any entries yesterday or today, so that's not so bad. I'll keep an eye on that log. There is this in the System log: I'm thinking that had to do with the latest update; I know I suddenly got a Windows security notice that I had no virus scanner installed and noticed the EAM icon had disappeared from the systray; then it came back and when I checked it was a new version. So I'm not concerned about that. Nothing else of note in the System log. Ach, I should smack myself in the head. I searched for "nvidia twinview shutdown" and quickly found others having similar problems with other AV/AM products installed; the solutions were invariably to exclude nview from the AM. I will give that a try and see what happens the next time I shutdown. Thanks for your patience, Lynx. Normally I try to think before speaking, but I guess I got focused on "EAM is the new thing, so it MUST be causing the problem".
  12. Hi Lynx, thanks very much for the response. I have not changed the driver -- it's the one I've always been using. You mean rules within EAM? I don't see any specific rules for nVidia in the "Application Rules" tab. I'd rather not disable nView from starting up, as I use the windows-positioning hotkey quite a bit. Yes, I've been answering "allow" and "remember this" for #4. I just wanted to confirm that was expected behavior (ie. the message coming from the app itself, not from NVIDIA's nView manager). I'm not sure what you mean by this: Which rules would I check? I know there may be some overlap between OA's HIPS and EAM's BB, but it's odd that it would affect shutdown and not startup. I have absolutely no issues on startup; the speed is even decent. But on shutdown I get no alerts from either OA or EAM; just the "Windows cannot close..." dialog. Is there a debug log I can enable within EAM to determine what it might be doing? Thanks again.
  13. Hello, I've been trialling EAM 5 for about a week now and have run into multiple instabilites or conflicts and I don't know where to start in trying to resolve them. I know you prefer having one issue per thread topic, so I will start with these since I think they are related: Windows shutdown is much slower than before. When I shutdown Windows I now get the dialog: NVIDIA Twinview not shutting down; it eventually goes away (I do not click "End Now"), then comes back, goes away and Windows does not shutdown. Then if I choose "Start > Shut Down" again, Windows does shutdown properly. All applications on the left screen hung once (dual screen setup). I have a hotkey to "move window to next display"; when I use it I get a BB warning not on nView but on the application itself that it's acting like a keyboard/mouse event handler. WinXP Pro SP3 NVIDIA nView Desktop Manager 120.64 (nview.dll 6.14.10.12064) EAM 5.0.0.61 (30 day trial) File Guard: on Behavior Blocker: on Surf protection: on with configuration pretty much the installed defaults OnlineArmor Premium 4.0.0.45 Mail Shield: off Web Shield: off Program Guard: on Firewall: on I had run with OA for 2 weeks without any issues prior to installing EAM. I previously had ESET Nod32 installed, but uninstalled it before installing EAM. Any idea how to figure out what's going on? Thanks