Hello folks,

After a fairly stable few days with DF 8.1 beta2 I added a third Display Port monitor yesterday to work on my multi-monitor not-firefox script and let the laptop go to sleep overnight. This morning the intel HD graphics driver had a complete meltdown and I had to do a hard reset since the laptop wouldn't display anything and just flashed as I suspect the driver was in a reset loop. It continued to do this when undocked.

When everything was up again I put the laptop to sleep (lid closed) then woke it up twice, all was well. After working on scripts all morning I locked the screens and went to lunch. On return the machine wouldn't wake up and BSOD'd on me with that stop code in the igfx driver stack.

This in itself brought on another problem which is a BIG failing with DF I think. When you're working on scripts it would appear to cache your changes temporarily despite what I thought was 'saving' scripts by OK-ing back to the Functions setup window to eg check another function or to tweak something. On reboot all this morning's work had gone and my list of scripts was back to yesterday.

I expect to be told the scripts are stored in a database and changes aren't committed until the Apply button is clicked, which is fine for settings but not OK for scripts.

Tonight I'll increase the log level for tomorrow's crash.

Cheers

Witchy

Morning Keith,

I think it's something to do with property sheets, yes. Before both crashes yesterday the script editing window was open and I'd been editing a lot. Last night I upped the log level to one, applied the change and locked the screens. This morning all was well.

I'll see if I can replicate it today.

Cheers

Witchy

Morning!

Last night I left the script editing window open and this morning, POW. BluescreenView shows it as a crash in dxgkrnl, dxgmms1 and igdkmd64 trying to reset the graphics driver.

I've attached the logfile. Crash would've been around 9:10am

Cheers

W

Yep, 4 crashes so far with the script editor open. If I leave just the settings window open it seems OK. Memory leak or buffer overflow? It certainly upsets directx

W

Seems like I spoke too soon, it's not property sheet related since I've had 2 crashes today after trying to unlock my desktop. I'll check for updated drivers for my laptop.

W

Hi Keith,

Yep, that's what I'm doing. There was a later driver (2014) for the graphics chip so I'm running on that one now, see how we get on. The actual Intel driver is from this year but it's not an official HP packaged one so I'll only install that if necessary.

This only started happening after I added the third monitor...

Cheers

Seems to be pretty stable now, and in the midst of all this DF updated itself to 8.1 which may also have helped.

I'll keep trying to crash it

cheers