Mac Mini reformatting problem

Hi all... I'm trying to wipe clean my mini and re-install Tiger for a friend who is buying it. When the computer restarts with the Tiger disk inserted I receive a black screen with the following message.
No debugger configured - dumping debug information
MSR=00001030
Latest stack backtrace for cpu 0:
Backtrace:
Proceeding back via exception chain:
Kernel version:
Darwin Kernel Version 8.6.2.: Thu Apr 13 18:51:54 PDT 2006; root:xnu-792.9.59.obj~1/release_ppc
Panic: We are hanging here...
Is this some kind of virus?? *????

I found my answer... Thanks for looking!

Similar Messages

  • My mac Mini has problem rendering images and video

    THE PROBLEM:
    My mac mini has problem rendering JPEG image. There are strips on the images. Other images such as GIF, PNG, TIFF, and BMP are displayed nicely.
    The images shown in the links below illustrate the problem:
    http://www.flickr.com/photos/terencewong/71481156/
    http://www.flickr.com/photos/terencewong/73360989/
    (Please note that this image is grabbed from my faulty Mac Mini and saved into TIFF. For uploading purpose, I converted it into JPEG on ANOTHER computer.)
    For movies, AVI can be playback without problem. But when it is converted to MPEG, it looks like an untunned TV channel.
    FIXES TRIED:
    I did erase and install 3 to 4 times using both the install disc and my Tiger Family Pack. All ended up with strips on the JPEG images and the generated MPEG movies.
    I've also tried to flash the firmware to 113-xxxxx-124 using ATI's october 2005 universal ROM update, however, the ROM Revision shown in System Profiler is still 113-xxxxx-116 no matter how many time I reboot the system.
    INVESTIGATION:
    Yesterday, I did some research and got to know that JPEG and MPEG are using DCT (Discrete Cosine Transform) for decompression. And the ATI Radeon 9200 chip provide such a transform on hardware basis, which free the CPU from doing something else. Feel free to point out my inaccuracy.
    HARDWARE SPECIFICATION:
    I bought the Mac Mini in the last Februray.
    The system Boot ROM version is: 4.8.9f1
    Display card is ATI Radeon 9200
    Chipset Model: ATY,RV280
    Revision ID: 0x0001
    ROM Revision: 113-xxxxx-116
    A POSSIBLE CONCLUSION:
    I suspect that it is this part of the chip (the DCT) that is faulty.
    Anyone know how to fix this problem?
    Many thanks!

    Assuming that your display is tightly connected, thus the problem is not caused by something as simple as that, the fact that a full erase and install has not removed the problem would, I think, point to this being a hardware issue, and given that everyone's mini (with the possible exception of some of the latest ones) has the same video chipset as yours, and do not suffer the problem that you appear to, it seems very likely that your mini has a fault which is in need of repair.
    If you have an Apple Store nearby, I would take it there to have it checked out - at the very least they should be able to replicate your problem using an in-store display, and if not, thusly suggest it's something external to the mini and concerning your display or something very unusual in the immediate environment of the mini. If you don't have an Apple Store in reach, I'd take the system to an Apple authorized service provider since at the present time it is under warranty.

  • Mac Mini Mail Problem

    Hi - I recently bought a Mac Mini so that I could have a desktop and a laptop (I'd been using the Titanium G4 as both) and I have been having trouble with the email on the Mini. Right off, I should say that the G4 had 768MB of RAM whereas my Mini only has 512MB. But the Mini is 1.5 GHz versus just 800 MHz for the G4. (I clearly don't know which of those matters more in a situation like this.)
    Anyway, whenever someone sends me a large file now, it takes a dog's age to get it on the Mini. And while it's clearly downloading it in the background, it seems to ignore if I delete other emails, etc. For example, I might read 10 emails and delete them, and notice that I have wait for some attachment to download, and minimize mail in the interim. When I open it again, those same emails that I deleted are in my inbox again. Occasionally, I have gone to mac.com to delete files, and eventually my mail app notices this and deletes them as well, but clearly large files are causing a problem when they're sent to me.
    It's not a bandwidth issue, as my G4 handled large attachments way better with the same Internet connection, and continues to do so while wirelessly connected to it. My guess is it's the RAM, but I really don't know. Do I need to go out and double the RAM on the Mini to make this stop?

    Please follow these directions to delete the Mail "sandbox" folders. In OS X 10.9 there are two sandboxes, while in 10.8 there is only one. If you're running a version older than 10.8, this comment isn't applicable.
    Back up all data.
    Triple-click anywhere in the line below on this page to select it:
    ~/Library/Containers/com.apple.mail
    Right-click or control-click the highlighted line and select
    Services ▹ Reveal
    from the contextual menu.* A Finder window should open with a folder named "com.apple.mail" selected. If it does, move the selected folder — not just its contents — to the Desktop. Leave the Finder window open for now.
    Log out and log back in. Launch Mail and test. If the problem is resolved, you may have to recreate some of your Mail settings. You can then delete the folder you moved and close the Finder window. If you still have the problem, quit Mail again and put the folder back where it was, overwriting the one that may have been created in its place. Repeat with this line:
    ~/Library/Containers/com.apple.MailServiceAgent
    Caution: If you change any of the contents of the sandbox, but leave the folder itself in place, Mail may crash or not launch at all. Deleting the whole sandbox will cause it to be rebuilt automatically.
    *If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination  command-C. In the Finder, select
    Go ▹ Go to Folder...
    from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.

  • New Mac Mini USB problem

    I have a brand new Mac Mini (December, 2011, 10.7.2) as well as an older Mac Mini (circa 2005, 10.6.4).
    I bought a new GearHead USB wireless mouse to go with the new mini.
    The mouse works fine on the old Mini (and also on a Windows PC).
    On the new Mini, the mouse works until the Mini hibernates or powers down. On wake-up, the mouse doesn't work until I unplug and replug the USB transmitter.  This is the case on all USB ports on the Mini, as well as on the keyboard and monitor USB ports. It doesn't matter which port I use or which port I unplug and replug into - I always need to unplug and replug the transmitter to get it to work after power- or hibernate-cycle.
    Note that I have also tried a Logitech USB wireless mouse and an Apple Bluetooth mouse and they both work fine on both the new Mini and the old Mini.
    The problem is only occurs between the Gearhead brand USB mouse and New Mac Mini (10.7.2).
    I assume that the problem is that the mini is powering down the USB port and not refreshing it after power cycle, until I unplug and replug the transmitter. Alternatively, I suppose, the transmitter could be asserting itself early in the boot process before the Mini is awake enough to hear it.  In either case, it seems that the band-aid fix is a command-line to force the OS to refresh the ports, but I can't find any reference to such a command.
    Thank you for any help you can provide.

    Hello,
    I assume that the problem is that the mini is powering down the USB port and not refreshing it after power cycle,
    To me it seems like when the usb is powered down the trnasmitter loses the signal with the mouse, i think your mini is perfectly fine, even though the mouse works fine on the old mini I think its how the transmitter handshakes with the new mouse on the new mac mini. Do you have a new mouse of the same brand that you can test and see if it has the same issue...
    If so then it forsure the transmitter... not the mini... else take your mini in for health check.
    good luck, let me know how u go...

  • Mac mini Overscan problem

    Hello, i just purchased a Mac mini and have connected it with DVI to HDMI onto my Panasonic plasma TV. The problem with this was if i turn overscan on the display is too big and is extended over the sides and some area isn't visble to me. If i turn overscan off there are black areas which is not covered around the sides of the screen. I have never had this with my PC connecting to this TV with HDMI DVI. But for some reason this problem is happneing to me right now...is there a Mac special software that can adjust the screen size so i can stretch the display around to manipulate it to a full screen size without anything being cut out or under cut in my display?

    When you connected the PC and had no trouble with overscan, is there a way to capture the details of the timing involved? Because if you apply the same settings from the mini, there is no reason the TV shouldn't react to timing in the same way, meaning no overscan.

  • Mac Mini Audio Problem

    Hi,
    My Mac mini is only sending sound to one side of the headphone. I can get sound on the right but no sound on the left. I'm wondering if the sound card might need replacing ???
    Any help would be appreciated.

    Actually I'm trying to hook it up to my stereo so I was trouble shooting with the headset as I only get sound from one speaker. The Bose rep suggested I try a head phone to make sure the problem is coming from the mac mini. Is it possible to hook up to a stereo via a usb?(USB to Stereo input cables?) Also do you think that would help? I've tried new head phone to stereo cables between the two and same problem....

  • Mac Mini Burn Problem

    Hello,
    I have been trying to burn a CD using my Mac Mini, which has a built in SuperDrive, but cannot complete large capacity burns. It can burn 14MB worth of photos/videos, but cannot complete a video CD burn, made with Toast 7, or an hour and five minute in length Audio burn with iTunes. It is reporting the following errors, in order:
    The drive reported an error:
    Sense Key = MEDIUM ERROR
    Sense Code = 0x0C
    WRITE ERROR
    and then:
    The drive reported an error:
    Sense Key = ILLEGAL REQUEST
    Sense Code = 0x30, 0x05
    CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT
    I have tried a lense cleaning disc, and two different types of CD, and it has made no difference. I have a feeling that the inside of the mini is quite dusty, so that might be the problem, but I'm afraid of actually opening it to clean it, in case I invalidate the warranty, and then left to pay to fix it myself. On the other hand, if I arrange for it to be looked at by Apple, and they find it is dust, then I might be charged for it anyway! So, I'm looking for advice/past experiences etc. please.
    Thanks Very Much,
    Thomas Wright.

    I have DVD-RW discs from TDK, that I can burn no problem in my Mac mini, but cannot get the Power Mac to recognize when I'm trying to access files on them, keeps asking to initialize, even though the optical drive isn't a rewritable. I would like to replace the drive with a rewritable, what brand/model would work in OS 9?
    In the past Pioneer drives have been a safe bet and are even bootable. However, check [Jeff's January 2010 post about re-branded Pioneer drives|http://discussions.apple.com/message.jspa?messageID=10839236#10839236] that are no longer really Pioneer manufactured.
    You could start by looking at what's on www.macsales.com. I know you're in Oz but OWC is a good place for reference for Mac compatibility.

  • Mac Mini RAM Problem

    Hi to all!!
    That's my (new) problem:
    after an incredible reanimation of my "dead" Mac Mini (it wasn't turn on at all except the white LED at the front), now the system can't read the total amount of installed RAM Memory.
    This Mini has installed 512MB in 2 banks of 256MB each. I'm sure of this because I opened the Mini and I seen this 2 banks. But:
    - in Mac OS X, system recognizes only 256MB (and, in System Profiler, Bank #1 results empty)
    - in Windows, system recognizes only 224MB and Intel Video Card see 32MB of video memory instead of 64MB
    Other details:
    - Apple Hardware Test DOESN'T reveals any problem!
    - Windows memory diagnostics (from Windows Vista install DVD) also DOESN'T reveal any problem
    - MemTest86 and another RAM tester reveals, at the opposite, RAM problems in several sectors.
    This Mini has been previously repaired from an Apple Center for the same problem, and they have replaced both RAM banks. It's possible that, again, RAM banks has became faulty?? And, over all, that 2 faulty RAM banks DOESN'T cause any Kernel Panic or Windows 's BSOD???
    If it can be usefully... also the built-in Wireless Card has stopped its work, in Windows and in Mac OS X: WiFi card is seen from the System but any WiFi Network is found....
    Please help me!!
    Thanks to all!

    Your best bet is to get the RAM replaced by high quality to spec RAM*:
    http://www.macmaps.com/badram.html
    If the same RAM tests fail again, then you can likely suspect the RAM slots themselves were never repaired.
    - * Links to my pages may give me compensation.

  • Mac Mini Booting Problem

    My mac mini has developed a problem starting up. The computer turns on and goes to the gray screen but on the gray screen the apple logo does not appear. After a few minutes the screen just goes gray with a folder flashing from a question mark to a finder logo. I tried the reinstall disks but nothing happend. Any ideas??
    jesse

    The timing of holding down the C key to boot from the install disk can be tricky. You may have to experiment.
    Force the Mini to turn off by holding down the power button for 5 seconds. Then restart and hold down the C key as soon as you hear the startup chime or beep. (Again, you may have to experiment with the timing slightly -- and you have to have a wired USB keyboard for this to work. Borrow one if you don't have one.)
    If none off this works, you can usually eject the CD during the startup process by holding down the mouse button, assuming you have a wired mouse.

  • Mac mini startup problem. Blank desktop - no dock/icons.

    But i can see the clock, wifi symbol, etc.... and i can move the cursor.

    In Target mode what shows on the problems Mini's screen?
    This does not make sense?
    Its an intel G4 - i think 2011 model
    How to identify Mac mini models
    Also:
    http://en.wikipedia.org/wiki/Mac_Mini

  • Mac Mini Crash Problem

    He is My information on my mac mini.
    Hardware Overview:
      Model Name:          Mac mini
      Model Identifier:          Macmini3,1
      Processor Name:          Intel Core 2 Duo
      Processor Speed:          2 GHz
      Number of Processors:          1
      Total Number of Cores:          2
      L2 Cache:          3 MB
      Memory:          4 GB
      Bus Speed:          1.07 GHz
      Boot ROM Version:          MM31.0081.B06
    When i spend around 54316 sec on here, it says "there was a problem found, Please press any key to restart, or wait a few secs. it done this about 6 times sence i updated to Mountain Lion. here is the crash report a coppyed...
    Interval Since Last Panic Report:  54316 sec
    Panics Since Last Report:          6
    Anonymous UUID:                    E8EDFB5A-D406-2293-DD5C-7307CF3E8E76
    Fri Sep 28 20:01:48 2012
    panic(cpu 0 caller 0xffffff8002051c07): "IOGMD: not wired for the IODMACommand"@/SourceCache/xnu/xnu-2050.18.24/iokit/Kernel/IOMemoryDescriptor.c pp:1424
    Backtrace (CPU 0), Frame : Return Address
    0xffffff807ac5a940 : 0xffffff8001c1d626
    0xffffff807ac5a9b0 : 0xffffff8002051c07
    0xffffff807ac5aa40 : 0xffffff800204c9de
    0xffffff807ac5aaf0 : 0xffffff800204d60a
    0xffffff807ac5ab10 : 0xffffff7f82335a44
    0xffffff807ac5ab80 : 0xffffff7f8239fd85
    0xffffff807ac5abd0 : 0xffffff7f8239feaf
    0xffffff807ac5ac20 : 0xffffff7f82385515
    0xffffff807ac5aca0 : 0xffffff7f82383815
    0xffffff807ac5ace0 : 0xffffff7f82372083
    0xffffff807ac5ad90 : 0xffffff7f8239c177
    0xffffff807ac5af80 : 0xffffff7f8239d1d8
    0xffffff807ac5b050 : 0xffffff7f833b7419
    0xffffff807ac5b190 : 0xffffff7f833b6efe
    0xffffff807ac5b1a0 : 0xffffff7f833e5c46
    0xffffff807ac5b770 : 0xffffff7f833e6539
    0xffffff807ac5b8b0 : 0xffffff7f83379a6b
    0xffffff807ac5b930 : 0xffffff7f83379bac
    0xffffff807ac5b960 : 0xffffff7f833669a5
    0xffffff807ac5b9a0 : 0xffffff7f8338dfc6
    0xffffff807ac5b9d0 : 0xffffff7f8335f3d3
    0xffffff807ac5ba00 : 0xffffff7f822e4350
    0xffffff807ac5ba40 : 0xffffff7f822e6717
    0xffffff807ac5ba60 : 0xffffff7f822e6e95
    0xffffff807ac5bb40 : 0xffffff7f822e72a7
    0xffffff807ac5bb70 : 0xffffff7f822ebd35
    0xffffff807ac5bbc0 : 0xffffff8002066f53
    0xffffff807ac5bc20 : 0xffffff8002064b8f
    0xffffff807ac5bd70 : 0xffffff8001c981e1
    0xffffff807ac5be80 : 0xffffff8001c20aed
    0xffffff807ac5beb0 : 0xffffff8001c10448
    0xffffff807ac5bf00 : 0xffffff8001c1961b
    0xffffff807ac5bf70 : 0xffffff8001ca5b16
    0xffffff807ac5bfb0 : 0xffffff8001cced53
          Kernel Extensions in backtrace:
             com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f822d8000->0xffffff7f8230ffff
                dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f8228d000
             com.apple.NVDAResman(8.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f8232f 000->0xffffff7f82631fff
                dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f8228d000
                dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8231b000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f822d8000
             com.apple.GeForce(8.0)[2E56ED9A-D848-3795-9E52-56BABDC9000C]@0xffffff7f8335e000 ->0xffffff7f83420fff
                dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f823 2f000
                dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8231b000
                dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f8228d000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f822d8000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    12C54
    Kernel version:
    Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
    Kernel slide:     0x0000000001a00000
    Kernel text base: 0xffffff8001c00000
    System model name: Macmini3,1 (Mac-F22C86C8)
    System uptime in nanoseconds: 8968793580753
    last loaded kext at 257505732992: com.apple.filesystems.smbfs          1.8 (addr 0xffffff7f821f7000, size 229376)
    last unloaded kext at 288616476826: com.apple.driver.PioneerSuperDrive          3.1.0 (addr 0xffffff7f839a8000, size 12288)
    loaded kexts:
    com.logmein.hamachi          1.0
    org.virtualbox.kext.VBoxNetAdp          4.1.22
    org.virtualbox.kext.VBoxNetFlt          4.1.22
    org.virtualbox.kext.VBoxUSB          4.1.22
    org.virtualbox.kext.VBoxDrv          4.1.22
    com.apple.filesystems.smbfs          1.8
    com.apple.driver.AppleIntelProfile          97
    com.apple.filesystems.udf          2.3
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.ApplePlatformEnabler          2.0.5d4
    com.apple.driver.AGPM          100.12.69
    com.apple.driver.AudioAUUC          1.60
    com.apple.driver.AppleHDA          2.3.1f2
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.iokit.IOBluetoothSerialManager          4.0.9f33
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f33
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.2.11
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.driver.AppleMCCSControl          1.0.33
    com.apple.GeForce          8.0.0
    com.apple.filesystems.autofs          3.0
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.driver.AppleIRController          320.15
    com.apple.iokit.SCSITaskUserClient          3.5.1
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.2.2
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.driver.AirPortBrcm43224          600.36.17
    com.apple.driver.AppleUSBHub          5.2.5
    com.apple.driver.AppleAHCIPort          2.4.1
    com.apple.nvenet          2.0.19
    com.apple.driver.AppleEFINVRAM          1.6.1
    com.apple.driver.AppleUSBEHCI          5.4.0
    com.apple.driver.AppleUSBOHCI          5.2.5
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.7
    com.apple.driver.AppleACPIButtons          1.6
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.6
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.driver.AppleProfileTimestampAction          97
    com.apple.driver.AppleProfileThreadInfoAction          97
    com.apple.driver.AppleProfileRegisterStateAction          97
    com.apple.driver.AppleProfileReadCounterAction          97
    com.apple.driver.AppleProfileKEventAction          97
    com.apple.driver.AppleProfileCallstackAction          97
    com.apple.iokit.AppleProfileFamily          97
    com.apple.driver.DspFuncLib          2.3.1f2
    com.apple.iokit.IOSurface          86.0.3
    com.apple.iokit.IOBluetoothFamily          4.0.9f33
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f33
    com.apple.driver.AppleHDAController          2.3.1f2
    com.apple.iokit.IOHDAFamily          2.3.1f2
    com.apple.driver.AppleGraphicsControl          3.2.11
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.2.0d16
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleUSBAudio          2.9.0f6
    com.apple.iokit.IOAudioFamily          1.8.9fc10
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.nvidia.nv50hal          8.0.0
    com.apple.NVDAResman          8.0.0
    com.apple.iokit.IONDRVSupport          2.3.5
    com.apple.iokit.IOGraphicsFamily          2.3.5
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IO80211Family          500.15
    com.apple.iokit.IOUSBUserClient          5.2.5
    com.apple.iokit.IOAHCIFamily          2.2.1
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOUSBFamily          5.4.0
    com.apple.driver.NVSMU          2.2.9
    com.apple.driver.AppleEFIRuntime          1.6.1
    com.apple.iokit.IOHIDFamily          1.8.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          344
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.6
    com.apple.iokit.IOPCIFamily          2.7.1
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0

    com.apple.NVDAResman seems to be a common problem, I think some have moved the kext to correct it... might search that out.
    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
    Reboot, test again.
    If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.
    Check the System Preferences>Other Row, for 3rd party Pref Panes.
    Also look in these if they exist, some are invisible...
    /private/var/run/StartupItems
    /Library/StartupItems
    /System/Library/StartupItems
    /System/Library/LaunchDaemons
    /Library/LaunchDaemons

  • Mac Mini boot problem - Debugger called: panic ?

    after i push the start button, the first page shows "Your computer restarted because of a problem. Press a key or wait a few seconds to continue starting up." it was written in six languages... secondly, the page i show in this picture appear for just a few second, but i manage to snap a picture on it using my ipad2. after that it repeats the same thing from the first page again and again for several times until it shut down by itself... i do not know what could possibly wrong with that, before it happen i was just finished installing Xcode from itunes store. please help me, i just bought this mac mini 2 weeks ago.

    Back up all data.
    Boot into Recovery by holding down the key combination command-R at the startup chime. Release the keys when you see a gray screen with a spinning dial.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with networks that require any kind of authentication other than a WPA or WPA2 Personal password.
    When the OS X Utilities screen appears, follow the prompts to reinstall the OS. You don't need to erase the boot volume, and you won't need your backup unless something goes wrong. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.

  • Mac Mini Sleep problem - help!

    I have a new Mac Mini 1.83 and a new Envision 22" LCD monitor and when I put the Mac Mini to sleep and click on the keyboard, the MacMini comes out of sleep but the display screen stays black. If I manually set the computer to sleep a second time and take it out of sleep a second time by clicking on the keyboard, then the display works properly. But I have to put it to sleep and make it come out of sleep TWICE before the Envision display works properly. Any ideas about this problem?

    I have that problem since Quicktime 7.1.6 update (or the Airport Update, can't say).
    When rebooting the display stays dark, but everything comes up fine. When I put in the Installation CD, the display turns on.
    (DVI-FullHD, as before).
    But after the "blank" screensaver gets activated, the display doesn't turn on again, not even using the CD.
    (Although everything else still runs fine.)
    HELP !
    Mac Mini Intel/1.66   Mac OS X (10.4.9)  

  • How i fixed my mac mini dvi problems

    Hi,
    I bought an 200W6 20inch tft philips screen on saturday. When i connected it to my mini i noticed that i wouldn't return to an on state after the monitor stanby, also it took very long to recognise my tft after boot( like 5 mins or so) then when i ran the flurry screen saver everything looked fine but after 30 sec. there was snow and all sort of distortion. So clearly my monitor didn't work well with the mac mini.
    After reading the topics here i was shocked to see that so many people have problems with there displays, and there is no real solution.
    I tried to run the ati firmware update, and after that all my problems are gone. My monitor show the apple image right away, and the screensaver doesn't crash or disort I'm very happy now, i hope the firmware update can help you guys aswell. Try it out...

    Hello. Thanx for the link, but i had tried this one already! This one says during the installation: This program does not upgrade Apple OEM hardware, such as the Powerbook, iMac, eMac, Mini or factory!
    I have tried it and it does not help and does not install right. My mini has the following graphic rom and Monitor attached:
    ATI Radeon 9200:
    Chipsatz-Modell:     ATY,RV280
    Typ:     Monitor
    Bus:     AGP
    VRAM (gesamt):     32 MB
    Hersteller:     ATI (0x1002)
    Geräte-ID:     0x5962
    Versions-ID:     0x0001
    ROM-Version:     113-xxxxx-116
    Monitore:
    Philips 200W:
    Monitortyp:     CRT
    Auflösung:     1680 x 1050 @ 60 Hz
    Farbtiefe:     32-Bit Farbe
    Core Image:     Nicht unterstützt
    Hauptmonitor:     Ja
    Synchronisierung:     Aus
    Eingeschaltet:     Ja
    Quartz Extreme:     Unterstützt
    Rotation:     Unterstützt
    It would be great if anyone could help.
    Thanx, Markus

  • Mac Mini Power Problems

    Ok. I have a mac mini 2009 and it was doing fine up until a week ago. Now it will randomly shut it self off. I have tried reseting my sms. I have also done a complete wipe and reinstalled the OS and I get the same problem. I got it checked at the local Apple store, they found nothing wrong. I brought it back home and plugged it up and it works for about 10 minutes before shutting off. I took the computer out of the bedroom where i have it always plugged in and moved it to another part of the house and now it works like new. My question is can my mac have caused a shortage in my wall socket or is there not enough power coming in. Any Ideas... Please cause i would love to move it back into my bedroom.

    I seriously doubt your mini caused a fault in your electrical system. Its more likely, especially based on your testing, that the circuit is the issue. Did you check to see if some of your power sockets are run through one of the light switches in the room? Did you or someone else recently move where the mini was plugged in to another socket in the room?

Maybe you are looking for

  • How to create a new row for a VO based on values from another VO?

    Hi, experts. in jdev 11.1.2.3, How to create a new row for VO1 based on values from another VO2 in the same page? and in my use case it's preferable to do this from the UI rather than from business logic layer(EO). Also I have read Frank Nimphius' fo

  • Can the new Mac Mini boot Snow Leopard from an external hard drive?

    I currently boot my 2009 Mac Mini from a FW800 external drive with 10.6.8. If I just plug my external drive into a new 2011 Mac Mini, will it boot into Snow Leopard if I set it as the startup disk or will I get a kernel panic?

  • My Computer crashes (blue screen of death) each time I open adobe acrobat 9 pro

    I sent the dump file to my IT person and below is response: Both of your crash dump listings list the fault of your crashes as FNPLicensingService.exe  This is normally installed as part of an Adobe product (Reader,Photoshop,etc.) but it could also b

  • Using Forms through ODBC

    Hi guys! I've got a strong wish to use Forms6i, but... My desire is some strange. Because I want to use Oracle Forms and Reports to develop application for MSSQLServer. Please say to me it is possible. Should I tune Net8 for that purpose? If I should

  • Mouse errors in log

    I have been noticing some stuff in dmesg, seems to be related to my mouse, however, my mouse works just fine. My issue, is that my console gets filled with this stuff (yes, the ttys) and it is REALLY irritating: [ 710.936312] usb 1-1.1: USB disconnec