We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need. Who are the certified experts?
How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk. We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed.
Plans and Pricing. Contact Us. Certified Expert Program. Click on the "Select All" button which is different than selecting the "All Exceptions" checkbox. Your configuration window should look like the screenshot to the left. Let's discuss a couple of the other options here. The option "Bugcheck after Dumping" will cause the machine to create a Kernel dump after creating the user-mode dump.
Be very careful with this option! The other feature to note here is under the "Exit Monitor" section. In some instances you will encounter processes that seem to close gracefully for no apparent reason. If you check the "Monitor Process Exit" box, you will get a dump file created every time the process is closed. Again - this is an option to use judiciously - even if a user closes the application being monitored deliberately you will create a dump file.
For an application like Internet Explorer, Word, or Excel, this could result in a large number of unnecessary dump files and quite a bit of wasted disk space! Version 1. Following the initial installation of DebugDiag, the configuration process is wizard-driven. So let's go ahead and set up a rule to monitor our machine for spooler crashes. For our example, we will go ahead and select "A specific NT service" and click "Next".
Remember that we can only use DebugDiag against bit user-mode processes. If you were to try and monitor the spooler on a bit machine, you would receive an error similar to this:. After Clicking "Next", we are presented with the Advanced Configurations screen. For our purposes, we leave this at the default settings, and click "Next", which allows us to name our rule, and select a location for our dump files see the image below.
Once we have completed these options, we click next and activate our rule. Now the Spooler process is being monitored for crashes. This will include the dump file and the log file. Finally, there is one last option to capture a process dump that is available on Windows Vista.
If you open up Task Manager, you can right-click on an application name, the process name or the service and select the option to "Create Dump File". This will create a dump of the process, but not terminate it - so you can capture multiple dumps of a running process!
And that brings us to the end of our post on Application Crash Dumps. Sign in to vote. All, I am not sure if this is the right place to post this issue but I have a windows Server SP2 set up as a print spooler and we are getting constand instances of the print spooler crashing, we have tried moving the spool file, increasing memory and have changed the drivers of some of the printers all to no avail.
Could anyone please offer some further advise as this is becoming a really frustrating issue as users are constantly excperiencing problems when printing. I have pasted below an extraction from the Dr Watson log file to assist - apologies for the rather huge post.
If you require a specific part of the log file please let me know and I will post it as I am unable to see away of attaching a file to the discussion. Thanks you in advance for your assitance. KiFastSystemCallRet 7cce e82c call ntdll! RtlRaiseException 7cff 7cd3 8b mov eax,[esp] 7cd6 8be5 mov esp,ebp 7cd8 5d pop ebp 7cd9 c3 ret 7cda 8da lea esp,[esp] 7ce1 8da lea esp,[esp] ntdll!
KiFastSystemCall: 7ce8 8bd4 mov edx,esp 7cea 0f34 sysenter ntdll! KiFastSystemCallRet: 7cec c3 ret 7ced 8da lea esp,[esp] 7cf4 8d lea esp,[esp] ntdll!
KiFastSystemCallRet aff90 a3 ffffffff c90 kernel32! KiFastSystemCallRet ffec b9 kernel32! KiFastSystemCallRet 00a7ff74 a 00a7ffac kernel32! KiFastSystemCallRet 00edff90 fa ffffffff kernel32!
0コメント