6 réponses à ce sujet

[mrfish88]

Hi everyone,

I am having a problem with Mass Effect 2, with a retail copy from play.com. 

• Mass Effect 2.exe v1.00
• Mass Effect 2 Launcher.exe v1.01
• Mass Effect 2 Config.exe v1.03
• Mass Effect 2 Uninstall.exe v1.03

My system specs:

1. OS: Windows 7 64x bit

2. CPU: Intel Core 2 Quad Q6600   2.4Ghz  Clock speed 2405 MHz

3. RAM - 4GB

4.Video - nVidia Geforce 9800 GT 512MB - Drivers 196.21  (NOTE: Have just noticed the driver version is blank in the Mass Effect 2 config...could that be something to do with it? 

5.Audio - Speakers (2- High Definition Audio Device) Driver Version 6.1.7600.16385

6. Direct X 10

7. PSU - 750Watt power supply unit.


Whenever I press play on the ME2 start up menu, my monitor switches off (Power Saving Mode), and then flicks back on to the blue screen of death.  I get the error code "BCcode 116."  This is the first game that I've ever had a problem with loading - I've seen posts on the forum where people were having problem with Dragon Age Origins, but that works fine for me.

I have downloaded RivaTuner and underclocked the Core clock and Memory clock all the way to the left.  I still had the same problem. I have also attempted turning off the audio and turned all graphics settings in the ME2 menu to minimum - still I get the blue screen of death.

I installed the game on the same disc drive, so it can't be the broken installation of using 2 disc drives.  I have also uninstalled the game and reinstalled - and that hasn't helped either.

I am really stumped! If anyone has any suggestions or ideas, I will be hugely grateful!
Thank you for your time.

[mrfish88]

Oh, on first installation I installed the Cerberus add-ons before attempting to play the game. Second time, I did not install them - so that narrows that down at least...

[Miriel Amarinth]

PS (yeah I know, shouldn't start a post with a PS but I'm doing it anyway ): the driver version in the config tool being blank doesn't mean much, mine is blank too and game works fine with 186.16 drivers.

First thing I'd probably try in your case is do a full clean reinstall of the graphics drivers, from start to finish. Last time I had a BSOD in a game it was due to messed up drivers.

To do a clean driver install first go to the Nvidia site and grab the latest 64-bit WHQL drivers. If you already have them redownload them just in case (unless you have a good reason not to, like a bandwidth cap).

Next, make sure you have a driver cleaning tool handy (I use Driver Cleaner Pro, which is free).

Now go to the control panel and uninstall your current graphics drivers. Once finished it will ask you to reboot your PC. Do this and reboot into Safe Mode (if you're not sure how, use Google to find out which key to press as this may vary depending on your type of Motherboard). If you miss the keypress and windows boots as normal, just restart the PC and again try until you succeed and get a window where you can choose 'start windows in safe mode'.

Once in Safe Mode run the driver cleaning tool twice, then restart the PC again as you normally would.

Now reinstall your latest 64-bit WHQL drivers that you downloaded earlier, if it asks you to restart then accept. Once done try running ME2 again and see if anything's improved.

If you still get the same BSOD you can try repeating the entire process above but using some older drivers that might offer better stability with ME2. Reverting to older drivers is known as a 'rollback'. Rollbacks are always worth a try, especially when you're having BSOD's.
I myself am using driver version 186.16 because I burned my fingers on some of the 190 series drivers last year when they gave me a BSOD in Fallout 3 every 20 minutes. Other good driver versions are the 185 WHQL and the 178.24 WHQL (although I don't know if those are still available).

Let me know if any of this helps.

Modifié par Miriel Amarinth, 14 février 2010 - 01:02 .

[Herethos]

Have you tried uninstalling/reinstalling the gfx or trying different drivers?
Maybe you're running the game in a unsupported gfx mode?
Perhaps just uninstall the nvidia ones and try it with the windows 7 ones that it installs automaticly and while using the default drivers, update your OS and install any service packs/hotfixes, then try messing around by installing the nvidia ones.
Are the fans on your gpu spinning and extra power connection connected to your gpu?
Basicly its trying to tell you that there is a problem with your gfx card or drivers.


http://msdn.microsof...y/aa469184.aspx

The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

http://forums.nvidia...howtopic=107831

Q: What is TDR?

A: TDR (Timeout Detection and Recovery) is a
windows vista and windows 7 feature. Its purpose is to detect when the
GPU stops responding, disable it and reinitialize it without the need
to exit windows or reboot.

Q: What does TDR have to do with atikmdag?

A:
A TDR event is reported to the end user by a notification bubble. This
bubble will indicate "The display driver [insert name here] has stopped
responding as was recovered." The driver name for all ATI systems is
atikmdag, for NVIDIA users the same error will be reported but with the
driver name nvlddmkm.sys. Atikmdag will also appear in the event viewer
log under the warning associated with the TDR event.

Q: What causes TDR to trigger an event?

A:
This is a very complicated question. The events can be due to almost
anything in your system hardware or software. This has caused much
confusion, as the same error is a symptom for everything from bad
memory to a software fault.

The following hardware issues are examples that can cause a TDR event:

- Failing overclock on CPU or GPU

- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory)

- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file

- Over heating of GPU or CPU again resulting in corrupt data being communicated.

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat.

The following software issues are examples that can cause a TDR event:

-Incompatible drivers of any sort (either GPU, sound, etc)

-Messy registry

-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers.

-Known
vista issues that sometimes cause corrupt information to be sent to the
video card from system memory (will be addressed completely in SP2, has
had various fixes applied since vista's release)

-Bad direct x files

-bad system files

-Bad
driver (some drivers will cause an event due to internal bugs, however
these are not nearly as common as many think due to all of the previous
things causing the same symptom)

Q: How do I fix my TDR events?

A:
This entirely depends on what is causing the event. As one can see
there are almost limitless causes. First you must determine if the
issue is hardware or software related, which can be quite a headache.

Q: Do new drivers cause TDR events?

A: Yes, they can bring about
new bugs that trigger TDR, this is common in all graphics manufacturers
drivers, and bugs appear from time to time. New drivers that utilise
more system resources also tend to bring to the forefront issues that
you may not have noticed before with other software or hardware. Some
drivers also do not play nice with each other; this was common with old
creative drivers and the 7 series CCC drivers causing many TDR events.

Addendum:
http://social.answer...b0-9c0adccc59a5

I have now fixed the problem after talking to pny the manufacturer of
the card - updating the bios worked. I tried manually at first and
failed but then found that my motherboard driver disks came with an
update program which did it for me and I managed to play an hour of
sims 3 without any troubles.

As you see it can be almost anything, thats worth trying too I guess, updating the bios that is. Be careful however since its possible to brick your motherboard.

Modifié par Herethos, 14 février 2010 - 01:41 .

[mrfish88]

Thanks for the replies guys, appreciated.



Have just had a fiddle about in safe mode, and used the Driver Cleaner Pro like you said. Deleted the drivers fully, restarted into normal mode and the default windows 7 drivers installed. Restarted, and then tried to load Mass Effect.



This time, instead of the BSOD, I got the monitor flicking from on to a blank screen (and the power light going from blue to orange showing its timed out/turned off). However, it came back on, and the PC hadn't crashed. Most importantly, I received a bubble message from the bar in the bottom right of the screen saying,



"Display Driver stopped responding and has recovered. Display driver NVIDIA Windows Kernel Mode Driver, Version 191.07 stopped responding and has successfully recovered."



I'm guessing that could well be significant in diagnosing the problem...That said, the 2nd time I attempted it I had the pleasure of the BSOD returning.



I checked Windows Update, and everything is upto date (except the drivers im playing with). I haven't tried a rollback yet - the rollback option was greyed out for me - where do I find older drivers to download and rollback to?



Those 116 causes you've listed look a nightmare for me...although I can't figure out why possible problems like GPU overload would only be occuring when trying to load ME2, and no other games..? I'm guessing that suggests its something more likely to do with the drivers, but other than that I'm still pretty stuck!



Any suggestions where to go from here?

Cheers

[Herethos]

Older drivers can be found:
http://downloads.gur...dows-7_c37.html
and
http://www.nvidia.co...aspx?lang=en-us

Keep in mind that the early drivers might be for beta version of windows 7.
Other than that its difficult to say reason for bluescreen just off the bat since some games like DA:O seems to be working ok.

Disable Phys-X gpu acceleration in nvidia control panel, try setting SLI or perhaps it says: Multi display/mixed-GPU acceleration to single display performance mode.

Also another topic:
http://forums.nvidia...howtopic=109407

As Miriel suggested try the 186.16 drivers, the guys in that topic on the nvidia forums also suggests the 186.xx drivers so perhaps there is something in it.

Anyway I suggest registering and posting here: http://www.techsupportforum.com After reading the stickies here: http://www.techsuppo...dows-7-support/
They should be able to help you better by analysing the dump files that windows creates when it blue screens. But they'll probably tell you the same thing that its the video drivers. But the real reason could be another driver thats causing problems which in turn causes the video driver to crash.

Modifié par Herethos, 14 février 2010 - 04:25 .

[The Time Mage]

I'm having a similiar problem. My game stops responding (in cut scenes) and then it either gives me the BSOD and the computer restarts or I am able to ctrl + alt + del and see the driver has stopped responding in the bottom right.

Mass Effect 2.exe v1.01
Mass Effect 2 Launcher.exe v1.01
Mass Effect 2 Config.exe v1.03
Mass Effect 2 Uninstall.exe v1.03

Win 7x64
Phenom II 940
4GB Ram DDR2
HD 4870 512mb


My drivers are up to date (I used driver cleaner in safe mode prior to install). I have updated my motherboard bios. I have tried the game with sound disabled and my processor at stock speed/volts. None of these have fixed the problem.

Modifié par The Time Mage, 26 février 2010 - 04:48 .