Page 2 of 2 First 12
  1. #21

    Re: Probable driver problem, windows 10, sound cracking, mouse lagging

    Quote Originally Posted by wfdots2 View Post
    Quote Originally Posted by OldGrayGary View Post
    Hi again


    Much of what follows is based on your Event Viewer error logs (thank you for providing them: no worries about having to compress/decompress them).

    Intel Rapid Storage
    I think we'll likely want to remove the Intel Rapid Storage drivers again. They are causing all sorts of trouble in your error logs. Your error logs were seriously large, considering the short span they covered (late August till now). Three different categories of errors were caused by the Intel Rapid Storage drivers: a Service Control Manager error, an Application error (crash event), and a .NET Runtime error related to "IAStorDataMgrSvc.exeFramework". These errors repeat over and over and over. Far too many.

    ASMedia Controller Driver
    I like the idea of sticking with a controller driver from ASMedia - whichever one yields the best results is OK. (It seems to be mostly the USB 3.1 drivers which get the worst press). And the generic storAHCI driver was generating a lot of warnings ("reset to device RaidPort2") while the ASMedia was gone.

    Critical Errors
    For that late August to present event period, your computer "rebooted unexpectedly" at least twenty times. A few of these were related to fatal "bugchecks". You can change a few settings to allow your system to display the error message when these errors occur (rather than automatically restarting) & to save a "mini dump" (which can be analyzed to try a determine the cause of the crash). If you have had system freezes that caused you to "hard reboot" (by holding down the power button for four to ten seconds and power off) - let us know. At the end of this post, I'll paste in the instructions for making those settings changes.

    AI Suite related errors
    A component named "Asus com service" seems to be having trouble loading. Now, if it is part of the Asus AI Suite, I imagine you might want to simply completely uninstall the AI Suite -- since it's a often-cited source of trouble.

    Norton 360 & Nvidia Stream service errors
    Norton & Nvidia were top suspects in your hard pagefault count charts. They are also producing a fair amount of errors in your logs. Both of them have had modules crashing regularly. For Nvidia, the errors point to the "NvStreamNetworkService.exe", the network streaming component of the optional "GeForce Experience" modules. Earlier in this thread, I think I posted a link to a few articles on how to manage the custom installs for the latest Nvidia drivers - you can clean out the old, and install the new - while being able to pick and choose which, if any, of the optional "extras" are needed or desired. For Norton, I still think trying things with Norton uninstalled is something to consider: your subscription is still good for the same period of time ... you can always reinstall if it turns out Norton isn't causing some of the trouble. Whether or not you uninstall Norton (at least for testing) -- Norton still needs to be either "repair reinstalled" or removed and reinstalled: it's causing errors in the background. And it's not good when modules of your antivirus crash. Can't hurt to boot the computer with a "Rescue CD" to provide a "second opinion" antimalware scan.

    Windows Fast Startup
    Your error logs have several entries "Windows failed fast startup with error status 0xC00000D4" ... now, these could well be related to the times when your system restarted after a crash (since "fast startup" relies on a partial hibernation to work, and Windows doesn't have time to hibernate when it crashes suddenly). If these entries continue even after the bugchecks and reboots are fixed, let us know - it might be worth investigating.
    ____________________________________


    I promised to attach instructions for the "Automatic Restart" settings change, and the "Save as Mini-dump" setting for fatal errors. Here they are:

    How to save "Minidumps" after Blue Screen Errors & Turn Off Automatic Restart after a System Crash


    1) Right-click the Windows 10 Start Menu icon
    2) Select System
    3) Select Advanced Settings
    4) In the Advanced tab, in the Startup and Recovery section, select Settings
    5) In the System Failure section, make sure there is a checkmark in the option box "Write an event to the system log"
    6) In the System Failure section, remove the checkmark from the option box "Automatically restart" (this will allow you to see the actual error screen - and be able to immediately see the error message without having to look through the logs)
    7) In the System Failure section, in the drop-down menu for "Write debugging information", select the item "Small memory dump (256 KB)" ... you should see the "Small Dump Directory" location automatically display the default %SystemRoot%\Minidump [%SystemRoot% stands for the directory containing the Windows folder.... on many systems, that is C:\Windows].
    8) Click OK to save and exit the settings window.

    If you continue to get fatal errors (also called Blue Screen errors), you can try investigating possible causes by using a simple and free dump-analysis program, such as WhoCrashed by Resplendence Software (the same software house that produces Latency Monitor). Should serious Blue screen errors continue for any length of time, we'll refer you to the BSOD forum here at SysNative - where the techs have training with in-depth analysis and advanced tools for such errors.

    Sorry for the extended length of this post ... there was a lot of material to cover. Might be easier to print this out, and just try things one small step at a time.

    Thank you for your kind reply. I am going to go through this one point at a time and then wait for the error to return. So far I have uninstalled Intel rapid storage and have kept my SATA driver at the current version. So far the error has not returned. Will keep you updated. Thank you!

    Well it didn't take long for things to go south again. Same driver, same lag.

    I would like to go through your points individually:

    Intel Rapid Storage: Uninstalled

    Asus driver: current running the 3.0.6 version

    Critical errors: This is something you might find surprising: I have not experienced any freezes or restarts. I have tried to bring the computer back from standby mode a couple times and I had a blank screen necessitating a hard reset, however have never had a system freeze.

    AI suite: I uninstalled this months ago, perhaps back in June. I have looked for it again in the program uninstall options and there is nothing there. I acutally installed AI suite thinking that something in it would fix my problem. Also known as the shotgun method, it didnt work.

    Nvidia: I went through the steps of uninstalling the stream.

    N360: I did a full system scan. There is an option for norton "power eraser" which apparently finds unused programs that need to be deleted. Would you recommend doing this?

    Fast startup: Not sure what this is. I know there is an option for fast startup in my BIOS which is currently turned on.



    Here is a question I am asking out of frustration: If I just bought a completely new motherboard and rebuilt this thing, would this problem go away?



    Thanks as always for your help


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22

    Re: Probable driver problem, windows 10, sound cracking, mouse lagging

    Hi again .... sorry for the very long delay: I seem to have an overabundance of some human bug (common cold) along with a large number of clients having emergencies lately ... Never dull, that's for sure.

    Replacing the motherboard is a fairly big step: it's a nice quick(ish) fix when it works (compared to the drawn-out frustration of trying to discover an obscure cause - in the maze of files that characterize modern computing) ... But it's a heart-breaker when a replacement board doesn't fix things.

    Since your audio improved a few times during our troubleshooting, it's possible that there is a mix of settings and processes that can eventually yield a suitably "listenable" outcome.

    I'm not familiar with Norton's "power eraser" ... If I find some time (after my current deluge), I'll take a look.

    The fast startup I mentioned is a Windows 10 power setting. I believe it is enabled by default on most Windows 10 systems. Instead of the computer completely shutting down (like the "old days"), "fast startup" (which could also be named "slower shutdown"!) uses a sort of "hibernation" - not a full hibernation, but a "hybrid" mix. It shortens startup time a bit. It can lead to problems on some system's mix of settings and processes ... and yet can run just fine on most. It's just a wild card ...

    To Enable or Disable Fast Startup in Windows 10


    1) Right-click the Windows 10 Start menu
    2) Select Power Options.
    3) Select Choose what the power buttons do.
    4) Select Change settings that are currently unavailable.
    5) Scroll down to Shutdown settings, and
    .......a) Place a checkmark in the option box "Turn on fast startup".
    or
    .......b) Remove the checkmark in the option box "Turn on fast startup".
    6) Select Save changes to save and exit.


    ... I've been so busy lately, I can't remember why I mentioned checking fast startup ... Hopefully, I can review this thread when my head is a bit clearer (thank goodness colds don't last long)

    Cheers & think positive

  3. #23

    Re: Probable driver problem, windows 10, sound cracking, mouse lagging

    P.S. ..... have a look at the Critical Errors & see if the times that they occurred jogs any ideas about what was happening then.... If you set the system to save the "minidumps", you'll have some error "dumps" that might yield a clue as to what is causing the errors to appear in your Event logs.

  4. #24

    Re: Probable driver problem, windows 10, sound cracking, mouse lagging

    [QUOTE=OldGrayGary;170748]Hi again .... sorry for the very long delay: I seem to have an overabundance of some human bug (common cold) along with a large number of clients having emergencies lately ... Never dull, that's for sure.

    Replacing the motherboard is a fairly big step: it's a nice quick(ish) fix when it works (compared to the drawn-out frustration of trying to discover an obscure cause - in the maze of files that characterize modern computing) ... But it's a heart-breaker when a replacement board doesn't fix things.

    Since your audio improved a few times during our troubleshooting, it's possible that there is a mix of settings and processes that can eventually yield a suitably "listenable" outcome.

    I'm not familiar with Norton's "power eraser" ... If I find some time (after my current deluge), I'll take a look.

    The fast startup I mentioned is a Windows 10 power setting. I believe it is enabled by default on most Windows 10 systems. Instead of the computer completely shutting down (like the "old days"), "fast startup" (which could also be named "slower shutdown"!) uses a sort of "hibernation" - not a full hibernation, but a "hybrid" mix. It shortens startup time a bit. It can lead to problems on some system's mix of settings and processes ... and yet can run just fine on most. It's just a wild card ...

    To Enable or Disable Fast Startup in Windows 10


    1) Right-click the Windows 10 Start menu
    2) Select Power Options.
    3) Select Choose what the power buttons do.
    4) Select Change settings that are currently unavailable.
    5) Scroll down to Shutdown settings, and
    .......a) Place a checkmark in the option box "Turn on fast startup".
    or
    .......b) Remove the checkmark in the option box "Turn on fast startup".
    6) Select Save changes to save and exit.


    ... I've been so busy lately, I can't remember why I mentioned checking fast startup ... Hopefully, I can review this thread when my head is a bit clearer (thank goodness colds don't last long)

    Cheers & think positive[/QUOTE


    I disabled fast startup to no avail. I am thinking about doing a complete clean install. I have done this a few times before with this problem, but what do you think about me being more methodical? IE making a list of installs and noting when the problem returns? Do you think this is worth it?

  5. #25

    Re: Probable driver problem, windows 10, sound cracking, mouse lagging

    Hello OldGrayGary,

    After a couple more months of try and research, I think the problem is fixed (bypassed).

    On the z97, there are intel only SATA ports. I switched all of my SATA devices to these ports, then in the BIOS disabled all the ASMEDIA SATA ports.

    Problem solved. Kind of simple but ridiculous as well. Of course, it didn't really fix the drivers, it just bypassed them.

    Thanks again for all your help.

Page 2 of 2 First 12

Similar Threads

  1. Hello All - Windows 7 Sound latency Problem
    By Steve3602 in forum Windows 7 | Windows Vista
    Replies: 0
    Last Post: 10-10-2016, 07:58 PM
  2. cracking/dropout audio problem.. (DPC?)
    By Jaewoong in forum Windows 8 | Windows RT
    Replies: 6
    Last Post: 08-20-2016, 05:42 AM
  3. Very frequent BSOD possibly due to sound driver / card - Windows 10 x64
    By Waxew in forum BSOD, Crashes, Kernel Debugging
    Replies: 28
    Last Post: 02-21-2016, 01:51 PM
  4. Audio cracking during video playback - DPC latency problem?
    By brandough in forum Windows 7 | Windows Vista
    Replies: 1
    Last Post: 08-14-2015, 12:56 PM
  5. problem with sound,got lagging 0.5s at random time
    By redsiamesecat in forum Windows 8 | Windows RT
    Replies: 16
    Last Post: 02-05-2014, 06:32 AM

Log in

Log in