(SOLVED) BSOD on installing zte data card Ac2739.

[rama]

Position as on 13.02.2015

My Toshiba Satellite A100 - PSAAKL - 00M008 runs on genuine Windows Vista Home Basic - SP2 with auto updates enabled and is up-to-date. Though the system is slow (old model), and the Bios is 2007, there has been no major problem. However, when I tried to install zte data card Ac2739, windows consistently blue screens. I've ascertained that there's no problem with the data card itself. I have done the memory test, checkdisc, and sfc /scannow, but no issues. I've tried to install it in Safe Mode, Clean Boot Mode and with Avast disabled, but no go. Whocrashed says the probable culprit is cdrom.sys, but the installed driver version (2006) is the latest one. I've  disabled the driver and tried to install the data card, but still the same result.
The USB port is ok, since I am using it to access GPRS through my phone.

I ran Driver Verfier for 48 hours continously, but no BSOD.

Position as on  09.03.2015

As a last resort, I re-installed Vista from my OEM disk - with no service packs. Still, the BSOD occurs when I try to install the modem. I think Vista is causing the BSOD by trying to install the wrong drivers. I've tried to prevent Vista from installing drivers by selecting the "do not install drivers" option from "Advanced System Settings - Hardware",but Vista still tries to install drivers, which results in an immediate BSOD. I've got the Reliance Netconnect software with drivers, but Windows is doing its own driver installation and BSODing.

There is another problem, doesn't seem to be related. After the Original 512 MB RAM failed, I've been using a 1 GB RAM in one of the slots. Now, because of the increased load, I've added another 1 GB RAM to the other slot, but both the BIOS and Windows show only 1 GB RAM. I've ascertained that both the sticks and both the slots work fine. Speccy and CPU-z also report 2GB RAM.I couldn't find any update for the bios.

I have uploaded the latest specs and mimidumps.

Any help is appreciated. Thank you.
Rama.

http://speccy.piriform.com/results/FK4TMhaINdRZasO3ZVEINUZ

[Shane]

Rather odd that the cdrom.sys is causing the crash, that is a very basic driver file, unless it is infected or not the right version of the file.

Have you ran TDSSKiller yet by any chance?

Shane

[Boggin]

When you boot up into Safe Mode you should be using the on board VGA.

In that mode go to Device Manager/Display Drivers and see if right clicking on the original graphics and selecting Disable allows you to install the new card.

It's a waste of time trying the Uninstall as Windows will probably reinstate it on the reboot.

As for the RAM - does your msconfig have a Max Memory check box - came across the same Vista problem (Google) where unchecking that box resolved so that Windows recognized both sticks.

[rama]

Thank you Shane and Boggin for your inputs. I had indeed run TDSSKiller before re-installing Vista, and it found no infection. As for as cdrom.sys is concerned, the driver is fresh from the re-install from the OEM original DVD.

I went to safe mode and disabled the display driver and inserted the modem. Still the same BSOD blaming cdrom.sys.

 msconfig does have a Max Memory check box, which was already unchecked. When I checked it, it showed 800 something and wouldn't go up by clicking the button. When I physically entered 1900, it returned to 800 something. There is no memory options in the BIOS.

Regarding BSOD, is there a way to actually stop auto-installation of drivers, and force it to install the drivers I have?

Regards,
Rama.

[Shane]

Give this a try
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

Shane

[rama]

Thank you Shane for the input. I had already seen that post, but it won't work, because Home basic editions don't have Group Policy Editor (gpedit.msc) installed. There is a patch for that, but I don't want to try it, because I don't know typing, and am not comfortable with patching. However, I will post the link here in case it benefits somebody else.

Regards,
Rama

http://www.askvg.com/how-to-enable-group-policy-editor-gpedit-msc-in-windows-7-home-premium-home-basic-and-starter-editions/

[Shane]

I have actually used that gpedit file downloaded from that site, it doesn't patch any files, it simply adds the files that are needed for gpedit

What I normally like to do is find which registry keys are set when setting something in gpedit so I can just make a reg file for it instead. When I have some free time in the next few days I could load up vista in vmware, do a reg snap shot before hand, do the gpedit and then do another reg snap shot and look for the changes and see if I can find the registry keys it changes (If any)

Shane

[rama]

