Greetings All,
New here, and hopefully I won’t be posing too terrible of a question. In 9 years as an MCSE, I’ve never seen the likes of this one.
Background Story: I am attempting to debug PGP’s [sarcasm] wonderful [/sarcasm] Netshare application on a Windows SBS 2003 PE server which I use as a testbed for new projects/app rollouts. I have ISA 2004 running on the machine. PGP Netshare 9.5.3 installs perfectly, then upon reboot I attempt to drag n’ drop a file into Netshare for encrypting, and the system crashes. No problem there; that’s why I use a testbed, right? Well, it just so happens that now I have a hosed dump.
The problem: PGP Tech Support of course would like my memory dump, but I can’t seem to get a clean one and I’m not 100% sure as to why as I’ve never had any problems with obtaining them in the past. I would like to switch to a mini-dump, but when I select “small dump (64KB)” and click Ok to that window and Ok to the system properties window, my server reboots and I get a “Windows has recovered from a serious error” message when I log back on. If I uncheck “automatically reboot” at the advanced system properties screen, then select mini-dump, the system crashes and I get a 1.5GB memory.dmp file on the next reboot (and every time I reboot, my change from full dump to mini-dump is not committed, i.e. it still reads full memory dump).
I have tried to view the mini-dumps and full dumps with WinDBG, but WinDBG states that they are corrupt and doesn’t give any useful information. I can’t seem to make heads or tails of this. Perhaps someone with more experience than I can help me? Much appreciated for any advice given!
Cheers, Jack Dorsey