DXRenderer.dll error

VMFA117_Poko · March 30, 2009

I've been getting errors for a month now. My game CTD always after 10-20 minutes of playing. What's wrong? I had been getting atiumdag.dll errors before with every driver. Now after total format and loaded catalyst 8.5 that came on my gcards cd this appear:

Product
DCS

Problem
Stopped working

Date
2009-03-30 23:40

Status
Report Sent

Problem signature
Problem Event Name: APPCRASH
Application Name: DCS.exe
Application Version: 1.0.0.0
Application Timestamp: 48e5e527
Fault Module Name: DXRenderer.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 48d2a486
Exception Code: c0000005
Exception Offset: 00028730
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1045
Additional Information 1: 88cd
Additional Information 2: 8fb030ed1410b1537d2ff6ce494a5078
Additional Information 3: 58da
Additional Information 4: 3862586f234311f51aacbe16919d3f46

Extra information about the problem
Bucket ID: 1208225327

# -------------- 20090330-214015 --------------
D:\Games\Ka50\bin\stable\DXRenderer.dll
# C0000005 ACCESS_VIOLATION at 02E28730 01:00027730
#
# EAX = 00000001
# EBX = 00000000
# ECX = 0363B6E8
# EDX = 00000008
# ESI = 0EA04350
# EDI = 0363B6E8
# CS:EIP = 0023:02E28730
# SS:ESP = 002B:0017F4B4 EBP = 0017F4F0
# DS = 002B ES = 002B FS = 0053 GS = 002B
# Flags = 00010206
02E28730 0017F4F0 0001:00027730 D:\Games\Ka50\bin\stable\DXRenderer.dll ?DrawNormalLights@DXRenderer@Graphics@@AAEXPAPAVRenderObject@2@H@Z()+20
02E28730 0017F4F0 0001:00027730 D:\Games\Ka50\bin\stable\DXRenderer.dll ?DrawNormalLights@DXRenderer@Graphics@@AAEXPAPAVRenderObject@2@H@Z()+20
0EA042B8 0EA04350 0000:00000000

My spec:

e8500 @ standard 3,16GHz

GA-x48-DS5

2 x 2GB DDR2 1066 (@2,17V)

2 x ATI HD4850 in CF (Driver Packaging Version 8.501-080602a-065253C-ATI)

X-Fi Audio PCI

2 x 250GB HDD in intelRCH9 RAID0

600W PSU

VISTA Ultimate x64 SP1

UAC dissabled

also: x52, tir4pro, logitech g25

Does it mean my gcards are no good?

Edited March 30, 2009 by Poko24

Infiniti3d · March 30, 2009

Disable CF and install the latest DirectX end user runtime.

VMFA117_Poko · March 30, 2009

Disable CF and install the latest DirectX end user runtime.

Thanks, I'll check it and write down if it helped.

VMFA117_Poko · March 31, 2009

Unfortunately it didn't helped. I installed newest DirectX end-user runtime, i dissabled CrossFireX, even Catalyst A.I. and I got CTD after 15 minutes again but little different. I have enough of these ATI cards!!! Help me to not throw them throught a window. I'm on the edge of frustration! :mad:

Product
DCS

Problem
Stopped working

Date
2009-03-31 16:37

Status
Not Reported

Problem signature
Problem Event Name: APPCRASH
Application Name: DCS.exe
Application Version: 1.0.0.0
Application Timestamp: 48e5e527
Fault Module Name: d3d9.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a65d
Exception Code: c0000094
Exception Offset: 00008620
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1045
Additional Information 1: 88cd
Additional Information 2: 8fb030ed1410b1537d2ff6ce494a5078
Additional Information 3: 58da
Additional Information 4: 3862586f234311f51aacbe16919d3f46

# -------------- 20090331-143811 --------------
D:\Games\Ka50\bin\stable\MitkaGraphics.dll
# C0000005 ACCESS_VIOLATION at 13499EBA 01:00028EBA
#
# EAX = 00000000
# EBX = 13528838
# ECX = 00000009
# EDX = 13528848
# ESI = 0EF8F120
# EDI = 00000000
# CS:EIP = 0023:13499EBA
# SS:ESP = 002B:0017FBF8 EBP = 025C57A0
# DS = 002B ES = 002B FS = 0053 GS = 002B
# Flags = 00010246