Thank you Shane for the info. I guess I was taken in by the patching disclaimer at the top of the page, and didn't read the post carefully. I have now downloaded and run the file, which installed  gpedit without any problem. However, my (Vista) version doesn't have any "Device Installation" folder under Computer Configuration->Administrative Templates->System, nor any option for "Prevent Installation of Devices not described by other policy settings". The only relevant option it has is "turn off windows update device driver search prompt". I enabled this, but as it pertains to update, it seems to be no use at the present situation.

Regards,
Rama.

[HeyRoxie]

Hi gentleman.. here is a fix for you...

enter through safe mode.. ..go to the device Mgr.. and update NetWork CONTROLLER.. (it will be down) also remove Atheros driver ,,it is causing a conflict I believe with the lastest updates from OS.. IF  you have IE 9.. that is corrupt and with corrupt the shell32 and you will than learn how to takeown if you do not have a system image or start up disk (like me)   

update your display driver.. and you may have to do this a few times.. if you can not go in by safe mode.. go in safe mode with access to CMD.. .. when you get in and it looks stable run sfc /scannow for elevated cmd prompt.. it will fit the disk and you will be able to see if IE errored out ..IF all the last updates did not load.. you will need the repeat the above.. each time you get BSOD...so make a back up when you can in between each download.. and I limited my downloads to 5 each run.. it does logged the system as much//

let me know if this helps... it has for everyone I past this on to.. I have learned a lot in the last few days

[rama]

Thank you very much for the input, you certainly have the right idea. Since Windows has been reporting that the drivers are up to date, I ran a free Driver Manager called "Drive The Life" to scan the drivers. Sure enough, it pinpointed the 3 drivers you mentioned ( NIC, Atheros and Display) plus one motherboard driver as needing repair. It downloaded them and installed, but the Display driver is not digitally signed and needs restart, so I restarted and inserted the  modem - BSOD. So next time I inserted the  modem without restarting - again BSOD. After some trials, I found out that Windows reinstalls the old display driver when it reboots. Finally I just uninstalled all the 3 items in safe mode and inserted the modem without giving Windows a chance to reinstall them - still the same old BSOD blaming cdrom.sys. I don't understand how a freshly installed OS can have driver errors.

Also, please clarify whether the other people had problem installing the modem, or running it after installation.

Regarding the other points, after reinstallation of Vista, there's no IE in the laptop.

I ran sfc /scannow. Here's the info about "can not repair". I think we can safely ignore the "gpedit" entries, since they were created yesterday only. I don't understand any of the others, and somebody knowledgeable will have to interpret them.

Regards,
Rama



POQ 51 ends.
2015-03-13 16:39:13, Info                  CSI    00000132 [SR] Verify complete
2015-03-13 16:39:14, Info                  CSI    00000133 [SR] Repairing 4 components
2015-03-13 16:39:14, Info                  CSI    00000134 [SR] Beginning Verify and Repair transaction
2015-03-13 16:39:14, Info                  CSI    00000135 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.0.6000.16386_none_a5d5397a5ec02105\fde.dll do not match actual file [l:14{7}]"fde.dll" :
  Found: {l:32 b:ofJrYBMvfbcRFAtPFwvTqckgU78Xi+9tWAnhLEg79/w=} Expected: {l:32 b:CZev8RyTePmcz/iNnXxsP21L7UrUSFJLD/c3nLJjKmd=}
2015-03-13 16:39:14, Info                  CSI    00000136 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000137 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.0.6000.16386_none_dd7ed04153d3440b\fdeploy.dll do not match actual file [l:22{11}]"fdeploy.dll" :
  Found: {l:32 b:X2Mxr15BWaSKXy2mybUslwVk9Y/FqInLy5D57coBHZA=} Expected: {l:32 b:h/n4DaywC5cZowEPvzatqmZJqn3OAVxEom2aWKV56Vx=}
