[SOLVED] Probable driver problem, windows 10, sound cracking, mouse lagging

W

wfdots2

Member
Joined
Oct 18, 2016
Posts
15
Hi Everyone,

I have been working on this problem when I have time for the past several months without a solution. First all, system specs:

Windows 10 pro 64
Core i7 4.0 GHz
Nvidia GTX 980 Video card
32 GB Corsair Vengeance quad channel ram
Asus Z97 motherboard
WD Black 2 TB 6GB p/s
512 GB Sata 6 SSD Crucial
500 GB Samsng SSD
Thermaltake 750 watt modular power supply
Soundblaster Z sound card.

The problem: intermittent cracking in sound and system/mouse lag every few seconds. Interestingly, it doesnt occur with every boot. I can usually tell when it is going to occur because startup time (usually about 7 seconds) is much delayed). It occurs in all settings, from streaming music, to listening to mp3s, to playing games.

I have updated the BIOS, all my drivers that I can possibly find, video card, etc. I bought the Soundblaster Z just in case it was the motherboard. This actually started happening in Windows 7 pro and I upgraded to 10 to see if this would help the problem. I have also performed 2 complete system wipes and the problem returns.

I have researched similar problems on other forums without much success.

I downloaded latencymon. I basically found that the windows storport and miniport drivers were causing severe lag. I upgraded my SATA drivers to try to fix this. Now latencymon is saying that it is causing the most lag. This is the Asmedia 106x SATA host controller. I have updated this to the latest beta 3.1.9.0 driver.

I dont know if I was on the right track with this or not.

I have included a screenshot of latencymon below.

Before updating Asus driver:

Dropbox - Screenshot 2016-08-28 20.07.58.png

After updating:

Dropbox - Screenshot 2016-10-18 09.52.23.png


I think I am on the right track with this, just need a little extra help. I sincerely appreciate your time.
 
Hi

The counts don't look so bad in either chart. It's not unusual, too, for Latency Monitor to have the highest latency numbers when testing - that's why it's a good idea to test both with it running and with it not running ("test by ear").

Try checking through your Bios settings again, and try creating a Latency Monitor chart with the highest hard pagefaults at the top of the list. Perhaps it's background activity or traffic causing the audio trouble. There have been a lot of "Cumulative Updates" lately, so some of the lagging performance might be due to the updates downloading in the background, Microsoft "telemetry" traffic, ... background updating, version-checking, configuring, & notifications by many of the Win10 'apps' ... (even the Photos app has a curious habit of hogging resources). You can turn off much of the background nonsense, and dial-down the MS telemetry - by going through your Windows 10 Settings screens one by one, and turning off nonsense that doesn't need to run. Some of the nonsense is several levels down, so look at every level you can! [For example, some things are a few levels down in the Privacy settings, and make sure to turn off "updates from more than one place" in Windows Update] . . .


P.S. ... also test with different headsets/speakers/cables/ports ... HDMI/Display port/VGA/DVI ...etc.
 
OldGrayGary said:
Hi

The counts don't look so bad in either chart. It's not unusual, too, for Latency Monitor to have the highest latency numbers when testing - that's why it's a good idea to test both with it running and with it not running ("test by ear").

Try checking through your Bios settings again, and try creating a Latency Monitor chart with the highest hard pagefaults at the top of the list. Perhaps it's background activity or traffic causing the audio trouble. There have been a lot of "Cumulative Updates" lately, so some of the lagging performance might be due to the updates downloading in the background, Microsoft "telemetry" traffic, ... background updating, version-checking, configuring, & notifications by many of the Win10 'apps' ... (even the Photos app has a curious habit of hogging resources). You can turn off much of the background nonsense, and dial-down the MS telemetry - by going through your Windows 10 Settings screens one by one, and turning off nonsense that doesn't need to run. Some of the nonsense is several levels down, so look at every level you can! [For example, some things are a few levels down in the Privacy settings, and make sure to turn off "updates from more than one place" in Windows Update] . . .


P.S. ... also test with different headsets/speakers/cables/ports ... HDMI/Display port/VGA/DVI ...etc.
Click to expand...


Thank you for your kind reply. To your points:

-I looked through BIOS settings again. I think everything looks as it should. All of my settings are set to high performance mode. The BIOS is the latest version I see on the Asus website. Is there a specific setting on which I should focus?

