Survey sometimes on startup

Sometimes i am redirected to a survey page (http://w.prize44.com). No strange programs installed, no Add-Ons, No strange startups in the about:config and my anti-virus and malwarebytes couldn't find nothing.
Please Help.

Do a malware check with several malware scanning programs on the Windows computer.
Please scan with all programs because each program detects different malware.
All these programs have free versions.
Make sure that you update each program to get the latest version of their databases before doing a scan.
*Malwarebytes' Anti-Malware:<br>http://www.malwarebytes.org/mbam.php
*AdwCleaner:<br>http://www.bleepingcomputer.com/download/adwcleaner/<br>http://www.softpedia.com/get/Antivirus/Removal-Tools/AdwCleaner.shtml
*SuperAntispyware:<br>http://www.superantispyware.com/
*Microsoft Safety Scanner:<br>http://www.microsoft.com/security/scanner/en-us/default.aspx
*Windows Defender:<br>http://windows.microsoft.com/en-us/windows/using-defender
*Spybot Search & Destroy:<br>http://www.safer-networking.org/en/index.html
*Kasperky Free Security Scan:<br>http://www.kaspersky.com/security-scan
You can also do a check for a rootkit infection with TDSSKiller.
*Anti-rootkit utility TDSSKiller:<br>http://support.kaspersky.com/5350?el=88446
See also:
*"Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked

Similar Messages

  • Firmware Update Bar sometimes on startup

    Hello,
    I have the last white unibody macbook Apple has released and sometimes during startup it gave me the firmware update bar and then booted normally.
    After showing this bar twice it restarts normally entering directly the operating system without any problems.
    Does anybody knows why this happened ?
    Any suggestions on what can be donne so to be sure it will not happen again ?
    Thanks In advance

    This article might answer your question:  http://support.apple.com/kb/ts3148.
    Looks like it could be just a normal event, especially if you had just installed system updates. 

  • Sometimes at startup the system freezes

    sometimes not always the system after i enter the login password the system freezes why this happening?

    the output of journalctl --since=2014-05-14 is
    May 14 01:07:56 archkostas systemd[943]: Starting Paths.
    May 14 01:07:56 archkostas systemd[943]: Reached target Paths.
    May 14 01:07:56 archkostas systemd[943]: Starting Timers.
    May 14 01:07:56 archkostas systemd[943]: Reached target Timers.
    May 14 01:07:56 archkostas systemd[943]: Starting Sockets.
    May 14 01:07:56 archkostas systemd[943]: Reached target Sockets.
    May 14 01:07:56 archkostas systemd[943]: Starting Basic System.
    May 14 01:07:56 archkostas systemd[943]: Reached target Basic System.
    May 14 01:07:56 archkostas systemd[943]: Starting Default.
    May 14 01:07:56 archkostas systemd[943]: Reached target Default.
    May 14 01:07:56 archkostas systemd[943]: Startup finished in 67ms.
    May 14 01:08:13 archkostas org.kde.kuiserver[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 14 01:08:13 archkostas org.kde.kuiserver[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 14 01:14:30 archkostas org.kde.ApperSentinel[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 14 01:14:30 archkostas org.kde.ApperSentinel[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 14 02:08:11 archkostas org.kde.kuiserver[956]: kuiserver: Fatal IO error: client killed
    May 14 02:08:12 archkostas systemd[943]: Stopping Default.
    May 14 02:08:12 archkostas systemd[943]: Stopped target Default.
    May 14 02:08:12 archkostas systemd[943]: Stopping Basic System.
    May 14 02:08:12 archkostas systemd[943]: Stopped target Basic System.
    May 14 02:08:12 archkostas systemd[943]: Stopping Paths.
    May 14 02:08:12 archkostas systemd[943]: Stopped target Paths.
    May 14 02:08:12 archkostas systemd[943]: Stopping Timers.
    May 14 02:08:12 archkostas systemd[943]: Stopped target Timers.
    May 14 02:08:12 archkostas systemd[943]: Stopping Sockets.
    May 14 02:08:12 archkostas systemd[943]: Stopped target Sockets.
    May 14 02:08:12 archkostas systemd[943]: Starting Shutdown.
    May 14 02:08:12 archkostas systemd[943]: Reached target Shutdown.
    May 14 02:08:12 archkostas systemd[943]: Starting Exit the Session...
    May 14 02:08:12 archkostas systemd[943]: Received SIGRTMIN+24 from PID 2887 (kill).
    -- Reboot --
    May 16 16:04:58 archkostas systemd[1109]: Reached target Paths.
    May 16 16:04:58 archkostas systemd[1109]: Starting Timers.
    May 16 16:04:58 archkostas systemd[1109]: Reached target Timers.
    May 16 16:04:58 archkostas systemd[1109]: Starting Sockets.
    May 16 16:04:58 archkostas systemd[1109]: Reached target Sockets.
    May 16 16:04:58 archkostas systemd[1109]: Starting Basic System.
    May 16 16:04:58 archkostas systemd[1109]: Reached target Basic System.
    May 16 16:04:58 archkostas systemd[1109]: Starting Default.
    May 16 16:04:58 archkostas systemd[1109]: Reached target Default.
    May 16 16:04:58 archkostas systemd[1109]: Startup finished in 67ms.
    May 16 16:05:15 archkostas org.kde.kuiserver[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 16:05:15 archkostas org.kde.kuiserver[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 16:11:32 archkostas org.kde.ApperSentinel[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 16:11:32 archkostas org.kde.ApperSentinel[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 16:48:41 archkostas org.kde.ApperSentinel[1123]: apper-sentinel: Fatal IO error: client killed
    May 16 16:48:41 archkostas systemd[1109]: Stopping Default.
    May 16 16:48:41 archkostas systemd[1109]: Stopped target Default.
    May 16 16:48:41 archkostas systemd[1109]: Stopping Basic System.
    May 16 16:48:41 archkostas systemd[1109]: Stopped target Basic System.
    May 16 16:48:41 archkostas systemd[1109]: Stopping Paths.
    -- Reboot --
    May 16 17:30:54 archkostas systemd[1063]: Starting Paths.
    May 16 17:30:54 archkostas systemd[1063]: Reached target Paths.
    May 16 17:30:54 archkostas systemd[1063]: Starting Timers.
    May 16 17:30:54 archkostas systemd[1063]: Reached target Timers.
    May 16 17:30:54 archkostas systemd[1063]: Starting Sockets.
    May 16 17:30:54 archkostas systemd[1063]: Reached target Sockets.
    May 16 17:30:54 archkostas systemd[1063]: Starting Basic System.
    May 16 17:30:54 archkostas systemd[1063]: Reached target Basic System.
    May 16 17:30:54 archkostas systemd[1063]: Starting Default.
    May 16 17:30:54 archkostas systemd[1063]: Reached target Default.
    May 16 17:30:54 archkostas systemd[1063]: Startup finished in 78ms.
    -- Reboot --
    May 16 16:04:58 archkostas systemd[1109]: Starting Paths.
    May 16 17:33:29 archkostas systemd[1371]: Reached target Paths.
    May 16 17:33:29 archkostas systemd[1371]: Starting Timers.
    May 16 17:33:29 archkostas systemd[1371]: Reached target Timers.
    May 16 17:33:29 archkostas systemd[1371]: Starting Sockets.
    May 16 17:33:29 archkostas systemd[1371]: Reached target Sockets.
    May 16 17:33:29 archkostas systemd[1371]: Starting Basic System.
    May 16 17:33:29 archkostas systemd[1371]: Reached target Basic System.
    May 16 17:33:29 archkostas systemd[1371]: Starting Default.
    May 16 17:33:29 archkostas systemd[1371]: Reached target Default.
    May 16 17:33:29 archkostas systemd[1371]: Startup finished in 78ms.
    May 16 17:33:46 archkostas org.kde.kuiserver[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 17:33:46 archkostas org.kde.kuiserver[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 17:40:02 archkostas org.kde.ApperSentinel[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 17:40:02 archkostas org.kde.ApperSentinel[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    May 16 17:40:48 archkostas org.kde.kuiserver[1416]: kuiserver: Fatal IO error: client killed
    May 16 17:40:48 archkostas org.kde.ApperSentinel[1416]: apper-sentinel: Fatal IO error: client killed
    May 16 17:40:48 archkostas org.a11y.Bus[1416]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async re
    May 16 17:40:48 archkostas systemd[1371]: Stopping Default.
    May 16 17:40:48 archkostas systemd[1371]: Stopped target Default.
    May 16 17:40:48 archkostas systemd[1371]: Stopping Basic System.
    May 16 17:40:48 archkostas systemd[1371]: Stopped target Basic System.
    May 16 17:40:48 archkostas systemd[1371]: Stopping Paths.
    May 16 17:40:48 archkostas systemd[1371]: Stopped target Paths.
    May 16 17:40:48 archkostas systemd[1371]: Stopping Timers.
    May 16 17:40:48 archkostas systemd[1371]: Stopped target Timers.
    May 16 17:40:48 archkostas systemd[1371]: Stopping Sockets.
    May 16 17:40:48 archkostas systemd[1371]: Stopped target Sockets.
    May 16 17:40:48 archkostas systemd[1371]: Starting Shutdown.
    May 16 17:40:48 archkostas systemd[1371]: Reached target Shutdown.
    May 16 17:40:48 archkostas systemd[1371]: Starting Exit the Session...
    May 16 17:40:48 archkostas systemd[1372]: pam_unix(systemd-user:session): session closed for user kostas
    -- Reboot --
    May 16 21:36:59 archkostas systemd[1049]: Starting Paths.

  • Safari won't open sometimes on startup

    Hi, over the last few days, safari hasn't been opening from the dock immediately after I have turned on my macbook, it just keeps jumping up and down and then I have to force quit it. Any idea why this might be happening?
    Thanks

    Possibly because Safari is starting up too soon, when resources aren't available to it. If you have it setup as a login item, you should remove it from that, then startup your Mac and after you get the Finder and Desktop fully initialized, start Safari and see if the problem is resolved.
    You also should use Disk Utility to Repair Permissions, then restart Safari to test it as well. If the problem still persists, create a new User Account and try running Safari there to see if the problem continues.
    Mulder

  • LV2009 SP1 Crashing (sometimes) on startup

    My morning has taken an significant turn for the worse.  
    It's funny how these things only seem to happen when there's a huge deadline or some other mitigating factors to the inconvenient into a disaster.
    After a reboot and three startup attempts in a row, LabVIEW finally started.  But I'm not sure that I can trust it will start again.  
    The instability seems to have started after I did the SP1 upgrades.  This PC (running XP SP3 on an Intel Dual Core) has Real Time and the FPGA addons. SP1 upgrades were done for these packages as well.  The latest Device Drivers have also been installed.  
    The problem first appeared when I was attempting to open an RT project directly from disk a few days ago. The crash warning appeared several times in a row, and then finally one attempt was successful.  
    I've attached the .txt dump that was generated this morning.  Not sure if the NI guys can find anything useful in this.  
    My predicament is that I've several important installs and some frantic development to complete this week.  The time to reinstall 2009 is something I really don't have.  But if my machine suddenly becomes completely unusable while I'm at the customer's site, I'll be up the creek without a paddle.  (Or I suppose I could use my laptop as a paddle, since that's about all it would be good for at that point)  
    I haven't seen any other reports like this one.  It's possible that LV is not the culprit here, and reinstalling won't remedy anything.  So I'm looking for suggestions.  
    My saving grace might be my dual boot.  I do have Win7 setup in another partition, and although it's seen very little use; I've not seen this happening there.  I am concerned about suddenly jumping OSes in the middle of some very important projects however.  
    Any suggestions (or perhaps shoulders to cry on) would be most welcome.    
    Patrick Allen
    Attachments:
    9b09_appcompat.txt ‏128 KB

    I have had this problem a few times in the past, but this afternoon it started occurred every time I tried to open LabVIEW. Tried reboot. Tried ending some processes. Tried pacpac's idea using the "IsFirstLaunch"=True, to no avail.
    What worked for me was: I launched MAX (thankfully that worked), then from within MAX, I launched LV 2009 (see picture).
    Someone else mentioned having this issue possibly related to a VI set to Run When Opened. Earlier today, I was working with just such a VI and having to abort a lot. I have since set that VI to not run when opened. Just hoping that was it.
    Richard
    Attachments:
    launch from MAX.JPG ‏35 KB

  • Sometimes on startup, Foxfire starts as a process rather than an application such that I have to end it as a process then restart it as an application

    When I click on the foxfire icon, the sound of the disk is heard. This soon stops. The hourglass appears for a short time and then disappears. There are no other signs that the program is running as a process other than using Windows TaskManager and looking in the process list. When this happen, I delete foxfire as a process and then restart it as I normally do. This usually works in getting it started.

    Although possibly not related to your problem, I have to remind you that the version of Firefox you are using at the moment has been discontinued and is no longer supported. On top of this, it has known unpatched bugs and security problems. I urge you to update to the latest version of Firefox, for maximum security, stability, performance and usability. You can get it for free, as always, at [http://www.getfirefox.com getfirefox.com].
    As for your problem, it's possible that you are having a problem with some Firefox add-on that is hindering your Firefox's normal behavior. Have you tried disabling all add-ons (just to check), to see if Firefox goes back to normal?
    Whenever you have a problem with Firefox, whatever it is, you should make sure it's not caused by one (or more than one) of your installed add-ons, be it an extension, a theme or a plugin. To do that easily and cleanly, run Firefox in [http://support.mozilla.com/en-US/kb/Safe+Mode safe mode] (don't forget to select ''Disable all add-ons'' when you start safe mode). If the problem disappears, you know it's from an add-on. Disable them all in normal mode, and enable them one at a time until you find the source of the problem. See [http://support.mozilla.com/en-US/kb/Troubleshooting+extensions+and+themes this article] for information about troubleshooting extensions and themes and [https://support.mozilla.com/en-US/kb/Troubleshooting+plugins this one] for plugins.
    If you need support for one of your add-ons, you'll have to contact its author.
    If the problem does not disappear when all add-ons are disabled, please tell me, so we can work from there. Please have no fear of following my instructions to the line, as all can be easily undone.

  • What to do when my Macbook air won't load from startup. It hangs in the middle during the black apple screen at the beginning

    my Mac book air will not start up it hangs in the middle of the status bar when I turn it on and will not move.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • Dual 2,5GHz G5 with startup problems

    Hi,
    I have a Dual 2,5GHz (June 2004 model) G5 with the following problem:
    When I try to turn it on, the screen sometimes stays dark. This is often the case the first time in the morning. Occasionally when this happens the front power LED is off. I have to power it off and try again.
    After usually 2-3 tries I get it to boot, the LED is on, the system boots but freezes during boot (sometimes at the grey Apple logo) or it boots completely and freezes after a while of working with it.
    I reseated the video card and also checked battery voltage (it's 3.6V as it should be) and even put in a new one just to be sure, but that didn't change anything. I also tried the PMU reset from time to time.
    I suspected bad RAM and since I have 2 pairs of the original 2x256MB and 1 pair of newer 512MB modules I started testing RAM by using the memtest in single user mode. Now comes the weird thing:
    Sometimes the G5 freezes during memtest, but most of the time it runs and passes all tests with OK. I always put in 1 pair of RAMs at a time (the first 2x256, then the other 2x256, then the 2x512) to rule out bad RAM. Since memtest never displayed an error as long as the machine did not freeze I think I ruled out bad RAM. They also seem to work fine in another G5 (same model).
    Then I thought maybe some RAM slots on the logic board are defective and repeated the above tests with other slot pairs, but the outcome is still the same.
    I am not quite sure, but I think the logic board went bad. Do you have any additional suggestions? Is it also possible that the CPUs are the culprit or can that be ruled out?
    Thanks
    Björn
    PS: I forgot to mention that sometimes the startup chime does not play and (very rarely) it plays but gets cut off at the end.

    Hi DaddyPaycheck,
    I know that.
    Sorry, but what I meant was that this problem has nothing to do with the hard disk not working or the OS on it being corrupted. The G5 doesn't even get to the point where booting comes into play. It hangs most of the time way before that. I am pretty sure that it's the logic board, but it could also be defective CPUs and I was hoping for someone with a similar problem to narrow it down.
    Björn
    PS: Can it still be the power supply even though it's always powering on and turning on the fans? I never had the case that the G5 stayed completely "dead" which usually means the PS is defective.

  • Startup Volume screen keeps on appearing - no keys pressed though

    I've had this problem since I've had my Mac mini (about a year now). Sometimes the startup volume screen appears despite not having any other Hard Drives connected apart from the boot drive (which is the internal Hard drive) and despite not pressing any keyboard keys on startup.
    I am using 10.5.2 with the latest mini firmware and am unable to think what could be causing this? I have selected my main hard-drive in the startup disk preferences and have no permissions/hard drive problems (so says disk utility) but the problem persists. It's a minor annoyance but one I would welcome any help with.
    Many thanks,
    Paul
    Message was edited by: Paul Woodford

    Hi and many thanks for the reply.
    The only drive I attach is a firewire one to do time machine backups but I always disconnect it once I've finished backing up (the firewire lead is still attached to my Mac though, just not to the drive).
    The SMART status of the drive in Disk Utility is verified.
    I've taken this Mac back once to be repaired for this problem but they found nothing wrong with it. It is a very intermittent problem though and only occurs rarely. A small, but annoying niggle. I am also using a KVM switch but I didn't have this problem with my last Mac, another mini, connected to the same KVM.

  • NetworkManager crashes/segfault - sometimes

    Sometimes at startup networkmanager crashes. Usually it's fine - it seems to be random and I cannot intentionally duplicate it. My system is 64-bit and fully updated. Other than this - no issues - no failed services or errors - other than this when it occurs. Here's what I see in the logs when it happens:
    systemd-coredump[938]: Process 484 (NetworkManager) of user 0 dumped core.
    -- Subject: Process 484 (NetworkManager) dumped core
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: man:core(5)
    -- Process 484 (NetworkManager) crashed and dumped core.
    -- This usually indicates a programming error in the crashing program and
    -- should be reported to its vendor as a bug.
    [ 46.003130] NetworkManager[484]: segfault at 2 ip 00000000004871b2 sp 00007ffffabcb750 error 4 in NetworkManager[400000+109000]
    My setup is luks on lvm with XFCE. I have ipv6 disabled in the kernel (ipv6.disable=1) and have added the following entries to my dhcpcd conf file:
    noipv6rs
    noipv6
    noarp
    I'm pretty sure that I've got all the necessary components installed because it usually works fine: networkmanager networkmanager-openvpn network-manager-applet xfce4-notifyd
    I do connect to openvpn when I connect to the wireless network but switching off the automatic connection to the vpn doesn't prevent networkmanager's problems.
    If I try to restart networkmanager (systemctl restart NetworkManager.service) I get the following error messages:
    dhcpcd already running on pid 589 (/run/dhcpcd-wlp3s0.pid)
    I run Arch on 2 laptops and a pc and they each suffer from this - but again it's intermittent.
    Any ideas, suggestions would be great. At the moment I can resolve it only by rebooting.
    Thanks,
    Jules

    Kinokoio wrote:Your setup is not a problem, so the mistake may be in nm. Try filing a bug so it gets a deep research.
    Before filing a bug report without any real info for the devs I would try to debug it at least a bit myself.
    See the following links for more information:
    https://wiki.gnome.org/Projects/Network … /Debugging
    http://www.freedesktop.org/wiki/Softwar … Debugging/ (It's about ModemManager but you'll get the hang of it)
    Especially I would try to alter the service file for NetworkManager to include the --log-level= parameter.
    Further, playing around with gdb might get some insight.
    See links:
    https://wiki.archlinux.org/index.php/Core_dump
    http://www.randombugs.com/linux/core-dumps-linux.html
    https://mytechrants.wordpress.com/2009/ … using-gdb/
    http://www.cs.cmu.edu/~gilpin/tutorial/
    http://stackoverflow.com/questions/8305 … -dump-file
    Maybe downgrading is an option too.
    It's a bit of work to do, but I don't think filing a bug report at this state is going to help.
    Last edited by MK13 (2015-01-12 08:33:42)

  • Mac mini occasionally boots in startup volume screen (SOLVED).

    Here is my original message from March 08:
    "I've had this problem since I've had my Mac mini (about a year now). Sometimes the startup volume screen appears despite not having any other Hard Drives connected apart from the boot drive (which is the internal Hard drive) and despite not pressing any keyboard keys on startup.
    I am using 10.5.2 with the latest mini firmware and am unable to think what could be causing this? I have selected my main hard-drive in the startup disk preferences and have no permissions/hard drive problems (so says disk utility) but the problem persists. It's a minor annoyance but one I would welcome any help with."
    http://discussions.apple.com/thread.jspa?threadID=1433640&tstart=0
    Because the original post is archived I thought I would post the answer in a new thread. The answer to this problem was to replace the network cable connecting my Mac mini to my Apple router.
    I think the previous faulty cable was causing the mini to do a phantom network boot and that's why the startup volume screen came up from time to time.
    Since, the cable change no more startup volume screen problem.
    Phew, this has been bugging me ever since I bought my mini. It's nice to know sometimes it's the simple answers that work

    I have a similar problem. Whenever I startup my Mac Mini, an icon of the "Macintosh HD" appears in the middle of the screen. It doesn't go away until I click on it. After that, every thing works fine... until I use Safari. If I use Safari long enough, some type of glitch occurs that doesn't let me type correctly; Safari will stop working as it should be, and every time i try to type, some really weird symbols appear, like these ones: ßêÄ©¶¢. The only option I have left is to restart the computer, over, and over, and over again. Please help!!!!

  • OC4J containers sometimes don't stop/start?

    Occasionally when I do opmnctl stopall or startall, an OC4J container will fail to start or stop. Sometimes I get the "forcibly shutting down..." message from opmnctl. Sometimes it just sits there. Sometimes it shuts down but a 'ps -ef | grep oracle' shows some hanging processes.
    Likewise sometimes on startup a component just won't start. It'll 'init' for a while, then drop back down to status = 'NONE'. But, I can go into OEM ASC and start it up there and it'll start right up!
    This is not consistent at all. This is 9.0.4 (10g).
    Any ideas? Anyone experience this sort of weirdness? So far it's not terribly confidence-inspiring.

    Depending on the environment, it may be necessary
    to modify the start, stop, and/or restart timeouts
    for components, as configured in $OH/opmn/conf/opmn.xml
    These elements, if not specified in opmn.xml for
    a component default to the following:
    start: 120 seconds
    stop: 60 seconds
    restart: 180 seconds
    The opmnctl startall/stopall commands result in the
    simultaneous start/stop of all configured components.
    If the machine is sufficiently powerful, this will
    result in all components completing the state
    transistion faster than if the components were
    started/stopped serially. Component initialization
    and shutdown can be resource intensive. Contention
    between components starting/stopping at the same time
    can lead to longer stop/start times compared to the
    time it takes to start/stop a component by itself.
    The different in behavior between OEM and opmnctl
    might be explained if a smaller set of components
    is being started/stopped by the OEM operation than
    the opmnctl operation. Another possibility is that
    the OEM operation is resulting in multiple, serial
    requests to start individual components instead of
    starting everything in parallel.
    How might this be investigated? $OH/opmn/logs/ipm.log
    now prints with timestamp command begin/end and info
    about the processes started/stopped as part of the
    command. You can see something like this:
    20:00:00 Request 4 Started. Command: start
    20:00:00 Starting Process: OC4J~home~default_is...
    20:00:00 Starting Process: HTTP_Server~HTTP_Ser...
    20:00:11 Process Alive: HTTP_Server~HTTP_Server...
    20:00:32 Process Alive: OC4J~home~default_islan...
    20:00:32 Request 4 Completed. Command: start
    This example shows a start command that resulted
    in the simultaneous start of HTTP_Server and an
    OC4J. HTTP_Server took 11 seconds to start,
    OC4J took 32 seconds to start.
    Compare the ipm.log output generated from the opmnctl
    and OEM operations. opmnctl and OEM use the same
    protocols to interact with opmn to perform process
    control requests.
    My guess is that the opmnctl operation is doing more
    work in parallel and is overloading CPU resulting
    in longer delays. I would be interested in seeing
    ipm.log output (at default log level) from the
    startall/stopall operation and a brief machine
    description.

  • PCI Device error on bootup/ and startup

    I have a Toshiba Satellite U405D-S2850 running on Windows Vista Home premium; 32-bit. 
    Everytime I turn on my laptop on bootup I hear two VERY loud beeping sounds and a black screen appears which shows the following text:
    Phoenix Trusted (tm) NB
    Copyright 1985-2008 Phoenix Technologies Ltd. 
    All Rights Reserved 
    CPU =AMD Turion (tm) X2 Duel-Core Mobile RM-70
    Video BIOS shadowed
    ATAPI CD-ROM: HL-DT-ST DVDRAM GSA-U20N
    Fixed Disk 0: Hitachi HTS542525K9SA00
    Mouse initialized
    ERROR
    Resource Conflict - PCI Serial Bus Controller in slot 08
    Bus: 09, Device: 01, Function: 00
    ERROR
    Resource Conflict - PCI inslot 08
    Bus: 09, Device: 01, Function: 02
    ERROR
    Resource Conflict - PCI in slot 08
    Bus: 09, Device: 01, Function: 03
    Press <F1> to Resume, <F2> to Setup
    When I press F1 my laptop just continues booting with no problems and when I press F2 it just goes to bios. And sometimes on startup a window opens saying it needs to install a PCI device, I've pressed install but in the end it always ends up saying failed to install cause of unkown PCI Device. Other than those two problems/messages my laptop runs fine. But still I'd like to fix this problem just in case it might turn into a bigger problem in the future. I hope someone can help me out. I'm not really computer literate. Thanks

    Hi, I was wondering if anyone has replied to you about this? I have the same problem and even though the computer still works, its just really annoying to hear the two loud beeps. Especially when I'm studying in a very quiet library!

  • Menu bar icons slow to appear on startup

    Of late, when I boot up my MBP, everything comes up quickly except the menu bar icons, which take forever to show up. After that, everything works fine. The only icons that need to load are Airport status, battery status, bluetooth, and date/time. The machine's not usable til these icons appear. They used to show up really fast. Sometimes on startup, they appear, then disappear, then reappear after about 45 seconds. This is not correct startup behavior. Anyone else experience this? It's only an annoyance, but it's driving me crazy.

    kiddredd
    Try deleting the com.apple.systemuiserver.plist file from the home / library / preferences folder. This will return things to the factory default.
    Regards
    TD

  • G4 powerbook shuts itself down on startup

    hello, my g4 1.33ghz powerbook has been an absolute workhorse for the past 5 years without 1 single glitch... until now. I have been getting kernel panics (sometimes) on startup, 2 different types (corrupt stack) and (invalid pmap). At first, after about 3 attempts my powerbook would startup and run fine. When I got it to boot up I would run the disk utility to attempt to repair the hard drive, it would find an error but would be unable to fix it. I tried over and over to no avail. After a few hours of this, the laptop stopped booting up at all, it wont even start to load OSX, just freezes on the grey screen and turns itself off.
    I have 2 powerbooks, and done a lot of reading on this matter. I have reset the pram, changed the ram around with ram i know that works (from my other powerbook) in several configurations (ie different ram slots) and tried booting from the factory disc (computer still freezes), tried to boot from tech tool delux disc (freezes the same as booting from factory disc). I have hooked up via firewire to my working powerbook and have run disc utility, and it finds a disc error but cannot fix it.
    I am 3 1/2 hours drive from the nearest mac service centre so I am trying to diagnose as best i can prior to going on a long return trip. I am thinking along the lines of a dead hard drive. All my data is backed up on external hard drives, so this would be no big deal. Does any one have any ideas? Or have experienced the same/similar problems and managed to fix them? I have done some research on replacing the hard drive and this seems like a relatively easy process, and the drives themselves seem pretty cheap so maybe something I could address myself? Any help on this matter greatly appreciated.

    Welcome to Apple Discussions!
    Notebook hard drives have an average useful life of 3-5 years, so if yours is the original drive, it is likely dying or dead. What does Disk Utility have to say about the S.M.A.R.T. status? Finding errors that cannot be repaired is not a good sign, and often an indication of a failing hard drive.
    However, you should be able to boot from a disc, even if the hard drive is not working. I am concerned that the freezing when booted from a disc may indicate some other problem.
    Are you able to boot and run the extended version of the Apple Hardware Test? If so, that might give a clue as to what is happening in the form of an error code.
    In my opinion, your hard drive has failed. But there may be some other problem as well.
    One thing to try would be to purchase a replacement hard drive along with a FireWire enclosure for it. You could try installing the OS on the external and see if it would run the PB. If the PB will run from the external, then you could simply remove the drive from the external and install it in the PB. If the PB proves to be beyond repair, you will still have an external firewire drive, which is always useful.
    Good places to get drives are OWC and Newegg--both often have specials. And I like OWC's Mercury on the Go firewire enclosures with the reliable Oxford 911+ chipset.
    You know about ifixit, right?
    http://www.ifixit.com/
    I think the "invalid pmap" might mean "invalid partition map", but I don't know what "corrupt stack" might refer to. No doubt someone else knows and can shed some light. It would probably be good to gather some further insights about the freezing before purchasing anything.
    Good luck!

Maybe you are looking for

  • IView is not being displayed in full page

    I created one iView, added it into a page. I set the layout as 1 Column Full width. My view is not being displayed in entire window. What kind of property, I should set in the page.

  • Printing a report

    I'd like to open this discussion because i did not find much information on the net, and maybe someone has already tried out this. I'm facing the problem of printing a report with my application and I'm having problem figuring out how to insert into

  • Help! I can't sign onto Adobe from my Potoshop Elements 9. I get a message saying Error 400

    This popup says that Adobe Services are not available at this time, try again later. I've tried later, and later, and later..... Anyone know what's up with this? I can sign into my account from this sight just fine...

  • Design thoughs CTAS vs TRUNCATE / INSERT

    Would like to hear your thoughts on the speed / other pro's and con's of Create Table As Select * from table and truncate table insert into /*+ append */ select * from table; Consider at present we have force logging on.

  • Automate workflow bounce

    Hi all, Need your help again!! Since bouncing WF is a regular and monotonous job, i would like to automate it. May be a shell script by running which Workflow Agent Listener Service, Workflow Mailer Service, Workflow Document Web Services Service wil