Aller au contenu

Photo

igdumd32.dll Rendering Error


  • Veuillez vous connecter pour répondre
14 réponses à ce sujet

#1
Serenity Frost

Serenity Frost
  • Members
  • 3 messages
I have really exhausted all options here, so please bear with me as I explain.

I have a digital copy of Mass Effect and Pinnacle Station from Origin. I'm currently using Windows 7 Home Premium 64bit (which I suspect is the problem already) and the laptop is more than capable of running Mass Effect according to systemrequirementslab.com.

I have redownloaded and reinstalled the game. I have tried running as an admin, making a new user account, compatability mode, downloading the latest patch and BDtS. I have changed my CPU affinity and I have updated my graphics driver. Intel® Core™ i3-2310M CPU @ 2.10GHz - DV: 8.15.10.2509 (8/31/2011) I installed the latest versions of both Dx9 and Dx10.

Even with all that done I still recieve the same error message. When I use Esc to go to the menu.

Now, when I first installed the game, before going through most of the steps above, I got this message.
http://imageshack.us.../unledjnxr.png/

So I contacted EA support via the phone and the lady on the line really did everything she could think of to help me (the rest of the things on the list, in fact) and there was a change, but it was just in what the message said.

In compatability mode XP-SP2 I get this message here.
http://imageshack.us...unled1rhwi.png/

As you can see, the information on the top half change addresses, but the problem is still with igdumd32.dll.

With compatability turned off I only get the top half of that error message.

Is there anyone out there who can tell me exactly what is going on?

EDIT: I should also note that I do have igdumd32.dll in my folder and I also downloaded a dll file specific to Origin called Outl60.dll. I was told to put that in the Origin folder and replace the one it already had, but I never had the dll in there to begin with. It wasn't in any subfolder either. I put it in the Origin folder anyway.

Modifié par Serenity Frost, 02 novembre 2011 - 10:16 .


#2
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
There is a sticky pinned on top describing how to request help here. Please follow it.

#3
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Systemrequirementslab.com is a useless website that goes by the adage "if the number is higher, its got to be better". Thus, it will think a HD6450 is better than a HD5790.

Because we dont have any system specs to work by, going by the error message, I'm going to guess that you're laptop is running an Intel graphics chipset. If this is the case, the game doesnt support Intel graphics, and you're out of luck.

There is a thread buried somewhere in this forum on how to get it running with the Intel chipset, but dont expect anything decent in the way of quality, or framerates.

#4
Serenity Frost

Serenity Frost
  • Members
  • 3 messages
Thanks for the confirmation guys, and I did see the sticky, but all the info it asked for didn't really apply as it was clearly a graphics problem. I don't like wasting people's time when I can be concise. Even if it's in a slightly rambling way.

Don't take that to mean I think I know everything about computers. I most certainly don't. If I'm wrong in that feel free to enlighten me.

In the mean time I'll instal it onto another computer that uses Nvidia and see how that goes. If it doesn't work I'll just have to return it and try to pick it up again if I ever manage to get an xbox. Thanks again!

Modifié par Serenity Frost, 03 novembre 2011 - 01:11 .


#5
jahuda

jahuda
  • Members
  • 8 messages
Serenity, I am having the EXACT same problem and I get the exact same error messages. I have both Mass Effect 1 and Mass Effect 2, and whenever I press the 'esc' key to pause either game, the game stops responding and crashes to the desktop.

The crazy thing is that these games both worked perfectly well on my laptop 6 months ago. As a matter of fact, I beat both of them, and I don't remember any performance issues occurring. This issue is driving me nuts because I KNOW it's not the hardware.

I am using the high-end 13" MacBook Pro, the ones that came out in February. I installed Windows 7 on this machine back in February and played these games, then I uninstalled Windows because I needed the harddrive space for a while. This month, I reinstalled Windows 7 and reinstalled the games, and like I said, both ME1 and ME2 crash to the desktop when i press the escape key. People will say my computer is not able to run these games, but that's not true, because like I said I beat both ME1 and ME2 with this computer. Furthermore, I tried installing the games on my parents PC and it also had the exact same issue. It's just so weird.