# -------------- 20090331-143754 --------------
C:\Windows\system32\d3d9.dll
# C0000094 INT_DIVIDE_BY_ZERO at 72148620 01:00007620
#
# EAX = 0017F674
# EBX = 00000000
# ECX = 13B1A2AC
# EDX = 00000004
# ESI = 13B177A4
# EDI = 13B177A0
# CS:EIP = 0023:72148620
# SS:ESP = 002B:0017F644 EBP = 0017F680
# DS = 002B ES = 002B FS = 0053 GS = 002B
# Flags = 00010246
72148620 0017F680 0001:00007620 C:\Windows\system32\d3d9.dll
72148620 0017F680 0001:00007620 C:\Windows\system32\d3d9.dll
02E1B6D6 0524C3F0 0001:0001A6D6 D:\Games\Ka50\bin\stable\DXRenderer.dll ?DrawGeometry@DXMesh@Graphics@@UAEXPAVRenderObject@2@@Z()+186

My spec:

e8500 @ standard 3,16GHz

GA-x48-DS5

2 x 2GB DDR2 1066 (@2,17V)

2 x ATI HD4850 in CF (Driver Packaging Version 8.501-080602a-065253C-ATI)

X-Fi Audio PCI

2 x 250GB HDD in intelRCH9 RAID0

600W PSU

VISTA Ultimate x64 SP1 --> up to date

UAC dissabled

also: x52, tir4pro, logitech g25

Edited March 31, 2009 by Poko24

EtherealN · March 31, 2009

Have you tried the 8.13ish drivers? I've not much experience with ATI myself but that is a version number I vaguely remember a guy getting success on.

It would be very interesting to see what exactly it is ATI has done in the newer drivers that make things act up so much, but ah well. I suspect they won't let us know. :P

VMFA117_Poko · March 31, 2009

Have you tried the 8.13ish drivers? I've not much experience with ATI myself but that is a version number I vaguely remember a guy getting success on.

It would be very interesting to see what exactly it is ATI has done in the newer drivers that make things act up so much, but ah well. I suspect they won't let us know. :P

I rember there were 8.13 drivers but you won't find them on ati.amd.com anymore - at least not for Vista64. Last "downloadable" catalyst before 9.2 and 9.3 is 8.12. I'll try them again. Let's see what kind of error will appear... Thanks for helping EtherealN.

VMFA117_Poko · March 31, 2009

What do these errors mean? I still get CDT. Help! I'm not a rocket scientist to solve this problem. I made every combination I could. I feel this happens because of my crappy cards. This is first and the last time I bought ATI cards. I will never ever, ever, ever, ever... ever buy them again. NEVER! I swear! :mad:

2009-03-31 20:11
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 4651002
warning: no weapon sensor for host 161b1002
warning: no weapon sensor for host 161b1002
warning: no weapon sensor for host 15651002
warning: no weapon sensor for host 161b1002
warning: no weapon sensor for host 161b1002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 22651002
warning: no weapon sensor for host 251b1002
warning: no weapon sensor for host 251b1002
warning: no weapon sensor for host 251b1002
warning: no weapon sensor for host 251b1002
warning: no weapon sensor for host 251b1002
warning: no weapon sensor for host 251b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 28651002
warning: no weapon sensor for host 28651002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 28651002
warning: no weapon sensor for host 28651002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 291b1002
warning: no weapon sensor for host 391b1002

and

SoundManager: Starting...
SoundManager: DirectSoundEnumerate
DXMixer Primary Sound Driver : Starting...
DXMixer Primary Sound Driver : Start succeeded
DXMixer Speakers (SB X-Fi Xtreme Audio) : Starting...
DXMixer Speakers (SB X-Fi Xtreme Audio) : Start succeeded
DXMixer Digital Output Device (HDMI) (2- High Definition Audio Device) : Starting...
DXMixer Digital Output Device (HDMI) (2- High Definition Audio Device) : Start succeeded
DXMixer Digital Audio Interface (SB X-Fi Xtreme Audio) : Starting...
DXMixer Digital Audio Interface (SB X-Fi Xtreme Audio) : Start succeeded
DXMixer Digital Output Device (HDMI) (High Definition Audio Device) : Starting...
DXMixer Digital Output Device (HDMI) (High Definition Audio Device) : Start succeeded
SoundManager: DirectSoundCaptureEnumerate
DXCapturer Primary Sound Capture Driver : Starting...
DXCapturer Primary Sound Capture Driver : Start succeeded
DXCapturer Microphone (SB X-Fi Xtreme Audio) : Starting...
DXCapturer Microphone (SB X-Fi Xtreme Audio) : Start succeeded
DXCapturer S/PDIF-In (SB X-Fi Xtreme Audio) : Starting...
DXCapturer S/PDIF-In (SB X-Fi Xtreme Audio) : Start succeeded
DXCapturer Line-In (SB X-Fi Xtreme Audio) : Starting...
DXCapturer Line-In (SB X-Fi Xtreme Audio) : Start succeeded
SoundManager: Start succeeded
Sound Card Information:
100 Minimum sample rate specifications that are supported by this device's hardware secondary sound buffers.
200000 Maximum sample rate specifications that are supported by this device's hardware secondary sound buffers.
1 Number of buffers that can be mixed in hardware. This member can be less than the sum of dwMaxHwMixingStaticBuffers and dwMaxHwMixingStreamingBuffers. Resource tradeoffs frequently occur.
1 Maximum number of static buffers.
1 Maximum number of streaming sound buffers.
0 Number of unallocated buffers. On WDM drivers, this includes dwFreeHw3DAllBuffers.
0 Number of unallocated static buffers.
0 Number of unallocated streaming buffers.

