You can use the following document to force a dump:
http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2007081601291939
Since Erik has now dropped in, I suggest you continue your responses with him. I note already that you have raised a concern about affecting a dump and no doubt Erik will respond in due course.
erik_carlstrom wrote:You can use the following document to force a dump:
http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2007081601291939
Hmm, I thought I replied to this? Don't see it?
Erik, I started to follow the above document.
One error, the WinDbg installs to a directory that has '(x86)' at the end of the directory. Need to update the link above for the command to run.
Also, I have SP 3, not 2. I couldn't locate the debug tools for SP 3, and I'm reluctant to install the SP 2 ones. Should I?
Irv
1 Like
The same tools will work for SP3.
erik_carlstrom wrote:The same tools will work for SP3.
Erik, OK, installed it.
Instructions at your site is NOT CLEAR for a BSOD... for instance, just what is the 'process name' I need to use? Is it necessary to do these CMD's on EVERY boot? I'm dealing with a RANDOM BSOD that I can not predict when it will happen?
Anyway, I'm removing my AV and Firewall now and installing N360 V2 and we'll see what happens.
Sending PM.
Erik and I have been exchanging e-mails. He has been very professional and helpful. We prepared my system for capturing data in case of a fail, but after a few days I've not had any and consider this case closed.
I suspect I had memory leaks in March when I was getting the BSOD's. Many fixes have gone in since then and some new s/w has been installed on my system including SP3. Who knows if or when the problem was fixed, but I consider it fixed now.
Thanks to all whom had replied.
Irv Spalten