Audigy LS stops random and functions properly after reboot

:Audigy LS stops random and functions properly after rebootM I am on a P5P800 motherboard with a SB Audigy LS in PCI2, running Windows 7 Beta and using version 5.2..200 of the driver.
I had the same problem on Windows Vista (both before and afer SP):
? at irregular intervals the sound card stops working. Mediamonkey does not detect the SB speakers anymore and none of the other programs can get audio to play.
All it takes is a system-reboot.
I know there is a later version of the driver, at least drivermax tells me there is a newer version. Trying to install this newer version results in the blue screen.
Any ideas where to look for the solution: I am sure that the chipset drivers are fine and I also tried switching the sound-card in from PCI3 to PCI2.
Help is wellcome: it is annoying most to have no sound randomly !

Restart the computer.

Similar Messages

Help! Keyboard stops responding and then works after reboot

My computer will start running really slowly and then the keyboard stops working, then after 30 seconds or so I lose the ability to click but the mouse still moves. Command-option-esc for force quit still works some of the time though but refreshing everything from there doesn't help. After I reboot everything goes back to normal. This has happened every other day or so for about a week. Help me please!

See if you get this behavior using another account.
See what happens when you safe boot.

Unable to stop applications and windows reopening after reboot Yosemite

I am wondering if my system became corrupted about a week ago after working well since upgrading to Yosemite when it was first released. When I reboot my system a number of applications open windows including Mail, iTunes, Excel, Adobe Reader, Calendar, Chrome, and VMWare. A window pops up asking for my iCloud password and it usually requires more than one attempt to enter the password before this disappears.
I have searched online and tried all the usual remedies. I have selected "Close windows when quitting an app" under "Settings, General". I have ensured that these items do not appear under "Login items" in "Settings, Users & Groups". I have tried selecting and unselecting "Reopen windows when logging back in" on the "Restart badge" that appears when requesting restart.
I also tried reinstalling Yosemite and later tried a "clean install" of Yosemite. In the latter case, I did restore my applications from Time Machine backup so it is not really a "fresh" system.
Does anyone have any idea how to approach this problem short of doing a clean install of Yosemite and then reinstalling all my applications?

I am wondering if my system became corrupted about a week ago after working well since upgrading to Yosemite when it was first released. When I reboot my system a number of applications open windows including Mail, iTunes, Excel, Adobe Reader, Calendar, Chrome, and VMWare. A window pops up asking for my iCloud password and it usually requires more than one attempt to enter the password before this disappears.
I have searched online and tried all the usual remedies. I have selected "Close windows when quitting an app" under "Settings, General". I have ensured that these items do not appear under "Login items" in "Settings, Users & Groups". I have tried selecting and unselecting "Reopen windows when logging back in" on the "Restart badge" that appears when requesting restart.
I also tried reinstalling Yosemite and later tried a "clean install" of Yosemite. In the latter case, I did restore my applications from Time Machine backup so it is not really a "fresh" system.
Does anyone have any idea how to approach this problem short of doing a clean install of Yosemite and then reinstalling all my applications?

Hi yesterday I and my companion stopped working and function imessedge facetime?

Hi yesterday I and my companion stopped working and function imessedge facetime?

My wifi doesn't work too what happened?

My itunes will stop working and shuts down after 5 to 10 minutes playing. I have the most recent updates. How can I repair or correct this from crashing?

My itunes will stop working and shuts down after 5 to 10 minutes playing. I have the most recent updates. How can I repair or correct this from crashing?

Hello there, jbenjaminii.
The following Knowledge Base article offers up some great recommendations for troubleshooting the issue you're describing:
iTunes for Windows XP: Troubleshooting unexpected quits, freezes, or launch issues
http://support.apple.com/kb/ts1421
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

File sharing between Mac Mini and iMac "breaks" after reboot of either device, and won't restore. Why? Running Maverick 10.9.1 on both. File sharing is setup on both. Help.

I'm a new user - recent convert from longtime Windows to Apple. Thought having desktops and computing aligned with phones and tablets would help. Not so far.
I have a MacMini running Mavericks 10.9.1, and an iMac running Mavericks 10.9.1. File Sharing is set up on both. If either device is rebooted for any reason, file sharing from the Mac Mini to the iMac "breaks" and will not easily restart. Various things eventually brings the connection back - usually having to do with checking and unchecking File Sharing, the AFP button, and/or the SMB button on the iMac - but never the same procedure twice in a row. File Sharing from the iMac to the Mac Mini is never disrupted - always comes back up without a problem. Screen Sharing also works between both without fail, and comes up after reboot of either. No problem there. Only difficulty is from Mac Mini to the iMac.
Why? Any ideas?

