Computer Folks got a quick question
Senior Member
Joined: Mar 2000
Posts: 481
Likes: 0
From: Westminster, CO
Originally Posted by jdoggfx4
I have a friends laptop and when you try to boot it up it gets to the windows login screen then has a error of (Isass.exe-System Error) Any Ideas!!!!
Senior Member
Joined: Mar 2000
Posts: 481
Likes: 0
From: Westminster, CO
Originally Posted by jdoggfx4
I can not boot into safe mode. Once I borrow a copy of it how do I get it on there with not being able to get past the login screen?
Senior Member
Joined: Dec 2004
Posts: 891
Likes: 1
From: Lost some where in the middle of the Ozark Mountains!
If it is a capitol L you are ok......
If it is lower case L then that is a virus.... This is from the same family as W32.Sasser....... which has many relations
If it's the virus, good luck... I can point you to the directions for a complete recovery but it's not an easy road.
If it is lower case L then that is a virus.... This is from the same family as W32.Sasser....... which has many relations
If it's the virus, good luck... I can point you to the directions for a complete recovery but it's not an easy road.
Thread Starter
|
Senior Member
Joined: Oct 2004
Posts: 338
Likes: 0
Originally Posted by PSS-Mag
If it is a capitol L you are ok......
If it is lower case L then that is a virus.... This is from the same family as W32.Sasser....... which has many relations
If it's the virus, good luck... I can point you to the directions for a complete recovery but it's not an easy road.
If it is lower case L then that is a virus.... This is from the same family as W32.Sasser....... which has many relations
If it's the virus, good luck... I can point you to the directions for a complete recovery but it's not an easy road.
I would have to assume that it is the lower case L since I thought it was a Capital I so any help would be great I was thinking of pulling the hard drive, setting it as a slave and just getting the important stuff off it and then reformat, But I'm open to ideas.
Trending Topics
Senior Member
Joined: Mar 2000
Posts: 481
Likes: 0
From: Westminster, CO
Originally Posted by PSS-Mag
If it is a capitol L you are ok......
If it is lower case L then that is a virus.... This is from the same family as W32.Sasser....... which has many relations
If it's the virus, good luck... I can point you to the directions for a complete recovery but it's not an easy road.
If it is lower case L then that is a virus.... This is from the same family as W32.Sasser....... which has many relations
If it's the virus, good luck... I can point you to the directions for a complete recovery but it's not an easy road.
Why dont you clue us in on how to fix it
Senior Member
Joined: Dec 2004
Posts: 891
Likes: 1
From: Lost some where in the middle of the Ozark Mountains!
From another poster with same virus on another forum....
Originally Posted by Russ Wanchisen
Good News everybody!
After suffering from a (seemingly catastrophic) fatal: "lsass.exe - System Error, Object Name not found" boot msg, I was able to successfully recover the OS and get my PC back up & running again! (even without an XP install CD)!
Here's how I did it:
On a separate machine, I navigated over to Microsoft's website and looked into the details of creating a set of Windows XP Setup boot disks. I found all the necessary information here: ( http://support.microsoft.com/default...b;en-us;310994 ). Since my home PC (the one with the lsass.exe error) was running XP Home Edition with SP1, the "winxpsp1_en_hom_bf.exe" file was appropriate for me. That program generated six (6) floppy disks which I subsequently used to boot up my XP Home machine and get into the "Microsoft Windows Recovery Console" mode as described here: http://support.microsoft.com/default...b;en-us;307654 "Recovery Console" mode is a DOS-like mode with limited access to the Windows directory system files (it supports FAT & NTFS file formats, but file access is limited to only the "root" OS sub-folders. User data files are not accessible in "Recovery Console" mode).
OK, now that I was able to boot from the floppies (and access the OS system files), I pretty much followed all the details presented by Charlie White as described in his article "Windows XP crashed? Here's help" (quick-link here: http://www.tunexp.com/faqs/windows_x...ed_heres_help/ ).
In summary, the instructions he provides allow you to effectively perform a manual system restore on your machine.
So, now in the future, if your machine fails on boot-up, don't fret! First try to force a "manual system restore"... If all goes well, you should have your machine back up/running in no time!
Good luck!
Russ
N.B. All the details in Charlie White's article are correct except a small detail in Part 1 where you grab the original system repair files out of the "c:\windows\repair" subdirectory: Specifically, on my machine, the "c:\windows\repair\system" file was actually called "c:\windows\repair\system.bak" (note the ".bak" suffix). As such, the line where he says to
"copy C:\windows\repair\system C:\windows\system32\config\system",
should actually read:
"copy C:\windows\repair\system.bak C:\windows\system32\config\system"
After suffering from a (seemingly catastrophic) fatal: "lsass.exe - System Error, Object Name not found" boot msg, I was able to successfully recover the OS and get my PC back up & running again! (even without an XP install CD)!
Here's how I did it:
On a separate machine, I navigated over to Microsoft's website and looked into the details of creating a set of Windows XP Setup boot disks. I found all the necessary information here: ( http://support.microsoft.com/default...b;en-us;310994 ). Since my home PC (the one with the lsass.exe error) was running XP Home Edition with SP1, the "winxpsp1_en_hom_bf.exe" file was appropriate for me. That program generated six (6) floppy disks which I subsequently used to boot up my XP Home machine and get into the "Microsoft Windows Recovery Console" mode as described here: http://support.microsoft.com/default...b;en-us;307654 "Recovery Console" mode is a DOS-like mode with limited access to the Windows directory system files (it supports FAT & NTFS file formats, but file access is limited to only the "root" OS sub-folders. User data files are not accessible in "Recovery Console" mode).
OK, now that I was able to boot from the floppies (and access the OS system files), I pretty much followed all the details presented by Charlie White as described in his article "Windows XP crashed? Here's help" (quick-link here: http://www.tunexp.com/faqs/windows_x...ed_heres_help/ ).
In summary, the instructions he provides allow you to effectively perform a manual system restore on your machine.
So, now in the future, if your machine fails on boot-up, don't fret! First try to force a "manual system restore"... If all goes well, you should have your machine back up/running in no time!
Good luck!
Russ
N.B. All the details in Charlie White's article are correct except a small detail in Part 1 where you grab the original system repair files out of the "c:\windows\repair" subdirectory: Specifically, on my machine, the "c:\windows\repair\system" file was actually called "c:\windows\repair\system.bak" (note the ".bak" suffix). As such, the line where he says to
"copy C:\windows\repair\system C:\windows\system32\config\system",
should actually read:
"copy C:\windows\repair\system.bak C:\windows\system32\config\system"
Senior Member
Joined: Dec 2004
Posts: 891
Likes: 1
From: Lost some where in the middle of the Ozark Mountains!
Then you;ll aslo need
Originally Posted by EiD_Sir_Airman01
It appears you have the SASSER WORM, lsass.exe has a flaw in it, sasser worm attacks that flaw and causes problems for the system, grab the latest Stinger from Network Associates(Creators of McAfee Virus Scan), grab this patch http://www.microsoft.com/downloads/d...displaylang=en after grabbing those 2, turn off system restore, unplug ur computer from the internet line, run Stinger, it should remove the crap that is causing that, afterwards, install the patch, then enable the windows firewall and restart computer than renable the System Restore
Thread Starter
|
Senior Member
Joined: Oct 2004
Posts: 338
Likes: 0
Originally Posted by PSS-Mag
Yea thats what I would do too if there wasnt anything really important on it.
Be sure the master is up to date before hooking the infected drive up.
Be sure the master is up to date before hooking the infected drive up.
I did I pulled all the important info and then scanned the folders and files I pulled. They all came up clean.
