Hp w2072a monitor out of range problem

Hey reader, I'm using a hp w2072a monitor and hooked it up to my ps3 from a hdmi to dvi cable but when output to 1080 p resolution onto the w2072a it said out of range change setting to 1600 x 900 - 60Hz and tried changing it but couldn't find it through the monitor's main menu please help Thanks
This question was solved.
View Solution.

Hi,
you have to change the resolution at you ps3, not in the monitor's menu.
V.
*** Say 'Thanks' with Kudos ***

Similar Messages

Monitor out of range problem

I have a G5 dual 2.3 with a Sony monitor (analog) connected to the DVI port by the converter that came with the Mac. I have a problem in that certain games set the default resolution to a setting that is out of range of the monitor. Specifically, the refresh rate is out of range for it. This same problem occurs with any VGA monitor I use. Is there any way around this? I just bought the Cars game for my kids, for example, and I can't use it (Cars does not have a windowed mode).

as a wild guess, some monitors come with software drivers that allow to get more options for setting parameters.
you can check Sony site for any drivers for your monitor model, and also check what video card you have in G5 and check on card manufacturer site for driver updates for Mac OS.

Out of Range problem

I have a G5 dual 2.3 with a Sony monitor (analog) connected to the DVI port by the converter that came with the Mac. I have a problem in that certain games set the default resolution to a setting that is out of range of the monitor. Specifically, the refresh rate is out of range for it. This same problem occurs with any VGA monitor I use. Is there any way around this? I just bought the Cars game for my kids, for example, and I can't use it (Cars does not have a windowed mode).
Thanks

As it turns out, I tried switchresX and I can force the game not to change the settings. It works, but it seems silly for me to spend an extra 17.00 to play a $29 game. Anyone know of a free utility that does the same thing?

VGA monitor out of range error

Hello all,
I'm putting together a new computer with an oldish VGA only monitor. I used the latest installation disk. Installation went fine. I then did pacman -Syu of course. After that, whenever I boot my computer, it boots the kernel and shortly afterwards (before the login prompt) cause the monitor to go "out of range". I've tested the monitor with a Windows laptop and it seems fine. My question is: why did the VGA mode change during boot? How do I avoid that? If I can get a prompt and install X it'll be one step anyway. Thanks,

lang2 wrote:
I'm assuming you meant kernel log. I had to enable sshd and login remotely to get it:
http://pastebin.com/QQwM99L3
The problem:
[ 4.544007] [drm] Initialized drm 1.1.0 20060810
[ 4.674859] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 4.674863] i915 0000:00:02.0: setting latency timer to 64
[ 4.706140] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
[ 4.706142] [drm] MTRR allocation failed. Graphics performance may suffer.
[ 4.706393] i915 0000:00:02.0: irq 41 for MSI/MSI-X
[ 4.706396] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 4.706397] [drm] Driver supports precise vblank timestamp query.
[ 4.736280] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 4.922865] checking generic (e0000000 fff0000) vs hw (e0000000 10000000)
[ 4.922868] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[ 4.922883] Console: switching to colour dummy device 80x25
[ 4.923077] fbcon: inteldrmfb (fb0) is primary device
[ 5.083490] Console: switching to colour frame buffer device 240x67
[ 5.195838] fb0: inteldrmfb frame buffer device
[ 5.195839] drm: registered panic notifier
[ 5.195954] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Maybe removing the vga part would help:
[ 0.000000] Command line: root=/dev/sda3 ro vga=773
but I'm basically guessing here.

Monitor out of range

Brand new Mac Mini out of the box. Hooking HDMI to a Westinghouse L2610NW. Showing "out of range". No way to hook up VGA with what is out of box because there is only a DVI-D adaptor. Tried powering on with no HDMI connected. Tried connecting another computer to the monitor and that works. No DVI connection on the monitor. No other monitor available to connect to. Can you set to 1024x768 out of the box just to get through the set up?

