Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

video card not being recognized

25 views
Skip to first unread message

Fredd Wright

unread,
Jan 26, 2011, 4:30:08 PM1/26/11
to
I have a Gateway GT5014 with XP media center edition that i just installed a
new video card in (A Radeon HD 4350). The PC doesn't recognize the new
video card. This computer came with integrated video so i installed the new
card, installed the drivers, hooked it up to the monitor, went into the BIOS
and changed the video setting for the PCI Express option. When it
restarted, i got the Windows splash screen then it went black and i got
nothing except for a beep every few seconds. I reset the BIOS to the old
setting and changed the monitor back, then i went to Device manager and the
new card doesn't even show up in the display section.

The one thing i didn't do is disable the old integrated video in device
manager. I'm afraid to do that as i don't know how to undo it if the new
card doesn't work and i can't get any picture.


Fredd


Paul

unread,
Jan 26, 2011, 7:45:28 PM1/26/11
to

There is a suggestion here, the D945GCZ has a PCI Express x16 1.0a slot.

http://www.fixya.com/support/t3716141-intel_d945gcz_pci_e_video_card

I've tried to find an article with definitive info on the standards
and reasons why a 1.0a slot wouldn't work with a 2.0 card, but haven't
succeeded. I can find occasional comments, that some cards don't work.

http://www.cableforum.co.uk/board/19/33668059-helping-replacing-graphics-card.html

And your video card, does seem to be Rev.2

http://www.gpureview.com/Radeon-HD-4350-card-585.html

The Intel site was no help, with respect to BIOS settings. I found
a couple manuals, but nothing to help out. One manual shows how to
insert a PCI Express video card, but there was no accompanying text
to describe difficulties to expect.

The fact you're getting a beep code of some sort, means something
isn't right.

Paul

Fredd Wright

unread,
Jan 26, 2011, 8:35:43 PM1/26/11
to
Thanks. I looked at the specs on the box which call for a "PCI express
based PC with one x16 lane graphics slot" After looking it up, it appears
that x16 is another name for a PCI-e slot so i imagine it should work.

If it is the case that this card doesn't work with my PC, can you recommend
a video card - either PCI or PCI-E that will support 2 monitors? (that's why
i got it in the first place). It doesn't have to be super fast. My onboard
video only has 128 mb of memory as it is.

Further info - the fan on the card DOES run and i am NOT getting the "no
signal" message on the monitor from it. It's just black.

Fredd

"Paul" <nos...@needed.com> wrote in message
news:ihqf79$p1d$1...@news.eternal-september.org...

Paul

unread,
Jan 26, 2011, 9:39:38 PM1/26/11
to
Fredd Wright wrote:
> Thanks. I looked at the specs on the box which call for a "PCI express
> based PC with one x16 lane graphics slot" After looking it up, it appears
> that x16 is another name for a PCI-e slot so i imagine it should work.
>
> If it is the case that this card doesn't work with my PC, can you recommend
> a video card - either PCI or PCI-E that will support 2 monitors? (that's why
> i got it in the first place). It doesn't have to be super fast. My onboard
> video only has 128 mb of memory as it is.
>
> Further info - the fan on the card DOES run and i am NOT getting the "no
> signal" message on the monitor from it. It's just black.
>
> Fredd

If that was the case, then it implies the card is being seen,
and something is setting up the card. But whether you're sitting in
the BIOS or the OS, nothing is writing or drawing to it.

I don't think it would do that (drive the screen, but with an all
black image), unless a minimum number of registers in the card had
been set up. So then the question would be, why isn't "new hardware"
detected, or something seen in Device Manager ?

To make the black image, you need a sync pattern of some sort, in the
signal sent from the computer to the screen. And video cards are designed
to do impedance sensing, and the driver is only supposed to enable
an output, if a monitor can be detected.

OK, I have another test for you. So right now, it sounds like you have
a monitor connected to the 945G video, and can see your Windows OS.
You either have a second monitor connected to the HD4350, or are
moving the monitor connector over to a connector on the HD 4350.

Download a copy of Everest. This edition is the last free one, and
the company (Lavalys) still works on a commercial version. This won't
have an up-to-date database in it, but it'll still tell you whether
hardware is present or not. (If a piece of hardware is detected,
there should still be some sort of entry in the list for it.)

http://majorgeeks.com/download.php?det=4181

