Hi Guy's,just been through this with a friends computer, sent off mindump files to sevenforums. Reply was, that it was of course, caused by Nvidia. However they pointed out that the Intel controller drivers were out of date; 16/3/2006, They advised a free program called 'slimdrivers', available here; http://www.driverupdate.net/Running this detected 48 out of date drivers, even though windows update said they were all ok. note; We had Realteck sound updates just the day before, but slim drivers said they were out of date. I selected 'all' except for the video one, and no need to explain why not. However, did one group at a time starting with Intel controller drivers, ( new drivers were 8/06/2011 ) and then went and tested. Fixed! Then repeated for all others ( except video ) and now running fine.I guess the chipset drivers are the bus link on which the PCI bus runs on. Not really sure but it worked for me.No problems running the slimdrivers updates, I was a bit nervous because some of these programs are not reliable.Worth a try if you're out of idea's.Ron.

I'm out of ideas.I know only that it was working for months and months now, overclocked and all. And suddenely, after a driver change, I start getting problems. Can't be anything else.Gonna try that program. Right now it said some stuff is not up to date.

Here is something that I noticed. I get a freeze/unfreeze/error usually after in monitor off mode (which is here 10min), and when I move the mouse over the taskbar. That is the sequence of things I do. Right now Outlook was open, I read my Email, and it still didn't lock up, when I wanted to open Excel which is on the taskbar, as soon as I went over it - freeze.And now I did something unconventional: installed 301.10 on the GTX580. I'm out of ideas...

And now I did something unconventional: installed 301.10 on the GTX580. I'm out of ideas...0Regards,

No use. :(

I just had an NT.DLL error..... Ugh Now I updated to the 296.1's. Hopefully this will fix it.

after a driver change, I start getting problems. Can't be anything else.

Same here, Srdan. I wish I had never heard of that 295 driver, because once I updated to that, all these issues have started.Thanks for that HU, Ron. Will try. I too saw that Realtek sound driver update, but as my motherboard is SoundMAX sound drivers, I did not consider that.

Ok, update time.Flew the Warbird's P-51D Mustang in and out of the default FSX Friday Harbor, and touch wood, no BSOD, but I'm not 100% certain turning the o/c on the GPU has done the trick, so I'll keep monitoring and updating on this.

hi Guys,every computer is dfferent, that's for sure. I always go to seven forums.>crashes and debugging section. you just register and follow the instructions to post your minidump crash files, and perfmon files. They have always answered within one hour. They can read the files and point you in the right direction at least.I find it life saving when you get to a sticking point, and from there it gets worse as you start making radical changes, not really knowing the problem.Windows 7 is a strange beast, as seen on this web site, having a dedicated section just for crashes. XP just crashed and then we were able to fix the error, where as, Win 7 can recover itself, leaving us going... #####!.. just happened.Srdan, do you put back your CPU o'clock to standard when installing new drivers.?I always,> CPU to standard.Use programs and features ( add/remove programs) to remove old drivers.Install new ones with custom, No 3D etc. and select clean install etc.sorry if this is obvious, have you considered a system restore to a time before this started?Ron.

Srdan, do you put back your CPU o'clock to standard when installing new drivers.?

No, I don't. But then again... I never did! This downclock to install is IMO quite a lot of rubbish, that has been spread around. I say, if you have a stable overclock - all is OK.Why - I changed so many drivers since the last nvlddmkm errors were happening, about 1-2 years ago. And I never, ever downclocked my machine. Nor I downclocked for the Windows 7 install, nor FSX, nor anything.And suddenely - a driver change causes the trouble. It's not due to overclocking.I respect others opinions, but I have mine.Interesting thing, I had 301.10 installed, it crashed once, and then I disbaled Nvidia service, now installed 296.10, also removed 3D vision stuff, but left HD audio, also disabled nvidia service, and funnily - no crash until now. I had it on the whole night, in the morning waking the monitor, all ok, after the breakfast, all OK... well, here's to hoping.

Maybe this thread helps someone (I right now did it, and awaiting results):http://extreme.pcgam...em-geloest.htmlUse some translator, maybe it helps, but it says:Uninstall all drivers.Remove all existing nvlddmkm.sys from your system (in the safe mode, set all files to show, including system ones). You might need to take ownership as Administrator, then change the permissions on the files, for each one separately. See links in the thread.Make sure there are NO old files on the system. I deleted ALL.Then I installed the driver in the safe mode.Rebooted normally and installed driver again (because of physics).Made a search and confirmed there is only one version of nvlddmkm.sys on my system (296.10).Now expecting results...(if you don't know how to take ownership, ask, but I won't now write a pagelong explanation, google is your friend :P )

Thanks for that HU, Srdan.

Solved! :yahoo:It was me this time... thinking I am so clever and not having an AV. Had a totally invisible worm, an Adspy, which apparently wasn't evening running actively, so not even existing in the process manager. But somehow it managed to f*ck up my system to that extent. God knows how.Anyway, I managed to figure it out through creation of the new user profile and seeing if it's happening there. That way I basically excluded everything "personalized", then I distabled all non-microsoft services through msconfig and all autostart items.Then I noticed it was fine.So from then it was only a matter of minutes until I found the bugger...I'll get NOD Smart Security or something and be done with it.

Well done, Srdan. Glad to read you finally nailed it. I thought I too had done that except last night when just taxying off OMDB with the Simcheck A300B2-400, I put the sim in pause mode,and a few minutes later I discovered that WIndow7 had re-booted itself from a BSOD crash. So I ran that slimdrivers and it found the network card and sound drivers needed updating which I let it do, but ignored its option to go for that Nvidia 295 driver. Not had the opportunity to re-test with these new drivers, but I'm inclined to believe that it is the 285 and 295 drivers that are the culprit.

If you look onto Nvidia forums, you'll notice there are not many problems reported. That is what made it all so uneasy for me...Did you or someone else suggest me to go to sevenforums and post there? Note that you have to put the minidump and perfmon log into your post. Instructions are on the side. In case of BSOD, this is going to help possibly.

No, it was another poster who suggested posting the mini-dump at sevenforums.Personally, I did not find the Nvidia forums all that helpful compared to here.