Blue screen and hardware/driver issues
Posted: Sun Jul 10, 2011 5:46 pm
Before installing Service Pack 2 for Vista 32 bit, I had a couple of blue screens reporting a hardware malfunction with the result that the system was halted.
I took it into my computer repair and had them run a complete diagnostic, which showed nothing malfunctioning. I then successfully updated to Service Pack 2. After that I had the same blue screen on a number of occasions. I ran a Microsoft automatic fix-it tool which resulted in the following message:
Microsoft ISATAP Adapter #8 has a driver problem.
Biometric Coprocessor doesn't have a driver
Sierra Wireless MC5720 Modem doesn't have a driver
I have never used the fingerprint device, nor the Sierra Wireless Modem. Apparently I had also never configured Windows update to look for new drivers. I enabled it, restarted, and Update attempted to find the Biometric Coprocessor driver, and the Sierra Wireless Modem driver. It was unable to do so, and unfortunately as I bought my T60P on craigslist I was not able to get the original installation disks (although the T60P itself was flawless). The ThinkVantage toolbox pointed to the necessity for the two drivers, but did not link me to any downloads.
When I went to Lenovo I was unable to find the biometric coprocessor driver. All I was able to find where these three patches:
Registry patch to change IDLE IRP timing by Fingerprint reader driver for Windows Vista (32-bit, 64-bit) - ThinkPad
[+] Click for files
Registry patch to change IDLE IRP timing by Fingerprint reader driver for Windows Vista (32-bit, 64-bit) - ThinkPad
[+] Click for files
Registry patch to change IDLE IRP timing by Fingerprint reader driver for Windows Vista (32-bit, 64-bit) - ThinkPad
When I tried to download the Sierra Wireless Modem I was presented with a bewildering array of drivers, and was a bit nervous about selecting one that may be inappropriate. My device is the 2623 DDU.
Is it possible that with the recent Windows Updates the system became unstable without these drivers? Also I cannot tell whether Windows update fixed Microsoft ISATAP Adapter #8.
Just anecdotally, it may be that playing Far Cry (never a problem in the past) preceded a few of these blue screens. Naturally I thought of the GPU, but the computer techs ran a complete diagnostic. Also GPU reports as functioning normally in device manager.
Any help would be appreciated.
I took it into my computer repair and had them run a complete diagnostic, which showed nothing malfunctioning. I then successfully updated to Service Pack 2. After that I had the same blue screen on a number of occasions. I ran a Microsoft automatic fix-it tool which resulted in the following message:
Microsoft ISATAP Adapter #8 has a driver problem.
Biometric Coprocessor doesn't have a driver
Sierra Wireless MC5720 Modem doesn't have a driver
I have never used the fingerprint device, nor the Sierra Wireless Modem. Apparently I had also never configured Windows update to look for new drivers. I enabled it, restarted, and Update attempted to find the Biometric Coprocessor driver, and the Sierra Wireless Modem driver. It was unable to do so, and unfortunately as I bought my T60P on craigslist I was not able to get the original installation disks (although the T60P itself was flawless). The ThinkVantage toolbox pointed to the necessity for the two drivers, but did not link me to any downloads.
When I went to Lenovo I was unable to find the biometric coprocessor driver. All I was able to find where these three patches:
Registry patch to change IDLE IRP timing by Fingerprint reader driver for Windows Vista (32-bit, 64-bit) - ThinkPad
[+] Click for files
Registry patch to change IDLE IRP timing by Fingerprint reader driver for Windows Vista (32-bit, 64-bit) - ThinkPad
[+] Click for files
Registry patch to change IDLE IRP timing by Fingerprint reader driver for Windows Vista (32-bit, 64-bit) - ThinkPad
When I tried to download the Sierra Wireless Modem I was presented with a bewildering array of drivers, and was a bit nervous about selecting one that may be inappropriate. My device is the 2623 DDU.
Is it possible that with the recent Windows Updates the system became unstable without these drivers? Also I cannot tell whether Windows update fixed Microsoft ISATAP Adapter #8.
Just anecdotally, it may be that playing Far Cry (never a problem in the past) preceded a few of these blue screens. Naturally I thought of the GPU, but the computer techs ran a complete diagnostic. Also GPU reports as functioning normally in device manager.
Any help would be appreciated.