-As soon as the problem reproduces itself I would post a latencymon with pagedefaults. This is a good idea.

-I have gone through windows 10 and turned off anything "automatic." I will also say I had this same problem running windows 7 prior to updating to windows 10.

-I have tried different speaker and headsets from my old PC. Have also tried my old monitor without success. I think it is more than just audio, as when the audio cracks I get a lot of mouse lag and screen jumpiness as well.

Some other points I may have not mentioned: this occurs about 70% of the time when I'm using the PC. Sometimes I can startup and there is no problem and I dont see the long execution times. I can always tell when I'm going to have a, "good," or "bad" startup as the good startups will take about 6-7 seconds, while the other ones will lag and take much longer.

Thank you again for your reply and help!
 
OldGrayGary said:
Hi

The counts don't look so bad in either chart. It's not unusual, too, for Latency Monitor to have the highest latency numbers when testing - that's why it's a good idea to test both with it running and with it not running ("test by ear").

Try checking through your Bios settings again, and try creating a Latency Monitor chart with the highest hard pagefaults at the top of the list. Perhaps it's background activity or traffic causing the audio trouble. There have been a lot of "Cumulative Updates" lately, so some of the lagging performance might be due to the updates downloading in the background, Microsoft "telemetry" traffic, ... background updating, version-checking, configuring, & notifications by many of the Win10 'apps' ... (even the Photos app has a curious habit of hogging resources). You can turn off much of the background nonsense, and dial-down the MS telemetry - by going through your Windows 10 Settings screens one by one, and turning off nonsense that doesn't need to run. Some of the nonsense is several levels down, so look at every level you can! [For example, some things are a few levels down in the Privacy settings, and make sure to turn off "updates from more than one place" in Windows Update] . . .


P.S. ... also test with different headsets/speakers/cables/ports ... HDMI/Display port/VGA/DVI ...etc.
Click to expand...


Another reply:

So I currently DON'T have the sound problem, so I wouldn't be running latencymon at this time (if there are no symptoms I have chosen to ignore this for the past several months and try to take advantage of good computer time when I have it). Even though I can detect no audio problems, there are still problems detected by latencymon:


Screenshot 1: Dropbox - Screenshot 2016-10-19 10.02.27.png

Screenshot 2: Dropbox - Screenshot 2016-10-19 10.02.41.png

Screenshot 3: Dropbox - Screenshot 2016-10-19 10.02.50.png


This may help or add to the confusion. Thank you
 
Hi again


Thanks for the latest details and charts. The DPC and ISR counts look pretty solid again - that's good. The hard pagefault counts are a bit too high still.

At the top of your pagefault chart, there are really only two sources that are too high: a Nvidia module called the "Nvidia Container" (nvcontainer.exe) and your security suite Norton 360 (n360.exe).

Nvidia Drivers
For the Nvidia side of life, if you happen to be using any of the latest beta versions - try reverting back to a different WHQL version. It might be good to try installing a recent driver using the "Custom" installation option, and consider doing without modules in the "GeForce Experience" suite that you might be able to live without. The "nvcontainer.exe" module really had a nasty bite to it when in beta, I wonder if that persisted in some of the full driver releases. Here are a few threads over at the Nvidia forums where users where trying to get around that issue:
https://forums.geforce.com/default/...100-disk-usage-on-my-primary-drive-/?offset=3
https://forums.geforce.com/default/...0-3-127-3-0-2-190-feedback-thread/?offset=310

Here are a few guides to the clean install method for Nvidia drivers - note that they are both a few months old, and the new driver packages might have changed a bit in the details since then (apologies if you are already familiar with all of this) ---
Disable NVIDIA Streamer Service and other NVIDIA processes - gHacks Tech News
Turn Off NVIDIA Windows Services You'll Never Use | Lifehacker Australia

Norton 360
Norton 360 is a premier program, and provides a high level of security. Some versions have fairly high resource usage - this seems to vary from year to year (from version to version). I'm not sure how easy it is to limit its pagefault usage, other than trying to schedule its most intensive background activities (heaviest scans) to times when you aren't using the computer much. The real-time scanning shouldn't be so bad that it produces audio/video lagging --- but the full scans are certainly capable of that sort of slowdown. I didn't see anything in my first quick search "high page faults Norton 360" .... but maybe something will turn up ...

It looks promising that if we can slim down the Nvidia & Norton hard pagefault issues, the lagging might well disappear.
 
