Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD: BUGCODE_USB_DRIVER


  • Please log in to reply
8 replies to this topic

#1 GaryG45

GaryG45

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Vernon Hills, IL
  • Local time:09:26 AM

Posted 24 May 2015 - 09:35 AM

Hi,

I've had this error twice in the last 6 weeks.  Yesterday it occurred while running dBpoweramp Music Converter to convert some audio files.  The input was from a folder on a USB external drive and the output was going to another folder on the same drive.  The first time it occurred I was backing up a folder on a USB external drive to another USB external drive.  I have a TASCAM Audio Interface USB connected to the laptop, and I believe it caused other BSODs due to a tscusb2.exe many months ago.  I wanted to make you aware of the TASCAM device in case it doesn't show up in any of the reports I've run.

 

I'm running Windows 7 Sp1 64-bit mode on a Toshiba laptop Satellite A505-S6980 Part No PSAT0U-00M001  with 4GB of RAM.  The OS has not been changed or reinstalled, and was already installed when I bought the laptop at Best Buy.  The CPU is a 2.2GHz Intel Core 2 Duo T6600, and the video card is a Mobile Intel 4 Series Express Chipset Family.  I think the laptop is about 5 1/2 years old.  Attached are the two zip files.

 

Gary

Attached File  SysnativeFileCollectionApp.zip   1.47MB   4 downloadsAttached File  PerfmonReport01.zip   170.16KB   1 downloads

 

 



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:26 AM

Posted 24 May 2015 - 10:52 AM

First, just FYI, USB audio is known to have some BSOD problems in Windows.  It's essential that you visit the manufacturer's website and obtain the newest drivers for your device.

 

Your BIOS dates from 2009.  If able to update it from within Windows, please do so.  If it asks to boot from a disk to update it, please skip it for now.

 

This device is disabled in Device Manager.  Is this deliberate?  If so, why?

 

Microsoft Virtual WiFi Miniport Adapter    {5D624F94-8850-40C3-A3FA-A4FD2080BAF3}\VWIFIMP\5&1B7D742E&0&01    This device is disabled.

 

I only ran the last 3 memory dumps.  I got a good look at all of the in the WER section of MSINFO32 - most were caused by tscusb2a (a driver for your ASCAM US-144 mk2 device)

The last 3 memory dumps also show driver problems with your ASCAM US-144 mk2 device.

Please:

- download a fresh copy of the latest, Win7 compatible driver for this device from the manufacturer's website

- uninstall the current driver from your system.

- install the freshly downloaded driver

- monitor for further BSOD's

 

Please uninstall the Western Digital software from the system.  The wdcsam64.sys driver is known to cause BSOD's in some Windows systems.

 

 

Here's the extracted information from the memory dumps

Debug session time: Sat May 23 16:35:36.977 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\052315-67595-01.dmp]
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
System Uptime: 3 days 19:09:08.991
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for tascusb2.sys
*** ERROR: Module load completed but symbols could not be loaded for tascusb2.sys
Probably caused by : tascusb2.sys ( tascusb2+263d1 )
BugCheck FE, {4, fffffa8007f2ac60, fffffa8007f2a7f0, fffffa80046f7000}
BugCheck Info: BUGCODE_USB_DRIVER (fe)
Bugcheck code 000000fE
Arguments:
Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp
    that is already pending in the USB bus driver.
Arg2: fffffa8007f2ac60, Address of IRP
Arg3: fffffa8007f2a7f0, Address of URB
Arg4: fffffa80046f7000
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_IRP_DOUBLE_SUBMIT_tascusb2+263d1
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = 1.60
BiosReleaseDate = 09/03/2009
SystemManufacturer = TOSHIBA
SystemProductName = Satellite A505
BaseBoardProduct = Portable PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Apr 16 08:20:15.034 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\041615-61121-01.dmp]
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
System Uptime: 0 days 15:04:06.767
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for tascusb2.sys
*** ERROR: Module load completed but symbols could not be loaded for tascusb2.sys
Probably caused by : tascusb2.sys ( tascusb2+263d1 )
BugCheck FE, {4, fffffa8007566c60, fffffa80076da010, fffffa8004a7a000}
BugCheck Info: BUGCODE_USB_DRIVER (fe)
Bugcheck code 000000fE
Arguments:
Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp
    that is already pending in the USB bus driver.
