Re: Dxdiag Windows 7
Ikluk Kennedy
This tool helps you troubleshoot DirectX* related issues. Use the tool to generate a dxdiag text report file, which has detailed information about your computer's graphics, sound, and other devices. You can use the file when communicating with Intel Support about reporting graphics issues. The tool can also help determine if your device drivers are up to date.
Well, this information isn't actually required and won't affect anything except the dxdiag screen. If you built your own PC, it won't necessarily be filled in. If you purchased a computer from a manufacturer, they tend to put a model name in there.
In terms of finding out the model, it may be an idea to check any receipts for the computer. Is there a reason you need to find out? Perhaps you are actually looking to find out which hardware is in the computer instead?
To change what is displayed, it's stored in this registry key: HKLM\SYSTEM\CurrentControlSet\Control\SystemInformation. If you access this via regedit.exe you should see a few keys, one if which will be called SystemProductName.
A technical support forum from a big company (I guess they know what they're doing) asks me to paste the contents of the file in the forum, for them to understand if my problem is caused by something in my system.
Essentially though, an attacker must work out what your system is (and this has no obvious Personally Identifying Information), and somehow find a specific driver of OS exploits. It's probably too much work to be worth it for most.
System Information: Mostly innocent. Machine name and exact OS version's there. If someone knew how to get to your system in the first place, and there was a specific issue with that version... maaaybe.
Preferred DirectShow Filters, Media Foundation Transforms,Media Foundation Enabled Hardware Categories,Media Foundation Byte Stream Handlers, Media Foundation Scheme Handlers, Preferred Media Foundation TransformsDisabled Media Foundation TransformsDisabled Media Sources: ALL TEH CODECS. Probably completely useless to anyone.
This depends on how paranoid you want to be. The dxdiag.txt file generated by using the Direct X Diagnostic utility will contain a lot of information about your computer and depending on the type of user you are, one particular thing may directly identify you (if you're the kind of person to name your PC Zachiel-PC).
There is a WineHQ for dxdiag, and I do recall seeing some howto about somewhere on
how to make it run, but like I say, it doesn't prove very much as the results it
obtains are often meaningless...see;
More importantly however, since the user mentioned having played the game with sound before, I provided an older version of the game to both and both confirmed having sound with that older game version.
We were using FMOD 2.01.07 on that older game version.
There was a recent patch that changed the behavior of IAudioClient that would explain the difference between 2.01.07 and 2.02.05 you are seeing. If the issue is what I suspect, then I recommend getting the user to disable all audio devices expect the one they intend to use. According to the dxdiag, both users have additional audio devices (DELL S2721DGF and AMD HDMI Output).
Whenever I open a 3d-accelerated game my computer will freeze and require a reset. Games include Mechwarrior 2: Mercenaries, Heavy Gear 2, and Half Life. Opening 2d games appears fine such as Putt Putt Enters the Race or Doom 95. What would be the cause of this? I've tried swapping out my gpu to a FX 5200 PCI, installing different nvidia drivers (45.23), and both removed and reinstalled my audio drivers, none of which worked. What would be causing these crashes? I've purpose built this pc to play old games, but most of the ones I want to play won't run. Could it be something to do with directx? All the problematic games use directx, but they all use different versions from 3 up to 7/8.1.
Have you run the tests in DxDiag? Assuming that you're running Win98 SE, I would do a clean install without any unofficial service packs, they seems to hurt more than they help. KT7AGuy put together a guide for Windows 98 installation: Generic Win98SE Installation & Setup Guide
DirectDraw test passes for my display in dxdiag, but Direct3D crashes dxdiag.exe. The program shows my display supports acceleration for both DirectDraw and Direct3D, but also shows some files out of date.
I can try a fresh install as a last resort, but directx seems the most likely culprit. How would I address the outdated directx files error message? I've already installed directx 8.1 from the files included with my gpu cd.
As Repo Man11 said, stay away from unofficial service packs which tend to do more harm than good with those third-party "patches". If you want to update Windows 98 SE, either check the Windows Update Restored website or get the Windows Security CD from February 2004.
That isn't normal and I would consider reinstalling Windows without any unofficial stuff at this point. Updating the DirectX runtime libraries usually don't cause troubles (which is a pet peeve of mine, each version since 8 has separate DLLs) unless you have crappy drivers installed around.
Dxdiag reported old files because I wasn't running my host's version of dxdiag (oops). Running the proper executable shows a successful 3d test with no outdated files. However, directx games still freeze my system.
Am I going through the steps in correct order? Motherboard drivers -> directx -> gpu drivers -> sound card drivers? My gpu manual instructs me to install directx before my gpu drivers, and a video on windows 98 from PhilsComputerLab shows sound card drivers being installed last. This is why I have gone through these steps in this order.
Are you sure your copy of Win98 SE is good?
Try another reinstall, but this time check dxdiag for those warnings before installing any drivers. I think SE comes with 6.1 out of the box. Then install just the video drivers and test.
My copy of windows is fine. I've burned multiple cds from different sources to no effect. I can install the same iso in a VM and am able to play some directx games that way without issue.
The problem persists without any sound card installed. Using integrated audio, which was disabled before with both jumper and bios settings, and only a video card installed still results in the same freezing.
Freezing occurs regardless of directx version. 9, 8.1, 8, 7, and 6.1. It doesn't make a difference.
I've tried a pci FX 5200 gpu and different ram. Same result.
This is driving me insane. I must have reinstalled windows a dozen times by now. Perhaps there is some hardware issue like with my chipset or motherboard? I've also read that newer power supplies, which I'm using, may not provide enough current on the 5V rail. The 600W Corsair unit I'm using is rated for 20A for its 5V rail. Is that sufficient? Assuming it's not shared somehow and is actually providing even less current. I'm at the end of my rope and ready to give up.
Maybe try setting the BIOS options to defaults if you haven't already, could be something there that's interfering. I've had weird issues with corruption, crashes, and freezes with my system that resulted from one particular option being enabled, "Write Cache Pipeline". Looking at a manual for your board, your BIOS has an option called "Pipelined Function" that's enabled by default, but I don't know if that is doing the same thing as mine or not. You could always play around with different options in there as well and see if the freezes happen to stop.
Disabling Pipelined Function in the bios had no effect, unfortunately. I originally started this journey with default bios settings. I have since adjusted ram timings and disabled unused peripherals like on-board parallel and serial ports.
I've finally found the issue! The culprit? My chipset's AGP driver. A fresh install without installing my chipset drivers has yielded a system finally free of this freezing issue. I had previously tried an FX 5200 PCI GPU, but only after installing the AGP driver. Even without an AGP card installed the driver would still somehow cause an issue. I had read some forum posts stating that this ALi ALADDIN V chipset has AGP issues with K6-2 CPUs, so I decided to try running the system without it. Re-enabling the pipelined function setting in my bios doesn't cause any issues either. I'm so happy to finally figure out the cause especially since this means my hardware is okay.
You can use nvidia-smi.exe to monitor GPUs. Please use a windows file find utility, such as the one available in Windows File Manager, to locate the install location of this utility on your system. The utility has command line help available (run with -h switch).
1) In Windows 7 and 8, you need to click the Start menu which is usually at the bottom-left corner of your screen and go to the "Search For Files and Programs" box to search for "dxdiag". For Windows 10, you can just type in the search function in your taskbar or just start typing while your start menu is open. You'll type in ''dxdiag'' and select ''dxdiag'' from the search results.
2) The DirectX Diagnostic Tool window will come up. Click on ' 'Save All Information'' to save the file on your computer. You can then choose the location where you want to save it just like any other file. We recommend saving it to your desktop.
3) Find the file ''dxdiag.txt'' you saved and send it as an attachment to your support email or chat.
Anyone familiar with clamav knows that in heuristic mode, it likes to flag lots of things as being infected that are actually fine. So when it detects something, I like to also scan it with virustotal.com. In most cases, virustotal shows 1 or 2 matches by some obscure anti-virus, and we can be pretty sure the file is fine. But scanning this dxdiag.exe file shows 16/70 detections!
03c5feb9e7