Should also clarify - usually takes multiple hours of checking/unchecking file sharing settings in order to restore the share between Mac Mini and iMac. NEVER happens automatically.
This is disruptive because I've got the Mac Mini pointing to several file locations on the iMac for various things - photos, music, etc. - and they all hang up unless the share is restored. Real bummer.

How to start CRS and other services after rebooting nodes.

Hi,
i have created two node cluster database.how to start CRS and other service after rebooting nodes?
Thanks,

use crsctl command start...
$ORA_CRS_HOME/bin/crsctl start crsOr check status about CLusterware...
$ORA_CRS_HOME/bin/crsctl check crs
CSS appears healthy
CRS appears healthy
EVM appears healthyIf not OK... check log at $ORA_CRS_HOME/log/hostname/*
and check status database , service and etc...
use crs_stat
$ORA_CRS_HOME/bin/crs_stat -t
$ORA_CRS_HOME/bin/crs_stat if you find some service or instance ... not online...
use srvctl command, help to start
Get Help...
$ORA_CRS_HOME/bin/srvctl -h

Frozen and still frozen after reboot

Macbook Airs frozen and still frozen after reboot?

Greetings Ging ging,
It seems your MacBook Air is frozen and is not responding after starting up. You may want to consider performing a PRAM reset, which may help you get your device back up and running:
OS X Yosemite: Reset your computer’s PRAM
If your Mac doesn’t seem to be remembering your speaker volume, display resolution, or the disk it should be using during startup, you may need to reset your computer’s PRAM.
Resetting PRAM may change some system settings and preferences. Use System Preferences to restore your settings.
Important: To print these instructions, click the Share button in the Help window, then choose Print.
Choose Apple menu > Shut Down.
Locate the following keys on the keyboard: Option, Command (⌘), P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on your Mac.
Immediately press and hold the Option-Command-P-R keys. You must press this key combination before the gray screen appears.
Continue holding the keys down until your Mac restarts, and you hear the startup sound for the second time.
Release the keys.
After resetting your computer’s PRAM, you may need to update your speaker volume, display resolution, and startup disk preferences. For more information about PRAM, see the Apple Support article About NVRAM and PRAM.
Thank you for contributing to Apple Support Communities.
Best,
Bobby_D

IMessage doesn't function properly after iOS 8 update

Looked everywhere for somebody with a similar problem but only came to find issues with group messaging, so here is my issue:
I have an iPhone 5C, 16GB with the brand new iOS 8 update.
Before iOS 8, I was able to use all the features of my phone to their full potential, including iMessage.
After about 2 days of having iOS 8, an issue presented itself, I couldn't iMessage only a handful of my friends.
Oddly enough, my iMessage has been acting slow, but still functioning for everyone else while the handful of friends I mentioned before cannot receive or message me using iMessage.
To clarify what happens:
When I click on my Messages app on my iPhone I use the above top-right plus sign to create a new conversation.
When I begin to type in their contact, I notice their name is gray. If this isn't an issue already, when I click on their name to create a new conversation, despite it being gray, it shows green instead of the official iMessage blue, which is the only way I can contact them.
I'd also like to point out that it does not matter whether I am connected to WiFi or using my AT&T Cellular data, iMessage just fails to function properly.
If it helps, the two people I have noticed this issue with have iPhone 4's running the latest iOS 7 firmware. I have been able to message another friend with an iPhone 4, which is a reason I think their phones aren't the issue.
Thanks!

I've had lots of problems with sending some messages as text messages and then other times as iMessages even though I have data and am signed into iCloud and am sending to another iPhone. Group messages are definitely problems with everyone having iPhones. It seems like it usually involves someone who hasn't updated to iOS8 yet. But it doesn't always mess up. It seems random for me and my friends and family who are having these same issues.

Ios 7.0.3 was updated and installed but after reboot it was still in 7.0.2

i'm unable to update from ios 7.0.2 to ios 7.0.3 which is the latest version for my iphone 4 but it isn't updating from 7.0.2 to 7.0.3 after rebooting
please help me what might be the problem

I believe in the initial iOS 7.0.0 release, the "Reduce Motion" only affected the Parallax effect. iOS 7.0.3 now affects both the Parallax effect as well as zoom effect. Disabling motion now changes the zoom effect to a fade effect while the Parallax feature remains the same.

Word 2010 "An error occured and this feature is no longer functioning properly" after sequencing in App-V 4.6 SP3

Hi all,
I've got a very frustrating one at the moment - I'm trying to sequence Office 2010 Pro Plus, and am having real issues with word throwing the error above. I've tried sequencing both 'manually' using the guidance
here and also using the available Package Accelerator and get exactly the same problem using either method. On launch of Word 2010 in the 'Streaming' phase I throws the aforementioned
error. I have read
this post and have seen that Office must be installed to a unique location in the sequencing drive - I am using 'A:\Office 2010 Professional Plus'. I'm using App-V 4.6 SP3 (for RDS), but I've tried with the SP1 and SP2 sequencer to see if that made a difference
which it didn't.
If anyone has any suggestions for anything to try I'd be very grateful.
Many Thanks,
James

Hi Steve, thanks for your reply.
On the sequencer I used the following flags as two separate commands when installing manually and combined as one when using the Accelerator Package as recommended;
Licensing Flags: PROPLUS=1 VISIOPRO=1 PROJECTPRO=1 SPD=1
Virtual Proxies: ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={F453A898-EFDC-40E2-8C64-C2FD7AA4D4E9} PACKAGEVERSION=14.0.4763.1000 OUTLOOKNAME="Microsoft Outlook 2010" ONENOTENAME="Microsoft
OneNote 2010" MAPISERVER="Microsoft Virtual Office Simple Mapi Proxy Server" VIRTUALSEARCHHOST="Search MAPI Protocol Handler Host" MLCFG32CPL="Virtual Mail Control Panel Applet" OWSSUPPServer="Microsoft SharePoint Client Support Manager"
I haven't even got as far as the client yet unfortunately as I'm getting this error before I even leave the Sequencing environment!
And Nicke, thank you also for your comment. I have tried on a new sequencing VM and get exactly the same results. I haven't quite followed your guide to the letter (Haven't installed some of the software you do) but I have followed the App-V Sequencing Guide
from Microsoft and I must say I haven't had any issues with any other applications I've sequenced so far.
Many thanks.

Auto Sync not functioning properly after Auto Tone

Auto Sync is functioning as expected, unless I choose Auto Tone first.
I have about 1000 Images that I wish to apply a Preset to. When I created the Preset using New Develop Preset, I left all of the options checked except Exposure.
I want to use Auto Tone to set the exposure for each image automatically, and then apply my preset to all images, leaving their exposures unchanged. If I apply the Preset to all of the images before selecting Auto Tone, everyting works as expected. If I choose Auto Tone first, a small portion of the selected images will be updated, but most will not. The preset will change all settings except those in the Basic Tone area. It's as if Auto Tone has somehow become "sticky" and will not allow itself to be overridden. Even if I choose a single image, apply my new settings to it, and then manually select Sync, it doesn't work for all images. It also won't work if I have have Auto Sync selected, and then make manual changes to individual sliders. It will work for some images near the ones I see in the filmstrip on the bottom, but not all of the images selected.
This is extremely frustrating. Again, everything works exactly as expected, unless I choose Auto Tone first.

kbarre wrote:
Auto Sync is functioning as expected, unless I choose Auto Tone first.
If I choose Auto Tone first, a small portion of the selected images will be updated, but most will not.
Lightroom's handling of auto-tone leaves something to be desired - I have a lot of experience with it, trying to make reliable develop-setting plugins which include auto-toning. Those plugins have a bewildering amount of logic - something like this: initiate auto-toning, check back to see if it has properly settled, issue the auto-toning again if it never seems to be properly settling... - usually it works out after a while, but even sometimes it never does, and generates an error: can't get auto-toning to settle across all photos.
The point of all this is that there are bugs in Lr's handling of auto-toning, as you are growing aware.
Try this:
* do the auto-toning, then let it percolate for a while.
* then visit each photo at 1:1 (to force Lr to finalize settings...), and confirm auto-toning has settled...
Then try auto-syncing that preset (make sure process versions are all the same, and preset does NOT include auto-toning - I would leave process version OUT of your presets).
Better?
I don't expect this is a workflow you'll want to do all the time, but as a test it might help shed some light on the problem.
Rob

USB 2.0 not functioning properly after upgrading to 3.10.3-1 kernel

After upgrading to the 3.10.3-1 kernel USB 2.0 is not working anymore on my ASrock ION330 nettop.
I just did a system upgrade (including a kernel upgrade to 3.10.5-1), but the problem remains...
Here's the relevant messages that I extracted with journalctl -b
Aug 07 09:59:11 alcyone kernel: ACPI: bus type USB registered
Aug 07 09:59:11 alcyone kernel: usbcore: registered new interface driver usbfs
Aug 07 09:59:11 alcyone kernel: usbcore: registered new interface driver hub
Aug 07 09:59:11 alcyone kernel: usbcore: registered new device driver usb
Aug 07 09:59:11 alcyone kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Aug 07 09:59:11 alcyone kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Aug 07 09:59:11 alcyone kernel: ehci-pci: EHCI PCI platform driver
Aug 07 09:59:11 alcyone kernel: ohci_hcd 0000:00:04.0: setting latency timer to 64
Aug 07 09:59:11 alcyone kernel: ohci_hcd 0000:00:04.0: OHCI Host Controller
Aug 07 09:59:11 alcyone kernel: ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 1
Aug 07 09:59:11 alcyone kernel: ohci_hcd 0000:00:04.0: irq 16, io mem 0xfae7f000
Aug 07 09:59:11 alcyone kernel: hub 1-0:1.0: USB hub found
Aug 07 09:59:11 alcyone kernel: hub 1-0:1.0: 6 ports detected
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: setting latency timer to 64
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: EHCI Host Controller
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: new USB bus registered, assigned bus number 2
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: debug port 1
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: cache line size of 64 is not supported
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: irq 18, io mem 0xfae7ec00
Aug 07 09:59:11 alcyone kernel: ehci-pci 0000:00:04.1: USB 2.0 started, EHCI 1.00
Aug 07 09:59:11 alcyone kernel: hub 2-0:1.0: USB hub found
Aug 07 09:59:11 alcyone kernel: hub 2-0:1.0: 6 ports detected
Aug 07 09:59:11 alcyone kernel: hub 1-0:1.0: USB hub found
Aug 07 09:59:11 alcyone kernel: hub 1-0:1.0: 6 ports detected
Aug 07 09:59:11 alcyone kernel: usb 2-2: new high-speed USB device number 3 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-2: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-2: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-2: new high-speed USB device number 4 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-2: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-2: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-2: new high-speed USB device number 5 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-2: device not accepting address 5, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-2: new high-speed USB device number 6 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-2: device not accepting address 6, error -71
Aug 07 09:59:11 alcyone kernel: hub 2-0:1.0: unable to enumerate USB device on port 2
Aug 07 09:59:11 alcyone kernel: usb 2-3: new high-speed USB device number 7 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-3: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-3: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-3: new high-speed USB device number 8 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-3: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-3: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-3: new high-speed USB device number 9 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-3: device not accepting address 9, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-3: new high-speed USB device number 10 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-3: device not accepting address 10, error -71
Aug 07 09:59:11 alcyone kernel: hub 2-0:1.0: unable to enumerate USB device on port 3
Aug 07 09:59:11 alcyone kernel: usb 2-5: new high-speed USB device number 12 using ehci-pci
Aug 07 09:59:11 alcyone kernel: usb 2-5: device descriptor read/64, error -71
Aug 07 09:59:11 alcyone kernel: usb 2-5: device descriptor read/64, error -71
Aug 07 09:59:12 alcyone kernel: usb 2-5: new high-speed USB device number 13 using ehci-pci
Aug 07 09:59:12 alcyone kernel: usb 2-5: device descriptor read/64, error -71
Aug 07 09:59:12 alcyone kernel: usb 2-5: device descriptor read/64, error -71
Aug 07 09:59:12 alcyone kernel: usb 2-5: new high-speed USB device number 14 using ehci-pci
Aug 07 09:59:13 alcyone kernel: usb 2-5: device not accepting address 14, error -71
Aug 07 09:59:13 alcyone kernel: usb 2-5: device not accepting address 15, error -71
Aug 07 09:59:13 alcyone kernel: hub 2-0:1.0: unable to enumerate USB device on port 5
Aug 07 09:59:13 alcyone systemd[1]: Found device MCP79 Ethernet.
Aug 07 09:59:14 alcyone kernel: usb 1-1: new low-speed USB device number 2 using ohci_hcd
Aug 07 09:59:14 alcyone kernel: usb 1-4: new low-speed USB device number 3 using ohci_hcd
I'm glad that keyboard and mouse are working properly under USB 1.0, but neither my usb-parport printer nor my USB external hard drive are recognised any more :-(
Any ideas how to solve this?? (I'd prefer not to downgrade the kernel)
Last edited by zilverling (2013-08-07 14:28:36)

I've discovered it's not that USB 2.0 is not working. 3 out of 6 usb ports/busses seem to work properly. The other three seem totally dead. Obviously this was not the case under kernel 3.9.9-1. Downgrading to kernel 3.10.2 made no difference.
In practical terms this means that I can use my printer and access my external drive if I use the right port/bus. And I could probably work around the problem by plugging a USB hub in one of the working ports. But I would be happy to get rid of the error messages and have all 6 usb busses working as they did before...

Open Office Not Functioning Properly After Mavericks 10.9.1 Update Today

Is anyone else getting this issue?
Everyone in the company I manage was using MS Office on their Windows-based computers and we were getting a lot of annoying formatting incompatibilities becasue I was using Pages on my Mac. I actually prefer Open Office and started using that again but we were still having trouble. I decided to install Open Office on all of our computers to avoid cross-platform dramas and with us all using Open Office, it has meant that we've elimintated all annoying little formatting incompatibilities and other problems.
We've been using Open Office on 3 Windows-Based computers and my MacBook Pro for about 3 months. I agreed to the latest Mavericks update 10.9.1 today and since then, whenever I start my Open Office application, I'm getting this annoying little box that won't go away (see attached picture) and numerous options in Open Office can't be accessed. I've deleted and reinstalled Open Office this morning and tried different combination of shutdown, restart, force quit and nothing seems to affect this problem. I also can't reopen files recently opened because an error box pops up to say that they can't be opened because Open Office is not installed. Yet I can go to finder and open them from there.
It would take too much time to list all of the separate issues I've found; so in summary, a lot of the Open Office functionality just ISN'T WORKING since the Mavericks update today. Apple, what have you done?! What can BE done to fix this?

Hi navaneeth27
Yes that's exactly what I'm experiencing.
I'm wondering whether it has something to do with having had Open Office running while installing the update to Mavericks 10.9.1. I had OO open when I agreed to the update and I was still working on a Writer file when my MacBook Pro unexpectedly shut itself down and began installing the update, showing only a progress bar in a small window before reloading everything. It was at that point that the unresponsive 'Don't Reopen' 'Reopen' window appeared. It's insidious and stopping much of the functionalty of OO from working. Such a pain!
I force-quit OO, fully uninstalled it, purged all mention of it from my MBP, restarted tried opening files that were set to be opened by OO by default, and confirmed that they were being opened by Pages - and they were by default. I then reinstalled OO 4.0.1 from the OO site (and that's what I had earlier today, before this adventure began). I then tried opening some previous documents that were saved as .doc and OO popped up WITH the 'Don't Reopen' 'Reopen' window AAAAGAIN!
I'm working on 2 screens so I've placed the box that just won't go away at the very edge of my MBP screen and am workng on files on my second screen - but much of the functionality still isn't available.
I'm stuck and don't know what to do next.

LG 22-inch monitor won't function properly after last Mac OS X Update

My new LG 22-inch monitor was working great until I received the last Mac OS X Update (10.4.9). I received this update after installing Tiger (better late than never...ha ha) and after I restarted my system, I saw multiples of the same files on my desktop, and when I would open a window, four duplicate windows would appear (this did not happen until after the update). The only thing that corrects the problem is to go into System Preferences => Displays and change the monitor resolution. But even after I Click to Lock Changes, I have to go in and do this every time I launch my system. I was so vexed that I hooked up the former monitor (Apple CRT, 17 inch) and now the same thing is happening to it! Sigh... I am no Mac Genuis, but I know someone out there can offer some advice! Thanks!
533 MHz PowerPc G4 Mac OS X (10.4.9) LG L226WTQ 22 inch flat panel monitor

lgcustodio wrote:
I ran the disk utility and saws verify disk ok. I did the same process for repair disk permissions and seems to have problems.
These warnings are accurate but according to Apple can safely be ignored. See Mac OS X 10.5: Disk Utility's Repair Disk Permissions messages that you can safely ignore. IOW, They are not normally problems.
I check the volume scheme but I don't have any partition
You do have partitions & a partition scheme. To check what the scheme is, click on +the drive itself+ in the list on the left in Disk Utility. It will probably be identified as "298,1 GB WDC WD3200AAJS-40VWA0 Media" or something very similar. If it contains the startup disk, it will be the first item in the list. It will have one or more named volumes indented under it, such as "Macintosh HD."
When you have clicked on the WDC drive instead of a volume name indented under it, you should see seven items of information about it at the bottom of Disk Utility's window, to the right of an icon representing the drive. The info is in two columns. The last item in the rightmost column, below the S.M.A.R.T. Status (which should say "Verified"), should be "*Partition Map Scheme :* " & be followed by the scheme type. It should be "GUID Partition Table."
If you don't see the seven info items after selecting the drive, it may indicate a problem that needs attention, but I suspect that you just haven't looked in the right place for the info....
As for the 'cannot install' message, make sure that you have downloaded the right update, that it is not the server update version for example. You may need to download it again, discarding the first download as somehow defective.

Audigy LS stops random and functions properly after reboot

Similar Messages

Maybe you are looking for