[SOLVED] DPC Issues that cause audio stuttering, distortion, as well as video lag
- Thread starter Araschon
- Start date
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Hi Araschon (& Andy & Jared)
I looked at your first trace, and there was a high interrupt count for a module in the Nvidia driver "nvlddmkm.sys". I think it might concern power management for the card - but I'm still checking on that.
A few things that I've seen users try to help with issues when that file is involved, especially for users with Asus/Asrock motherboards:
1) If the current USB 3.0 driver is the Asus/Asrock version (usually downloaded from their website, or installed from a "driver CD" that comes with the motherboard), try using a generic Intel USB 3.0 driver. You can try uninstalling the current driver using Device Manager, and then visiting Windows update (probably before you restart [so that you don't end up reinstalling the same Asus-version driver]) and let Windows Update provide whatever USB 3.0 driver it has in its library.
2) If you haven't already, set your Energy Plan to "Maximum Performance" in Control Panel's "Power Options" app.
3) If the first two steps don't help, you can try using an old app to lower the Nvidia power management settings, called Nvidia "PowerMizer". This used to help a few users who had Windows 7 - some Windows 10 users report that it helps in 10 also ... [though some report that sometimes updates arrive, and then they have to re-set the power settings again using PowerMizer]. The trick is to lower the settings, as mentioned in the thread (scroll down to the reply by Douglas Wilcox):
Screen going black but still running - General Hardware - Laptop - Dell Community
4) If none of the above three steps help,, you can try an alternate/opposite attempt --- use a few Registry tweaks to disable the power management of nvlddmkm.sys ... this will only work if the Windows 10 Nvidia Registry settings are in the same places as the Windows 7 settings...
SOLVED! Dropouts, Cracks, Pops on Windows 7 and NVIDIA GFX CARD! | NI User Forum
Something to try ... before deciding to reinstall Windows 7 :)
I looked at your first trace, and there was a high interrupt count for a module in the Nvidia driver "nvlddmkm.sys". I think it might concern power management for the card - but I'm still checking on that.
A few things that I've seen users try to help with issues when that file is involved, especially for users with Asus/Asrock motherboards:
1) If the current USB 3.0 driver is the Asus/Asrock version (usually downloaded from their website, or installed from a "driver CD" that comes with the motherboard), try using a generic Intel USB 3.0 driver. You can try uninstalling the current driver using Device Manager, and then visiting Windows update (probably before you restart [so that you don't end up reinstalling the same Asus-version driver]) and let Windows Update provide whatever USB 3.0 driver it has in its library.
2) If you haven't already, set your Energy Plan to "Maximum Performance" in Control Panel's "Power Options" app.
3) If the first two steps don't help, you can try using an old app to lower the Nvidia power management settings, called Nvidia "PowerMizer". This used to help a few users who had Windows 7 - some Windows 10 users report that it helps in 10 also ... [though some report that sometimes updates arrive, and then they have to re-set the power settings again using PowerMizer]. The trick is to lower the settings, as mentioned in the thread (scroll down to the reply by Douglas Wilcox):
Screen going black but still running - General Hardware - Laptop - Dell Community
4) If none of the above three steps help,, you can try an alternate/opposite attempt --- use a few Registry tweaks to disable the power management of nvlddmkm.sys ... this will only work if the Windows 10 Nvidia Registry settings are in the same places as the Windows 7 settings...
SOLVED! Dropouts, Cracks, Pops on Windows 7 and NVIDIA GFX CARD! | NI User Forum
Something to try ... before deciding to reinstall Windows 7 :)
Will I have to repartition my drive before reinstalling windows 10 if these options don't work?'
Also, I uninstalled the asmedia 3.0 usb, and I was wondering if it is necessary to uninstall these two as well.
Gyazo - 2574ec199bea6d725e7243661cce5d.png
Do you know anywhere else to download powermizer manager from? The website douglas provided looked EXTREMELY sketchy, I pressed download and it doesn't send me a file, but to a website that doesn't even looked like it's owned anymore.
Gyazo - 57b2657a34f9 3de5b6b1d7965263c8 .png
Also, I uninstalled the asmedia 3.0 usb, and I was wondering if it is necessary to uninstall these two as well.
Gyazo - 2574ec199bea6d725e7243661cce5d.png
Do you know anywhere else to download powermizer manager from? The website douglas provided looked EXTREMELY sketchy, I pressed download and it doesn't send me a file, but to a website that doesn't even looked like it's owned anymore.
Gyazo - 57b2657a34f9 3de5b6b1d7965263c8 .png
Another bluescreen (IRQL_NOT_LESS_OR_EQUAL)
Event viewer has 3 events describing it.
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000."
"The DSM service was delayed by 71 seconds for a driver query/download/install on device 'HDAUDIO\FUNC_01&VEN_10DE&DEV_0041&SUBSYS_38422666&REV_1001\5&1ED170FF&3&0001'"
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Also, there are no generic intel usb drivers that I can see on the site, there are only usb host controllers that are for win 7 (tried running in compatibility for win 7 and it still didn't let me setup). When I try to uninstall asmedia usb controllers and restart all it does is reinstall them. :/
Event viewer has 3 events describing it.
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000."
"The DSM service was delayed by 71 seconds for a driver query/download/install on device 'HDAUDIO\FUNC_01&VEN_10DE&DEV_0041&SUBSYS_38422666&REV_1001\5&1ED170FF&3&0001'"
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Also, there are no generic intel usb drivers that I can see on the site, there are only usb host controllers that are for win 7 (tried running in compatibility for win 7 and it still didn't let me setup). When I try to uninstall asmedia usb controllers and restart all it does is reinstall them. :/
DPC_ watchdog_violation BSOD occurred again,
the error is still The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000.
IS THIS RELATED TO WHATS CAUSING THE AUDIO ISSUES?
New errors...
Gyazo - 6da34234683c44d32ce8764f1b .png
the error is still The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000.
IS THIS RELATED TO WHATS CAUSING THE AUDIO ISSUES?
New errors...
Gyazo - 6da34234683c44d32ce8764f1b .png
Jared
Sysnative Staff, BSOD Kernel Dump Expert
- Feb 3, 2014
- 1,591
Upload the dump files, especially the DPC_watchdog_violation, it will be related to the latency issues.
I do apologise for the delay, I have been very busy with work.
The .etl was absolutely massive, and wouldn't open because of the huge memory allocation it needed for all of the events. It used all of my RAM trying open, and I have 16GB.
You could untick minifilter drivers.
I do apologise for the delay, I have been very busy with work.
The .etl was absolutely massive, and wouldn't open because of the huge memory allocation it needed for all of the events. It used all of my RAM trying open, and I have 16GB.
You could untick minifilter drivers.
I will attach the other .etl file I made, this one was running for only 5 mins so should be a lot better. https://www.dropbox.com/s/ur7qkcxqugfa1ja/DESKTOP-IISOT11.04-15-2016.05-40-22.rar?dl=0
Don't worry about the delay I'm just really relieved that you haven't given up yet. Thank you so much. I can't find the dump file path in the event viewer descriptions of the errors (do you know where dump files are usually located in a computer?), but while poking around to try to find the file path, I found these errors.
"Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help. -event id 26"
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Don't worry about the delay I'm just really relieved that you haven't given up yet. Thank you so much. I can't find the dump file path in the event viewer descriptions of the errors (do you know where dump files are usually located in a computer?), but while poking around to try to find the file path, I found these errors.
"Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help. -event id 26"
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Jared
Sysnative Staff, BSOD Kernel Dump Expert
- Feb 3, 2014
- 1,591
C:\Windows\MEMORY.dmp for a Kernel dump which would be more helpful.
Or C:\Windows\Minidumps for small dump files.
The first error indicates you are using way too much memory with something, either through opening too many programs, or (most likely) something has leaked.
The second error is just an application error, which isn't setting its permissions correctly (I believe).
I'm still looking into that trace.
Or C:\Windows\Minidumps for small dump files.
The first error indicates you are using way too much memory with something, either through opening too many programs, or (most likely) something has leaked.
The second error is just an application error, which isn't setting its permissions correctly (I believe).
I'm still looking into that trace.
Last edited:
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Hi again all (hello there Jared, pretty busy here lately, huh)
Araschon - go back into Device Manager ... of the two Intel USB drivers, the second one looks like it is waiting to be enabled. You likely have a driver there already, it is just waiting to be enabled.
The handy dandy PowerMizer linked to by Mr. Wilcox is from quite a few years ago, but I've seen a few Win8.1 users who benefited from it - so I sent the link along. I can check that site for you if you'd like. [A safe way to encounter such sites is through a Linux computer, then scan the download both from Linux (you can scan for Windows malware on a Linux machine, if you add such software), or to put the download on removable media, and scan that from a well-protected Windows machine)].
Did you look at the Registry entries that used to apply to the Nvidia power management? ... I'd be interested to hear if they are still the same in Windows 10 - or not.
Regarding your Virtual Memory settings: since you have 8 GB of memory, test with a custom range: I like to give a generous range to virtual memory: it helps for situations when a game has an issue with memory leaks .... gives you a fighting chance to "stay in the game" longer :)
If you've never changed Virtual Memory settings, here's how:
1) Right-click the Windows 10 Start Menu icon
2) Select System
3) Select Advanced System Settings
4) In the Performance section, select Settings
5) Select the Advanced tab
6) In the Virtual Memory section, select Change
7) Create a custom range -- lower range 8192 -- higher range 16284
It's a more generous range than average ... but I find that it can be useful for heavy usage situations, (like 3D graphics, games)...
Is it an error or a warning that shows the Driver\WudfRD failed to load message? If it's a warning - it's likely because you have a SATA/AHCI drive which has hibernation turned on... I don't think that it is the likely cause of a BSOD.
If you want to use the SysNative info collection app, it will automatically zip and attach all sorts of error logs - including any BSOD memory dumps - if Windows was able to create them after the STOP error occurred. The app is available from a thread on our BSOD forum -- https://www.sysnative.com/forums/bs...windows-10-8-1-8-7-vista-post303.html#post303
You might consider trying the perfmon /health and diagnostics tips as well. If you also try the Driver Verifier idea, just remember to turn the darn thing off after you finish using it. It can make using your computer quite a "crashy" experience.
The BSODs files are thankfully reasonably small, too.
_________________________
Regarding the Windows Store error, a quick fix might be to uninstall/reinstall it using the PowerShell command method.
It's been a while since I last reviewed this thread from start to finish (it is rather long, after all) - so I can't remember if you've run extensive diagnostics yet or not. Seems worthwhile at this point. I like to recommend diagnostics, if for no other reason that they give you the assurance that you aren't trying to fix a problem caused by faulty hardware with software fixes (which doesn't end well)....
See if enabling the 2nd Intel USB driver stops the Asus/Asmedia USB driver reinstallation from recurring. We really do want the Intel version, and not the one from Asus (which has proven troublesome for a fair number of users).
And I'll have a look (& I believe Jared is having a look, too) at your latest trace ....
Araschon - go back into Device Manager ... of the two Intel USB drivers, the second one looks like it is waiting to be enabled. You likely have a driver there already, it is just waiting to be enabled.
The handy dandy PowerMizer linked to by Mr. Wilcox is from quite a few years ago, but I've seen a few Win8.1 users who benefited from it - so I sent the link along. I can check that site for you if you'd like. [A safe way to encounter such sites is through a Linux computer, then scan the download both from Linux (you can scan for Windows malware on a Linux machine, if you add such software), or to put the download on removable media, and scan that from a well-protected Windows machine)].
Did you look at the Registry entries that used to apply to the Nvidia power management? ... I'd be interested to hear if they are still the same in Windows 10 - or not.
Regarding your Virtual Memory settings: since you have 8 GB of memory, test with a custom range: I like to give a generous range to virtual memory: it helps for situations when a game has an issue with memory leaks .... gives you a fighting chance to "stay in the game" longer :)
If you've never changed Virtual Memory settings, here's how:
1) Right-click the Windows 10 Start Menu icon
2) Select System
3) Select Advanced System Settings
4) In the Performance section, select Settings
5) Select the Advanced tab
6) In the Virtual Memory section, select Change
7) Create a custom range -- lower range 8192 -- higher range 16284
It's a more generous range than average ... but I find that it can be useful for heavy usage situations, (like 3D graphics, games)...
Is it an error or a warning that shows the Driver\WudfRD failed to load message? If it's a warning - it's likely because you have a SATA/AHCI drive which has hibernation turned on... I don't think that it is the likely cause of a BSOD.
If you want to use the SysNative info collection app, it will automatically zip and attach all sorts of error logs - including any BSOD memory dumps - if Windows was able to create them after the STOP error occurred. The app is available from a thread on our BSOD forum -- https://www.sysnative.com/forums/bs...windows-10-8-1-8-7-vista-post303.html#post303
You might consider trying the perfmon /health and diagnostics tips as well. If you also try the Driver Verifier idea, just remember to turn the darn thing off after you finish using it. It can make using your computer quite a "crashy" experience.
The BSODs files are thankfully reasonably small, too.
_________________________
Regarding the Windows Store error, a quick fix might be to uninstall/reinstall it using the PowerShell command method.
It's been a while since I last reviewed this thread from start to finish (it is rather long, after all) - so I can't remember if you've run extensive diagnostics yet or not. Seems worthwhile at this point. I like to recommend diagnostics, if for no other reason that they give you the assurance that you aren't trying to fix a problem caused by faulty hardware with software fixes (which doesn't end well)....
See if enabling the 2nd Intel USB driver stops the Asus/Asmedia USB driver reinstallation from recurring. We really do want the Intel version, and not the one from Asus (which has proven troublesome for a fair number of users).
And I'll have a look (& I believe Jared is having a look, too) at your latest trace ....
For both:
I also found out that in device manager there were two SATA/AHCI drivers. One is Intel (R) 7 series/C216 chipset Family SATA/AHCI controller-1E02, and the other is the generic windows one. I uninstalled the generic windows one and kept it from reinstalling for now, and the audio issues have improved somewhat after doing that. Is this related? Should I try having the intel SATA uninstalled and the microsoft one enabled?
Jared:
Memory dump: Dropbox - MEMORY.rar
Are the two errors something that are issues?
Gary:
1. I enabled the second intel usb thing and uninstalled asmedia, I'll keep you updated, haven't restarted computer to check yet.
2. I followed the instructions and did not find the specified registry file/registry, so I'm pretty sure it isn't in the same place anymore, if it's there at all.
3. Finished changing virtual memory to the exact values you gave me
4. It says "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000.", so is that it? If it's a SATA issue, is it likely for it to be causing the audio issues?
5. Dropbox - SysnativeFileCollectionApp.zip (as for the perf health report it is stuck at collecting data for 60 seconds for around 20 minutes now. :V)
6. I think I've run Driver Verifier before.
7. How do I run extensive diagnostics?
(PS. Do you guys prefer me using this format for answering questions or is there something else I could do? As always, thank you very much for the help and information.)
I also found out that in device manager there were two SATA/AHCI drivers. One is Intel (R) 7 series/C216 chipset Family SATA/AHCI controller-1E02, and the other is the generic windows one. I uninstalled the generic windows one and kept it from reinstalling for now, and the audio issues have improved somewhat after doing that. Is this related? Should I try having the intel SATA uninstalled and the microsoft one enabled?
Jared:
Memory dump: Dropbox - MEMORY.rar
Are the two errors something that are issues?
Gary:
1. I enabled the second intel usb thing and uninstalled asmedia, I'll keep you updated, haven't restarted computer to check yet.
2. I followed the instructions and did not find the specified registry file/registry, so I'm pretty sure it isn't in the same place anymore, if it's there at all.
3. Finished changing virtual memory to the exact values you gave me
4. It says "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000.", so is that it? If it's a SATA issue, is it likely for it to be causing the audio issues?
5. Dropbox - SysnativeFileCollectionApp.zip (as for the perf health report it is stuck at collecting data for 60 seconds for around 20 minutes now. :V)
6. I think I've run Driver Verifier before.
7. How do I run extensive diagnostics?
(PS. Do you guys prefer me using this format for answering questions or is there something else I could do? As always, thank you very much for the help and information.)
Update: Another IRQL NOT LESS OR EQUAL BSOD.
The event viewer messages are strange, most are from certain services being delayed or unable to start or connect.
The errors:
"The DSM service was delayed by 135 seconds for a driver query/download/install on device 'HDAUDIO\FUNC_01&VEN_10DE&DEV_0041&SUBSYS_38422666&REV_1001\5&1ED170FF&3&0001'"
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000000000000005e, 0x0000000000000002, 0x0000000000000000, 0xfffff8006d8e8735). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 474dcf81-f3a7-4327-bbbe-f44bd2e7f560."
"The PlaysService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion"
"A timeout was reached (30000 milliseconds) while waiting for the SystemUsageReportSvc_WILLAMETTE service to connect."
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000."
"Audit events have been dropped by the transport. 0"
The event viewer messages are strange, most are from certain services being delayed or unable to start or connect.
The errors:
"The DSM service was delayed by 135 seconds for a driver query/download/install on device 'HDAUDIO\FUNC_01&VEN_10DE&DEV_0041&SUBSYS_38422666&REV_1001\5&1ED170FF&3&0001'"
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000000000000005e, 0x0000000000000002, 0x0000000000000000, 0xfffff8006d8e8735). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 474dcf81-f3a7-4327-bbbe-f44bd2e7f560."
"The PlaysService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion"
"A timeout was reached (30000 milliseconds) while waiting for the SystemUsageReportSvc_WILLAMETTE service to connect."
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000."
"Audit events have been dropped by the transport. 0"
I also did some digging around on the usb drivers. I can't get rid of the ASMEDIA one no matter what so far (I've put in its hardware id on a group policy setting that makes it so that it won't redownload drivers with ____ id, and it still reinstalls it. The only thing I could possibly do is disable it I guess).
I found out though, that the intel 3.0 usb controllers are only for windows 7 and lower. (Drivers & Software)
Is there anything I should replace the intel usb drivers with or something?
I found out though, that the intel 3.0 usb controllers are only for windows 7 and lower. (Drivers & Software)
Is there anything I should replace the intel usb drivers with or something?
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Hi again
Perfmon /report never finishes
I haven't been able to find out why this happens on some systems. It happened to one of my Windows 10 laptops that I use for testing (I try to duplicate issues forum visitors experience). But so far, no luck in finding an answer for that one yet....
SATA/AHCI drivers
I probably would have tried the generic one first, but you could simply test them separately, and see which works better on your system. The Intel driver has been associated with some latency issues ... but then driver updates are truly in flux with Windows 10 - so I think testing both is reasonable (that is -testing one, and then testing the other ... not both at the same time).
USB drivers
I'd try testing with the Intel driver enabled. It's OK if the ASmedia version re-installs. Just disable it in Device Manager. For the sake of thorough testing, you can try things with the Intel on and Asmedia disabled, then try things with ASmedia enabled and Intel disabled. It's just a few clicks in Device Manager, after all. In theory, one should prove to be less troublesome. The USB drivers from Intel do indeed come from 64-bit Windows 7 drivers, but they are supposed to work in Windows 10 as well. You don't have to download anything - I believe the Intel USB drivers were installed during your first installation of Windows 10 (you just recently enabled one of them).
Error = "The DSM service was delayed by 135 seconds for a driver query/download/install on device 'HDAUDIO\FUNC_01&VEN_10DE&DEV_0041&SUBSYS_38422666&REV_1001\5&1ED170FF&3&0001'"
This error points to what I believe is the Nvidia HD Audio driver that is part of the drivers for your Nvidia card. I believe DSM refers to the Driver Setup Manager: it was likely looking for a driver for the Nvidia HD Audio. The easiest way to deal with that (sometimes troublesome) driver, is to let it install, and then disable it in Device Manager. Once a working version of it arrives, those with Nvidia cards will be quite happy, because some of the stuttering audio issues might be linked to the current driver. The hardware ID is the 0041, vendor 10DE is Nvidia.... here is a screenshot of a chart from Nvidia that shows their hardware IDs - I highlighted the one in your error message:
Diagnostics
Since your system is experiencing some STOP errors (the "BSODs" or "Blue Screen of Death" errors), it's a good idea to make sure that faulty hardware isn't the problem. It can be hard determine why an error occurs in the system kernel, for example -- because it could be a driver problem or a hardware problem. By running diagnostics on the hardware, you can rule out failing hardware as the problem. Or reinforce it's likelihood of it being the source.
Diagnostics built-into your computer are a good first step, since they tend to test so many critical parts: motherboard, display, hard drives, optical drives, ports. But often the tests are quite brief and not very thorough. If your system has built-in diagnostics, that would show up in your user manual. System memory can be tested using MemTest86+, a reliable diagnostic many techs have trusted over many years... it is kept reasonably up-to-date, too. It is included with several other diagnostics on the free open-source diagnostic CD called the "UBCD". You can download and create the bootable CD from Ultimate Boot CD - Overview
All the instructions on how to create the CD, and how to use it, are on their website. For your hard drives, use the diagnostics from the hard drive manufacturer's support website, if available. There are some hard drive diagnostics on the UBCD ... but these tend to be older versions. If no diagnostics are available from your hard drives manufacturers, for the standard IDE/SATA drives the Hitachi/IBM diagnostics can sometime run a generic test. I don't have my notes with me at the moment... but if you have an SSD drive, use the diagnostics from the manufacturer, if possible. They are so new, I'm not sure that decent generic diagnostics are available yet ... so we'll hope for diagnostics from the manufacturers.
If your system passes all the diagnostics (or not) let us know...
Driver Verifier
This can be a handy tool, but it has to be handled carefully. Since it tends to induce crashes (in order to test drivers extensively.. which can yield helpful memory dumps after crashes).... Driver Verifier is best run for short periods, and turned off when not actively testing. It can skew the results of other diagnostics if both run at the same time.
The Windows User mode Driver Framework error (Wudfrd failed to load)
I'm not sure which device is being pointed to, but I have seen others for whom the issue as an internal hard drive & hibernation enabled on the drive. Since Windows 10 uses a "fast startup" mode that actually is a form of hibernation, you could try turning off "Fast Startup" just to see. It's harmless, usually. Microsoft figured you wouldn't care if your PC takes longer to shutdown, so long as it started up faster. It was a trade-off.
To Turn off "Fast Startup" in Windows 10:
1) Right-click the Windows 10 Start Menu icon
2) Select Power Options
3) Select Change what the power buttons do
4) Select Change settings that are currently unavailable
5) In the "Shutdown settings" section, make sure to remove the checkmark in the option-box "Turn on fast startup".
6) Select "Save Changes" and exit.
If testing things with Fast Startup disabled doesn't help, you can re-enable it following those same steps, except put a checkmark back in the option box.
_________________________
I haven't yet had a chance to look through your latest files, but I'll try to find time a bit later on....
Good luck!
Perfmon /report never finishes
I haven't been able to find out why this happens on some systems. It happened to one of my Windows 10 laptops that I use for testing (I try to duplicate issues forum visitors experience). But so far, no luck in finding an answer for that one yet....
SATA/AHCI drivers
I probably would have tried the generic one first, but you could simply test them separately, and see which works better on your system. The Intel driver has been associated with some latency issues ... but then driver updates are truly in flux with Windows 10 - so I think testing both is reasonable (that is -testing one, and then testing the other ... not both at the same time).
USB drivers
I'd try testing with the Intel driver enabled. It's OK if the ASmedia version re-installs. Just disable it in Device Manager. For the sake of thorough testing, you can try things with the Intel on and Asmedia disabled, then try things with ASmedia enabled and Intel disabled. It's just a few clicks in Device Manager, after all. In theory, one should prove to be less troublesome. The USB drivers from Intel do indeed come from 64-bit Windows 7 drivers, but they are supposed to work in Windows 10 as well. You don't have to download anything - I believe the Intel USB drivers were installed during your first installation of Windows 10 (you just recently enabled one of them).
Error = "The DSM service was delayed by 135 seconds for a driver query/download/install on device 'HDAUDIO\FUNC_01&VEN_10DE&DEV_0041&SUBSYS_38422666&REV_1001\5&1ED170FF&3&0001'"
This error points to what I believe is the Nvidia HD Audio driver that is part of the drivers for your Nvidia card. I believe DSM refers to the Driver Setup Manager: it was likely looking for a driver for the Nvidia HD Audio. The easiest way to deal with that (sometimes troublesome) driver, is to let it install, and then disable it in Device Manager. Once a working version of it arrives, those with Nvidia cards will be quite happy, because some of the stuttering audio issues might be linked to the current driver. The hardware ID is the 0041, vendor 10DE is Nvidia.... here is a screenshot of a chart from Nvidia that shows their hardware IDs - I highlighted the one in your error message:
Diagnostics
Since your system is experiencing some STOP errors (the "BSODs" or "Blue Screen of Death" errors), it's a good idea to make sure that faulty hardware isn't the problem. It can be hard determine why an error occurs in the system kernel, for example -- because it could be a driver problem or a hardware problem. By running diagnostics on the hardware, you can rule out failing hardware as the problem. Or reinforce it's likelihood of it being the source.
Diagnostics built-into your computer are a good first step, since they tend to test so many critical parts: motherboard, display, hard drives, optical drives, ports. But often the tests are quite brief and not very thorough. If your system has built-in diagnostics, that would show up in your user manual. System memory can be tested using MemTest86+, a reliable diagnostic many techs have trusted over many years... it is kept reasonably up-to-date, too. It is included with several other diagnostics on the free open-source diagnostic CD called the "UBCD". You can download and create the bootable CD from Ultimate Boot CD - Overview
All the instructions on how to create the CD, and how to use it, are on their website. For your hard drives, use the diagnostics from the hard drive manufacturer's support website, if available. There are some hard drive diagnostics on the UBCD ... but these tend to be older versions. If no diagnostics are available from your hard drives manufacturers, for the standard IDE/SATA drives the Hitachi/IBM diagnostics can sometime run a generic test. I don't have my notes with me at the moment... but if you have an SSD drive, use the diagnostics from the manufacturer, if possible. They are so new, I'm not sure that decent generic diagnostics are available yet ... so we'll hope for diagnostics from the manufacturers.
If your system passes all the diagnostics (or not) let us know...
Driver Verifier
This can be a handy tool, but it has to be handled carefully. Since it tends to induce crashes (in order to test drivers extensively.. which can yield helpful memory dumps after crashes).... Driver Verifier is best run for short periods, and turned off when not actively testing. It can skew the results of other diagnostics if both run at the same time.
The Windows User mode Driver Framework error (Wudfrd failed to load)
I'm not sure which device is being pointed to, but I have seen others for whom the issue as an internal hard drive & hibernation enabled on the drive. Since Windows 10 uses a "fast startup" mode that actually is a form of hibernation, you could try turning off "Fast Startup" just to see. It's harmless, usually. Microsoft figured you wouldn't care if your PC takes longer to shutdown, so long as it started up faster. It was a trade-off.
To Turn off "Fast Startup" in Windows 10:
1) Right-click the Windows 10 Start Menu icon
2) Select Power Options
3) Select Change what the power buttons do
4) Select Change settings that are currently unavailable
5) In the "Shutdown settings" section, make sure to remove the checkmark in the option-box "Turn on fast startup".
6) Select "Save Changes" and exit.
If testing things with Fast Startup disabled doesn't help, you can re-enable it following those same steps, except put a checkmark back in the option box.
_________________________
I haven't yet had a chance to look through your latest files, but I'll try to find time a bit later on....
Good luck!
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Update .... still haven't looked at much except for the "Minidump" BSOD files saved by Windows when your computer crashed with STOP errors. Seems like a lot of Blue Screens for such a short time. You've had eight crashes in the last two weeks. The two crashes at the end of March (on the 22nd & 23rd) point to storport.sys --- and two of the recent crashes also point to storport.sys. Of the others, Nvidia driver modules are mentioned twice, and Windows kernel modules four times. I've attached a document showing a brief description of each. I don't do BSOD analysis, but we do have a forum full of folks that do (and actually, I think Jared does). The analysis you see in the document I posted is just a "quick look" at the dump by a program called "Who Crashed" (made by the same folks who created Latency Monitor). At first glance, it certainly seems that the drivers aren't happy....
I have some travel going on tomorrow, but I should be back in the late evening. I'll try to take a look as soon as I can.
I have some travel going on tomorrow, but I should be back in the late evening. I'll try to take a look as soon as I can.
SATA driver: I have tried instead replacing the intel SATA driver with a generic one because when I tried disabling it my computer wouldn't boot at all and I had to system restore :/ (Do I just keep both of the SATA drivers running then?)
USB Drivers: Tested with both options, audio issues do not go away with either.
DSM Service Delayed: I reinstalled nvidia and then disabled it (but it's now shown as high definition audio because I replaced nvidia audio with that before, do I need to change it back to nvidia? Tbh I don't even know how to do that because it won't let me rollback).
Diagnostics: I tried windows memory diagnostics but I don't know where the logs are. I also tried Ultimate boot CD but I realized I don't have a CD, and the instructions for putting it on a USB are really difficult for me to understand.
Driver Verifier: I've run it for around 20 minutes maybe? For some reason it didn't give me any BSODS, it instead just restarted randomly every 2-5 minutes after I enabled it. I looked in event viewer and here's what I found.
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000."
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_PNY&Prod_USB_2.0_FD&Rev_1100#AD23HD1000000287&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}."
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
(I still don't know if this is an issue or not, if it is I have no clue how to change the settings to make it not happen.)
USB Drivers: Tested with both options, audio issues do not go away with either.
DSM Service Delayed: I reinstalled nvidia and then disabled it (but it's now shown as high definition audio because I replaced nvidia audio with that before, do I need to change it back to nvidia? Tbh I don't even know how to do that because it won't let me rollback).
Diagnostics: I tried windows memory diagnostics but I don't know where the logs are. I also tried Ultimate boot CD but I realized I don't have a CD, and the instructions for putting it on a USB are really difficult for me to understand.
Driver Verifier: I've run it for around 20 minutes maybe? For some reason it didn't give me any BSODS, it instead just restarted randomly every 2-5 minutes after I enabled it. I looked in event viewer and here's what I found.
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{96a4eb17-ef21-11e5-b865-806e6f6e6963}#000000E8C4A00000."
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_PNY&Prod_USB_2.0_FD&Rev_1100#AD23HD1000000287&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}."
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
(I still don't know if this is an issue or not, if it is I have no clue how to change the settings to make it not happen.)
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Hi again ...
Diagnostics
Just got back from some travelling .... No need to hunt down the Windows Memory diagnostics results, if they'd noticed anything wrong, they'd have let you know. MemTest86+ does a much more thorough job of testing the memory, so if you have a friend with an external CD drive (they are quite popular with the old "netbook" users, and the new "ultrabook" users) see if you can borrow it for an afternoon to create & run the tests. Creating a bootable USB drive is a little complicated for the average user (although there is a program called Rufus that helps alleviate that somewhat) ... so I still recommend using a CD (much less can go wrong). .... The hard drive diagnostics that I recommended also usually run from a bootable CD.
Driver Verifier
I imagine that the restarts your system experienced were actually Blue Screen errors crashing your computer, which then automatically restarted. There is a setting that toggles on/off the option to "automatically restart" on a fatal system error. You can turn the option off, so that you will see the STOP error message:
1) Right click the Windows 10 Start Menu icon
2) Select System
3) Select Advanced System Settings
4) In the Startup and Recovery section, select Settings
6) In the System Failure section, remove the checkmark from the option box in front of "automatically restart"
7) Click on OK to save and exit.
Event Viewer
The errors you mention seeing in Event Viewer don't appear to be related to whatever caused your system to restart (I'd expect "Critical" errors). When in Event Viewer, make sure to choose Event Viewer (Local) at the top of the navigation tree window on the left. This will allow you to see the "Summary of Administrative Events" window. In that window, you can view instances of Critical and non-critical errors (without having to endlessly scroll past unrelated "Informational" events]. Since Event Viewer doesn't necessarily catch the reason for the BSOD event, it's critical error messages tend to be a bit less helpful than the memory dumps themselves. The memory dumps in C:\Windows\Minidumps tend to help the most in diagnosing a STOP error. Not including any of your latest, the others are possibly linked to driver issues. A BSOD specialist can verify this for us, or let us know if it was likely due to some other cause. (If you zip and post the files in your "Minidump" folder, I imagine Jared might be able to use his expertise to let us know)....
Of the Event Viewer errors in your last post: two concern drivers for USB devices, and the last is a DCOM permissions error. At this point, heck, I wonder if you should just uninstall the whole lot of your USB devices, and let Windows 10 reinstall them upon system restart. For the permissions error, there are lengthy tutorials on how to manually edit permissions - but this is tedious and dangerous work. If I can find an easy-to-follow tutorial with step-by-step instructions and screen-shots, I'll put a link to it in this thread....
Traces
The last trace was still over 750 MB... (the one before was 1.5 GB!) ... My laptop doesn't stand a chance analyzing anything that large :)
Got to run off for a bit, ... things to do! I'll stay tuned....
*** P.S. If the restarts yielded memory dumps, those should help: and you probably will want to turn Driver Verifier off (or your system will likely crash a lot)
Diagnostics
Just got back from some travelling .... No need to hunt down the Windows Memory diagnostics results, if they'd noticed anything wrong, they'd have let you know. MemTest86+ does a much more thorough job of testing the memory, so if you have a friend with an external CD drive (they are quite popular with the old "netbook" users, and the new "ultrabook" users) see if you can borrow it for an afternoon to create & run the tests. Creating a bootable USB drive is a little complicated for the average user (although there is a program called Rufus that helps alleviate that somewhat) ... so I still recommend using a CD (much less can go wrong). .... The hard drive diagnostics that I recommended also usually run from a bootable CD.
Driver Verifier
I imagine that the restarts your system experienced were actually Blue Screen errors crashing your computer, which then automatically restarted. There is a setting that toggles on/off the option to "automatically restart" on a fatal system error. You can turn the option off, so that you will see the STOP error message:
1) Right click the Windows 10 Start Menu icon
2) Select System
3) Select Advanced System Settings
4) In the Startup and Recovery section, select Settings
6) In the System Failure section, remove the checkmark from the option box in front of "automatically restart"
7) Click on OK to save and exit.
Event Viewer
The errors you mention seeing in Event Viewer don't appear to be related to whatever caused your system to restart (I'd expect "Critical" errors). When in Event Viewer, make sure to choose Event Viewer (Local) at the top of the navigation tree window on the left. This will allow you to see the "Summary of Administrative Events" window. In that window, you can view instances of Critical and non-critical errors (without having to endlessly scroll past unrelated "Informational" events]. Since Event Viewer doesn't necessarily catch the reason for the BSOD event, it's critical error messages tend to be a bit less helpful than the memory dumps themselves. The memory dumps in C:\Windows\Minidumps tend to help the most in diagnosing a STOP error. Not including any of your latest, the others are possibly linked to driver issues. A BSOD specialist can verify this for us, or let us know if it was likely due to some other cause. (If you zip and post the files in your "Minidump" folder, I imagine Jared might be able to use his expertise to let us know)....
Of the Event Viewer errors in your last post: two concern drivers for USB devices, and the last is a DCOM permissions error. At this point, heck, I wonder if you should just uninstall the whole lot of your USB devices, and let Windows 10 reinstall them upon system restart. For the permissions error, there are lengthy tutorials on how to manually edit permissions - but this is tedious and dangerous work. If I can find an easy-to-follow tutorial with step-by-step instructions and screen-shots, I'll put a link to it in this thread....
Traces
The last trace was still over 750 MB... (the one before was 1.5 GB!) ... My laptop doesn't stand a chance analyzing anything that large :)
Got to run off for a bit, ... things to do! I'll stay tuned....
*** P.S. If the restarts yielded memory dumps, those should help: and you probably will want to turn Driver Verifier off (or your system will likely crash a lot)
Diagnostics: I will see if I can get anything done about the bootable CD drive.
Driver Verifier: I am just about to sleep, but I will run driver verifier tomorrow. A strange thing that happened when I was following your instructions: when I unchecked automatically restart, it gave me a message that I didn't have any virtual memory, so I went to change the virtual memory back to the size you gave me. When I looked at it it was set to system managed paging file instead, even though I changed it before and set it. I'll probably have to run driver verifier again tomorrow since it didn't yield any events or memory dumps because of the lack of virtual memory. :/
Event Viewer: I've checked local, summary of administrative events and looked through every one for today, and those were all I found.
About the USB devices, I'll probably try doing that, but windows doesn't generally reinstall new ones from what I've experienced. (PS, did I mention how windows is ridiculously sneaky about renabling and reinstalling drivers? I have my group policies set in a way so that devices that match the hardware id I put in are rejected by device manager and are not allowed to install without my permission, and some drivers actually get by that by re enabling themselves or reinstalling themselves. Ugh.)
Traces: I dunno what to do about that, maybe I'll just wait for Jared to analyze the traces.
Thanks!
Driver Verifier: I am just about to sleep, but I will run driver verifier tomorrow. A strange thing that happened when I was following your instructions: when I unchecked automatically restart, it gave me a message that I didn't have any virtual memory, so I went to change the virtual memory back to the size you gave me. When I looked at it it was set to system managed paging file instead, even though I changed it before and set it. I'll probably have to run driver verifier again tomorrow since it didn't yield any events or memory dumps because of the lack of virtual memory. :/
Event Viewer: I've checked local, summary of administrative events and looked through every one for today, and those were all I found.
About the USB devices, I'll probably try doing that, but windows doesn't generally reinstall new ones from what I've experienced. (PS, did I mention how windows is ridiculously sneaky about renabling and reinstalling drivers? I have my group policies set in a way so that devices that match the hardware id I put in are rejected by device manager and are not allowed to install without my permission, and some drivers actually get by that by re enabling themselves or reinstalling themselves. Ugh.)
Traces: I dunno what to do about that, maybe I'll just wait for Jared to analyze the traces.
Thanks!
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Hi - get a good night's sleep!
The virtual memory settings change probably needs us to click on OK or Apply ... then it generally tells us that we need to restart the system to apply the changes.
I think I'm headed for some sleep myself ... every morning brings a new day: let see if it's a lucky one!
The virtual memory settings change probably needs us to click on OK or Apply ... then it generally tells us that we need to restart the system to apply the changes.
I think I'm headed for some sleep myself ... every morning brings a new day: let see if it's a lucky one!
Has Sysnative Forums helped you? Please consider donating to help us support the site!