Blue screen on DVI

have a problem today with a blue screen on dvi connection using original mac mini and syntax olevia 30". was fiddling around in displays earlier and saw a higher res display that syntax manual said dvi could handle, so said "hey, wonder if that'd work?". four hours later, still cannot get dvi connection to work again. connected to antique vga monitor-works, reset to 1024X786 60 HZ. works using vga to syntax. but cannot get dvi to work again. reset the pram using PR+optioncontrol. tried other resolutions, somtimes get out of frequency on old vga monitor-says at 75 hzs when settings are 60 hz. pleas help get rid of that darn blue screen on dvi. thanks.

I got it to work finally by abanding trying to set it up through the vga monitor, setting up directly through the DVI connection. First disconnect all USB and firewire stuff-except keyboard and mouse and monitor. then start up in safe mode:
shut the computer down. Press the power button. Immediately after you hear the startup tone, press and hold the Shift key. Release the Shift key when you see the gray Apple and progress indicator (looks like a spinning gear).
this will get you into the directconfigX control panel, if not,you may have to do it on VGA first. Then set the screen to the specs on directconfigX for you monitor, I looked online and in the LCD owners manual for good specs. setting up on vga first worked for the VGA but the computer wouldn't transfer that info for the DVI. For the most part, I couldn't get a grey screen at all without unplugging all accessories and starting in safe mode, starting holding down the "C" never worked either. The directconfigX seems to be running it pretty smoothly for the last couple weeks, even tried an out of spec resoluions and it didn't screw it all up again.
Mac Mini 1.42   Mac OS X (10.4.6)   imac-dv G3, mac3500, mac7500, apple IIe, ipod nano

