Just a heads up to any intending to update their NV drivers.

Trying out the nVidia 361.60 Hotfix Driver, from here, I found it reinstalled and activated services I had disabled, since they tend to make my PC 'churn', I don't use them, and they seem to impact crunching and general machine performance (Old Core2 CPU)

These were:
- NVidia GeForce Experience Service (despite not using GeForce Experience)
- NVidia Network Service
- NVidia Streamer Network Service
- NVidia Streamer Service

So if you have an older host, and find things bogging down, it's worth disabling those to see if that helps (unless you use them).

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

One question - Did you install the driver automatically, or did you do a selective install where you can deselect certain features?

---

I don't buy computers, I build them!!

One question - Did you install the driver automatically, or did you do a selective install where you can deselect certain features?

I chose custom, and unticked GeForce experience.

[Edit:] best possibility I can think of, is the installer picked up on old inactive versions, updated them, and assumed I wanted them active.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I couldn't find 361.03, but I did find 364.43 (WHQL) and successfully custom installed it as a clean install. The only service listed is the display service. You may want to try it, just make sure that you check the box for clean install. BTW, I only select the driver and the PhysX software.

---

I don't buy computers, I build them!!

If I may borrow this thread for a related matter?

I'm preparing to do a big NVidia driver test. Along the way, I found:

GeForce HotFix driver 361.60 for Windows, released 12 January 2016.

This may, or may not, assist with/resolve the problems people have been reporting with NV driver 361.43

.

What are the problems that people are having with 364.43? I just installed it on my 4770K win7 (x64) w/ twin GTx750Ti. I was attempting to help Jason_gee with his problem with 631.03. They must have pulled the install package because I didn't find the 361.03 package listed.

---

I don't buy computers, I build them!!

I couldn't find 361.03, but I did find 364.43 (WHQL) and successfully custom installed it as a clean install. The only service listed is the display service. You may want to try it, just make sure that you check the box for clean install. BTW, I only select the driver and the PhysX software.

Could you double-check those version numbers, please? Your 750Ti is currently reporting "driver: 361.43 OpenCL: 1.2"

That's the one which people have been having problems with, and which the 361.60 hotfix is supposed to repair.

I'm all good on 361.60 (since disabling the extras). If anything, Probably just serves as a warning that I should use DriverSweeper to get rid of anything lurking [on top of clean install]. Good to know the installer is behaving sensibly for you :)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

To answer the question in a post by Cliff which I hope will soon be moved here:

driver 361.43 has been reported problematic in places like

Message 1756024
Thread 78792
Message 56153 (Beta)

I think I posted some suspicions that the problems applied to the version supplied by Windows Update, and the NVidia direct-download versions were OK, but I can't find my own post now.

I think I posted some suspicions that the problems applied to the version supplied by Windows Update, and the NVidia direct-download versions were OK, but I can't find my own post now.

I posted on that subject in this thread http://setiathome.berkeley.edu/forum_thread.php?id=78710#1758761

361.75 released Jan 27th. Hopefully this corrects any issues you have been experiencing.

---

Life's short; make fun of it.

361.75 released Jan 27th. Hopefully this corrects any issues you have been experiencing.

That version is running fine so far on my main rig since yesterday evening.

---

Aloha, Uli

I have 2 Pcs, both on Win 7 Ultimate, both with 361.43, BOINC 7.6.22, S@H 8 and Lunatics 0.44.

One (5974961) is fine & running great so far (touch wood). This is my daily driver as well as crunching

The other (7578105), with older hardware started hanging and BSOD soon after I upgraded it to 7.6.22 with S@H 8 and lunatics. This one only crunches.

I'll try upgrading the one that has problems to the lastest driver from NVIDIA and see how it goes.

---

Happy Crunching,

Graham

OK,at last I've got some time to try things...

I tried the latest driver (361.75) on the PC that had issues, and it hung, then rebooted itself within about 3 mins of starting processing S@H.

So I reverted that system to 355.6. It's now been running for about 5 mins & OK so far (now, where's some wood.... touches head).

I'll update on how things go, or whether I seem to have a hardware issue later on, maybe tomorrow now as it's 22:10 here.


Wish me luck.

---

Happy Crunching,

Graham

Sh, well it was a hope...

BSOD this time so looks like HW something rude!!!, so I've powered it off, and start stripping it down to clean and see if I cann see any issues tommorrow.

My Luck!!!!!!

---

Happy Crunching,

Graham

Since starting this thread, I came across a couple of 'iregularities' on the machine [since running 361.60]. First was the GPU [GTX 980] temps reaching 90C and throttling, which I resolved with a good cleanout of the GPU fan, and the rest of the machine.