Arg2: fffffa8007566c60, Address of IRP
Arg3: fffffa80076da010, Address of URB
Arg4: fffffa8004a7a000
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_IRP_DOUBLE_SUBMIT_tascusb2+263d1
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = 1.60
BiosReleaseDate = 09/03/2009
SystemManufacturer = TOSHIBA
SystemProductName = Satellite A505
BaseBoardProduct = Portable PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Apr  1 09:58:35.483 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\040115-71604-01.dmp]
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
System Uptime: 3 days 14:53:00.250
*** WARNING: Unable to verify timestamp for tscusb2a.sys
*** ERROR: Module load completed but symbols could not be loaded for tscusb2a.sys
Probably caused by : tscusb2a.sys ( tscusb2a+9a98 )
BugCheck 50, {fffffa8005a04000, 0, fffff8800ae3aa98, 0}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments:
Arg1: fffffa8005a04000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800ae3aa98, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_tscusb2a+9a98
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = 1.60
BiosReleaseDate = 09/03/2009
SystemManufacturer = TOSHIBA
SystemProductName = Satellite A505
BaseBoardProduct = Portable PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

Here's the list of 3rd party driver present in the memory dumps:

BHDrvx64.sys                Tue Apr 28 21:53:40 2015 (554039A4)
BHDrvx64.sys                Sat Apr  4 00:27:40 2015 (551F683C)
BHDrvx64.sys                Thu Jan 22 19:46:20 2015 (54C199DC)
ENG64.SYS                   Sat Nov 15 04:15:33 2014 (546719B5)
EX64.SYS                    Sat Nov 15 04:14:03 2014 (5467195B)
EraserUtilRebootDrv.sys     Tue Nov 25 15:15:44 2014 (5474E370)
FwLnk.sys                   Mon Jul  6 20:51:41 2009 (4A529C1D)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
IDSvia64.sys                Tue Mar 17 19:43:19 2015 (5508BC17)
IntcHdmi.sys                Fri Jul 10 09:45:10 2009 (4A5745E6)
Ironx64.SYS                 Tue May 20 18:27:42 2014 (537BD6DE)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
RTKVHD64.sys                Tue Jul 28 09:00:05 2009 (4A6EF655)
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
SRTSP64.SYS                 Wed Aug 20 16:56:53 2014 (53F50B95)
SRTSPX64.SYS                Fri Jun 13 13:27:22 2014 (539B347A)
SYMDS64.SYS                 Tue Jul 30 19:29:08 2013 (51F84C44)
SYMEFA64.SYS                Thu Feb 27 18:32:07 2014 (530FCAF7)
SYMEVENT64x86.SYS           Fri Jul 26 22:26:58 2013 (51F32FF2)
SYMNETS.SYS                 Thu Feb 13 06:25:14 2014 (52FCAB9A)
SynTP.sys                   Mon Jul 20 20:07:29 2009 (4A6506C1)
TVALZFL.sys                 Fri Jun 19 06:05:44 2009 (4A3B62F8)
TVALZ_O.SYS                 Mon Jul 13 22:19:26 2009 (4A5BEB2E)
Thpevm.SYS                  Mon Jun 29 04:15:37 2009 (4A487829)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ccSetx64.sys                Mon Sep 23 23:58:04 2013 (52410DCC)
ctxusbm.sys                 Mon Sep  7 14:09:28 2009 (4AA54C58)
eeCtrl64.sys                Tue Nov 25 15:15:44 2014 (5474E370)
fltsrv.sys                  Fri Mar  1 08:53:39 2013 (5130B2E3)
iaStor.sys                  Fri Aug  7 08:23:37 2009 (4A7C1CC9)
igdkmd64.sys                Thu Aug 27 11:07:00 2009 (4A96A114)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
pgeffect.sys                Mon Jun 22 05:00:11 2009 (4A3F481B)
rimspe64.sys                Wed Jul  1 19:54:49 2009 (4A4BF749)
risdpe64.sys                Tue Jul 28 05:24:10 2009 (4A6EC3BA)
rixdpe64.sys                Sat Jul  4 06:27:00 2009 (4A4F2E74)
rtl8192se.sys               Mon Jun 20 04:34:18 2011 (4DFF060A)
snapman.sys                 Wed Jan 16 08:44:06 2013 (50F6AEA6)
tascusb2.sys                Thu Apr 28 15:10:00 2011 (4DB9BB88)
tdcmdpst.sys                Thu Jul 30 04:39:35 2009 (4A715C47)
thpdrv.sys                  Sun Jun 28 22:02:56 2009 (4A4820D0)
tib.sys                     Wed Mar 20 05:00:38 2013 (51497AB6)
tib_mounter.sys             Thu Dec 27 08:25:05 2012 (50DC4C31)
tos_sps64.sys               Wed Jun 24 01:31:09 2009 (4A41BA1D)
tscusb2a.sys                Thu Apr 28 15:10:01 2011 (4DB9BB89)
tscusb2m.sys                Thu Apr 28 15:10:00 2011 (4DB9BB88)
vididr.sys                  Thu Feb 14 01:47:31 2013 (511C8883)
vidsflt.sys                 Thu Feb 14 02:04:41 2013 (511C8C89)
wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)

