Stopping the Win10 download nagging

[Slytod]

Wow, that fence info page made me feel as if I was back in Uni again. I should get a printer working to print it out and analyse it in detail

Still, it looked as if it boiled down to a request to change a memory location that wasn’t valid for whatever reason. One might have thought that this would be known and a fix (such as this hotfix driver) suggested when I was chasing it with NVIDIA customer support ages ago. That said, that thread was only started this year. Still… moving on.

I did purchase a kit for removing the thermal gunk and putting on new, over the weekend; but as the temperature has come down a fair bit since we started I’m loathe to mess about there again unless it proves vital to do so. The second CPU fan is now operational too. Although I note the GPU remains warm.

I’ll give the driver uninstall and reinstall soon, and see where it goes from there. Thanks once again for your attention. Really wish I could do this sort of thing for myself but it looks like it needs a LOT of experience/knowledge (plus a few pro tools I suspect )

[phillpower2]

Understand about being reluctant to remove the cooler again and as long as you do not have any further problems with the CPU temps you shouldnt get any thermal related shutdowns.

A clean install of the drivers at the link is about as much as you can do as based on the info available neither party is willing to admit responsibility for the problems that yourself and others have had with what is a known conflict between Nvidea and MS drivers

You are welcome btw

NB: Some unrelated info for you in case you have not already seen it, you previously mentioned the Windows 10 Creators Update, are you aware that MS is advising users not to manually install the said update as doing so can cause problems, the blog here explains.

[Slytod]

Cheers. Not started the AV reinstall nor the driver stuff yet. I’ll check out the blog: what I have done is find an opinion that said KB 3150513 that precedes it was not something to load; but I don’t have the knowledge to know whether it is an irrational rant or a genuine warning. I do know I dislike commercial concerns etc. nosing at me and my PC since I value privacy and only give out what I wish to (as far as I can). http://www.infoworld.com/article/318...ppearance.html This update is presently waiting in the list to be downloaded/installed.

To be honest the frequency of crashes in the game has dropped to nothing (touch wood) and I’m unsure what, out of all the things we’ve done, has been the reason. Maybe it’s a number of things all adding a slight improvement. Valley seems to hit the spot though, eventually. Meanwhile I’ll repost when I’ve progressed some.

[phillpower2]

(y) take as long as you need, no rush here and if you can use the computer trouble free then I will be made up for you.

. I do know I dislike commercial concerns etc. nosing at me and my PC since I value privacy and only give out what I wish to (as far as I can). http://www.infoworld.com/article/31…...ppearance.html This update is presently waiting in the list to be downloaded/installed.

Ditto and honest answer is that it is up to all of us to be diligent when it comes to downloading and installing anything at all from anywhere online.

[Slytod]

Ah… Valley managed to crash it again. I’ll give some thought as to whether I wish to reinstall Windows in a partition of it’s own. I think the drive letter changes may break many shortcuts etc..

[phillpower2]

I’ll give some thought as to whether I wish to reinstall Windows in a partition of it’s own. I think the drive letter changes may break many shortcuts etc..

Entirely up to you but fwiw it really is not good practice to have anything on the C: partition/drive other than Windows and your AV protection.

Have you disabled DV as your latest crash dmp is not show to be Verifier enabled.

Valley is not shown to be the cause of the latest crash, it looks more hardware related this time;

Debug session time: Thu Apr 27 12:08:45.516 2017 (UTC - 4:00)
System Uptime: 0 days 0:53:17.394

---

•                                                                         *

•                    Bugcheck Analysis                                    *

•                                                                         *

---

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 0000000000031c32
Arg3: 0000000000031c48
Arg4: ffffbf0dd899c180
[HEADING=1]Debugging Details:[/HEADING]
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x119

PROCESS_NAME: svchost.exe

CURRENT_IRQL: b

LAST_CONTROL_TRANSFER: from fffff809834534ae to fffff800cf3ce7c0

