Grid still not working. [Archive]

PabloBruno

12-07-2008, 01:53 AM

Okay - just tried Patch 1.2 - got bsod. Here goes...

Dxdiag:
http://rapidshare.com/files/129015321/DxDiag.txt.html

Rough spec:
Q6600 @ 3.0Ghz
Geforce 9800 GX2
4Gb ram
X-fi extreme audio
Water cooled

Updated all drivers. Tried game at all resolutions and graphical settings. Used Grid launcher. Patched to 1.2. Run as admin. I use HWmonitor and the temps are fine. Even tried uninstalling everything and then reinstall to patch 1.2.

However, the game, sometimes after 2 minutes, sometimes after 10 mins crashes to desktop. ALWAYS.

Examples of error codes:
Faulting application GRID.exe, version 1.1.0.0, time stamp 0x484d667e, faulting module GRID.exe, version 1.1.0.0, time stamp 0x484d667e, exception code
0xc0000005, fault offset 0x006a5c98, process id 0x190c, application start time 0x01c8dc404a0d6704.

Faulting application GRID.exe, version 1.1.0.0, time stamp 0x484d667e, faulting module GRID.exe, version 1.1.0.0, time stamp 0x484d667e, exception code
0xc0000005, fault offset 0x003612b9, process id 0x97c, application start time 0x01c8db9130be2aa2.

Faulting application GRID.exe, version 1.1.0.0, time stamp 0x484d667e, faulting module GRID.exe, version 1.1.0.0, time stamp 0x484d667e, exception code
0xc0000005, fault offset 0x006027a1, process id 0x19f8, application start time 0x01c8daff98412f22.

CM asked me (via custservice@codemasters.com) to disable my onboard realtek soundcard and uncheck everything from my startup programmes (via msconfig). I did all of that and I kept getting the same crashes.

Their last communication with me was on July 4th when they asked me to open the game using 'safe mode'. I replied back stating that there is no such option in my Windows start menu. I was led to believe this was only available for XP. I am running Vista Home Premium 32bit (which they should have known).

Now I have installed patch 1.2 and I got the Blue Screen of Death after 8 minutes of play (le mans circuit). I didn't get a look at the error code and it hasn't appeared in 'event viewer' so I cannot give you any of the details.

I have just uninstalled the game and started from scratch and then patched to 1.2 (not even using my old profile) but only got halfway through the first race before yet another crash to desktop.

As stated before I can run Crysis with AA, CoD 4, Assassin's Creed, etc, on my native res of 1680x1050 and all at Ultra settings with excellent fps and no crashes. I have built my own PCs before and I know my way around them pretty well. I believe I have tried everything. Now that this patch has not worked I really don't know what else to do.

Please advise.

