Probedis.exe DLL Initialization Failed Error

J

JSM

For the past couple of years, whenever I shut down my computer I get a
"Probedis.exe DLL Initialization Failed" error. I've tried this fix:

Step 1:

1. From our support site download the 5699B_XP_2k_v170.exe file to a
temporary location on your computer's hard drive.

Here is direct link to the driver.

http://www.usr.com/support/5699b/5699b-files/5699B_XP_2k_v170.exe

2. Double-click the file in Windows Explorer. The file will self
extract
to C:\USR\5699B. Windows XP will install your modem with a default
driver. This default driver will need to be updated from the Device
Manager to reflect the current driver for your modem.

3. Select Start, right-click My Computer, select Properties, select
Hardware, and select Device Manager.

4. From the Device Manager window, double-click Modems, right-click
U.S.
Robotics 56K Fax Win, and select Update Driver. This will prompt the
Hardware Update Wizard to begin.

5. Select Install from a list or specific location(Advanced). Click
Next.

6. In the Please choose your search and installation options window,
select Don't search. I will choose the driver to install and click
Next.
Windows will show you the current driver that is installed for the
modem.

7. Make sure U.S. Robotics 56K Fax Win is selected and click Have Disk.
8. Type C:\USR\5699B in the Copy manufacturer's file from field and
click Okay.

9. Click Next. If the Hardware Installation window appears, click
Continue Anyway.

10. Click Finish.

11. Close any open windows.

12. Restart your PC.

This should fix the problem.

Step 2:

- Click Start, Run... and type in msconfig and click OK.
- When System Configuration window pops up click the Startup tab.
- Under the Startup Item, uncheck the 3compip.exe (not sure what is the
exact name) which has Command address of "C:\Windows\system32\"
- Click OK and restart your computer.

This eliminated the error, but it also disabled my modem. U.S.
Robotics' only response was to refer me to the support page for my
modem. Does anyone have a solution for this problem?
 
B

Brian A.

Try a different modem, some are problematic with an OS and a real PITA to get up and
running. I had a Netgear NIC that when installed kept the machine from booting.
After 2 days of battling with it I swapped it out for an IBM NIC and never looked
back again.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top