BLEND - possible resource drainage due to graphic acceleration

BLEND - possible resource drainage due to graphic acceleration by Head_Storms

Closed

as Deferred Help for as Deferred

Type:	Bug
ID:	731327
Opened:	3/15/2012 4:24:02 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I elected to make this a separate topic from the one below me pertaining to BLEND and WPF crash; which I had the same issues - not wanting to intrude, I found some odds and ends on top of everything:

Just a brief addendum to the above, mine too does crash (on stand alone version) on the designer; have found three things of interest (I am on the top three latest nVidia graphic card - runnig on 1980 x 1080 resolution @ 60 Hz x86 platform / 32 bit).

1) HDMI - Program tends to (if everyone could watch your core system; I am on a x4) - it will overclock quickly and fast; in spite of water cooling and so forth. I have yet to figure this one out yet; there is no reason for this since this is my primary native monitor.

2) HD - this is where I moved to the BETA mode until designer just crashed with the Fatal Exception Error, with blue screen of death - was unable to restart until I remembered I had my BIOS configured to restore at "Last State", had to turn that off; once returning back on - noticed the program was still running in SysInternals (Microsoft System Internals) in Task Manager in which was not appearing in Task Manager (Windows) *NOTE: Autoruns / Process Explorer does work in Win 8 *

3) Analog - ODD; if I turned the Hz down to 50, it will work but it degrades the program itself, however, I found out if you shut off Microsoft's Net (it works better but not what one would call "par excellent".

-----------------------------------

If no one had noticed; after completion of program, close it - you will see it is still running in the background which cause resource drainage. (BUG) I elected to put these in manual mode at this present stage.

-------------------------------------

Other things I found interesting:

1) Had difficutlies with VS 11

2) Did not do so well with VS 2010, unrecognized

3) VS 2008 - non-compliant

4) VS 2007 (very old version) actually recognized this and picked it up as long as it was under analog and in 50 Hz mode (?) I do not recomend anyone venturing into this avenue because it does require usage of another version of nVidia Graphic card (I have 3 differing versions installed, therefore I switch the cables - enabling me to work around and toy around. There is a lot of limitations as far as what one can do, a lot of degrading and functionality.

Details (expand)

Blend for Visual Studio 11 Beta

C++

Bug

Perceiving it might be "clash" between configurations of the graphic card (even more so if one is also a gamer or heavy into development) with the acceleration configuration (whether in BIOS and/or Settings configuration(s) itself).

Since the clocking (HUD for NVIDIA) does not work in WIN 8; Microsoft's System Internals does; had to wire and install a clocking device on the small Server where the Wn 8 is installed on to monitor the resources - especially with the graphics, it tends to "overclock" when this Program is in use insomuch I am currently making observations as to why. It does this on both NVIDIA graphic cards; worse on the latest edition than the few editions back; I am considering installing a few editions back onboard and replacing the newest NVIDIA card to see how VS 11 BLEND functions (also an HDMI, HD, Analog - see notes below).

(x86 platform, MSI Professional Series Mainboard, AMD Quad (x4) Pro Seroes. Dual nVidia Graphic Cards ** not operating at same time, only when cable is connected, the multi-SLI has been disconnected to prevent any damages **, Pro-Water Cooling Sys, et al)

Concerns here - possible bug in drainage of resources and possible burn out of graphic card for those unaware.

0 attachments

Workaround recommendation: In BIOS for those running on x86 platforms / 32 bit OS - if you have that option to control your DDR2, DDR3, DDR4 - I strongly recommend to turn it down during this BETA phase to prevent overlocking; if you have spectrum enabled - turning down high speed by 1 or 2 degrees may help. I have not reached a finalized conclusion yet; you cannot rely on the HUD or Shader Perfect (old nVidia Program) for provision of info; they do not work on Win 8 and provides in accurate info - closing off and immediately going to BIOS if you have it as implied above; you will be able to view the actual readings.

NOTE: In my own BIOS, I had aleady attempted the configurations to automatically shut down if it hits the core (max) levels to prevent damages, it does not work for me on my mainboard system. Alerady shut down the accleration / hi*speed; and that failed; for it seems to, in VS Blend 11 BETA in C Sharp in Designing - it is self-activating. If you have the equipment to install a monitoring system as a stand alone to monitor it; that is strongly recommended.