Nvidia kernel mode driver stopped responding (Help needed)

[Darkspine]

So, I got my computer sent in to the place where I bought it, someone i worked with before is looking at it and is realy stumbling on rocks when the problem at my home is not occuring at his workplace.

this message pops up


"Nvidia kernel mode driver stopped responding and has been restored"
(not sure if its that, but. it is kernel driver, and nvidia's driver version 197.45 for example)


So, here's the thing, whenever I try to log in / change zones on WoW. my computer goes blackscreen for maybe 3-6 seconds and then pops back up giving me the said msg (look at the beginning)

And, the problem is, that.. he is not getting this message at the workplace,
so we ruled out bad drivers, software,motherboard faulth.
(Meaning it can't be that, nor the HDD cuz I just got a new one) and it stopped freezing everytime i started it so..
My only issue now is, that msg that pops up..
Now I'm not sure if it has anything to do with driver versions, or anything like that.

Since everything seems to be working fine at his workplace...
I'm trying to rule out what it could be, since the computer seems to be fine, at the same time it seems to be faulthy.
Or wherever I am connecting the "screen wire" not sure what it's called in english but ill try to explain, the one that gives you the screen image of the computer, or could it be the power wire (the one that juices the computer up with electricity)


Now, ONRPG.. please, tech my brain , help me out..

(If you could understand anything and if you know anything about this problem, please.. add me on msn, I realy want to get this fixed)

my email is: Smashoo1@hotmail.com

[SnOwBunZz]

Unless you reinstalled your drivers already (with the latest official ones and not some 3rd party site one), you cannot tell if they are faulty drivers or not.

The only reasons here why your error is happening is faulty drivers, the videocard isn't seated properly (very likely as you moved the pc) or the power cables aren't seated properly.

Oh and you mentioned a new HDD... run a chkdsk on it to make sure there aren't any corrupt sectors.

[LegendaryKonan]

I remember having this error at a time, but then I just ran a full scan with malware anti bytes and it fixed.