OldGrayGary said:
Hi again


Thanks for the latest details and charts. The DPC and ISR counts look pretty solid again - that's good. The hard pagefault counts are a bit too high still.

At the top of your pagefault chart, there are really only two sources that are too high: a Nvidia module called the "Nvidia Container" (nvcontainer.exe) and your security suite Norton 360 (n360.exe).

Nvidia Drivers
For the Nvidia side of life, if you happen to be using any of the latest beta versions - try reverting back to a different WHQL version. It might be good to try installing a recent driver using the "Custom" installation option, and consider doing without modules in the "GeForce Experience" suite that you might be able to live without. The "nvcontainer.exe" module really had a nasty bite to it when in beta, I wonder if that persisted in some of the full driver releases. Here are a few threads over at the Nvidia forums where users where trying to get around that issue:
https://forums.geforce.com/default/...100-disk-usage-on-my-primary-drive-/?offset=3
https://forums.geforce.com/default/...0-3-127-3-0-2-190-feedback-thread/?offset=310

Here are a few guides to the clean install method for Nvidia drivers - note that they are both a few months old, and the new driver packages might have changed a bit in the details since then (apologies if you are already familiar with all of this) ---
Disable NVIDIA Streamer Service and other NVIDIA processes - gHacks Tech News
Turn Off NVIDIA Windows Services You'll Never Use | Lifehacker Australia

Norton 360
Norton 360 is a premier program, and provides a high level of security. Some versions have fairly high resource usage - this seems to vary from year to year (from version to version). I'm not sure how easy it is to limit its pagefault usage, other than trying to schedule its most intensive background activities (heaviest scans) to times when you aren't using the computer much. The real-time scanning shouldn't be so bad that it produces audio/video lagging --- but the full scans are certainly capable of that sort of slowdown. I didn't see anything in my first quick search "high page faults Norton 360" .... but maybe something will turn up ...

It looks promising that if we can slim down the Nvidia & Norton hard pagefault issues, the lagging might well disappear.
Click to expand...


Thank you again--

I used driver uninstall and did a clean uninstall of graphic driver. I installed a driver from last December from before the problem started. I didn't install the geforce experience, etc, just physx and the driver itself.

In terms of Norton, I only having it doing full system scans once a week.


So here is something else I noticed-- I was playing an mp3 and looking at latencymon at the same time. Everything sounded find and was in the green zone. I was watching the driver list as the scratching and popping started, and what shot to the top of the list was the Asus driver with the 41 ms delay. Because this popped up as at the same time the I heard the first pop, I feel strongly this has something to do with things. Am I totally off base with this? Thank you for your help

PS changing the display driver to the old one didn't help unfortunately.
 
Which Asus driver went to the top of the list? Was it something like "ASMedia USB 3.1", by any chance? (if so, uninstall that driver & let Windows 10 install a generic driver instead).

Also test with Latency Monitor not running once every now and then (since Latency Monitor can itself be a source of latency) . . .
 
OldGrayGary said:
Which Asus driver went to the top of the list? Was it something like "ASMedia USB 3.1", by any chance? (if so, uninstall that driver & let Windows 10 install a generic driver instead).

Also test with Latency Monitor not running once every now and then (since Latency Monitor can itself be a source of latency) . . .
Click to expand...

It is the Asmedia 106x host controller driver. When I uninstalled it, windows installed a generic SATA driver, however then I went back to having the STORPORT drivers be the issue like initially.
 
I'm curious to hear which list the storport driver is at the top of .... Is it DPC, ISR, or pagefaults? As far as the DPC & ISR charts, all the charts so far would indicate that those aren't the source of the trouble. It was the pagefault counts that were too high.

If storport is causing high pagefaults (or if its DPC/ISR counts have jumped recently), you can try uninstalling the Intel Rapid Storage Technology drivers, and let the generics install from Windows Update.

See how it goes. If the audio stuttering has disappeared, and the only high counts exist on charts ... then you might be good to go. Sometimes the charts don't accurately reflect the actual user experience.

We'll hope for the best
 
OldGrayGary said:
I'm curious to hear which list the storport driver is at the top of .... Is it DPC, ISR, or pagefaults? As far as the DPC & ISR charts, all the charts so far would indicate that those aren't the source of the trouble. It was the pagefault counts that were too high.

