BSOD started a few months ago on old computer

[svLew]

I installed Win7 about 1 year ago as an upgrade to XP. I had no problems until a few months ago - now I am getting fairly frequent BSOD. There have been few significant HW or SW upgrades recently, other than the usual MS distributions.

From looking as some of the debug reports, it appears there may be a problem with the USB support. The computer does have a lot of USB hubs and ports, but no recent additions.

Hopefully the attached files will help. The dmp file is from the BSOD today and the driverview file lists all non-MS drivers.

Thanks for any help

 

[Arc]

Upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

We need to see this file for some more info about the issue.

_________________________________________________

BugCheck FE, {5, 869d40e0, 10024396, 875071ac}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+45 )

Followup: MachineOwner
---------

 

[svLew]

Updates

Hi Arc,

I thought I had already done the requested submission with the driverview.txt file.

But it is all moot anyway. The next day, the computer wouldn't boot - at all. I didn't even get any BIOS execution. I guess you have to expect that with an 8 year old system.

So now I am building another computer.

Thanks for looking into the problem. I'm sure I will need assistance - hopefully with less serious issues.

Lew

 

[Arc]

I asked for the file because what you provided is just a copy-paste, which is difficult to read. Anyway, it however serves the purpose.

Concentrate on this driver:

ser2pl.sys    0x95681000    0x956AA000    0x00029000    1    132    System Driver    USB-to-Serial Cable Driver    [B]3.4.67.325[/B]    Prolific Technology Inc.    Prolific USB-to-Serial Bridge Cable    9/3/2014 6:49:36 AM    9/3/2014 6:49:36 AM    C:\Windows\system32\DRIVERS\ser2pl.sys    A    Ser2plx86    Prolific Serial port WDF driver

It is the only one that falls within the scope of the issue. But that is the latest one as per Products.

Remove this device form the computer. See how it goes. Let us know.

There are some other unwanted things there that may cause various issues. The ATK0110 ACPI Utility. It should not be installed in a computer at the first place.

If Removing the Prolific's USB-to-Serial Bridge Cable does not help, then what you will need is a clean reinstall, but before doing that consult with us. We will guide you how to do it avoiding things like ATK0110 ACPI Utility.

The age of the computer is not a very serious matter, if it is not overheating and the hardware are not failing.