@jefft oh, man, I'm so sorry for you, this sucks ! My utmost respect for you grappling with this problem for years . I'm quite sure I couldn't stand this for so long. At least the "hardware solution" is working and you can keep on making music.

 

Yeah, this is the thing that had me wanting to look at the event logs. Just to see if it's the same service hanging with both devices. But hey, if I had a good workaround in place, and everything else worked as it should, I wouldn't hesitate to implement that as well.
I myself came from the component level troubleshooting world of consumer electronics. Unfortunately that industry has become modular throwaway with the advent of SMD manufacturing as most small shops didn't have the equipment/expertise needed to repair those types of boards.
I've also been in the software development world and can attest to the workaround methodology of that industry as well. So we as end users often have to implement our own workarounds to work around the workaround that the coders did.

 

So true.
But, honestly, I don't like it very much to work * at all.

So my way is looking for shortcuts to solve the problem and, if this doesn't work out, I would handle it the same as @jefft


*on computer problems

Couldn't agree more. BFD is so buggy, I deleted everything. No fun at all.

But I dream of a really new kind of OS - not for everything but especially designed for CPU heavy stuff like A/V and 3D (e.g. really heavy parallel processing). So well designed and slick that all vendors need to deliver highly optimized boards, drivers and software. No bells and whistles like a streetfighter bike. And a capsuled UI for those who like it colorful etc....
For that I would be even willing to pay ... you know, chistmas is around the corner so we all can make a wish ;)

 

Last edited: Nov 12, 2017

My first computer was a Dragon 32, no problems
My second computer was a Sharp MZ, no problems
My third was an Atari ST, running Dr T's sequencer, no problems.
My fourth was an Atari ST running Cubase ( on one floppy disk )
My fifth was where the trouble started, PC, windows .
Since then I ran several PC,s and a Mac, so I'm fairly experienced, but I realise that the more a computer can do, the more unreliable they become, so yes twoheart a Christmas wish for maybe better compatability, between computer formats, if the two main contenders got their heads together and built a computer that was compatable with all the third parties, one system for all.

 

your troubles started with Windows, right? any chance to remember how old, eventually what motherboard do you have, and where exactly do you plug the usb devices?
I'm afraid I have no memory of exact solution, but I remember years back when I was messing with BIOS, overclockin&shiet, I had no problems with my PC, but when I gave it to my brother, upgraded (and reseted) BIOS, he started to have strange issue of the backlit keyboard (which I had before too) to remain lit when PC is turned off, BUT when he put PC in sleep mode, keyboard backlit got turned off,
this led me to conclusion, there is something in BIOS which affects that,
moreover as I've been trying various rigs as hackintosh builds, I noticed every BIOS treats usb controllers differently (there's Intel 2.0, Intel 3.0, ASMedia 3.0, ASMedia with charging 3.0 etc...), there are some "handoff" settings, some options to set various levels of usb device initialization during boot, options to disable charging (a phone for ex.) via usb when PC is turned off, then there are "power states" options (basically means entire PC is not running at 100% performance when not doing intensive tasks etc..),
then also there's an issue with usb devices which are actually usb 1.1, those may cause severe problems with newer motherboards which are not designed for them directly (so for ex. you cannot plug mouse and audio interface in same usb pair, or PC refuses to shutdown etc.., much shiet to troubleshoot and find specific ports where the legacy device causes least problems),
and then there is another chance, that the Windows OS gets fucked up, it happened to me countless times I just did usb/chipset driver (re)install (or update) in slightly different order, and it just happened my external HDD sometimes failed to get recognized in Windows, also because it got powered off within seconds (strangely, the exact same hardware, just running hackintosh, external HDD connected properly every time lol)

 

i did have problems with usb on windows 7 and got a firewire card for audio, now it works great

normal windows 7 default crash every few months or so but nothing regular, except live likes to crash when you close it after big projects

Firewire is dee best

 