Install the software, and run the program. Go to Devices:PCI Devices
(things like PCI, AGP, PCI Express will be there).

I can see, in my hardware list...

NVIDIA GeForce 7900 GT/GTO [NoDB]

which means the program may have got the name of my video card, from the
VESA ROM on the video card or something. The [NoDB] implies it wasn't
identified by Plug and Play VEN/DEV/Subsys. (The program is too old,
to know about the 7900 GT.)

When I click on the entry, a table of Field and Value appears in
the second pane down on the screen. I can see

Device ID 10DE-0291

I can look that up here. This is an informally maintained list,
as the official list is a secret (so new hardware designs can get
an ID, without "blowing their cover").

http://pciids.sourceforge.net/pci.ids

"10de nVidia Corporation
...
0291 G71 [GeForce 7900 GT/GTO]"

so I can confirm the identity that way, using the Device ID (VEN-DEV).

Now, your card is HD 4350. These would be the numbers for it.

"1002 ATI Technologies Inc
...
954f RV710 [Radeon HD 4350]"

so your Device ID would be 1002-954F.

If you have an OS like WinXP, you can look at the tail end
of the setupapi.log file (open in Notepad), and look for
1002 or 954F, and if those numbers are present, it means
Plug and Play has been at work.

If you're getting some signal on that video connector,
I wouldn't buy a new card just yet.

The HD4350 doesn't have an auxiliary PCI Express power connector
on it, so I don't interpret the beeping to mean it's missing
something like a power connection. It really should be working,
barring some Rev.2 versus Rev.1.0a nonsense.

You can also try moving the monitor connector, and testing more
than one of the connectors on the HD 4350.

The Display control panel, may show more than one monitor present.
But that is prefaced on a good entry appearing in Device Manager.

http://www.techrepublic.com/i/tr/cms/contentPics/multimon-c.gif

Paul

Kele

unread,
Jan 26, 2011, 11:25:44 PM1/26/11
to
I'm a novice at computer guts, but I've been following your posts. The
first thing I thought of was whether the video card needed power beyond just
being plugged into the open slot. I've seen computer with extra power plugs
bundled near the front by the unused disc drive bays. I've also seen video
cards that require to be plugged into this type of power port. You stated
your new card has a fan and that prompted me to comment. Maybe someone can
clarify if this could be the problem.

Your other post reminds me of the time the wife tore off the record player
needle when dusting - those busy woman!


Fredd Wright

unread,
Jan 27, 2011, 7:08:38 AM1/27/11
to
Your first assumption is correct. I have a second monitor hooked up to the
new video card. I downloaded Everest and looked at PCI devices. I see "ATI
Rio 550 PCI TV Card" which i'm sure is the new one although the name is not
exactly the same. The device ID also differs a little from what you said it
should be - 1002-4D52 which comes up on the list as "Theater 550 PRO PCI
[ATI TV Wonder 550]". The new card does NOT show up in Display properties
at all.

The lasts few lines of the setupapi.log file are:

#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&61AAA01&1&08".
#W100 Query-removal during install of
"PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&61AAA01&1&08" was vetoed by
"PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&61aaa01&1&08" (veto type 6:
PNP_VetoDevice).
#W104 Device "PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&61AAA01&1&08"
required reboot: Query remove failed (install) CfgMgr32 returned: 0x17:
CR_REMOVE_VETOED.
#I121 Device install of
"PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&61AAA01&1&08" finished
successfully.
[2011/01/26 16:42:46 3120.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{B074F582-EAF4-408D-93D3-F146B16A9094}
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
hdaudio\func_01&ven_1002&dev_aa01&subsys_00aa0100&rev_1001,hdaudio\func_01&ven_1002&dev_aa01&subsys_00aa0100
#-018 Searching for compatible ID(s):
hdaudio\func_01&ven_1002&dev_aa01&rev_1001,hdaudio\func_01&ven_1002&dev_aa01,hdaudio\func_01&ven_1002,hdaudio\func_01
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.

If i'm reading this right t appears to me that the drivers could not be
installed for some reason - even though they are the drivers from the CD
that came with the card.

Another thing, i have the new card hooked up via DVI connection which i've
never used before. Always used VGA. Is there something special or
different about DVI i need to know to make it work?

Fredd


"Paul" <nos...@needed.com> wrote in message

news:ihqltb$ukt$1...@news.eternal-september.org...

Fredd Wright

unread,
Jan 27, 2011, 11:53:29 AM1/27/11
to
i finally got it to work after reinstalling the drivers twice! Not sure
what i did differently but it works now!

Fredd

"Fredd Wright" <flob...@optonline.net> wrote in message
news:pLednRgdXbZY_NzQ...@giganews.com...

Paul

unread,
Jan 27, 2011, 12:56:33 PM1/27/11
to
Fredd Wright wrote:
> i finally got it to work after reinstalling the drivers twice! Not sure
> what i did differently but it works now!
>
> Fredd

If at first you don't succeed...
use a bigger hammer :-)

