Could this be malware?


Recommended Posts

While I am not super up to speed on that specific board... Its all over the specs and info page for that board about its onboard display options, etc.  I did not see any * noting, model XYZ only sort of thing, etc.

 

I am not sure if OP built this himself, had someone build it, bought it from a build to suite site, etc.  But everything I show is that board for sure has onboard.. And also didn't see any mention of lite version or non onboard video version, etc.. Not saying I couldn't miss that - but its more likely they just plugged them up, or not seeing the dvi or vga port OP assumes there is no onboard video..  display port can be a bit misleading to those not familiar with them.. But hdmi is pretty easy to spot.. Pictures I see show the hdmi and display port right next to each.. Maybe mistook for something else?  Or they are plugged up and assumed not there..

6 hours ago, devnulllore said:

Ok so since I have a backup anyway I did yet another clean install, yes CLEAN, no extra drivers software or anything but what Windows does automatically. The first thing I noticed is the system ran quite smoothly until Windows automatically installed the video drivers then the stuttering began. Right now WINVER reports Windows x64 Version 1903 (OS Build 18362.329) so it seems to be  introduced by a Windows update or the video drivers or something to do with both. What now?

That right there is telling me the issue is with the video driver then, which is why I'm suggesting trying the onboard video, if your monitor doesn't support HDMI or DisplayPort than you may want to connect up to a TV but for all intents and purposes if you do in-fact have the TUF Sabretooth Z77 Motherboard than you do in-fact have onboard intel graphics.

20 minutes ago, jnelsoninjax said:

Grab SDI (Snappy Driver Installer) run it and let it find your drivers, I have used this program for a long time and no issues with it at all!

All we really care about at the moment is the video card and or the video driver. We know what card he has. He could go straight to NVIDA and grab the latest driver. First I would check the device manager and see which version of the driver windows 10 installed.

As a heads up, Windows 10 1903 has a habit of grabbing DCH drivers for graphics cards - If you then try to download the 'standard' drivers from nVidia and install them - the installer will fall over as the DCH driver windows fetches is incompatible with the standard driver.

 

I had this problem myself when I upgraded graphics card.

 

If Windows has installed a DCH driver, the best course of action is to download the standard driver from nVidia then unplug the ethernet cable from the PC (this will stop windows redownloading the DCH driver whilst you install the standard driver).

 

The next step is to remove the DCH driver (load up Device manager, right click the graphics card, choose 'uninstall device', then when the dialogue appears tick the 'delete the driver software for this device').

 

Once done, reboot your PC, then install the standard nVidia driver.

 

Once this is done, you'll then be fine to plug the ethernet cable back into your PC.

 

nVidia has info on DCH drivers here: https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch%2Fstandard-display-drivers-for-windows-10-faq

Ok, first if I do have onboard video why don't I see it in the device manager? Second I tried all the instructions to install the standard drivers and nothing worked. No matter what I did I could not get the standard drivers to install it kept failing. I have the latest DCH drivers that Windows installed in there now. Anything else I can try?

27 minutes ago, devnulllore said:

why don't I see it in the device manager?

Because most time when a discrete card is added the onboard is disabled.

 

Do you have the ports on the back of the PC?  Then you have it - just pull your discrete boot into the bios and make sure onboard is now enabled.

 

Example - here is mine showing my discrete card, but nothing more - but I for sure have onboard, since was just using it when my old card died ;)

 

video.thumb.png.e681f6a90c72cf729e8d3e6b0d5af623.png

 

If you have been messing with it for this long - what would be the big deal to pull the video card and test with just onboard ;)

 

edit:  Here I just did a show hidden and now see my old card, and the onboard.. the highlighted is my old card that died, and the HD is the onboard

showhidden.thumb.png.dc9a34fa3240d76fadecd64d6ed6617f.png

 

1 hour ago, devnulllore said:

Ok, first if I do have onboard video why don't I see it in the device manager? Second I tried all the instructions to install the standard drivers and nothing worked. No matter what I did I could not get the standard drivers to install it kept failing. I have the latest DCH drivers that Windows installed in there now. Anything else I can try?

Because when you have a dedicated graphic card most BIOS/Firmware disable the iGPU (unless your motherboard has that weird GPU switching feature that mimic's the MacBook Pro's), 

 

Second stop just relying on just looking at Device Manager when trying to determine your hardware specs, physically look at it and also look at the spec sheets for your specific model.

 

Third when you do test with just the iGPU remember to fully remove the NVidia driver (if you don't do a full clean install again...) since that may be what's causing your issue, where basically trying the same additive approach you did when did the clean install, this time with hardware, also when you do this it may be wise to remove any USB devices sans HID's (Keyboard & Mouse) to rule those out too...

 

1 hour ago, BudMan said:

edit:  Here I just did a show hidden and now see my old card, and the onboard.. the highlighted is my old card that died, and the HD is the onboard

showhidden.thumb.png.dc9a34fa3240d76fadecd64d6ed6617f.png

 

;) Both your old card and iGPU are "HD"s lol 😛 BudMan meant the Intel HD 😛 

