186 réponses à ce sujet

[Geraldine]

Well, thats one way to fix it! And to date, thats the only solution that will work. Wish I could afford to do the same thing

[Jackal13th]

i Finley got the image shack thing figured out . mass effect 1 imageshack.us/photo/my-images/828/badpic.jpg//828/badpic.jpg/

Modifié par Jackal13th, 15 mai 2012 - 09:37 .

[2-b]

got the same issue (fx-8120, kingston 16gb 1600 mhz, sabertooth mobo, asus 5670)
so frustrated, just want to finish the game(on ilos know) without the glitches

[Leonxwerty]

Well I have a idea but I don't really know how to do it so I expect pros out there.

Why don't we change the name or the code for CPU to detect as another CPU?

For Example:
AMD FX XXXX --------> AMD Phenom or Athlon.
So do you think will this work for pros out there?

[Tomppak88]

Had the same probolem. Tried everything mentioned in this thread. The final solution was playing the Noveria and Ilos parts on a friends computer that, for some reason, didn't have this problem. Then again, he had the game installed a good while ago, and didn't remember if he had patched it - I downloaded it from steam not long ago, and it didn't run before it was patched. We didn't check version numbers, but I'd think it has something to do with different versions. Both have 8 or 6 core AMD's.

[Geraldine]

Thats another bios update (1003) from ASUS just installed and still no difference with Noveria. The cause is lost methinks :/

[Tisaku]

Question: Has anyone tried using Texmod to fashion a replacement for the things that are broken on Noveria and Ilos?

[Melorian]

 To save everyone else from trying it:

after seing that besides an amd-fx-cpu everyone encountering this problem also has win7, i tried to install it on winXP. long story short: it didn't work 

[Geraldine]

Hey Melorian, thanks for letting us know, I didn't think it would work, but it was certainly worth a try!

When I first discovered this bug with the AMD FX, I thought all that was needed was a bios update, but now, after 3 updates applied to my mobo, the bug is still there. As EA/Bioware has no interest in patching the game, all we can hope for is either for some kind person to create a community based patch and that sadly, may never happen or for AMD to pull their finger out and look into the issue

It would be nice though to know exactly why it's happening in the first place. Possibilities of timing issues between the cores has been said in the past. If this is the case, then all the FX CPUs (both 4 & 8 cores) must have this timing mis-match. I have a 4100 myself, but as I said it's just speculation on my part. :s

[Wabisuke]

Toadbasher wrote...

After playing ME3 i thought i wanted to go for a complete run on all 3 games and i reached noveria just a moment ago and i get the same problem....
It is strange because i played ME1 for like 5 times before never having any problems. But i upgraded my MB and CPU not long ago. Everything else of my hardware is the same even the OS is the same, Win7 64. So must be MB/CPU related.
I have all my crew, enemies and some objects turn black the moment i enter peak 15.

It doesn't make sense.... why would the cpu cause a bug like this?
Unless there is embeded graphic card or something like that in the fx series ( like intel i3-i7 series)

It is clearly a game bug since it only appears at that area..

Did the problem occur in the normal editions of ME1 too, or just the steam version?
If it is hardware-related it would make more sense to have something to do with the graphics card rather than the CPU..
On the other hand...If it was hardware-related it should happen constantly or at least more frequently during the game it wouldn't only affect just 1 or 2 places....
I tried the compatibility thingy, but it didn't work, i don;t have any extra armors in my inventory to change armors to my characters but that seems a little unlikely as well.

Modifié par Wabisuke, 31 mai 2012 - 10:52 .

[Geraldine]

Wabisuke wrote...

It doesn't make sense.... why would the cpu cause a bug like this?
Unless there is embeded graphic card or something like that in the fx series ( like intel i3-i7 series)

I know, it doesn't make sense to me either Wabisuke , but looking over this thread and at all the posts people have made, the only common denominator we all have is the AMD FX CPU. Both Steam and retail have the bug and it still persists in Windows 7, XP, Vista (anyone tried it on Windows 98 yet?) and with ATI and Nvidia cards and goodness knows how many different makes of mobos. "Something" in the CPU is causing it, but what it is still remains a mystery, at least for now.

[Melorian]

Geraldine wrote...

[...] Possibilities of timing issues between the cores has been said in the past. If this is the case, then all the FX CPUs (both 4 & 8 cores) must have this timing mis-match [...]