STACK_TEXT:
fffff800[ICODE]d16edc38 fffff809[/ICODE]834534ae : 00000000[ICODE]00000119 00000000[/ICODE]00000001 00000000[ICODE]00031c32 00000000[/ICODE]00031c48 : nt!KeBugCheckEx
fffff800[ICODE]d16edc40 fffff809[/ICODE]84adabdb : 00000000[ICODE]00031c32 ffffbf0d[/ICODE]d8d42000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
fffff800[ICODE]d16edc80 fffff809[/ICODE]84ada655 : ffffbf0d[ICODE]d899c180 ffffbf0d[/ICODE]d8d42000 00000000[ICODE]ff04000a 00000000[/ICODE]00000002 : dxgmms2! ?? ::FNODOBFM::[ICODE]string'+0x56eb fffff800[/ICODE]d16edcb0 fffff809[ICODE]84acc0ad : fffff800[/ICODE]00031c32 fffff800[ICODE]d16edec0 ffffbf0d[/ICODE]d899c180 fffff800[ICODE]cf59e040 : dxgmms2! ?? ::FNODOBFM::[/ICODE]string’+0x5165
fffff800[ICODE]d16edd00 fffff809[/ICODE]8418c2c4 : ffffbf0d[ICODE]d2181030 0053002b[/ICODE]002b0010 fffff809[ICODE]867bea48 00000000[/ICODE]00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
fffff800[ICODE]d16edd30 fffff809[/ICODE]867f3a23 : ffffbf0d[ICODE]d2181030 fffff800[/ICODE]d16ede39 fffff800[ICODE]d16edec0 ffffbf0d[/ICODE]d8c93000 : dxgkrnl!DxgNotifyInterruptCB+0x74
fffff800[ICODE]d16edd60 ffffbf0d[/ICODE]d2181030 : fffff800[ICODE]d16ede39 fffff800[/ICODE]d16edec0 ffffbf0d[ICODE]d8c93000 fffff809[/ICODE]867f39b3 : nvlddmkm+0xd3a23
fffff800[ICODE]d16edd68 fffff800[/ICODE]d16ede39 : fffff800[ICODE]d16edec0 ffffbf0d[/ICODE]d8c93000 fffff809[ICODE]867f39b3 ffffbf0d[/ICODE]d8c93000 : 0xffffbf0d[ICODE]d2181030 fffff800[/ICODE]d16edd70 fffff800[ICODE]d16edec0 : ffffbf0d[/ICODE]d8c93000 fffff809[ICODE]867f39b3 ffffbf0d[/ICODE]d8c93000 00000000[ICODE]00000000 : 0xfffff800[/ICODE]d16ede39
fffff800[ICODE]d16edd78 ffffbf0d[/ICODE]d8c93000 : fffff809[ICODE]867f39b3 ffffbf0d[/ICODE]d8c93000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0xfffff800[ICODE]d16edec0 fffff800[/ICODE]d16edd80 fffff809[ICODE]867f39b3 : ffffbf0d[/ICODE]d8c93000 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 : 0xffffbf0d[/ICODE]d8c93000
fffff800[ICODE]d16edd88 ffffbf0d[/ICODE]d8c93000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nvlddmkm+0xd39b3
fffff800[ICODE]d16edd90 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 ffffbf0d[/ICODE]d2181030 : 0xffffbf0d`d8c93000

STACK_COMMAND: kb

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BYTE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BYTE

Followup: memory_corruption

Some further reading for you here

[Slytod]

I’ve not deliberately disabled anything. I just reinstalled Kaspersky.
Ah “VIDEO_SCHEDULER_INTERNAL_ERROR” is very familiar.
Bank Holiday visitors again at present. I shall check the link as soon as I am able. Thanks.

[phillpower2]

To check if DV is still running type verifier /query (in a cmd/DOS screen) and when time permits run the Video Memory Stress Test (free) which you can download from Majorgeeks, see info here

Busy myself tomorrow so no rush on our behalf (y)

[Slytod]

Gee whiz that sent more info to the screen than I expected, and but it seems to have Xs against the things you spoke of.
Interestingly I downloaded vmt almost 2 years ago. Only realised when I downloaded it again and it arrived as vmt(1).

I’ll kick off vmt and see what happens.

[phillpower2]

Couple of drivers shown to have problems, click on links below for info

MODULE: klids.sys (load: 2 / unload: 1)
MODULE: dump_atapi.sys (load: 2 / unload: 1)
MODULE: dump_dumpfve.sys (load: 2 / unload: 1)

[Slytod]

Tried the vmt programme, once with the default setting, once setting the memory checked to the number of megabytes Speccy indicated. Thought the second one would be larger but no. Unsure what to make of the results, it complains of unsupported things.

Hmm Malwarebytes doesn’t exactly go a bundle on those SlimDrivers.

[phillpower2]

Did you put a tick in the Use onscreen buffer check box.

OCCT is another test for your card, newer and still supported, I know its on the Windows 7 forum but if my memory is not failing me the details are the same for Windows 10, info here

[Slytod]

No I’d left it as the default unticked. Just started it up again with that ticked, expecting it to be a quick test, but at the present rate it’ll end in the early hours of tomorrow morning. I’ll update when I can.

My error, I come back to it and the screen has gone black, and then I move the mouse to find it’s ended.

Changing video mode to 640x480x16…OK
[01/05/2017 16:47:57] Test started for “Primary Display Driver (NVIDIA GeForce GTX 470)”…
Trying 16bpp RGB:565 mode…OK
TEST FAIL (Code: 8876017C)
Trying 16bpp RGB:555 mode…OK
TEST FAIL (Code: 8876017C)
Trying 16bpp BGR:565 mode…NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode…OK
TEST FAIL (Code: 8876017C)
Trying 32bpp BGR:888 mode…NOT SUPPORTED (Code: 80004001)
NO PASS COMPLETED
Changing video mode to 640x480x16…OK
WARNING: Do not place other windows over program window!
INFORMATION: Only one mode can be tested now, all others will not match.
[03/05/2017 11:44:33] Test started for “Primary Display Driver (NVIDIA GeForce GTX 470)”…
Trying 16bpp RGB:565 mode…OK
Trying 16bpp RGB:555 mode…NOT MATCH WITH CURRENT
Trying 16bpp BGR:565 mode…NOT MATCH WITH CURRENT
Trying 32bpp RGB:888 mode…NOT MATCH WITH CURRENT
Trying 32bpp BGR:888 mode…NOT MATCH WITH CURRENT

I’ll go look at that OCCT download now. Unsure if I try to find the 3.1.0 as suggested, or the 4.4.1 that the link chain ends up with. I’ll try for the latter for now.

Hmm Unclear how to install but clicking on OCCT.exe from within the zip file seems to have kicked it off. 4.4.1 is similar to that shown but not identical. Unsure the correct thing to do/set so I’ll choose the GPU:3D tab and leave all at default settings. Since that means test type = infinite, I may see how it is after about an hour, if it is still running.

Well it just seems to keep running, but to be honest I caught it twice but on the third occasion the screen went black again and it spent the last few minutes running without the display showing (I don’t know if that effects the graphics board load). I think I may go search the settings and try to find out what is happening and stop it. But meanwhile do we have anything that takes us forward ? (Update: just changed the screen off setting to never.)

For what it’s worth, OCCT is claiming that the CPU is overclocked by 5% and the bus by 0.5%.

I notice OCCT 4.4.1 only shows options for DirectX 9 & 11, not 12, (above run with 11 selected) but now I look at the game options I see the DirectX there is locked at 113D. Must be the existing drivers; I swear it used to show 12 as an option. Maybe that’s why the game doesn’t have as many issues now (that stated, I got a little tired of it for now, which is why I was using Valley to trigger crashes of late.)

[phillpower2]

I suspect that VMT is not compatible with your cards drivers being that they are more modern than what the program was last updated for, VMT duly discarded from the toolbox

I notice OCCT 4.4.1 only shows options for DirectX 9 & 11, not 12, (above run with 11 selected)

Your video card was released for DirectX 11 some five years before DirectX 12 was released so no surprises there Slytod.

Looks like you run the program with the error checking box unticked, you need to do this and as the test can take a good while I would do it when you are out for the day or leave it overnight.

Btw, s4.5.0 is the version of OCCT that I have and the Windows 7 forum link was for info only purposes (n)

[Slytod]

Thanks. Downloaded 4.5 and kicked it off before going to bed. Will check it in the morning.

Doesn’t look like anything rebooted. I’ve not looked at the results myself yet, but these were produced.

As usual I won’t be in a position to check much over the weekend. Apologies for being tardy during the week; what with getting bored with the game (for a while) and doing other things, I’ve not got back to it so much. Whilst there is still an issue it would be good to solve, it normally only affected me during the high graphics game: and the replacement drivers seem to have avoided that issue, pretty much. Would still appreciate any further advice to get rid of the underlying problems though.

Seems to be a lot of “no error”.