i had several BSOD last night but it was because i forgot to juice up VDDP and SOC when i was trying to get a better speed out of my ram. I discovered pyprime last night and was trying to eek a few seconds out of my time.
any way thats kinda how the conversation got going it came up some how and they wanted to let me know that BSOD were only from memory trying to read at the same register twice or read and empy area. i didnt know what to say, as this was a pre screening thing with an employer and well i was up till 4 am melting for some reason and they called me pretty early in the morning.
i just kinda "huh" and stopped because it seemed strange and i couldnt tell if it was part of the screening or not. it kinda felt like not, and i've dealt with, more times than i can count, the i'm never wrong technical person and i couldnt tell if thats what i was dealing with there. frankly with less than 4 hours of sleep, an in depth conversation about it and overclocking was not something i was able to accomplish. but it really stuck with me today.
in case any one was wondering the initial question was how would you explain BSOD to the general public and if they were permanently damaging, system ending events.
My answer was; BSOD are brain farts for windows with error codes and that they are not permanent.
either way my answers were enough to get me a more formal interview, however, changes were made to the initial posting and sadly its not a livable wage
