current workaround (if no bugfix BIOS available):
use intel display driver 126.96.36.1992 (v15.2.6) dated 05/11/2007 or older
bugfix BIOS (yet only released for the following systems):
Dell Inspiron 1420 : Update BIOS to >= A09 (BIOS A09 here)
Dell Inspiron 1520 : Update BIOS to >= A09 (BIOS A09 here)
Dell Inspiron 1525 : Update BIOS to >= A09. Verify VBIOS >= 1566
Dell Inspiron 1720 : Update BIOS to >= A09 (BIOS A09 here)
Dell Latitude D530 : Update BIOS to >= A07 (BIOS A07 here)
Dell Latitude D630 : Update BIOS to >= A12 (BIOS A12 here)
Dell Latitude D830 : Update BIOS to >= A13 (BIOS A13 here)
Dell XPS M1330 : Update BIOS to >= A12 (BIOS A12 here)
Dell Vostro 1400 : Update BIOS to >= A09 (BIOS A09 here)
Dell OptiPlex 330 : Update BIOS to >= A05 (BIOS A05 here)
still waiting for fixes for at least these notebooks:
Dell Vostro 1500
I don't know whether these notebooks are affected as well, nor whether a BIOS update is being prepared:
Dell Vostro 1510, 1710, 1700
Dell Latitude ATG
List of notebooks NOT affected:
Dell Vostro 1310
I have sufficient reason to belive in some memory corruption bug with the X3100 drivers v15.8 + v15.7.3. I do not think it affects your hardware, but I have the problem. There is also the chance that my GM965 chip is faulty. In addition there is the chance that my bug is not related to the gfx drivers, but just emerges with those two particular gfx drivers and is caused by some other faulty driver or device.
I filed a bug report at intel, with the outcome that they haven't reproduced anything like that. Since I found people with bugs that sound very similar (see below), I want to raise awareness in this forum and help other people google it (if they encounter the same problem). I will updates this posting if I get more information or by some magic it's not the drivers fault.
My walkaround is to use the slightly outdated 188.8.131.523 of the GM965 gfx drivers. It does not show up in this version.
I've got a fancy Dell M1330 notebook with intel X3100 graphics integrated into the GM965 chipset. Dell ships this Core2Duo notebook with 184.108.40.2063 of the graphics driver version runnning Vista Business 32Bit @2GB memory. It runs perfectly except that sometimes it doesn't recognize HDMI attached video beamers and big monitors.
Thus I tried:
Both fix the external HDMI attached device bugs.
However I encounter a severe bug: Memory corruption!
Unfortunately it occurs very infrequent and my test setup to detect memory curruption in this case requires reading big files from harddrive in a loop and checking their md5sum. In general I have to read ~50 - 1000 GB of Data u ntil I encounter a single md5sum error.
The whole course of isolating this bug and accounting the gfx system is not that interesting here. Let me just mention that I threw all the memory tests (incl. the brand new GM965 supporting MemTest86+ V2.01), changed memory modules, CPU stre testing at every single P-State, Harddrive checking (incl. different drivers such as IASTOR.SYS 220.127.116.112, 18.104.22.1680, MSAHCI.SYS 6.0.6000.20765). I do not encounter these bugs running ubuntu 7.10 or Mac OS X 10.5.1 on the same hardware reading the same files. It took me every evening the last week and some nights to do a thorough test. The bug seems not to be file/harddrive related - just my testing setup is built this way, since it gives me an easy way to validate some of the main memory content.
I am extremely careful if it comes to making hardware or software responsible for a given bug and try to think of every possible inference.
Certainly while switching back and forth with the drivers above I did not change anything else, after having isolated the bug. At that point I tried to find evidence that I'm not the only person. And I found:
Posting #161 (X3100 on MacBook):
"Our assessment of the error is that a bug in the graphics driver code is causing memory corruption within the data used by WoW under some circumstances, leading to a crash."
This is written by a WoW/Blizzard employee. Well, but it's 3D and it's Mac OS X!
There is code sharing amoung different intel drivers (Linux, Windows, Mac OS X). But the same crash also occured using WINDOWS by means of Boot Camp on the same hardware! posting #182:
"heres my windows crash report on the same macbook"
Regarding 3D: I'm using Aero, but the errors occurs with Aero being enabled and disabled.