Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Tex10's Topic only :Spybot Freezes PC at: 23282/31725 Gain.Gator.

  1. #11
    Esteemed Member
    Join Date
    Oct 2005
    Posts
    554

    Default

    I was trying to confirm that the detections themselves weren't the problem as I'd suspected. It appears that some combination or build-up from previous detections may be involved. I'm not at all sure what it is, but at least we proved it wasn't a direct conflict with the C2.lop or GAIN:Gator detections, which likely rules out malware too.

    I'd next like to determine if it's an interaction with any other specific detections, but first, would you please post just the first couple sections from a full Spybot Report? I want to make sure everything's current and it's not an issue with out of date or mixed files.

    Just run another scan the same way since a successful scan is all that's needed, we don't really care what the resilts are. Then, right-click in the results screen and select 'Save full report to file...' and save it where you can easily find it. Open the file itself by double clicking and copy everything from the beginning up to the 'Startup entries list' section heading, but not the start-ups themselves. Paste this into your next post.

    After we know there isn't a file issue we'll look at options to determine if there's interaction with other detections.

  2. #12
    Junior Member
    Join Date
    Dec 2005
    Location
    Calgary, Alberta, Canada
    Posts
    11

    Question

    Quote Originally Posted by bitman
    I was trying to confirm that the detections themselves weren't the problem as I'd suspected. It appears that some combination or build-up from previous detections may be involved. I'm not at all sure what it is, but at least we proved it wasn't a direct conflict with the C2.lop or GAIN:Gator detections, which likely rules out malware too.

    I'd next like to determine if it's an interaction with any other specific detections, but first, would you please post just the first couple sections from a full Spybot Report? I want to make sure everything's current and it's not an issue with out of date or mixed files.

    Just run another scan the same way since a successful scan is all that's needed, we don't really care what the resilts are. Then, right-click in the results screen and select 'Save full report to file...' and save it where you can easily find it. Open the file itself by double clicking and copy everything from the beginning up to the 'Startup entries list' section heading, but not the start-ups themselves. Paste this into your next post.

    After we know there isn't a file issue we'll look at options to determine if there's interaction with other detections.
    Hi bitman; Here is what I got.


    --- Search result list ---
    Congratulations!: No immediate threats were found. ()



    --- Spybot - Search & Destroy version: 1.4 (build: 20050523) ---

    2005-05-31 blindman.exe (1.0.0.1)
    2005-05-31 SpybotSD.exe (1.4.0.3)
    2005-05-31 TeaTimer.exe (1.4.0.2)
    2005-11-28 unins000.exe (51.41.0.0)
    2005-05-31 Update.exe (1.4.0.0)
    2005-05-31 advcheck.dll (1.0.2.0)
    2005-05-31 aports.dll (2.1.0.0)
    2005-05-31 borlndmm.dll (7.0.4.453)
    2005-05-31 delphimm.dll (7.0.4.453)
    2005-05-31 SDHelper.dll (1.4.0.0)
    2005-05-31 Tools.dll (2.0.0.2)
    2005-05-31 UnzDll.dll (1.73.1.1)
    2005-05-31 ZipDll.dll (1.73.2.0)
    2005-12-09 Includes\Cookies.sbi
    2005-12-09 Includes\Dialer.sbi
    2005-12-09 Includes\Hijackers.sbi
    2005-12-09 Includes\Keyloggers.sbi
    2005-12-09 Includes\Malware.sbi
    2005-12-09 Includes\PUPS.sbi
    2005-12-09 Includes\Revision.sbi
    2005-12-09 Includes\Security.sbi
    2005-12-09 Includes\Spybots.sbi (*)
    2005-02-17 Includes\Tracks.uti
    2005-12-09 Includes\Trojans.sbi (*)



    --- System information ---
    Windows XP (Build: 2600) Service Pack 2
    / .NETFramework / 1.0: Microsoft .NET Framework 1.0 Service Pack 3 (KB867461)
    / .NETFramework / 1.0: Microsoft .NET Framework Service Pack 1
    / .NETFramework / 1.1: Microsoft .NET Framework 1.1 Service Pack 1 (KB867460)
    / DataAccess: Microsoft Data Access Components KB870669
    / DataAccess: Patch Available For XMLHTTP Vulnerability
    / DataAccess: Patch Available For XMLHTTP Vulnerability
    / DataAccess: Security update for Microsoft Data Access Components
    / DataAccess: Security Update for Microsoft Data Access Components
    / DirectX: DirectX Update 819696
    / Internet Explorer 6 / SP1: Windows XP Hotfix - KB834707
    / Windows Media Player: Windows Media Player Hotfix [See KB837272 for more information]
    / Windows Media Player / SP0: Windows Media Player Hotfix [See wm828026 for more information]
    / Windows Media Player: Windows Media Update 320920
    / Windows Media Player: Windows Media Update 320920
    / Windows Media Player: Windows Media Update 819639
    / Windows Media Player: Windows Media Update 828026
    / Windows XP / SP2: Windows XP Service Pack 2
    / Windows XP / SP3: Windows XP Hotfix - KB834707
    / Windows XP / SP3: Windows XP Hotfix - KB867282
    / Windows XP / SP3: Windows XP Hotfix - KB873333
    / Windows XP / SP3: Windows XP Hotfix - KB873339
    / Windows XP / SP3: Security Update for Windows XP (KB883939)
    / Windows XP / SP3: Windows XP Hotfix - KB885250
    / Windows XP / SP3: Windows XP Hotfix - KB885835
    / Windows XP / SP3: Windows XP Hotfix - KB885836
    / Windows XP / SP3: Windows XP Hotfix - KB885884
    / Windows XP / SP3: Windows XP Hotfix - KB886185
    / Windows XP / SP3: Windows XP Hotfix - KB887472
    / Windows XP / SP3: Windows XP Hotfix - KB887742
    / Windows XP / SP3: Windows XP Hotfix - KB887797
    / Windows XP / SP3: Windows XP Hotfix - KB888113
    / Windows XP / SP3: Windows XP Hotfix - KB888302
    / Windows XP / SP3: Security Update for Windows XP (KB890046)
    / Windows XP / SP3: Windows XP Hotfix - KB890047
    / Windows XP / SP3: Windows XP Hotfix - KB890175
    / Windows XP / SP3: Windows XP Hotfix - KB890859
    / Windows XP / SP3: Windows XP Hotfix - KB890923
    / Windows XP / SP3: Windows XP Hotfix - KB891781
    / Windows XP / SP3: Security Update for Windows XP (KB893066)
    / Windows XP / SP3: Windows XP Hotfix - KB893086
    / Windows XP / SP3: Security Update for Windows XP (KB893756)
    / Windows XP / SP3: Windows Installer 3.1 (KB893803)
    / Windows XP / SP3: Windows Installer 3.1 (KB893803)
    / Windows XP / SP3: Update for Windows XP (KB894391)
    / Windows XP / SP3: Hotfix for Windows XP (KB896344)
    / Windows XP / SP3: Security Update for Windows XP (KB896358)
    / Windows XP / SP3: Security Update for Windows XP (KB896422)
    / Windows XP / SP3: Security Update for Windows XP (KB896423)
    / Windows XP / SP3: Security Update for Windows XP (KB896424)
    / Windows XP / SP3: Security Update for Windows XP (KB896428)
    / Windows XP / SP3: Security Update for Windows XP (KB896688)
    / Windows XP / SP3: Update for Windows XP (KB896727)
    / Windows XP / SP3: Update for Windows XP (KB898461)
    / Windows XP / SP3: Security Update for Windows XP (KB899587)
    / Windows XP / SP3: Security Update for Windows XP (KB899588)
    / Windows XP / SP3: Security Update for Windows XP (KB899591)
    / Windows XP / SP3: Security Update for Windows XP (KB900725)
    / Windows XP / SP3: Update for Windows XP (KB900930)
    / Windows XP / SP3: Security Update for Windows XP (KB901017)
    / Windows XP / SP3: Security Update for Windows XP (KB901214)
    / Windows XP / SP3: Security Update for Windows XP (KB902400)
    / Windows XP / SP3: Security Update for Windows XP (KB904706)
    / Windows XP / SP3: Security Update for Windows XP (KB905414)
    / Windows XP / SP3: Security Update for Windows XP (KB905749)
    Last edited by Tex10; 2005-12-10 at 20:08.

  3. #13
    Esteemed Member
    Join Date
    Oct 2005
    Posts
    554

    Default

    That's it and they look OK, though I wanted the '--- System information ---' section after it too, just to be sure about the condition of Windows. You could post that if you wish, even add it to the post above using edit, I'll see it.

    I have to head out to real life for awile, probably won't post again until late evening. I need to think about the best step to take next anyway. Feel free to try adding back the detections one at a time by checking the SBI filenames in File Sets one at a time in reverse (Security, then Revision, etc.) and running a scan. At some point it should freeze again.

    If you'd rather wait til later, that's fine, but if you've got more time now then later the above should at least tell us what combination might be causing the freeze. Once it does freeze, try scanning only the last one checked with the Spybots.sbi checked also. Then we'll know if it's the combination of all the SBI files or just the two checked that's causing it.

    Lot's of testing, so take it at whatever pace works for you, I'll get back as I'm able.

  4. #14
    Junior Member
    Join Date
    Dec 2005
    Location
    Calgary, Alberta, Canada
    Posts
    11

    Default

    Quote Originally Posted by bitman
    That's it and they look OK, though I wanted the '--- System information ---' section after it too, just to be sure about the condition of Windows. You could post that if you wish, even add it to the post above using edit, I'll see it.

    I have to head out to real life for awile, probably won't post again until late evening. I need to think about the best step to take next anyway. Feel free to try adding back the detections one at a time by checking the SBI filenames in File Sets one at a time in reverse (Security, then Revision, etc.) and running a scan. At some point it should freeze again.

    If you'd rather wait til later, that's fine, but if you've got more time now then later the above should at least tell us what combination might be causing the freeze. Once it does freeze, try scanning only the last one checked with the Spybots.sbi checked also. Then we'll know if it's the combination of all the SBI files or just the two checked that's causing it.

    Lot's of testing, so take it at whatever pace works for you, I'll get back as I'm able.
    Hi bitman; Okay, I have used the "Edit" and included the "System Information" as requested. I will start adding the detections one at a time. I will have to do this later as well as I have to go shopping for food. Thanks again. I do appreciate it.....

  5. #15
    Junior Member
    Join Date
    Dec 2005
    Location
    Calgary, Alberta, Canada
    Posts
    11

    Default

    Hi bitman; This morning I started adding the File Sets back and running a scan with each. The Spybot program frooze the computer after adding "Hijackers.sbi" at "GoldenPlace.Casino". The definitions that were selected are:
    "Trojans.sbi"
    "Spybots.sbi"
    "Security.sbi"
    "Revision.cbi"
    "PUPS.sbi"
    "Malware.sbi"
    "Keyloggers.sbi"
    "Hijackers.sbi"
    The only two left to check (select) were:
    "Dialer.sbi"
    "Cookies.sbi"
    Hope this helps in determining the resolution to this matter...

  6. #16
    Junior Member
    Join Date
    Dec 2005
    Location
    Calgary, Alberta, Canada
    Posts
    11

    Default

    Quote Originally Posted by Tex10
    Hi bitman; This morning I started adding the File Sets back and running a scan with each. The Spybot program frooze the computer after adding "Hijackers.sbi" at "GoldenPlace.Casino". The definitions that were selected are:
    "Trojans.sbi"
    "Spybots.sbi"
    "Security.sbi"
    "Revision.cbi"
    "PUPS.sbi"
    "Malware.sbi"
    "Keyloggers.sbi"
    "Hijackers.sbi"
    The only two left to check (select) were:
    "Dialer.sbi"
    "Cookies.sbi"
    Hope this helps in determining the resolution to this matter...
    Hi Bitman; it has been awhile since I posted the above and I have not heard from you. I understand that it has been over the holidays, but I would still like to solve this problem. Looking forward to your reply after you review this post. Thanks....

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •