DiRT Rally 2.0

DiRT Rally 2.0

View Stats:
oPlayer1 Feb 13, 2020 @ 1:04am
access violation help
Access violation at address 0x7cb276c7 in module 'dirtrally2.exe' + 0x8a76c7.
dirtrally2.exe

anyone outhere has solved this prob?

i have r7 37x 2080 ti 32gb 3600
< >
Showing 1-15 of 15 comments
Axe Feb 13, 2020 @ 1:51am 
No one on here has ever had an error. You are the very first.
Lorelei Feb 13, 2020 @ 7:02am 
Well. I have that occasionally too, last week my AI weekly kept crashing my game with that error, same with my sister. And this week my friend got it while watching events. Sooo.
Eagleizer Feb 14, 2020 @ 7:24am 
Originally posted by Post-nut Clarity:
Access violation at address 0x7cb276c7 in module 'dirtrally2.exe' + 0x8a76c7.
dirtrally2.exe

anyone outhere has solved this prob?

i have r7 37x 2080 ti 32gb 3600

If this happens regularly:

This is usually solved by lowering your clocks. Parts of this game have code that tries to fry
your GPU. Although my GPU is rock stable in 3DMark and other tests, this game have some
really bad code that will make it hot and crash.

Here is what I do to test stability:
After finishing a stage, go to "Restart". Wait in the Yes/No screen for a few minutes to
check if your game is stable (somewhat). If your game does not crash here, you should
only occasionally get the "Access violation"-message.

You can also lock your fans to a higher speed instead of auto if you need every Hz you can get.
(I have a profile in Afterburner that I use for DR2 where the fans are locked to 85%, works
noticeably better than having it on Auto). Or you can set a fan curve that takes the fans to
90-100% at 65C or so, or whatever fits best for your GPU. Set temp a bit low to make sure it
cool GPU before it's to late.

It's a bit hard to explain how to set your curves, but by studying the graphical temp logs in
Afterburner, you should find the "average" highest temp, and make sure your fan is already
spinning about 70% througout the game, without hitting bad code. That way it will react faster
to go to 90-100% when it hits the bad code.

My curve is set like this:

- Fan at 0% up to 50C (This makes sure they are always spinning when running the game
so it's not constantly going up and down between zero and next speed step.)
- Next step is at 40% at 57C
- Then 70% at 60C
- Last is 90% at 65C

If you find that the fan is going a lot up and down, you can add points to the curve to take
care of that, but usually it's best to have as few points as possible. Usually set the C to
a lower value so the fan starts spinning faster earlier.

At 100%, my fans are too loud, so it's better to lower the clock more if 90% is not enough
for me.

If curves are not your thing, you can just stick with lets say 70% if that works on most stages,
and if it crashes on some stages, just raise the fan speed to whatever you need for that stage.

It's a PITA, but over time you will learn what is the best combination of clocks and fan speed
to make the game stable on your system.

P.S.
Try not to stay too long in the same menu. If you pause the game, go to window mode and
make it as small as possible and click somewhere on the desktop to take focus away from
the game. (The Split Time screen seems to be safe for me).


Cheers :)
OCEAN MAN Jun 25, 2020 @ 9:36am 
I'm just posting here because i fixed an issue that a lot of players has :

My game runs at 5/10 fps on very low altought i have a good computer ( RTX 2070super, i7 cpu, 18Gb RAM, thrustmaster t150 wheel etc). You might even have this report when your game crash :
 "access violation at address 0x2e1cc875 in module 'dirtrally2.exe' + 0x8dc875. dirtrally2.exe"


I'll make it short for you because i know you are prob tired of trying a lot of solutions :


1) go behind your computer

2) unplug your screen and search for another hdmi port BEHIND YOUR GRAPHIC CARD, it might be hidden behind a plastic cover.

3) Now your motherboard recognise your main graphic device as your GPU and not your CPU, and the game should run smoothly.



i hope this helps, good luck
SaxonRaider Jun 26, 2020 @ 2:04pm 
This has just happened to me first time ever in this game 600+ hours. Did a huge windows 10 update yesterday, and new graphics drivers. then this happens. :steamsad:
Originally posted by Ac!d:
I'm just posting here because i fixed an issue that a lot of players has :

My game runs at 5/10 fps on very low altought i have a good computer ( RTX 2070super, i7 cpu, 18Gb RAM, thrustmaster t150 wheel etc). You might even have this report when your game crash :
 "access violation at address 0x2e1cc875 in module 'dirtrally2.exe' + 0x8dc875. dirtrally2.exe"


I'll make it short for you because i know you are prob tired of trying a lot of solutions :


1) go behind your computer

2) unplug your screen and search for another hdmi port BEHIND YOUR GRAPHIC CARD, it might be hidden behind a plastic cover.

3) Now your motherboard recognise your main graphic device as your GPU and not your CPU, and the game should run smoothly.



i hope this helps, good luck

I am playing on my laptop and getting this error "Access violation at address 0x13ee9527 in module 'dirtrally2.exe' + 0x8b9527.
dirtrally2.exe"

