PDA

View Full Version : Delta Series, Vista 32, Suspend lockup

redrol
07-06-2008, 01:04 PM
I have Vista 32bit Business, A core 2 duo home build with an Asus P5B Intel 965 chipset, 4GB RAM, and 150GB WD Raptor Hard drive. My audio card is the M-Audio Delta Audiophile 192 and it is the only card in my system other than the GFX card which is an ATI X1650 Pro.

The issue is basically if Vista goes into suspend for any reason while sound is either being played OR if there is an audio app open which is accessing the M-Audio Delta (I have a Audiophile 192), the system goes into a hard lock.

This is pretty much not ok. I read the FAQ stating m-audio doesn't support suspend/hibernate but that does not make it ok for the audio card to lock the system entirely.

Any solutions?? :mad:

I have tried every driver revision available for Vista and they all do the same thing which is hard lock windows on suspend.
Vocalpoint
07-06-2008, 04:30 PM
Any solutions or am I going to have to get a new audio card?

Why would anyone use "suspend" anyway? Leave your machine at the ready or shut it off. Pretty simple fix.

And what's to say another card wouldn't do the same thing?
redrol
07-06-2008, 04:56 PM
Why would anyone use "suspend" anyway? Leave your machine at the ready or shut it off. Pretty simple fix.

And what's to say another card wouldn't do the same thing?

Because I used to have an EMU card and it worked, and also other various cards work fine. I can also remove the m-audio card, or disable it and use other cards and suspend works fine.

I use suspend every night and to save power durning times when I am not there. Its a very useful feature.
redrol
07-09-2008, 12:59 PM
I would like an official to comment on this issue so here is another bump.
redrol
07-09-2008, 01:04 PM
Im going to add something else. The default off button in Vista is actually suspend. I am very technically savvy but other users are going to hit the suspend button and wonder why their computer just locked up.
JA
07-14-2008, 10:28 AM
Our Verifications department has tested and reproduced this issue; logged it as a bug and reported it to the developer.
redrol
07-14-2008, 11:19 AM
That's fantastic. I just submitted a Incident report which is ID = NA127943. I will add one more thing which is that I have this problem using Service Pack 1 installed. Just a bit more info, if it helps.

Thank you!