K7N2 - Power on, Immediate Shutdown Problem!

I recently purchased a MSI K7N2 Delta Series motherboard and I am having problems with it. When I press the power button to turn the system on, the computer powers up and immediately shuts off after about 2-3 seconds. I have a AMD XP 3200 processor and Crucial 512mb of ram.
I have put a new processor and new ram in the motherboard, however it still does not work.
I have tried everything from clearing CMOS to booting the system with only the ram, HD, and processor however, I always get the same results. I have also tried using another brand new powersupply and it doesn't help either.
Can you please further assist me with this matter? Thank you.

Call MSI in City of Industry for an RMA.
MSI™ Computer Corp.
901 Canada Court, City of Industry,
CA 91748
URL: http://www.msicomputer.com
TEL: 1-626-913-0828
FAX: 1-626-913-0818
Then I would consider making a proper investment in a good power supply Comp USA's PSU's are crap, and I wouldn't be surprised if it had something to do with your problems. Look at it this way, if your PSU is faulty or of poor quality, it can take a dump on you and then wipe its bum with the rest of your system
Protect your investment is my motto, I would rather suffer the expense than to have the insecurity in troubleshooting a problem and worrying if it could damage my components, it's just not something I am willing to live with considering what I have seen, heard, read and experienced.
Good luck

Similar Messages

Troubleshoot recent overheating + immediate shutdowns (hard/software?)

