Stopping the Win10 download nagging

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • phillpower2
    PCHF Administrator
    • Sep 2016
    • 15205

    #91
    Example link here

    Being that you have a certain Kaspersky driver that keeps on failing to install, if uninstalling the audio drivers does not work uninstall Kaspersky and test.

    If Kaspersky is a paid for product make a note of the licence key first then use the removal tool from here

    Comment

    • Slytod
      PCHF Member
      • Jan 2017
      • 269

      #92
      Ah thanks for the link. Itโ€™s not random resets, itโ€™s when either I remove one monitor, or boot into safe mode and a more coarse resolution, that Windows start to move things around, and then leaves them in the new position when things are otherwise back to normal. I was hoping for a setting saying to leave the icons alone.

      I see no IDT driver. Was also concerned it might upset the Scarlett audio control I had to fiddle with to get working, but Iโ€™ve just realised it doesnโ€™t seem plugged in any more ?!? Iโ€™ll sort out why that is later, itโ€™s not as if Iโ€™ve used it โ€œin angerโ€ yet anyway. Got it working, got distracted by other things.

      In the circumstances I feel I probably wasnโ€™t clear. Iโ€™ll read through the page particularly option 3 which Iโ€™ve not read yet, but may leave acting on it for now.

      Oh, yes, the whole Kaspersky suite is paid for. Does more than I need but after a free AV let a nasty through a few years back I bought it and have stuck with it since. Peace of mind, although granted it may be no more than that.

      Comment

      • phillpower2
        PCHF Administrator
        • Sep 2016
        • 15205

        #93
        Steps for disabling auto arrange icons + see #3 here as to one such reason why your desktop icons keep on moving around.

        Comment

        • Slytod
          PCHF Member
          • Jan 2017
          • 269

          #94
          Cheers. The trouble with that is we expect the resolution to change in safe mode, and the amount of screen space to approximately half when a monitor is unplugged. The issue is that Windows decided to be โ€œusefulโ€ and try to get them all on the existing screen when they ought to be left alone until things are back to normal. I suspect there isnโ€™t a solution to the bug. It reads as if it is deliberate.

          Additional: That is weird. Got another crash but no dump file, so I checked the virtual page size. I donโ€™t claim to understand it but it is not at 16000 as I set it, but back at 0 ! Going to reset it again. Ah I see I have to set it per drive not per PC. Iโ€™ll assume 16000 for C: none for the rest.

          Comment

          • phillpower2
            PCHF Administrator
            • Sep 2016
            • 15205

            #95
            Originally posted by Slytod
            I suspect there isnโ€™t a solution to the bug. It reads as if it is deliberate.
            If you mean that the icons on the second screen appear on the first screen when that is the only screen connected then that is quite normal and not a bug, Windows basically reshuffles the icons and then displays them in what it deems the most appropriate order on the single desktop.

            Comment

            • Slytod
              PCHF Member
              • Jan 2017
              • 269

              #96
              I think weโ€™ll disagree on that. Still seems like a deliberate bug to me. MS could have coded it so one could always ask for a one-off auto placement if one wanted to, but it goes and messes them all up anyway. They should be left off screen until the owner makes a decision.

              Thanks for your help. Did you come up with anything else on the crash issue, or am I left with no other course of action than to buy a better graphics card ? If so I have supplementary questions on that; as when I bought the existing one I found so many different variations on a theme it was nigh impossible to sort the bargain priced ones from the not as good ones. There are so many different โ€œsubvendorsโ€ creating versions of what seems like the same thing, and no clue if one is considering something very different from the one found on websites to be recommended, and even a single โ€œsubvendorโ€ can produce a range of what seems to be basically the same thing at different prices. How does one make head or tail of it all ? And if one digs deeper it may be one finds a โ€œsubvendorโ€ has different levels of overclocking as one of the changes. Isnโ€™t that what enthusiasts do anyway ? How should the extra risk/ extra expense ratio be viewed ?

              Comment

              • phillpower2
                PCHF Administrator
                • Sep 2016
                • 15205

                #97
                Originally posted by Slytod
                Thanks for your help. Did you come up with anything else on the crash issue,
                Can[ICODE]t do anything without a crash dmp to look at I[/ICODE]m afraid, only Windows creates crash dmps so if you are not getting a BSOD + an onscreen Stop code then Windows is not crashing.
                Originally posted by Slytod
                am I left with no other course of action than to buy a better graphics card ?
                You do need a better add on video card but I would hold off on purchasing anything for now.

                Two things that I personally would do before adding any new hardware;
                1: A proper clean of the HS and CPU + fresh thermal compound application.
                2: A clean install of Windows on its own partition on the HDD.

                Comment

                • Slytod
                  PCHF Member
                  • Jan 2017
                  • 269

                  #98
                  Noting that the page file had not set to zero and ensuring it was should now help, but ironically itโ€™s not crashed since. However I wonโ€™t be at the PC again until Tuesday, so thereโ€™s a natural pause for now. Perhaps we can pick up again later next week ?

                  Comment

                  • phillpower2
                    PCHF Administrator
                    • Sep 2016
                    • 15205

                    #99
                    Not a problem & thanks for letting us know (y)

                    Comment

                    • Slytod
                      PCHF Member
                      • Jan 2017
                      • 269

                      #100
                      Short update; may well edit later. Feeling played out I, nevertheless, played the game a while today and got tired of waiting for it to crash out. So I closed that down and ran the Valley benchmark. Sure enough that caused an issue. Initially it looked as if it would recover but when it tried to the benchmark also restarted (if the loud sounds from the speaker are to be believed) and then went to a BSoD. I let it save data and reboot, and when in came back in, checked the Minidump. No .dmp file more recent than the 18th ! The virtual page is set to 16000. I shall up it to 32000 and see if it sorts the no .dmp issue. (And if that doesnโ€™t work may well simply tick for automatic sizing.)

                      Ah right: that seemed to do the trick. Turns out 16000 may not be sufficient, but 32000 scored a success.
                      .dmp file from running the Valley benchmark attached, if you have a moment to scan it for me please; and I hope it is of use given it wasnโ€™t from the game crashing.

                      Comment

                      • phillpower2
                        PCHF Administrator
                        • Sep 2016
                        • 15205

                        #101
                        Still the same cause and drivers that are failing to load - including the Kaspersky driver that keeps failing (highlighted in red below)

                        Temporarily uninstall Kaspersky make a note of the licence key first then use the removal tool from here check Windows Defender is running, update it and allow it to run a scan etc then see how the computer behaves.

                        Kernel base = 0xfffff800[ICODE]ef67e000 PsLoadedModuleList = 0xfffff800[/ICODE]ef97d000
                        Debug session time: Tue Apr 25 10:31:11.280 2017 (UTC - 4:00)
                        System Uptime: 0 days 0:08:36.159

                        • Code:
                                                                                                  *
                        • Code:
                                             Bugcheck Analysis                                    *
                        • Code:
                                                                                                  *



                        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: 000000000000b5c1
                        Arg3: 000000000000b5db
                        Arg4: ffffa20407ea1180
                        [HEADING=1]Debugging Details:[/HEADING]
                        TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

                        OVERLAPPED_MODULE: Address regions for โ€˜rspndrโ€™ and โ€˜WUDFRd.sysโ€™ overlap

                        CUSTOMER_CRASH_COUNT: 1

                        DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

                        BUGCHECK_STR: 0x119

                        PROCESS_NAME: System

                        CURRENT_IRQL: 5

                        LAST_CONTROL_TRANSFER: from fffff809b7e034ae to fffff800ef7cc7c0

                        STACK_TEXT:
                        fffff800[ICODE]f1ad2a28 fffff809[/ICODE]b7e034ae : 00000000[ICODE]00000119 00000000[/ICODE]00000001 00000000[ICODE]0000b5c1 00000000[/ICODE]0000b5db : nt!KeBugCheckEx
                        fffff800[ICODE]f1ad2a30 fffff809[/ICODE]b9fdabdb : 00000000[ICODE]0000b5c1 ffffa204[/ICODE]0974c000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
                        fffff800[ICODE]f1ad2a70 fffff809[/ICODE]b9fda655 : ffffa204[ICODE]07ea1180 ffffa204[/ICODE]0974c000 00000000[ICODE]ff04000b 00000000[/ICODE]00000002 : dxgmms2! ?? ::FNODOBFM::[ICODE]string'+0x56eb fffff800[/ICODE]f1ad2aa0 fffff809[ICODE]b9fcc0ad : fffff800[/ICODE]0000b5c1 fffff800[ICODE]f1ad2cb0 ffffa204[/ICODE]07ea1180 00000000[ICODE]00000000 : dxgmms2! ?? ::FNODOBFM::[/ICODE]stringโ€™+0x5165
                        fffff800[ICODE]f1ad2af0 fffff809[/ICODE]b7e2c2c4 : ffffa204[ICODE]0829b030 0053002b[/ICODE]002b0010 fffff809[ICODE]bbade8ac 00000000[/ICODE]00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
                        fffff800[ICODE]f1ad2b20 fffff809[/ICODE]bbb137bf : ffffa204[ICODE]0829b030 fffff800[/ICODE]f1ad2c29 fffff800[ICODE]f1ad2cb0 ffffa204[/ICODE]08282000 : dxgkrnl!DxgNotifyInterruptCB+0x74
                        fffff800[ICODE]f1ad2b50 ffffa204[/ICODE]0829b030 : fffff800[ICODE]f1ad2c29 fffff800[/ICODE]f1ad2cb0 ffffa204[ICODE]08282000 fffff809[/ICODE]bbb1374f : nvlddmkm+0xd37bf
                        fffff800[ICODE]f1ad2b58 fffff800[/ICODE]f1ad2c29 : fffff800[ICODE]f1ad2cb0 ffffa204[/ICODE]08282000 fffff809[ICODE]bbb1374f ffffa204[/ICODE]08282000 : 0xffffa204[ICODE]0829b030 fffff800[/ICODE]f1ad2b60 fffff800[ICODE]f1ad2cb0 : ffffa204[/ICODE]08282000 fffff809[ICODE]bbb1374f ffffa204[/ICODE]08282000 00000000[ICODE]00000000 : 0xfffff800[/ICODE]f1ad2c29
                        fffff800[ICODE]f1ad2b68 ffffa204[/ICODE]08282000 : fffff809[ICODE]bbb1374f ffffa204[/ICODE]08282000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0xfffff800[ICODE]f1ad2cb0 fffff800[/ICODE]f1ad2b70 fffff809[ICODE]bbb1374f : ffffa204[/ICODE]08282000 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 : 0xffffa204[/ICODE]08282000
                        fffff800[ICODE]f1ad2b78 ffffa204[/ICODE]08282000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nvlddmkm+0xd374f
                        fffff800[ICODE]f1ad2b80 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 ffffa204[/ICODE]0829b030 : 0xffffa204`08282000

                        STACK_COMMAND: kb

                        FOLLOWUP_IP:
                        dxgmms2! ?? ::FNODOBFM::[ICODE]string'+56eb fffff809[/ICODE]b9fdabdb cc int 3

                        SYMBOL_STACK_INDEX: 2

                        SYMBOL_NAME: dxgmms2! ?? ::FNODOBFM::`stringโ€™+56eb

                        FOLLOWUP_NAME: MachineOwner

                        MODULE_NAME: dxgmms2

                        IMAGE_NAME: dxgmms2.sys

                        DEBUG_FLR_IMAGE_TIMESTAMP: 58ba5e7e

                        FAILURE_BUCKET_ID: X64_0x119_VRF_dxgmms2!??::FNODOBFM::string+56eb

                        BUCKET_ID: X64_0x119_VRF_dxgmms2!??::FNODOBFM::string+56eb

                        Followup: MachineOwner

                        Unloaded modules:
                        fffff809[ICODE]ba160000 fffff809[/ICODE]ba19c000 WUDFRd.sys
                        fffff809[ICODE]ba100000 fffff809[/ICODE]ba13c000 WUDFRd.sys
                        fffff809[ICODE]b8f50000 fffff809[/ICODE]b8f5f000 dump_ataport
                        fffff809[ICODE]b8f70000 fffff809[/ICODE]b8f7c000 dump_atapi.s
                        fffff809[ICODE]b8fa0000 fffff809[/ICODE]b8fbd000 dump_dumpfve
                        fffff809[ICODE]bb7f0000 fffff809[/ICODE]bb80c000 EhStorClass.
                        fffff809[ICODE]b8480000 fffff809[/ICODE]b849c000 EhStorClass.
                        fffff809[ICODE]b9c30000 fffff809[/ICODE]b9c44000 dam.sys
                        fffff809[ICODE]b7a70000 fffff809[/ICODE]b7a7b000 klelam.sys
                        fffff809[ICODE]b8e30000 fffff809[/ICODE]b8e3f000 hwpolicy.sys

                        Comment

                        • Slytod
                          PCHF Member
                          • Jan 2017
                          • 269

                          #102
                          Will give it a try in a while but Iโ€™ve asked Kaspersky Support for info at the moment. If I uninstall I need to know I can reinstall. Iโ€™ve searched my disk and can find an executable that seems it may be version 16 but not one for 17, which is installed. Iโ€™m hoping they will send me a link to a version 17 install executable before I remove anything.

                          Comment

                          • phillpower2
                            PCHF Administrator
                            • Sep 2016
                            • 15205

                            #103
                            (y)

                            Comment

                            • Slytod
                              PCHF Member
                              • Jan 2017
                              • 269

                              #104
                              Ok. Iโ€™ve both downloaded the latest Kaspersky install file, and managed to get the CPU fan power splitter on so both CPU fans now run. (That was a trial, could write a paragraph on that on itโ€™s own. Not helping that originally the single fan had a 4 socket, socket, and now I have 2 leads plugged in to a 3 socket, one of which only has 2 wires. The pain trying to pick the right way to orient it and which pin to omit.) But letโ€™s not get distracted.

                              Uninstalled Kaspersky, got Defender running. Kicked off Valley benchmark, it seemed to be surviving well so went outside to get on with a few tasks, but when I came back Windows was reloading. Yes there is a .dmp file, which I attach.

                              Iโ€™ve presently got Defender performing a scan, as a second opinion on oneโ€™s PC is no bad thing. I take it that the plan is to replace it with Kaspersky again ASAP ?

                              Cheers.

                              Comment

                              • phillpower2
                                PCHF Administrator
                                • Sep 2016
                                • 15205

                                #105
                                Same conflict with your Nvidea drivers I`m afraid Slytod

                                While it has not resolved the crashes you have at least now ruled out Kaspersky so reinstall it at your earliest convenience.

                                Your latest crash dmp;

                                Built by: 14393.1066.amd64fre.rs1_release_sec.170327-1835
                                Machine Name:
                                Kernel base = 0xfffff800[ICODE]58403000 PsLoadedModuleList = 0xfffff800[/ICODE]58702000
                                Debug session time: Wed Apr 26 07:24:52.474 2017 (UTC - 4:00)
                                System Uptime: 0 days 0:25:50.339

                                • Code:
                                                                                                          *
                                • Code:
                                                     Bugcheck Analysis                                    *
                                • Code:
                                                                                                          *



                                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. Some info on this [COLOR=rgb(255, 77, 77)]here
                                Arg2: 0000000000022545
                                Arg3: 000000000002254d
                                Arg4: ffffac08a60dc180
                                [HEADING=1]Debugging Details:[/HEADING]
                                TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

                                DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

                                BUGCHECK_STR: 0x119

                                PROCESS_NAME: Valley.exe

                                CURRENT_IRQL: 5

                                LAST_CONTROL_TRANSFER: from fffff8016c8f34ae to fffff800585517c0

                                STACK_TEXT:
                                fffff800[ICODE]5a1a2c38 fffff801[/ICODE]6c8f34ae : 00000000[ICODE]00000119 00000000[/ICODE]00000001 00000000[ICODE]00022545 00000000[/ICODE]0002254d : nt!KeBugCheckEx
                                fffff800[ICODE]5a1a2c40 fffff801[/ICODE]6febabdb : 00000000[ICODE]00022545 ffffac08[/ICODE]a6125000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
                                fffff800[ICODE]5a1a2c80 fffff801[/ICODE]6feba655 : ffffac08[ICODE]a60dc180 ffffac08[/ICODE]a6125000 00000000[ICODE]ff04001a 00000000[/ICODE]00000002 : dxgmms2! ?? ::FNODOBFM::[ICODE]string'+0x56eb fffff800[/ICODE]5a1a2cb0 fffff801[ICODE]6feac0ad : fffff800[/ICODE]00022545 fffff800[ICODE]5a1a2ec0 ffffac08[/ICODE]a60dc180 00000000[ICODE]00000000 : dxgmms2! ?? ::FNODOBFM::[/ICODE]stringโ€™+0x5165
                                fffff800[ICODE]5a1a2d00 fffff801[/ICODE]6d53c2c4 : ffffac08[ICODE]a6a91030 0053002b[/ICODE]002b0010 fffff801[ICODE]7035e8ac 00000000[/ICODE]00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
                                fffff800[ICODE]5a1a2d30 fffff801[/ICODE]703937bf : ffffac08[ICODE]a6a91030 fffff800[/ICODE]5a1a2e39 fffff800[ICODE]5a1a2ec0 ffffac08[/ICODE]a6bd5000 : dxgkrnl!DxgNotifyInterruptCB+0x74
                                fffff800[ICODE]5a1a2d60 ffffac08[/ICODE]a6a91030 : fffff800[ICODE]5a1a2e39 fffff800[/ICODE]5a1a2ec0 ffffac08[ICODE]a6bd5000 fffff801[/ICODE]7039374f : nvlddmkm+0xd37bf
                                fffff800[ICODE]5a1a2d68 fffff800[/ICODE]5a1a2e39 : fffff800[ICODE]5a1a2ec0 ffffac08[/ICODE]a6bd5000 fffff801[ICODE]7039374f ffffac08[/ICODE]a6bd5000 : 0xffffac08[ICODE]a6a91030 fffff800[/ICODE]5a1a2d70 fffff800[ICODE]5a1a2ec0 : ffffac08[/ICODE]a6bd5000 fffff801[ICODE]7039374f ffffac08[/ICODE]a6bd5000 00000000[ICODE]00000000 : 0xfffff800[/ICODE]5a1a2e39
                                fffff800[ICODE]5a1a2d78 ffffac08[/ICODE]a6bd5000 : fffff801[ICODE]7039374f ffffac08[/ICODE]a6bd5000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0xfffff800[ICODE]5a1a2ec0 fffff800[/ICODE]5a1a2d80 fffff801[ICODE]7039374f : ffffac08[/ICODE]a6bd5000 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 : 0xffffac08[/ICODE]a6bd5000
                                fffff800[ICODE]5a1a2d88 ffffac08[/ICODE]a6bd5000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nvlddmkm+0xd374f
                                fffff800[ICODE]5a1a2d90 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 ffffac08[/ICODE]a6a91030 : 0xffffac08`a6bd5000

                                Use DDU to uninstall the present drivers (this will include the present Nvidea registry keys, folders and files, driver store etc).
                                Download driver 378.72 from here (chose this particular link to draw your attention to the following comment in the reply #10 of Sora;

                                If you want to whine at someone, go whine at microsoft who left a serious crash bug in their DirectX memory manager for almost a year (10586 - 14393)

                                When installing the suggested driver, please choose custom advance option and perform the clean driver installation.
                                After the successful installation you must reboot your computer for the changes to take effect;

                                In addition;

                                The following drivers are still shown to be having issues so if the above does not resolve the present issues then as suggested previously I would do a clean install of Windows 10 on its own partition using the latest Windows 10 ISO that is available for download, if as it is being suggested that the issue is a problem with OS builds 10586 - 14393 then using your original ISO will only reproduce the problem.

                                Unloaded modules:
                                fffff801[ICODE]70270000 fffff801[/ICODE]702ac000 WUDFRd.sys
                                fffff801[ICODE]70230000 fffff801[/ICODE]7026c000 WUDFRd.sys
                                fffff801[ICODE]6fe60000 fffff801[/ICODE]6fe7c000 EhStorClass.
                                fffff801[ICODE]6c780000 fffff801[/ICODE]6c78f000 dump_ataport
                                fffff801[ICODE]6c7a0000 fffff801[/ICODE]6c7ac000 dump_atapi.s
                                fffff801[ICODE]6c7d0000 fffff801[/ICODE]6c7ed000 dump_dumpfve
                                fffff801[ICODE]6c290000 fffff801[/ICODE]6c2ac000 EhStorClass.
                                fffff801[ICODE]6d7e0000 fffff801[/ICODE]6d7f4000 dam.sys
                                fffff801[ICODE]6ba70000 fffff801[/ICODE]6ba80000 WdBoot.sys
                                fffff801[ICODE]6c660000 fffff801[/ICODE]6c66f000 hwpolicy.sys
                                Originally posted by phillpower2
                                Can[ICODE]t do anything without a crash dmp to look at I[/ICODE]m afraid, only Windows creates crash dmps so if you are not getting a BSOD + an onscreen Stop code then Windows is not crashing.

                                You do need a better add on video card but I would hold off on purchasing anything for now.

                                Two things that I personally would do before adding any new hardware;
                                1: A proper clean of the HS and CPU + fresh thermal compound application.
                                2: A clean install of Windows on its own partition on the HDD.
                                [/COLOR]

                                Comment

                                Working...