2015-03-13 16:39:14, Info                  CSI    00000138 [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000139 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.0.6000.16386_none_35190a8e921bbf42\gptext.dll do not match actual file [l:20{10}]"gptext.dll" :
  Found: {l:32 b:4R/wpzngnfdc0a94M7qP6Hg+i5N+LV89wlqPbSNLqTt=} Expected: {l:32 b:nHTHvUBGGBqit4oUTvrcam63/8I5zfU11jkc5Iw01Y8=}
2015-03-13 16:39:14, Info                  CSI    0000013a [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    0000013b Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.0.6000.16386_none_cbfb6a9967fc57b1\gpedit.dll do not match actual file [l:20{10}]"gpedit.dll" :
  Found: {l:32 b:kr66STTQJj/SGCfMluAmidqauu1XH+iINrNGn3DUoo7=} Expected: {l:32 b:YRuQ0/4v6elpjn/fZ1RsgTAHbfRMZUm7+4XQcKq14T6=}
2015-03-13 16:39:14, Info                  CSI    0000013c [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    0000013d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.0.6000.16386_none_35190a8e921bbf42\gptext.dll do not match actual file [l:20{10}]"gptext.dll" :
  Found: {l:32 b:4R/wpzngnfdc0a94M7qP6Hg+i5N+LV89wlqPbSNLqTt=} Expected: {l:32 b:nHTHvUBGGBqit4oUTvrcam63/8I5zfU11jkc5Iw01Y8=}
2015-03-13 16:39:14, Info                  CSI    0000013e [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    0000013f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.0.6000.16386_none_cbfb6a9967fc57b1\gpedit.dll do not match actual file [l:20{10}]"gpedit.dll" :
  Found: {l:32 b:kr66STTQJj/SGCfMluAmidqauu1XH+iINrNGn3DUoo7=} Expected: {l:32 b:YRuQ0/4v6elpjn/fZ1RsgTAHbfRMZUm7+4XQcKq14T6=}
2015-03-13 16:39:14, Info                  CSI    00000140 [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000141 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.0.6000.16386_none_dd7ed04153d3440b\fdeploy.dll do not match actual file [l:22{11}]"fdeploy.dll" :
  Found: {l:32 b:X2Mxr15BWaSKXy2mybUslwVk9Y/FqInLy5D57coBHZA=} Expected: {l:32 b:h/n4DaywC5cZowEPvzatqmZJqn3OAVxEom2aWKV56Vx=}
2015-03-13 16:39:14, Info                  CSI    00000142 [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000143 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.0.6000.16386_none_a5d5397a5ec02105\fde.dll do not match actual file [l:14{7}]"fde.dll" :
  Found: {l:32 b:ofJrYBMvfbcRFAtPFwvTqckgU78Xi+9tWAnhLEg79/w=} Expected: {l:32 b:CZev8RyTePmcz/iNnXxsP21L7UrUSFJLD/c3nLJjKmd=}
2015-03-13 16:39:14, Info                  CSI    00000144 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000145 Repair results created:
POQ 52 starts:
 
POQ 52 ends.
2015-03-13 16:39:14, Info                  CSI    00000146 [SR] Repair complete

[Boggin]

Doing an offboot sfc /scannow can work in Win 7 when the one run in Windows is unable to repair all files so give this a go.

Your install disk would need to match the current state of the installed Vista - i.e. if it has the SPs then the install disk must be SP2, otherwise you would need to reinstall from scratch, which could fix it anyway.

However, all things being equal, boot up with the install disk and navigate to where you can select Repair your Computer and then onto the Recovery Environment.

Select Command Prompt and enter bcdedit |find "osdevice"

Using whichever partition letter, enter (assuming c) sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows and see what that reports.

Just in case it isn't clear, that's a Pipe symbol before find and there's a space before each forward slash.

Enter exit to close the command window, remove the install disk and Restart.

You could still get the gpedit errors as they aren't native to Vista, so perhaps using a restore point prior to adding those may help - unless it was adding gpedit that has caused the other errors.

To eliminate that, use your restore points to prior adding gpedit and run the sfc /scannow again or a chkdsk /f.

[rama]

Even once again reinstalling Vista and immediately trying to install the modem in safe mode resulted in the same old BSOD. It looked more and more likely that Vista is messing up things. Having struggled with this for a month, I decided enough is enough, and installed Windows 7, which had no problem in installing the modem even in regular mode.

I'd like to record my heartfelt gratitude to Shane, Boggin and Heyroxie for taking the time and effort to help me out.

I had posted this problem at http://www.vistax64.com/crashes-debugging/303557-bsod-installing-zte-data-card-ac2739.html some weeks back. The thread has had more than 1700 views, whish shows the keen interest this problem has created. I'll post there and give a link to this thread, so that more people come to know about this place and utilize it.

Regarding memory non-detection problem, in the absence of other explanations, we can attribute it to the very old BIOS, and leave it at that.

Thank you once again, one and all.

Regards, 
Rama.

[Boggin]

I think that was a good decision 

[rama]

Thank you Boggin.

I posted at the other forum immediately after posting here, but that post has been removed, and I didn't get any messages. Being a Vista forum, may be they were reluctant to let it be known how Vista failed, and there was no help.

I noticed a curious thing about the memory . In Vista, like I said, the Max Memory box won't go above  800 something, and in Windows 7 it won't go above 1024. May be somebody has an insight into this.

Regards,
Rama.

[Boggin]

I don't have a max memory option in my Win 7 msconfig and thought from the Google I'd found, that this was just a Vista thing.

Some forums won't allow references to other forums threads and is probably why your post was removed - have you checked their forum's T&Cs ?

[rama]

During the past month, I have come to see the seamy side Of Windows. Now I have the same problems as at http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/why-does-windows-7-think-my-usb-modem-is-a-cd-rom/1c5be829-0e97-4900-a80c-344dab4f58ff, and have to shut down the computer if I want to safely remove the modem. I've decided to let it be and ignore the "solutions" suggested by MS, lest Windows messes up and renders the modem inoperable like it did in Vista.

Regarding the rules at the Vista forum, this is what they say:

This site includes links to other sites on the world wide web. We are not responsible for such sites and cannot vouch for the suitability or accuracy of their content. You link to them at your own risk.

though they also say

The owners of [ARG:2 UNDEFINED] reserve the right to remove, edit, move or close any thread for any reason.

Regards,
Rama.

[Boggin]

I should have Googled what that card was as I was working on the assumption you were trying to install another video card. 

Have you tried uninstalling the DVD drive then rebooting to see if you still get the same error ?

As the problem has started again in Win 7 have you contacted ZTE as it may not be Windows which is the cause.

If others have reported this problem to them they may have a solution such as going to your computer support site and downloading the chipset drivers ?

http://www.zte.co.nz/main/data.htm

Edited for details change.

[rama]

Uninstalling the DVD drive then rebooting has made no difference. http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/why-does-windows-7-think-my-usb-modem-is-a-cd-rom/1c5be829-0e97-4900-a80c-344dab4f58ff clearly says that the issue was there in two different makes. Also, the zte modem is a self-contained unit, and is also working perfectly. I'm sure Windows is messing up with the drivers, because when I first reinstalled Vista and installed Sony Ericsson PC companion, Vista tried to install drivers and BSODed.  When I tried again, Sony Ericsson PC companion said "don't let windows install drivers", and somehow managed to install its own drivers. After installation it worked perfectly, but Vista showed an error in Device Manager that drivers are not properly installed.

As far as chipset drivers are concerned, there is no support for this model in Toshiba site, not even in the legacy category.

Regards,
Rama.

[Boggin]

If your Toshiba is using AMD as mine is, the AMD video drivers are the chipset drivers.

AMD has an auto detect and install if that is the case. http://support.amd.com/en-us/download/auto-detect-tool

The AMD's video drivers Southbridge looks after the USB Controllers and if these apply to you, use the Custom install and select all as sometimes it just wants to reinstall the CCC.

I'm an update behind on the auto detect and install because their latest drivers put a red hue on mine so I had to go into Device manager and roll back the driver, but it may not be the same for you.

If your Display drivers are Radeon HD then they are AMD.

[rama]

Thank you very much Boggin for your  untiring help. My video card is ATI RADEON XPRESS 200M Series. Before reinstalling Vista, I had indeed tried the AMD tool as well as the Intel tool, but they did not find any drivers to install.

I forgot to tell you yesterday that the Maximum memory box is under the advanced boot options (msconfig - system cofiguration - Boot - Advanced options). It seems to indicate more and more towards  the Bios, considering the fact that the system originally came with a 512 MB RAM   (and 80 GB HDD).

I found out something very important today. When the modem installed and worked in Windows 7, my relief was so great that I failed to check what driver Windows has used. I checked now and found it that it is none other than the villain of the past month - cdrom.sys. Now we can understand what has been happening. When I inserted it in Vista, Widows tried to install it with cdrom.sys, which created a conflict, and Vista crashed, correctly blaming cdrom.sys. Windows 7 seems to be more tolerant and is working, but taking it as a cdrom, which of course can not be ejected, but can be uninstalled from the device manager.

Regards,
Rama.                                                                                                                                                               .                                               

[Boggin]

Well that's something else that's came to light since installing Win 7.

I'd forgotten about that bit in msconfig.

This laptop is Dual Core and initially I'd wondered why it only showed 1 in the Core box, but realised that it would only use one core at Boot and my Max Memory is also unchecked.

[rama]

Finally it seems that I have found workarounds for the two problems.

First, the ejecting problem. According to http://www.windows7library.com/blog/performance/usb-quick-removal-option/, "Removing USB flash memory devices from your computer does not require you to use the Safely Remove Hardware and Eject Media function if the removal policy is set to default.". I first came to know of this from the comments of "Zibrz" at http://www.pcworld.com/article/2040932/how-to-safely-remove-a-usb-drive-even-when-windows-says-it-isnt-safe-to-do-so.html , so all thanks to him. I've also considered the warning at http://www.howtogeek.com/118546/htg-explains-do-you-really-need-to-safely-remove-usb-sticks/ , but I still think it is safe because of the following reasons.

1. I will be pulling out the modem only after disconnecting from the internet and closing the modem's interface.
2. There is 0 bytes free of 46.4 MB in the modem, so there is no possibility of Windows or other programs writing to it.

If there is any error in my reasoning, or if anyone has some relevant info that I'm unaware of, please post.

Second, the autoplay problem . I have gone to Control panel - Hardware and Sound - Autoplay and changed the option to "take no action" for the very first item in the list- Audio CD. Now when I insert the modem, the  autoplay menu doesn't open, but the modem's interface opens and gets ready to connect to the internet. I have confirmed that this change only has made the difference, because I haven't made this change in another User Account, and there Autoplay menu opens when the modem is inserted. Don't ask me what's the connection between playing an audio cd and opening a modem's interface, you'll have to  ask MS that!

Regards,
Rama.   

[Boggin]

Although my laptop is default to remove safely, I still use the safe to eject.

Not sure if you'll be able to do anything about this, but go Start - type msinfo32 - press enter - expand Hardware Resources - Conflicts/Sharing and then in IRQs.

Then expand Components - Problem Devices to see if anything is listed in there.

I agree, plugging in a networking USB shouldn't bring up Autoplay.

According to the specs for your laptop, it has a ATI Radeon HD5870 chip fitted, but to confirm, go Start - type dxdiag - press enter and see what it has under the Display tab.

AMD's video drivers are also the Chipset drivers so it could be worth going to Toshiba's driver support site for your location or use AMD's auto detect and see what it has for your graphics. http://support.amd.com/en-us/download/auto-detect-tool

I always use the Custom install and select all, but the latest Win 7 drivers for my HD6310 puts a red hue on my screen so I had to roll back that driver in Device Manager, but it may be different for you.

I would also check Toshiba's support site for a BIOS update - the System tab in dxdiag will show which BIOS version you have installed.

[rama]

I too would prefer to unplug the modem after shutting down the laptop most of the time, but I think there is no harm in deviating in special circumstances.

No "Problem Devices" have been listed under System info.

Directx,  as Speccy did, mentions ATI RADEON XPRESS 200M Series. The AMD tool says "We are unable to find a driver for your system". However, I don't think there is a problem with drivers, except this modem case. Earlier, two devices were marked with driver errors in device manager, but Drive the Life has taken care of that. The Bios is Phoenix 5.40  but unfortunately there is no update available in their or Toshiba's  site.

Regards,
Rama.   

[Boggin]

What does dxdaig under the System tab give for your Processor ?

When you are using an AMD Processor, the video drivers are the chipset drivers and the Southbridge aspect looks after the USB Controllers.

My thinking was if something had gotten corrupted with those, reinstalling may straighten them out.

You could check to see if Device Manager/Action/Add legacy hardware has any AMD video/chipset drivers to suit, but under Display it only has chipset  drivers for Intel in mine.