Since last Friday, I've been experiencing frequent, instant shutdowns due to overheating. I've had these occur before, but generally when running intensive computations in R. I'd initiate a script at bedtime, and wake up to find my computer off (shut down in the night). I learned to put a small book under it, run a fan next to it, or literally place it on it's side, resting on the non-fan edge and the lid to expose the whole bottom to "breathe." Recently, however, I have incessant, unexpected, immediate shutdowns during "normal use" (terminal, browser with, say, 4-10 non-video-playing tabs open), or even just updating with pacman.
Unfortunately, use of some proprietary software along with needing some IE-specific sites at work had me in Windows 7 for ~1.5 weeks non-stop. This is really unusual for me, and I prefer to live in Arch as much as possible. Because of this, I didn't get to notice if this would have gradually increased in frequency or started abruptly. The behavior is drastically and noticeably different than anything I've experienced, completely kills the use of Linux for me, and I'd really like to identify if this is something to do with software, or if I'm experiencing a hardware failure of some sort (loose thermal gel?). I did a mess of trials this weekend, with results below. Thanks for any input or suggestions.
System details
- HP 8540w workstation
- Intel i7 Q720 (4 physical cores, 8 virtual)
- Nvidia Quadro FX 1800M
- Using nvidia (334.21-4), nvidia-utils (334.21-4), nvidia-libgl (334.21-7)
- Relevant BIOS options (as far as I can tell):
--- Multi-core: turns off all physical cores other than the first
--- Intel HT Technology: hyperthreading support (appears to turn off all virtual/hyperthreaded cores)
--- Virtualization (unsure if relevant, but affects dmesg output for kvm abilities)
$ uname -a
Linux bigBang 3.14.0-5-ARCH #1 SMP PREEMPT Fri Apr 11 21:02:33 CEST 2014 x86_64 GNU/Linux
$ sudo cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ondemand # same for all other cpus, 1-7
I have acpi installed, but not acpid, laptop tools, cpupower, or others mentioned in the power management or CPU frequency scaling Wiki articles.
Edit: Oops! I caught that I actually did have cpupower installed, from way back in 2012, and removed it last night. I don't recall ever setting it up, and issuing `locate cpupower` now that it's gone doesn't get any hits, so I'm thinking this means I never created a config file for it (which would have yielded, I think, a file.pacsave upon removal). Sorry for the mixup!
Assume everything else is "stock" (in other words, no kernel options appended, etc.). This is pretty much a "vanilla" Arch system other than the applications I've installed. Feel free to ask follow up questions if I've missed something relevant.
System messages
Here are examples of the errors I'm seeing:
$ dmesg | grep -i mce
[ 0.040954] mce: CPU supports 9 MCE banks
[18912.069281] mce: [Hardware Error]: Machine check events logged
[19662.531507] mce: [Hardware Error]: Machine check events logged
[20112.808818] mce: [Hardware Error]: Machine check events logged
$ dmesg | grep -i temper
[ 367.990859] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)
[ 367.990862] CPU7: Core temperature above threshold, cpu clock throttled (total events = 1)
[ 367.991919] CPU6: Core temperature/speed normal
[ 367.991922] CPU7: Core temperature/speed normal
[ 668.175622] CPU6: Core temperature above threshold, cpu clock throttled (total events = 508)
[ 668.175623] CPU7: Core temperature above threshold, cpu clock throttled (total events = 508)
[ 668.176683] CPU6: Core temperature/speed normal
[ 668.176685] CPU7: Core temperature/speed normal
Here are my limits, per lm_sensors:
$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +57.0°C (high = +84.0°C, crit = +100.0°C)
Core 1: +57.0°C (high = +84.0°C, crit = +100.0°C)
Core 2: +57.0°C (high = +84.0°C, crit = +100.0°C)
Core 3: +57.0°C (high = +84.0°C, crit = +100.0°C)
I installed the mcelog package, which shows messages like this:
Hardware event. This is not a software error.
Apr 14 21:36:50 bigBang mcelog[10019]: MCE 0
Apr 14 21:36:50 bigBang mcelog[10019]: CPU 5 THERMAL EVENT TSC 1b184fe88d88
Apr 14 21:36:50 bigBang mcelog[10019]: TIME 1397511379 Mon Apr 14 16:36:19 2014
Apr 14 21:36:50 bigBang mcelog[10019]: Processor 5 heated above trip temperature. Throttling enabled.
Apr 14 21:36:50 bigBang mcelog[10019]: Please check your system cooling. Performance will be impacted
Apr 14 21:36:50 bigBang mcelog[10019]: STATUS 880003c3 MCGSTATUS 0
Apr 14 21:36:50 bigBang mcelog[10019]: MCGCAP 1c09 APICID 5 SOCKETID 0
Apr 14 21:36:50 bigBang mcelog[10019]: CPUID Vendor Intel Family 6 Model 30
Apr 14 21:36:50 bigBang mcelog[10019]: Hardware event. This is not a software error.
Apr 14 21:36:50 bigBang mcelog[10019]: MCE 1
Apr 14 21:36:50 bigBang mcelog[10019]: CPU 4 THERMAL EVENT TSC 1b184fe8a5da
Apr 14 21:36:50 bigBang mcelog[10019]: TIME 1397511379 Mon Apr 14 16:36:19 2014
Apr 14 21:36:50 bigBang mcelog[10019]: Processor 4 heated above trip temperature. Throttling enabled.
Apr 14 21:36:50 bigBang mcelog[10019]: Please check your system cooling. Performance will be impacted
Apr 14 21:36:50 bigBang mcelog[10019]: STATUS 880003c3 MCGSTATUS 0
Apr 14 21:36:50 bigBang mcelog[10019]: MCGCAP 1c09 APICID 4 SOCKETID 0
Apr 14 21:36:50 bigBang mcelog[10019]: CPUID Vendor Intel Family 6 Model 30
Apr 14 21:36:50 bigBang mcelog[10019]: Hardware event. This is not a software error.
Method
In updating my AUR-built packages, I got repeated shutdowns when trying to build pandoc-static, a pretty compiling-heavy package. I googled around quite a bit about thermal events, with nothing conclusively sticking out as the solution. Honestly, it reduced to trying pcie_aspm=0 or pcie_aspm=force -- that's really about all I could find! I thought I would try various things and log the temperature and frequency while trying to build pandoc-static. Here was my final summary of trials conducted:
Key:
- bios virt: "Virtualization Technology" turned on in BIOS?
- bios multi: "Multi-Core" turned on in BIOS?
- intel ht: "Intel HT Technology" turned on in BIOS?
- X: started X with `startx` or run from TTY1?
- cores: which CPUs were active (as per the scheme in /sys/devices/system/cpu/cpu*)?
- success: did pandoc-static build successfully (1), or did the machine hard kill itself (0)?
| log id | kernel | pcie_aspm | bios virt | bios multi | intel ht | X? | cores | success? | note |
|--------+----------+-----------------+-----------+------------+----------+----+---------------+----------+-----------------------|
| 4 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | [0-5] | 1 | |
| 5 | 3.14.0-5 | pcie_aspm=0 | 1 | 1 | 1 | 1 | all | 0 | |
| 6 | 3.14.0-5 | pcie_aspm=force | 1 | 1 | 1 | 1 | all | 0 | |
| 7 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | all | 1 | |
| 8 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | 0, 2, 4, 6 | 0 | |
| 9 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | 0, 1, 3, 5, 7 | 0 | can't turn off core 0 |
| 10 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | [0-5] | 1 | replicate (4) |
| 11 | 3.10.36 | default | 1 | 1 | 1 | 1 | all | 0 | |
| 12 | 3.14.0-5 | default | 1 | 1 | 1 | 0 | all | 0 | |
| 13 | 3.14.0-5 | default | 0 | 1 | 1 | 1 | all | 0 | |
| 14 | 3.14.0-5 | default | 0 | 0 | 1 | 1 | 0-1 | 1 | |
| 15 | 3.14.0-5 | default | 0 | 1 | 0 | 1 | 0-3 | 0 | |
| 16 | 3.10.36 | default | 1 | 1 | 1 | 0 | all | 0 | |
| 17 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | all | 0 | |
| 18 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | [0-5] | 1 | replicate (4) |
For instances where only certain cores were enabled, the following method was used:
# echo 0 > /sys/devices/system/cpu/cpu6/online
The effect was verified in the output of dmesg for each core:
[ 2024.174235] kvm: disabling virtualization on CPU6
[ 2030.187053] kvm: disabling virtualization on CPU7
I tried a couple without X to rule out an Nvidia issue, as I also have a recent issue of closing my lid not suspending anymore. This is apparently an Nvidia issue, so I thought I'd at least try to rule it out. I threw in the LTS kernel just to see if I noticed any differences (I didn't).
In each case, I used the following procedure:
- Fresh boot
- Open one instance of urxvt with three tabs (or three TTYs if running one of the two non-X trials)
- run a cpu-logging script as root in one tab, a dmesg logging script from a regular user tab, and `yaourt pandoc-static` from a third tab
- if the machine hard killed, move on. If not, stop the logger, reboot, and start over (applying any BIOS changes when necessary)
All trials except 16, 17, and 18 were run at my house in the dining room, with the laptop resting on a small book (not obscuring the fan ports underneath). The last three were run today at work, and I put a similarly sized book under the laptop to try and replicate conditions reasonably well.
I wrote a kludgy script (I'm no bash guy...) to collect the data in csv format. It's called by another script (not shown) that runs a continuous while loop every 10 seconds.
#!/bin/sh
temp0=`sensors | grep "Core 0" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
temp1=`sensors | grep "Core 1" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
temp2=`sensors | grep "Core 2" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
temp3=`sensors | grep "Core 3" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
for i in 0 1 2 3 4 5 6 7
do
eval cpu$i=`cat /sys/devices/system/cpu/cpu$i/cpufreq/cpuinfo_cur_freq`
done
time=`date +%H:%M:%S`
top=`ps aux | awk '{print $11, $3}' | sort -k2rn | head -n 3`
top=`echo $top | sed s/" "/", "/g`
echo "$time, $temp0, $temp1, $temp2, $temp3, $cpu0, $cpu1, $cpu2, $cpu3, $cpu4, $cpu5, $cpu6, $cpu7, $top" >> /home/jwhendy/temp-freq.log
I also output the results of `dmesg | grep -i mce` and `dmesg | grep -i temper` to two separate files every 10 seconds.
Results
The result of most interest came when I noticed that it was always cpu6 and cpu7 that showed up in dmesg logs. I found the trick above about disabling specific cores, and decided to try it... the build succeeded! I replicated this effect three different times, which I find significant given that almost nothing else succeeded.
I used R and the ggplot2 package to plot the results, and here are two replicates of "default" Arch 3.14.0 (no changes) vs. the three runs in which I've disabled cores 6-7:
Note the absence of the rapid spikes > 90C, which are entirely the blue lines in the left two plots. That color is for the "Core 3" temperature reported by lm_sensors (fourth core), which I take it is responsible for cpu6 and cpu7. Subjectively, I noticed that the laptop ran with much lower fan speeds, they kicked in later in the build, and simply ran less with cpu6/7 off. Frequencies appear to jump around with both, showing a pretty even spread of them cycling. The plots don't make it very clear, but the first default run succeeded, while the second one hard shutdown. Again, all three with cpu6/7 off succeeded.
Discussion
Case closed? Is this definitely a hardware issue? I'm still not sure, and that's where I'd like some assistance. Having replicated three successes with cpu6 and cpu7 off, I felt pretty confident. But from my current boot (with cpu6/7 off), I checked dmesg after running rsync for a couple hours catching up on backups!
[18661.079071] CPU4: Core temperature above threshold, cpu clock throttled (total events = 1)
[18661.079072] CPU5: Core temperature above threshold, cpu clock throttled (total events = 1)
[18661.080133] CPU4: Core temperature/speed normal
[18661.080135] CPU5: Core temperature/speed normal
[19598.570458] CPU5: Core temperature above threshold, cpu clock throttled (total events = 182)
[19598.570459] CPU4: Core temperature above threshold, cpu clock throttled (total events = 182)
[19598.571517] CPU4: Core temperature/speed normal
[19598.571520] CPU5: Core temperature/speed normal
[20015.016963] CPU4: Core temperature above threshold, cpu clock throttled (total events = 221)
[20015.016965] CPU5: Core temperature above threshold, cpu clock throttled (total events = 221)
[20015.019037] CPU4: Core temperature/speed normal
[20015.019040] CPU5: Core temperature/speed normal
Also, note that run #15 above (disabling hyperthreading in BIOS) turns off cpu4-7, however the dmesg temp logs show that cpu3 was reporting temperature overages and that trial resulted in a hard shutdown. I'm not confident in how the system numbers the cpus (cpu0 and cpu1 are the hyperthreads for the first physical core? Is this always the case?). If numbering is consistent and this means that cpu6 and cpu7 are both hyperthreads of two different cores, this is also perplexing, since runs #8 and #9 turned off odd and even (respectively) cores yet saw no improvement. Both reported one of the suspect cpus (6 for even run, 7 for the odd), and both hard killed, #8 before it could even log any high spikes.
- Here's a plot of those two runs
There's also the issue that this never happens on Windows, or at least the forced shutdowns don't occur. Perhaps there are warnings or logs somewhere showing the same issue, but it's controlling the issue somehow. I'd love suggestions to check; if there aren't any errors reported, that shifts the evidence back to a potential software issue.
Lastly, mcelog says flat out "This is not a software error." Now, I hear that... but I don't understand why changing which hyperthreads are online should change which cores overheat (always the highest numbered one). Or, say, could disabling those cores just disable the associated temperature sensor and it's still just as hot in that area, but it's not being measured/reported?
For now, turning off cpu6 and cpu7 at least gives me a system that doesn't die on me with every action, so Arch remains usable. I've read a bunch of posts on this that frankly aren't much help. They range in content from "One cpu is ~10C higher than others" (to which people say, "Don't worry about it") to advice to simply go in an manually change the cpu temperature threshold values (seems like a horrible idea to me), to aspm fiddling (which seems like it was supposedly fixed in Linux 3.0+ if not before), and changing governors (I'm on ondemand, not performance, which seems reasonable).
I typed a lot above, and that's because I would like the best chance I have to know what this is related to. Alright, 'nuff of the problem. Onto the solution. Many thanks for reading, and any assistance/suggestions you can provide.
Last edited by jwhendy (2014-04-15 16:08:56)

@ewaller: thanks for the feedback! Yeah, this was one of my more obsessive ones for sure. I admit that data collection and analysis is both a part of my job, and a hobby
Re. Windows: subjectively, I think Windows runs with the fan much less (but always has, not a recent thing). It's also much slower and far less responsive (issue something like alt+tab to change windows and wait 1-3 full seconds for it to catch up). I could run something intensive in Win7 and check the logs to see if anything similar shows up (could Win7 just be controlling it somehow?). What surprises me is that Arch is catching that the cpus are over critical and throttling them, but they seem to spike so fast from ~80C to 100C that it can't do anything but hard kill.
Re. hardware: thanks for your take. I plan to take this apart and brush/blow any dust out, so I'll take a look while I'm in there for anything obviously loose or weird.
Re. what's changed: I've wondered that myself and am just drawing a blank. I tried to check for over-temp reports in journalctl, but unfortunately, have SystemMaxUse=250M in /etc/systemd/journald.conf. It appears that all of my experiments this weekend purged older entries, so journalctl starts at 2014-04-12 -- bummer. Still, I haven't changed anything major that I'm aware of. Just booted up, started doing normal stuff (updating packages, chromium, etc.), and I noticed the fan ramp up like crazy. Then that horrid "peeew" sound when the computer kills itself. Thought it was a fluke, but happened again and again.
Re. pacman logs: here's my pacman log for what I think is a relevant period. Prior to 2014-04-09, the previous entry was 2014-03-31 (that period was the living-in-Windows time I mentioned). I omitted some more recent entries since the problem was already present as of Apr 09-10, and a majority of more recent entries are related to trying to get nouveau to work with acceleration (lots of installing/un-installing nvidia/nouveau to troubleshoot that issue -- in progress!).
[2014-04-09 17:48] [PACMAN] Running 'pacman -Syu'
[2014-04-09 17:48] [PACMAN] synchronizing package lists
[2014-04-09 17:48] [PACMAN] starting full system upgrade
[2014-04-09 17:54] [PACMAN] upgraded apr-util (1.5.3-3 -> 1.5.3-4)
[2014-04-09 17:54] [PACMAN] upgraded readline (6.3-3 -> 6.3.003-2)
[2014-04-09 17:54] [PACMAN] upgraded bash (4.3-3 -> 4.3.008-2)
[2014-04-09 17:54] [PACMAN] upgraded boost-libs (1.55.0-4 -> 1.55.0-5)
[2014-04-09 17:54] [PACMAN] upgraded openssl (1.0.1.f-2 -> 1.0.1.g-1)
[2014-04-09 17:54] [PACMAN] upgraded ca-certificates (20140223-2 -> 20140325-1)
[2014-04-09 17:54] [PACMAN] upgraded cpupower (3.13-2 -> 3.14-1)
[2014-04-09 17:54] [PACMAN] upgraded cups-filters (1.0.50-1 -> 1.0.52-1)
[2014-04-09 17:54] [PACMAN] installed libavc1394 (0.5.4-2)
[2014-04-09 17:54] [PACMAN] installed libiec61883 (1.2.0-4)
[2014-04-09 17:54] [PACMAN] installed gstreamer0.10-good-plugins (0.10.31-5)
[2014-04-09 17:54] [PACMAN] upgraded farstream-0.1 (0.1.2-3 -> 0.1.2-4)
[2014-04-09 17:54] [PACMAN] upgraded fftw (3.3.3-2 -> 3.3.4-1)
[2014-04-09 17:54] [PACMAN] upgraded sqlite (3.8.4.2-1 -> 3.8.4.3-1)
[2014-04-09 17:54] [PACMAN] upgraded nss (3.15.5-2 -> 3.16-1)
[2014-04-09 17:54] [PACMAN] upgraded flashplugin (11.2.202.346-1 -> 11.2.202.350-1)
[2014-04-09 17:54] [PACMAN] upgraded ghostscript (9.10-3 -> 9.14-1)
[2014-04-09 17:54] [PACMAN] upgraded gnutls (3.2.12.1-1 -> 3.2.13-1)
[2014-04-09 17:54] [PACMAN] upgraded groff (1.22.2-5 -> 1.22.2-6)
[2014-04-09 17:54] [PACMAN] upgraded hplip (3.14.3-2 -> 3.14.4-1)
[2014-04-09 17:55] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-04-09 17:55] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Starting build: 3.13.8-1-ARCH
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Starting build: 3.13.8-1-ARCH
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-04-09 17:55] [PACMAN] upgraded linux (3.13.7-1 -> 3.13.8-1)
[2014-04-09 17:55] [PACMAN] upgraded linux-headers (3.13.7-1 -> 3.13.8-1)
[2014-04-09 17:55] [PACMAN] upgraded man-pages (3.63-1 -> 3.64-1)
[2014-04-09 17:55] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2014-04-09 17:55] [PACMAN] upgraded pacman-mirrorlist (20140107-1 -> 20140405-1)
[2014-04-09 17:55] [PACMAN] upgraded python2-numpy (1.8.0-3 -> 1.8.1-1)
[2014-04-09 17:55] [PACMAN] upgraded r (3.0.2-2 -> 3.0.3-1)
[2014-04-09 17:55] [PACMAN] upgraded xorg-xauth (1.0.8-1 -> 1.0.9-1)
[2014-04-09 17:55] [PACMAN] upgraded yajl (2.0.4-2 -> 2.1.0-1)
[2014-04-09 18:03] [PACMAN] Running 'pacman --color auto -Sy'
[2014-04-09 18:03] [PACMAN] synchronizing package lists
[2014-04-10 13:45] [PACMAN] Running 'pacman --color auto -Sy'
[2014-04-10 13:45] [PACMAN] synchronizing package lists
[2014-04-10 13:45] [PACMAN] Running 'pacman -Syu'
[2014-04-10 13:45] [PACMAN] synchronizing package lists
[2014-04-10 13:45] [PACMAN] starting full system upgrade
[2014-04-10 13:46] [PACMAN] upgraded kmod (16-1 -> 17-1)
[2014-04-10 13:46] [PACMAN] upgraded libsystemd (212-1 -> 212-2)
[2014-04-10 13:46] [PACMAN] upgraded coreutils (8.22-3 -> 8.22-4)
[2014-04-10 13:46] [PACMAN] upgraded libutil-linux (2.24.1-4 -> 2.24.1-6)
[2014-04-10 13:46] [PACMAN] upgraded util-linux (2.24.1-4 -> 2.24.1-6)
[2014-04-10 13:46] [PACMAN] upgraded systemd (212-1 -> 212-2)
[2014-04-10 13:46] [PACMAN] upgraded chromium (33.0.1750.152-1 -> 34.0.1847.116-1)
[2014-04-10 13:46] [PACMAN] upgraded x265 (0.8-2 -> 0.9-1)
[2014-04-10 13:46] [PACMAN] upgraded ffmpeg (1:2.2-2 -> 1:2.2-3)
[2014-04-10 13:47] [PACMAN] upgraded git (1.9.1-1 -> 1.9.2-1)
[2014-04-10 13:47] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-04-10 13:47] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Starting build: 3.14.0-4-ARCH
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Starting build: 3.14.0-4-ARCH
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2014-04-10 13:48] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-04-10 13:48] [PACMAN] upgraded linux (3.13.8-1 -> 3.14-4)
[2014-04-10 13:48] [PACMAN] upgraded linux-headers (3.13.8-1 -> 3.14-4)
[2014-04-10 13:48] [PACMAN] upgraded lirc-utils (1:0.9.0-70 -> 1:0.9.0-71)
[2014-04-10 13:48] [PACMAN] upgraded nvidia (334.21-2 -> 334.21-4)
[2014-04-10 13:48] [PACMAN] upgraded systemd-sysvcompat (212-1 -> 212-2)
[2014-04-10 13:51] [PACMAN] Running 'pacman -Syu'
[2014-04-10 13:51] [PACMAN] synchronizing package lists
[2014-04-10 13:51] [PACMAN] starting full system upgrade
[2014-04-10 13:51] [PACMAN] Running 'pacman -Sc'
[2014-04-10 14:16] [PACMAN] Running 'pacman --color auto -Sy'
[2014-04-10 14:16] [PACMAN] synchronizing package lists
[2014-04-10 14:21] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.K0M/chromium-libpdf-1:34.0.1847.116-1-x86_64.pkg.tar.xz'
[2014-04-10 14:21] [PACMAN] upgraded chromium-libpdf (1:33.0.1750.149-1 -> 1:34.0.1847.116-1)
[2014-04-10 14:26] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.R9f/dropbox-2.6.25-1-x86_64.pkg.tar.xz'
[2014-04-10 14:26] [PACMAN] upgraded dropbox (2.6.13-1 -> 2.6.25-1)
[2014-04-10 15:41] [PACMAN] Running 'pacman -Syu'
[2014-04-10 15:41] [PACMAN] synchronizing package lists
[2014-04-10 15:41] [PACMAN] Running 'pacman --color auto -Sy'
[2014-04-10 15:41] [PACMAN] synchronizing package lists
[2014-04-10 15:43] [PACMAN] Running 'pacman --color auto -S -u'
[2014-04-10 15:43] [PACMAN] starting full system upgrade
[2014-04-10 15:43] [PACMAN] upgraded libjpeg-turbo (1.3.0-4 -> 1.3.1-1)
[2014-04-10 15:43] [PACMAN] upgraded mpd (0.18.9-1 -> 0.18.10-1)
[2014-04-10 15:43] [PACMAN] upgraded python2-urwid (1.2.0-2 -> 1.2.1-1)
[2014-04-10 15:43] [PACMAN] Running 'pacman --color auto -S --asdeps --needed extra/itstool'
[2014-04-10 15:44] [PACMAN] installed itstool (2.0.2-1)
[2014-04-10 15:53] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.Ikd/evince-gtk-3.12.0-1-x86_64.pkg.tar.xz'
[2014-04-10 15:53] [PACMAN] upgraded evince-gtk (3.10.3-1 -> 3.12.0-1)
[2014-04-10 16:08] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.7Bs/jdk-8u0-1-x86_64.pkg.tar.xz'
[2014-04-10 16:11] [PACMAN] Running 'pacman -S lm_sensors'
[2014-04-10 16:12] [ALPM-SCRIPTLET] ==> Updating desktop MIME database...
[2014-04-10 16:12] [ALPM-SCRIPTLET] ==> Updating MIME database...
[2014-04-10 16:12] [ALPM-SCRIPTLET] ==> Updating icon cache...
[2014-04-10 16:12] [PACMAN] upgraded jdk (7.51-1 -> 8u0-1)
[2014-04-10 16:12] [PACMAN] Running 'pacman --color auto -S --asdeps --needed extra/cabal-install extra/ghc community/alex community/happy'
[2014-04-10 16:13] [PACMAN] installed cabal-install (1.18.0.2-1)
[2014-04-10 16:13] [PACMAN] installed ghc (7.6.3-1)
[2014-04-10 16:13] [PACMAN] installed alex (3.1.3-1)
[2014-04-10 16:13] [PACMAN] installed happy (1.19.3-1)
[2014-04-10 16:14] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.DcA/zukitwo-themes-20140329-1-any.pkg.tar.xz'
[2014-04-10 16:14] [PACMAN] upgraded zukitwo-themes (20131210-1 -> 20140329-1)
[2014-04-10 16:14] [PACMAN] Running 'pacman -Syu'
[2014-04-10 16:14] [PACMAN] synchronizing package lists
[2014-04-10 16:15] [PACMAN] starting full system upgrade
[2014-04-10 16:16] [PACMAN] Running 'pacman -Rsc itstool happy ghc alex cabal-install'
[2014-04-10 16:16] [PACMAN] removed cabal-install (1.18.0.2-1)
[2014-04-10 16:16] [PACMAN] removed alex (3.1.3-1)
[2014-04-10 16:16] [PACMAN] removed ghc (7.6.3-1)
[2014-04-10 16:16] [PACMAN] removed happy (1.19.3-1)
[2014-04-10 16:16] [PACMAN] removed itstool (2.0.2-1)
[2014-04-10 17:40] [PACMAN] Running 'pacman -Rsc gnome-themes-standard unixobdc'
[2014-04-10 17:40] [PACMAN] Running 'pacman -Rsc gnome-themes-standard unixodbc'
[2014-04-10 17:40] [PACMAN] removed unixodbc (2.3.2-1)
[2014-04-10 17:40] [PACMAN] removed gnome-themes-standard (3.10.0-1)
[2014-04-10 17:40] [PACMAN] removed cantarell-fonts (0.0.15-1)
[2014-04-10 17:40] [PACMAN] Running 'pacman -Sc'
[2014-04-11 12:51] [PACMAN] Running 'pacman -S gnome-themes-standard'
[2014-04-11 12:52] [PACMAN] installed cantarell-fonts (0.0.15-1)
[2014-04-11 12:52] [PACMAN] installed gnome-themes-standard (3.10.0-1)
I found a post about the graphics driver affecting the laptop temperature, which is prompting me to re-run the test above with nouveau. Unfortunately, I can't startx without noaccel=1 and I get horrible performance with this.The solution there was to use the kernel option `radeon.dpm=1`, which for nvidia appears to be to use DPMS, which I seem to have, so perhaps that isn't relevant/related?
$ grep -i dpms /var/log/Xorg.0.log
[ 52.969] Initializing built-in extension DPMS
[ 56.794] (==) NVIDIA(0): DPMS enabled
While I was looking for how far back the overheating went, I also stumbled across some other errors in journalctl like this:
Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20131218/utaddress-258)
This post mentions a similar warning, but doesn't really get resolved. Here's another bug about that, which is both recent and also unresolved (active). The bug, however, says nothing about what effect it actually has! I'm not sure if there's anything undesirable about it other than an ugly warning...
Action items for me
- Try with nouveau (X and no-X)
- I'll be trying one of these utilities on Windows 7 shortly to see if the cpu temp is reported there.
Thanks again for the response/suggestions!

