Stopping the Win10 download nagging

[Slytod]

An update to say I’ve been testing this longer than I ought this morning, but I deliberately turned on the game and indulged in a graphic intensive battle that I could not end before it crashed out, previously. It may be coincidence, maybe speaking too soon, but I reached the end that time. Have just the graphics drivers and PHYSX divers installed. But of course it will take some time to see if a problem with the drivers still exists. Really must get on now though. Thanks.

BTW CPU was in high 50s, can not swear they didn’t hit 60s when I wasn’t looking, I think they probably did. GPU running in mid 60s.

Whoops. BSOD. Not quite there then.

[phillpower2]

Whoops. BSOD. Not quite there then.

When you have the time, upload the crash dmp for the BSOD concerned please, no rush on my behalf as I am snowed under with work and family atm, sound familiar

[Slytod]

Cheers. Had a further one also. I’ll attach both. No great rush, just grateful to get advice on it all.
Seems to always be VIDEO_SCHEDULER_INTERNAL_ERROR.

Oh, unsure if it has any significance, but I’ve noticed it doesn’t restore properly after a BSOD any more. Since the last set of changes I end up with a movable cursor on a black background. Have to cycle the power to get back properly.

[phillpower2]

Edit to add, the second crash dmp file was empty btw.

The game Dragon Age: Inquisition is named as the process that caused the crash and the conflict was again with dxgmms2.sys.

Does any other game that you play crash.

To see if we can identify any specific driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2 (y)

1. Create a Windows System Restore Point -

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select “Create a Restore Point”
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support

2. Run Driver Verifier -

• Windows 7 & Vista - START | type verifier
• Windows 10/8.1/8 - Press WIN +X keys | select “Command Prompt (Admin)” | type verifier

Make these selections -
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -

▪️ Special Pool
▪️ Pool Tracking
▪️ Force IRQL checking
▪️ Deadlock Detection
▪️ Security Checks (new as of Windows 7)
▪️ Concurrency Stress Test (new as of Windows 8) The Concurrency Stress Test option is not available in Win10.
▪️ DDI compliance checking (new as of Windows 8)
▪️ Miscellaneous Checks

4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where “Microsoft” IS NOT the Provider
7. Click on Finish
8. Re-boot[/HIDE]

• If the Driver Verifier (DV) finds a violation, it will result in a BSOD
• After re-start, you may not be able to log on to normal Windows

… • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

… • Select “System Restore”

… • Choose the restore point that you created in step #1

• For Driver Verifier status

— select last option, 1st screen -or-

— type verifier /query (in a cmd/DOS screen)

• To turn Driver Verifier off - verifier /reset then re-boot
• The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
• All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.

[Slytod]

To be honest I tend to play one thing at a time, but as far as I am aware, no only it. Worth recalling I returned to play through the trilogy again for nostalgia reasons: the first two were not an issue, but that said this third is probably the most graphic reliant game I have.

I may be mistaken about the black screen. I experienced a crash and left it “whining” though the speakers as I went out to pay a bill and get shopping and when I returned it was no longer a black screen. So maybe it just takes ages to properly recover. (Or maybe it simply rebooted again ?)

I’ll copy out and run though the instructions soon, and let you know what happens.

Oh wow, you are quite correct, in fact I have 2 dmp files in Minidump that are zero bytes large. One from yesterday and one from today. Maybe it’s when I give up on the recovery from a black screen and cycle the power.

(PS does anyone know how to stop the icons on the desktop changing positions after a crash ?)

Ok unsure about the [/hide] bit but it tells me I need a reboot so I’ll go restart it anyway.
Wow, that sure is taking it’s time coming in o_O and as I type it seems to be rebooting. Well either that or the monitors were forced not to go to sleep.

Ok it seems to have come back in ok. Not any need for safe mode so I’m assuming I skip the bit about driver verifier. So… If I have interpreted your post correctly, I’m to continue as before hoping for a BSOD ? I’m assuming it is unlikely unless I fire up the game, but very likely if I do fire it up.

[Slytod]

Well that took next to no time. Hardly needs an excuse these days. Nothing much exciting going on, on the screen and off it went. The game has become unplayable for some reason, as it crashes rather quickly.

[phillpower2]

Ok it seems to have come back in ok. Not any need for safe mode so I’m assuming I skip the bit about driver verifier.

Sorry but a bit confused by the above, was the above crash dmp with Driver Verifier enabled.

There is a bit more shown to be going on in this crash dmp;

Same drivers involved, DirectX either does not like the Nvidea drivers or your card is faulty.