(linked with other thread - http://community.codemasters.com/forum/showthread.php?t=294230)

PabloBruno

14-07-2008, 05:32 PM

No? No assistance or advice?

electronichead

14-07-2008, 07:05 PM

what is your memory speed, and the bus speed of your mainboard? If you have very fast timings, maybe you can try to lower their speed.

PabloBruno

14-07-2008, 09:16 PM

No idea - where do I look to find that info?

Devil Dave

14-07-2008, 11:55 PM

Hey folks,

I had a serious problem, so I thought! I was using the Demo of Grid, I had it for a week, worked like a champ! I loaded up anothe software program (a DivX codac) and GRID stopped working. I did everything to try to get it to work, with no hope. I even went and picked up the retail game, samething! Game installed perfectly. Go to launch the game, screen turned black with the GRID splash screen. No error no nothing, just sits there! I did a lot of frantic work. Come to find out, the DivX program did something to the OpenAL driver. I uninstalled OpenAL and downloaded OpenAL from there website, and Grid Worked like a champ! I am a happy camper now

I am using Vista Ult. 64 bit.

I just wished that GRID would make use of SLi!

You can download OpenAL from: http://www.openal.org/

Good Luck!

DD

SpannerB

15-07-2008, 08:07 PM

No? No assistance or advice?

Get your money back while you still can. Ive had the game for a month and can't return it now. Codemasters support have said they have run out of things to try and troubleshoot.

Ive asked them to refund me my money. I just want out now - Ive wasted enough of my life on this. Id suggest you get out before it consumes you!

All the best.

electronichead

15-07-2008, 09:17 PM

TheJedi

15-07-2008, 09:55 PM

Well, the OpenAL32.dll and wrap_oal.dll belong into the system directory (for XP 32 for example ..\Windows\System32).

If you look into ..\Program Files\OpenAL\ , you'll notice an oalinst.exe and an OalinstGridRelease.exe.

In fact, the OalinstGridRelease.exe (came with GRID) installs OpenAL32.dll and wrap_oal.dll with higher version numbers than the current installer from the Creative website. Seems to be new builds made to work with GRID.

jigglybean

16-07-2008, 05:46 AM

Two things to try -

Unplug your Logitech controller to see how you get on

Secondly, what power is your power supply?

PabloBruno

16-07-2008, 10:45 AM

Jiggly - I have Thermaltake 750W PSU - should be more than ample.

I have unplugged my controller and I am still experiencing the crashes.

MonkeyMike

17-07-2008, 02:00 PM

Before I changed GFX cards I was getting that with any Nvidia driver newer than 169.25 on Vista64 (Dec 07 release). I could go older OK, but they didn't perform as well as that release.
I don't know whether my card had started to become a little bit flaky or I just needed to do a clean Windows install to sort out potential legacy driver related issues, but as I upgraded to a GTX280 when they dropped the prices that problem's gone for me now...

PabloBruno

17-07-2008, 03:49 PM

Perhaps it is the nvidia driver but until I get some useful advice, CM bring out a 1.3 patch or nvidia a new driver for my 9800 GX2 then I am stumped.

electronichead

17-07-2008, 05:14 PM

Perhaps it is the nvidia driver but until I get some useful advice, CM bring out a 1.3 patch or nvidia a new driver for my 9800 GX2 then I am stumped.

that Nhancer tool for Nvidia cards, have you tried that already?

-FireBall-

18-07-2008, 01:35 AM

Try some of these drivers,

http://www.tweakforce.com/

electronichead

18-07-2008, 04:41 AM

and, as responded in another thread of yours, if you have 4 Gb of memory, please remove a stick and try again....it wouldn't surprise me it would fix your issue.

PabloBruno

18-07-2008, 06:26 PM

Cheers. Yes will have a go over the weekend and get back to you all. Never heard of Nhancer so will try that too.

I really do appreciate all the help but it still burns that I have spent over a month trying to get a game to work on a system that the game says fulfills the requirements and that has experienced no problems with every other modern game.

PabloBruno

24-07-2008, 03:55 PM

Tried taking out my ram and I still get the crashes. This is past a joke now. Any ideas? CM - any responses?

electronichead

24-07-2008, 04:33 PM

i m out of ideas for your situation, but have you read the audio sticky from yesterday? It seems especially the OpenAl sound driver is important

audio sticky (http://community.codemasters.com/forum/showthread.php?t=297651)

PabloBruno

25-07-2008, 06:13 PM

Thanks electronichead. Yep, I'm stumped too. Yes, I did read the sticky and yes, have all the updated drivers and the OpenAl one too. But same old same old.

zBobG

25-07-2008, 11:48 PM

One last thing to try.

CAUTION: Setting the memory volts too high can destroy the memory sticks.

Check what the recommended volts is for your memory sticks. That information can sometimes be found printed on the memory sticks, otherwise you need to check the memory manufacturers website. Check in your motherboard BIOS what volts is currently applied to the memory bank.

Standard memory volts applied in BIOS is 1.8 volts. It is common that 1Gb memory sticks require 2.1 volts. Most memory sticks that specify 2.1 volts will run at 1.8 volts but they will not be stable, especially in games.

To change the memory volts in BIOS change the power setting to manual then set the memory volts to +0.3 to change it from 1.8 to 2.1 volts. You might want to increase the volts by only a 0.1 volts increase at a time then test with memtest86 or Prime95. CAUTION: Some motherboards specify a 2.0 volts standard memory voltage.

DO NOT DO THIS if the memory does not specify that it requires 2.1 volts or specifies that it can run at a higher voltage. Some memory is designed for overclockers and will specify a minimum and maximum voltage. Increasing the memory voltage will increase the heat produced by the memory sticks, this can also lead to unstable memory and memory errors. Increasing the memory voltage above the specified maximum can reduce the useful lifetime of a memory stick and can (rarely) result in instant destruction of the memory sticks. It is ordinarily safe to increase the memory voltage in 0.1 volts steps followed by a thorough memory test to determine if the memory remains stable.

MORE INFO: Heat produced by the memory sticks, particularly during gaming, can cause memory errors. Adjusting the memory voltage will not fix this problem and can cause an even more unstable memory because the higher voltage will generate more heat. If the memory stick does not have a heat spreader or heatsink then these can be added to improve heat dispersion. A good case fan will also help to prevent overheated memory sticks.

PabloBruno

27-07-2008, 11:20 PM

I have never overclocked the memory and I think the power to them is correct. This info is all new to me so I will check it out and get back to you. Thanks for the post.

However, I have never had any other crashes with any other software or game (video editing, sound editing, Crysis, Assassin's Creed, CoD4, etc) and so have never really needed to think that it could be a hardware problem.

Don't really know (and feel comfortable with) changing the voltage to the memory as apart from Grid my system is faultless but will look into it.

PabloBruno

28-07-2008, 03:01 PM

Is there really no one at CM who will answer me?

jigglybean

28-07-2008, 03:04 PM

Can you please post a new full dxdiag

PabloBruno

29-07-2008, 12:07 PM

http://rapidshare.com/files/133306424/DxDiag.txt.html

And please don't tell me to update my sound drivers:
http://rapidshare.com/files/133306507/driver.jpg.html

I have - they are fine.

Also, I really don't know why I am posting a new dxdiag. The system is the same and I still have the same problems.

PabloBruno

04-08-2008, 02:14 PM

Jigglybean - almost a week now. You have my dxdiag which you requested. Any thoughts/ideas/solutions?

PabloBruno

06-08-2008, 04:41 PM

Over a week now. Anyone?

CM?

Jigglybean?

Bueller?

Anyone?

*goo

06-08-2008, 08:04 PM

Looks like he only wanted it to print off and fan himself during the good weather. Honestly, you've got to laugh. Otherwise you'd probably cry.

Joking aside, I sincerely hope you get it sorted. I've seen you on here virtually every other day trying to get your game working and sympathise with your predicament.

Codemasters support of their game, and ultimately you (their customer) has cemented the fact that I'm not going to reinvest in this game.

electronichead

06-08-2008, 09:38 PM

Over a week now. Anyone?

CM?

Jigglybean?

Bueller?

Anyone?

PB, i wonder, :

control panel > administrative tools > event viewer : any interesting errors to check?

jigglybean

06-08-2008, 09:50 PM

I would turn off your over clocked processor and see if that helps. I would place at a lower resolution as well to see if that helps. I would also look at background programs before starting GRID. Turn off what you dont need - turn off the Aero transparency with Vista as well.

There really isn't much else we can do :( - Out of ideas. Unless you are local to us in Leamington to drop your PC in for us to have a look.

PabloBruno

07-08-2008, 10:31 AM

Jiggly - I hope I don't sound annoyed but I am a little frustrated.

I have, in my previous posts, told you/everyone that I have reverted back to the default settings on my cpu (which is the only thing that is OC'd) and tried all resolutions with all settings on low and no AA. I still get the crashes. My processor is OC'd in the dxdiag but, as stated before, that is only because I have reverted it back to what is a stable set-up for me and allows me to play all of my other games and use all of my other applications seemlessly.

As for the background programmes, there aren't any. No msn messenger, no anti-virus, no IE7, nothing.

I'm not local to Leamington but I am sorely tempted to see if I can drop in at some point.

One final question then. If there are so many people here with pretty much the same problem as me (random crashes when their rig is more than able to run Grid) why is there nothing more you can do?

PabloBruno

07-08-2008, 10:33 AM

*goo - only the usual:

Faulting application GRID.exe, version 1.2.0.0, time stamp 0x4863839e, faulting module GRID.exe, version 1.2.0.0, time stamp 0x4863839e, exception code 0xc0000005, fault offset 0x006a0006, process id 0x1024, application start time 0x01c8f7e41ffc2bde.

Faulting application GRID.exe, version 1.2.0.0, time stamp 0x4863839e, faulting module GRID.exe, version 1.2.0.0, time stamp 0x4863839e, exception code 0xc0000005, fault offset 0x001e8e9a, process id 0xf1c, application start time 0x01c8f7cd73b9e99e.

Faulting application GRID.exe, version 1.2.0.0, time stamp 0x4863839e, faulting module GRID.exe, version 1.2.0.0, time stamp 0x4863839e, exception code 0xc0000005, fault offset 0x006a0006, process id 0x1b8, application start time 0x01c8f7cd3468227e.

etc, etc.

electronichead

07-08-2008, 04:43 PM

you know, maybe the Securom protection is causing it. It don't think it is wrong to go for their support.

http://www.securom.com/support.asp

PabloBruno

07-08-2008, 05:21 PM

Thanks electronichead. Have just mailed them with all the info.

Jiggly - any answer yet?

PabloBruno

07-08-2008, 06:29 PM

"Hello, Thank you for your e-mail.
After careful inspection of the analysis file and due to your error description, it appears that the issue is not SecuROMrelated. Please contact the software publisher for further support options related to issues specific to the software.
Best regards, SecuROM Support Team"

Another avenue bites the dust.

*goo

08-08-2008, 06:34 PM

electronichead

08-08-2008, 11:35 PM

I know it's a taboo subject, but have you tried backing up the original .exe then trying the no-dvd .exe?

At this point, you've got nothing to lose by trying. If it works, you could potentially then filter the problem down to the .exe itself.

ditto. The "support" from CM is failing in your case atm. Tho, i doubt if it makes a difference, since Securom claims they didn't cause your probs.

If you need to know where to d/l a no-dvd.exe, just PM.

PabloBruno

09-08-2008, 12:41 PM

Yes, I don't like to use no-cds but I have used one for 1.0, 1.1 and 1.2 and I still get the same crashes.

Thanks for responding though.

It wouldn't be so bad if I got swift responses from CM on here or from their customer support via email. I wait about a week each time and, I'm not joking, half the time they repeat themselves and suggest updating my drivers or changing the resolution.

Jiggly - any response?

zBobG

10-08-2008, 04:30 AM

My system:
e6600@3.2Ghz, 2Gb PC-8500@1068MHz, BFG 9800GTX-OC (stock clock=700/1100MHz), nv177.41 video driver @ 1680x1050, X-Fi Fatal1ty 2_18_0004 driver (Aug 08), XP SP3. My system is Prime95 stable! This is stated to rule out the possibility that there might be some random hardware problem or an overheating problem.

(Just installed the X-Fi 2_18_0004 driver, I think it is causing GRID to crash.)

For about the last week I've been having random crashes with GRID v1.2 (and v1.1). This seems to be a sound driver problem since I've randomly lost part of the sound or lost all of the sound shortly followed by a crash. GRID also seems to want to crash at the end of a race when the menu background music is loaded. In most cases I have had a graceful crash and have seen the 0xc000005 error in the logs but have not seen a sound driver file identified as the cause of the error. In one instance GRID crashed immediately upon starting with a DEP (data execution protection) error and BSOD, this is a serious Windows kernel error and required a power-off to restart Windows. Not so suprisingly the ha20x2k.sys driver was identified as the problem, it is the sound kernel driver.

In any case I had not had any GRID crash problems before I installed the latest X-Fi driver.

In addition, GRID no longer detects my X-Fi as capable of hardware acceleration. This is probably due to having the newest X-Fi driver installed and GRID no longer recognizes it as hardware capable. Very annoying!

I can conclude that the newest X-Fi sound driver (Aug 08) is not compatible with GRID. I haven't yet tested other installed games so I don't know whether the driver may be just a bad driver and not specifically a GRID problem. It's also possible that the OpenAL no longer works well with the newest X-Fi driver. GRID v1.1 however is not so likely to crash as the v1.2 patch but I have had the v1.1 crash with the same symptoms being a sound driver problem.

Current driver: 2_18_0004
Previous driver: 2_15_0006 (28 June 08) <--- seemed to work fine.
Older driver: installed 11 Jan 2007 <--- no evident problems noted for this driver.

@PabloBruno
Your soundcard, the X-Fi Audio, is in my opinion not a good soundcard (a POC) and very likely may be causing your crashing problems.

If you have an onboard sound chipset you might disable your soundcard and try the onboard sound to see if that makes a difference.

PabloBruno

10-08-2008, 04:46 PM

I can concure, my soundcard is a bit pants. I got it free from a chum who had never used it so I put it into my new build which only had onboard sound. I am looking to upgrade next payday.

However, I still fail to see why it works with every other game and application I have and yet is responsible for Grid crashing. CM themselves told me to disable my onboard soundcard and use the xtreme audio. Perhaps I will try it the other way around after your suggestion.

If it is the soundcard it should be able to fixed with a new patch for the game or a new driver from Creative - surely? The new X-Fi driver is unfortunately not compatible with the xtreme audio card.

I really do appreciate your response and I hope you get yours working soon.

Sandero

10-08-2008, 07:28 PM

There are multiple threads on this forum describing problems with X-Fi cards. Like this one that includes 2 potential solutions: http://community.codemasters.com/forum/showthread.php?t=299798

PabloBruno

11-08-2008, 08:53 AM

Thanks Sandero.

The trouble is my soundcard works fine and the in-game sound is perfect. However, some people think it might be what's causing the game to crash in my instance. The fact that it works fine makes me suspect otherwise.

Sandero

11-08-2008, 09:07 AM

I don't have an X-Fi card, but based on the others' input on this forum, it seems to lead to game crashes too, not just "no sound" problems. I think it may worth trying with those beta drivers, as Creative claims these drivers "Resolves issues of intermittent and random application/system crash when playing games or running applications that use EAX, DirectSound, OpenAL and/or ASIO features".

So even the card manufacturer admits that a sound card can cause crashes.

PabloBruno

11-08-2008, 05:28 PM

I have asked Creative and the new/beta drivers are no good with my card. All the other X-Fi cards - Yes. Mine - no. And they still claim the xtreme audio is a real X-Fi card?

I really want to play this game but my soundcard works perfectly for everything else. So, having to waste £30 on Grid which doesn't work and then to fork out another £80 on a decent soundcard makes it a little hard to swallow.

I appreciate your responses though.

norebert

11-08-2008, 08:07 PM

Maybe a PATCH THAT WORKS

--------------------------------------------------------------------------------

Since patching to 1.2 i have started a new profile
1st race SanFran at completion and past the replay next screen hit continue and i get a grid has stopped working message each and every time
if i reinstall and run with 1.1 patch i can play with my teammate far down the game or start a new profile and get further than the first race
whats going on ???????????????????????????????????????

iam using the latest nvidia driver (and get same results with the previous 2 drivers)

Vista 32 2 gb ram ddr2 8800 gtx 756 meg ram onboard intel 6600 chip sata drives no other problems at all in any game recent or otherwise i thought patching to 1.2 would help with my driving force pro which is good (was good) except for a bit of a shake down the straights

What is going on with this patch????????????????????????????????????????????? ????????

electronichead

12-08-2008, 04:09 PM

What pops up in my mind now, cause you are also running Vista : ever heard of DEP (Data Execution Prevention) ? DEP can be a pain-in-the-ass, and recently someone wrote me (i had trouble with a game to run) it depends on your CPU how stable DEP is. DEP can be found by control panel>system>advanced system settings> advanced tab> Performance > settings > D.E.P. > select "turn on DEP except....." > add Grid.exe to the list. I guess Grid is the only .exe the game is running?

Maybe worth a try, if you haven't done it already.

From my experience i sometimes get a DEP message with certain programs/games, but not ALWAYS. DEP can also stop your running game/software for whatever mysterious reason.

and about hardware acceleration in Vista : never found that either. With XP you could change it with dxdiag, but in Vista there are no sliders available.

PabloBruno

13-08-2008, 11:25 AM

Sorry electronichead... tried it... didn't work.

Still really pleased people are pitching in though as CM are either on holiday or have completely given up.

CM/Jiggly - if you are listening... I did put one last question to you which you seem to have ignored. I shall repeat it - pasted from my post one week ago - this thread:

If there are so many people here with pretty much the same problem as me (random crashes when their rig is more than able to run Grid) why is there nothing more you can do?

*goo

13-08-2008, 08:58 PM

PabloBruno,

I genuinely applaud your sincere commitment to Codemasters and their game. It certainly appears to me though, that it may be time you consider giving up on Grid, because Codemasters have given up on you.

Hopefully, your efforts will at the very least illustrate to all the customers who read this board the level of commitment and quality that can be expected from Codemasters.

I wish you luck in solving Grids problem.

PabloBruno

15-08-2008, 03:59 PM

Maybe *goo, maybe.

CM - is there anything you can do to persuade me that you actually give a toss about me/your customers?

Look at all the problems here from people who know what they are doing and have been through all the troubleshooting 'tips' and still their game does not work.

PabloBruno

19-08-2008, 03:59 PM

CM - please answer my question. Haven't heard from you in almost two weeks now.

Some further info...

Now, whenever I have the outrageous good fortune to actually complete a race without crashing it crashes after the 'replay' with this error code:

Problem Event Name: APPCRASH
Application Name: GRID.exe
Application Version: 1.2.0.0
Application Timestamp: 00000000
Fault Module Name: StackHash_fd00
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: aa1ed5fa
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

This happens if I complete any race and sometimes as a 'Drift' game is loading. I do, however, seem to be able to play and complete 'Driver Offer' games (when it doesn't crash).

This is still on top of the existing crashing problems I am experiencing.

Please CM, please respond.

KartAce

19-08-2008, 05:32 PM

Most other people on the 'net who seem to be having that StackHash_fd00 error indicate that it happens when connecting to the internet. I wonder if it's crashing when it's trying to upload lap times etc?

I know it's not a long term fix but try it with your internet connection disconnected.

PabloBruno

20-08-2008, 12:29 PM

From CM via email:

"If you are still gettting regular crashes, then this does indicate a hardware problem with your PC unfortunately."

So that's it. Despite the hundreds of people on here with problems, despite all evidence to the contrary they have given up any support and are determined to blame user's hardware.

I'm done. Unless I hear anything back or find some magic cure-all fix then I suppose this thread, and my other ( http://community.codemasters.com/forum/showthread.php?t=294230&page=1&pp=10 ) are now closed.

Thanks to everyone who tried to help. I appreciate it.

*goo

20-08-2008, 03:42 PM

Regular crashes could indicate a serious problem with the software as well.

Their response is a complete cop-out. But, what do they care? they've already got your money.

At least you can use your experience to reflect on the quality of Codemasters games and support in the future. I know I will.

If I were you, I'd also consider contacting online games reviewers and popular gaming magazines about the difficulty you've had.

Brand X

20-08-2008, 11:32 PM

Pablo,

I have been having problems with Grid with all patches so far. My problem was that after I finished the rookie race in Grid World, my game would crash to desktop with a grid.exe error popup.

This was occuring with all patches, all no-dvd.exe patches, using DVD, updating sound card and videocard and even upgrading to SP3.

It was really ****ing me off because Dirt worked perfect on my computer no crashes or anything. Got the game to 100% completion without any crashes.

This is what I have done which now lets me play Grid with no crashes...thus far.

First install the 1.2 patch then download 1.1 no-dvd.exe NOT the 1.2.

Try it out and tell me if it works.

PabloBruno

21-08-2008, 11:22 AM

Brand X - tried it (as per other thread) and it doesn't work. But thank you.

*goo - I can only agree. In the other thread (and others) Brand X states that his Grid crashed until he used the 1.1 cracked exe with the 1.2 patch and now it works well. This is proof that his hardware wasn't at fault and that it IS a software issue.

If people are using no-cd exes just so they can get the game to run then it's a software problem which CM should be fixing themselves.

*goo

21-08-2008, 08:38 PM

Even if you update the game to 1.2 but then revert to a previous .exe, doesn't that mean the game is running in 1.1? I'm fairly certain it does.

Not so bad if you are playing single player (if it works!) but not good at all if you are a multiplayer racer.

zBobG

21-08-2008, 10:43 PM

The version of the GRID.exe executable is what determines the version of the game that you are running.

The GRID v1.2 or v1.1 patch does install some changes to other files particularly changes to the tracks and changes to some graphics files.

The GRID.exe v1.0 or v1.1 can be used to run the game after applying the v1.2 patch to get the advantage of those changes but the reported version will be whatever version of the GRID.exe that you are running.

The (current) GRID v1.2 no-DVD replacement executable is known to be bugged both online and offline, it should probably not be used by anyone.

The GRID v1.1 no-DVD replacement executable seems to work OK but you can't play online with the v1.2 players.

If the official GRID v1.2 works for you then that is what you should run. There is an official substitute v1.2 GRID.exe executable available from the SecuRom support website that MAY be more stable for some users but it must be requested from the SecuRom website.

*goo

05-09-2008, 04:49 PM

Not been on this forum in a few weeks, but it's nice to see Codemasters still think ignorance is bliss.

CM, you should be disgusted with yourselves. This guy has been at you for months and you've failed in every respect possible.

Yep, I know most of my posts in this thread are negative. It infuriates me to see a company treat a paying customer with such utter contempt.

PabloBruno

08-09-2008, 12:26 PM

Yup.

If you read my other thread it has become even more ludicrous. They won't tell me how to get a refund, they won't admit it is a software issue, they wait over two weeks to respond and when they do they ignore all my questions and ask for yet another dxdiag (despite them having at least 6 of mine that I have sent previously).

If they even bother to read this forum here goes one last time:

1 - As there are so many people on here with similar problems to mine surely a new patch is warranted. When is it coming out?

2 - If you really think that my problem is hardware related, despite everything pointing to software issues, can you tell me how to get a refund as 'Game' (where Grid was purchsed) do not provide refunds on PC games?

3 - Why does it take you over two weeks to respond?

4 - Why will you not answer my questions, despite me providing all the correct information, and merely repeatedly request dxdiags from me and then ignore them?

Kind regards

WhiteSnake

08-09-2008, 12:54 PM

Got this game wen it came out and still unable to play it with out isues.

I gave up a while ago on playing this game, both me and a friend got exactly the same isues with this game and both patches did not even address or change these isues.

The only thing that they did change was the problem with the GRID.exe remaining active in the Taskmanager after closing the game, but now the game simply does not close anymore at all and hangs on trying to exit.

Good job guys, i wont be buying Feul after all this, thats for sure.

Purple44

08-09-2008, 11:32 PM

WhiteSnake, I see you have AMD duo core, have you run AMD_Dual-Core_Optimizer program?

Problem resolved with Amd x2 and ATI 1950 XT (http://community.codemasters.com/forum/showthread.php?p=4304980&posted=1#post4304980 )

Also see you have SLI, are you running SLI mode when trying to run GRID. Under Vista for me, SLI mode lock up GRID when I get to the first menu. So I run in single card mode.

PabloBruno

13-09-2008, 04:07 PM

Any response Codemasters? I have been waiting WEEKS.

PabloBruno

16-09-2008, 03:56 PM

Your silence is both unprofessional and the antithesis of your claim of 'support'.

You have refused to respond to both my entries on here and my emails.

Whereas in the past I was curious as to where I stand legally I am now actively seeking legal advice. I have been a loyal customer of yours for nigh on ten years. This will be the last CM product I buy and I will make sure my friends in the community are fully aware of your failings. I am sorry that it has come to this. To be honest, I am mainly sorry as you will probably never read this and the hundreds in here with similar problems will also be ignored. I'm not after compensation - I just want my money back for a game that doesn't work.

Si_Dez

21-09-2008, 04:10 PM

@ whitesnake (& hopefully others):
Mine wouldn't start, even with the patch. Would give the busy mouse cursor then nothing happened. Task manager would show that it was open but it wasn't doing anything and couldn't be closed, preventing reboots. Both codemasters suggestions worked in conjunction. Trying to get to the root of which prog is causing the clash. So far i've worked out it's not any of my user startups...

Codemasters suggestions:
"alter the properties of the GRID application shortcut & add the argument –novirtual to the end of the “Target:” box. Eg:
"C:\Program Files\Codemasters\GRID\GRID.exe" -novirtual

Windows Vista users may also need to run the game in Windows XP compatibility mode and choose the "Run as Administrator" option by modifying the shortcut for the game.

THEN:
a) Click on the Windows Start button and select 'Run'. In the 'open' box enter "msconfig" (without the speech marks). For Windows Vista, just enter the text in the search box.
b) In the general tab click on 'selective startup'
c) Now click on the startup tab (the last tab at the top of the msconfig screen) and UNtick everything EXCEPT 'systray' and 'scanregistry' (if they appear. If they do not, don’t worry).
d) Now close msconfig, you will be prompted to re-start your PC. Select 'Restart'
e) When the PC has re-booted, you will see a box with System Configuration Utility as its title. Tick the checkbox and then click on OK.
f) Now try the game again.

Best of luck all. The game's wicked once it works!