Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
my pc wont load into win xp pro, complains of bad image (lass.exe) in the file c:\windows\system32\dnsapi.dll. Says its not a valid windows image. So it wont even let me log in. Have tried the advice found here: http://www.cyberspacesupport.com/question.php?question_id=3127 of using recovery console to build new boot list but to no avail. Any help welcome!!!
Are you sure that's the filename? It's not lsass or isass?
Life is more painless for those who are brainless.
0 
Go to your XP cd ( SP2 if installed ) & copy dnsapi.dll, then paste it into System32 & it will overwrite the file there.
Or,
Click Start and then click Run.
In the Open box, copy & paste > sfc /scannow, and then click OK. Note that you may be prompted to insert the Windows XP installation CD-ROM.
http://www.updatexp.com/scannow-sfc.html
http://askmaggymae.com/Maintenance/sfcxp.htm
Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310747
0
Hi Jennifer, dont know, will check ASAP.
Hi Johnw, cant get past error screen so cant use any of OS resources like startbar, copy & paste e.t.c. Though presumably I could try copying after booting into dos using a boot disk? Also - could I try the scannow from dos/wrc?
0
No, exact same problem - :).
Yes, it was lsass.exe - Bad Image.
Tried Safe Mode and Last Known Good Config before the fix suggested on cyberspacesupport, (which has now brought up two OS's to start when PC begins to boot up). Also wrote something to distinguish the two (in terms of nomenclature) just in case so have definately tried the one that is supposed to have had the boot list rebuilt.
0
Right, just to throw an added complication into the mix: just tried re-installing XP, three times, each time it fails half way through - just after entering serial code, keyboard/language settings, TCP/IP settings. Every time it starts copying files but then says it cant find a file on disk - and each time the filename changes.
Nothing wrong with the disk - have used it to install OEM copies before and since with no problem.
Now, i'm thinking it may be to do with the hard disk??
So - just tried a boot disk and cant access c: (it says invalid drive specification). Also cant get into Safe Mode Command Prompt because of lsass.exe error as before. Will have to try Recovery Console to try sfc /scannow. Hope it works.
Only other fix I could see is installing the OS to another HDD and scanning this one as a slave.
0
Tried installing a new HDD with old one as slave to see if HD issue. Again had one file not copy during install so skipped:
"e:\windows\setuperr.log" =
Error:
D:\i386\rover.ac_ was not copied to E:\WINDOWS\srchasst\chars\rover.acs because of the following error:
The user chose to skip the file operation.
***Now everything appears to work fine except one error which says:
The application at "0x7727925" referenced memory at "0x7d462e20". The memory could not be "read".
Oh dear.
0
You may be able to get more info from the Event viewer.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427
Or,
Start > Run, copy & paste > eventvwr.msc /s & press Enter.
Scroll down to the last time your computer crashed and it should tell you what device/driver caused the problem?================================
Windows XP Events and Errors
Enter the message source and ID in the text field, then click Go.
http://www.microsoft.com/technet/support/eventserrors.mspx
http://www.microsoft.com/technet/support/ee/search.aspx?DisplayName=Windows%20XP%20Professional&ProdName=Windows%20Operating%20System&MajorMinor=5.1&LCID=1033You may get more info from minidumps.
Control Panel --> System --> Advanced --> Startup and Recovery --> Settings ---> Write debugging
information --> Complete memory dump
Minidumps are located in c/windows/minidumps
How to solve Windows system crashes in minutes
http://www.networkworld.com/news/2005/041105-windows-crash.html
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://forums.majorgeeks.com/showthread.php?t=35246
This primer will show you how to solve problems quickly. Using a tool that costs nothing, you can solve approximately 50% of Windows server and workstation crashes in a few minutes. The tool is WinDbg, the free Windows debugger.
You've probably never used the debugger, don't have it and don't want it. After all, it's a developer's tool, not an administrator's, right? Yes, but what you need to know is remarkably easy to learn, and even a rudimentary familiarity with the debugger could enhance your skills and your resume.
Still hesitant? Think about this: After rebooting a crashed machine, we've brought up the debugger, opened a memory dump file, given the debugger a single command, and learned not only that the cause was a driver, but also the driver's name — all in less than a minute. Granted, the debugger was installed and configured, we knew what commands to use and what to look for.
But so will you by the end of this article.
Or,
Event Log Explorer
http://www.eventlogxp.com/
http://www.eventlogxp.com/download/elex.zip
Event Log Explorer is a free software for viewing, monitoring and analyzing events recorded in Security, System, Application and another logs of Microsoft Windows NT/2000/XP/2003 operating systems. It extends standard Event Viewer monitoring functionality and brings new features.
Or,
Extract troubleshooting info from Windows XP BSOD error messages
http://techrepublic.com.com/5100-10877-6053684.html#
Or,
http://www.eventid.net/search.asp
Or,
Windows Error Generator
http://www.netdevel.net.nz/index.php?mod1=netdevel/software
Ever wondered what Error(312) means ? Look it up with this, or have it list all the errors your operating system is able to give. Also good for programmers who need to throw a specific system error. Go to Software menu.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