0 Maximum number of 3-D buffers.
0 Maximum number of static 3-D buffers.
0 Maximum number of streaming 3-D buffers.
0 Number of unallocated 3-D buffers.
0 Number of unallocated static 3-D buffers.
0 Number of unallocated streaming 3-D buffers.
0 Size, in bytes, of the amount of memory on the sound card that stores static sound buffers.
0 Size, in bytes, of the free memory on the sound card.
0 Size, in bytes, of the largest contiguous block of free memory on the sound card.

Loading error: bleeper is zero - class wHumanHel
Creating error: bleeper is zero - WarningTone1
Creating error: bleeper is zero - A10_AutopilotEngage
Creating error: bleeper is zero - A10_StallWarnSteady
Creating error: bleeper is zero - A10_StallWarnChopped
Loading error: bleeper is zero - class wHumanHel
Loading error: bleeper is zero - class wHumanHel
Loading error: bleeper is zero - class wHumanHel
Loading error: bleeper is zero - class wHumanHel
ObjectSounder-Play() error: bleeper zero pointer - class wHumanHel
Unloading error: bleeper is zero - class wnHelicopter

What the heck is wrong?

Edited March 31, 2009 by Poko24

VMFA117_Poko · March 31, 2009

Tried 8.12 again - no luck. Tried with unplugged one card - no luck. Tried with switched to the other - no luck...

Every game crash after a while...

Ramstein · March 31, 2009

are you running any 3rd party software? :huh: Utilities for games or software?

VMFA117_Poko · March 31, 2009

No, i have no 3rd party software. Never overclocked anything. I have just reinstalled vista and installed only necessary drivers.

Infiniti3d · March 31, 2009

No, i have no 3rd party software. Never overclocked anything. I have just reinstalled vista and installed only necessary drivers.

Keep CF disabled and remove 2GB of ram and test agian, its definatly not your GFX cards becouse you have no screen corruption, and CF or non CF doesn't change anything. It might be you ram so try 2gb AND SET the ram to 2.2V

EtherealN · March 31, 2009

I feel it's a bit weird to recommend a voltage without knowing the model. Now 2.17v is a bit of a strange number, that I will grant, but if it's an 8500 kit with a recommended voltage of 2 (more of them out there than the ones with 2.2 from a quick survey I ran) then the issue could be that the voltage is too high, not that it's 0.03 below 2.2.

Before adjusting voltages I'd definitely recommend doublechecking what the recommendation is for the sticks.

EDIT: Poko, if you want to test out if there's a system instability in CPU or RAM that is causing the issue, check this program out: http://www.overclock.net/downloads/138142-orthos.html

I definitely recommend that you run temperature monitors while running it, and don't attempt to do anything else at the same time since it'll put an insane load on your computer. I used the program to stability-check my computer after overclocking, but even without overclocking it can be a good thing to check - for example if your power supply is having minor malfunctions to cause an unstable power supply to the components or just bad luck with a given component getting a semi-defective one. For a preliminary run, if you don't get any warnings or errors from the program after an hours run, you are probably safe. (For overclocked machines the recommendation really is at least a 12 hour run to be really sure, but that's not as necessary when you haven't tinkered with the system.) Unclean voltage can cause stuff to go on paths they shouldn't in the various chips and that can cause all kinds of funny errors.

