Win7 will not connect to camera - device driver error 31

S

slate_leeper

I would suggest that you load the drivers that came with the camera on
the cd -

first delete the yellow marked device from the device manager

Stick the CD in the slot which came with the camera.

Connect the camera turn it on and force the computer to find the device
driver on the CD.

You can have BTW some devices which MS say are ok and working but aren't
because MS can't supply drivers for each and every device they are only
generic. Like printers scanners etc.

The Canon camera comes with no driver software, and the Canon website
says no special drivers are needed with Win-7. In addition, the camera
connected just fine until recently.




--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

How about the idea of doing a system repair with the win 7 operating system
disk?
That may restore USB functionality without losing any data.
Of course, before trying this, I would make an image backup of the
drive.


Yeah, I've thought of that. Kind of a last-gasp measure. I'm hoping we
can figure this out without resorting to that. I'm worried about what
other problems that might bring up.

-dan z-


--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

snip getting too long


What you may have to do is reset the USB ports.

MS have a Fixit solution on there site unsure which one it is to get but
have a look up problem solutions.

Google this - "microsoft W7 resetting usb ports" just to get started

or

http://preview.tinyurl.com/ab9yl3k

which is this page

https://www.google.com.au/search?q=...s=org.mozilla:en-US:official&client=firefox-a

I have run the "fix-it" routine, which ended giving the same error as
trying to reinstall the drivers.

-dan z-


--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.

By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.

"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.

Thanks for the reply.

-dan z-


--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
W

Wolf K

On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.

By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.
I'd move them to a safe location with a name change, just in case.
"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.
The keys are in the registry, which among other things refers to
locations of drivers, etc. Win uses it to find what's needed for devices
etc to work properly. Running regedit to clean up the registry ranges
from dead easy to very scary, depending on what's installed. But you may
want to explore the registry anyhow. Use Find to locate relevant keys.
It's a "learning opportunity", as they say. ;-)
Thanks for the reply.

-dan z-
You're welcome, it's last-resort, based on your comment that the USB
ports are OK, and that the same problem occurs on different ports.

Another last resort comment: the issue could be in the camera's
firmware, and/or the flash card's OS. Try reading the card with a card
reader.

Good luck.
 
S

slate_leeper

On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.

By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.
I'd move them to a safe location with a name change, just in case.
"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.
The keys are in the registry, which among other things refers to
locations of drivers, etc. Win uses it to find what's needed for devices
etc to work properly. Running regedit to clean up the registry ranges
from dead easy to very scary, depending on what's installed. But you may
want to explore the registry anyhow. Use Find to locate relevant keys.
It's a "learning opportunity", as they say. ;-)
Thanks for the reply.

-dan z-
You're welcome, it's last-resort, based on your comment that the USB
ports are OK, and that the same problem occurs on different ports.

Another last resort comment: the issue could be in the camera's
firmware, and/or the flash card's OS. Try reading the card with a card
reader.

Good luck.

OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?

New update.

I went back to un-rename (is that a word) the files, and found that
Update DID load new copies. However it still doesn't work. Same
symptoms as before. Update did not reinstall the WpdMtp.dll, but did
reinstall the WpdMtpUS.dll.

Also, yesterday I reinstalled the AMD driver software from ASUS, which
has the drivers for audio, video, USB, USB3, and PC-BUS. Still no
change.

It doesn't work in a USB3 port either. Same symptoms.

Card reader also still doesn't work. Same symptoms.

Yes, it is getting weirder.

-dan z-




--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
W

Wolf K

On 2/2/2013 11:59 AM, slate_leeper wrote:
[...]>
OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?
Yes. And way beyond my expertise.
 
P

Paul

slate_leeper said:
New update.

I went back to un-rename (is that a word) the files, and found that
Update DID load new copies. However it still doesn't work. Same
symptoms as before. Update did not reinstall the WpdMtp.dll, but did
reinstall the WpdMtpUS.dll.

Also, yesterday I reinstalled the AMD driver software from ASUS, which
has the drivers for audio, video, USB, USB3, and PC-BUS. Still no
change.

It doesn't work in a USB3 port either. Same symptoms.

