Stopping the Win10 download nagging

[Slytod]

I have uninstalled Experience in the past but it reinstalls every time I run the setup.exe file I have for version 347.88. As it only every seems to tell me there is a later version when I ask it to check, and otherwise not even that, and doesn’t actually automatically download it, I opted out of getting rid of it every time. I think I must have found the opt out a while ago. I can remove it again and try the custom next install.

It occurs to me that here are further updates awaiting download now and maybe I should do them before proceeding. I understand one takes hours to download/install ?

On some occasions I have seen that message but not of late. It used to appear when the game window failed to recover but the rest of Windows did. Now it simply recovers without a message, or fails to recover and needs a power cycle. Maybe I’ll try the DirectX reinstall first, perhaps after the mega download.

The graphics card data taken from Pirform Speccy page, is:

Graphics
1279MB NVIDIA GeForce GTX 470 (ZOTAC International) 50 °C

NVIDIA GeForce GTX 470
Manufacturer NVIDIA
Model GeForce GTX 470
GPU GF100
Device ID 10DE-06CD
Revision A4
Subvendor ZOTAC International (MCO)/PC Partner (19DA)
Series GeForce GTX 400
Current Performance Level Level 3
Current GPU Clock 405 MHz
Current Memory Clock 1701 MHz
Current Shader Clock 1701 MHz
Voltage 0.975 V
Technology 40 nm
Die Size 526 mm²
Release Date Mar 26, 2010
DirectX Support 11.0
OpenGL Support 5.0
Bus Interface PCI Express x16
Temperature 51 °C
Driver version 9.18.13.4788
BIOS Version 70.00.35.00.00
ROPs 40
Shaders 448 unified
Memory Type GDDR5
Physical Memory 1279 MB
Virtual Memory 1280 MB
Bus Width 64x5 (320 bit)
Filtering Modes 16x Anisotropic
Noise Level Moderate
Max Power Draw 215 Watts
Count of performance levels : 4
Level 1 - “Default”
GPU Clock 50 MHz
Memory Clock 101 MHz
Shader Clock 135 MHz
Level 2 - “2D Desktop”
GPU Clock 405 MHz
Memory Clock 810 MHz
Shader Clock 324 MHz
Level 3 - “3D Applications”
GPU Clock 405 MHz
Memory Clock 810 MHz
Shader Clock 1701 MHz
Level 4 - “3D Applications”
GPU Clock 656 MHz
Memory Clock 1312 MHz
Shader Clock 1701 MHz

I have JUST noticed the “DirectX Support 11.0” which may explain a lot ? Or maybe it’s a Pirform Speccy limitation ? It was supposed to be a good card when I bought it.

The power supply seems to be an XFX Black Edition P1-750B-NLG9 as far as I can tell from the label under the strap and old documentation I found on the PC.

[phillpower2]

On some occasions I have seen that message but not of late. It used to appear when the game window failed to recover but the rest of Windows did. Now it simply recovers without a message, or fails to recover and needs a power cycle.

The fact that you do not get the driver error message and after looking at the HWMonitor and Speedfan results I suspect that the issue is related to overheating when the computer is under load.

The voltages are fine but you are shown to have a lot of CPU usage for a computer that is doing very little + the CPU and CPU socket (CPUTIN) temperatures are way too hot and will only get hotter when gaming, as a further check see what is reported in the BIOS;

Please restart your computer and check the temperatures/voltages in the BIOS, no screenshot is required just make a note of the temperatures and the +3.3V, +5V and the +12V and post them with your next reply.

NB: BIOS voltage readings.

The readings are not conclusive in the BIOS as the computer is under the least amount of load, if they are higher or lower than what they should be though it does suggest a overheating problem.

Regarding the Nvidea drivers, only consider doing the following after sorting out the overheating and high CPU usage.

Being that the card is the Zotac brand any drivers should normally be downloaded from them, they do not provide Windows 10 drivers for the GTX 470 only up to Windows 8.1, those are the drivers that I would try and if no joy try the Windows 7 versions next, if still no joy try Windows 10 own generic graphics drivers.

Zotac have gone to the trouble of providing their own drivers for their card and it will be for a very good reason, one possibility would be because of their Firestorm program that they recommend for the card and another is because they may have modified the cards BIOS.

Edit to add, did a bit of faffing about on the Zotac homepage and found the following drivers here

[Slytod]

Shall do. Meanwhile the download didn’t include the creators update after all, and Speccy shows that the driver has not been updated.

By the way as the PC is rarely off I only don’t get the ‘overheated press F1 to continue’ type message on reboot after it has been off for an age.

Apologies but rebooted, pressed Del and went into CMOS, but failed to find the voltage and temperature info. Found many places where they could be set, but not where the existing values were show. So finally gave up on that one.

When I bought the CPU it came with a cooling heatsink so I used that and didn’t bother with the Frio one I had bought and which needed construction. I did take a further look at it recently and managed to put together the parts that go with the CPU (sans the washers which have gone missing) but a combination of now wanting to dismantle the PC and that the board is upright in the tower and this double fan thing looks heavy and bound to strain the motherboard, means I’ve not built up the nerve to try it.

[phillpower2]

By the way as the PC is rarely off I only don’t get the ‘overheated press F1 to continue’ type message on reboot after it has been off for an age.

