If you read a little bit back you can see that some of us have also tested with the 2653 driver, in fact it has become our routine to always try the new driver.
Sometimes the problem is just gone for a week or so, which makes it hard to reproduce and appoint to a certain configuration.
While the 2653 is not the latest driver on the intel site (2622 is), I believe it was offered through Windows Update in my case.
Hey guys, i have same problem but with Mass Effect 3 game, here's my report:
Problem Event Name: APPCRASH
Application Name: MassEffect3.exe
Application Version: 1.0.5427.1
Application Timestamp: 4f28564a
Fault Module Name: igdumd32.dll
Fault Module Version: 184.108.40.2066
Fault Module Timestamp: 4e415161
Exception Code: c0000005
Exception Offset: 0005c560
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1026
Additional Information 1: d7df
Additional Information 2: d7df6762e2195a0183d3ea64a93fc6ac
Additional Information 3: 2ada
Additional Information 4: 2ada5396279475b612904a240f76bb6e
I never had problems like this before, the game crashes randomly, no matter what i do, i play 10-15 mins and then ...... boom!
After reading many forums i think the problem isn't from the game itself, its from the intel card (or driver).. Im running 64bit Win 7...
Very Interessting new Driver release including Video Bios:
Couldnt find the driver on the Intel HP or specific MB Release for DH61AG yet, so i couldnt test it.
Alternative DL from a German Side:
Please report your findings.
Yes, very interesting, I found a newer driver for my board (DH67CF) which is a few versions earlier (2656) and I'm testing with that one.
My boards also has a newer BIOS, which I still need to apply,
After that some testing will indeed reveal if this helped. and I will report back.
Hopefully the 2696 will release on the Intel download site soon.
I'm starting to become hopeful. After the installation of 2656 version pluse the new system bios for my board, I have not seen the error.
It has been absent for a little over a week now. Still a bit too early to call it solved, but "better" seems a valid judgement for what I'm seeing.
Will report back in about a week.