Similar Messages

  • Mini DVI to Video: blue screen after disconnect

    Hi,
    can't find a solution: after disconnecting the mini dvi to video-adapter I always get a blue screen and I need to restart my brandnew 20" iMac.
    I use it to connect my (old) television via s-video. It is clear that I bought the right Mini-DVI-Adapter.
    Can anyone help or has the same problem?
    iMac 20"   Mac OS X (10.4.8)  

    Thanks for the help. I'd figured out that shutting it off would keep it from happening and was probably a "best practice," but since 90% of my television watching is from my eyeTV, I'd be turning it on and off a lot.
    The only problem with leaving the setup plugged in, is that as soon as the mini DVI cable is plugged in, the resolution on the iMac resets itself to super-large fit for television mode and becomes virtually unusable as a computer, thus when I want to use my computer, the cable has to be unplugged....unless of course you know something I don't
    Thanks,
    Shaun

  • Radeon 9800 pro 256mb hanging on blue screen

    I'm deep in the waters of frustration right now, and am hoping someone here might have the answer.
    About 3 months ago I was looking for a video card for me to run motion. I saw the 9800 mac special edition with 128mb video ram had rave reviews. At that time ATI was not making them. So I turned to eBay...
    I purchased a card that was advertised as a Mac 9800 pro special editing 128mb. I later found out it was a flashed pc card. The ebay seller told me the card worked fine on all his mac's that he tested it on.
    The problem I was having was the machine boots up, I see the grey screen with the Apple logo and spinning wheel. I see the blue screen where normally I see the login progress bar loading the OS. But with this card I only see the blue screen. I hear the hard drive churning, so I am assuming it is still loading the OS, but I cannot see anything. I can reboot in safe mode and the video card works fine.
    Well... I assumed it was the fault of the card and that it was flashed. I returned the card to the ebay seller, who sent me another one, same results with that one. I returned the card to the seller and he refunded my money.
    I put the money toward the just released Radeon 9800 Pro Mac Edition 256mb card. I just got it a couple days ago and am experiencing the same problems. I have tried everything... everything I know and still can't get the card to work? Here is a list of what I have done:
    With the flashed card:
    1. Shut off computer and unplugged it. Removed OEM video card and installed ATI 9800 card. Plugged the power supply cable for the card into the computer power supply cable and hard drive.
    Problem Occurs: When starting up, the grey screen comes up with the Apple on it, then the screen turns blue, where I typically would see the progress bar of the system loaded up before the user login screen. I only see a blue screen at this point but can hear the hard drive working for about a min.
    2. Restarted the computer in safe mode.
    3. Logged in as Admin user and opened the ATI preference pane to verify it sees the card.
    When the ATI preference pane was loaded the following error message occured:
    A startup problem has occured.
    Cannot connect to ATI TVOut Kernal Extension. Some features are not available.
    Clicked OK and the ATI preference pane appears.
    4. Close the preference pane and reinstalled ATI Displays 4.5.6. Restarted computer.
    Problem Occurs
    5. Restarted computer holding down AppleOption+PR to clear PRAM. Cleared the PRAM 4 times in a row, by allowing the chime to happen 4 times.
    Problem Occurs
    6. Shut computer down. Disconnected the DVI plug for the cinema display and connected a VGA CRT monitor. Started computer.
    Problem Occurs
    7. Shut computer down, disconnected the VGA CRT monitor. Reconnected DVI plug and restarted computer.
    Problem Occurs
    8. Started the computer in safe mode. Logged into admin account. Opened the ATI Preference pane.
    When the ATI preference pane was loaded the following error message occured:
    A startup problem has occured.
    Cannot connect to ATI TVOut Kernal Extension. Some features are not available.
    Closed preference pane.
    Went to ATI site and downloaded:
    aug2005-radeo-universal-rom-update.dmg
    Ran the updater.
    Restarted computer.
    Problem Occurs.
    9. Restarted the computer in safe mode. Changed the login preference pannel to automatically log into the administrator account. Restarted computer, waited for the blue screen, then walked away for about 2 hours with the computer on blue screen, hoping the system was loading or doing something.
    Problem Occurs.
    10. Put in the TechTools Pro CD, hoping to run some tests on the video card from the cd. When booting from the CD OS...
    Problem Occurs.
    11. Enabled Root user. Logged in as root and installed ATI Displays 4.5.6 from there. Restarted computer.
    Problem Occurs.
    12. Shut down computer and installed old video card.
    13. On an internal hard drive in the computer. Wiped the drive and formatted it. Installed 10.4.1 on the drive. booted up into the drive, installed ATI drivers, shut down computer, installed 9800 pro video card, booted up.
    Problem Occurs.
    With the new 9800 for Mac ATI card with 256mb:
    With original card, install drivers, repairpermissions, shut down, install new card
    Set to restart in single user, give 5 min to see if ATI monitor startup item in user starteputems loads
    Hooked VGA & DVIt in together, both showed blue screen
    Reset NVRAM via open firmware
    Reset cuda button
    Take battery out, wait at least 10 min, re-install new battery, press cuda button
    Reinstall ATI update 4.5.6
    Reset nvram from open firmware
    In ATI control panel, selected 'Force Single Display Operation'
    Change display scaling to 50%
    Download latest Mac OS update from apple & reinstall
    Help?

    I get dizzy just thinking about it.
    I have tried installed a brand new OS, 3 different times on a different Hard Drive, still the card doesn't work.
    I had one person suggest that it may be the card is not communicating with the OS Window Drawing module? (excuse my ignorance of what that is really called. I just know there is some program, possibly in the kernel, that is responsible for drawing out the OS windows.)
    How can we rule out that it is a bad AGP slot?
    •The slot works fine with my 9000.
    •It works in safe mode with the 9800.
    •I have installed a brand new OS, three different times, still doesn't work.
    •I have used Apple Hardware test to test my hardware, the AGP slot didn't report any problems.
    I am assuming that the AGP slot is working. Although I worry about it a bit, because by now I have swapped cards in it about 50 times in my troubleshooting.
    Here is a link to a complete list of everything I have tried:
    http://www.macosx.com/help/qview.php?questionid=19554#54138

  • Why does my Mac Pro randomly flash a blue screen to both monitors?

    For a while now my Mac Pro (Early 2009) has this occasional issue. The system uses a pair of ViewSonic 22" monitors. At random times, both monitors just turn to a solid light blue color. After a brief time (1 to 5 seconds maybe) normal operation returns. The system is still working. Text typed on the keyboard during the 'blue' screen still shows in whatever application I'm in. Just the screen seems to be affected.
    I leave the system running 24/7 with only occasional reboots (weeks or months apart). The screens I turn off at night. Most of the time this happens right after the system 'wakes' in the morning (temperature does not seem to be a factor). Although the system is doing this as I'm typing this. The blue screens show up than go away on their own. This repeats from one to ten times before it goes away. Once it is 'done' everything is normal until it happens again.
    This 'issue' has been occurring since the original Snow Leopard. But, it also happened with Lion and now still happens with Mountain Lion (just upgraded to 10.8.2).
    I am thinking this has something to do with the graphics controller (NVIDIA GeForce GT 120 512MB). But, I've never found any online references to this sort of behavior.
    Any comments or suggestions will be appreciated.

    The cable connections have (so far) solved this problem for my situation. Even though the monitor's DVI cable was firmly connected to the mini Display port connector, when I touched it the attached monitor would go 'blue' or lose its connection entirely. After disconnecting and reconnecting this junction the monitors would still take a hit on touching the connection. I also checked the connection of the mini Display port connection to the graphics board and could not push it in any further. However, after a second go-round I unplugged this connection to the board and reconnected it. I am certain it was fully inserted the first time. But, connection contacts can oxidize over time and sometimes it may just need to be disconnected and reconnected to 're-wipe' the connections. This effectively cleans them at the point of contact. So in my case I'm thinking it was the connection age that was an issue more than a 'loose' connection. Either way, I haven't had this issue for the past two weeks.

  • Encore CS4 Missing Frames/Stops Starts  and Blue Screen Crashes During Playback

    I'm opening Premiere Pro CS4 with the default presets of HDV Capture, HDV 1080i30 software only mode. I'm capturing from my Canon HV20 using firewire HDV out 1440 x 1080. All goes well during the editing process but when I Dynamic Link and playback in Encore CS4 I observe dropped frames or stop and starts in Encore timeline sequence. At times I may even crash Encore with a Blue Screen. While still running Encore I can go back to Premiere Pro and play the timeline sequence with no issues. I will mention that I have the Matrox RT.X2 installed. But when starting a project I'm doing software only and disabling RT.X2 hardware playback. If I remove all effects in the timeline sequence and then Dynamic link to Encore the playback is normal with no effects. I did exported the Premiere Pro CS4 project using Adobe Media Encoder CS4 with a setting of MPEG 2 Blu-ray 1440 x 1080i 29.97 High Quality. I than import this MPEG2 back into Adobe Encore CS4 and it plays without dropping frames or hang-ups.
    Build
    Case: Coolmaster-830
    Op System: Vista Ultima 64 Bit
    Edit Suite: Adobe Creative Suite 4 Production Premium Line Upgrade
    Adobe Premiere Pro CS 4.0.1 update before installing RT.X2 Card and 4.0 tools
    Performed updates on all Adobe Production Premium Products as of 01/12/2009
    Matrox RTX2 4.0 Tools
    Main Display: Dell 3007 30"
    DVI Monitor: Dell 2408WFP 24"
    MB: ASUS P5E3 Deluxe/WiFi-AP LGA 775 Intel X38
    Display Card: SAPPHIRE Radeon HD 4870 512MB GDDR5 Toxic ver.
    PS: Corsair|CMPSU-1000HX 1000W
    CPU: INTEL Quad Core Q9650 3G
    MEM: 2Gx4|Corsair TW3X4G1333C9DHXR DDR3 (8 Gigs Total)
    1 Sys Drive: Seagate Barracuda 7200.11 500GB 7200 RPM 32MB
    Cache SATA 3.0Gb/s
    2 Raid 0: Seagate Barracuda 7200.11 500GB 7200 RPM 32MB Cache SATA 3.0Gb/s Using Intel's integrared Raid Controller on MB

    Try to remember this:
    Encore "Tries" to playback from premiere pro.  If you have a full set of previews available, it will play those, but you are probably seeing a lot of dropped frames and choppy video if your previews in premiere are set pretty low.  What you can do to combat this--in my experience--is export your video from premiere into a whole file in full format (in a non-lossy format with full frames, and in it's proxy equivalent;  I use Prores LT for many projects, and export that as a final output from premiere), then have that encode in an h.264 format (which will maximize smooth motion and quality playback).  Now... ...In your encore project, you should be outside of your original formats and in the intermediary that encore will recognize, so you should have it "Locate transcoded file".  Once you have done so, it will playback that movie in the preview.  I've done it.  With CS6 and 4gb ram with a vidcard at 256mb and a core2duo 2.16ghz, it plays fine.  With CS4 the encoding takes a while, and if you go to dvd, even longer for compression to work properly.  I use Compressor to output AVCHD .264 stream and an AC3 file.  When I locate the transcode for BD, I locate the .264 file first, then I get asked for the AC3 file.  This allows me to import them both, and have Encore encode them into the transport stream without transcoding.  I use Distributed processing to get the job done quickly, as I have minimal access to several computers and have connected them by that method for a Render Farming setup.  It works well.  With a hardware based device playing back your files, you won't see the same performance in Encore.  It has to make two hops already to get to your video, and adding a third (goes from encore to Premiere, then to codec, then plays normally;  third step is to external hardware, which eats up processing like crazy when it has to come all the way back to an encoding output to screen through encore, adding more steps for the system along the way) really can slow down the performance in Encore.  IF you take the Steps out by encoding a finished playback stream, Encore will handle it quickly with it's own processing.  It really does work well.  If you don't like it, make your changes in Premiere, then re-encode with your hardware and make an h.264 file for encore again.  You can use AME, but you'll always get standard Blu-ray (old file-stream format; lesser res and quality).  You can use Compressor to make AVCHD which allows for 264 output that is PSF or progressive that is interpreted as simultaneous fields (fake interlace), or even solid progressive formatting for AVCHD compatible players, and you can render-farm it to speed up the encoding process.

  • Lightroom 4.1 (3, 4 or any version) causes computer to blue screen and crash

    Recently bought the new Lightroom 4.1 in an attempt to fix this issue, which had been occuring off and on for some time.  I have major difficulties with importing and/or rendering previews or editing Canon 5D Mark II and Canon 5D Mark III images using Lightroom.  The computer abruptly blue screens, then reboots.  The blue screen code is 124.  I'll attach a record of minidumps (all caused by editing or importing images using LR4.)
    Not sure if that can be viewed, but please ask so I can send you the dump file for inspection if necessary.  It essentially shows the Bug Check Code as 0x00000124, caused by address ntoskrnl.exe+4b09bc.
    System Information
    Time of this report: 6/14/2012, 02:40:11
    Machine name: THANATOS
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.120401-1505)
    Language: English (Regional Setting: English)
    System Manufacturer: System manufacturer
    System Model: System Product Name
    BIOS: BIOS Date: 12/09/10 21:08:39 Ver: 08.00.15
    Motherboard type is a Asus Crosshair Forumla IV
    Processor: AMD Phenom(tm) II X6 1100T Processor (6 CPUs), ~3.3GHz
    Memory: 16384MB RAM
    Available OS Memory: 16382MB RAM
    Page File: 2892MB used, 29870MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7600.16385 32bit Unicode
    Display Devices
    Card name: NVIDIA GeForce GTX 580
    Manufacturer: NVIDIA
    Chip type: GeForce GTX 580
    DAC type: Integrated RAMDAC
    Device Key: Enum\PCI\VEN_10DE&DEV_1080&SUBSYS_15803842&REV_A1
    Display Memory: 4063 MB
    Dedicated Memory: 1503 MB
    Shared Memory: 2559 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)
    Monitor Name: Generic PnP Monitor
    Monitor Model: SMBX2450
    Monitor Id: SAM0722
    Native Mode: 1920 x 1080(p) (60.000Hz)
    Output Type: DVI
    Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 8.17.0012.9610 (English)
    Driver Version: 8.17.12.9610
    DDI Version: 10.1
    Driver Model: WDDM 1.1
    Driver Attributes: Final Retail
    Driver Date/Size: 2/29/2012 20:02:00, 17642816 bytes
    WHQL Logo'd: Yes
    WHQL Date Stamp:
    Device Identifier: {D7B71E3E-53C0-11CF-787E-8C351FC2C535}
    Vendor ID: 0x10DE
    Device ID: 0x1080
    SubSys ID: 0x15803842
    Revision ID: 0x00A1
    I have an 850W PSU.  Running Windows 7 Ultimate on a 150GB SSD.
    I find this very frustrating because it's a PC that I built and that can do any complex task--anything from using PS CS4 with multiple layers, playing top-end games like Crysis 2 and Diablo 3 with graphics on full.  Other than this RAW development issue, the computer is flawless and VERY fast.  Anyone have any ideas, or see a hole in the system specs?
    Cheers,
    _E

    The video driver is up to date, and I would assume compliant with LR4.
    My BIOS version is default, and I tried installing new BIOS updates but ran into troubles.  The Asus motherboard uses ATI Catalyst to introduce new system updates, but it fries my PC (assuredly a conflict with my nVidia card) making the rig run even slower.  In fact, using the ATI Catalyst disc (the one that came with my mobo) crashed once I had tried to install any motherboard utilities!  I've gone through the BIOS configuration and turned off all of this mobo's overclocking features and set everything to default.
    No overclocking going on whatsoever--not once, and never will.
    Reseated the memory and tested the memory with no negative feedback.
    The PSU is relatively new and of high quality.  I replaced an old PSU because of exactly what you mentioned above.  It's a Corsair GS800 (not 850W, 800W).
    I'm at the point right now where I suspect the motherboard is failing me somehow.  I only bought it because I was in a rush and would have normally opted fro a "non-overclocking-enthusiast's" board.  Perhaps there's a way of updating BIOS without utilizing the disc (the ATI Catalyst, more to the point?)
    The PC is new in a sense.  I seem to recall a point where LR3 worked with fewer crashes.  I built the thing April 2011.  Just reinstalled Windows 7 and all the software again.

  • Blue screen when booting from USB drive in UEFI mode (2013.07)

    SOLUTION for me was to update the firmware on my ASRock mb as thatu pdate changed the EFI software (by American Megatrends) version from 2.00 to 2.31. However, other users are still experiencing the blue screen.
    SHORT VERSION
    When I try to boot Arch Linux 2013.07 with an USB drive in UEFI mode (for installation), I get a blue screen (which is rather a literal description and not a hint towards the old Windows' one) with the message
    Failed to install override security policy (14): Not found
    LONG VERSION
    I made an USB installation media (product: Intenso Rainbow) by following this advice on the wiki.
    I used the july release of Arch for that. First of, after installing the image to the USB stick I found that I needed to correct the label in the archiso-x86_64.conf file to ARCH_201307 (or was it the label of the usb stick, can't remember right now). (Pretty sure it was the same problem with "Linux Live USB Creator" which I used 3-4 months ago...)
    After doing that, I rebooted and selected the entry
    UEFI Intenso Rainbow
    from this list of entries:
    SATA HDJ ... something (the hard drive where Win 7 64 bit is installed with all programs)
    SATA something (hard drive which only contains data)
    Windows Boot Manager
    USB: Intenso Rainbow
    UEFI: Intenso Rainbow
    It went to a blue screen with a message in white text saying
    Failed to install override security policy (14): Not found
    Below that was an OK button which had a black rectangle over it.
    After I experienced the bluescreen, I tried booting the
    USB Intenso Rainbow
    entry and the boot process then worked fine, I got to that Arch menu where I could choose
    Boot Arch Linux (x86_64)
    Boot Arch Linux (i686)
    Boot existing OS
    Run Memtest...
    and so on...
    But just to make sure, I then did the check for UEFI mode according to this and only saw a folder acpi and ... something else I can't really remember, but it definitely was not efi. Thing is, I needwant to boot into UEFI mode as I have Win 7 already installed in UEFI mode.
    Some info about my motherboard: it's from ASRock and is called H67M. The BIOS is dated to 2011-10-26 and is version 1.7.
    So far, I only found a mention of the problem here at superuser.com.
    Last edited by jones (2013-07-15 07:15:18)

    Ok then, so this thread has also become about the blank screen problem when booting (in this particular case, Arch 2013.06 since 2013.07 seems to be worse).
    srs5694 wrote:Typically, you adjust kernel boot options using your boot manager or boot loader. In GRUB, you hit the "e" key to open an editor. In rEFInd, you hit F2 or Insert twice. I don't recall offhand what key does the job for gummiboot (which I'm pretty sure the Arch installer uses), but I'm certain it's got the feature.
    You are right. Thanks. I realized I had the gummiboot config right in front of me all the time. It's the file 'archiso-x86_64.conf' in \loader\entries (on Windows).
    An addendum: I think the USB: Intenso Rainbow boot option takes me into a GRUB menu. Hitting 'e' in this "big" and fully designed menu didn't do anything IIRC. Hitting 'Tab' did the trick to get into editing the boot command line.
    Hitting 'e' worked in the gummiboot menu though.
    So I tried booting with the following options (also by combining some of them)
    nomodeset
    acpi_backlight=vendor
    radeon.modeset=0 (I have a Gigabyte 7870 card in this desktop machien)
    i915.modeset=0
    but it did not help.
    To be rather safe than sorry: I should mention that there are two grey-ish bars visible on the top and bottom of the screen after I try to boot the first entry, Arch Linux archiso x86_64 UEFI USB. Always has been with those two older Arch version (2013.05+2013.06). I also found another thread where one user talks about using the VGA port of the monitor, which I am currently not, I am using the DVI one, so that's worth a try too. EDIT It did not help either. What I did was setting the primary graphics adapter in the UEFI north bridge configuration menu to 'onboard' which worked immediately when rebooting (I hit the button labeled "Source" on my monitor and it showed it is using the "Analog" mode), but the problem just stayed the same. Adding aforementioned boot options or a combination thereof did not change anything.
    Thanks for the e-mail addresses, I sent one to James Bottomley.
    Last edited by jones (2013-07-07 11:12:05)

  • Belkin Flip KVM Switch and Blue Screen

    G5 Dual 2ghz, clean install of Leopard.
    I have a dual head video card, attached to the DVI port is a 22" monitor connected via DVI, on the ADC port I have ADC to VGA adaptor which a Belkin "Flip" KVM switch is attached, leading to a 17" monitor.
    On booting I get to the point when the Finder should be loading and get a blue screen on both monitors, the monitors both periodically do a fade from black as though the system has just tried to change video resolution. However this loop continues.
    If I remove the KVM and have the 17" plugged in, boot up is fine. This set up worked fine with 10.4x.
    Any suggestions.
    Thanks

    Zork, have you cracked this problem yet?
    I have a similar item - Belkin's Switch2 for Mac mini - and I get the same halting at the blue screen. Belkin UK's 2nd line support failed to replicate this error and replaced my device with the one that they used. It failed as well on my system (which works fine without the Switch2!).
    In case it helps, a dig in the logs showed the following fault repeating itself presumably while the screen stayed blue:
    (starts 6 lines down, I think)
    01/05/2009 10:12:25 com.apple.SystemStarter[29] kextload: /Library/Extensions/VBoxDrv.kext loaded successfully
    01/05/2009 10:12:25 com.apple.SystemStarter[29] Loading VBoxUSB.kext
    01/05/2009 10:12:25 com.apple.SystemStarter[29] kextload: /Library/Extensions/VBoxUSB.kext loaded successfully
    01/05/2009 10:12:25 com.apple.SystemStarter[29] Loading VBoxNetFlt.kext
    01/05/2009 10:12:25 kernel vboxdrv: fAsync=0 offMin=0x1230 offMax=0x39450
    01/05/2009 10:12:25 kernel VBoxDrv: version 2.1.4 r42893; IOCtl version 0xa0009; IDC version 0x10000; dev major=18
    01/05/2009 10:12:25 ReportCrash[110] Formulating crash report for process WindowServer[68]
    01/05/2009 10:12:25 com.apple.SystemStarter[29] kextload: /Library/Extensions/VBoxNetFlt.kext loaded successfully
    01/05/2009 10:12:26 com.apple.launchd[1] (com.apple.WindowServer[68]) Exited abnormally: Floating point exception
    01/05/2009 10:12:26 kernel VBoxFltDrv: version 2.1.4 r42893
    01/05/2009 10:12:27 kernel AirPort: Link Up on en1
    01/05/2009 10:12:28 ReportCrash[110] Formulating crash report for process WindowServer[116]
    01/05/2009 10:12:28 com.apple.launchd[1] (com.apple.WindowServer[116]) Exited abnormally: Floating point exception
    01/05/2009 10:12:28 com.apple.launchd[1] (com.apple.WindowServer) Throttling respawn: Will start in 9 seconds
    01/05/2009 10:12:30 ReportCrash[110] Saved crashreport to /Library/Logs/CrashReporter/WindowServer2009-05-01-101214GottaLight-2.crash using uid: 0 gid: 0, euid: 0 egid: 0
    01/05/2009 10:12:30 ReportCrash[110] Saved crashreport to /Library/Logs/CrashReporter/WindowServer2009-05-01-101227GottaLight-2.crash using uid: 0 gid: 0, euid: 0 egid: 0
    01/05/2009 10:12:38 ReportCrash[121] Formulating crash report for process WindowServer[120]
    ...and repeats it every 9-10 seconds.
    Do/did you get this as well?
    Can anybody comment on what is going on, please?

  • External display no longer working - stuck at blue screen

    Hi everyone. I just don't know what in the bloody **** happened here.
    Everything was working fine, I even had my macbook 13 upgraded to 10.5.6 and it always worked fine with my external DELL 2007WFP screen thru DVI cable and miniDVI adapter.
    Suddenly when I got home today and plugged the miniDVI adapter, I saw the screen blinking forever at the blue screen that usually fades out to both screens with extended desktop turned on.
    If I unplug the miniDVI adapter, everything gets back to normal on the macbook screen. I plug it again, I get the blinking blue screen.
    Tried rebooting, unplugging everything else from the external screen, no luck.
    If I boot the macbook with the external screen on and the macbook closed, then it is recognized fine and I can use it, but when I want to use both screens, it will blink again.
    I need to use both screens as that's how I arranged my workspace.
    Again, everything was working fine yesterday.
    Thanks

    Did you ever figure out what was doing this, and more importantly, did you get it fixed? I have the same thing happening to my macbook 13. It has worked fine in the past with external displays, both mini-DVI to DVI and mini-DVI to VGA, and many types of monitors/projectors. All of a sudden last week, i try to connect to my external monitor and I get the flashing blue - dark blue - light blue - repeat...
    I tried the command-f1 trick to switch displays, and it sits there for a second, my desktop will flash onto the external monitor for a second, and then it'll give up and go back to the repeating blues.
    I ran the hardware test, both the short and the long, to no avail.
    I tried with the lid closed and an external mouse and keyboard. I tried this both from the startup and from when the laptop was already on.
    Any ideas? Time to go to the genius bar?

  • Blue screen

    My MacBookPro has been working great... but now it sometimes freezes to a blue screen. it does not happen at login... but while i am running different programs. it will remain on the blue screen anywhere from a second to a minute, and then return to normal. it happens more frequently when i am connected to the internet.
    i can tell when the blue screen is about to appear, because first the buttons will become unavailible to select, and then the mouse will also freeze. it has been getting progressively worse. Does anyone know what this is?

    I've been having the same problem for the last week or so.
    I'm not starting up or shutting down.
    I tried messing with the energy settings. While I can't get the new settings to stay on restart, the changed settings don't seem to change the problem.
    It's not running hot.
    I hadn't done a software update when it started happening.
    I'm using the same Apple wireless mouse I bought with the computer, the same monitor, and the same DVI adaptor.
    It's not going into or coming out of sleep mode. This happens when I'm using it. I notice it most when I'm checking email in Eudora or using Firefox. I'm using the computer and the screen suddenly goes blue for a few seconds. Then it comes back to the regular desktop and I'm able to resume work. I can't find anything in this usually helpful board that indicates a possible cause or solution. But I'd sure like to! It's getting really annoying!

  • Get the blue screen but the TV doesnt find the signal from my mac via hdmi

    Before my mac could connect to my TV Samsungs LE32B350 without any problem, but now it just keep saying no signal from the tv. I get a blue screen when I connect the hdmi on the laptop for one sec then nothing happens. I have tried search for more screens but aint finding anything.
    Please help me

    Unfortunately older G4 minis are very touchy about certain hi-res monitors when run from DVI. Hi-res in this case means any monitor whose resolution causes the pixel clock to be above 135 MHz. It is normally the case that 1680 x 1050 timing will have a pixel clock above 135 MHz, although there is no way to observe that directly from within OS X.
    There are only two known work-arounds for the issue. One is to run the monitor over a VGA interface. The other is to use a program like SwitchRes X to lower the pixel clock below 135 MHz. If you choose to do the latter, write back if you'd like some guidance on how to do that.

  • Blue Screen 10.5.8 Please Help

    From out of nowhere, I started my PM G5 and get to where the screen turns blue and it stays there rather than getting to the desktop. When it starts up, I don't hear the sound, but the gray screen shows up with the Apple logo and the black pin wheel spins (it takes much longer than normal, usually it will spin 20-30 times now it goes for 80-90 spins) then the blue screen shows up and instead of getting to the desktop, it stays at the blue screen. I've tried rebooting 4-5 times with the same result.
    I am using 10.5.8 with all updates. I have even tried connecting an external hd and holding down the option key to start from that, but it won't allow the screen that shows the available hd's to start from to show up.
    Please help.
    Thanks,
    Bob

    Well, one mystery solved and another new one.
    I ma using a Samsung LCD tv/monitor using the DVI port and a separate audio connection from the monitor to the G5. When I connect the audio line from the monitor to my G5 and restart the G5, there is no chime, either for startup or if doing a PRAM reset. If I leave the audio line disconnected and do a restart, then the chime sounds at startup (the sound comes from the small speaker on the G5) as well as when I do a PRAM reset. What is perplexing is that with the audio line connected, it will play itunes music, QT videos, but will not allow the startup chime. With the audio line not connected, evrything including the chime works.
    Is there a setting somewhere that is causing this.
    Thanks for your help.
    Bob

  • Windows Server 2003 install blue screen crash

    I am attempting to install windows 2003 R2 standard addition on the following system currently running Windows XP.
    PROCESSOR
    Intel® Core™2 Duo 375W,E6550 (2.33GHz,1333Mhz FSB, 4MB L2 Cache, Dual Core)
    edit
    OPERATING SYSTEM
    Genuine Windows® XP Professional, SP2 (NTFS) (+ Media) - English (32bit)
    edit
    TOWER/BASE ORIENTATION
    Vertical Chassis Orientation (Minitower, W: 170,2 x H: 447.3 x D: 468.4 mm)
    edit
    BUSINESS SUPPORT
    No Business Support Required
    edit
    MEMORY
    4GB ( (4 x 1.0GB DIMM) 800MHZ DDR2 ECC SDRAM Memory
    edit
    GRAPHICS CARD
    256MB nVidia NVS 290, Dual Monitor DVI or VGA Graphics Card (ULGA8)
    edit
    HARD DRIVE
    160GB (7,200 rpm) SATA 3.0Gb/s Hard Drive with NCQ and 8MB DataBurst Cache™
    edit
    OPTICAL DRIVE
    48X CDRW/DVD
    The box is a Dell  T3400.
    All the specs fit the server requirments.  Does anyone have any suggestions? 
    Just to summarize.  I'm booting from CD.  The drivers are copied across and when windows attempts to start the blue screen crash occurs.
    Jay

    Hello Customer,
    Thank you for using TechNet Forum, and also many thanks for Aaron's assistance.
    Please note, this forum is for General questions on Windows Server 2008. I suggest you try to post Windows Server 2003 related issue to the Windows Server 2003 Newsgroup for your best serve:
    http://www.microsoft.com/technet/community/newsgroups/serveros/win2003.mspx
    Thanks for your understanding.
    Moreover, the blue screen is mostly caused by hardware or drivers incompatibility. I suggest you take a look at the following website
    If the hardware appear to be on the Hardware Compatibility List (HCL): 
    http://www.microsoft.com/whdc/hcl/default.mspx
    Thanks.
    Best wishes
    Morgan Che
    Microsoft Online Community Support
     

  • Screen fades to blue screen continually (video attached)

    Here is what is going on. On boot the computer would lock up after the spinning gear. Or it seem to. It would get past the apple logo, flash pink for a second and go to a white screen. I could hear the hard drives being accessed but it never seemed to come out of this white screen after waiting 10 or minutes. So I ran the hardware test on this computer. It found no problems, so rebooted and oddly enough I the computer booted fine. However occasionally after being logged in the computer would flash to a blue screen and fade back in. This is the same animation you see when you log into your machine right before you see the desktop. In some cases it will continue over and over (see the youtube link bellow). Even booting off the original restore disc this issue kept continuing. Which leads me to believe its a hardware issue. Ive tried, resting the PRAM, SMC, ran the hardware test a second time, ran a check on the hard drive using disk utility, fixed the permissions, swapped out dvi cables, and changed out the power strip. I am leaning towards it being a video card issue, but i cant be for sure. The problem is intermittent, so its hard to track down. Has anyone seen an issue like this before?????
    http://www.youtube.com/watch?v=jtN6pU0eW5A
    Computer specs:
    Model Name: Mac Pro
    Model Identifier: MacPro1,1
    Processor Name: Dual-Core Intel Xeon
    Processor Speed: 2.66 GHz
    Number Of Processors: 2
    Total Number Of Cores: 4
    Memory: 5 GB
    Chipset Model: NVIDIA GeForce 7300 GT
    PCI-E audio card: http://www.motu.com/products/pciaudio/2408/

    Have you figured out the solution for this? I'm experiencing the same problem with almost the same setup.
      Model Name:          Mac Pro
      Model Identifier:          MacPro3,1
      Processor Name:          Quad-Core Intel Xeon
      Processor Speed:          3.2 GHz
      Number Of Processors:          2
      Total Number Of Cores:          8
      Chipset Model:          NVIDIA GeForce 8800 GT
      MOTU PCIe-424 2408mk3
    I've just recently upgraded to Snow Leopard 10.6.3, when this blue screen issue started to bug me. I tried resetting the
    RAMs and GFX card, but to no good result. I also tried to remove the PCIe-424 card, and found out that this causes to stuck the system in blue screen. I was wondering maybe MOTU has new released driver for OS X 10.6. I only downloaded the latest driver for mac which is for 10.4 and up. But whenever I'm plugging back the PCI card in, the blue screen problem still occurs and cannot continue with the installation procedure anymore.
    Hope someone could give me idea on any solution for this.

  • Why does my mac book pro have a blue screen when booting up for a second just before the login screen

    When turning on my Mac Book pro before it get to the log in screen it has a blue screen for a couple of second the goes to the login sreen. It seams to take some time to complete the login to my computer.
    can anybody give me some help with this problem.
    Thank you

    The cable connections have (so far) solved this problem for my situation. Even though the monitor's DVI cable was firmly connected to the mini Display port connector, when I touched it the attached monitor would go 'blue' or lose its connection entirely. After disconnecting and reconnecting this junction the monitors would still take a hit on touching the connection. I also checked the connection of the mini Display port connection to the graphics board and could not push it in any further. However, after a second go-round I unplugged this connection to the board and reconnected it. I am certain it was fully inserted the first time. But, connection contacts can oxidize over time and sometimes it may just need to be disconnected and reconnected to 're-wipe' the connections. This effectively cleans them at the point of contact. So in my case I'm thinking it was the connection age that was an issue more than a 'loose' connection. Either way, I haven't had this issue for the past two weeks.

Maybe you are looking for