Shutdown Problem with KT4AV MS6712

Here is the problem.
I am running XP service pack 1, XP2600 processor FSB 333, 512 mb mem,
40 gig hard drive, dvd rom and cd burner.
If I use XP to power down system (shutdown) it actually performs a soft reboot (restart).
I have checked to make sure all wake ups are off. Double checked my reset and power switch connectors.
Any clues on what is wrong would be appreciated.
Thanks,
2dts

Quote from: Fredrik Åsenius on 13-June-06, 06:36:20
You have the wrong or no driver for a device. It is hard to say which one, if there isn't an explicit mark in Device Manager. But a start could be to install the mobo drivers found here:
http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=456&kind=1
If the problem doesn't go away, you should think about when the problem started, and what driver you installed then.
i suppose i am up to no good ...
i could eliminate the "unknown device" issue by removing one of my older PCI cards. ultimately i could even live with that. just to say that the STOP error is not related to this plug and play thing.
rephrasing the question: is DRIVER_POWER_STATE_FAILURE really caused by a driver or by a piece of hardware?
for your info: i am running a fairly clean installed w2K (will change to XP one of these days, but i assume no difference) on a 915P mainboard
big thanks!

My solution (or so I thought) to Power Manager/CPU throttling problems!!!

I have found a solution to all my Power Manager/CPU throttling problems!!! Though there is some good and bad news.
{EDIT: The problem has NOT been fixed, even after latest PowerManager (3.62) and BIOS (1.30) versions. Pretty much ignore anything I say below as the problem is still occurring. You can see my full post here: http://forum.lenovo.com/t5/W-Series-ThinkPad-Laptops/W520-Speedstep-not-working-properly-on-battery-...}
Good news: I have NONE of the throttling issues or inconsistent CPU frequency problems I was having before on AC or battery power. Everything, including TurboBoost on battery works! It is completely fixed! (I have no idea how this factors into Lenovo’s statements that TurboBoost is disabled on battery “by design”. There is at least one other post from someone else that also reported TurboBoost was working for them on battery)
Bad news: I don’t really know which one of the many things I tried actually worked. I am sorry I wasn’t more methodical about recording what I did and checking results, but this was my last ditch effort to get this fixed on my own without sending the system in for repair and frankly, I didn’t think it would work. Now that it has worked, I’m hoping my steps can help others.
For anyone interested, here’s what I did… and before anyone says something like “That has nothing to do with managing power/cpu, why would that help?!… etc., please keep in mind I’m just stating exactly what I did. I am aware some of the steps may not be relevant, but who knows… We all know how weird PC’s are sometimes, even the smallest, oddest thing may resolve a problem.So anyway, here goes.
**IMPORTANT** Not sure how many noticed, but there was a new version of Power Manager released a few weeks ago, 3.62. The PM driver seems to have stayed the same. That alone could very well be the sole fix, I’m not sure. You may just want to completely remove PM and PM driver and install the latest version before trying any of the steps below.
1)Made a complete system image via Windows built-in backup feature
2)Disable any 3rd party fan/CPU control utilities (Throttlestop, etc). Make sure they are also not going to run at startup or from a scheduled task
3)Remove Power Manager Driver, then remove Power Manager software
4)Reboot to Windows
5)Remove all traces of the Power Manager drivers/software directories (think it was something like C:\readyapps and C:\drivers.) **For some odd reason after I did this, my wireless stopped working but it resolved itself by the time I was done with these steps, strange
6)Reboot
7)Access BIOS and reset all settings to default
8)Boot into Windows, downgrade to BIOS 1.25 [UEFI: 1.25 - 8BET44WW / ECP: 1.14 8AHT32WW ] via the Windows flash utility. I wanted to downgrade all the way back to 1.06, but the software would throw up some error for any version prior to 1.25 and wouldn’t proceed
9)Reboot to Windows; make sure system booted w/ out issues
10)Reboot again, access BIOS, reset to defaults again
11)Shut down system
12)Disconnect AC power. Remove main battery. Access and disconnect system backup (a.k.a CMOS) battery under keyboard. Discharge residual power in the system (there are various ways to do this, but you could just leave the battery disconnected for a few minutes). Visually inspect the system for anything funky…my system had a slightly but noticeably loose CPU/GPU heat sink/fan assembly power connector.
13)Reconnect backup battery.
14)Reconnect AC power but leave main battery disconnected.
15)Power on. Should get a message indicating “checksum error, system time reset” or something like that.
16)Reboot to Windows. Verified still okay.
17)Downloaded latest BIOS version, 1.26. This time I burned the bootable BIOS flash CD instead of running it through Windows.
18)Restart and boot from disc, flash BIOS to 1.26. Once complete, restart. Verify BIOS set to defaults.
19)Boot back into Windows.
20)Install latest Power Manager driver (1.62 ), reboot if/as prompted. Install Power Manager (3.62), reboot as prompted.
21)Boot into Windows, verified Power Manager was active and working. Verified TurboBoost was working. Restarted system a few times and played around with Power Manager for a bit to see if the different power plans worked and retained the settings, all the while monitoring the Intel TurboBoost utility and PM’s own “power gauges”. Let system Sleep, changed power sources, resumed, etc. Everything was working great.
22)Shutdown, reconnect main battery. Booted into Windows. Again, fiddled with Power Manager for a bit, switching between power plans and AC/battery power. Still worked great.
23)Success!
That’s it. Again, this is not a guaranteed fix guide. These are just simply the steps that I took on my system that resolved the problems many of us are having. Hopefully it will work for others.
T520 4239-CTO | i5 2410M
W520 4270-CTO | 2720QM | 16GB RAM | Quadro 1000M | BIOS 1.30 | PwrMgr 3.62