STACK_TEXT:
fffff801[ICODE]e94d9c38 fffff806[/ICODE]bd7a34ae : 00000000[ICODE]00000119 00000000[/ICODE]00000001 00000000[ICODE]00010681 00000000[/ICODE]0001069a : nt!KeBugCheckEx
fffff801[ICODE]e94d9c40 fffff806[/ICODE]bf1dabdb : 00000000[ICODE]00010681 ffffaf05[/ICODE]72d88000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
fffff801[ICODE]e94d9c80 fffff806[/ICODE]bf1da655 : ffffaf05[ICODE]72d66010 ffffaf05[/ICODE]72d88000 00000000[ICODE]ff04000c 00000000[/ICODE]00000002 : dxgmms2! ?? ::FNODOBFM::[ICODE]string'+0x56eb fffff801[/ICODE]e94d9cb0 fffff806[ICODE]bf1cc0ad : fffff801[/ICODE]00010681 fffff801[ICODE]e94d9ec0 ffffaf05[/ICODE]72d66010 00000000[ICODE]00000000 : dxgmms2! ?? ::FNODOBFM::[/ICODE]string’+0x5165
fffff801[ICODE]e94d9d00 fffff806[/ICODE]bc60c2c4 : ffffaf05[ICODE]73329030 0053002b[/ICODE]002b0010 fffff806[ICODE]bf77e8ac 00000000[/ICODE]00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
fffff801[ICODE]e94d9d30 fffff806[/ICODE]bf7b37bf : ffffaf05[ICODE]73329030 fffff801[/ICODE]e94d9e39 fffff801[ICODE]e94d9ec0 ffffaf05[/ICODE]73469000 : dxgkrnl!DxgNotifyInterruptCB+0x74
fffff801[ICODE]e94d9d60 ffffaf05[/ICODE]73329030 : fffff801[ICODE]e94d9e39 fffff801[/ICODE]e94d9ec0 ffffaf05[ICODE]73469000 fffff806[/ICODE]bf7b374f : nvlddmkm+0xd37bf
fffff801[ICODE]e94d9d68 fffff801[/ICODE]e94d9e39 : fffff801[ICODE]e94d9ec0 ffffaf05[/ICODE]73469000 fffff806[ICODE]bf7b374f ffffaf05[/ICODE]73469000 : 0xffffaf05[ICODE]73329030 fffff801[/ICODE]e94d9d70 fffff801[ICODE]e94d9ec0 : ffffaf05[/ICODE]73469000 fffff806[ICODE]bf7b374f ffffaf05[/ICODE]73469000 00000000[ICODE]00000000 : 0xfffff801[/ICODE]e94d9e39
fffff801[ICODE]e94d9d78 ffffaf05[/ICODE]73469000 : fffff806[ICODE]bf7b374f ffffaf05[/ICODE]73469000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0xfffff801[ICODE]e94d9ec0 fffff801[/ICODE]e94d9d80 fffff806[ICODE]bf7b374f : ffffaf05[/ICODE]73469000 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 : 0xffffaf05[/ICODE]73469000
fffff801[ICODE]e94d9d88 ffffaf05[/ICODE]73469000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nvlddmkm+0xd374f
fffff801[ICODE]e94d9d90 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 ffffaf05[/ICODE]73329030 : 0xffffaf05`73469000

What crashed this time; PROCESS_NAME: firefox.exe

The following can be caused by flaky RAM and/or a problem with the page file;

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

Took a look at the size of your page file in your Speccy report and it is too large, rule of thumb if you are going to have a page file is that it should be 1.5 X the size of the physical memory, you have 24GB of RAM so the maximum page file size should be 36GB, for testing purposes use the guide here to temporarily disable the page file.

[Slytod]

• If the Driver Verifier (DV) finds a violation, it will result in a BSOD
• After re-start, you may not be able to log on to normal Windows

… • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

… • Select “System Restore”

… • Choose the restore point that you created in step #1

• For Driver Verifier status

— select last option, 1st screen -or-

— type verifier /query (in a cmd/DOS screen)

• To turn Driver Verifier off - verifier /reset then re-boot

This bit all seemed to relate to, if the PC had a problem coming in. It didn’t. so I missed those instructions out.

[sharp intake of breath] a new card to test with would be pricey.

Ok followed instructions for removing the virtual memory. Does it now need a reboot or does it just stop using the page ? Restarted anyway. Unsure where Speccy shows it. Still has some virtual memory apparently.

[phillpower2]

So DriverVerifier was running when the last crash happened and the computer restarted ok so you did not need to do the additional steps above.

Wouldn’t worry about a new card atm as I have a feeling that the problems that you are having may be related to when Windows 10 was installed, with the exception of the Kaspersky driver that I have highlighted in red all of the other drivers that have failed to load are Windows related hardware drivers;

Unloaded modules:
fffff806[ICODE]bf600000 fffff806[/ICODE]bf63c000 WUDFRd.sys
fffff806[ICODE]bf5c0000 fffff806[/ICODE]bf5fc000 WUDFRd.sys
fffff806[ICODE]bf290000 fffff806[/ICODE]bf2ac000 EhStorClass.
fffff806[ICODE]bb300000 fffff806[/ICODE]bb31c000 EhStorClass.
fffff806[ICODE]bae20000 fffff806[/ICODE]bae2f000 dump_ataport
fffff806[ICODE]bae40000 fffff806[/ICODE]bae4c000 dump_atapi.s
fffff806[ICODE]bae70000 fffff806[/ICODE]bae8d000 dump_dumpfve
fffff806[ICODE]bccc0000 fffff806[/ICODE]bccd4000 dam.sys
fffff806[ICODE]baa70000 fffff806[/ICODE]baa7b000 klelam.sys
fffff806[ICODE]bad00000 fffff806[/ICODE]bad0f000 hwpolicy.sys

Was Windows 10 a clean install and what type of media was used.

If Windows 10 was a clean install, did you install the drivers for the MB as well and starting with the chipset drivers first.

The info below is from your Speccy report regarding the page file which is the virtual memory;
Physical Memory
Memory Usage:
17 %
Total Physical:
24 GB
Available Physical:
20 GB
Total Virtual:
48 GB
Available Virtual:
43 GB

[Slytod]

Problem is that I was getting issues In Windows 7 which was when I first investigated via the Net and found other NVIDIA owners seemed to have the same issue.
That aside. I thought we were doing well but have just had another crash, albeit one that crashed but all but the game window apparently recovered. So no dump file.

Windows 10 was a free upgrade from 7 when the offer was on. Opted for at least partly in the hope it would clear the crash issue, but it didn’t. Not sure now, too long ago to recall exactly, I suspect I must have the upgrade file somewhere on disk, but at the time I simply followed MS instructions. As far as I can recall I simply let the MS setting/download page to list driver file replacements, with the exception of my installing the older, less volatile drivers. Do not remember loading any other in addition.

Ah Speccy still shows I have 24Gb total, 15Gb available virtual, so that isn’t just this disabled page file then ?

Just found a DVD labelled Win 10 with windows.iso on it. I guess that would have been the one I used.

[phillpower2]

The problem with doing an in place upgrade of any OS is that the hardware drivers may also need to be upgraded, you would have been better taking advantage of the free upgrade, downloading the Windows 10 ISO and then doing a clean install of Windows and the MB chipset drivers.

Problem is that I was getting issues In Windows 7 which was when I first investigated via the Net and found other NVIDIA owners seemed to have the same issue.

If you were having exactly the same issue in Windows 7 while using the same graphics card and playing only the same game that would suggest a problem with the game itself, you would have had problems with every game otherwise.

Ah Speccy still shows I have 24Gb total, 15Gb available virtual, so that isn’t just this disabled page file then ?

Not sure what you mean, can you post an updated Speccy link for us.

[phillpower2]

Aye didn’t think it would change much. Just had a BSOD, but puzzlingly no .dmp file that I can see. Last of those is from yesterday.

As said it was only temporary for testing purposes but you won`t get a crash dmp with the virtual memory set at 0, please reset the page file at something like 16GB (16000MB).

