How to find out the DLL file that caused system failure in WinXP

Everyone knows the importance of DLL files. In the running process of WinXP, almost all programs use DLL programs, but many system software failures are often caused by DLL programs. A lot of DLL programs, then how can we find out the culprit causing the system failure? The following small series will tell you the solution through a case.

Case playback: After an illegal operation, WinXP & ldquo; Search Companion & rdquo; become a & ldquo; whiteboard & rdquo ;, only that, & ldquo; Control Panel & rdquo; in & ldquo; user account & rdquo; The item also appears to be “no expression”. Click “Start →Help and Support”, the mouse flashes but never sees <;Help & Support” program interface traces.

Case Study: Based on the feeling, Xiao Bian believes that a DLL file in the system has been logged out, lost or damaged. However, almost every program in WinXP has to be called into hundreds of DLL files. If you look for analysis one by one in the usual way, it is tantamount to finding a needle in a haystack. Considering that the three programs are "destroyed" at the same time, they should be affected by the same (or several) DLL files. To do this, you must find the DLL file that is used together by the above three programs, and then find out from the behind-the-scenes murderer.

Finding and Comparing

Step 1: Start with “Search Assistant> first, and get rid of it <;history of the world”. Open “Search Assistant> in another machine with WinXP, and press Ctrl+Alt+Del to bring up the “Task Manager”, in the “Applications” tab, select ““ Search Assistant & rdquo; and right click, select & ldquo; go to the process & nbsp;, huh, it turns out that it is part of Explorer.exe (resource manager).

Step 2: Use a similar method to know that “Help and Support” belongs to the process Helpctr.exe, but in the “User Account”, you can only use the method of observation and comparison to find out the attribution process. Mshta.exe.

Tips

You can determine the process to which you belong by comparing the changes in the "Task Manager" by turning the "User Account" on or off; you can also open &ldquo When searching for the assistant, enter "<quo;tasklist /fo table>C:acc1.txt” in the "command prompt"", after closing the program, enter “tasklist in “command prompt" /fo table>C:acc2.txt”, then use the fc command to compare “fc C:acc1.txt C:acc2.txt>C:acc.txt”, the extra items obtained by comparison are the program belongs to process.

Step 3: Restart the computer. Please check the software LISTDLLS. Download the software here, then move listdlls.exe to C:Windows, press Ctrl+R to open the "Run" box, type "ldd;cmd", and type in the "Command prompt":

listdlls -r explorer.exe>C:explorer1.txt.

Then open “Search Assistant”, again in the “command prompt""listdlls -r explorer.exe>C:explorer2.txt

Finally use the fc command Comparison:

fc C:explorer1.txt C:explorer2.txt>C:explorer.txt.

This opens the C:explorer.txt file, and the extra file after comparison is the DLL file called "Search Assistant".

Tips

The usage of ListDlls is: listdlls [-r] [processname pid] or listdlls [-r] [-d dllname]

Step 4: Restart Computer, use the command “listdlls -r helpctr.exe>C:helpctr.txt” to get the DLL file used by “Help and Support”. The restart here is to unload the DLL files that have not been used from the memory.

Step 5: Restart again, use the command “listdlls -r mshta.exe>C:mshta.txt” to get the DLL file used by “user account”.

Filtering the last "true fierce"

Analyze the DLL file in explorer.txt, where the file directory contains “srchasst”, all “search assistant” document. The remaining files are sxs.dll, vbscript.dll, jscript.dll files in the C:Windowssystem32 directory. You can find the above files in the files helpctr.txt and mshta.txt by using the "Search" method. It seems that "the culprit" is not the three.

Back to the original computer, I found that all three files existed and were not damaged. Register with the regsvr32 command. Sure enough, after registering the jscript.dll file (using the command regsvr32 jscript.dll), the "whiteboard> program finally restored its beautiful  face".

Finally, I want to explain to you that many software failures in the system are caused by DLL file errors. In the past, we often paid more attention to whether the DLL file was lost. In fact, there are still many reasons why the DLL file was not registered successfully. After reading the method described in this article, we can easily find out the DLL file that caused the failure, and give the best solution, and finally solve the problem.