Toshiba driver download error occurred in system module (-135)

Trying what you told me now. Here is the link to dump files Is that dump file from when verifier was enabled already! OK ran Windows Mem diag and it found no errors. Ran the verifier.. It started normally and did not come up with any errors. Just restarted again and right when computer was going to shutdown to reboot I got this BSOD message:. Ran verifier. When I shutdown and restarted this is the error I received.

Also, I updated the dump files on skydrive. Perhaps check for an update to that driver as well. Proposed as answer by No. It is still a mystery and puzzling to me, why the WinXP operating system would no longer recognize the Toshiba internal module, after all Bluetooth software was uninstalled.

The Toshiba Stack Manager software was not installed until about one year after this machine was placed in service. I did not have any Bluetooth devices during that time. When I would click on the Bluetooth icon at the Windows Taskbar, it would return a message that Bluetooth was not yet configured and asked if I wanted to install the device.

When I got my first Bluetooth device in February of I then clicked on the Bluetooth icon and this time answered "yes". The Toshiba Stack Software was then installed successfully, from the software already on the hard drive from the Dell factory image load. It was not until I removed that software, for reasons stated in previous thread, when the internal Toshiba module nor the Windows Stack Manager install, because Windows XP no longer detected the Toshiba module.

My concern about doing a Recovery and Restore from the CD was whether or not the pre-loaded Toshiba Stack software would reappear as it did with the original factory image load. I have found in the past that the Recovery CD's only reinstall the Windows Operating System and is not the same as the original factory image load. I would then have to update all the drivers from another CD or the Dell support web site manually.

I was not optimistic that the internal Toshiba module or Stack Software would have worked properly and still have no Bluetooth. Then what would be Dell's excuse, after I blew away all my previous hard work only to start over reinstalling a ton of software as previously installed. I guess I will never know, unless I have a catastrophic failure and have to reinstall the operating system.

I have read many threads by others that had similar if not the exact same experience as I. As mentioned earlier, my biggest disappointment with Dell is that they have not spent the time and resources to find out why this is happening and come out with a patch to correct the registry or missing files that would correct this problem.

On another note, just curious if you are a corporate pilot, retired pilot, etc. I am a Corporate Pilot, same corporation for past 33 years. I have long held an Airline Transport Certificate License , but had I gone for the Airlines, regulations that they are now trying to change would have forced my retirement years ago, I love my 'job' and have no desire to retire. The symptoms you described looked like your firmware flash's USB Utility was still installed and that will prevent Windows or Toshiba Stack from seeing that you have the module.

There are stories on the Network Board about even more serious Bluetooth issues related to Vista and utilities provided to "awaken" your module if had been off on an install.

I fixed my problem with the Bluetooth Stack for windows by Toshiba. I then chose by service tag to look for updates. Under the Network heading there is a recommended download for the Wireless module bluetooth. I saved this to my desktop and and the download automatically uninstalled my old software and I rebooted and double clicked on the icon the update was saved to on my desktop and it loaded the new software and I needed to reboot one more time.

Now everything works fine. Browse Community. Laptops General - Read Only. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Click here to Register a free account now! Please log in to reply. Posted 04 November - AM Hello I have trouble with my new notebook toshiba ZC.

Sometimes after few hour of work, sometime after few seconds I thing that the problem with drivers for GPU is there, but i am not really sure The sysnativefile together with perfmon are attached. BR Martin Attached Files perfmon. Posted 06 November - AM This is very similar to another topic posted here.

The analysis of the memory dumps shows the same thing. Please uninstall Acronis and see if that stops the problem.

If it does, then try a fresh copy of the program from the Acronis website. Please un-install the program, then use the following free tool to ensure that the troublesome sptd.

Don't worry about it, just let us know in your post. Finally, please note the drivers below that date from before when W10 came out. My browser caused a flood of traffic, sio my IP address was banned.

Hope to fix it soon. Will get back to posting as soon as Im able. To view the details that included in the CBS. Log file, you can copy the information to the Sfcdetails. To do this, follow these steps:. Note The Sfcdetails. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.

How to manually replace a corrupted system file with a known good copy of the file. After you determine which system file was corrupted and could not be repaired through the detail information in the Sfcdetails. To do this, follow these steps: Note You may be able to get a known good copy of the system file from another computer that is running the same version of Windows with your computer.

You may perform a System File Checker process on that computer to make sure the system file that you intend to copy is a good copy.

Take administrative ownership of the corrupted system file. To do this, at an elevated command prompt, copy and then paste or type the following command, and then press ENTER:. Grant administrators full access to the corrupted system file. Replace the corrupted system file with a known good copy of the file.