The native resolution for your L2610NW is 1920 x 1200 and the Mac Mini supports that using the HDMI port.
With the monitor connected, reset the PRAM as per > About NVRAM and PRAM
1. Shut down the computer.
2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
3. Turn on the computer.
4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
6. Release the keys.

Live Install - Monitor "Out of Range"

Brand new to Solaris, and fairly new to *nix.
Tried installing from the Live CD, and my monitor goes "out of range" when the GUI boots. Likewise, did the text installer, installed "slim_install" and enabled gdm and the same same thing occurred. I am able to boot from the Live CD with the VESA driver, but curious how to troubleshoot and resolve the issue without using VESA.
Video is Intel i915.
What would be the best avenue to t/s? Is there a config file I can use to specify the default video settings? Or is this a driver issue?

Just adding 1 to the kernel boot line is enough to boot in single user mode.
Try removing kdm from rc.conf and instead edit /etc/inittab where you can change the default run level from 3 to 5
id:5:initdefault:
and run kdm rather than xdm
x:5:respawn:/opt/kde/bin/kdm -nodaemon
If you get stuck in future, add 3 to the end of your boot line - you'll be in multi-user text mode but with network running so you can download packages, browse the forum with links. I recommend downloading the (text mode) mc file manager which also provides mcedit.

Mbuf address out of range problem - worth downgrading?

I've been getting kernel panics since the 10.4.7 update. The general opinion seems to be that they're Airport driver related. Has anyone tried dropping back to 10.4.6 and if so did they have any success?
The panics log like this:
panic(cpu 0 caller 0x00351703): mbuf address out of range 0x10e48000
Which is consistent with what other people are seeing?
MacBook Pro Mac OS X (10.4.7)

I tried that and still got an "mbuf address out of range" error as follows..
Sat Jul 15 12:52:24 2006
panic(cpu 0 caller 0x003500DC): mbuf address out of range 0x2fcd8000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24dbbe64 : 0x128b5e (0x3bc46c 0x24dbbe88 0x131bbc 0x0)
0x24dbbea4 : 0x3500dc (0x3dbeb8 0x2fcd8000 0x369b6a00 0x34f035)
0x24dbbec4 : 0x350483 (0x369acf00 0x1e 0xffffffff 0x369a9b00)
0x24dbbee4 : 0x24f138 (0x369acf00 0x0 0xe3 0x36aa78e3)
0x24dbbf64 : 0x21125d (0x369acf00 0x369acf00 0x42db5c 0x3585608)
0x24dbbfa4 : 0x1f7871 (0x4b8000 0x369acf00 0x369acffc 0x3585608)
0x24dbbfd4 : 0x197b19 (0x0 0x0 0x3585880 0x134aec) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386

Envision monitor "out of range"

I have a widescreen Envision monitor that I've used on my PC for years but I'm not having any luck getting it to work with my new Mac Mini. Envision's website says it needs some drivers and I need to talk to Mac support...
I've tried safe booting several times, but still end up the same: power up the Mac Mini the Apple logo and gear going round look fine, but as soon as it switches to its regular display mode the screen goes black.
The monitor menu's Info screen says: 1440 X 900, 55 kHz, 59 Hz.
Anyone with a solution?

The way a Mac gets it's display driver is directly from the display, so the Envision website is not correct if it directs you to Mac support for a display driver.
If you own a second computer, I recommend setting up a VNC connection between the mini and a second computer. You can then see what resolution the mini is sending to the Envision. You can also change that setting from the other computer and hopefully get the mini set to a resolution that will cause the Envision to start working.

Mac mini 2014 mDP out of range

Hi,
I have a strange issue with Mac mini late 2014 and NEC PA272W monitor. Mac mini and the monitor are connected by high quality mini display port cable.
Sometimes on boot the display is reporting: Out of range message H 14,6KHz. Its a sync problem?
Then I have to turn off and on the monitor to restore image.
Any advice to this?