The "ATI Rio 550 PCI TV Card" would be a TV card. You said in the original
posting, that this was a Media Center PC, so it likely has one card to
receive TV in it. The Theatre 550 chip would be an example of such a
decoder. The card might normally be used for cable or antenna reception
of the older analog TV signals (channels 2-69 etc).

(When ATI used to make "All In Wonder" AIW cards, chips like the Theatre 550
plus a silicon tuner chip, might have been included on a video card. That
means the graphics card had TV functions built in. But I don't think ATI
does that any more, so the Theatre 550 is likely to appear on a separate
plug-in card. Look for a card with an antenna input terminal.)

The "hdaudio\func_01&ven_1002" thing, would be "audio over HDMI" of the
HD 4350 video card. That would be my guess there. If it installed properly,
you might see a new entry in the Sound control panel (but there is no
reason to select it, unless you have a monitor with a couple built-in
speakers). HDMI is capable of carrying both video and audio, which for
an HTPC is a desirable function in terms of cutting down on the number of
cables.

I'm surprised you still aren't seeing evidence of the HD 4350 numbers.
Now that all is well, go to Device Manager, find the HD 4350 entry
as a display device, do Properties on it, then select the Details
tab. The first value I see in mine, is a Device Instance id, and
that contains the VEN and DEV values. Everest should also be
showing the card, in its list of PCI Devices. And it really should
be in setupapi.log as well.

There can be more than one setupapi.log file, and you have to be careful
to select the latest one. The log file rolls over after it gets to some size.
When a driver is actually instantiated, an entry should appear in the log.
If you pull the card, reboot, install the card, reboot, you might even see a
fresh entry in setupapi.log, when the card is discovered a second
time.

And for a card to be fully functional, may require more than
one reboot. That's because the driver dependencies (DirectX, audio
over HDMI, .NET for CCC and the like), get discovered one at a time.
So one reboot isn't always sufficient to get full functionality.
The last time I was screwing around with my current video card, it
wasn't accelerated after the first reboot - but the resolution
setting function worked. The fonts were also a bit goofy. It took
a bit of coaxing and rebooting, to get it put back again. I sometimes
test an old PCI video card in my system, which kinda upset things.
Drivers stack like building blocks, and the "next block up" can't
install, unless the "base it stands on" is present.

The reason a video card can install at all, is because all video cards
strive to support VESA mode. That means the video cards are designed
to standards. (The only exception on compatibility, was a few Matrox
cards that had some bad habits.) A Windows OS (or Linux for that matter),
has a built-in VESA driver. It allows the computer to drive out
unaccelerated 640x480 (just like the BIOS screen), and that is necessary
so the user can see the screen, and insert the driver CD and finish the
job. Similarly, if you uninstall the ATI Catalyst driver and reboot,
the OS will go back to using the VESA driver. If you somehow manage to
trash the VESA driver, well then you're in a lot of trouble. In Linux
that isn't a problem, because you can run in console text mode (which
isn't pleasant, but it does allow you to eventually bootstrap yourself
back into a GUI world).

Paul

Fredd Wright

unread,
Jan 27, 2011, 1:13:31 PM1/27/11
to
Yep, it's in device manager correctly now and it's also in Everest in
addition to the "TV Card" i mentioned before. So, from what you said, the
problem may have been that i didn't reboot enough times. Interesting. That
never would have occurred to me. I would think the documentation for the
card would mention that. Something like, "restart the computer five times".
Thanks for all your help.

Fredd


"Paul" <nos...@needed.com> wrote in message

news:ihsbkh$o4p$1...@news.eternal-september.org...

0 new messages