Posted on 12/14/2009 12:05:45 PM PST by Lady Jag
SISZYD32.exe has possibly killed my FR computer.
Yesterday it hit suddenly despite the anti-virus and other utilities I run to protect against such stuff.
The victim computer is one I only use for FR and the sites it cites. That is the only clue I have to offer as to where it came from. I run several computers off a network and my FR computer is the only victim.
This is the worst I have ever encountered and a search for it shows that it is very dangerous and it showed up only about a week ago (AFAICT).
From years of experience I knew what to do yet the virus blocked every action, not even allowing startup in safe mode.
MalwarBytes, Spyware Doctor, SpyHunter and another one or two I tried to run were able to find it yet were blocked and defeated by siszyd32.exe.
This is day 2 and the computer boots with a black screen.
WARNING! Update all your protection software including registry cleaner, et al.
HELP! Can anybody help me get my FR black screen computer back?
Not sure ow you arrived at that...I might have missed something...
but I thought the last difficulty was that she was not seeing a BIOS screen...which to me would indicate, one of a)keyboard problem b)monitor problem C) motherboard problem
a couple days yes.
Make sure you back up your files or tell them to do it..for another 99 bucks.
Is is possible and worth trying to recover some files?
What's this thing about freezing the drive bringing it temporarily back to life?
Freezing has worked for me twice. Left it in the freezer overnight and the next day plug it in and turn it on. It worked for me about 3-5mins the first time and almost 10 mins the second time. If you can’t get everything off the first time freeze and try again. I could do it twice with one of them before it finally had enough.
I wouldn’t waste time getting it out of the fridge and open the case, mount it in the drive bay, etc. Have the case open, plug in the drive cable and power cable and turn on the box.
It may sweat as it warms up so keep that in mind :-)
What programs did you have on the drive that you can't find the original material to reinstall them on a new drive....?
STOP - don’t freeze HD until you know for sure that it’s dead. Questions need to be asked/answered first.
The first thing to check is the drive jumper - if you connected the drive as a secondary drive, then you must change the jumpers on both primary and secondary drives to be sure they correctly reflect that (or that both jumpers are set to auto-select and the bios, OS, and type of connecting cables support that).
1. Is the HDD (hard disc drive) in question a recent larger drive? The bios of older computers can not recognize HDD larger than 32 gig. And the bios of really old computers freak out if not below 1 gig. The bios is the software hardcoded on a chip on the motherboard that starts the computer, tests basic hardware, and calls up the OS (operating system - Windows, Dos, etc.).
2. If the bios recognizes the HDD, but your OS does not, then the file system type might not be recognized by the OS on that computer.
3. The file system used might be locked (such as NTFS) or encrypted. This is probably not your problem (yet) if you can not even see the drive listed.
4. If you can get a computer to recognize the drive, but just can’t access the files (assuming the same file system), then you might be able to recover the drive with a very good program designed to do that. I use Spinrite 6 by Steve Gibson. It is a very good program which I have used for many years (starting with version 1) and has a reasonable price. It has several levels of recovery which take progressively longer for the deeper levels if needed (up to a day for deepest level and really large drives). It’s very thorough and worth the money. I have recovered some really messed up drives using this program:
5. If your data is really important, there are very good data recovery services/companies that can recover all your data for a fee, even on physically damaged drives.
Hope this helps.
When you moved the drive to another computer did you detach the drive in the receiving computer.
If you just plugged it in along with the other drive you would likely have two drives on the same cable with both set as Master....in which case only one would be recognized....
OOPS - sorry, I meant master/slave instead of primary/secondary.
My excuse - it’s been a long day, it’s late and I’m tired plus it’s been awhile since I actually had to work on a computer.
(Well, that sounds good, right? Right?) LOL
Say goodnight, Gracie.
Goodnight Gracie.
;>D
I love sandboxie... but the problem I have is that it cannot and will not be installed an a x64 >.<
Bikk
All the drive activity of the trojan loader and removal efforts probably ended its miserable life, but it was showing signs of trouble for a long time. Bootups took longer and longer, etc., and files corrupted, but scandisk never found anything wrong when it did run.
People who write trojan loaders, etc do NOT want the machine disabled. They NEED a running machine to sell for their botnets. A broken machine is of no value to them...So I do not regard it as an atack per se.
Anyway, recovering the data from a badly infected drive may not be the best answer anyway. It's like digging up the corpse of a plague victim.
I was thinking it could be the BIOS.
Years ago in the mid 90’s I had a black screen and of course we are to make a copy of our hard drive which I never did.
But one can go to Statbles etc they have that CD back up for almost all kinds of computers to restore the BIOS.
How to enter the BIOS or CMOS setup
http://www.computerhope.com/issues/ch000192.htm
How to Set BIOS to Boot from CDROM
http://www.hiren.info/pages/bios-boot-cdrom
Some where among your CD’s that came with the computer you might have that CD!
That is why we moved the drive to an intact machine with a proven BIOS. No Joy. I replaced the BIOS battery in the sick computer as the first effort. Nope, it’s the HD. :-(
What is siszyd32.exe, How to remove siszyd32.exe
http://htlogs.com/what-is-siszyd32-exe-how-to-remove-siszyd32-exe/
siszyd32.exeDec 8, 2009 ... siszyd32.exe was added to FreeFixer’s database on 7th December 2009. The most recent search for this file was done on 7th December 2009. ...
Did we all forget that Dec 7 was D-day?
“A Date Which Will Live in Infamy”: FDR Asks for a Declaration of War
The Japanese attack on Pearl Harbor, Hawaii, on December 7, 1941, stunned virtually everyone in the United States military. Japan’s carrier-launched bombers found Pearl Harbor totally unprepared. President Franklin Roosevelt quickly addressed Congress to ask for a declaration of war as illustrated in this audio excerpt. Although he never mentioned Europe or the fact that Germany had by then declared war on the United States, the Pearl Harbor attack allowed him to begin the larger intervention in the European war he had long wanted.
http://historymatters.gmu.edu/d/5166/
LJ's BIOS began to boot and passed the POST (Power on self test), but since the boot device was dead and it could find no other devices to boot from it just threw up its hands in despair, or looped trying to find them.
It sure was D-Day hell for a precious old Dell!
Most everything was backed up except for some contacts & a few other important files in MS Outlook email. Sure has put a damper on Christmas activities.
Freezing, never heard of that, but there are some problems I can see it might temporarily remedy. Bugaboo could be the condensation building up on the external circuit board while it's running.
Something else - if you put it in another computer as a slave on the primary controller there may be a slave jumper on the drive that you need to set. Also, depending on the second computer you might need to go into it's setup and allow it to autodetect the drive.
My second computer is a netbook (Acer Aspire One) and I love it. Solid little computer that's literally the size of a book. Very convenient to carry from room to room or use when traveling. Oh I do keep an extra strong pair of reading glasses in the carrying case because the screen is small.
This is a first for me. Never saw such a thing! I don’t think it was 2 hours between Avast reporting the virus and the drive dying.
Re: freezing. I’m not going to try it but it works. First you put it in an ant-static bag and then a ziploc, freeze it for 72 hrs, and when you take the drive out, work it ASAP.
Someone upthread said it worked on the same drive twice.
I’m too saturated to try anything more at the moment so I’m trying to convince myself that what is lost can be lived without. I was going to replace the old Dell after the start of the new year, anyway, and had copied a lot of the files...
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.