Sadly, this "out of range" problem has re-appeared today :-/
This is log from the console:
08.02.2015 13:36:44,486 WindowServer[121] Received display connect changed for display 0x28da5200
08.02.2015 13:36:44,486 WindowServer[121] Found 1 modes for display 0x28da5200 [1, 0]
08.02.2015 13:36:44,486 WindowServer[121] Display 0x28da5200 changed state to offline
08.02.2015 13:36:44,490 WindowServer[121] No display devices are on-line. Switching to virtual display mode
08.02.2015 13:36:44,493 WindowServer[121] Received display connect changed for display 0x3f003d
08.02.2015 13:36:44,493 WindowServer[121] Found 1 modes for display 0x003f003d [1, 0]
08.02.2015 13:36:44,503 WindowServer[121] Display 0x41dc9d00: GL mask 0x1; bounds (0, 0)[2560 x 1440], 35 modes available
Main, Active, on-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 0, Rotation 0
UUID 0x3cd5b411aa96bcb56a310d5b3ba2be96, ColorSpace { 847203028 }
08.02.2015 13:36:44,503 WindowServer[121] Display 0x41dc9d02: GL mask 0x4; bounds (3584, 0)[1 x 1], 2 modes available
off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:44,503 WindowServer[121] Display 0x41dc9d01: GL mask 0x2; bounds (3585, 0)[1 x 1], 2 modes available
off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:44,506 WindowServer[121] CGXDisplaysDidReconfigure: Display added
08.02.2015 13:36:44,506 WindowServer[121] CGXDisplaysDidReconfigure: Display removed
08.02.2015 13:36:44,507 WindowServer[121] Display 0x41dc9d00: GL mask 0x1; bounds (0, 0)[2560 x 1440], 35 modes available
Main, Active, on-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 0, Rotation 0
UUID 0x3cd5b411aa96bcb56a310d5b3ba2be96, ColorSpace { 847203028 }
08.02.2015 13:36:44,507 WindowServer[121] Display 0x41dc9d02: GL mask 0x4; bounds (3584, 0)[1 x 1], 2 modes available
off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:44,507 WindowServer[121] Display 0x41dc9d01: GL mask 0x2; bounds (3585, 0)[1 x 1], 2 modes available
off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:44,521 com.apple.AmbientDisplayAgent[169] AMBD: copyVCGTtoLUTtable() synth'ing linear LUT
08.02.2015 13:36:46,507 WindowServer[121] **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
08.02.2015 13:36:46,518 DMProxy[373] CGSCopyDisplayInfoDictionary: error requesting display info dictionary (0x3e8)
08.02.2015 13:36:46,523 WindowServer[121] CGXSetDisplayColorProfileAndTransfer: Display 0x41dc9d00: Unit 0; ColorProfile { 847203028 }; TransferTable (256, 3)
08.02.2015 13:36:46,526 com.apple.AmbientDisplayAgent[169] AMBD Agent: xpc connection became invalid during event handler
08.02.2015 13:36:46,539 DMProxy[373] AMBD Services: connection interrupted: com.apple.AmbientDisplayAgent (Connection interrupted)
08.02.2015 13:36:46,543 WindowServer[121] CGXSetDisplayColorProfileAndTransfer: Display 0x41dc9d00: Unit 0; ColorProfile { 847203028 }; TransferTable (256, 3)
08.02.2015 13:36:46,547 com.apple.AmbientDisplayAgent[169] AmbientDisplayAgent started
08.02.2015 13:36:46,550 com.apple.AmbientDisplayAgent[169] AMBD initializing devices
08.02.2015 13:36:46,554 com.apple.AmbientDisplayAgent[169] AMBD: copyVCGTtoLUTtable() synth'ing linear LUT
08.02.2015 13:36:46,555 com.apple.AmbientDisplayAgent[169] AMBD Agent: xpc connection became invalid during event handler
08.02.2015 13:36:47,000 kernel[0] EDID CEA Extensions not valid for audio [Revision ID]: 1 (minimum value: 3)
08.02.2015 13:36:48,212 WindowServer[121] Received display connect changed for display 0x3f003c
08.02.2015 13:36:48,213 WindowServer[121] Found 43 modes for display 0x003f003c [43, 0]
08.02.2015 13:36:48,213 WindowServer[121] Display 0x003f003c changed state to online
08.02.2015 13:36:48,239 WindowServer[121] New display device coming on-line. Switching from virtual display mode
08.02.2015 13:36:48,240 WindowServer[121] Received display connect changed for display 0x3f003d
08.02.2015 13:36:48,240 WindowServer[121] Found 1 modes for display 0x003f003d [1, 0]
08.02.2015 13:36:48,252 WindowServer[121] Display 0x003f003e: GL mask 0x4; bounds (3584, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:48,252 WindowServer[121] GLCompositor: GL renderer id 0x01024501, GL mask 0x00000007, accelerator 0x00002447, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
08.02.2015 13:36:48,252 WindowServer[121] Display 0x003f003d: GL mask 0x2; bounds (3585, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:48,252 WindowServer[121] Display 0x28da5200: GL mask 0x1; bounds (0, 0)[2560 x 1440], 43 modes available
Main, Active, on-line, enabled, boot, OpenGL-accel, Vendor 38a3, Model 6948, S/N 0, Unit 0, Rotation 0
UUID 0x3cd5b411aa96bcb56a310d5b3ba2be96, ColorSpace { 847203028 }
08.02.2015 13:36:48,252 WindowServer[121] GLCompositor: GL renderer id 0x01024501, GL mask 0x00000007, accelerator 0x00002447, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
08.02.2015 13:36:48,262 WindowServer[121] Display 0x28da5200: Unit 0: Startup Mode 2560 x 1440, CGSThirtytwoBitColor, Resolution 1, ioModeID 0x80001000, ioModeDepth 0x0, IOReturn 0x0
08.02.2015 13:36:48,262 WindowServer[121] CGXDisplaysDidReconfigure: Display added
08.02.2015 13:36:48,262 WindowServer[121] CGXDisplaysDidReconfigure: Display removed
08.02.2015 13:36:48,263 WindowServer[121] Display 0x28da5200: GL mask 0x1; bounds (0, 0)[2560 x 1440], 43 modes available
Main, Active, on-line, enabled, boot, OpenGL-accel, Vendor 38a3, Model 6948, S/N 0, Unit 0, Rotation 0
UUID 0x3cd5b411aa96bcb56a310d5b3ba2be96, ColorSpace { 847203028 }
08.02.2015 13:36:48,263 WindowServer[121] GLCompositor: GL renderer id 0x01024501, GL mask 0x00000007, accelerator 0x00002447, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
08.02.2015 13:36:48,263 WindowServer[121] Display 0x003f003e: GL mask 0x4; bounds (3584, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:48,264 WindowServer[121] GLCompositor: GL renderer id 0x01024501, GL mask 0x00000007, accelerator 0x00002447, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
08.02.2015 13:36:48,264 WindowServer[121] Display 0x003f003d: GL mask 0x2; bounds (3585, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
08.02.2015 13:36:48,273 WindowServer[121] MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x28da5200 device: 0x7fa849516e60 isBackBuffered: 1 numComp: 3 numDisp: 3
08.02.2015 13:36:50,241 WindowServer[121] **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
08.02.2015 13:36:50,263 WindowServer[121] **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
08.02.2015 13:36:50,267 WindowServer[121] CGXSetDisplayColorProfileAndTransfer: Display 0x28da5200: Unit 0; ColorProfile { 847203028 }; TransferTable (256, 12)
08.02.2015 13:36:50,270 com.apple.AmbientDisplayAgent[169] AMBD Agent: xpc connection became invalid during event handler
08.02.2015 13:36:50,301 WindowServer[121] CGXSetDisplayColorProfileAndTransfer: Display 0x28da5200: Unit 0; ColorProfile { 847203028 }; TransferTable (256, 12)
08.02.2015 13:36:50,304 com.apple.AmbientDisplayAgent[169] AMBD Agent: xpc connection became invalid during event handler
08.02.2015 13:36:50,312 DMProxy[374] AMBD Services: connection interrupted: com.apple.AmbientDisplayAgent (Connection interrupted)
08.02.2015 13:36:50,319 com.apple.AmbientDisplayAgent[169] AmbientDisplayAgent started
08.02.2015 13:36:50,334 com.apple.AmbientDisplayAgent[169] AMBD initializing devices
08.02.2015 13:36:50,334 WindowServer[121] CGXSetDisplayColorProfileAndTransfer: Display 0x28da5200: Unit 0; ColorProfile { 847203028 }; TransferTable (256, 12)
08.02.2015 13:36:50,340 com.apple.AmbientDisplayAgent[169] AMBD Agent: xpc connection became invalid during event handler
08.02.2015 13:36:50,346 DMProxy[375] AMBD Services: connection interrupted: com.apple.AmbientDisplayAgent (Connection interrupted)
08.02.2015 13:36:50,350 WindowServer[121] CGXSetDisplayColorProfileAndTransfer: Display 0x28da5200: Unit 0; ColorProfile { 847203028 }; TransferTable (256, 12)
08.02.2015 13:36:50,355 com.apple.AmbientDisplayAgent[169] AmbientDisplayAgent started
08.02.2015 13:36:50,359 com.apple.AmbientDisplayAgent[169] AMBD initializing devices
08.02.2015 13:36:50,365 com.apple.AmbientDisplayAgent[169] AMBD Agent: xpc connection became invalid during event handler
08.02.2015 13:36:51,808 Console[376] Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable

Importing 59.94 fps - edl from Premiere CC - error - Frame index out of range

I have a Adobe Premiere project with a 5k 59.94 sequence.
The sequence has two R3d 5K clips both interpreted at 59.94.
I've exported an edl for the sequence and want to import it into SpeedGrade.
I have adjusted my preferences in SpeedGrade for 59.94.
- playback at 59.94
- base frame rate is set at 59.94, with "both edits and footage have the current base FPS as set above or in the EDL itself"
I import the EDL and the reels are not loaded. I select "Load from desktop", and the reels still do not load.
I deselect "don't replace loaded reels" and manually drag the two clips and replace the two reels.
I can now see the clips in the timeline, but have an error message in my display - "Frame index out of range".
I'm guessing this could also a be a Premiere CC export problem, but not sure. The sequence is just cuts, no audio.
Here's the edl info:
TITLE: sg_test_edit
FCM: NON-DROP FRAME
001 A002C035 V C 17:40:23:54 17:40:38:41 00:00:00:00 00:00:14:47
* FROM CLIP NAME: A002_C035_05094K_001.R3D
002 A002C013 V C 16:46:38:36 16:46:52:24 00:00:14:47 00:00:28:35
* FROM CLIP NAME: A002_C013_0509UM_001.R3D
Trying to nail down a workflow for 4k 60p, and not feeling very encouraged.
Any suggestions?
Thanks

I've had a similar frame-out-of-range problem for the last week or so in Sg ... import an edl, and even if I've already set the "base" in Prefs, and for that project BEFORE re-loading the reels, I ALWAYS get the f-o-o-r screen instead of my footage. After going back and forth setting those things to the same thing again and maybe again, I'll finally get where it all loads & runs. Save the project.
Come back by opening it again later ... and GET THAT DAMN FRAME-OUT-OF-RANGE thing again and have to ... again ... spend 10-15 minutes setting and re-setting all those same DAMN things until it finally decides to accept my footage.
I've only ... in the last two weeks ... TWICE opened a project I'd previously had working and graded on ... that simply loaded. Every other time I've had to waste time re-setting/re-setting/re-setting/close-open-re-set/re-setting & etc. until it finally works.
No help from anyone about why this is now happening, how to stop it, or fix it quickly. Damn dumb behavior.
Neil

G3 Monitor saying "out of range" after itunes upgrade - HELP PLEASE

I'm running a G3 with 512RAM. It has been running Panther totally reliably for a year. I upgraded to 10.3.9 and the G3 ran no problem. I upgraded to the latest Itunes, restarted the G3 and now after the tones the monitor turns black with the message "out of range" refering to the frequency setting. I can hear to G3 drive running but I cant progress beyond this message on the monitor. Please help...have I lost my G3 for ever? is there a safe mode I can start the G3 in? I have the Panther discs but I don't seem able to do anything to start this G3 now. Please help..I love this Mac, I dont want to loose it, don't mind loosing the data, but not the mac..any ideas..please

Refer to mac manual - Resetting the PRAM (parameter randon access memory).
Restart whilst holding Command/option/p/r keys and release after second tones. Suggest changing internal battery also.

G3 mini-tower beige powerpc. monitor signal out of range w/ upgrade to OSX

Hi. I have a beige G3 minitower with an 80 gig hd, 448 mb ram, ATY Mach 64 3DUPro 6mb vram pci. Monitor is a NEC Multisync FE770. I have an 8 gig partition on which I successfully installed OSX10.2.08, and another partition has 9.2.2.
I can boot in 9.2 no problem, but when I boot up in 10.2, I get a red bordered box on a black screen that says "Signal frequency is out of range. FH>80 OKHZ. FV>75OHZ. Please change signal timing."Monitor preferences have been reset to different frequencies, but it still persists.
I have read for hours on this forum, and have tried resetting pram via keyboard, only to get the "?" start-up screen. I was able to boot in OS9 to get to utilities to re-choose the startup disc. But nothing changed, still got the out of range box. I also tried the Mac solution posted here, "Blue or Black screen after updating" but that did nothing. Anyhow, I know you suggested replacing the battery, but why would it work in OS9 if the battery is the problem? Can anyone suggest any fix to this? I have been trying to get this computer updated for my 10 year old son, and have put way too much time into it:) Best,JER

daordster wrote:
daordster wrote:
daordster wrote:
Hi. I have a beige G3 minitower with an 80 gig hd, 448 mb ram, ATY Mach 64 3DUPro 6mb vram pci. Monitor is a NEC Multisync FE770. I have an 8 gig partition on which I successfully installed OSX10.2.08, and another partition has 9.2.2.
I can boot in 9.2 no problem, but when I boot up in 10.2, I get a red bordered box on a black screen that says "Signal frequency is out of range. FH>80 OKHZ. FV>75OHZ. Please change signal timing."Monitor preferences have been reset to different frequencies, but it still persists.
I have read for hours on this forum, and have tried resetting pram via keyboard, only to get the "?" start-up screen. I was able to boot in OS9 to get to utilities to re-choose the startup disc. But nothing changed, still got the out of range box. I also tried the Mac solution posted here, "Blue or Black screen after updating" but that did nothing. Anyhow, I know you suggested replacing the battery, but why would it work in OS9 if the battery is the problem? Can anyone suggest any fix to this? I have been trying to get this computer updated for my 10 year old son, and have put way too much time into it:) Best,JER
Hi, I am updating this original post to say that I ordered and installed a new battery into my G3, and I still am getting the "out of range" warning on my monitor at startup. Can anyone offer a solution? It only happens when I boot in OSX, and never happened in system 9. The only additional info I can offer is that I installed 10.2 with the grey install discs from an older IMAC. Someone on the forum mentioned that the grey install discs would only work for the same machine, though I was able to do a clean install. Does a disc meant for an imac install a system geared to that model? Could it be a reason for the monitor issue? I am grasping at straws. Any additional help is welcome. Best,JER
Hey, I just borrowed a retail disc of OSX 10.2, and went through a clean install, only to get the SAME out of frequency message on start-up. So that eliminates that. New pram battery also done. Any other ideas? If the monitor is generating the message, and nec is no help, what next? Can the NEC adaptor work for another crt monitor? I have a PC computer with a monitor the same size. I guess I'll check to see. Best,JER
What is happening is that the physical pixel characteristics of your monitor don't match the resolution that your Mac is calling for (this is one area that Windoze's display handling routines differ on PC; windoze will "cut off" or black out portions of the display to make it fit.)
I just had this happen yesterday with an oddly-shaped LCD monitor that is slightly squarish. Zapping the Mac's PRAM did no good because it defaults to 800 X 600, which the monitor was geometrically unable to achieve. The resolution had to be set to 640 X 480 (or 1280 x 960 or other common denominator.)
The reason OS 9 can display it is because a compatible resolution is stored in the prefs, while OS X does not contain it.
I solved my problem by booting from a secondary disk and replacing the display pref with a known-good one. Since you can't swap prefs between 9 and X, you could boot with a different monitor, set the resolution to a compatible setting, then hook up the previous monitor.

"Out of Range" on LG Ultrawide Monitor on Mac Mini

I am currently running dual monitors
Primary: LG Ultrawide IPS 32" Monitor running at resolution 2560x1080
Secondary: AOC IPS 27" Monitor running at resolution 1920x1080
Every once in a while my primary monitor will go Blank and say "OUT OF RANGE"
What is causing this to happen?
I have to use the secondary monitor to close down all the applications and restart the computer.
Then everything goes back to normal.
It doesnt happen all the time. But it is starting to become more frequent.
How do I fix this?
Thank you
Clance

Hi,
I've also had this same problem using the 29" LG ultrawide screen.
Thanks for the two articles, I hoped that they would work. Seemed fine for the rest of the time that I was signed on but once I logged off and started the next day things went back to normal.
This has got worse for me since Yosemite was installed.
Any ideas?
Thanks

My LG monitor says the display is out of range.

My LG W2040T Flatron monitor says the D-Sub is out of range. No matter what I do in the settings will change this issue. My Macbook Pro is the new version with Thunder Bolt. I never had this problem with my old black macbook. Has anyone else had this problem? If so, how did you fix it? Thanks for you help in advance.
-Paul

If you have the two displays "Mirrored" (which is usually the default) it will use a resolution that is closest to a resolution that both displays can handle. But sometimes it misses, and one or both displays are left "out of range". If you set "Extended desktop" instead, you can set each display's resolution separately.
System Preferences > Displays > ( Arrange )
... if the Icons for the two screens are one on top of the other, that is Mirrored. Drag one off and arrange them to correspond to their positions in space. Now you have Extended Desktop.

Monitor says "Out of Range"

G3 Beige tower OS9 Monitor message"out of range"Then goes black.Battery changed.Hoping for a miracle,I use this setup for music,Studio vision Pro.

Hi, George -
The 'out of range' message indicates that the resolution setting being read for the monitor is one the monitor can not handle. This can result from someone fiddling with the monitor resolution settings, or possibly from a damaged prefs file.
Have you tried booting to a CD?
If you're using OS 9 on that machine, try using an OS 9 Install CD as the boot volume. If it boots successfully using that, then try throwing away these two preference files -
Display Preferences (located loose in Preferences in System Folder)
Monitor Preferences (located in a folder by the same name in Preferences in System Folder)
- and then do a restart, zapping the PRAM in the process.
If that works, it should reset the resolution to either 600x480 or 800x600. You can then reset the resolution to what you usually keep it at, followed by a shutdown (the shutdown is necessary to transfer the setting to PRAM).
Occasionally the problem can exist in the monitor - some of those, especially CRT types, can have their own PRAM, and it can get bollixed or retain the wrong info. If your monitor has separate power and video cables, you can try resetting the PRAM in the monitor itself. To do this, power everything down, disconnect the video cable from the Mac. Then turn the monitor on, wait 15 to 20 seconds, then turn it off; wait about 10 seconds, then repeat the cycle, 3 or 4 times. Then reconnect the video cable and boot back up.

Hp w2072a monitor out of range problem

Similar Messages

Maybe you are looking for