Another Rundll Problem (Unique, I think)

Whenever I try to run some, but not all, exe files from Windows Explorer, Power Desk, 2xExplorer, etc..., I get a popup error message: Rundll.exe (not 32) has encountered a problem and needs to close.

When I drop to the DOS prompt and run the same file, it works fine.

I guess this means I'm having a problem with 16 bit exe's.

Any ideas??? I'm stumped.

Thanks.

WindowsXP Professional - Up to date
Compaq 1gig Athlon - 512 RAM
NVidia GeForce2 MX/MX400 - 64meg

 

Tried all the compatibility modes. No go.

Thanks Pete.

 

More details in your event logs?

 

Tried safe mode. No go.

Applications event log:

Faulting application rundll.exe, version 0.0.0.0, faulting module rundll.exe, version 0.0.0.0, fault address 0x00001e6f.

No errors in the System event log.

 

Open the event again and then click on the icon below the up/down arrows. That will put a text copy of the entire event in your clipboard. Post that please.

 

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 11/27/2003
Time: 9:56:21 AM
User: N/A
Computer: MYSTICAL
Description:
Faulting application rundll.exe, version 0.0.0.0, faulting module rundll.exe, version 0.0.0.0, fault address 0x00001e6f.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 72 75 6e ure run
0018: 64 6c 6c 2e 65 78 65 20 dll.exe
0020: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0028: 69 6e 20 72 75 6e 64 6c in rundl
0030: 6c 2e 65 78 65 20 30 2e l.exe 0.
0038: 30 2e 30 2e 30 20 61 74 0.0.0 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 30 30 30 30 31 65 36 66 00001e6f
0050: 0d 0a ..

 

Your problem is similar enough to This one that the same fix should work.

 

Thanks, Newt.

I didn't do a repair because I didn't want to install all the hot fixes again, but I tried "sfc /scannow" and it seems to have worked. Should have been awake enough to try that first.

 

Glad sfc worked on this problem. Certainly the simplest fix. And hopefully (if all is working right with sfc) it will have put the updated versions of any bad files back in place. It's supposed to work like that and usually does. Usually.