Long Boot Time and BSOD from Non-Existent Device

[saroman]

I have an issue with my wife's HP Pavilion Slimline s3330f computer running Windows 7 Home Premium 32-bit.

Recently, the boot times have been in excess of five minutes and on shutdown there is an occasional and seemingly random BSOD. The BSOD error message includes a reference to xcfev.sys - Address 8F1510A0 base at 8F150000; DateStamp 48Ce158e. This is preceded in the error message by STOP: 0x0000007E (0xC0000005, 0x8F1510A0, 0x8B276BCC, 0x8B276780). The xcfev.sys file is 593 KB in size and resides in:

C:\Windows\System32\DriverStore\FileRepository\xcbdav.inf_x86_neutral_8e8664e62708b91f , and in:

C:\WINDOWS\winsxs\x86_xcbdav.inf_31bf3856ad364e35_6.1.7600.16385_none_23239678b7db5032\.

Apparently xcfev.sys is a ViXS XCode AVStream Driver Front-End Library sold by ViXS Systems Inc.

In addition, under Sound, video and game controllers in Device Manager there is a listing for VIXS Pure TV-U 48A3, which I believe is a TV tuner and which is indicated as working properly.

However, there is no TV tuner on the system, nor has there ever been, and I have never seen the device previously in Device Manager.

I suspect the long boot time may be the result of the system looking for a device that isn't there and the BSOD may be the result of the system trying to unload the same.

Thanks in advance for any help you can provide to eliminate this problem.

 

[maxseven]

You could make a Restore Point and then un-install all greyed-out devices. You can use Device Manager to do this:

Remove Old Drivers After Upgrading to New Hardware - How-To Geek

or there's a program called Ghostbuster that can do it. This link talks of both methods:

Remove old, unused, hidden device drivers in Windows with GhostBuster | The Windows Club

I've never used Ghostbuster but am going to take a look at it.

EDIT: After looking at Ghostbuster I'm not sure at all about it--it seems it might be an "all or nothing" hidden device remover, and I prefer to uninstall in a more orderly/controlled manner. So, "use at your own risk".

 

[A Guy]

That would indeed seem to be the culprit, see this thread:

http://www.sevenforums.com/crashes-debugging/31843-system-hangs-then-bsods-when-shut-down.html

A Guy