Welcome Guest.   Make a donation to an author on the site December 20, 2014, 02:03:58 AM  *

Please login or register.
Or did you miss your validation email?


Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.


You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
 
The N.A.N.Y. Challenge 2013! Download dozens of custom programs!
   
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Process Tamer crashes Vista  (Read 5123 times)
koehlerb
Supporting Member
**
Posts: 5

View Profile Give some DonationCredits to this forum member
« on: February 13, 2008, 11:15:09 AM »

Process Tamer crashes Vista.  About once a day.  It's only happened once or twice while I am there - it usually happens overnight.  If I am there when it happens, it presents the BSOD briefly, then goes through a reboot.  After the reboot, Windows posts a message that it has encountered a problem and will notify me when a solution is found.  I can't find any clues in the Windows system logs, but perhaps I don't know the right place to look.

The processes I am taming are:
sidebar.exe (2 instances)
SearchIndexer.exe
SearchProtocolHost.exe
SearchFilterHost.exe

All these are set to "Force Low".

I love the program, but can't live with the crashes, so have suspended using it until I hear from you with some suggestions.  I guess an obvious one is to stop taming, and then tame one item at a time; however I am hoping that you can direct me to a system log that I can look in for some clues for you.

Thanks for the super support you provide.

Bruce
Logged
mouser
First Author
Administrator
*****
Posts: 33,786



see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #1 on: February 13, 2008, 11:22:19 AM »

I've not heard about it crashing vista before, but it's possible there is some process that it is interacting with that is making it crash.

Two suggestions:
  • Go to configuration and make sure you have checked the box to save a log file (upper right of Configuration tab),
  • Then the next time the bsod happens, start it up and go to the log file (Log file tab of Configuration dialog) and see what the latest entries are -- see if you spot any clues.

  • Do what you are doing -- dont run Process Tamer for a couple of days and really confirm that the problem is indeed Process Tamer and that it's not a coincidence.  Note that PT does not run any services or secret stuff or make any changes, so if PT is not running, and you still get the BSODs, then its not PT (i.e. no need to completely uninstall it to test).

A last thing you could try is, to disable the options to:
  • Tame Applications Based on CPU Usage
  • Foreground Process Special Handling (disable any checkboxes here especially!)

And see if that solves it.  That would at least be a clue that it's some process interaction with another program (not the explicit ones you've listed about that you manually force low).
Logged
koehlerb
Supporting Member
**
Posts: 5

View Profile Give some DonationCredits to this forum member
« Reply #2 on: February 21, 2008, 05:47:21 PM »

Using your suggestions, I determined that Process Tamer IS NOT THE CAUSE of my Vista crashes.

My apologies!

Now if I can only figure out what IS crashing it.  It was ROCK SOLID for almost a year - not one crash!

Thanks for the GREAT SOFTWARE!

Bruce
Logged
mouser
First Author
Administrator
*****
Posts: 33,786



see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #3 on: February 21, 2008, 06:47:58 PM »

smiley

thank you for posting the follow up -- i've noticed a lot of the time on forums people will post about something and then if they figure out the solution they just dissapear leaving everyone to wonder what happened.  thank you for the update  thumbs up
Logged
f0dder
Charter Honorary Member
***
Posts: 8,774



[Well, THAT escalated quickly!]

see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #4 on: February 24, 2008, 07:10:15 AM »

koehlerb: you need to go to System Properties, "advanced" tab, "settings" button in "startup and recovery" group, and uncheck the "automatically restart" checkbox under the "system failure" heading".

This will give you enough time to read the BSOD message. See if it mentions any drivers, and tell us the BSOD error code and driver name.
Logged

- carpe noctem
koehlerb
Supporting Member
**
Posts: 5

View Profile Give some DonationCredits to this forum member
« Reply #5 on: February 25, 2008, 12:20:24 AM »

Thanks for the GREAT information - will do!
Is there any way to cause the system to CAPTURE this info (logs, etc)?
Logged
mwb1100
Supporting Member
**
Posts: 1,356


View Profile Give some DonationCredits to this forum member
« Reply #6 on: February 25, 2008, 12:53:26 AM »

Is there any way to cause the system to CAPTURE this info (logs, etc)?

The BSOD should leave a dump file, usually in the C:\Windows\Minidump directory (this is controlled in the same dialog as f0dder mentioned).  I'm not sure if there's a good way to get information from the minidump except by using the Kernel Debugger, though.  I could take a look, but I'm not sure if I'd really be able to figure out anything other than what driver was the immediate cause of the crash (this is usually, but not always, the driver that has the bug).  That driver should be mentioned in the blue screen, too.
Logged
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
 
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.031s | Server load: 0.07 ]