After 9 years game developer Adrian who also goes by the name Silent or CookiePLMonster, has finally fixed the strange ‘black blob’ artifacting/glitch issue in Mass Effect, that only impacted AMD FX and Ryzen processor systems.
Just in case you didn’t know about this old Game glitch/bug, when Mass Effect was released, the PC port was affected by a mysterious ‘blocky’ character texture issue, when AMD released its Bulldozer-based CPUs in 2011, and it even effects all the current AMD Ryzen processors. As you can see from this video the character models are all in ‘black shapes’.
As game developer Adrian points out in his lengthy blog post, vendor-specific game bugs are certainly not new, but they are typically related to GPU or driver issues. This seems to be the only graphical bug to affect particular CPUs from a specific vendor, which is AMD in this case. There are few existing workarounds that can fix this ‘black character texture’ issue, but the game developer decided to find out the root cause of this problem.
After some investigation, it appears that AMD’s FX and Ryzen processors don’t support the 3DNow! Instruction set, so the previous assumption was that the game engine will try to use these instructions whenever it detects an AMD processor. Though, according to Adrian, this doesn’t seem to be the case, because the game does not use that instruction set directly. The problem was first isolated to the Processor Specific Graphics Pipeline (PSGP) and Adrian found out that disabling this feature corrected the issue.
Upon further investigation, Adrian found that the issue was related to NaN values in pixel shader constants, but even after fixing the issue some of the in-game character models were still rendering as ‘dark grey’ images. After a bit more thorough testing, Adrian finally found the real root cause of this bug which lies with the game` engine being too sensitive to issues when it uses the AMD SSE2 instruction set, with improper calculations.
This whole process/testing might seem very complicated to some of you, so you should read his full Blog post for more details. But these are some of the important ‘technical’ points taken from his blog post:
- We verified that the game does not use 3DNow! instructions directly (only the system DLLs do).
- We found out that disabling PSGP fixes the issue on AMD processors.
- Using PIX, we found the culprit – NaN values in pixel shader constants.
- We nailed down the origin of those values to D3DXMatrixInverse.
- We fuzzed that function and found out that it does not give consistent results between Intel and AMD CPUs when SSE2 instructions are used.
- We accidentally found out that XMMatrixInverse does not have this flaw and is a viable replacement.
‘Adrian’ has actually posted a fix that works with both the Steam and Origin version of the Mass Effect game and doesn’t require an ASI Loader or any third-party software. Very few gaming bugs have affected a certain batch of CPUs instead of graphics cards, and Mass Effect 1 appears to be that PC game which was plagued with this black blocky texture glitch/bug.
Check this screenshot taken from the PC version of Mass Effect. As you can see all the character models are rendered in black.
It’s also worth noting that CookiePLMonster has released unofficial patches for Bully: Scholarship Edition, Scarface The World is Yours, GTA3, Far Cry and more.
Hello, my name is NICK Richardson. I’m an avid PC and tech fan since the good old days of RIVA TNT2, and 3DFX interactive “Voodoo” gaming cards. I love playing mostly First-person shooters, and I’m a die-hard fan of this FPS genre, since the good ‘old Doom and Wolfenstein days.
MUSIC has always been my passion/roots, but I started gaming “casually” when I was young on Nvidia’s GeForce3 series of cards. I’m by no means an avid or a hardcore gamer though, but I just love stuff related to the PC, Games, and technology in general. I’ve been involved with many indie Metal bands worldwide, and have helped them promote their albums in record labels. I’m a very broad-minded down to earth guy. MUSIC is my inner expression, and soul.
Contact: Email

Nice to have an alternative for this solution (in my last run a couple of weeks ago i used FPSc Engine and worked fine on my Ryzen)
its so funny, today, there still a bug like this for ryzen 3000….. ^^
Indeed…Its strange to know this bug has been active since 9 years or so !
Glad to finally hear this. Thanks for posting ! Even tho I never experienced this glitch since I”ve always used Intel CPUs, lol, but this bug seems very unique and weird, only effected by processors..
I wondered what was causing that.
read the article again. I think the last SSE2 instruction set is the main culprit imo. Though Metal messiah might give you a correct answer.
Awesome; good man
interesting….
Wait, Ryzen CPUs do not support 3DNow!, which is a technology developed by AMD??????
Yep! AMD deprecated these instructions somewhere in 2010.
i am a big fan of your work , thank you from the bottom of my heart for all ur hard work and releasing patches for one of my favourite game Gta san andreas
Just finished the trilogy for the first time today with a Ryzen CPU. Until today there was no fix except a console windows and viewmode set to unlit. Glad this has been fix, but I am really hoping for a remaster!
Metal messiah, I really love reading your articles ! Some of them have been really helpful. Keep it up ‘Metal’ man, lol ! 😀
Btw, if you don’t me asking this, do You like listening to Def leppard, Eagles, Dire straits, and Pink Floyd ??
Yes, I like ALL the sub-genres in METAL and ROCK, including “extreme” metal.. I even listen to classical, instrumental, and spiritual music ! Send me an email, so we can talk about music over there, since this is a gaming forum.
You might like these as well, ??
https://www.youtube.com/watch?v=_gtUD5ncyNA
https://www.youtube.com/watch?v=HRjKhNEvQQ4
https://www.youtube.com/watch?v=jhat-xUQ6dw
you gay bruh ? i would love to date you , i don’t mind being a top or bottom
Cool stuff ! Weird it took 9 years to fix this, and why can’t the game developers patch this bug in the first place ?
Did anyone out here experience this black glitch with Mass Effect ?
A couple of years ago i got the same issue with a AMD Fx-6300 CPU, so we are talking about a fairly old bug.