All Compiled Exes Start to Crash

Keywords:  Crash GPF encountered problem

Question:

Seemingly for no apparent reason, all WinBatch executable stop working on some of our user�s laptops. The users receive a message stating � has encountered a problem and needs to close.� If I move these programs to another machine, they run fine, so I�m assuming that the problem exists with something external to the exe (.dll?)
Troubleshooting:
I�ve replaced all the Full exe�s
I�ve deleted all of the WinBatch .dll files and let them extract from the full exe
Cleared all of the temp/internet temp files
Tried reregistering the WinBatch .dll files

Dependency Walker information:
Every WinBatch has its Link Checksum highlighted in Red
I get Warning: At least one delay-load dependency module was not found. I think this is the MSJAVA.DLL file which I�ve seen posted here as not to be concerned with.
I also get Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

Environment:
WinXP SP2
IE 6
Office 2003
.Net 2.0

Out of a user population a little under 2,000, I�ve seen about 30 of these in the past 6 months.

Any help would be appreciated, as the only resolution I have now is to have the users ship their laptop in to be re-imaged.

Answer:

So at some point the WinBatch scripts did run okay on the problem systems, then mysteriously started crashing. Correct?

IMPORTANT: Make sure you can run Perfmon.exe. Try adding a Process counter. If there is ANY issue running perfmon.exe, address the issue with performance monitoring on the system. At command line run 'Lodctr /R' to restore counter settings.
What Virus scanners are installed on these systems? Do they have all the latest updates? Compare the virus utilities on the problem systems with working systems. Are they the same or different? At some point in the distant past, it seems the WIL DLL (WBDEG44I.DLL) was incorrectly flagged as possibly having a virus. This incorrect information was duplicated to some other related utilities, including several free ones. Heavy suspicions are being focused on virus scanners / system protection utilities. Check all related log files correctly.
Check the event logs for anything that looks interesting.
Run Dependency Walker to help track down any system dll problems.Goto http://www.dependencywalker.com and download the free dependency walker. On a failing machine point it at the WIL DLL (WBD__44I.DLL) file and see if it red flags anything. If so Fix it. Usually some kind of system dll disaster struck. If a quick look at the dependency walker screen does not flag any dlls, then run (profile) your script thru dependency walker and then look at the log file. Usually very near the bottom the problem crops up and then the program exits and the log ends. With that info you can figure out how to fix your systems.
Is there anything in common on all of the problem workstations?
You may wish to try a current version of WinBatch and see the the problem just mysteriously disappears.

Article ID:   W16910

File Created: 2013:05:21:07:58:54

Last Updated: 2013:05:21:07:58:54

Database Search

TechHome