No way for me to unpluge the kable. My laptop has i7 7700 and gtx 1070. Game is unplayable for me now even though I had couple of hours before
CaptainNebulous Jul 6, 2020 @ 12:03pm 
Access Violations are usually caused by a block in your memory (either GPU memory or RAM) malfunctioning or becoming corrupt, then your computer blocks access to it to attempt to prevent damage..... however normally if you see this regularly it means there is either already damage or that you are pushing your hardware/temps too far or for too long, or both.

Typically laptops (even the so called "gaming" laptops, which really don't exist btw) are not designed with longevity in mind. The necessary cooling and safety to prevent damage would require more space than what you typically find in a laptop. For example the average life span of a "gaming" laptop is often times about 40% the average life span of a gaming desktop. Meanwhile, the typical shutoff for a GPU doesn't happen until somewhere around 92 degrees C.... but in reality it is unhealthy to run at anything over 83C for long periods of time... and particularly with laptops those gaming GPU's are known to hover between the 83 and 92 degree mark for long periods of time, due to lack of cooling (they only provide just enough cooling to not hit the shut off). You can get around this by specifically targeting gaming laptops that advertise a lot of cooling but really the ones that have enough cooling will also be heavier and bulkier than what most people want in a laptop.
Last edited by CaptainNebulous; Jul 6, 2020 @ 12:07pm
oPlayer1 Jul 6, 2020 @ 9:12pm 
Replaced my turned out broken 2080ti, finally didnt get any errors
Originally posted by CaptainNebulous:
Access Violations are usually caused by a block in your memory (either GPU memory or RAM) malfunctioning or becoming corrupt, then your computer blocks access to it to attempt to prevent damage..... however normally if you see this regularly it means there is either already damage or that you are pushing your hardware/temps too far or for too long, or both.

Typically laptops (even the so called "gaming" laptops, which really don't exist btw) are not designed with longevity in mind. The necessary cooling and safety to prevent damage would require more space than what you typically find in a laptop. For example the average life span of a "gaming" laptop is often times about 40% the average life span of a gaming desktop. Meanwhile, the typical shutoff for a GPU doesn't happen until somewhere around 92 degrees C.... but in reality it is unhealthy to run at anything over 83C for long periods of time... and particularly with laptops those gaming GPU's are known to hover between the 83 and 92 degree mark for long periods of time, due to lack of cooling (they only provide just enough cooling to not hit the shut off). You can get around this by specifically targeting gaming laptops that advertise a lot of cooling but really the ones that have enough cooling will also be heavier and bulkier than what most people want in a laptop.

temp are not over 80C, I have undervolted and put some cooling under my laptop, game crashes even when I jsut start a race. I don't have problems playing other games like PUBG where temps are getting higher.

I am reinstalling the gaming, I can remember that before some updates it was running smooth so maybe something broke it. Verification of files didn't solve the problem. I hope downloading the game again will help.
Fuzza Apr 7, 2021 @ 12:35pm 
this is happening for me now too, had 140 hours in now all of a sudden it only happens when i launch a certain stage, right now whenever i load up Spain it gives me a crash with the acess violation error but i can go fine on powys and stuff for example weird af games unplayable dirt 4 just wont work at all now either
oPlayer1 Apr 7, 2021 @ 1:36pm 
turns out, my video card was broken when this stopped happening
Rudolf Fischer May 4, 2021 @ 12:49pm 
Deinstall SteamVR and Colin 2.0 works.
Kinder Azazel Jul 21, 2024 @ 7:06pm 
Originally posted by Eagleizer:
Originally posted by Post-nut Clarity:
Access violation at address 0x7cb276c7 in module 'dirtrally2.exe' + 0x8a76c7.
dirtrally2.exe

anyone outhere has solved this prob?

i have r7 37x 2080 ti 32gb 3600

If this happens regularly:

This is usually solved by lowering your clocks. Parts of this game have code that tries to fry
your GPU. Although my GPU is rock stable in 3DMark and other tests, this game have some
really bad code that will make it hot and crash.

Here is what I do to test stability:
After finishing a stage, go to "Restart". Wait in the Yes/No screen for a few minutes to
check if your game is stable (somewhat). If your game does not crash here, you should
only occasionally get the "Access violation"-message.
.
.
.
P.S.
Try not to stay too long in the same menu. If you pause the game, go to window mode and
make it as small as possible and click somewhere on the desktop to take focus away from
the game. (The Split Time screen seems to be safe for me).


Cheers :)

Thanks Eagleizer, this helped me. I run my GPU slightly overclocked, nothing major, and it's stable for everything I play. Dirt Rally was crashing with "access violation" error but not during the stage driving, it was mostly on after stage while replay was going on the background. I changed the config to the stock clocks and power, haven't had any crashes since. Cheers bro.
Glitch Dec 27, 2024 @ 2:13pm 
Originally posted by Fuzza:
this is happening for me now too, had 140 hours in now all of a sudden it only happens when i launch a certain stage, right now whenever i load up Spain it gives me a crash with the acess violation error but i can go fine on powys and stuff for example weird af games unplayable dirt 4 just wont work at all now either

I have exactly 140 hours as well and this is the first time this problem has occurred. I tried to load up a Monte Carlo stage but the game ended up crashing. How did you fix this?
MacLayd Mar 8 @ 2:39pm 
It's because of vr, write it to the startup parameters -novr
< >
Showing 1-15 of 15 comments
Per page: 1530 50