that doesn't seem to be the case. after thinking that to avoid timing issues between cores one should have to simply assign the game process to a single core, i tried that. it didn't work. (<-- i'm tired of that sentence, next time i post here i want to replace "didn't" with "did"...)

[Gorath Alpha]

You people do know that the "Rage 3D" forums are sponsored by AMD, right?

http://www.rage3d.co...isplay.php?f=65

[Gorath Alpha]

AMD is moving forward with the very different processor architecture that Bulldozer represents, including as part of the Trinity APU series. In the long run, they can't afford to turn their corporate backs on a marketing segment that really rewarded them when their A64 and X2 CPUs were very good for games. The forum in the URL above is not specifically for Radeon GPUs at all, which is why I named it.

Modifié par Gorath Alpha, 01 juin 2012 - 10:23 .

[Geraldine]

Melorian wrote...
 i tried that. it didn't work. (<-- i'm tired of that sentence, next time i post here i want to replace "didn't" with "did"...)

Yes you are right, it would be nice to see a successful solution appear on the thread for once. Perhaps one day I hope

[dodge83]

i have the same issue as you guys too

i assume we all have a 64bit setup? i dont recall anyone mentioning that

my machine
win7 64bit
Processor: AMD FX™-4100 Quad-Core Processor (4 CPUs), ~3.6GHz
Ram 8gb
graphics: AMD Radeon HD 6450


also i think its not the door but the wind/snow partiicales because if you try faceing the burning wreck and sidestep left into a visual of current of snow/wind as soon as you touch it you turn into a black blob!

just a theroy outside of the box

Modifié par dodge83, 15 juin 2012 - 09:08 .

[Geraldine]

You just might be on to something there dodge83, Ilos also has lots particles, but for me at least, the black blob thing still persists well into the Noveria mission when I am inside the complex. Only about the last third of the mission, (or so) does it finally clear up. All of the Ilos mission too is effected

Modifié par Geraldine, 16 juin 2012 - 10:36 .

[Tisaku]

Noveria is broken from the doorway to enter the facility on up to the Mira core section. the corruption will persist past the Mira core, in the areas to reactivate Mira but can be purged by changing armor.

[B-Ri.hoosier]

Changing armor didn't work, changing core scheduler didn't work, and setting Admin Privileges to XP SP3 didn't work. The only way I fixed this was by reinstalling the old 965 Phenom II Black (which is what the FX CPU replaced).

[Victor Brav0]

Same problem....

AMD FX-6100 CPU
nVidia GTX 560
8 GB RAM

Happens right when I enter peak 15, really annoying

[SapereAude1490]

Same Here

FX-6100
Sapphire HD6850
8GB RAM

I've sent a mail to AMD Customer Care. This is what they said:

"Your service request : SR #{ticketno:[##########]} has been reviewed and updated.

Response and Service Request History:

Thank you for contacting AMD!

Is this the only game that has an issue?

From the comments in the forum, the issue most likely lies within the FX -CPUs.

I understand your frustrations with the CPU. Please provide more information so we can help you troubleshoot.

If I missed any information about your issue please let me know, as my suggestions may change."

I've also uploaded this and gave the link to AMD. Waiting for reply now.

[Geraldine]

Thats the way to do it SapereAude1490 ! If enough people do what you did, perhaps AMD will sit up and take notice.

[SapereAude1490]

Well, it's a bit of a pain in the ***, so I understand why people don't bother contacting AMD. We should all send a mail to AMD, though.

If ME fans could raise $80000 for a charity or gather more than $1000 for cupcakes in matter of hours, we sure as hell can do this.

[Geraldine]

As Garrus might say,............indeed!

I sent in details of the problem to here http://emailcustomercare.amd.com/

[SapereAude1490]

I've got a new response, here goes:

"Your service request : SR #{ticketno:[#########]} has been reviewed and updated.

Response and Service Request History:

I will have this issue noted.

If the problem is fixed as soon as you swap CPUs i suggest you get the CPU replaced and see if the problem persists.

Did Bioware mentioned the problem only happens with FX CPUs?

Try another BIOS version although i believe the issue lies with the FX processor as well.

Please submit a RMA request. If the CPU was not purchased in a retail box, than please go to the manufacturer (Dell, HP, ASUS, Gateway Etc) of your system to get the warranty processed.

I suggest you submit a RMA request on the link provided if you wish to submit a request for a replacement CPU.

http://support.amd.c...yServices.aspx.

Please ensure you verify and have the correct (SN) Serial Number as well as (OPN) Part Number. Please ensure you submit a prove of purchase when you requested to do so."

So... They know it's a problem with the FX processor series, yet they tell me to ask for a replacement processor (presumably another FX CPU). Puzzling.
The weird thing is that there are no problems while playing this on my 7 year old system (AMD Athlon 64 2GHz). No black spots, all normal. Maybe I should just play Skyrim.