Here's a list of links to information about the above drivers - in case you need to locate replacement drivers:

http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
http://www.carrona.org/drivers/driver.php?id=EX64.SYS
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=FwLnk.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=IntcHdmi.sys
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMDS64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEFA64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=TVALZFL.sys
http://www.carrona.org/drivers/driver.php?id=TVALZ_O.SYS
http://www.carrona.org/drivers/driver.php?id=Thpevm.SYS
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=fltsrv.sys
http://www.carrona.org/drivers/driver.php?id=iaStor.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=pgeffect.sys
http://www.carrona.org/drivers/driver.php?id=rimspe64.sys
http://www.carrona.org/drivers/driver.php?id=risdpe64.sys
http://www.carrona.org/drivers/driver.php?id=rixdpe64.sys
http://www.carrona.org/drivers/driver.php?id=rtl8192se.sys
http://www.carrona.org/drivers/driver.php?id=snapman.sys
tascusb2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=tdcmdpst.sys
http://www.carrona.org/drivers/driver.php?id=thpdrv.sys
http://www.carrona.org/drivers/driver.php?id=tib.sys
http://www.carrona.org/drivers/driver.php?id=tib_mounter.sys
http://www.carrona.org/drivers/driver.php?id=tos_sps64.sys
tscusb2a.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tscusb2m.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=vididr.sys
http://www.carrona.org/drivers/driver.php?id=vidsflt.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
 


Edited by usasma, 24 May 2015 - 10:52 AM.

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.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 GaryG45

GaryG45
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Vernon Hills, IL
  • Local time:09:26 AM

Posted 25 May 2015 - 02:37 PM

John,

Thanks for your quick reply.  It is disheartening to hear that USB Audio on Windows can cause BSOD.  I'm converting approx. 550 albums to digital and have converted about 210 so far.  The problem always occurs when a digital coax from the digital output of the TASCAM US-144 MKII is connected to a digital input on my receiver.  I only make that connection when playing back recorded music on my laptop in order to do cleanup clicks and other noise.  Maybe Windows has a problem with S/PDIF.

 

I investigated updating the BIOS some time ago, but I didn't do it because it seemed risky.  I'll reinvestigate and reply if I have any questions.

 

I found a newer version of the TASCAM driver, so I uninstalled the old one and installed this one.  Unfortunately it appears that it doesn't have some audio options I have been using.  I'll try to get an answer from TASCAM for that issue.

 

I uninstalled the Western Digital software.

 

After I check into the BIOS and figure out the audio options issue, I'll start converting albums and monitor for BSOD.  Thanks for all of your help.

 

Gary



#4 GaryG45

GaryG45
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Vernon Hills, IL
  • Local time:09:26 AM

Posted 25 May 2015 - 02:56 PM