As for the huge error log you had, I'm afraid I didn't quite understand what was happening in it either. :(

Edited March 31, 2009 by EtherealN

VMFA117_Poko · April 1, 2009

Thanks for your interest guys. My stickers on ram say it should be 2.2V ~ 2.4V. There are two GeIL PC2-8500 1066MHz EVO ONE 2GB (memory timing is 5-5-5-15). But default BIOS settings set the voltage much lower (1.7V) than recommended. When the problem had started i decided to rise the voltage gradualy. Two years old games play stable. I have the issue with only newest games.

Also my CPU temps are OK - never go above 70 degrees of Celsius but GPUs were always high (each above 80 degrees). My stickies on the GPU cooler case became unstack but I have no graphic corruption. I read somewhere it's quite normal for these cards (little weird). So I tried setting 75% - 85% of FAN speed in CCC (this option is available since catalyst 8.9 IIRC). Temps drop to 75 degress when bussy. No differences.

I'll try your prog EtherealN. Thanks for the link. Let's see if it's not my RAM then (I prefer to spend additional money on RAM than graphic card with nVidia GPU. I have crossfire motherborad - not SLI. So i should buy a strong nVidia one to not loose much of performance).

Edited April 1, 2009 by Poko24

Infiniti3d · April 1, 2009

I can tell you that DDR2 ram on 1066mhz needs at least 2.2V. You should test each module seperately and go beyond 2.2V. Also set the timings and speed (1066mhz) manualy, even when they show the recommended setting in BIOS. Running Orthos seems a bit radical btw but you can try and see if you trace the problem.

I see you dont have any overclocks applyed to your system so hours of testing with stress tools is not neccesary. Keep CF disabled while testing with one stick of ram and report back, we must find the problem

Edited April 1, 2009 by Infiniti3d

VMFA117_Poko · April 1, 2009

I can tell you that DDR2 ram on 1066mhz needs at least 2.2V. You should test each module seperately and go beyond 2.2V. Also set the timings and speed (1066mhz) manualy, even when they show the recommended setting in BIOS. Running Orthos seems a bit radical btw but you can try and see if you trace the problem.
I see you dont have any overclocks applyed to your system so hours of testing with stress tools is not neccesary. Keep CF disabled while testing with one stick of ram and report back, we must find the problem

:)

I'll try. And yes, I have everything set manualy in BIOS what relates to DDR2.

EtherealN · April 1, 2009

I can tell you that DDR2 ram on 1066mhz needs at least 2.2V.

[citation needed]

Only about 25% of PC-8500 sticks I checked were at 2.2V, most were at 2 and 2.1. Of course the recommendations can be erroneous but if you are saying that DDR2 at 1066MHz per definition requires 2.2v then I am really sceptical. My 6400 sticks run nicely at 1092MHz with "only" 2v of juice. It is entirely dependant on the sticks themselves what they need.

Also, poko, I would definitely recommend cranking up the cooling on that GPU if it is possible. It may be able to run at 80 degrees without corruption, but the higher temperatures will cause increased wear on the components, causing it to fail sooner. It's not anything that's likely to help you with your current problems, sadly, but it might help avoid future problems.

My own GPU I have running at about 45 degrees C even while overclocked, but sadly that was achieved through cranking up it's stupidly fast fan quite a bit, so it causes a bit of noice. But I personally don't really mind a buzzing sound - I get more worried when I can't hear it, causes me to wonder if the fan has failed and I'll soon have a barbeque inside the box. :D

Edited April 1, 2009 by EtherealN

Infiniti3d · April 1, 2009

Only about 25% of PC-8500 sticks I checked were at 2.2V, most were at 2 and 2.1. Of course the recommendations can be erroneous but if you are saying that DDR2 at 1066MHz per definition requires 2.2v then I am really sceptical. My 6400 sticks run nicely at 1092MHz with "only" 2v of juice. It is entirely dependant on the sticks themselves what they need.

I agree,

Unfortunately many mobo's undervolts the ram, in other words when you set 2.1V in Bios its in windows 2.0 or even less! Keep in mind Poko has high speed ram modules that are volt hungry. I mean i dont recommend something abnormal or stupid so lets try to help him instead of confuseing him,altough i see you point.

By testing the modules each seperate you can trace down a faulty stick, if the situation doesn't change he knows that its not the ram but something else.Also 2x2GB increases the load on the sytem bus. thats why i recommended to test with 1X2GB. Memory modules are easy to test, easyer than replacing a CPU or complete mobo. Post back with you finding Poko and we try to sort it out together with you! I sugest you remove one card while testing and put it back in when its solved. The problem doesn't look very serious its something small i think, do you face any problems when not playing games?

Edited April 1, 2009 by Infiniti3d