Ok so I was finally able to get my system out so I could get the video card out and yes there is an HDMI port. I was just going by the device manger. I pulled the video card out and went into the bios but there is no settings for onboard video. When I tried to boot into Windows all I got was no HDMI signal and a black screen. I waited some time to see if maybe windows was going to do something in the background but I get no signal from the onboard video. Any ideas? Should the onboard video just automatically enable itself?

Onboard video should automatically disable and enable itself if/when a gfx card is pulled or not. Unless you have a really really old computer that can't switch by itself (2003 era)

 

The problem you are probably having is driver conflict. It is looking for your gfx card, and it isn't there.\

 

See if you can get into safe mode.

Well I did nothing different but it just decided to work after a couple of reboots. So far all that's installed is the Intel HD driver and I am having no stuttering at all. I will let you know after a few hours of using my system.

1 hour ago, devnulllore said:

Well I did nothing different but it just decided to work after a couple of reboots. So far all that's installed is the Intel HD driver and I am having no stuttering at all. I will let you know after a few hours of using my system.

So, just to confirm.. did you install the Nvidia drivers direct from Nvidia? If you had issues did you try using the Geforce Experience?

1 hour ago, devnulllore said:

Well I did nothing different but it just decided to work after a couple of reboots. 

Did you by change give the motherboard caps a once over? Any bulging or leaking? Just wondering seeing how the HDMI didn't work at first then just started spontaneously started working.

@warwagoncould have just been a simple driver conflict as he could access the bios while it was connected to the iGPU's HDMI port.

 

@devnullloreYou got that video card recently correct?  did you also get new drives recently too? if so... what's your PSU's wattage rating?

11 minutes ago, Matthew S. said:

@warwagoncould have just been a simple driver conflict as he could access the bios while it was connected to the iGPU's HDMI port.

AH, great point, didn't catch the part when he went into the bios after pulling the card.

52 minutes ago, Matthew S. said:

@warwagoncould have just been a simple driver conflict as he could access the bios while it was connected to the iGPU's HDMI port.

 

@devnullloreYou got that video card recently correct?  did you also get new drives recently too? if so... what's your PSU's wattage rating?

Just a thought too, when did the issue actually first occur (not counting the clean installs), right after a Windows update or right after a graphics driver update? if the latter try an older version of the driver but follow @ReAnimation's steps to remove the DCH version of the driver..

The more I think about it, it seems once I installed the update just prior to 1903 and they were the newest video drivers at that time, 431.36. i have been in contact with Nvidia about any issues with the drivers and they said there was an issue with that revision on and Windows 10. They claim it is an issue with Windows 10 and Microsoft is just releasing a fix this weekend. I don't see it yet but I will keep an eye out for it.

Oh also I tried and tried to get the standard driver to install but nothing works. I followed all the instructions mention here and even use the DDU utility but the standard drivers keep failing. What is the difference?