I forgot to address one item.  The Microsoft Virtual Wi-Fi Miniport Adapter being disabled.  It is something I didn't do.  Should it be enabled?  I see that I can enable it from Device Manager.

 

Gary



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:26 AM

Posted 26 May 2015 - 06:04 AM

The BSOD's with USB audio aren't a regular problem - they just appear more often in the BSOD forums than a lot of other problems.

The point here is that BSOD's are actually fairly rare - and most people don't ever experience them on a regular basis.

 

There's a range of BSOD's - from the very simple to the very complex.  The simple one's are easy to fix, where as the more complicated can take quite a while to fix.

 

Just FYI - here's how I do BSOD analysis':
- first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
- then I rule out hardware (less than 10% of BSOD's are due to this)
- then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).

 

I may not follow the above list exactly.  For example, if it looks like you're havinging issues with Windows Update or if it looks like you're missing updates - I'll ask that you update Windows Updates as the very first thing.  But each thing that we do helps to narrow down where the problem lies.

 

First and foremost.  You've replaced the driver that was blamed in the memory dumps.  Now is the time to see if that fixed things.  So I wouldn't do anything further to the system until you see if that has worked.

 

A BIOS update from within Windows isn't as risky as one that has you boot from a disk to update.

The reason here is that the software in Windows can check for the suitability of the BIOS update for your system - while the bootable disk can't.

I suggest updating the BIOS from within Windows routinely - and rarely suggest that anyone do it from a bootable disk.

 

Are you experiencing any wifi problems?  Let's leave the disabled wifi device alone for now.  It may be necessary to enable it later on, but for now we're busy trying to fix the audio issues.

Good luck.

 


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.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 GaryG45

GaryG45
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Vernon Hills, IL
  • Local time:09:26 AM

Posted 26 May 2015 - 10:23 AM

John,

Thanks for the BSOD analysis info.  I used to do problem determination/debugging for mainframe OS and application programs and had specific things that I would look for, depending on the problem type.

 

I've contacted TASCAM support because the new driver doesn't have an option that I was using with the old driver.  Because the US-144 MKII has been replaced by a different device I don't know what kind of response I'll get from TASCAM, if any.  Because I need that option I may reinstall the old driver and disconnect the TASCAM device when I'm not using it.  I want to see what TASCAM support says before going back to the old driver.  The problem has never occurred while using the device that I'm aware of.  Another option is to get a different audio interface device and see if I have better luck with it.

 

I'm not having any wifi problems with that laptop, so I'll leave it alone.

 

The most recent BIOS update is about a year later than what I'm using now.  It is from late 2010.  I'll leave it alone for now.

 

Gary

 

 

Thanks again for your help.



#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:26 AM

Posted 27 May 2015 - 05:25 AM

Removing features is usually done for a reason - so I wonder if it was those settings that were affecting the crashes?

It'll be interesting to see TASCAM's response.

Good luck!


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.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#8 GaryG45

GaryG45
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Vernon Hills, IL
  • Local time:09:26 AM

Posted 30 May 2015 - 04:33 PM

John,

I agree that TASCAM probably removed the features because they were the cause of problems.  About 4 months after I purchased it, they stopped selling it, so I was surprised to find the new drivers.  No word from TASCAM, and based on some posts I've seen in their forum, I;m beginning to believe that I will not hear anything.  I have re-downloaded and reinstalled the new driver in case something occurred during the previous download or installation to drop the features.  No changes in features with the second download and installation.  Therefore I've developed two options.

 

One is to re-install the old driver that has the features I need and change my workflow.  I always had the TASCAM device connected to the laptop, so now I've decided to connect it only when required.  From what I can remember, the BSOD always occurred when I wasn't using the TASCAM device, but when it was connected and I was using other USB connected devices(hard drives).  I've got the old driver installed, used the TASCAM device, and used USB connected external hard drives. No problems yet.

 

The other option is to get another audio interface device, and I've begun to research ones that have the features I want.  If I get another similar BSOD, it will be time to get another audio interface.

 

Thanks again for your help!

 

Gary



#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:26 AM

Posted 31 May 2015 - 05:04 AM

Thanks for letting us know.

Good luck!


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.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users