All I basically did was download and install...
(Chipset driver) http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/oss924ww.exe
(PM driver) http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/83ku14ww.exe
Now, I did chipset first (didnt ask to reboot) then installed the PM driver (did ask to reboot)
I rebooted.... then I went into bios (1.26) and set everything to default... then restarted saving changes...
Since I prefer not using optimus I changed the display settings in bios right after saving the default settings...
Not sure whether or not you really had to go into bios... but everything seems to be working...
My settings in PM is set to Maximum Power in the Advanced tab, 3rd party monitoring tools is TPFanControl and HWInfo64....
W520 (4270 CTO) | i7-2820QM | 16GB RAM 1333 MHz | Runcore MSATA SSD | 2x Kingston SATA2 SSD | Quadro 2000M | FHD | Windows 7

Random shutdown problem on G5 dual 2.3 GHz w/OS 10.4.7

Hello,
I’m using a dual 2.3 GHz G5, and it’s been working flawlessly since I bought it about a year ago. Until yesterday, I was running OS 10.4.5. Yesterday I upgraded to 10.4.7, and as soon as I booted up after the install, I started having a maddening problem with my computer randomly shutting down. (Not sleeping, but a complete power down.)
At first, the shutdown would happen immediately after powering up; my computer wouldn’t even make it to the blue progress bar. I zapped the PRAM and tried something I found online about unplugging the computer for 15 seconds, then plugging it back in. It now boots up, and I can log in, but the computer still shuts down randomly.
There seems to be no pattern to the shutdowns. I tried taxing the processor by opening and resampling huge Photoshop files while lots of other apps were open, and things were fine. Then it would conk out while I was composing an email.
I’ve heard of this random shutdown problem affecting Macbooks, but I have yet to find anything about G5 towers and OS 10.4.7. Does anyone have any info/advice?
Many thanks.
G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD
G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD

