K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 20, 2018 #1 I have audio cracking and everything laggs also the monitor frezzes for a second I let Latencymon run for 10 minutes. my pc specs: Motherboard: Msi x370 pro carbon GPU: Msi gtx 1060 6gb gaming x CPU: Amd ryzen 5 2600 SSD: 250GB Samsung 860 HDD: 1000GB Toshiba 500 Watt be quiet! Pure Power 10 Non-Modular 80+ Silver Im running on windows 10 my bios is also the newest
I have audio cracking and everything laggs also the monitor frezzes for a second I let Latencymon run for 10 minutes. my pc specs: Motherboard: Msi x370 pro carbon GPU: Msi gtx 1060 6gb gaming x CPU: Amd ryzen 5 2600 SSD: 250GB Samsung 860 HDD: 1000GB Toshiba 500 Watt be quiet! Pure Power 10 Non-Modular 80+ Silver Im running on windows 10 my bios is also the newest
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 20, 2018 #2 Hi Kaya, How often do the audio glitches and freezing occur? Did it take 10 minutes for LatencyMon to finally register that high of a DPC processing time from the storage driver or is it constantly happening?
Hi Kaya, How often do the audio glitches and freezing occur? Did it take 10 minutes for LatencyMon to finally register that high of a DPC processing time from the storage driver or is it constantly happening?
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 20, 2018 #4 Are your drive(s) set to go to sleep after a certain amount of inactivity?
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 20, 2018 #6 Power & Sleep -> Additional power settings -> Change plan settings -> Change advanced power settings should get you to a dialog where you can check and change sleep settings for the hard disks.
Power & Sleep -> Additional power settings -> Change plan settings -> Change advanced power settings should get you to a dialog where you can check and change sleep settings for the hard disks.
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 20, 2018 #7 No they arent set to go to sleep after a limited time there is only a zero
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 20, 2018 #8 We could try capturing a trace using the built-in Windows 10 wpr command. You'd start it, let it run in the background using the system as you normally would until the glitch happened, and then stop wpr to save the trace to a file. To do so, open a command prompt with administrator privileges. Then run the command: Code: wpr -start GeneralProfile Leave the command window open while you use the computer and when the glitch happens switch back to the command window and run: Code: wpr -stop d:\general.etl We'd then need to try and analyze the general.etl file so you'd need to make it available. They can get rather large so you'd want to zip the file and make it available via a cloud drive or file sharing service if you'd like us to look at it.
We could try capturing a trace using the built-in Windows 10 wpr command. You'd start it, let it run in the background using the system as you normally would until the glitch happened, and then stop wpr to save the trace to a file. To do so, open a command prompt with administrator privileges. Then run the command: Code: wpr -start GeneralProfile Leave the command window open while you use the computer and when the glitch happens switch back to the command window and run: Code: wpr -stop d:\general.etl We'd then need to try and analyze the general.etl file so you'd need to make it available. They can get rather large so you'd want to zip the file and make it available via a cloud drive or file sharing service if you'd like us to look at it.
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 21, 2018 #10 I only get a error is this normal?
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 21, 2018 #11 The command console needs to be started with Administrator privileges. Assuming you're using the Start menu you'd need to right-click the Command Prompt icon and select "Run as administrator".
The command console needs to be started with Administrator privileges. Assuming you're using the Start menu you'd need to right-click the Command Prompt icon and select "Run as administrator".
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 22, 2018 #12 This is the general.etl file https://1drv.ms/u/s!AuaBBXquo5mMig4VbCxlWGfnf6M8 Its a onedrive link
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 22, 2018 #13 The problem also appears when i start programs like CrystalDiskInfo But my hardware is not broken or?
The problem also appears when i start programs like CrystalDiskInfo But my hardware is not broken or?
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 22, 2018 #14 Have you used Samsung Magician to check the health of your SSD and also for firmware updates? There is definitely something odd going on with storport.sys but I can't tell which drive, yet.
Have you used Samsung Magician to check the health of your SSD and also for firmware updates? There is definitely something odd going on with storport.sys but I can't tell which drive, yet.
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 22, 2018 #15 Samsung Magician shows that my ssd is okay The screenshot is german but everything is Well also the firmware version is the newest but i get the error VID 1022 at system Compatibility
Samsung Magician shows that my ssd is okay The screenshot is german but everything is Well also the firmware version is the newest but i get the error VID 1022 at system Compatibility
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 22, 2018 #16 It also looks like you have plenty of free space on the system drive. Please run the Sysnative BSOD Collection App and post the zip it creates. It might have clues in the event logs collected. You mentioned that you can recreate the issue by running CrystalDiskInfo. It might be worth disconnecting the Toshiba HDD temporarily to see if the glitch stops when the Toshiba is out of the equation. I don't think Toshiba has a disk testing utility but I've usually been able to use Seagate SeaTools for Windows on Toshiba drives. If you haven't done so already, please do a long test of your Toshiba HDD using SeaTools if that seems appropriate based on the above.
It also looks like you have plenty of free space on the system drive. Please run the Sysnative BSOD Collection App and post the zip it creates. It might have clues in the event logs collected. You mentioned that you can recreate the issue by running CrystalDiskInfo. It might be worth disconnecting the Toshiba HDD temporarily to see if the glitch stops when the Toshiba is out of the equation. I don't think Toshiba has a disk testing utility but I've usually been able to use Seagate SeaTools for Windows on Toshiba drives. If you haven't done so already, please do a long test of your Toshiba HDD using SeaTools if that seems appropriate based on the above.
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 22, 2018 #17 Can you post the link for Seagate Seatools here please? Where can i find the zip?
K Kaya Active member Joined Oct 20, 2018 Posts 33 Oct 22, 2018 #18 I tested my hdd with HD Tune website Hd tune pro
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 22, 2018 #19 Making notes, really, but for anyone interested - in the attached screenshot I've zoomed into the glitch. The graphs show that core 0 was stuck at DPC level for around 100 milliseconds while trying to process RaidpAdapterTimerDpcRoutine DPC(s). 10 milliseconds is enough to cause a noticeable audio glitch. They also show all the other cores basically doing nothing that entire time. They all seem to be more or less waiting for core 0 to finish the DPCs.
Making notes, really, but for anyone interested - in the attached screenshot I've zoomed into the glitch. The graphs show that core 0 was stuck at DPC level for around 100 milliseconds while trying to process RaidpAdapterTimerDpcRoutine DPC(s). 10 milliseconds is enough to cause a noticeable audio glitch. They also show all the other cores basically doing nothing that entire time. They all seem to be more or less waiting for core 0 to finish the DPCs.
C cwsink Sysnative Staff, BSOD Kernel Dump Expert Staff member Joined Apr 3, 2017 Posts 520 Oct 22, 2018 #20 SeaTools for Windows The output for the Sysnative app should be in the Documents folder. Steps 1 and 2 on this page describe its use.
SeaTools for Windows The output for the Sysnative app should be in the Documents folder. Steps 1 and 2 on this page describe its use.