|
As far as I've seen, the PSU is one of the problems.
It looks like the GPU needs at least 400W and the current PSU has only 300W. This is clear. Now, after some nice posts of other ![Green Alien | [Alien]](https://codeproject.freetls.fastly.net/script/Forums/Images/alien.gif) members I've known that there are other details that are important regarding the PSU capabilities which I'll double check at the shop this weekend.
But, there's always one but, this is 100% sure not the only problem.
After receiving some answers, I've seen that the motherboard installed in that computer has strange compatibility problems and that I'll be forced to update the BIOS from 7.13 to 7.16A which is the latest version from 2012 and even after doing that I'll have to make some extra steps to make it work.
Now, I'm curious: why you are shouting? why this was a painful thread? 
This community is great to get help and again it has proven that it works wonderfully well to provide it...
|
|
|
|
|
Probably I won't need that amount of Watts, but let's see what we can find at the shop this weekend.
Thank you!
|
|
|
|
|
It's been a while since I have done a lot of work with graphics cards (and I don't have time to read all the posts, maybe this was already suggested.)
Have you tried putting the old graphics card in, firing up windows, and switching to the generic VGA driver (can you still do that with newer versions of Windows?) and then putting the new card in?
Wayne
|
|
|
|
|
Nope, this will be the second set of problems (software ones) now the computer is not capable to go after the BIOS POST screen, therefore the OS drivers are still not the issue...
Thank you!
|
|
|
|
|
This may help. https://www.youtube.com/watch?v=fkBTSlBW2oc[^]
This guy has the same problem as you and he's got a 600w PSU. It seems to me to be an incompatibility between the HP bios and the nvdia card.
modified 19-Jan-15 14:37pm.
|
|
|
|
|
Without prolonging the thread too much I just wanted to mention that I have an nVidia card which requires an additional plug from the PSU; however if you do not plug in the extra plug, the system will still boot into windows just fine. You then get a friendly reminder/warning when you log in from the nVidia driver that the card cannot achieve peak performance without the extra power. But it works just fine for non-game stuff. So I'm putting my money on Paul's theory.
|
|
|
|
|
Yes Paul!
You are the second one to post the same video here and it looks like there's an incompatibility issue here... I'll test it and see what would happen if I would select the PXE network boot in the BIOS settings as the default option, if that mitigates a little bit the issue and my inlaw is happy I'll be happy too, if he is not happy then it will be time to get another motherboard and some thermal paste for the processor... 
Thank you for posting! 
|
|
|
|
|
No problem. I've had similar issues on an older HP mobo and nvidia card. One particular machine ground to a near halt after adding an nvidia GT8800 card. On the post screen you could watch it take a second or two to draw each individual character. Boot time was something like 30 minutes!!
|
|
|
|
|
NIIIIIIIICE!
I understand it is difficult to keep everything updated, but... this kind of things are terrible.
|
|
|
|
|
Wrote a new SQL Scalar function in SSMS toady, and just couldn't get it to do anything:
SELECT MyFunctionName(MyColumn) FROM MyTable Just underlined it in red and gave me
'MyFunctionName' is not a recognized built-in function name. And wouldn't run my query.
SELECT dbo.MyFunctionName(MyColumn) FROM MyTable Underlined it in red, said
Cannot find either column "dbo" ot the user-defined function or aggregate "dbo.MyFunctionName", or the name is ambiguous. But would run it, and returned null for all rows.
Spent an hour trawling google and playing with user execute permissions. Starting to pull my hair out.
Then I looked closely at the function and realised I didn't use the input parameter at all, and the function was rightly returning null... 
I still hate SSMS and functions...but it works now... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
That is so reassuring to us mere mortals. 
|
|
|
|
|
Glad to be of help! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
And you ask yourself why functions require schema name, but not stored procedures and views and tables...
Good question...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
And why it can't find them, but runs them happily... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Oh...That one...The intellisense of SSMS is just does not exists...Even SQL is case-insensitive dbo and DBO are not the same for intellisense...So do not expect too much there...(It's one of the most reported bugs, but Microsoft do not plan to do anything with it for now)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: intellisense of SSMS
Is completely pointless; I turn it off.
|
|
|
|
|
Red-Gate's tool (SQL Prompt) is more flexible!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
[Ctrl]+[Shift]+[R] any time you change anything other than data. In my world that has confused the crap out of many a junior developer (or people more used to Visual Studio)
My plan is to live forever ... so far so good
|
|
|
|
|
You forgot to mention the complete lack of meaningful error messages in SSMS...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
My all time favorite is "String or binary data would be truncated"...Where?!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
That's easy. In any column that isn't NVARCHAR(MAX). 
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Now please explain me why I should trust you I think it is only one time more: sh*t simply happens 
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
That's exactly the reason I don't like business rules in SQL Server... Try troubleshooting that #@$#*@#*@^R#@#^!!
And it gets really annoying that any object you create isn't recognized by intellisense or even any query (but runs fine) until after you restart SSMS completely (just reconnecting to your database won't work)!
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Pressing Ctrl + Shift + R refreshes intellisense no need to restart SSMS
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
The shortcut I've been searching for all my life... (Or at least the last few years)!
This will certainly make my productivity sky-rocket! 
And shame on me for not knowing this 
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
