Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


This will check your Hijack log.

  • Please log in to reply
3 replies to this topic

#1 alpine


  • Members
  • 6 posts
  • Local time:12:09 PM

Posted 24 June 2005 - 08:03 PM

Heres a great link thats kept up to date. Try this before asking for help and if u get a nasty then ask.

Hijack this log file analysis


BC AdBot (Login to Remove)


#2 tg1911


    Lord Spam Magnet

  • Members
  • 19,274 posts
  • Gender:Male
  • Location:SW Louisiana
  • Local time:11:09 AM

Posted 24 June 2005 - 11:02 PM

Trying to self-diagnose a HijackThis log can be dangerous.
You should not try to fix anything with HJT, unless you have been properly trained in it's use.
HJT is a tool used to locate "problems".
The removal of these "problems" is sometimes much more involved, than just having HJT fix it.
The improper use of HJT could cause irreparable damage to your system.
MOBO: GIGABYTE GA-MA790X-UD4P, CPU: Phenom II X4 955 Deneb BE, HS/F: CoolerMaster V8, RAM: 2 x 1G Kingston HyperX DDR2 800, VGA: ECS GeForce Black GTX 560, PSU: Antec TruePower Modular 750W, Soundcard: Asus Xonar D1, Case: CoolerMaster COSMOS 1000, Storage: Internal - 2 x Seagate 250GB SATA, 2 x WD 1TB SATA; External - Seagate 500GB USB, WD 640GB eSATA, 3 x WD 1TB eSATA

Become a BleepingComputer fan: Facebook

#3 jgweed


  • Members
  • 28,473 posts
  • Gender:Male
  • Location:Chicago, Il.
  • Local time:12:09 PM

Posted 24 June 2005 - 11:02 PM

Hold in memory that unless you are somewhat experienced with making changes and have a relatively good idea what is going on, you can do more harm than good working a log by yourself.
If you are a new user, or a casual user, I am sure the team would rather you post a log with relatively few problems, than do even greater harm to your computer by attempting to do it yourself.
Whereof one cannot speak, thereof one should be silent.

#4 CrEsPo


  • Members
  • 10 posts
  • Location:Canada
  • Local time:01:09 PM

Posted 26 June 2005 - 10:14 AM

I'll also advise to not do anything if you do not know what you're doing. As already mentioned, you'll more than likely cause more problems than what you have fixed.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users