ATI & NVIDIA on the same computer

[calvario]

Hello,

I register on this site for the following reason:

At the beginning of the year I got a new computer. I got a GA-MA785GM-US2H motherboard. I am running windows 7 ultimate 64 bit, 4Gigs of RAM, AMD Phenom II X4 965 black edition, and Ultra 650 power supply. I have a video card, Geforce 220 GT and I have it hooked up to 47 inch Vizio HDTV.

My first question – is it a good idea to have this video card with this motherboard? The chipset drivers for the motherboard are ATI and obviously the video card NVIDIA. Can this only cause trouble?

Second question – It maybe a sign of what could be the two drivers being on the same machine. When I am watching movies, I can see during the playback, some flickering on the video. It’s a horizontal line, either on the top part of the screen or the bottom part.
I have the latest drivers from NVIDIA. The onboard video is disabled on the BIOS.
Sometimes, when I leave the computer locked and walk away, come back say 10 minutes later, I try to log in and the screen goes black I can see text, it’s white but I have to cold boot the computer to get it working right again, the video that is. The resolution that I currently have is 1920 X 1080 at 24hertz. Is this a good resolution to have it at? Would this be the reason for the problem I described before?

I have tried Video LAN and windows media player, the two of them have the same flickering.

If you need more information please let me know. Any advice you can provide, I would really appreciate.

Thanks!

 

[ThePizzaMan]

um thats a good res as long as it is what your tv supports.... it could be that it doesn't like it, did you try uninstalling the ati drivers?

 

[Frostmourne]

That card is pointless, seeing as the onboard GPU is perfectly acceptable for everything except gaming. Uninstall the nvidia drivers, take out the card, PC on, enable onboard graphics. See if you get graphical corruption then.

 

[Night Hawk]

Hello calvario Welcome to the Se7en Forums!

Your main problem is not having an NVidia card installed with the onboard disabled but likely have the power options set to turn the display off automatically after so many minutes. Once the system switches the display to the standby mode you need a full restart in order to refresh the signal output to the tv itself to put that back in normal display mode.

The native resolution for the tv is the 1920x1080. With the ATI for the onboard installed that would cause a software driver conflict. Removing any ATI drivers for the onboard while the NVidia card is in along with disabling the onboard under display adapters in the Device Manager would be the things to try there.

 

[calvario]

Thank you guys for your replies.
I had initially installed the video drivers for the on-board ATI video display. I removed it after and only installed the chipset drivers. I went to the AMD website and downloaded from there.
I will try taking out the card, removing the NVIDIA drivers and test with the on-board.

Also, I installed sifsoft sandra today and ran one of the test. While the test was going on, it checked the card and I received an error that the video driver had stopped working, the screen went black twice for a few seconds. There must be something going on with the card then.
I was able to save the information from one of the crashes from the NVIDIA card. You can see it below. I hope it's not too long.
Thanks!

---------------------------
Fatal Error
---------------------------
Fatal error occurred. Please send the following information to the application developer at [email protected] (You can copy this text by pressing Ctrl+C or use the log file in the installation directory (must Run as Administrator in Vista+)): Version 3.0.1.0, OS: Microsoft Windows NT 6.1.7600.0 Message: An unspecified error occurred on the render thread.
Stack trace: at System.Windows.Media.MediaContext.NotifyPartitionIsZombie(Int32 failureCode)

at System.Windows.Media.MediaContext.NotifyChannelMessage()

at System.Windows.Interop.HwndTarget.HandleMessage(Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

at System.Windows.Window.ShowHelper(Object booleanBox)

at System.Windows.Window.Show()

at System.Windows.Window.ShowDialog()

at WBFSManager.MainWindow.AddCommandBinding_Executed(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)

at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)

at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)

at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)

at System.Windows.Input.CommandManager.TransferEvent(IInputElement newSource, ExecutedRoutedEventArgs e)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)

at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)

at System.Windows.Controls.Button.OnClick()

at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)

at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)

at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

at System.Windows.Input.InputManager.ProcessStagingArea()

at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)

at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)

at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)

at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

at System.Windows.Application.RunInternal(Window window)

at WBFSManager.AppMain.Main()
---------------------------
OK

 

[Night Hawk]

Have you gone into the device manager and disabled the onboard video item there? In addition to seeing the onboard disabled in the bios any item for the onboard in the DM is best disabled as well to prevent driver clashes even if it was an ATI card installed. The two will conflict automatically.

With both disabled having the ATI drivers on shouldn't effect the NVidia drivers since those out of the loop with that taken care of and there if needed. Another thing to look at is how you are plugged into the tv since you are using that as the primary display. HDMI, S-Video, or other?

 

[calvario]

Hi Night Hawk,
The onboard does not show up on device manager. I checked to make sure and ther is nothing there. My connection is HDMI from the NVIDIA Card to the Vizio TV.

 

[Night Hawk]

That solves any driver clash at least while the Windows updates if left set to automatic will still download and install those likely. One trick was to let them install and disable the DM item once found to insure no conflicts.

The next item on the list would be how well the detection of the tv is compared to running a standard or widescreen lcd monitor. While all new tvs seen out now are lcd they still lack a bit for use as monitors for pc while this is an available option for many. Your high res lcd monitors on one hand run at 60hz compared to the tv's 24hz as one factor resulting in the flickering problem.

When checking for Windows updates manually which is one idea look in the optional hardware updates to see if one is seen for Visio. Typically with any recent or new install of Windows the driver for the particular monitor detected will be seen included. If one is found for that tv or model series it could be a help. The other option is to try a regular pc lcd if you have one onhand to see if the problems are seen then.

 

[stormy13]

The resolution that I currently have is 1920 X 1080 at 24hertz.

The 1920x1080 I can see, but why are you forcing a 120 Hz TV to run at 24 Hz?

VIZIO 47" LCD HDTV | VIZIO

Might eliminate the flickering if you let it run at its native resolution and refresh rate.

 

[Kipper]

Lots of information in this thread. If you would like to keep the nVIDIA card as your GPU then:

Go into the BIOS and disable the on-board video

Run "Driver Sweeper" and delete the ATI Video drivers and I would also delete the nVIDIA drivers as well

Then download the current nVIDIA drivers for your card and reinstall them.

That should take care of all the problems.

http://www.pureoverclock.com/downloadget.php?id=18&file=1&evp=4dc0f32d154c5c8c5d47ef0b49e08b6dDriver Sweeper

 

[Night Hawk]

I looked at that as well but wondered if it was simply a typo for a 24" screen which made no sense either for the 47" tv. The native resolution is correct while you should be running at the native refresh rate as stormy13 pointed out. That should have been set as default as well by Windows upon the initial detection.

 

[calvario]

Thank you guys for all the replies!
I'll try setting the resolution to native. Just to let you know, at the beginning it defaulted to this 1920X1080 24hrtz. I thought that this was the normal one. I'll try the other one and report back.

Thanks again!