Windows Vista Bugs
If you're new here, you may want to subscribe to our RSS newsfeed so you don't miss out on all the information, news, tips and tricks.
Thanks for visiting!
Please post us details of any bugs or issues you’ve found in Windows Vista. We’ll report them to Microsoft on your behalf and save you the risk of being charged loads of money!
Please report it in this format:
1. Summary of bug
2. Steps to reproduce the bug
3. Outcome/Application Output/Errors Being Report
4. Other info
e.g.
1. Summary of bug
Display driver crashes a dozen times a day!2. Steps to reproduce the bug
Turn the computer on and use it! No pattern can be found as how to make the crash happen.3. Outcome/Application Output/Errors Being Report
Error balloon from the system tray announcing the system driver crash.4. Other info
Using an NVIDIA graphics card.
June 24th, 2007 at 6:57 am
The SoundBlaster Audigy cards (I have an Audigy 2 ZS) and the game Battlefield: 2142 do not work together in Vista.
[Game will launch, all other crash issues people have reported don't affect it, but trying to load an actual map or pressing the "audio" options menu will kill the program.]
I disabled the card in Vista - boom, the game runs.
I removed the card from my case to allow onboard audio to kick in - boom, the game runs.
Not sure if MS is going to do anything about this, but I’m afraid my card is now useless.
June 24th, 2007 at 5:40 pm
This sounds more like a Creative driver or a Battlefield game issue. Games have always been notorious for having to run with full administrator privledges, which under Vista will cause all kinds of issues! Some gamers are also very down on the quality of Creative drivers! It is most likely that Creative and/or EA Games, the developers of Battlefield, need to fix this issue to meet the new Vista security model.
You should still be able to keep the card installed and run the game. May mean changing the sound settings in Control Panel when running the game and then restoring them once you’re finished.
It is also worth installing current up-to-date drivers and ensuring the game is fully patched.
June 25th, 2007 at 4:14 am
On another note, what’s up with the “check online for solutions” button not offering feedback? All the times I’ve pressed it, it has *once* given me information (about Nero software), whereas all the other times nothing happens. A little “no information found” message would be wonderful, eh?
Back to BF2142, having been able to play last night in software audio mode, I point my finger squarely at Creative.
Or perhaps both EA and Creative: you can’t enter the control panel in the game with the soundcard installed! Now that it’s out, I was able to set it to “software mode”. The interesting question will be whether it’ll stay in software mode and not crash if I re-install the card. Should be an interesting little experiment. Had to give it a day’s rest, though, seeing as how I’ve been fiddling with my case all day.
Thanks for the link - I noticed that it actually *is* listed in compatible as long as your graphics card can handle it (”Battlefield 2142(64bit) - Same settings used on XP, crashes to desktop at every map change (after a certain period) due to low video card memory (256mb).”)
June 25th, 2007 at 1:29 pm
>>>what’s up with the “check online for solutions” button not offering feedback?
Maybe you’re the only one who’s having problems therefore Microsoft haven’t got anything to go on :-).
Seriously, they take the information sent to them seriously and work on the issues based on what seems to be the biggies. They probably haven’t got around to analysing the type of crashes that show no feedback.
June 26th, 2007 at 6:25 am
So I gather they’re automatically collecting crash info now, eh? In XP they made it much more obvious you’re submitting info - sounds much more “silent background”-ish now, eh?
June 26th, 2007 at 7:57 am
Have a look at this article:
http://technet2.microsoft.com/WindowsVista/en/library/03a97dba-6b24-42c7-81f0-fb751f6e839d1033.mspx?mfr=true
July 2nd, 2007 at 6:28 am
Interesting. As was this: http://cubicspot.blogspot.com/2007/06/why-windows-error-reporting-wer-does.html
On the strength of the above post, and moreso because nothing useful has happened, I’m just disabling it.