EtherealN · April 1, 2009

Yeah, but the point of Orthos and Prime95 is that it has specific modes for testing the RAM specifically.

A very good point about load on the system bus however.

VMFA117_Poko · April 1, 2009

Ok, I've made a test today with BS and GTR Evo for an hour each game (no time for more testing). I had no crash :). Don't want to be happy yet. Will try tomorrow again little longer.

What I did is:

Again dissabled CF and catalyst a.i., increased gpu fan speed to 85% (temps don't reach 80 degrees C now) as recommended by you guys. I left both sticks in slots but rised a voltage by one more click to 2.24V. I'm still on cat 8.12 now BTW. If tomorrow BS will CTD I'll try to unplug one stick then switch them (hope I won't have to). Does this one click could have such a meaning? Will see. Thanks for help.

I tried Orthos too for an hour but no problems found.

Edited April 1, 2009 by Poko24

EtherealN · April 1, 2009

Let's hope it's all found and fixed. :)

Infiniti3d · April 1, 2009

Thats very good news, hopefully it's solved.

Edit: You might check you BIOS version becouse there was an issue with the ICH9R RAID, wich is solved in the F7 release. If you have F5 wich is the release version you might Flash it to F7, you are running RAID. But first test ofcourse.

Edited April 1, 2009 by Infiniti3d

Slayer · April 2, 2009

Without rehashing an old thread:

Also might want to look at your joystick....This is a known issue of random crashing for X52/X52 pro users. Not everyone is affected by this but there are many people with this problem.

You need to rename or get rid of the file called lua-direct_output.dll in your C:\Eagle Dynamics\Ka-50\bin\stable (or whereer your game is installed) folder. I just renamed mine and added a 1 onto the end of it because this will be addressed in the patch.

http://forums.eagle.ru/showthread.php?t=34311&highlight=x52+crash

VMFA117_Poko · April 2, 2009

Thats very good news, hopefully it's solved.

Edit: You might check you BIOS version becouse there was an issue with the ICH9R RAID, wich is solved in the F7 release. If you have F5 wich is the release version you might Flash it to F7, you are running RAID. But first test ofcourse.

Yes, I know. I used GSATA when problems occured. When I was started to look for solution I flashed BIOS and set new RAID0 from the very beginning using Intel ICH9R.

Without rehashing an old thread:

Also might want to look at your joystick....This is a known issue of random crashing for X52/X52 pro users. Not everyone is affected by this but there are many people with this problem.

You need to rename or get rid of the file called lua-direct_output.dll in your C:\Eagle Dynamics\Ka-50\bin\stable (or whereer your game is installed) folder. I just renamed mine and added a 1 onto the end of it because this will be addressed in the patch.

http://forums.eagle.ru/showthread.php?t=34311&highlight=x52+crash

Thanks, I read this post but forgot about it.

VMFA117_Poko · April 6, 2009

I did tests for couple days, changing voltage on ram, testing with both sticks of ram, unplugging one stick, then changing them, testing with crossfire on and off, testing with catalyst a.i. on and off, switching between every possible driver, testing with only one card and with the other, both, flashing bios, testing on vista64, xp32, switching between SATAs ports, doing total format and installing fresh vista64, testing CPU with no problem found...

...and I still have atiumdag.dll, atikmdag.dll (most common) and other (dxrenderer.dll) errors with every new game. Most probably it's ATI issue. I start saving money for nVidia card and will never come back to Radeon. Decision made. Houk!

Why? Read about atiumdag.dll error on web, how many people have it. Only one solution you'll find - switching to 8.12 catalyst package. But it doesn't solve my problem. It is almost impossible to have both cards broken. ATI just can not make proper drivers and their CrossFireX technology is pointless.

Edited April 6, 2009 by Poko24

Ramstein · April 6, 2009

Poko24, do these problems happen with TrackIR in use? Do they happen without TrakIR in use?

Edited April 6, 2009 by Ramstein

Sign In

DXRenderer.dll error

Recommended Posts

VMFA117_Poko

Infiniti3d

VMFA117_Poko

VMFA117_Poko

EtherealN

VMFA117_Poko

VMFA117_Poko

VMFA117_Poko

Ramstein

VMFA117_Poko

Infiniti3d

EtherealN

VMFA117_Poko

Infiniti3d

VMFA117_Poko

EtherealN

Infiniti3d

EtherealN

VMFA117_Poko

EtherealN

Infiniti3d

Slayer

VMFA117_Poko

VMFA117_Poko

Ramstein

Recently Browsing 0 members