Recommended Posts

Just installed the Release Preview but I'm not sure which NVIDIA drivers to use.

There is a version for the Windows 8 CP, which is version 296.17. However, the latest version for Windows 7 is newer than this at 301.42.

Which would be better to use, anyone know?

I suggest waiting until next week for NVIDIA to release drivers designed for the Release Preview.

Using the default drivers that came with the release preview prevented me from using things such as Spoutcraft. Using NVIDIA's latest Windows 7 drivers cause graphical glitching like no tomorrow with something like Fruit Ninja.

Best bet is to just wait. :)

According to some of the graphics hardware forums 301.42 works perfectly. I don't see any reason not to mess with those then swap to the official ones later this week.

Read my comment. I have an EVGA GTX 260, using the latest Windows 7 drivers I had a lot of problems with metro-based apps such as Fruit Ninja and Internet Explorer

Running a Geforce GTX 260m, and I've had some issues with the latest Windows 8 drivers, but my guess is those were for the Consumer Preview version, despite the fact that they are semi-recent drivers. Haven't tried the 301.42 drivers, but I'm apprehensive about reinstalling it since there were so many drivers issues.

im having huge problems with NVIDIA drivers since the Consumer Preview..

if I uninstall the drivers and use the default ones in Windows 8 CP .. there were no crashes ... games ran perfectly.. but Photoshop didn't detect my GPU. With drivers it always crashed on playing utube or just simply playing a video in WMP.. although they run fine in VLC as it wont use hardware acceleration..