Make shure you plug it into a non-powered usb plug ( i mean when the computer is off, some USB port still still send current. That's why everybody was saying to turn off wake-on USB)
i have a behringer, which also doest have power on/off switch.
1-i made one for the power. (using a power supply will do also, but was not proper for me)
2-And to disconnect USB - to prevent it to pull current from the pc - ( or, in your case, prevent the pc to turn off ) just use a usb switch box.
(be carefull, they come in 2 types - 1 square plug to 2 USB male.This is what you need)
(( the other type is 1 USB female to 2 square plugs - not good in your case))

 

Sorry I'm late to the party. I have read a lot but not all of the previous posts, so apologies for that.


Is it possible to add the device in safe mode, by booting into safe mode with the networking option on?

 

Have Hou tried wait to kill process and force to kill tweaks in registry?

 

Event logs of the shutdown process would help identify which ones to kill. I think there's a way to have a batch automatically run on shutdown.
Granted, not a fix, but another workaround. Perhaps a bit more elegant than shutting devices down and/or disconnecting them prior to shutdown.
I know the OP has said he's got a solution he's satisfied with, but I like continuing the discussion. Perhaps it will help someone else.

 

BIG THANKS guys, but I finally gave up on this, and installed a switchable mains supply to both units. Now I just have to power down the units with a simple switch,before shutting down the PC. Not ideal but it works...... that is if I remember to do it...Lol

 

OK Ill send you the logs, But first please explain how to go about it, and where to find the logs.

 

I have a USB audio card (Tascam U-200) that gives me trouble. It either freezes my PC (Win 7) with BSOD or it just cut the communication with the interface (midi signal AND audio) . The BSOD message is clear about the culprit. It has to do with the driver. I have uninstalled. reinstalled, updated the driver but Tascam hasn't upgrade its drivers for a while.

That makes that card unusable. So it now serves as a trinket that picks up the dust. Like you, unfortunately' I could never found a cure so I gave up.

 

I'm sorry to hear that safran5020. Yes, it is the driver. ASIO driver is tricky to program properly. That's why you will usually hear me say "just buy RME". I'm not a fanboy nor RME's PR, just a realist. ;) My firewire TC Electronic SK48 used to give me blue screens at times before they updated the driver. I should have listened to my own advice.

Luckily, TC is working perfectly for me now and I'm incredibly happy with it.

 

You'd need to generate a log of a successful shutdown (with the interface turned off) and a log of a hung shutdown. The culprit would likely be either the last entry in the hung shutdown, or the very next item in the successful shutdown dependant on what's hanging. Once you see what's hanging up, you can try manually killing that process/service to see if it will successfully shutdown then. That way you know if killing it in a shutdown batch will work or not.
Hope I'm not bugging you with my curiosity about this.
@safran5020, I had an M-Audio Fast Track that would crash the DAW frequently. Got a Lexicon Omega and had similar results. Upgraded to a MOTU HD 192, and those difficulties disappeared. I'm very reluctant to entertain using any USB audio interfaces after this experience.

 

Man I sure hope I won't have any crash with my new Scarlett 18i20G2 USB

 

Digital Dragon, you've missed the point I think!. I'm not using the pod or the digitech as an audio interface, I use them so let as separate instruments, I have a focusrite sapphire pro 40 connected via FireWire for my main audio interface. I have the pod and digitech connected on the analogue inputs of the focusrite, and only use the USB connection to the pod and digitech to edit them. The two units and the pc are a distance away from my working area, and having to unplug stuff isn't practical, so I rewired the mains at a point I can reach with ease. This has solved my problem

 

Oh no, I get that. Merely was illustrating that I've had problems in the past with USB audio interfaces that I've used. I understand that you're using these connected up for patch editing. I tried doing the same with my old Roland GP-100 as I could see how much easier it would have been to edit patches this way.
To be fair, @safran5020, I wouldn't expect problems from a Scarlett. These were old XP era interfaces so likely it was driver problems with the Win 7 drivers.

 

Everytime that Ive had problems with USB, using a hub solved it. I dont understand it myself but it worked

 

@subGENRE, good to see you!