I installed NIS 2010 on my XP SP3 laptop and my mother's Media XP SP3 desktop. Since doing so I've seen a Data Execution Protection (DEP) crash on both my machine (Firefox 3.5.3) and my mother's (Compaq Connection Manager). Neither of these programs have ever had a DEP crash prior to installing NIS 2010.
The Firefox 3.5.3 crash occurred when resuming from Hibernation, while the Connection Manager crash occured when shutting down windows.
Could these be NIS 2010 related?
hello.
i have been using a program, coollector, a work in progress since march. much too often than not, it crashes.
only recently have the crashes evoked the DEP, perhaps coincidental to the upgrade to NIS 2010 on a vista64.
what specific components are we talking about disabling to test cause and effect?
neigh-ho-ma wrote:what specific components are we talking about disabling to test cause and effect?
First I would try Auto-Protect and firewall from the system tray.
If it's working that way, open the main window of NIS, and turn off the components one-by-one listed on the main screen. (Click on the green button thingy, and it will stop that function.) This way we can found out which one of the protection layers causing the error, and then find a (partial) solution for it.
Morac, Neigh-ho-ma,
Can you pls create complete dumps and send it to us ? Once the dumps are ready, pls let me know and I can send you a private message on where to upload them.
To create a complete dump -
In the "System Properties" window on the "Advanced" tab, click the "Settings" button under "Startup and Recovery" header. Make sure "Complete Memory Dump" is selected. You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed.
Thanks.
hello, snehansh_asuri.
you must have misunderstood our posts on the DEP crashes. they are program crashes, not operating system crashes. our program crashes will not create the system crash dumps you wish for.
This is the method Tony asked us to gather logs during the 2010 beta program:
x86: http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi
x64: http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.11.1.404.msi
1) After installing windbg, open a command prompt (Start/Run/“CMD”)
2) navigate to the install directory( eg: cd c:\program files\debugging tools for windows [or whatever directory you installed windbg])
3) type “windbg.exe -I” - that’ll setup windbg to run as a post-mortem debugger (should get a prompt stating as such.)
Reproduce the error. When the crash occurs, windbg should show up (big grey screen.)
4) Inside windbg, type the following command in the lower part of the screen command area: .dump /ma c:\dump.dmp
5) Once that’s complete, the dump should be located “C:\dump.dmp”.
Compress that dump file.
It must work with other apps too (I used it to send dumps to MS too, so it will work ;)).
Then you will be able to send the dump to Symantec.
PapauZ wrote:
Reproduce the error. When the crash occurs, windbg should show up (big grey screen.)
That might be difficult since I haven't been able to reproduce this at will.
hello.
before i received the message about the windows debugging tool for creating dumps, i ran through the components from the main screen disabling each in turn. aside from the temporary not being temporary, crashes were reproduced triggering DEP.
is there one particular dump that would be useful, such as one with my chosen settings or with a component disabled?
hello.
the instructions for running windbg included a flag that translated to an "ell" instead of an "eye". the help contents of windbg lists only an "eye" as a flag and no "ell".
running from an elevated cmd.exe, there was no prompt of "post-mortem debugger". the normal windbg window has a red background which won't change despite the change in the "options" under the view menu. not knowing whether to minimize or close this normal window, i minimized and continued.
i ran "coollector" and soon enough, a crash occurred with the accompanying DEP notice. however, no "big grey window" appeared. nothing.
by the way, the link for the 64-bit debugger was for a native itanium processor, not our run-of-the-mill 64-bit processors.
I installed NIS 2010 on my XP SP3 laptop and my mother's Media XP SP3 desktop. Since doing so I've seen a Data Execution Protection (DEP) crash on both my machine (Firefox 3.5.3) and my mother's (Compaq Connection Manager). Neither of these programs have ever had a DEP crash prior to installing NIS 2010.
The Firefox 3.5.3 crash occurred when resuming from Hibernation, while the Connection Manager crash occured when shutting down windows.
Could these be NIS 2010 related?