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.

Photo

Help! Iolo Sys Mech Pro Killed TWO Machines on Same Day


  • This topic is locked This topic is locked
4 replies to this topic

#1 deandome

deandome

  • Members
  • 65 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:54 PM

Posted 09 April 2010 - 01:07 PM

This is extremely weird troubling.

I have an HP desktop running XP Media Ctr (SP3), my mom has a Dell desktop running XP Media Ctr (SP3). I

We've both been using Iolo System Mechanic Professional for over a year (it has 3 licenses) , but we had Norton 360 before that, (also 3 licenses) so we was only using the diagnostic stuff, not the firewall & antivirus components.

I renewed our SysMechPro about a month ago about the same time 360 expired...so rather than pony up $80 to renew 360, we removed it & installed the full SysMechPro package (updated to v9.5). BTW, I used the 3rd SysMech 'seat' on my office laptop, but that is/will always be diagnostics/repair only;It is FINE...no problems...making me think the prob below has to be w/the firewall or antivirus components.

SysMech scans & updates automatically, so sometimes you see "you must reboot your computer to complete your repairs. I got that Wed night, and shut down completely. My mom always shuts down.

Low and behold, Thursday morning...BOTH OF OUR COMPUTERS ARE CRASHED!!! Mine is caught in a rebooting loop (but get BSOD when I hit "disable auto-restart", hers goes right to SAME BSOC that say "serious damage...blah blah...preventing..blah blah...restart"...then some error codes:

0x0000007B (0XBA4C3524, 0X0000034, 0X0000000) I think this means there's no driver for my hard drive or something

We can't start in safemode (or anything). I have a PowerSuite recovery disc...it says it can't find windows. I CAN get to my disc via a Winernals program, so I think I can pullout my docs/photos.

And I called Iolo, and they gave me these instructions:

Boot from windows cd and wait for the main setup menu.
Press R to enter recovery console.
Choose 1 as seen below and enter the admin pw.

Then type this command:

cd system32\drivers
ren atapi.sys atapi.old
expand D:\i386\atapi.sy_

Get message 1 file expanded
Reboot normally.

(btw, how do I do those 3 'lines'; all together (they DO say "..this command" [singular] Or do I do them one at a time with "enter" after each one?)

I'll certainly try that, but my god...Iolo tried to say it must have been a virus or something. HUH? My 84 yo mother & I really don't surf the same sites, and the fact that they both crashed THE SAME FRIGGEN DAY, THE SAME FRIGGEN WAY has to signal it's the program's fault.

Did this happen to anyone else? Do you think that fix looks good?

Thanks!

Edited by deandome, 09 April 2010 - 01:30 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:54 PM

Posted 09 April 2010 - 03:01 PM

System Mechanic...I tried that during my Win 98 days and found that it did nothing useful that I could not do without it.

Just for the record...BC (and others) takes a dim view of such programs, for the very reasons that you now are experiencing.

Why I Don't Use Registry Cleaners Mr. Bott is, among other things, the person who hosted the first computer forum I ever visited/participated in. I, and others, hold his advice/suggestions in high regard.

Should I Use A Registry Cleaner - http://aumha.net/viewtopic.php?t=28099.

To answer your questions...I have a question...have you actually tried following the directions provided?

Are these two systems part of a home network?

The "fix" may or may not work, trying it will reveal such. There's no point in speculating as to whether it will work, when attempting to execute it will reveal whether it works or not.

Iolo may have had documented history where their software produced this particular STOP error...I don't know, you don't indicate why they suggested the sequence you listed. I will say that the cure for this type of STOP error varies and is not something universally agreed on.

Google List, 7B STOP Errors

The typical "authority" on STOP errors is at http://www.aumha.org/a/stop.htm. This site reflects generic info on various types of STOP errors, yours (7B) can be found by scrolling the left column. As you see, 7B is "inaccessible boot device" but the fact is that any number of situations can cause this.

If I had this error...I would start with checking the status of the hard drive itself. The known correction I would employ...would be a repair install of XP.

Louis

#3 tg1911

tg1911

    Lord Spam Magnet


  • Members
  • 19,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:SW Louisiana
  • Local time:10:54 PM

Posted 09 April 2010 - 06:52 PM

In answer to one of your questions:
QUOTE
Or do I do them one at a time with "enter" after each one?
This is the correct procedure.
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

#4 JSntgRvr

JSntgRvr

    Master Surgeon General


  • Malware Response Team
  • 11,693 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:12:54 AM

Posted 11 April 2010 - 12:10 AM

Hi, deandome smile.gif

Welcome.

Lets give this a try. You will need a flash drive to move information from the sick computer to a working computer. It is the only way we can see the progress of our actions. Save these instructions in your flash drive as a text file (use notepad) so you can have access to these while in an external environment (PE).

Here is what you need to do.

Two programs to download

First

Download ISOBurner. Click Here for ISOBurner Instructions. Install the program, and follow the next set of steps.

Second
  • Download OTLPE.iso and burn to a CD using ISO Burner. NOTE: This file is 276.7MB in size so it may take some time to download.
  • When downloaded double click and this will then open ISOBurner to burn the file to CD
  • Boot the Non working computer using the boot CD you just created.
  • In order to do so, the computer must be set to boot from the CD first
    Note : For information click here
  • Your system should now display a REATOGO-X-PE desktop.
  • Double-click on the OTLPE icon.
  • When asked "Do you wish to load the remote registry", select Yes
  • When asked "Do you wish to load remote user profile(s) for scanning", select Yes
  • Ensure the box "Automatically Load All Remaining Users" is checked and press OK
  • OTL should now start. Change the following settings
    • Change Drivers to All
    • Change Standart Registry to All
    • Under the Custom Scan box paste this in

      /md5start
      eventlog.dll
      scecli.dll
      netlogon.dll
      cngaudit.dll
      sceclt.dll
      ntelogon.dll
      logevent.dll
      iaStor.sys
      nvstor.sys
      atapi.sys
      IdeChnDr.sys
      viasraid.sys
      AGP440.sys
      vaxscsi.sys
      nvatabus.sys
      viamraid.sys
      nvata.sys
      nvgts.sys
      iastorv.sys
      ViPrt.sys
      eNetHook.dll
      ahcix86.sys
      KR10N.sys
      nvstor32.sys
      ahcix86s.sys
      nvrd32.sys
      userinit.exe
      explorer.exe
      ntoskrnl.exe
      /md5stop
      %SYSTEMDRIVE%\*.*
      %systemroot%\*. /mp /s
      %systemroot%\System32\config\*.sav
  • Press Run Scan to start the scan.
  • When finished, the file will be saved in drive C:\OTL.txt
  • Copy this file to your USB drive.
  • Please post the contents of the C:\OTL.txt file in your reply.

No request for help throughout private messaging will be attended.

If I have helped you, consider making a donation to help me continue the fight against Malware!
btn_donate_SM.gif


#5 JSntgRvr

JSntgRvr

    Master Surgeon General


  • Malware Response Team
  • 11,693 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:12:54 AM

Posted 27 April 2010 - 12:54 AM

Due to lack of feedback, this topic has been closed.

If you need this topic reopened, please contact a staff member with address of this thread. This applies only to the original topic starter. Everyone else please begin a New Topic.

No request for help throughout private messaging will be attended.

If I have helped you, consider making a donation to help me continue the fight against Malware!
btn_donate_SM.gif





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users