If storport is causing high pagefaults (or if its DPC/ISR counts have jumped recently), you can try uninstalling the Intel Rapid Storage Technology drivers, and let the generics install from Windows Update.

See how it goes. If the audio stuttering has disappeared, and the only high counts exist on charts ... then you might be good to go. Sometimes the charts don't accurately reflect the actual user experience.

We'll hope for the best
Click to expand...


I uninstalled rapid storage tech---I don't even think I'm using this to be honest, but this is a little above my knowledge. I know I haven't configured this for use in the BIOS. Nothing changed after uninstall, unfortunately.
 
Hi again


Is the problem still only happening on some restarts/startups?

The ASMedia drivers that I've seen the most complaining about are their USB 3.1 drivers ... not as much 'noise' concerning the controller driver (although for Windows 10 that might vary)... Were the controller drivers WHQL for Windows 10? or something earlier? If a recent Windows 10 driver is available (that you haven't tried yet) give it a go....

I imagine the controller drivers might figure in to the problem - I/O performance is generally at the root of audio/video lag/glitching.

I noticed in an older post a fellow moved from an ASMedia controller driver to a "JMicron" Sata controller driver (not sure that your board is the same as his, though)
Solved Asmedia Sata Host Controller driver for Asus MOB - Windows 10 Forums

And --- just for the sake of thoroughness: I forgot to mention a possible source of audio issues in Windows 10 ... some report issues with the Game DVR bar in the Windows 10 XBox app. Truthfully, I'm not sure of its resource usage - but if you happen to be certain that you're unlikely to need it, you can disable it - and test to see if there's any difference (and re-enable it if you don't see any improvement).
Game DVR and Game Bar - Enable or Disable in Windows 10 - Windows 10 Forums

I'll stay tuned . . .
 
OldGrayGary said:
Hi again


Is the problem still only happening on some restarts/startups?

The ASMedia drivers that I've seen the most complaining about are their USB 3.1 drivers ... not as much 'noise' concerning the controller driver (although for Windows 10 that might vary)... Were the controller drivers WHQL for Windows 10? or something earlier? If a recent Windows 10 driver is available (that you haven't tried yet) give it a go....

I imagine the controller drivers might figure in to the problem - I/O performance is generally at the root of audio/video lag/glitching.

I noticed in an older post a fellow moved from an ASMedia controller driver to a "JMicron" Sata controller driver (not sure that your board is the same as his, though)
Solved Asmedia Sata Host Controller driver for Asus MOB - Windows 10 Forums

And --- just for the sake of thoroughness: I forgot to mention a possible source of audio issues in Windows 10 ... some report issues with the Game DVR bar in the Windows 10 XBox app. Truthfully, I'm not sure of its resource usage - but if you happen to be certain that you're unlikely to need it, you can disable it - and test to see if there's any difference (and re-enable it if you don't see any improvement).
Game DVR and Game Bar - Enable or Disable in Windows 10 - Windows 10 Forums

I'll stay tuned . . .
Click to expand...


Ok I like this idea. I am going to try and wait until the problem reproduces itself again, then try a totally different driver. The one I have is the latest asus version and it says windows 10 64 compatible. Trying a totally different SATA driver might be the ticket. Will keep you updated. Thank You!
 
wfdots2 said:
OldGrayGary said:
Hi again


Is the problem still only happening on some restarts/startups?

The ASMedia drivers that I've seen the most complaining about are their USB 3.1 drivers ... not as much 'noise' concerning the controller driver (although for Windows 10 that might vary)... Were the controller drivers WHQL for Windows 10? or something earlier? If a recent Windows 10 driver is available (that you haven't tried yet) give it a go....

I imagine the controller drivers might figure in to the problem - I/O performance is generally at the root of audio/video lag/glitching.

I noticed in an older post a fellow moved from an ASMedia controller driver to a "JMicron" Sata controller driver (not sure that your board is the same as his, though)
Solved Asmedia Sata Host Controller driver for Asus MOB - Windows 10 Forums

And --- just for the sake of thoroughness: I forgot to mention a possible source of audio issues in Windows 10 ... some report issues with the Game DVR bar in the Windows 10 XBox app. Truthfully, I'm not sure of its resource usage - but if you happen to be certain that you're unlikely to need it, you can disable it - and test to see if there's any difference (and re-enable it if you don't see any improvement).
Game DVR and Game Bar - Enable or Disable in Windows 10 - Windows 10 Forums