That on it`s own is reason enough to look into the present cooling set up, the maximum safe operating temperature for the i7 930 is 67.9°C at which point the MBs thermal sensor should shut the computer down to protect the CPU, the fact that your CPU and CPU socket could be reaching 100 °C and above means that something may have become disabled in the BIOS or the temperature at what the thermal sensor should activate has been increased somehow, the alternative is that HWMonitor and Speedfan are wrong and possibly being screwed up by some ASUS software that may be installed such as AI suite, that would still not explain the high CPU usage though which again is a sign of overheating.

When I bought the CPU it came with a cooling heatsink so I used that and didn;t bother with the Frio one I had bought and which needed construction. I did take a further look at it recently and managed to put together the parts that go with the CPU (sans the washers which have gone missing) but a combination of now wanting to dismantle the PC and that the board is upright in the tower and this double fan thing looks heavy and bound to strain the motherboard, means I’ve not built up the nerve to try it.

MBs have mounting screws that hold them in place and as long as they are all in place the board will not bow or flex and they are in fact more at risk of overheating.

ARCTIC Freezer 13 CO - 200 Watt Multi-compatible Low Noise CPU Cooler with Extreme High Durability

Please note that depending on how long your hardware has been getting so hot one or more items may have suffered irreparable damage

[Slytod]

Ok thanks. I’ve installed the Zotac driver you found. Not enthusiastic about getting the PC innards all over the place at the moment so I’ll try it as it is for a time and see if there’s any improvement. May bite the bullet and fit the Frio tomorrow, but failing that after my expected visitors have gone after the Easter weekend. As for the high temperatures, IIRC they have been high for the last 7 years when the PC was built. At some times worse than others as I removed the simple heatsink, wiped away the grease, regreased it and put it all back together about 2 years ago (at a guess). Trying to get the stuff to snap onto those plastic pillars was an absolute nightmare, enough to dissuade anyone from touching it ever again, but eventually got it done and the temperatures were slightly improved for a while. I just figured it was supposed to run high.

[phillpower2]

We will leave it with you for now then and just hope that the high temps are being caused by the MBs software.

NB: Does your MB happen to have a “clear CMOS button” just below the mouse and keyboard ports at the rear of the case, if yes, using that should reset the MBs default factory settings including the thermal sensor and CPU cooling fan settings, this would mean that if the HWMonitor and Speedfan readings are accurate your system will shut down in a matter of minutes from boot.

[Slytod]

Looking at the back panel there is what looks like a small hole labelled Clear CMOS. Can’t say I’ve noticed it before. Managed to find a needle that was thin & long enough to jab at whatever was underneath. Speedfan still looks much the same, higher if I’m honest. So no immediate change. May try a reboot, and regret it.

Thought I was going to for a while too. Got the “express” screen back, on exiting that I was given the option to use default values or set things up. Chose F1 and soon found out that default values don’t achieve a lot. Disk invalid. Rebooted again and bumbled my way through. Seems default is to have the USB stick as first choice. Managed to disable the F1 error stop. And the “express” screen. Wish I knew how to use all those settings. Heck of a lot. Looks like one could have some fun there.

Did stumble on the hardware monitor though. No idea why I didn’t see it before.
CPU 84º
MB 29º
CPU voltage 1v008
3.3 voltage 3v312
5 voltage 5v190
12 voltage 12v193

Doesn’t seem to have turned itself off yet (famous last words).

[phillpower2]

Your CPU is definitely frying at 84º

Wish I knew how to use all those settings. Heck of a lot. Looks like one could have some fun there.

You can download your MB manual from here everything you need to know about settings can be found in it

[Slytod]

Thanks. I should have the manual safely stored somewhere but it’s good to be able to access stuff from the Net at any time.
Not wishing to temp fate but no crashes so far. But there again I’ve not spent an hour or so playing the game. We shall see.

[phillpower2]

Your welcome

Not wishing to temp fate but no crashes so far.

Not being pedantic but as said earlier I suspect that your computer is overheating, crashing is software related whereas overheating is hardware related and is not referred to as crashing, hanging, freezing and lock-ups are often used terms for overheating as that is what tends to happen.

[Slytod]

Oh dear. New drivers, first BSOD for a while. VIDEO SCHEDULER INTERNAL ERROR. Ah well…

[phillpower2]

Have you got a new crash dmp for us.

A suggestion for you to try at steps 1 to 9 here

Btw Slytod, as long as you are getting temps as high as what you are you will not be able to resolve all of your computer problems I`m afraid

[Slytod]

I assumed you wouldn’t be interested in dump files after concluding it’s all about the hot processor. But yes I can attach some. (Had a second crash overnight - I’d booted up again to check I’d not lost anything in the crash and then left it on (as I usually do) only to find it rebooted overnight. Don’t recall that before, different drivers, different symptoms.)

May be speaking too soon but a vacuuming of the fans seem to have dropped the CPU temperature if not the others. But I have little expectation of it remaining so. If I find time I’ll try running the game later today. (in fact looking at it again it seems to be creeping up. May just be the result of the additional suction whilst cleaning.)

[phillpower2]

Both dmps point to IMAGE_NAME: dxgmms2.sys which is the same known conflict with Nvidea drivers mentioned previously and which are also shown to be present in both crash dmps.

[Slytod]

Thanks for checking. Then even if I get the heat sorted there will still be an issue. I’d rather crashes recovered most of Windows than BSODed. I’ll consider going back to the old NVIDIA ones then. I can take it that more recent NVIDIA and AMD cards would have the same issue ?

(BTW, just tried the DirectX link, but it won’t even try to install because it detects an equal or newer version already installed, so it won’t correct any potential issues. Tried it after a recoverable crash. Didn’t note the exact details but is was something about DirectX failing due to an ill formed command and complaining about the NVIDIA driver, which is very familiar.)