As far as problem solving goes, I downloaded a new igdumd32.dll file and put it in my system32 directory (it wasn't there before).  That didn't work.  I also tried running the games as administrator, which didn't work.  Compatibility mode also didn't work.

If you find a solution, please let me know!

Modifié par jahuda, 13 novembre 2011 - 04:30 .


#6
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Igdum32.dll is a file associated with intel graphics chipset. The intel graphics chipset is not supported by Mass Effect 1 or 2. There is a thread floating around telling you how to get it working, but as it is not officially supported, good luck getting it running at a decent framerate.

#7
jahuda

jahuda
  • Members
  • 8 messages
do you know where to find the thread you mentioned? because i haven't been able to find it. again, when i played the game on my computer earlier this year, the framerate was fine, albeit on low settings. the game runs fine even now, actually. i am able to go on missions, move in and out of cities, talk with people, watch cinematic moments... the only thing i can't do is pause the game.

#8
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
http://social.biowar.../index/6267063/

#9
jahuda

jahuda
  • Members
  • 8 messages
THANK YOU for looking that up for me. i tried running the game in compatibility mode after turning off UAC. unfortunately, the same problem persists. hopefully someone will stumble upon a solution. i've kind of given up for now. i wonder if anyone has had success reverting to an older version of drivers. oh well.

#10
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages

Bogsnot1 wrote...

Igdum32.dll is a file associated with intel graphics chipset. The intel graphics chipset is not supported by Mass Effect 1 or 2. There is a thread floating around telling you how to get it working, but as it is not officially supported, good luck getting it running at a decent framerate.

Everyone reading this thread needs to adjust their expectations.  Intel simply isn't interested in gaming enough to do either of the two things involved, which are to actually design a usable device, first, and then to develop and make available the appropriate driver to support it.  They have very gradually, incrementally, inched upward from 1998 to 2005 level over the last three years, but we aren't talking about the X1900 XT or the 7900 GT, but rather the next lower cards back then, the X1600 and the 7600. 

Actually, they don't have the image quality that the Radeon had then -- they don't have the pixel shader power for it, but they now, with the Sandy Bridge, do have the speed of the 7600, when you can get a driver you can use.  The rest of their video chips are a great deal slower than those in Sandy Bridge CPUs, although the image quality remains at the 2005 level fot the best of the rest (in their i3 / i5 CPUs). 

Assuming that you jump through the right hoops to get an Intel video chip to operate in the game, ypu simply aren't going to have what a console game player sees and experiences, let alone the gaming environment available to a PC owner with a real gaming GPU in it from AMD or nVIDIA. 

Gorath

#11
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
We're going to keep on seeing this error as unwitting buyers trade off usable desktop PCs for marginal laptops with tinker toy video chips instead of real video cards from real 3D game-conscious companies.

#12
jahuda

jahuda
  • Members
  • 8 messages
SOLUTION HEREIN (worked for me, anyway)

the problem lies in the fact that Intel's driver update in September caused this game to malfunction, so people need to use an older version of the driver.

user bnomad solved this issue. here is a link to his original post. http://social.biowar...25025/1#8920171

this is what he wrote

"I just wanted to post here so that people know I found the solution to this problem.
If your PC is running a Intel HD 3000 graphics driver, when you try to open the menu it will result in a crash and will bring you back to windows. There is however a solution that dose not require you to go out and by a new PC. the solution is to use the older .2361 drivers.
you can download this from
http://www.wikidrive...MA_15.22.1.2361
once you install that the game will function beautifully. you can hit escape all day long and you won't crash to desktop
Thanks again everyone. See you around."

Modifié par jahuda, 20 janvier 2012 - 05:12 .


#13
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages

Gorath Alpha wrote...

To be absolutely clear. This subject matter is one that can too easily go astray. I have been building my own computers almost as long as I have been enjoying CRPG game playing. That's gettng close to thirty years for both. Personally, I already feel that the type of game I prefer most has been watered down and mixed with lesser types until it's hardly recognizable. I feel "protective" of what little is left of the games I prefer to enjoy.

Intel does not care about me or my games. They don't care about any game players, or they wouldn't have kept making a 1995 level video chip until 2000, and a 1998 level chip until 2005, a 2002 chip until 2008, and now a 2006 level chip since 2009. Bioware designed their game to run a particular way, to look the way they wanted, and to flow as smoothly as they intended. They named the hardware that would do that. They did not name anything from Intel for video as adequate.

They offer no support for Intel's CRAP. Because it is crap. I don't want them to support such terrible hardware. I don't want to encourage anyone anywhere to consider anything that Intel does with video (now) to be acceptable. I suspect that eventualy, Intel will be shoving some 2008 level video out the door, in 2013, perhaps. I consider the idea of arguing in favor of Intel's trash to be ludicrous.

This is not a proper place for people with limited expectations to try to tell me I am wrong. I consider it off topic in a way, because it's more about philosophy than about gaming. The only CORRECT answer will ALWAYS be "get the right card for the job".


QFT

The only CORRECT answer will ALWAYS be "get the right card for the job".

#14
jahuda

jahuda
  • Members
  • 8 messages
Gorath Alpha - first of all, sorry about those repeat posts last night.  I just wanted to make sure that the solution to the problem I have had for months was posted on the threads that needed it.

I am not trying to tell you you're wrong.  I don't know much about computers, and I believe you when you say that Intel is crap.  Same for bogsnot1 who, by the way, was overall helpful towards me and tried to help me with my problem.

I take issue, good sir, with the flow of information.  If there is a solution to this specific problem, people should be aware of it.  If you're not able to provide that information, people will look elsewhere on the Internet for a better resource.  Then, suddenly, this forum is not a democratic forum of the people, it is your forum driven by your opinions with information that only you see fit.  You literally said that even if there is a solution to this problem, you would not provide because the correct answer is to "get another graphics card" or whatever.  But that's wrong, that's not the only answer, and now this entire forum is suffering because of your opinions.

It's really that simple.  If you know that there is a solution out there but don't say it, or if you beat a thread into the ground so much with your 'philosophy' that the solution is buried, or if you constantly reiterate that the only answer is "get a better computer" when that is NOT the only answer, then you are attempting to censor information.  You are doing this because you have a certain opinion about how games should be played.

I understand providing information on how it can be dangerous for that person's computer.  Bogsnot1 did this - something about overheating - and I thought that information was helpful.  I'm sure you have valid opinions too.

The rest of the debate is mute to me.  I COULD tell you that it's not fair to assume people can afford a gaming PC, but they still have a right to play video games.  I COULD tell you that there are advantages to playing games on a Mac laptop running Intel chips, such as owning and using a flipping Mac.  I COULD question why you think that people playing games on Intel chips somehow devalues your experience.  I COULD ask you why you think your infallable opinions preclude debate ("this topic is not up for debate").  Most importantly, I COULD point out that people have the right to make their own decisions about how they choose to play games.

But I won't do any of these things because I doubt I would change your mind.

I want to reiterate my original point.  If there is a solution to a problem, it should be stated for the sake of information.  You have no right to censor that because of your opinons.  You're nont obligated to provide solutions, but please don't get in the way of others.

Modifié par jahuda, 20 janvier 2012 - 02:38 .


#15
Skumov

Skumov
  • Members
  • 1 messages
Hi guys, i have same problem with igdumd32.dll file, here's my report

Problem signature:
Problem Event Name: APPCRASH
Application Name: MassEffect3.exe
Application Version: 1.0.5427.1
Application Timestamp: 4f28564a
Fault Module Name: igdumd32.dll
Fault Module Version: 8.15.10.2476
Fault Module Timestamp: 4e415161
Exception Code: c0000005
Exception Offset: 0005c560
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1026
Additional Information 1: d7df
Additional Information 2: d7df6762e2195a0183d3ea64a93fc6ac
Additional Information 3: 2ada
Additional Information 4: 2ada5396279475b612904a240f76bb6e

My system is: Intel Core i5-2430M, 6GB Ram, 1GB ATI AMD Radeon HD 6470 / Intel HD 3000 (Switchable Graphics)

When i play the game there's no problems before going to Mars mission.. when i get inside the Mars base starts crashing randomly with this report, can anyone help me with this?! As i understand this file is from Intel graphics, but i use high performance graphics (HD 6470) instead of lower performance Intel card... HELP PLEASE!