Card reader also still doesn't work. Same symptoms.

Yes, it is getting weirder.

-dan z-
Do you have the registry key mentioned here ?

http://www.android-hilfe.de/allgeme...7-mtp-treiber-unter-windows-7-error-31-a.html

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{EEC5AD98-8080-425F-922A-DABF3DE3F69A}

"Upperfilters" = klfltdrv

I don't have one of those here. My key includes these four

(Default) Windows Portable Device
Class WPD
Icon 100
Installer32 wpd_ci.dll,WpdClassInstaller

but I don't have an Upperfilter.

Check to see if you have an upperfilter or not.

BTW - I don't read German :) You can run that
page through translate.google.com if you want
though.

Upperfilter, is a way for a driver to "shim" into the
stack. And "listen in" on a conversation. Exactly why
software would need to do that for MTP, is unclear.
As MTP has limited useful functionality (copy file from
portable device to computer or vice versa).

Paul
 
D

Deano

Silly and paranoid suggestion from an old DOS user: If it has been
established that there is a link to one or more file indicating a
connection to Windows 8. Could this just be a simple case of "planned
obsolescence" from Microsoft?? Let's watch to see if more of these
cases crop up...;-Deano
 
C

Char Jackson

New update.

I went back to un-rename (is that a word) the files, and found that
Update DID load new copies. However it still doesn't work. Same
symptoms as before. Update did not reinstall the WpdMtp.dll, but did
reinstall the WpdMtpUS.dll.

Also, yesterday I reinstalled the AMD driver software from ASUS, which
has the drivers for audio, video, USB, USB3, and PC-BUS. Still no
change.

It doesn't work in a USB3 port either. Same symptoms.

Card reader also still doesn't work. Same symptoms.

Yes, it is getting weirder.
I don't remember if you mentioned this, but have you tried connecting the
camera to another PC to make sure it still works? It would be a shame to
spend this much time 'fixing' the PC if the problem was really a camera that
had gone south.
 
R

Rob

I have run the "fix-it" routine, which ended giving the same error as
trying to reinstall the drivers.

-dan z-

Thats not the error31 fixit but the usb fixit.
 
R

Rob

On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.


By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.
I'd move them to a safe location with a name change, just in case.
"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.
The keys are in the registry, which among other things refers to
locations of drivers, etc. Win uses it to find what's needed for devices
etc to work properly. Running regedit to clean up the registry ranges
from dead easy to very scary, depending on what's installed. But you may
want to explore the registry anyhow. Use Find to locate relevant keys.
It's a "learning opportunity", as they say. ;-)
Thanks for the reply.

-dan z-
You're welcome, it's last-resort, based on your comment that the USB
ports are OK, and that the same problem occurs on different ports.

Another last resort comment: the issue could be in the camera's
firmware, and/or the flash card's OS. Try reading the card with a card
reader.

Good luck.

OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?

Just as a suggestion -

Why don't you try and reload your Motherboard drivers off the CD. or you
could see if there is any newer USB driver software on the MB site.

It would seem that its a USB port problem.

One other question, would be, are you using the front USB ports or rear?
 
S

slate_leeper

I don't remember if you mentioned this, but have you tried connecting the
camera to another PC to make sure it still works? It would be a shame to
spend this much time 'fixing' the PC if the problem was really a camera that
had gone south.

Actually, yes. I plugged the camera using the same cable into an old
XP machine, and all worked fine. First thing I thought of.



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

Silly and paranoid suggestion from an old DOS user: If it has been
established that there is a link to one or more file indicating a
connection to Windows 8. Could this just be a simple case of "planned
obsolescence" from Microsoft?? Let's watch to see if more of these
cases crop up...;-Deano
DOS? Young whippersnapper, that's new-fangled stuff. CP/M and Altair
Basic are the only things to use!


In my searches via Google for a solution, I found many references to
the exact same problem. These date back as far as 2008 and involve
both Vista and Win7. A common comment is "this has been going on for
years. Why hasn't Microsoft fixed it yet?"

My sentiments exactly!

