OS9 bootable G4 mac fails to boot with NI-DAQ4.9

We're going to use the OS9 bootable G4 machine with NI-DAQ4.9 driver. However, after the installation of NI-DAQ4.9 the G4 machine failed to boot up(Pure OS9 boot. Not classical environment). The error message said that address error occurred when the NI-DAQ was loaded during the icon parade.
We installed the OS completely newly without any other softwares and installed the NI-DAQ4.9 driver. So it must be difficult to account for the problem by any conflict with other inappropriate softwares. Minimum set of system extension plus NI-DAQ also caused the same problem.
Now I doubt the problem caused by the conflict of new G4 with NI-DAQ4.9 because other hardwares work OK (Other G3 or older G4 machines).
If anybody ca
n post any idea or solution on this problem, we'll appreciate.
(*)We need to control PCI-DIO-96 board with our homemade C-program, so NI-DAQ 4.9 is required instead of NI-DAQ 6.
Machine: PowerMacintosh G4(Single1.25G4 Processor)-Latest OS9-bootable G4 machine
NI-DAQ:4.9.4

First, we will want to make sure that you have the latest NI-DAQ driver that still supports C program. That driver should be v4.9.4 and can be found from the link in the previous post (or here http://www.ni.com/support/daq/mac/macversn.htm).
After verifying this, I would try to restart the computer without your hardware installed to check if it is a hardware/NI-DAQ configuration issue or if you just had a bad install of the software. If it still does not work without the hardware than you can attempt to uninstall/reinstall NI-DAQ v4.9.4.
Finally, the problem may lie with in a conflict with the extensions on your MAC. If you are familiar with troubleshooing MACs, then you can disable all but the core extensions and see if you can get the computer up and running
that way. Below are a few KnowledgeBases that discuss some of these issues:
Computer Hangs While Trying to Install NI-DAQ or LabVIEW on Macintosh
My NI-DAQ Crashes Either at Boot (4.x) or When Loading (6.x) on the Blue and White Power Macintosh G...
Regards,
Michael
Applications Engineer
National Instruments

Similar Messages

  • Z68A-GD65 (G3) fails to boot with new Gigabyte Radeon HD 7950 OC

    Hi,
    I have a problem with my new Gigabyte AMD Radeon HD 7950 (GV-R795WF3-3GD):
    My system fails to boot with this GPU, with the old Radeon HD 4850 everything works fine.
    Here are my system specs:
    MSI Z68A-GD65 (G3)
    CPU: Intel Core i5-2500K
    RAM: 8Gb DDR3-RAM (Corsair)
    power supply: be quiet! Pure Power L7 530W
    What I have already tried to fix the problem:
    -CMOS Reset
    -other PCI-e slot
    -other power supply (old 750W)
    Nothing worked.
    Do I need a Bios update? My current version is V23.7, but I'm not sure whether I can use the latest versions because my CPU is a SandyBridge...

    We can't help you woth your vga as it is no MSI product. You can try latest bios for your board (http://www.msi.com/product/mb/Z68A-GD65--G3-.html#/?div=BIOS) because the latest bios versions for G3 boards are  working well with Sandy and Ivy. If latest bios should not help and you like to downgrade the bios we can give you the needed files if you ask here.

  • IBook G4 fails to boot with internal HD installed, works when removed

    The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
    The long version–
    Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
    This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
    I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
    After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
    Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
    Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
    Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
    Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
    Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
    Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
    Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
    Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
    Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
    +same error message a bit faster than one every 3 seconds+
    Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
    Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
    I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
    When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
    Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
    Thanks!

    I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
    Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
    BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
    There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

  • Kernels 3.10.6 and 3.10.7 fail to boot with EFI stub

    Been using rEFInd for some time now. Current installed version is 0.7.1. Kernels 3.10.5 and earlier would boot without incident. Yesterday I upgraded to 3.10.6 and boot failed. As a workaround, I copied the Liquorix kernel and initramfs from my Kubuntu partition; to my mild surprise, this worked. My next test was to install the 3.10.7 Zen kernel from heftig's repository. This kernel boots fine (I added a version number string to the name of the kernel image and the initramfs so that rEFInd would automatically match them). After that, I enabled Arch testing and updated the Arch kernel to 3.10.7; this also fails to boot just like the 3.10.6 kernel did.
    I'm a fan of boot text, so I've configured rEFInd in text mode only. Here's my refind.conf, with almost no changes from defaults:
    timeout 20
    textonly 1
    use_graphics_for
    scan_all_linux_kernels
    And my /boot/refind_linux.conf:
    "Boot to X" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=graphical.target"
    "Boot to single user" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=multi-user.target"
    # "Boot to recovery" "ro root=/dev/sda3 nox2apic nomodeset systemd.unit=rescue.target"
    Finally, details abot my laptop -- a ThinkPad T520:
    steve@t520 ~ $ inxi -xxSMCGDp
    System: Host: t520 Kernel: 3.10.7-1-zen x86_64 (64 bit, gcc: 4.8.1)
    Desktop: KDE 4.11.00 (Qt 4.8.5) dm: kdm Distro: Arch Linux
    Machine: System: LENOVO product: 423926U version: ThinkPad T520 Chassis: type: 10
    Mobo: LENOVO model: 423926U Bios: LENOVO version: 8AET63WW (1.43 ) date: 05/08/2013
    CPU: Dual core Intel Core i7-2620M CPU (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10769.3
    Clock Speeds: 1: 1188.00 MHz 2: 1809.00 MHz 3: 1809.00 MHz 4: 1080.00 MHz
    Graphics: Card: NVIDIA GF119M [Quadro NVS 4200M] bus-ID: 01:00.0 chip-ID: 10de:1057
    X.Org: 1.14.2 driver: nvidia Resolution: [email protected]
    GLX Renderer: NVS 4200M/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 325.15 Direct Rendering: Yes
    Drives: HDD Total Size: 1256.3GB (8.2% used)
    1: id: /dev/sda model: M4 size: 256.1GB serial: 000000001140031E608A temp: 0C
    2: id: /dev/sdb model: HGST_HTS721010A9 size: 1000.2GB serial: JG40006PG61HKC temp: 43C
    Partition: ID: / size: 108G used: 37G (37%) fs: ext4
    ID: /boot/efi size: 511M used: 3.1M (1%) fs: vfat
    ID: /mnt/kubuntu size: 118G used: 59G (53%) fs: ext4
    ID: swap-1 size: 9.64GB used: 0.00GB (0%) fs: swap
    Last edited by steveriley (2013-08-19 05:27:15)

    Steve, your picture is far too large for these forums.  You are going to want to put it in some kind of a picture sharing/hosting site and link back to it.  Otherwise it will end up disappeared (likely via black magic) from your post.  I don't think that it provides any useful information anyway.  If you want to post your kernel command line that is great.  But posting a picture of a frozen screen with no output... doesn't really do much good.
    Efistub has been a bit shaky since 3.6 actually.  There is a monster thread about this already, the title of which references 3.6, but the content continues on through several kernel releases.  Still people continually report this as being an issue.  What I do is I keep a normal efi bootloader (one that doesn't rely on efistub) at the ready all the time.  My choice was elilo, but since [testing] started including syslinux-efi in the syslinxu package, I have started using that... though I still have elilo set up.
    Can you boot with efistub from the UEFI Shell or gummiboot?  I prefer gummiboot, but I have had this problem in the past, and when I did, I was able to boot with rEFInd... which was strange.  Some people even report that simply having a direct efibootmgr entry in their firmware causes it to magically work.  Though there should be to reasonable explanation for this, it was confirmed by several people in the mentioned thread.

  • K8N Neo fails to boot with more than one DIMM

    I have been searching the forums for a while now, and will continue, but I am really hoping for a quick resolution.  My system was running fine for over a year with a pair of PC3200 512MB DIMMs.  I normally leave my computer on all the time.  Recently I updated my BIOS to 2.10, and the system performed a soft boot afterwards.  Christmas Eve day I knew I was going to be gone the whole day and probably not need my computer until late on Christmas day.  I received a very unpleasant surprise.
    I attempted to boot the computer up, and I got nothing but a repeating single long beep.  I did a lot of troubleshooting and discovered that the system will boot and run fine with ONE DIMM, either DIMM.  My system will no longer boot with a second DIMM in either the 2 or 3 DIMM slots.  This is a major bummer for me, please help.
    I have not played around much with memory timings and such as of yet.  It is quite a pain to put in a single DIMM, and boot the system to make a BIOS change then shut it down again and install the second DIMM to see if it works.
    Thanks in advance for any help.
    Scott

    Go back to your previous BIOS.

  • Win7 x64 install fails at boot with alternating Mac and Cross-Circle  Logo

    Thanks for reading.
    I have a new late 2009 i7 2.6Ghz Macbook (6.1 model) that I purchased in February this year. I'm having real problem trying to get a Windows 7 DVD to boot on it; whenever I try (either by using the bootcamp assistant to parition my drive then start the boot process, or by holding down the OPTION key, or even using the C key at boot) instead of the normal Windows 7 boot process, the disc spins, then I am left with an alternating Apple logo with a circle with a angled cross line through it, sometimes showing a folder with a ? mark.
    I have tried resetting the PRAM, using other Windows 7 media, but I just can't seem to get a disk to boot. I have even tried wiping my Mac parition in case it was a corrupt partition by backing up to a timedesk then reinstalling, but again when I come to install Windows 7 I get the same problem.
    I can boot the Mac OS install disks not problems.
    Really appreciate if anybody has any guidance or resolutions?

    Hi - no nothing plugged, except my external DVD drive.
    I managed to install TechTool Pro's emergency EDRIVE from DVD, and have managed to reinstall Mac OS X without any problems, so unsure about a hardware problem. All TechTool tests come back ok, so no issues seem visible from that.
    You might be thinking why I am using an external DVD; well this is because I've taken out the internal DVD using OWC Datadoubler http://eshop.macsales.com/item/Other%20World%20Computing/DDAMBS0GB/
    I have a 512GB SSD in the normal hard drive space, and a 500Gb Hybrid disk where the DVD drive was. The drives are seen perfectly well in Max OSX; indeed when I did a reinstall I used the 2nd internal hard disk as the time machine and then restored from it.
    Could it be a problem with partitions or some issue with the EFIboot from the Windows 7 DVD's? I've tried looking at rEFIit http://refit.sourceforge.net/ to see if that would help, but no luck.
    The data doubler shows examples of this being used in my mac model for a specific Windows implementation (which is why I bought it) so don't think its that. Anybody have any ideas?

  • PC22224 switch fails on boot with message "Invalid switch MAC address"

    Ok moderators, I know this is a nonsupported product, but you moved all Switch messages to the archive.  This seemed to be the most appropriate folder for it.  Hope that's ok?
    I have a NEW (can you believe it?) PC22224 managed Cisco/Linksys switch with a problem.  When it boots, it passes all tests until it is almost ready to run, then I get this message:
    Checking file integrity..... Done
    Decompressing Code Image.... Done
    System PANIC.....
    Invalid switch MAC address
    Does anyone know how to correct this problem?  I can find nothing on it anywhere on the web.
    Thanks in advance!
    Kid

    Hi kidbyte!
    All Linkys Business Series are now part of Cisco Small Business. For
    discussions about this product, please go here.

  • MacBook Pro 15-inch Mid 2009 failed to boot with internal display

    Hi all, we recently received a MBP 15-inch, this unit won't power up, upon power up, we can hear half boot chime and immediately the unit will power off.
    We manage to get it booted by removing the internal LVDS connector. Video out to DVI and Dual-link DVi tested to work flawlessly. We've done ASD on it and the following are flag failed:
    Video Controller Internal: Gmux switch to EG and Verify (test #41) - Gmux switch to EG and Verify
                        - test will switch display to EG and Verify
    ERROR -- 28 [Mux switching Failed...Didn't switch error] -- TEST FAILED
    Video Controller External (test #41) - Gmux switch to EG and Verify
                        - test will switch display to EG and Verify
    [16:21:16]           ERROR -- 28 [Mux switching Failed...Didn't switch error] -- TEST FAILED
    [12/31/00 16:21:16]           Video Controller External (test #2) - OpenGL Point Test
                        - Render Points
    [16:21:16]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:16]           Video Controller External (test #3) - OpenGL Line Test
                        - Render Lines
    [16:21:16]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:17]           Video Controller External (test #4) - OpenGL Triangle Test
                        - Render Triangles
    [16:21:17]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:17]           Video Controller External (test #5) - OpenGL Quad Test
                        - Render Quads
    [16:21:17]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:17]           Video Controller External (test #6) - OpenGL Quad with Texture Test
                        - Render Quads with Textures
    [16:21:17]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:17]           Video Controller External (test #7) - OpenGL Rectangle Test
                        - Render Rectangles
    [16:21:18]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:18]           Video Controller External (test #8) - OpenGL Cube Test
                        - Render Cubes
    [16:21:18]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:18]           Video Controller External (test #9) - OpenGL Cube with Fog Test
                        - Render Cube with Fog
    [16:21:18]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:18]           Video Controller External (test #10) - OpenGL Wireframe Model Test
                        - Render Wireframe Model
    [16:21:19]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:19]           Video Controller External (test #11) - OpenGL Solid Red Model Test
                        - Render Solid Red Model
    [16:21:19]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:19]           Video Controller External (test #12) - OpenGL Solid Red Model with Fog Test
                        - Render Solid Red Model with Fog
    [16:21:19]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:19]           Video Controller External (test #70) - Fragment Instruction Test
                        - Tests each instruction of the ARB fragment program instruction by doing calculation and comparing actual against expected
    [16:21:20]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:20]           Video Controller External (test #71) - Vertex Instruction Test
                        - Tests each instruction of the ARB vertex program instruction by doing calculation and comparing actual against expected
    [16:21:20]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:20]           Video Controller External (test #72) - Fill Rect 2D Acceleration Test
                        - Tests hw accelerated fill rect by filling screen with many rects, calculating checksum, and comparing actual against expected
    [16:21:20]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:20]           Video Controller External (test #73) - Copy Region 2D Acceleration Test
                        - Tests hw accelerated copy region by copying various size of regions many times, calcuating checksum, and comparing actual against expected
    [16:21:21]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:21]           Video Controller External (test #74) - Copy Rect 2D Acceleration Test
                        - Tests hw accelerated copy rect by copying various size of rects many times, calcuating checksum, and comparing actual against expected
    [16:21:21]           ERROR - 80000003 [Unsupported] -- TEST FAILED
    [12/31/00 16:21:21]           Video Controller External (test #94) - PCIe 16 Link Width Verification Test
                        - Verifies that the pcie link width is 16
    I wonder any of you faced similar issue? What was the diagnose result? Did you send to any out of warranty repair? Reflow? Re-chip?
    We suspecting GPU failure, but then the unit is working totally fine switching from 9400M and 9600M no issue. Even pushing it with 30-inch external display now have yet to yield any performance issue. It's still a very good Mac with 2.8GHz and 8GB RAM. Any input to help on the recovery would be great.

    These are user to user forums, your describing a serious hardware issue that needs to be serviced by Apple.
    Good luck and I hope your issue gets resolved.

  • Mac mini dosnt boot with the programmer

    i use some minimacs with automatic boot every day. But one dosn't start yesterday. it is blocked. I started manually and woked again. What is the cause? solution?
    Can be a power supply fail ? on/off in few secons?
    there is any update solution or option to put of this kind of protection?
    i haven't acess to the minimac every time that this happend...
    thanks,
    /a

    Hi Peggy
    Thanks for your reply and information.
    However maybe I wasn't very clear about what I was asking.
    My Mini has only Windows 7 installed on it and I'm not trying to get OS X installed.
    I know I could auto boot  at a specific time if I had OS X installed and this maybe my only option, but it needs only Windows 7 on the Mini.
    I was wondering if there is a way to auto boot the Mini without OS X.  I can do this with a regular PC BIOS, but was wondering if there is a solution for Windows 7 on a Mini.
    So really this isn't a Mac Mini question but a Bootcamp/Windows problem.

  • My macbook pro (13 in, mid-2010) failed to boot with single beep. Reset PRAM, now it's working normally. Should I still be worried/take it in?

    Okay so my mbp has had a couple minor freakouts lately, particularly while streaming video (the screen would turn one solid color and the only solution was to reboot) then today I opened my laptop and was in the process of entering my password when the screen shut off. The computer attempted to reboot, failed, told me there was a problem and it was trying again, and a bunch of weird text appeared over the gray boot screen. I turned it off, and when I tried to turn it back on again, it wouldn't boot and instead emitted a low beep once every 5 seconds accompanied by a flashing light on the front. I read that it was a RAM problem so I did the hold down P R command control (or something) and restarted it and now it's working normally.
    But should I be worried? Should I still take it in? Is there some sort of memory diagnostic I should run?
    Any help would be appreciated.

    Which model MacBook Pro do you have (e.g., "15-inch Late 2011")?
    Oops! Should have read the header! There are no known issues affecting that particular model and I would only take it in for testing if it begins to exhibit similar problems again. You may have 'fixed' it with a NVRAM reset. But just be on the look-out for further glitches and, if they occur, then take the machine into your local Apple Store or AASP.
    Clinton
    Message was edited by: clintonfrombirmingham

  • Windows 8.1 fails to boot with error code 0x5c after moving physical drives

    Hi,
    i just rearranged hard drives on my desktop PC. I removed 4 RAID drives, installed a single drive and reattached all drives into different SATA connectors on the motherboard.
    After this, my PC doesn't boot. IT always fails with errorcode 0x5c. My OS is on SSD drive, which was not part of the RAID drive so it should boot up just fine - except it doesn't.
    I've tried safe mode, I've tried starting with driver signature enforcement disabled - but it never does boot up properly.
    What else do i do apart from reinstalling the OS?

    Hi,
    This error 0x5c indicates that the HAL initialization failed. A hardware abstraction layer (HAL) is an abstraction layer, implemented in software, between the physical hardware of a computer and the software that runs on that computer.
    It seems that the issue can be cause by interface compatible. Please enter BIOS and change SATA to AHCI to see what’s going on.
    Also, I suggest you arrange your 4 RAID drives back to original SATA connector and connect the new single drive to another to check the results.
    Hope this could be helpful.
    Kate Li
    TechNet Community Support

  • Mac Mini 2014 Boots With Black Background/White Apple

    Mac Mini Specs: 2014 Model with 2.6GHz processor, 8GB RAM, 1TB HD, Intel Iris Graphics, Mini-Display Port to DVI adapter with Dell monitor
    Issue: When booting the Mac Mini up it goes through a very standard Yosemite boot but the background is black and the apple and progress bar are both white.  The issue is entirely cosmetic in nature and doesn't seem to have any negative effects.  What I normally expect and have seen in 30+ macs upgraded to Yosemite is the same loading but with a grey screen.  It's worth noting that I have noticed this issue on 2 iMac 2010s that had been upgraded to Yosemite that belonged to some friends, but their issues were intermittent or fixed.
    Steps Taken:
    Updated from 10.10 to 10.10.1 and installed all other available updates
    Checked the Start-up Manager, Recovery, and Internet Recovery.  All have black backgrounds and internet recovery's globe is small then normal.
    Reset SMC and NVRAM
    Tested Safe Boot
    Erase and Reinstall OS X
    Removed all peripherals except monitor
    Tested another monitor and DVI cable
    Tested HDMI without the adapter
    Replaced Mac Mini with new Mac Mini
    Questions:
    1. Have you seen this issue before and what are the specs of the device it occurred on? (OS, Model, Year)
    2. I wonder if this might be expected but can't find anything to reference that it would be and didn't get any answers even when asking people at the store or over the phone.  Have you seen any articles/pages that talk about this issue?
    3. Can you think of anything else to try and resolve this?

    This is normal for the newer machines running Yosemite. There's nothing wrong.

  • Mac mini safe boot with bluetooth keyboard

    I have a mac mini running mac os 10.6
    Cannot boot my mac mini. When I start from CD and run disk utility i am getting following error msg: "invalid b-tree node size"
    Seems to be a fs problem and not hw. Safe boot might solve the problem :  )
    Now i am trying to do a safe boot but no success so far. I am having a bluetooth keyboard and mouse.
    Holding down shift key and power on is not working but holding down cmd&s for single mode or holding
    down c for booting from cd is working.
    Any ideas?
    Cengiz

    lazom wrote:
    I have a mac mini running mac os 10.6
    Cannot boot my mac mini. When I start from CD and run disk utility i am getting following error msg: "invalid b-tree node size"
    That message indicates that one or more of the directories on the drive has become damaged. Disk Utility can usually diagnose such problems, but not repair them.
    Suggest you get a copy of Alsoft's DiskWarriot. DiskWarrior can usually fix such problems with no loss of data. There's no need to install DiksWarrior - boot the machine to the CD and run DiskWarrior from that.
    http://www.alsoft.com/

  • Mac Pro only booting with option key down

    I have an 8-core mac pro that is great except for some odd booting issues. I have 3 internal drives, one with OSX 10.4.9 on it, the other with just files and the last with windows XP. I also, at times, have USB drives (or an iPod) plugged into the mac. When I restart, even if I have selected a boot volume in the startup settings, the machine will just go black. Sometimes it will play the startup chime multiple times, other times only once or not at all. The only way to get it to boot up into osx or windows is to hold down options. Even then, it only seems to work if I unplug all external drives from the machine. Any ideas whats going on or how I might fix this?
    Thanks!

    If you remove all of your USB/FireWire devices will your start up issue go away. What about resetting PRAM…
    http://docs.info.apple.com/article.html?artnum=2238

  • Laptop fails to boot with battery

    Probably the wrong subsection.. :3
    Okay, so I have a Toshiba satellite l735-m14t running windows 7.
    The problem started when I used CCleaner to clear out registry entries of uninstalled applications. Everything was running fine until I restarted. I can't connect to any network (ethernet/wifi/ad-hoc) after I restarted, so I foolishly restored what was apparently the latest backup of my registry, which is 6 months old (I have no saved image files to restore back to, so really had no choice). So I thought everything would run smoothly again but I soon discovered that my laptop started off restarting randomly between processes. Then a week after it started to do it even more. I can still boot it up when the adapter is plugged in, but it still does happen, but when I boot unplugged, after the Windows screen I just hear one click, then it restarts. When I plug in, boot, then try to unplug, during the 10 seconds in which it automatically restarts, the fan becomes noisy and the laptop becomes hot.
    I read that it is apparently a hard drive failure. This Hard Drive has already been replaced once due also to a faulty hard drive. I also received three blue screens since about 2 weeks ago when this started happening. I don't know if the registry entries were the cause or it was just coincidence.
    I've tried making another administrator account and the problem still persists. Also tried checkdsk, windows memory diagnostic for 4 hours, scanning for viruses, malware, but no results so far. I just want to know if I need to backup my files and take it back in for another replacement. ..
    Also, can someone help me in booting to the freakin BIOS. whenever my laptop boots up, I see no prompt to press a function button to change boot settings, just a black screen with a cursor (?) like the one in cmd. I would like to try troubleshooting using a BootCD, but I can't access the BIOS. (tried f1-f12, esc, spacebar, tab, enter, and del, none works),

    BUMP!
    Okay, so I've found out I can boot unplugged to safe mode, but not in normal mode. So I tried boot logging, can somebody take a look in here for me. So many unloaded drivers.
     Also, I've tried HWSetup and moved ODD as first in the order. It won't boot the CD and just directly goes to booting from the Hard Drive. Still can't access BIOS though.
    EDIT: Uploaded another log file. (deleted the original then rebooted.)
    Attachments:
    ntbtlog.txt ‏565 KB
    ntbtlog.txt ‏149 KB

Maybe you are looking for