So after a few hours of no stuttering without the Nvidia card in I reinstalled the Nvidia card and let Windows decide what drivers to install. 436.02 (26.21.14.3615) Winver 1903 v.18362.329) and the stuttering has started again. Should I install Nvidia Experience and see if it updates my drivers? Wait for Windows update?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Indeed. But note that this has Wifi7, HDMI 2.1, BlueTooth 5.4, and 5G Ethernet, so even in the additional features list this bundle blows the Steam Machine away. And, with the money saved, one could improve this dramatically.
    • One of the strangest galaxies in our Universe could help answer some long overdue questions by Sayan Sen Image by Pixabay via Pexels | Not representative An international team of astronomers led by the Department of Astronomy at Tsinghua University has discovered an unusually metal-poor galaxy that may contain signs of first-generation star formation. The galaxy, named Metal-Pristine Galaxy COSMOS Redshift 3 (MPG-CR3), or CR3, was identified using observations from the James Webb Space Telescope (JWST), the Very Large Telescope (VLT), and the Subaru Telescope. The findings, published in The Astrophysical Journal Letters, describe CR3 as the most metal-poor galaxy known from the period known as "cosmic noon," around 11.5 billion years ago. Cosmic noon refers to a period when the universe was producing stars at its highest rate and galaxies were growing rapidly. In astronomy, "metals" refers to all elements heavier than helium, including oxygen, carbon, and iron. Because CR3 contains so few of these heavier elements, researchers say it closely resembles what scientists expect the earliest galaxies in the universe may have looked like. The discovery is significant because it could offer clues about Population III (Pop III) stars, the first generation of stars thought to have formed after the Big Bang. These stars are believed to have formed from gas made almost entirely of hydrogen and helium, before heavier elements were created inside stars and spread across the universe through supernova explosions. Hence this is why CR3 has been referred to as a "living fossil." Scientists have long believed that Population III stars existed only in the very early universe. As more generations of stars formed and died, they enriched surrounding gas with heavier elements, making the conditions needed for metal-free star formation increasingly rare. Because of this, researchers expected the formation of such stars to have largely ended after the epoch of reionization, a period when radiation from the first stars and galaxies transformed the neutral hydrogen filling the universe and made it largely transparent to ultraviolet light. CR3 appears to challenge that idea. The galaxy was observed at a redshift of z = 3.193 ± 0.016. Redshift measures how much light from a distant object has been stretched as the universe expands and helps astronomers determine how far back in time they are looking. In this case, the redshift corresponds to roughly 11.5 billion years ago during cosmic noon. Although the universe was already several billion years old by that point, CR3 shows characteristics more commonly associated with much earlier galaxies. Observations revealed exceptionally strong emissions from hydrogen and helium, including Lyα, Hα, and He I λ10830. Lyα, or Lyman-alpha emission, is a specific wavelength of light produced by hydrogen and is widely used to study distant galaxies. Hα emission is another hydrogen signature commonly used to trace active star formation, while He I λ10830 is produced by helium and can indicate the presence of very hot, young stars. The measured equivalent widths of EW₀(Lyα) = 822 ± 101 Å and EW₀(Hα) = 2814 ± 327 Å are among the highest ever observed in star-forming galaxies. Equivalent width is a measure of the strength of an emission line relative to the surrounding light, and such large values are typically associated with intense and very recent star formation. At the same time, researchers found no statistically significant detections of metal emission lines, including [O III] λλ4959, 5007 and C IV λλ1548, 1550. Emission lines act as chemical fingerprints that reveal which elements are present in a galaxy. Oxygen and carbon lines are commonly seen in galaxies that have already undergone significant chemical enrichment. Their absence in CR3 suggests an unusually pristine environment. Using abundance calibration methods developed with JWST observations, the team placed a 2σ upper limit on the galaxy's gas-phase metallicity of 12+log(O/H)<6.52, corresponding to less than 0.7% of the Sun's metallicity (Z < 7 × 10⁻³ Z⊙). Gas-phase metallicity measures the abundance of heavy elements in a galaxy's gas. A 2σ upper limit indicates that the true value is very unlikely to be higher than the quoted threshold. Even when accounting for uncertainties in the calibration methods, the most conservative limit remains 12+log(O/H)<6.95, making CR3 the most metal-poor galaxy identified at cosmic noon. The galaxy also appears to contain very little dust. Researchers measured a Lyα/Hα flux ratio of 13.9 ± 2.5, a result that suggests negligible dust attenuation, meaning very little of the galaxy's light is being absorbed or scattered by cosmic dust. Because dust is usually produced by earlier generations of stars, this finding further supports the idea that CR3 has experienced very little chemical enrichment. Further analysis using spectral energy distribution modelling, a technique that compares observed light with theoretical models, suggests that CR3 contains an extremely young stellar population only around 2 million years old. The modelling, which used Population III stellar templates, also indicates the galaxy has a stellar mass of approximately 6.1 × 10⁵ M⊙. The symbol M⊙ represents one solar mass, or the mass of the Sun. One of the key questions raised by the discovery is how such a chemically primitive galaxy could exist in a universe that had already spent billions of years producing heavier elements. To investigate this, the researchers examined CR3's surroundings. Their analysis suggests the galaxy may lie in a slightly underdense environment, with a density contrast of roughly δ ≈ −0.12. An underdense region contains less matter and fewer galaxies than average. The team suggests that this relative isolation may have helped preserve pockets of pristine gas. Metal-rich material expelled from nearby galaxies may never have reached CR3, while the lower rate of galaxy mergers and interactions could have slowed the mixing of enriched gas into the system. If future observations confirm these findings, CR3 could provide some of the strongest evidence yet that first-generation star formation continued well after the epoch of reionization. Such a result would challenge the conventional view that pristine star formation ended by z ≳ 6 and suggest that small pockets of metal-free gas survived much longer than previously thought. Researchers stress that more observations will be needed to determine the galaxy's true nature. Future spectroscopic studies with higher resolution and better signal quality could help confirm whether CR3 is genuinely hosting Population III star formation. The discovery is also expected to encourage searches for other similar galaxies, which could help astronomers better understand how the first stars formed and how galaxies evolved in the early universe. Source: Tsinghua University, IOPscience This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • "I think in the immediate absence of a partner to apply relief" In the words of Sterling Archer... "Phrasing!"
    • For me, the fundamental problems with these "smartglasses" is that they really don't work well for people with significant prescriptions and massively up the price if you use attached lenses if they have displays, and if they don't, then they're not actually "smart" anything, rather just connecting to your phone and relaying voice to an AI. In a few cases like this, they throw in small cameras to feed video to the AI. All around, these feel like both a solution looking for a problem, and the problems it tries to solve seem more easily solved by different approaches and designs. Oddly, if the rumours are true, Apple may actually have invented something for once and it kind of does this right: put cameras in ear buds and manage the interface to AI exactly as most of us do: tapping on an ear bud and saying "Hey Google" or "Hey Siri." That makes them compatible with almost everyone, can double up as a hearing assist device, an impaired vision assist device, a "smart" device... and answer your phone and play music. That just seems like a better solution all around.
    • Usually the bigger ones with many fixes/changes take a few, theyre an exception to the rule most likely
  • Recent Achievements

    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      452
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      107
    4. 4
      Michael Scrip
      84
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!