WEBCAM issue - SFC /Scannow detects corrupt files but can't fix.

MarkW91

MarkW91

MarkW91

Associate
Joined
5 Oct 2012
Posts
10
My main problem is that each time that my computer is shutdown/rebooted/woken out of sleep it fails to pick up my webcam, device manager says error code 43.

if i unplug my webcam and plug it back in it works straight away but from time to time it is reinstalling the drivers for the webcam every now and then.

i have changed the power settings for all usb ports so that the computer does not turn them off to save power, pointless since i'm using a custom built pc.

anyway i remember to run a sfc scan and it came up with that it has picked up corrupt files but it is unable to fix the issue, i have found the file that it creates but i have no idea what i'm looking for and how to downsize the list in order to find out what is wrong, and what i need to do to fix it.

Current specs in my machine are.
Windows 7 Ultimate 64bit
AMD Phenom2 x6 1100T 3.3ghz CPU - Watercooled
MSI 5850 twin frost II 1gb
Alpine 750W power supply
3TB storage
16GB DDR3 1333mhz RAM
ASUS M5A97 EVO R2.0 Motherboard

I have also tried using different ports and the issue remains and all software is up to date and all drivers have been updated.

Please help.
 
Check your Bios. If your Bios is set to PNP OS you will continue to get errors like this. Hardware PNP is taken care of by the Software Address space and not the BIOS address space once used under 16 bit and 32 bit operating systems. The bios setup for PNP OS is a legacy left over from the 8086 era and where the overhead of the Basic Input and Output system was limited to 640Kb. Extended memory was anything above this. Some Bios's still have this function enabled for shadow functions like integrated graphics. This can cause dropouts of the type you are describing because it is acting like a graphic address space.
 
I have changed the setting in my BIOS as per instructed and it has made no difference what so ever.

I should mention that the issue with the webcam did not happen before, in the past after boot it worked right away and has only been happening for the past 2 weeks. also the webcam has been changed and the issue remains the same also.

Anymore idea?
 
What it comes down to now is a timing issue. USB uses memory timing as well as io base timing. if you are overclocked that could be the issue. What happens is that if say you have it plugged into a USB 3 socket you may have all of the above because they are not truly compatible. If it is an accepted fact that usb 1.1 works in USB 2 but USB 1.1 will not really work in USB 3. USB 2 devices are evidently slower when running on USB 3. Please check your port or hub are both compatible.
 
The USBs that are being used are use 2.0, i'm aware of what devices are and are not compatible with different use ports. But as mentioned this has not been an issue before until about 2 weeks ago. And i do not use use hubs because I find them to be pointless.
 
Are you running the latest BIOS. As looking at the Asus website they released a new one on the 1st August.

I have recently upgraded the BIOS on my Asus motherboard as I was having usb issues on boot with my trackball and/or keyboard randomly not being detected and having to unplug and plug them in again to get them working.
 
Yeah i'm having that issue as well from time to time as well but after 10 seconds of being in the OS it works fine. I have updated the BIOS or at least I tried. The download for the most recent update for the bios of my motherboard is in a file format that for some reason does not load right and that I needed to download a Microsoft update to boot the file. So it might have updated, it might not have.

If you can supply me with a link of an .Exe file it would be a massive help just to make sure.
 
It does sound very much like an ASUS Quick Bios issue. Sometimes the ASUS Bios flash uttility doesn't do its job very efficiently. My advice would be to Flashback to the previous bios and then reset defaults just to test it out and then update the Bios to the newer version. I have several Asus boards. I have even got my old ASUS P5N32-E SLI MB here. The trick I found with an ASUS board a long time ago is that you only update the Bios if there is something wrong with your current configuration that means it is neccessary to update it.
Or if it ain't broke, don't fix it.
I currently use the Cheap end one with my i7 and i5 which is the ASUS P8Z77-V LX.
The only criticism I have of the EFI is that it doesn't work as intended or described. You have to use advanced settings to get the most out of it.
In my experience you have to run a Bios check against the current Bios file you installed otherwise checksums could result in a new bios chip.
 
First webcam I had was an old mikomi 1.3mpx webcam to which I replaced it with a Trust elight 1080p webcam to which is fully supported in Windows 7 and 8. I had the issue with the old one, thought it was that and since having the new one and it persists I Knew then it was not the webcams.
 
If you have a digital camera why don't you connect that up via usb as an experiment and see if the storage point exists. This is just an experiment to test via the pnp point that persistent storage works on your USB refresh rate. Otherwise you may have a duff MB. The only thing I can put it down to is power drain somewhere on the 5v line. which is either a cap or PSU problem. I would say try putting the old one back in as an experiment but it still will not solve the issue. You have to think outside the box on this one.
 
If you have a spare drive somewhere try a fresh install of Windows to see if it is an update error or an installation error. Obviously you don't have to activate it to test out your system. But something I would do to just check my device settings are correct and I haven't missed anything and any trick. I just sorted out my friend's Bios problem with EFI on a ASUS P8Z77-V Premium. It wouldn't pick up his other drives on boot. And often would not boot at all. But his board has known issues because ASUS gave that MB everything it could need. The only thing is that it cannot handle that basics.
Error code 43 is a remarkably simple error to clear by removing or uninstalling the Root hub in Device Manager and rebooting. This should find your devices and reinstall them. The only issue I have is that your problem eminates from your Hard Disk. At the start of the thread you said it happens when coming out of Hibernation. Why don't you turn off hibernation for a start because this could be the root of your issues. Hibernation uses the Hard disk to image your Windows state and when on the appropriate moment of the power up status is resumed part of the file is corrupted.
start at the root of your issue and work forwards. Remember a year or a month could be a long time but even a simple virus could have cause this. One that your system has automatically erradicated but the echoes still persist because the save state still exists on your pagefile on the Hard disk.
 
My entire system when up in smoke, i have now placed Windows 8 Pro 64bit on my machine and the issue remains on the operating system as well. Any further ideas?
 
It is obviously conflicting with some other device in the same address space as itself. If it is Error code 43 on Windows 8 then it is an IRQ conflict. Also another thing to test out: If your new Webcam has a built in Mic which could show up in a directX Audio conflict with the onboard sound processor.
 
You must log in or register to reply here.
Back
Top Bottom