Various solutions are suggested on these pages. For each, some people
say it fixed the problem and others say it did not. It appears that
there is possibly more than one cause for the same error results. None
of those suggested solutions have worked for me. I just hope we can
find the correct one!

-dan z-



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

On 2/2/2013 7:49 AM, slate_leeper wrote:
On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.


By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.

I'd move them to a safe location with a name change, just in case.

"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.

The keys are in the registry, which among other things refers to
locations of drivers, etc. Win uses it to find what's needed for devices
etc to work properly. Running regedit to clean up the registry ranges
from dead easy to very scary, depending on what's installed. But you may
want to explore the registry anyhow. Use Find to locate relevant keys.
It's a "learning opportunity", as they say. ;-)

Thanks for the reply.

-dan z-

You're welcome, it's last-resort, based on your comment that the USB
ports are OK, and that the same problem occurs on different ports.

Another last resort comment: the issue could be in the camera's
firmware, and/or the flash card's OS. Try reading the card with a card
reader.

Good luck.

OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?

Just as a suggestion -

Why don't you try and reload your Motherboard drivers off the CD. or you
could see if there is any newer USB driver software on the MB site.
I appreciate your help Rob.

ASUS does not provide ANY CD with the computer. (Cheap bastards. The
computer does not even have a case cooling fan). I have reinstalled
the AMD driver software I downloaded from ASUS. This includes the
audio, video, USB, USB3, RM-Bus drivers. No change in the problem

It would seem that its a USB port problem.

One other question, would be, are you using the front USB ports or rear?

The ASUS has six USB2 and two USB3 ports. Two of the USB ports have
the keyboard and track ball. One has the Cannon printer. One has the
AnFi USB sound device. I usually plug the camera into one of the two
front ports, but have also tried rear ports and a USB3 port. There has
been no change in the symptoms.

-dan z-

--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
R

Rob

On 2/2/2013 7:49 AM, slate_leeper wrote:
On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.


By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.

I'd move them to a safe location with a name change, just in case.

"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.

The keys are in the registry, which among other things refers to
locations of drivers, etc. Win uses it to find what's needed for devices
etc to work properly. Running regedit to clean up the registry ranges
from dead easy to very scary, depending on what's installed. But you may
want to explore the registry anyhow. Use Find to locate relevant keys.
It's a "learning opportunity", as they say. ;-)

Thanks for the reply.

-dan z-

You're welcome, it's last-resort, based on your comment that the USB
ports are OK, and that the same problem occurs on different ports.

Another last resort comment: the issue could be in the camera's
firmware, and/or the flash card's OS. Try reading the card with a card
reader.

Good luck.


OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?

Just as a suggestion -

Why don't you try and reload your Motherboard drivers off the CD. or you
could see if there is any newer USB driver software on the MB site.
I appreciate your help Rob.

ASUS does not provide ANY CD with the computer. (Cheap bastards. The
computer does not even have a case cooling fan). I have reinstalled
the AMD driver software I downloaded from ASUS. This includes the
audio, video, USB, USB3, RM-Bus drivers. No change in the problem

It would seem that its a USB port problem.

One other question, would be, are you using the front USB ports or rear?

The ASUS has six USB2 and two USB3 ports. Two of the USB ports have
the keyboard and track ball. One has the Cannon printer. One has the
AnFi USB sound device. I usually plug the camera into one of the two
front ports, but have also tried rear ports and a USB3 port. There has
been no change in the symptoms.

-dan z-
Not sure what you can do except use a card reader. BTW card readers
don't damage SD or CF cards. Ithink you can buy USB3

I now have 7x32Gb sd cards for my camera and change them all the time
without any detrimental effect.
 
S

slate_leeper