Just noticed something that I should have spotted earlier while going over your Speccy report;

1279MB NVIDIA GeForce GTX 470 (ZOTAC International): 43 °C

For multiple displays or a single display larger than 32" even for gaming on low settings you need a minimum of 2GB of VRAM but ideally you should go for a 4GB card.

Various threads on this here

To put your card through it paces, disconnect one of your screens then download and run Valley Benchmark (free) from here

[Slytod]

I do wish that the PC would not use a screen going off to mess up all the desktop icon positions. Is there no way to prevent that ?

Thanks for the info/suggestion. Did the page change. Regarding the test software, unsure what to set anything to so I’ll leave them at defaults and run it. Most likely will update with results in the morning.

Ah, seemed to be doing well, then BSOD and I’m unconvinced it created a dump as it said it would. Just suddenly rebooted. No, still nothing from today

Just tried it again with quality set to low. Lasted a lot longer (does it come to and end ?) but eventually crashed out the same, with no dump file, typically when I was out of the room getting a coffee. Does this prove a graphic RAM deficit or is it still just a possibility ?

[phillpower2]

I do wish that the PC would not use a screen going off to mess up all the desktop icon positions. Is there no way to prevent that ?

Just to address the above for now, create a new restore point, uninstall all audio drivers, restart the computer and test (if new audio drivers are offered for installing please do that when prompted).

[Slytod]

I’ll give that a try, thanks, although I’m not seeing the connection between desktop icons and audio drivers ?

Before I continue with the uninstall do I remove these from device manager “audio inputs and outputs” or “sound, video and game controllers” which seems to have audio devices ?