Second was a more subtle problem with watching internet streams on twitch, bufferring for no apparent reason. I eliminated the usual suspects first:
- Network [OK]
- DPC Latencies [OK[
- CPU temps [OK] on top of gpu temps beign fixed
- Host memory usage OK

Then thought "well nothing to lose, run Windows update" and caught something fishy going on.
- Windows update with 'important' patches would freeze on downloading at 0%
- machine was relatively up to date, though on manual updates

Turns out at the 'Checking for updates" part, the Windows update client had been trying to update itself, finding the diagnostic services disabled, skipping, then going to stick at downloading

Next I enabled the diagnostic* services to see what would happen, then the fun begins on check for updates. It updated the windows update client, then systematically started rooting through the whole HDD (2TB RAID) with a process called CompatTelRunner.exe, A windows 10 update checking thing apparently, spotted with process explorer.

That pegged a whole core at full, and thrashed the harddrive for several hours, with no result or end in sight, so I killed the Windows update service.

As a last step I have tracked down a list of Windows updates not related directly to Win7, created a batch file to remove them, run it, disabled all Windows updates after that point, run anti-beacon.

Now watching ironchefbobbyflail play GTAV on Twitch, no unexplained CPU usage, buffering, or HDD thrashing. SLick.

A friend of mine has messaged he's getting problems with his Win7 host that sound similar. Keeping notes and analysing findings, but *feels* like Win7 support being abandoned through doing the worst possible things... So much for support through to 2020. Can't migrate main development rig to Win10 yet, simply too much that will break (even the surreptitious compatibility check chokes the host Lol).

Not happy about the cost in time, effort and worry. Last shreds of trust gone.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Jason,

That's what screwed me up on my 650ti rig, that damned "hotfix". It locked up my system too and I finally shut it down after a night of hammering the HDD. When I fired it back up it had no driver at all so I reinstalled the version that I had on it before the attempted hotfix and all is well now.

I have wondered many a time about taking the chance doing MS updates and wondered if I really should. I always do, but that may end soon too.

You know, at any time MS could sabotage all of our machines by putting a time bomb in one of their updates. I know it's not likely, but who knows for sure?

Thanks for sharing your experience!

Allen

---

Looks like they're (M$) are out to make Win7 experience as much of a hell as possible. Will be working through things as best I can, but let's alert the Linux Community they may need to take some refugees from this Putinesque calamity.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

A friend of mine has messaged he's getting problems with his Win7 host that sound similar.

I was having issues With my Win7 system freezing, or just pausing for 1-10 seconds & it took me a bit to figure it out.
I've always had Windows update set to "Check for updates but let me choose whether to download and install them". Since getting all the Win10 upgrade updates (I haven't bothered removing them) Windows does the daily check for updates, but no longer notifies me.
So after about 6 weeks of not being notified about any updates (just the odd reminder that WIn10 is available, click here to download & install) it started having the sluggish system/ system lockups occur again.

I ran Process Explorer (awesome programme) & when the system finally started misbehaving again I found there was a svchost entry that was taking up a full core.
Looking at it's associated services I noticed that one of them was wuauserv (wuaueng.dll)- Windows Update.
I didn't have any real reason to suspect Windows Update, other than the fact that it no longer would automatically tell me there are updates available.
I killed wuauserv & the CPU load of that instance of svchost dropped from 12% to nothing.
And the system stopped pausing.

A few days later the system started pausing & then freezing up, so after re-booting I fired up Process Explorer again, and there was that svchost chewing up a core. Killed wuauserv, everything worked again.

So I went to manually do Windows Update, but found that it would start, and then sit there at 0% and go no further. After a lot of screwing around i was able to get Windows Update to start updating again.
After doing all the updates that had accumulated, the system was stable again.

Several weeks later the system started freezing/pausing again. Manually did Windows Update & installed (most of) what was there, and the system was happy again.

Basically I'm manually doing Windows update every 4-6 weeks, and the system remains stable. If I don't do it, the system will eventually freeze, and keep freezing (after pausing & being very annoying) until I do the current updates.

---

Grant
Darwin NT

hmmm, good to know, and will watch out for further anomales. While still exploring, here is the batch, I named removeupdates.cmd and ran, which was based on information from http://www.dslreports.com/forum/r30348398-WIN7-Win-7-updates-to-avoid-or-be-careful-with. More precisely the initial list there later adding more from further in that thread. There could be more lurkers, though seems OK for now. Some entries I know only apply to Win8/8.1 and 10. It'd be interesting to me if someone so inclined wanted to compare to information in the Win10 thread.

@echo off 
wusa /uninstall /kb:2505438 /quiet /norestart 
wusa /uninstall /kb:2670838 /quiet /norestart 
wusa /uninstall /kb:2922324 /quiet /norestart
wusa /uninstall /kb:2952664 /quiet /norestart
wusa /uninstall /kb:2976978 /quiet /norestart 
wusa /uninstall /kb:2977759 /quiet /norestart 
wusa /uninstall /kb:2990214 /quiet /norestart
wusa /uninstall /kb:3014460 /quiet /norestart
wusa /uninstall /kb:3015249 /quiet /norestart 
wusa /uninstall /kb:3021917 /quiet /norestart 
wusa /uninstall /kb:3022345 /quiet /norestart 
wusa /uninstall /kb:3035583 /quiet /norestart
wusa /uninstall /kb:3044374 /quiet /norestart 
wusa /uninstall /kb:3050265 /quiet /norestart
wusa /uninstall /kb:3050267 /quiet /norestart 
wusa /uninstall /kb:3065987 /quiet /norestart
wusa /uninstall /kb:3065988 /quiet /norestart
wusa /uninstall /kb:3068707 /quiet /norestart 
wusa /uninstall /kb:3068708 /quiet /norestart 
wusa /uninstall /kb:3075249 /quiet /norestart
wusa /uninstall /kb:3075851 /quiet /norestart
wusa /uninstall /kb:3075853 /quiet /norestart 
wusa /uninstall /kb:3080149 /quiet /norestart
wusa /uninstall /kb:3083225 /quiet /norestart
wusa /uninstall /kb:3083324 /quiet /norestart
wusa /uninstall /kb:3083325 /quiet /norestart 
wusa /uninstall /kb:3083710 /quiet /norestart
wusa /uninstall /kb:3083711 /quiet /norestart

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

In general, would it be better to uninstall updates in this order, or to remove the most recent ones first, and work backwards?

In other words, should the batch files be sorted in descending order?

I'll compare your list with the two separate lists I made up for win7 and win8.1