On 3/02/2013 3:59 AM, slate_leeper wrote:
On 2/2/2013 7:49 AM, slate_leeper wrote:
On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]
5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)
[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.


By uninstall/reinstall do you mean the problem device via Device
Manager? I have done that (repeatedly), but not with the drivers first
removed. I'll try that.

I'd move them to a safe location with a name change, just in case.

"Delete all camera related keys" I'm not quite sure what you mean
here. While I used to be an application programmer, a senior field
engineer, and a FCC licensed technician, that was a while back and I
am not very familiar with the innards of Windows.

The keys are in the registry, which among other things refers to
locations of drivers, etc. Win uses it to find what's needed for devices
etc to work properly. Running regedit to clean up the registry ranges
from dead easy to very scary, depending on what's installed. But you may
want to explore the registry anyhow. Use Find to locate relevant keys.
It's a "learning opportunity", as they say. ;-)

Thanks for the reply.

-dan z-

You're welcome, it's last-resort, based on your comment that the USB
ports are OK, and that the same problem occurs on different ports.

Another last resort comment: the issue could be in the camera's
firmware, and/or the flash card's OS. Try reading the card with a card
reader.

Good luck.


OK, here is what I did. I removed (actually renamed to .bak) all the
files that were listed as drivers in my original post EXCEPT the usb
driver, since I would be in trouble if my keyboard and track ball stop
working.

Then I brought up device manager, and selected the bad device and went
to "properties/driver."

It said "Reinstall device drivers for this device, To reinstall the
drivers, click Reinstall Drivers"

So I did that, selecting automatic search. After a prolonged period,
with lots of internet activity, the message was "best driver is
already installed."

Dang. That's the same message as before!

Is it getting weirder?





Just as a suggestion -

Why don't you try and reload your Motherboard drivers off the CD. or you
could see if there is any newer USB driver software on the MB site.
I appreciate your help Rob.

ASUS does not provide ANY CD with the computer. (Cheap bastards. The
computer does not even have a case cooling fan). I have reinstalled
the AMD driver software I downloaded from ASUS. This includes the
audio, video, USB, USB3, RM-Bus drivers. No change in the problem

It would seem that its a USB port problem.

One other question, would be, are you using the front USB ports or rear?

The ASUS has six USB2 and two USB3 ports. Two of the USB ports have
the keyboard and track ball. One has the Cannon printer. One has the
AnFi USB sound device. I usually plug the camera into one of the two
front ports, but have also tried rear ports and a USB3 port. There has
been no change in the symptoms.

-dan z-
Not sure what you can do except use a card reader. BTW card readers
don't damage SD or CF cards. Ithink you can buy USB3

I now have 7x32Gb sd cards for my camera and change them all the time
without any detrimental effect.

Since the bulit-in card reader gives the same symptoms as does the
camera, I would be surprised if an external one would work.

Since last post I have disconnected the card-reader and front USB
ports completely. No change in symptoms.

I have also checked the "UpperFIlters" registry entry suggested, again
with no positive results.

All I can say for sure is that the camera and card reader are NOT the
problem. The problem is in Microsoft's WPD drivers or associated
settings.

I have found many references to this exact same problem on the web,
dating back as far as 2008 and Vista. A very common comment is "This
has been going on for years. Why hasn't Microsoft fixed this?" Yeah.

The problem always involves WPD, but the actual hardware that reveals
it varies (cameras of various brands, ipods, etc.)

On these pages a variety of cures have been suggested. For each some
say it worked and others say it didn't. So far none have worked for
me. Apparently there are many things that can trigger the problem.

Thanks for your suggestions. I really appreciate your help.

By the way, I posted the problem on the Microsoft "hardware and
drivers" forum. It only drew one response, and my response to that one
went unanswered. Too bad MS doesn't actually have a real support
system.

-dan z-



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
S

slate_leeper

Rob,

Do you have anything in this directory or know what it used for?
E:\ProgramData\Microsoft\WPD

(Note, when I installed Win-7, it was on a second drive. Even though
that is now the primary and only drive, it still carries the "E:"
label. Yours is probably C:)

-dan z-




--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.
 
W

Wolf K

Rob,

Do you have anything in this directory or know what it used for?
E:\ProgramData\Microsoft\WPD

(Note, when I installed Win-7, it was on a second drive. Even though
that is now the primary and only drive, it still carries the "E:"
label. Yours is probably C:)

-dan z-
FWIW, on this box (W8-Pro-64) that directory is empty. I also have not
had any problems connecting the camera or card reader through any USB
port. Maybe that's a clue.

HTH
 

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