Uninstalling a monitor

BlackHawkBlackHawk Bible music connoisseurThere's no place like 127.0.0.1 Icrontian
edited December 2003 in Hardware
Is ther any way to remove the monitor(s) that the video card drivers or machine see? Right now ReForce reports 7 monitors and I think it's causing a problem cause my monitor seemed to go in standby after I booted and I had to restart. It may have been the drivers (Cat 3.9) or maybe cause it was OC'ed. I went back to 3.7's but when I try to use reforce, it gives me a warning of a "Default monitor driver" or something being active and it could report the refresh rate wrong. I haven't applied the settings and the machine seems to work but I would still like to remove all those monitor it reports.
«1

Comments

  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Well now I'm confused. I installed the Omega 3.7's, OC'ed the card to 285/285 (just to see what happens), I play BF1942 for like an hour w/o a problem but when I close the game, try to open IE and winamp, it starts to do the same thing as before. Freezing for a moment and then the monitor shutting off. I do a three finger salute and XP gives me an error saying it's recovered from a video card/driver (?) failure and the screen is 640x480 8bit color. I click ok and try to set the res back and the blinking dos prompt thingy comes and the machine hangs. I've reinstalled XP like 3 times in 2 days just like I do everyother time but these times it's acted a bit wierd. Seems to hang for a few secs, when accessing some files and the monitor turning off thing happened less. What could be the problem. Getting really annoying. TIA :)
  • SimGuySimGuy Ottawa, Canada
    edited December 2003
    Uninstall your CAT's & Control Panel.

    Restart in safe-mode with networking support.

    Download this file: http://www.driverheaven.net/cleaner/download/DC2Setup_26.zip

    Delete C:\ATI

    Run the Driver Cleaner.

    Download this file: http://www.macecraft.com/downloads/RegSupreme_setup.exe

    Run the RegSupreme Cleaner and delete all ATI entries.

    Download the Catalyst 3.7's & Catalyst 3.7 Control Panel.

    Restart.

    Install Catalyst 3.7 & Control Panel (Do NOT restart until both are installed in that order).

    Restart.

    System should be good now if it was a driver/multiple monitor detection issue. :D
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    :scratch: I ran the driver cleaner and the registry cleaner didn't show anything under ATi. But I didn't do it in safe mode. Would that change anything?
  • SimGuySimGuy Ottawa, Canada
    edited December 2003
    The readme for the program says to run it in safemode, so I'm not exactly sure if it would make a difference (I'm inclined to say yes..)
  • SpinnerSpinner Birmingham, UK
    edited December 2003
    Yeah, the drivers won't be in use in safe mode. I mean you knew that obviously, but it's reasonable to assume it might affect the way the program works, whether or not a driver file is enaged or not. Though why do I get the feeling it isn't gonna work in safe mode either. Oh the trials.
  • SimGuySimGuy Ottawa, Canada
    edited December 2003
    I've only ever used it in safe-mode on a backup machine I have here, never in normal-mode, so I can't really tell if it will work. :)

    Should though... it cleared all 14 monitor entries I had from different Catalyst installs...
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Did what you said and the monitor entries are still there. :(
  • SimGuySimGuy Ottawa, Canada
    edited December 2003
    DAMN!

    Humm..., you can try to do it the manual way, but I would suggest backing up your registry before you try this (just incase it borks something). :)

    Crack open regedit.exe and navigate to the keyset below (minus the (786B9D52-blah blah blah). Take a look through each entry for the information that looks similar to what is shown in the screenshot below. Easiest way to tell if it's an ATI driver entry is to look for the key "Catalyst_Version." Mine read's 03.7 as I'm using Catalyst 3.7's.

    Delete the entire key-structure (the 786B9D52.blah blah blah) and do that for all entries that refer to the Catalyst Version somewhere.

    That should remove them. If it doesn't, then I have no friggin idea how to do it. :(
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Ok lemme see if I get this straight. I basically just search for anything that says Catalyst_Version and I delete the key structure? Do I do this in safe mode? Do I reinstall the drivers after I delete them?
  • SimGuySimGuy Ottawa, Canada
    edited December 2003
    No no no.

    Regular mode. Leave drivers installed.

    Go into registry.

    Go to:

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Video\

    There will be a ****-load of keys in there, MOST referring to monitor settings entries for Catalyst. There are a few for NetMeeting and other video programs, so be watchful.

    Look through each one and look for an entry that has information referring to your Radeon card (see above screenshot for the information).

    When you see it, delete the entry (in my screenshot, I would delete the entry "786B9D52-4CC0-46E2-ADE4-D91399454CA1" and it's subkeys/folders.)

    Then, I would check the next one and continue to do this until all of the entries are removed. You may have 1 or 2 left over, as they refer to NetMeeting and such (like the screenshot below).

    AWW ****! My PC just crashed (GRR!!). Back in a second. God damn memory errors. Corsair can bite my ass.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Umm...there's nothing there ATi :(.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Well I played a few maps of BF1942 with the video card at stock speed and there hasn't been any problems. Don't know it was but how can a OC cause those problems? The card has ran without a problem at higher speeds and most of the time when it's cause of heat, it locks up completely. What sucks is that this card is underclocked by default :bawling:
  • SpinnerSpinner Birmingham, UK
    edited December 2003
    That sucks dude. But it would obviously seem your GPU is getting a little tired of being cranked up above stock. You might want to think about vamping up the cooling for it, memory and all. Then try OC'ing it again. If it still gives out then at least you'll know it ain't a heat problem.

    I personally hardly ever overclock, especially when it comes to video cards, and I've a nice worry free system as thanks for it. But I guess that's why I have trouble breaking any benchmarking records.

    Just out of interest are you using DVI or RGB output?
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    RGB
  • SpinnerSpinner Birmingham, UK
    edited December 2003
    Hmm, okay nevermind. Just a thought. If you have one, you could try plugging it in through the DVI port using a DVI to RGB apapter, presuming your monitor hasn't got a DVI input.

    The reason I mention this is just because of a problem my bro' had a few days ago with his Nvidia card. Just something to try, though I imagine it will have no effect. Just something random to try.
  • TheLostSwedeTheLostSwede Trondheim, Norway Icrontian
    edited December 2003
    Tick the 000 key as Simguy did in his screenie. Or did you do that?
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Mackanz had this to say
    Tick the 000 key as Simguy did in his screenie. Or did you do that?
    Sorry didn't reply but I did that.

    Well I was bored so I installed the new 3.10's. Uninstallation and installation went well. The extra monitor entries are still there but ReForce hasn't given me the error about the default monitor driver thing. The only problem now is the the drivers or something seem to be reporting my monitor incorrect.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Meh. It seems like since the drivers aren't reporting the monitor correctly, I can't use ReForce, so all my games are now in 60hz. :grumble:
  • SpinnerSpinner Birmingham, UK
    edited December 2003
    Have you actually got the correct monitor driver for your screen installed? do you have one for it?

    Also, in device manager, if the extra monitors are listed, try disabling, not uninstalling, the monitors you feel are the least applicable to your hardware and situation. See if that helps.

    Cheers
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Spinner had this to say
    Have you actually got the correct monitor driver for your screen installed? do you have one for it?
    AFAIK my monitor doesn't have drivers for XP/2k :(
    Also, in device manager, if the extra monitors are listed, try disabling, not uninstalling, the monitors you feel are the least applicable to your hardware and situation. See if that helps.

    Cheers
    The drivers (correct?) are the only ones reporting the extra monitors. There's no other monitor installed in device manager.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    I'm currently so bored, I'm gonna go and reinstall xp for the hell of it. Screw ghost images.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited December 2003
    Um, ghosts, or dobles, are almost always a refresh rate problem. Guess at what is happening-- You have an earlier PNP monitor that is not DDC2, rather it is DDC or non-DDC or the DDC circuit died in monitor. Windows is making its best guess as to the closest PNP table that the DDC converstaion as Widnows comes up reports is "right". What is the montior real model and brand, please. From sticker on monitor back?? MAYBE I can help find a mode .inf file for the thing that will work with 2000 and then XP.

    When you OC, you are tossing the ACTUAL refresh higher than XP thinks, and reforce wants a DDC2 conversation. Probably reforce and XP are guessing high for what monitor can now do, reforce more than XP. The only other thing is, if the thing has an OSD (on screen display) menu, see if it has manual degauss, and if so degauss 2-4 times in a row (one after the other, 3 seconds or so pause between), then see what happens (horseshoe upside down with a slash through it, usual symbol). The better monitors made from late 99 through about 2001 late had manual degauss on the OSDs many times. Monitors with gaussian field residual or persistant charges can do wierd things-- including ghost.

    John.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Ageek had this to say
    Um, ghosts, or dobles, are almost always a refresh rate problem. Guess at what is happening-- You have an earlier PNP monitor that is not DDC2, rather it is DDC or non-DDC or the DDC circuit died in monitor. Windows is making its best guess as to the closest PNP table that the DDC converstaion as Widnows comes up reports is "right". What is the montior real model and brand, please. From sticker on monitor back?? MAYBE I can help find a mode .inf file for the thing that will work with 2000 and then XP.

    When you OC, you are tossing the ACTUAL refresh higher than XP thinks, and reforce wants a DDC2 conversation. Probably reforce and XP are guessing high for what monitor can now do, reforce more than XP. The only other thing is, if the thing has an OSD (on screen display) menu, see if it has manual degauss, and if so degauss 2-4 times in a row (one after the other, 3 seconds or so pause between), then see what happens (horseshoe upside down with a slash through it, usual symbol). The better monitors made from late 99 through about 2001 late had manual degauss on the OSDs many times. Monitors with gaussian field residual or persistant charges can do wierd things-- including ghost.

    John.
    Well from what I got from that I think that DDC thingy is fubar'ed cause I installed the 3.7's and it reported it wrong (used to report correctly). The monitor is a Dell M781p (17inch). Don't know if it matters but I'm also using the tv-out of the 9700 on a 27" Wega Trinitron.

    [EDIT]Correction. The drivers aren't actually reporting the monitor wrong. It's just putting some gibberish before the actual model number.[/EDIT]
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Well it seems that XP is seeing the monitor as a unknown device. :sad2:
  • maggie99635maggie99635 Alaska
    edited December 2003
    As long as you stay within these parameters You shouldn't have any problems
    Horizontal scan range
    30 - 85 kHz (automatic)

    Vertical scan range
    50 - 160 Hz (automatic)

    Optimal preset resolution
    1024 x 768 at 85 Hz

    Highest preset resolution
    1600 x 1200 at 60 Hz

    Highest addressable resolution*
    1600 x 1200 at 65 Hz

    I've had problems with ATI recognizing Monitors refresh rates. I didn't see any .inf for XP( just up to 2000) to download off Dell's Site.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    The only actual problem I have is that I can't use ReForce since the monitor weren't reported correctly. Everything else works. I guess I gotta play the games at 60hz :sad2:
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    Well I think I know what the problem was. The tv-out. Took it out before installing the video drivers and now the monitor is reported correctly. Weeeeeeeeeeeeeee!!! :vimp:
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited December 2003
    EXCELLENT! Yes, running two at once (TV out and monitor) will get Windows confused if the basic Monitor drivers are not in first. similar thing happens with a BIOS and two IDE drives jumpered to same ID on same channel (like both MASTER) IF the BIOS can even say anything about the "device it thinks the two drives combine to signal to it at same time" are.

    In this case, Windows got two results at once, tried to set up one device and got radically "confused." TWO DDC2 results will do that, so trick is to set up monitor first, then use the TV-Out and let Windows set that up, AFTER restarting, with XP and most other Windows.

    One other trick, actually a pair of tricks, if you have a box that seems not to wake up its monitor, set it to respond to keyboard power button, and use lower left control key to wake it up, and tell BIOS to refresh display on wakeup (this is in power management). That is the older monitor backwards wakeup compatibility stuff for monitors in power management to use when you have older monitor, newer video card and O\S, as far as wakeup. This CTRL plus BIOS settings trick works for 95 OSR2 and up through XP, but can take 30 seconds to a minute to wake up, as BIOS is doing wakeup and older monitors have to powerup and then warm up their guns, for CRTs. My NEC flat panel actually wakes up faster by 10-20 seconds than my monitor (CRT) with these settings, no gun to pixel warmup time almost.

    Happy it works now.... And very happy you did not FUBAR the power supply circuitry in monitor, which was what would have happened long term with that problem remaining unsolved. Among other much worse things.

    John.
  • SpinnerSpinner Birmingham, UK
    edited December 2003
    Black Hawk had this to say
    Well I think I know what the problem was. The tv-out. Took it out before installing the video drivers and now the monitor is reported correctly. Weeeeeeeeeeeeeee!!! :vimp:

    You DIPSTICK!, I didn't realise you had something plugged into the TV Out on the GPU, well hello... duh!;D

    Oh the trials...

    Glad you got it sorted though buddy. Ha ha.

    Cheers;)
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited December 2003
    :O Didn't think it would've caused a problem. So I wasted a good 4hrs reinstalling xp over and over again just cause of a damn tv out. :ninja:
Sign In or Register to comment.