Mildy OT: Success with IntelHD 3000 dual display Tweet

[larsmidnatt]

Finally it's all coming together! Woot! I just have to share my success with hardware.

I've only got one TI660, and dedicated display cards have not worked out for me in my computer. So if I wanted a display card my only option was to find a way to get the onboard intel to play nicely.

Basically no matter how you set up the bios or drivers, for some reason many people can not get their HD 3000 to run dual display and use the HDMI port. Many people can't get the HDMI to work at all.

But If you disable the card via the device manager, and then reenable it, it will work fine with two displays!

I found that workaround after searching online for a half hour.

So now I'm dancing around with dual display Daz Studio and Octane render with zippy UI updates and a big grin on my face. And I didn't have to spend a dime!

This trick has to be reapplied each time you reboot, but I can deal with that. Intel should fix it, known bug for what looks to be 2 years. But oh well. (and yep I have latest drivers)

[t_3]

great to know. even if the method to get this work is a bit a pain.

imo worth to note: standby does work pretty well with windows 7 - so it might be a way to avoid that procedure.

apart from that, have you tried to change the initialization order in the bios usually you can tell which gpu should be the main one (onboard or other); may this helps. a consequence could be, that you won't see startup screens until the moment windows initializes the drivers itself, but as long as the onboard graphics is not completely turned off everything should still work...

[larsmidnatt]

great to know. even if the method to get this work is a bit a pain.

imo worth to note: standby does work pretty well with windows 7 - so it might be a way to avoid that procedure.

apart from that, have you tried to change the initialization order in the bios usually you can tell which gpu should be the main one (onboard or other); may this helps. a consequence could be, that you won't see startup screens until the moment windows initializes the drivers itself, but as long as the onboard graphics is not completely turned off everything should still work...

Yeah I went through the no startups screen drama for a bit actually and couldn't tell if the onboard card was even enabled LOL. Might try tinkering again this weekend. Also I've looked into having a hotkey to do it, or maybe a script for boot up but haven't had the chance to try anything. I bookmarked a few threads I found talking about how to do that, but haven't attempted yet since they require me to read Much rendering to do ATM.

[t_3]

Yeah I went through the no startups screen drama for a bit actually and couldn't tell if the onboard card was even enabled LOL. Might try tinkering again this weekend. Also I've looked into having a hotkey to do it, or maybe a script for boot up but haven't had the chance to try anything. I bookmarked a few threads I found talking about how to do that, but haven't attempted yet since they require me to read Much rendering to do ATM.

there is a way to dis/enable hardware components by a rather simple script; used to do this to reset my nvidia cards after failures... have posted it somwhere... will search it and post again... remind me pls. if i forget to do so...

[p3taoctane]

there is a way to dis/enable hardware components by a rather simple script; used to do this to reset my nvidia cards after failures... have posted it somwhere... will search it and post again... remind me pls. if i forget to do so...

I am not sure if you are talking about a problem I have been having for months. I keep getting nVidia display errors where GPU's cut out.
I've tried everything, changed the registry settings, lowered power consumption and GPU speed etc... but they still drop out.

With the stand alone it is fine it just keeps going with whatever GPU's did not drop out... but it tends to kill plug ins.

Does your script address this or something else.

Thanks

Peter

[t_3]

With the stand alone it is fine it just keeps going with whatever GPU's did not drop out... but it tends to kill plug ins.

Does your script address this or something else.

Thanks
Peter

depends on; i have used it for the standalone, to recover from failing gpu's without having to restart. even if it can be done from the hardware management it's of course faster, and if you need to restart your main (display) gpu, you might be lost without, since drivers have no restart option in the manager - just stop and run.

it's a .cmd one-liner + a small tool needed... post found: viewtopic.php?f=9&t=10541

[p3taoctane]

Thanks for the extra info.

[larsmidnatt]

Finally got this to work. I had seen a tutorial on devcon and this confirmed that was the way to go. Restarting doesn't work for me though, I do an disable then enable command. I set up a bat file that I can run after startup. I need to run as an admin, so I haven't been able to get it to run at startup by itself, but I can deal with it. Only takes a second.

thanks.