Thanks for the advice. I did check the system.log in Console and found the following altert:
PMU FORCED SHUTDOWN, CAUSE = -122
Now, since my computer is just over a year old, and since this problem happened immediately after applying the 10.4.7 OS update, I found it hard to believe that my hardware could be responsible. After 2 days of troubleshooting, I was stumped; after a 2-hour service call, so was Apple tech support. I ended up doing an archive and install back down to 10.4.5, and all is well.
I tested this issue on other machines running 10.4.7 and had no problems. It seems that the following specific combination of elements triggered the problem:
• PowerMac G5 dual 2.3 GHz (dual 1.8 machines did not exhibit the same problem)
• OS 10.4.7
• Logging in with Open Directory/Active Directory mobile profiles
• iTunes 7
Bottom line: if you’re using a dual 2.3 GHz PowerMac with mobile OD/AD profiles, do not update to 10.4.7, and steer clear of iTunes 7, at least until there is a patch update available.
(And Apple wants to be taken seriously in the enterprise market?)
G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD

Clock problem and shutdown problem! Are they related?

Having a problem with my Dual 2 GHz Power Mac G5
A few days ago I noticed that my clock was not showing in the menu bar in the upper right corner of my desktop.
I went into System Preferences and went to Date & Time. Under the clock tab “Show Date and Time in Menu Bar” the box was not checked off. I checked it off and went to the “Date and Time” tab. The date and time was correct. I then checked the box “Click the lock to prevent further changes” to lock it. The date and time did not show up in the menu bar. I then went back to the tab “Show Date and Time in Menu Bar” and the box I checked was not checked off even thought the lock was still locked.
I then moved my cursor up to the menu bar in the upper right corner to see what would happen and the spinning beach ball started up but only for the original icons such as Bluetooth, Mobile Me (which I do not use), Time Machine, Spaces (doesn’t indicated the number when I switch Spaces, etc. The icons Norton Anti Virus and Tech Tool Pro in the menu bar are okay.
Also, when I attempt to shut down my computer the system clears the icons from my desktop except for a picture I have on my desktop and I get a gray wheel spinning and the system just hangs until I press and hold the on/off switch. I don’t know if the clock and shutdown problems are related.
The only new software I loaded recently was Skype with Logitech WebCam for the Mac and Quicken 2007 (Had a problem with Quicken 2006). They both are working okay.
And ideas on why I cannot get my clock to show up and my computer to shutdown?

You may have to consider a new post in the Hardware forum area for the computer
model and build/year; if there is a possibility of some basis the matter could be in
the machine and not the software running within it.
Your last two/three posts are in the Leopard 10.5(.8) forum area and do indicate
some kind of problem where troubleshooting the computer to discover if the matter
at hand would be either hardware or software based, may be the way to go.
The link to the 10.6 Snow Leopard forum won't be of help if your computer is a
PPC-based G5 tower, or other older pre-Intel configuration. And I remember
your earlier questions about the iMac G4 and some other issues in the past.
You may ask the moderators to put your post in a new thread of its own, in the
Leopard 10.5 area; so as to not 'piggy-back' another topic; even though some
of the odd issues you've had seem similar to this OP's topic line and appear to
be in the same general series of hardware. {The question here seems valid.}
The routine suggestions to check, test, verify, and perhaps repair or replace
the system; save a bootable clone to suitable external standalone device if
testing a suspect computer's viability is recommended; and the basics if not
already tried to help isolate the issue(s) as you've posted elsewhere, may be
of some help to try and do; so in that matter, a new thread of your own is best
for your own directed feedback. Since this kind of advice applies to most any
situation, including troubleshooting what may be hardware or software, I'm
adding my two and three-tenths cents worth here.
Your original included Apple Hardware Test may be of some help, in the process
of elimination; but is not conclusive, so other methods would be also suggested.
Some ideas appear to cover the same ground. However, system corruption or
disc failure can also manifest itself in odd ways & affect things indirectly for a time.
• OS X Maintenance And Troubleshooting
http://www.macattorney.com/ts.html
• Mac OS X BASIC TROUBLESHOOTING & MAINTENANCE
http://www.gballard.net/macrant/osx_troubleshooting.html
• Troubleshooting Tips for computers:
http://www.stcdio.org/offices/cem/mediaandtechnology/cem-computer-classes/troubl eshooting.html
So, at the risk of inadvertently alienating the OP, I am posting this as
a general help to following readers at some later time; and it may not
be too simple for a refresh course.
Some software issues can be resolved by repairing disk permissions,
and re-applying the last OS X update Combo file over the same one
already in the system; or if not up-to-date already, check & repair all
the general items and then apply the last Combo update.
A too-full hard disk drive can compromise the system integrity, so that
is a matter of course to keep up on what resources exist and remain
for the OS X to function correctly and for apps to multi-task together.
However that works out...
Good luck & happy computing!

Shutdown problems

I tried updating to 10.5.6 this evening (I should have read these forums first to be forewarned...but anyway..). I was prompted to restart and ever since I have had difficulty shutting down. All icons, the dock, desktop and menu bars switch off (as usual) and the screen goes to blue and just sits there. The HD is spinning and the screen goes from a light blue to a slightly darker shade of that blue and the cursor shows up on the screen as well. But the computer just doesn't shut down.
Is there a way to force shutdown (other than holding the power button down)??
Also, what can I do to help fix the problem.

I ran disk utility and no apparent problems came up.
I then went hunting in other threads for clues and found a link to the Apple download updates page which gave me an idea.....
Since my shutdown problems started when I was prompted to restart for the 10.5.6 update I thought to re-install the 10.5.5 update.
This seems to have worked. No idea why 10.5.6 would lock up the shutdown process but at least I get a clean shutdown now.
Anyone have a similar issue??

Need more info - same spontaneous shutdown problem...

I'm using a very trustworthy 2.5 year-old T500 running Vista SP2 32-bit and my laptop has begun to have the same spontaneous shutdown problems as other users who've written here. I suspect it's overheating. I normally use my T500 on a docking station, which may or may not exacerbate an overheating issue.
I want to address this problem to ensure that I can continue to progress on my PhD dissertation (!) without crises, so I have taken some of the steps previously recommended for this problem here on this board. I installed TPFC today to begin monitoring CPU temperature and it appears that it runs between 55 and 65 C. Other temps listed are lower. I also made necessary adjustments in Power Settings to maximize fan speed and allow CPU speed to float. I also removed the battery so I'm using AC power with no battery/recharging processes to add to the problem, though I'm not certain that last part will make any difference.
I want to also clean the fan since I'm sure it's probably dirty after 2.5 years of continous use in my house. How can I take my laptop apart to clean the cooling fan? Or is this something I should take it to a repair shop to accomplish?
Thanks in advance for your advice.

No, my machine is not under warranty any longer. I agree, if it was, there's no way I'd risk voiding it by tearing it apart myself.
Thanks for causing me to double check. I DO have a few months of warranty left, so this baby is going to a professional! I could probalby do it myself, but why risk it?

Leopard (10.5 & 10.5.1) shutdown problems

I just got a brand new 20" iMac with Leopard. When I started it up I migrated user settings (but no applications) over from my 12" PowerBook G4 (in case that is relevant).
A few of the times I went to the "apple" menu to shutdown the computer, the spinning gear/wheel looking icon came up and the computer did not shutdown. I had to hold the power button down in the back to reboot it.
Also, I installed 10.5 -> 10.5.1 upgrade. At the end of the installation process it said it was updating the "boot cache" and would reboot when it was finished. After an hour it was still spinning, so I manually rebooted the machine.
I am still having shutdown problems.
Any help is greatly appreciated. I backed up all my important files and am thinking of reinstalling Leopard from scratch and going from there. Is this an easy task?
Thanks,
JRF

Hi JRF;
Since you admitted to forcing the iMac to shut down a number of times, it is very likely that you have corrupted the disk. I would suggest as a start that you boot from the install media and use Disk Utility to repair the disk. Hopefully that will be able to repair any disk corruption that you may have caused by your forced shutdowns.
Allan

Strange shutdown problem

Hi,
Last night, I had a strange shutdown problem on my iMac G5 (revB, 20", 2.0 Gig), with 1 Gig RAM, running 10.4.4 with all updates. I had had the computer on most of the day, using it off and on. I shut it down, and left the room. When I came back about an hour later, the fans were running (not rapidly, just at the normal speed they run when the computer is running), but the screen was blank, and the "sleep" light was not on. The computer wouldn't respond to any moving the mouse or to keyboard input. I finally shut it down by holding the power button until the fans shut down. Upon restart, everything was normal, and after using it for a few minutes, I was able to shut it down normally. Has anyone else seen this sort of behavior, and is it normal ? Or am I about to have more problems.
Thanks in advance,
Dave Fritzinger
Honolulu, HI

Hi Dave,
By the sound of it your computer has "hung" during the shutdown process, but at a point in the process where the system's temperature control mechanisms were still operating (otherwise the fans would be running flat out). My guess in this case is that it was probably actually a finder crash.
Various things can prevent proper shutdown. Often USB or FW devices are to blame. USB adsl modems , some scanners and hubs and the occasional printer driver seem to be common causes. Software can be responsible too, though - background virus or drive checkers are probably the most common, but far from the only possible causes ( I seem to remember "SpringCleaning" causing this problem when people moved to Tiger 10.4.2 for example) .
New software or hardware are therefore the first things to look for.
If you haven't installed anything completely new then one possibility may be that something you are using is not compatible with the latest OS update, and needs an upgrade to a driver. Its also possible that this is a "one off" glitch caused by a temporary problem , but if it happens again I'd be taking careful note of anything that you were using in the previous session.
You might also want to use the Console (in Utilities folder) to look at your system and crash logs.
Cheers
Rod

Airport Time Capsule Shutdown problem

My 3TB 2014 Airport Time Capsule shuts down by itself approx once a week :Green light out with no wi-fi signal. Need to unplug and reconnect power to restart system. System has plenty of air flow, fan works and capsule body is cool.
Want to find out what is the cause and solution to prevent this repetitive shutdown problem.
Thanks
Dunkin888

This shutdown problem does not seem to apply to the Airport Extreme which does not have the Harddrive,
Yes, it does.
Re: My Airport Extreme intermittently shuts down completely.
Search here is now a hopeless failure but we do see the complaint fairly often.
And the same thing happens.. people return them and come back with the same problem.
There was some discussion as to the Airports being ultra sensitive to spikes.. or power dips.. so using it on a UPS was one recommendation..
I have found btw that the power supply design for universal, often works better in our part of the world on 240v than on 110v. If you happen to have an 110v to 240v transformer handy or cheaply available have a go running it on 240v. There are various methods used to handle 110v but voltage doubler on the primary circuit is one of the main ways it is done. That is a lot more susceptible to power spikes and dips than standard full wave rectifier.
In the end though.. power supply really should not shutdown.. AFAIK there is no soft off on them .. so for the power supply to shut down completely means it is in protection mode..
If you wanted to open and replace the supply with external 12v supply you probably can.. but so far nobody has trusted me with one.. and I think they are too issue prone to go buy one for myself to do experiments... although I am always keeping my eyes open for the dead ones.
See the teardown in
https://www.ifixit.com/Teardown/AirPort+Time+Capsule+A1470+%28Mini%21%29+Teardow n/15067
Then look at the link to the airport extreme.. they are identical except for the drive.. ie Apple has same power supply in both.. since it is under so much less load in the airport extreme yet they still have the problem I suspect it is fundamental design flaw in the supply.

Laptop-mode: shutdown problem

I have HP Elitebook 8540W.
When I enable the laptop-mode on this computer, I can't shutdown it anymore.
When I shutdown my PC, everything goes well until it reaches "Remounting root filesystem readonly":
Remounting root filesystem readonly
>POWER OFF
[137.532383] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[137.532529] ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392
[137.532531] res 40/00:02:00:00:02/00:00:00:00:00/00 Emask 0x4 (timeout)
[137.532813] ata2.00: status: {DRDY}
[142.849448] ata2.00: revalidation failed (errno=-5)
After this I have to shutdown my PC manually by pressing the power button for 5 seconds.
The ata2 in the logging above points to my BD-ROM drive (BC-5501H).
When I disable laptop-mode in rc.conf, the problem is gone.
Are there any "powersave options" I can disable for my BD-ROM somewhere in laptop-mode ?

As I understood my problem was caused by Wake-on-LAN function. You can disable it in BIOS if you don't need it.
Also if you don't realy need ethernet connection you can remove eth0 from ethernet interface in wicd options, so wicd won't touch it anymore.
These solutions worked for me as well as one mentioned above, but now I just removed laptop-mode and using pm-utils powersave script. More information on
https://bbs.archlinux.org/viewtopic.php?id=134109
http://crunchbanglinux.org/forums/topic/11954
Battery life is now much longer than with laptop-mode and I didn't encounter shutdown problems yet.

KT3 Ultra 2 (333) SHUTDOWN problem

i have a shutdown problem, it's probably relatet to the mainboard - when i press the POWER OFF/ON button on the PC, the computer kind off goes into stand-by and reapetedly make series of 3 beeeps at a time.
Is there a bios upgrade necessary? Anybody with similar problems?
tnx,
Greg

Quote
Originally posted by vincent1288
yeah, I'm having the same problem with my 3 AMD XP 2000+ KT3 system. There is no way to solve this problem. Tryed Bios update , Tryed 3 different System with different component, none of the three system turn off and follow with 3 beep.
Have you resolved this? I have identical problem but without the beeps..........
2Busy

Neo4 Platinum Shutdown Problems

I'm having problems to turn off my PC from windows or using the power button, my PC wont turn off completely monitor will go to stand by mode and the computer stays ON well I have to push the power button for 5 seconds and finally goes OFF!!
When I bought My MSI Neo4 platinum Nforce4 ultra (MS-7125) came with bios V1.6 and looks like I was experiencing problems with USB external drives so I updated to Bios V1.9 and the computer will not shudown I when back to V1.6 and the problem was gone then MSI released Bios V1.A I jumped and flashed my bios to see what happens!!
Well the PC is having shutdown problems again!!
I dont know What's going I installed a fresh WindowsXP just in case and the problem stays the same
I can only think of a defective PSU if that is the case why with Bios 1.9 and 1A have that specific problem?
Can somebody give me an idea?
thanks!!
Neo4 Platinum Nforce4 ultra (MS-7125)
Athlon 64 4000+
2GB OCZ PC3200 EL
XFX 7800GT
2x200GB Maxtor SATA Raid 0
2X300GB PATA
Audigy2ZS
Thermaltake 420W PSU 20pin

Hi,
I had the same problems.
installed with the help of the Diskette (also 2raidO HD), en then the drivers from the CD.
problem still there.
I then upgraded to 3.7 bios & 6.66 msi nforce (downloaded from MSI website): problem solved.
I later upgraded to the Nvidia 3.70 drivers, no issues.
I do have a problem about the Sound and the Digital Decoder of the DTT3500 Cambridge Soundworks.. (already posted in this tread):
Can't get 5.1 sound running! (with digital output, like on the SB LIVE! 5.1)
quote below:
I have bought a new PC with an MSI k8n sli platinum MB. this mainboard has a built in soundblaster live!24-bit chip onboard. it works great on headphones and normal 2 set speakers (analog connection).
however, when I try to set them up at the DTT3500 speaker set, trouble begins.
before continuing, just want to say First that my older PC is standing next to it, with a Soundblaster live! 5.1. If I connect with this PC to my speaker set, via the digital uitput, everythin works great. (5.1 surround).
In the DTT3500 manual, when Digital DIN is blinking, it says it isn't recieving any signal, or not the right one (like AC-3). (I know this when on my old PC when I switch to headphones, the digital din is then blinking, which is normal as I disabled Digital output in Windows)
now my questions:
Is this digital port is ac-3 signal or somthing else on the Soundblaster live! 24-bit?
Do I need to use another type of cable, like SPDIF Din Cable? (I now have a minijack to Din cable)
I tried with optical, it works, but only with 2 speakers (left and right / digital output is on). is this normal? If i look at the manual, it's typical used for gameconsoles with stereo left and right. I guess this is so with the DDT3500 decoder...?
if I try Digital Din on the Decoder, it doesn't work. the Decoder Led keeps blinking. Yet in Windows, digital output is on and 5.1 speakers is selected.
In short, exact the same setup on the Decoder and PC as my older PC.
My guess is the the soundblaster live! 24-bit is an enhanced version of the soundblaster live! 5.1? Am I wrong, I don't know....
I do know that the reviews said you could use the digital port (orange one)"
NOTE, yesterday, I disable the onboard SB live! 24 bit card, plugged in the SB live! 5.1 card from my other PC. This works ok like it should.
I would apreciate any help, as i'm really stuck at the moment & I just hate to disable this lovely onboard card.

How im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

how im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

What "auto shutdown problem" are you talking about?

K7N2 - Power on, Immediate Shutdown Problem!

Similar Messages

Maybe you are looking for