Now the problem with RP is that the default drivers that come with this one are the updated NVidia drivers from CP.. so they crash my system. :(

And I cant roll back or anything.. im just waiting for the latest drivers and hope it fixes this problem..

else ill have to download MANY old drivers and look for the one that work fine :(

anybody having this problem here?

[update] (6/6/2012): We have decided to postpone the driver release to pick up some additional fixes that we feel are necessary for a great Windows 8 experience. We apologize for the delay and will post the new driver as soon as possible.

http://blogs.nvidia.com/2012/05/nvidia-drivers-receive-windows-8-certification/

[update] (6/6/2012): We have decided to postpone the driver release to pick up some additional fixes that we feel are necessary for a great Windows 8 experience. We apologize for the delay and will post the new driver as soon as possible.

http://blogs.nvidia....-certification/

In other words, we are incompetent.

[update] (6/6/2012): We have decided to postpone the driver release to pick up some additional fixes that we feel are necessary for a great Windows 8 experience. We apologize for the delay and will post the new driver as soon as possible.

http://blogs.nvidia....-certification/

Disappointing. Still, it is a pre-release operating system and they are building the new drivers on a different architecture so it's not the end of the world. The regular Win7 drivers work fine.

Disappointing. Still, it is a pre-release operating system and they are building the new drivers on a different architecture so it's not the end of the world. The regular Win7 drivers work fine.

they don't.. I did some research and it seems all drivers after 289.xx cause the system to crash when playing a video on win8 CP or RP for my GPU. its universal ive read many ppl with the same gpu as mine having this same problem.

I installed 289.xx and they crash but recover after it. so I don't need to hard reset the system. I hope NVidia take notice of this.

they don't.. I did some research and it seems all drivers after 289.xx cause the system to crash when playing a video on win8 CP or RP for my GPU. its universal ive read many ppl with the same gpu as mine having this same problem.

I installed 289.xx and they crash but recover after it. so I don't need to hard reset the system. I hope NVidia take notice of this.

Hi so have you found a driver that is stable and not insanely slow? I have tested a few and like you found that the driver crashes and restarts itself but it's not viable at all.

Even 285.79 does this (pre 289.xx) :/

Using Microsoft WDDM inbuilt drivers for my 330M. Working fine so far.

I have nvidias annoying optimus setup, though disabled the intel gpu so only running with the nvidia 330m How ever! its not found as a sinlge gpu so basically I have to mod the inf to install drivers which is totally fine for the most part. it does also mean that I need the WDDM install as I can't install it from windows update. Can they be found anywhere? :D

Hi so have you found a driver that is stable and not insanely slow? I have tested a few and like you found that the driver crashes and restarts itself but it's not viable at all.

Even 285.79 does this (pre 289.xx) :/

Using Microsoft WDDM inbuilt drivers for my 330M. Working fine so far.

Well the old ones crash I know. But atleast they just recover.

Also the inbuilt drivers are really ****ty in the sense that no GPU acceleration software will detect the GPU.

Well on guru3d forum, some people mentioned that mobile driver of r302 works good with Windows 8.

Just installed 302.71, and they seem to crash as well. When I start a game of starcraft 2, the screen goes black, and comes back and core/memory settings on the gpu have reset. unfortunately.

Not that I start looking around, it turns out all the drivers I have tested do the same, Crash the drivers. :( Can't find WDDM anywhere either.

So I did a bit more testing and it turns out! Win8 REALLY does not like GPU overclocking with the current drivers available. Before I was way under what I "can" normally in win7 but after resetting clock speeds to default, starcraft 2 started without! crashing the nvidia drivers. Which is interesting! (sorry editor told me I didn't have permission to edit the post above?)

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

    • No registered users viewing this page.
  • Posts

    • Transmission 4.1.2 by Razvan Serea Transmission is a fast, easy-to-use bittorrent client with support for encryption, a web interface, peer exchange, magnet links, DHT, µTP, UPnP and NAT-PMP port forwarding, webseed support, watch directories, tracker editing, global and per-torrent speed limits, and more. Transmission has one of the lowest memory & resource footprints of any major BitTorrent client. Transmission's light overhead is one reason why it is so well suited for home NAS and media servers. Having been used by Western Digital, Zyxel and Belkin, Transmission gives truly impressive performance on almost any compatible hardware. Transmission is an open source, volunteer-based project. Unlike some BitTorrent clients, Transmission doesn't play games with its users to make money. Transmission doesn't bundle toolbars, pop-up ads, flash ads, twitter tools, or anything else. It doesn't hold some features back for a payware version. Its source code is available for anyone to review. Transmission doesn't track users, the website and forums have no third-party ads or analytics. Transmission 4.1.2 changelog: This is Transmission 4.1.2, a bugfix release. It fixes 20+ bugs and has a few performance improvements too. All users are encouraged to upgrade to this version. Highlights Fixed 4.1.0 bug that could cause duplicate HTTP announces to be sent to trackers. (#8639) All Platforms Reject benc data that has invalid characters. (#8577) Fixed a bug during the startup sequence where if one torrent failed to parse, subsequent torrents would also fail. (#8605) Fixed a bug that stalled some downloads at 99%. (#8654) Fixed a 4.1.0 upgrade bug that could overwrite utp_enabled and tcp_enabled settings. (#8658) Fixed a 4.1.0 crash that could happen when a peer supplied reqq value smaller than 32 in LTEP handshake. (#8713) Fixed a 4.1.0 regression that periodically wrote upload & download stats to disk even when Transmission had been idle since the last write, preventing the stats file's disk from hibernating while idle. (#8722) Fixed a 4.1.0 bug that prevented TCP peer connections on some systems. (#8748) Added safeguards to HTTP responses to prevent clickjacking. (#8749) Fixed edge case that didn't preserve the order of a batch of torrents when moving their queue position up or down. (#8782) Added sanitization for UTF-8 client names provided by peers during handshake. (#8809) Stopped appending redundant zeros to blocklist files when downloaded from a remote URL. (#8819) Fixed a build failure that occurred when building with link-time optimization. (#8540) macOS Client Fixed a 4.1.0 memory leak. (#8613) Fixed navigation focus issues in the Inspector. (#8792, #8810) Improved UI code to use less CPU. (#8832, #8833, #8835, #8836, #8842, #8846, #8851) Qt Client Fixed a 4.1.0 crash when parsing some RPC responses from older Transmission servers. (#8618) Fixed a 4.1.0 bug that saved both deprecated and current settings names to settings.json. (#8623) GTK Client Fixed a 4.1.0 bug that did not show translated logging level strings. (#8611) Fixed a 4.1.0 crash when toggling alternative speed limits. (#8709) Web Client Fixed a 4.1.0 bug that displayed timestamps in some dropdowns as 6.75:45 instead of 6:45. (#8624) Fixed a bug that could show incorrect torrent status when reconnecting to the server after a lost connection. (#8780, #8783) transmission-remote Improved transmission-remote console output for JSON-RPC 2. (#8799, #8805) Download: Transmission 64-bit | Qt 5 Setup ~20.0 MB (Open Source) Download: Transmission 32-bit | Qt 5 Setup Links: Transmission Homepage | Other OSes | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The sweet release of death has never looked more appealing.
    • Meh, just another dongle-haven downgrade compared to my Surface Pro 7+. Whenever I decide to upgrade in the next decade or so, it certainly won't be another microslop Surface with this enshitification trend they've been having after the Surface Pro 7+. Hopefully a future generation of the Framework 12 will be a real upgrade...
    • This could exactly be how our Sun ends but it's not as simple by Sayan Sen Image by Drew Rae via Pexels An international team led by Université de Montréal (University of Montreal) PhD student Érika Le Bourdais has found that the ancient white dwarf star LSPM J0207+3331 is still pulling in planetary debris, even though it has been cooling for about three billion years. White dwarfs are dense, Earth-sized stellar remnants left behind when Sun-like stars exhaust their nuclear fuel and shed their outer layers. The star, located 145 light-years away in the constellation Triangulum, is the oldest and coldest white dwarf known to have a surrounding disk of dust. The star was first spotted in 2019 by a citizen scientist through the Backyard Worlds: Planet 9 project. Its cool temperature immediately suggested that it was very old, since white dwarfs gradually lose heat over time. Using the W. M. Keck telescopes in Hawaii, astronomers later confirmed that the star shows infrared signals consistent with dust rings formed by asteroids breaking apart under its strong gravity. Such infrared excesses occur when a star emits more infrared light than expected, often because warm dust surrounding it absorbs and re-radiates energy. “This discovery challenges our understanding of planetary system evolution,” said Le Bourdais. “The fact that we still see planetary debris being accreted three billion years after the star became a white dwarf suggests that asteroids, comets, and even planets can remain in orbit around these stars for a very long time.” Spectroscopic analysis—a technique that studies light to identify the chemical elements present in an object—revealed thirteen heavy elements in the star’s atmosphere: sodium, magnesium, aluminium, silicon, calcium, titanium, chromium, manganese, iron, cobalt, nickel, copper, and strontium. Normally, heavy elements sink quickly in hydrogen-rich white dwarfs, making them hard to detect. “We expected to see only a few elements, but we found dozens!” explained Le Bourdais. The research paper adds more detail. The absence of carbon features suggests the debris came from a carbon-volatile-depleted source. The abundance pattern shows slight deficits of magnesium and silicon compared to iron but otherwise resembles Earth-like material. This points to a differentiated rocky body—one whose materials have separated into distinct layers such as a metallic core and rocky mantle—with a metallic core fraction higher than Earth’s. In other words, the star is accreting the remains of a large rocky object, similar in structure to Earth or the asteroid Vesta. “White dwarfs offer one of the only ways we can directly measure the composition of exoplanets,” said Patrick Dufour, co-author and professor at Université de Montréal. “When planetary debris come too close, they are torn apart by the star’s gravity and end up polluting its atmosphere, leaving a detailed chemical fingerprint of its composition.” The team also detected weak Ca II H & K line core emission, making this only the second known isolated polluted white dwarf to show this feature. These are specific spectral signatures produced by ionised calcium and can indicate unusual physical activity in a star’s upper atmosphere. The finding suggests that extra physical processes may be happening in or above the star’s upper atmosphere. The study stresses the importance of including heavy elements in model atmosphere calculations, since leaving them out can distort the inferred structure and lead to inaccurate stellar parameters. Earlier work suggested the star’s infrared excess came from two dust rings. The new analysis shows that a single silicate dust disk—a ring composed largely of rock-forming minerals rich in silicon and oxygen—can explain the observed signal at 11.6 μm, simplifying the picture of the system’s structure. The question of how debris ended up falling into the star so late remains open. One idea is that giant planets in the system slowly destabilised smaller bodies over billions of years. Another possibility is that a passing star disturbed the orbits of debris. “Future observations with the James Webb Space Telescope or archival data found in the European Space Agency’s Gaia mission could help distinguish between a planetary rearrangement and the gravitational effect of a close stellar encounter,” said John Debes, co-author and researcher at the Space Telescope Science Institute. Dufour noted that hydrogen-rich white dwarfs are the most common type, and the coolest among them are the oldest stars in the galaxy. “We didn't have the habit of looking for signs of accretion in them. This unique case motivates us to expand our search to more of these stars.” The findings show that even after billions of years, planetary systems can remain active and complex. Substantial accretion events—the gradual accumulation of surrounding material onto a celestial object—can still occur long after a star’s death, offering a rare window into the composition and fate of distant worlds. Source: University of Montreal, 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.
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      485
    2. 2
      PsYcHoKiLLa
      228
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      58
    5. 5
      neufuse
      56
  • Tell a friend

    Love Neowin? Tell a friend!