Windows 8 Versus Windows 7: Game Performance, Benchmarked


Recommended Posts

We already know that the look and feel of Windows 8 is very different from Windows 7. But once you fire up your favorite title, does Microsoft's latest affect your experience? We test 10 games and talk to one of the company's SDEs to answer that question.

If you're a Tom's Hardware reader, I'm willing to bet you've endured your share of fresh Windows installations, perhaps even dating as far back as 1985 and Windows 1.0. This one, like those before, will give us new features. We'll love some of them, and we'll hate others. Things we've used for years will break, and other things we've needed add-on driver packages for in the past will work right out of the box. Certain capabilities have the potential to improve performance, and more overhead elsewhere will gnaw away at it.

Really, we don't expect to see gaming performance change in the move from Windows 7 to Windows 8. AMD even let us know prior to the FX-8350 launch that a properly patched Windows 7 machine shouldn't behave any differently from one with Windows 8 on it (that's why you didn't see us include Windows 8 numbers). Companies like AMD and Nvidia have had plenty of time for driver development, and proper support for modern graphics cards was in place on Microsoft's launch day. For the most part, once you fire up your favorite game, your experience should be pretty similar.

"But wait a second," exclaims the well-read, now-troubled gamer."What about Gabe Newell's statement that 'I think Windows 8 is a catastrophe for everyone in the PC space'"? Gabe seems to know what he's doing most of the time, Valve Corporation is a respected game development company, and Steam is a massive digital distribution platform. Of course we raised our eyebrows when he declared that Valve is investing serious resources into a Linux-based version of Steam and adapting its games to run on the open-source operating system. So, what's the deal, really? Is Windows 8 irreparably bugged? Should gamers avoid it at all costs and stay with Windows 7?

I saw an interview where Gabe claimed that Windows 8 has a terrible interface, and that everything is a lot more difficult to do in the new OS. To his credit, I've been using the RTM of Windows 8 for a while now, and I agree that it should be possible to completely avoid the Metro interface on a desktop PC. But I don't think Microsoft's latest is a sign of the apocalypse.

It's very brash to sweep the desktop-and-icon paradigm under the rug. And yes, this is going to alienate a lot of people. But I'd also like to think that the enthusiast crowd is pretty adaptable. Figuring out how to launch games from Steam isn't going to take very long at all, and after some hands-on time, the folks determined to learn their way around Windows 8 will do so. Gaming won't screech to a halt unless the operating system outright breaks an older title.

I believe Gabe's main issue with Windows 8, and it's one he's addressed, is the new Windows Store. This is Microsoft's equivalent of Apple's App store, and the company similarly takes a 30% cut of everything sold there. An ever bigger concern is that Microsoft might disallow certain software to run on its new operating system. Sound a little like Apple's closed platform? The development community is rightly afraid that Microsoft's Windows Store is going down the same path. And while it's clear that the company will exercise control over what is offered in its Store, nobody is certain what will happen outside of it. Hence, Newell is willing to spend (or at least threaten to spend) big money on development for Linux.

As far as I'm aware, Microsoft hasn't done anything to wall off Windows 8. You can install Steam without an issue, along with any other legacy application. Of course, this is a different story entirely on Windows RT, which is being limited to applications available through the Windows Store. As a result, it's going to be harder for Valve to make as much money on Windows RT-based devices, and developers have to be worried that Microsoft may go a similar route in Windows 8 as well, taking a share of each sale they make.

For the time being, then, aside from learning the new interface, the main concern you're going to have is how your favorite titles perform on the new operating system. Windows 8 does update DirectX to version 11.1 (Direct3D 11.1, DXGI 1.2, WDDM 1.2, etc.), but at least for the time being, we're not expecting much difference. Even still, we had to see for ourselves if frame rates or compatibility would be negatively affected. And so we're comparing 10 of our favorite titles in both Windows 7 and 8.

http://www.tomshardware.com/reviews/windows-8-gaming-performance,3331.html (View full article)

would be ppl saying that win8 dont have their drivers optimized and ****. The truth is that 8 is basically 7 with a selling store and a new start menu, nothing else, bah, dont forget the advertisment, that seems a huge step for a desktop OS. Its a pretty risky card to play, I think 8 its pretty hard to sell, more when both stores (phone and desktop) are differents, that doesnt make any sence. If there is an android for desktop, the game would change, even more.

+1

I don't rely on benchmark too...but hoping AMD and Nvidia will release stable and optimized driver for Windows 8 very soon

I'm running the latest stable Nvidia driver on laptop. Nvidia 675M.

Its performance is excellent and I have had no driver issues.

Are you having problems with ATI or nVidia?

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

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!