Random Freezes with 1.2

[SpannerB]

Hi All,

I still get the random freezes with Grid 1.2. However, things are slightly different this time. The game will freeze, then drops back to desktop saying Grid has stopped responding. However, the nVidia driver logs a message saying it successfully restarted - it does this 3 times, then BSOD (mentioning the nvidia driver nv(something).sys)

After a reboot and a quick look through event logs and msinfo32 - it doesn't look like it's grid that is crashing anymore. Its the nVidia driver.

In contrast, using version 1.1 the event log was full of errors from Grid after the freezes.

Im using nVidia 175.19 (the lastest drivers available for download for the 8800 GTS). Im going to try the .inf fix to allow more recent drivers to be installed and see if it makes a difference.

In the meantime, I have logged a bug report with nVidia.

[Purple44]

I'm using the 177.35 drivers for Vista 64-bit and there working good for me and gave me 8 FPS boost over the 169.25 drivers on the San Fransisco track.

But did have to do the modified inf for install to work with my older 8800 GTS.

[BEERPower12]

Update OS and all Drivers and Directx also and try this.
http://community.codemasters.com/forum/showthread.php?t=295040

[SpannerB]

BEERPower12 - stop just posting the same thing over again. Its annoying. Maybe I should have posted links to my previous posts, but the game is running on a completely clean and updated system install with GRID being the only installed application.

There were no issues with the Codemasters 1.2 patch install - it put everything in the correct directory and I am not suffering from any of the issues listed in your own post.

Also, even if the patch did install directly in the Windows directory, people would not have to reinstall windows, the patch doesn't overwrite any system files.

[SpannerB]

Using the 177.41 drivers now. It doesn't solve the problem, and infact points the finger back at GRID.

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 0x00776900, process id 0xe4c, application start time 0x01c8e4bfaa67c553.

Crashes back to desktop - the display driver sometimes restarts (up to 3 times), sometimes its just fine. But GRID logs an error.

Back to the drawing board...

[zBobG]

The 0xc0000005 error is most often caused by faulty hardware rather than program code. Since most people running GRID do not have that error frequently occurring I would not suspect that the GRID code itself is causing the error.

The 0xc0000005 error is a bad (out of range) memory address being detected. This is commonly caused by too overclocked hardware or overheating although it can be caused by borked OS support files. The main memory chips could be failing, test them with a long run of the memtest program that is appropriate for your OS (memtest.org or memtest86.com).

Usually, you can only suspect that the error is caused by bad code if the 0xc0000005 error repeatedly reports the same memory address (or within the same range of addresses) every time it fails.

The fact that an error report identifies a failure in the video driver can be just a coincidence. A graphics intensive program will spend much of its time in the video driver code, it's just more likely that that is where a hardware failure might occur.

[SpannerB]

Hi zBobG,

Thanks for the advice - I already suspected the memory (was having a few CRC errors installing from DVDs). However, I left memtest running for 3+ hours with 0 errors found.

Im on a completely clean install of Vista with nothing but GRID (no anti-virus, no other background apps).

I've got no other software to test on the machine currently - but before I reinstalled Vista, GRID was the only application I was getting 0xc0000005 errors with.

Nothing is overclocked, and I went through thermal checks with Codemasters, and all looks good.