The (current) pinned thread at the very top describes how to get the report from this Windows utility. There has also been at least one member wanting to hijack that thread for his own purposes and attach a private DxDiag report there.

That is the preferred system diagnostics summary form suggested here on the Bethesda PC Tech Forums (for all gamesas game tech problems).

Have you been wondering what is most important in that huge report that the DxDiag utility generates? This is a leftover from a long while ago. I'll see about updating it (remove "Pentium" and insert "Core", for instance)

What kind of game did you buy? Retail or Digital?
What Geographical Region Version did you buy?
What language(s) have you tried installing?
Processor Manufacturer: AMD / Intel
Processor Type: Athlon 64 / Core / Phenom / dual core / quad
Processor Speed: ?.? Ghz (or the old AMD Performance Number)
Operating System / Service Pack: WindowsXP, Vista, W7, with SP # ?
System RAM: ? ? GBs (or MBs, if less than 1024)
Video (GPU) Manufacturer: ATI / Nvidia (only those are supported)
Video Card Model: (examples) Radeon x1650 Pro / Geforce 7600 GS
Video Card onboard RAM: ??? MBs
Video Card Driver Version: Catalyst ?.? / Nforce ??.?? (use numbers, not the word latest)
Power Supply Make, Model, and 12 volt amperage
Sound Card Manufacturer:
Sound Card Model:
Sound Card Driver Version: ?.?? (again, numbers)

There's a lot more, but those are the critical ones, named in a proper System requirements label (although in the case of FalloutNV, that's useless -- refer instead to the Fallout 3 requirements).


In any case, you need to provide specific details about the symptoms, such as error messages' exact wording, and any preliminary symptoms you may have been seeing / hearing, and system information. Otherwise, your problem report cannot be answered at all, and there are already too many unanswered questions here that do have DxDiag reports attached (just far more incoming traffic here than there are readers with time and experience to respond).

I should have included a suggestion to the effect that if you have exhausted the entire range of ideas revealed through a search of the forum archives, you should say so in your problem report.

And, I am now so disappointed over Obsidian's failure to deal with Windows 7 (64 bit) properly, and nVIDIA's Geforces specifically, I don't think there is any current reason to have any more message threads about the Geforces crashing, freezing, performing badly, showing white spots, whatever. We already have a couple of thousand of those in the archives right now, hundreds of which are unanswered, and there are already a half dozen assorted work-arounds and threads discussing those, that the Search can bring up, with the very simplest being the time-tested running in a Window option.

There has been a fairly busy week in here so far, and there are many of the Geforce / Win 7 questions stacking up; perhaps you aren't among those, however, if you include no data to work with, even if there were more experienced gamers present to offer answers, it's simply a case of no data in equals none back out.

A few of the "No-data" included messages have been coming in from folks who won't read the pinned message threads. Besides that method (the DxDiag Report in the stickied thread), you can get all of the needed information with EVEREST:

http://majorgeeks.com/EVEREST_Free_Edition_d4181.html

. This comes from one of your own posts. I find it odd that you continue to give advice when you have previously admitted to not knowing much about dxdiag.

Perhaps someday when you can actually read one and give some helpful advice I will give more credence to what you have to say in this department.

My apologies, somebody had to say it.

You're playing at being a left-wing liberal network newscaster and taking things out of context, instead of being honest. What I've said a hundred times, maybe a thousand, is as soon as the report goes border to border without formatting, it starts swimming visually, so that picking out useful bits is like trying to spell words with alphabet soup. It's got to do with my visual correction, certainly. I can, and do, read down to the first audio processor block, which doesn't tell much. An Everest report, on the other hand, is actually useful for something besides wasting forum space.

What the heck does politics have to do with this? I would recommend that you read the rules regarding discussion of that.

As far as reading a dxdiag goes, there is far more useful info there than you are obviously capable of making use of. Beyond the "audio block" there is info concerning things like codecs/filters some of which can and do wreak havoc with Bethesda's games, such as NERO, and even ffdshow do not always play nice with a persons rig when gaming. There is a reason why people request that someone posts their entire dxdiag, it is because it gives a more complete view of a persons rig and helps to determine what may be causing that persons problems. it It is these types of shortcomings that prevent you from giving useful advice.

Again, I apologize for providing you with the cold hard truth, but sometimes it is necessary.