I'll stay tuned . . .
Click to expand...


Ok I like this idea. I am going to try and wait until the problem reproduces itself again, then try a totally different driver. The one I have is the latest asus version and it says windows 10 64 compatible. Trying a totally different SATA driver might be the ticket. Will keep you updated. Thank You!
Click to expand...

OK the problem is back: I can't find this JMicron driver or an alternative driver: is there any chance you could point me in the right direction for this? Thank you!
 
Yes as soon as I uninstalled the Asmedia driver, the problem became persistant and now Storport and Miniport are causing the lag. This is after windows 10 installed a generic SATA driver.
 
Hi again


See what happens if you reinstall the latest Intel Rapid Storage drivers, and test things. If not better (or no difference), try the latest WHQL driver for the ASMedia Controller (you mentioned you've tried the beta 3.1.9 ... I remember that 3.1.6 was WHQL, but I'm not sure if there's something newer in between those two). Then test again.

Is it still true that it shows up mostly after the slower boots? I wonder if something is having trouble loading in ... Hm... just to see: check in Event Viewer, especially the Administrative Events - and see what errors look linked to the current troubles. You can save and post the Event log here if you'd like: open Event Viewer, select "Custom Views" (on the left-hand side) then right-click "Administrative Events" and select "Save All Events in Custom View as" and then select the file format ".evtx". You can upload that file here in this thread.

I'm also curious if you have the giant 2 TB drive actively indexing it's contents much - that would likely cause a fair amount of background I/O. You can check in "Indexing Options" in the Control Panel. I'm also guessing that it's possible that Norton scans any file that is getting accessed in your system in real-time: so that if files on all three hard drives are being indexed often, then they might also be getting scanned often. If nothing else helps after constant juggling of indexing options and driver versions, it might be worth a try to remove Norton 360 (as a test --- you can always reinstall it again) and let Windows Defender provide some minimal protection while testing.

And, since SATA ports and controllers seem to be a recurring theme in our investigation, have a look at an old thread that involves interesting issues with SATA and USB traffic --- especially note the comments by Cluberti near the end of the thread:
https://www.sysnative.com/forums/wi...efaults-fresh-install-usbport-sys-others.html

Let's see what turns up
 
OldGrayGary said:
Hi again


See what happens if you reinstall the latest Intel Rapid Storage drivers, and test things. If not better (or no difference), try the latest WHQL driver for the ASMedia Controller (you mentioned you've tried the beta 3.1.9 ... I remember that 3.1.6 was WHQL, but I'm not sure if there's something newer in between those two). Then test again.

Is it still true that it shows up mostly after the slower boots? I wonder if something is having trouble loading in ... Hm... just to see: check in Event Viewer, especially the Administrative Events - and see what errors look linked to the current troubles. You can save and post the Event log here if you'd like: open Event Viewer, select "Custom Views" (on the left-hand side) then right-click "Administrative Events" and select "Save All Events in Custom View as" and then select the file format ".evtx". You can upload that file here in this thread.

I'm also curious if you have the giant 2 TB drive actively indexing it's contents much - that would likely cause a fair amount of background I/O. You can check in "Indexing Options" in the Control Panel. I'm also guessing that it's possible that Norton scans any file that is getting accessed in your system in real-time: so that if files on all three hard drives are being indexed often, then they might also be getting scanned often. If nothing else helps after constant juggling of indexing options and driver versions, it might be worth a try to remove Norton 360 (as a test --- you can always reinstall it again) and let Windows Defender provide some minimal protection while testing.

And, since SATA ports and controllers seem to be a recurring theme in our investigation, have a look at an old thread that involves interesting issues with SATA and USB traffic --- especially note the comments by Cluberti near the end of the thread:
https://www.sysnative.com/forums/wi...efaults-fresh-install-usbport-sys-others.html

Let's see what turns up
Click to expand...

I am going to try and figure out how to upload this: View attachment Log 1.zip

OK I had to zip it before I could upload the log. Sorry.

I am going to sort through this other post now. Thank you.
 
I had 3 days without the problem, booted up again this afternoon. It took about 3 times as long to boot so I knew the problem would be there. Again ran latencyMon. Storport and miniport were the problem again. Will try to install 3.1.6 of the asmedia sata driver.
 
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.
 
OldGrayGary said:
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.
Click to expand...


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!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top