 |
 |
 |
 |
 |
 |
27.10.2015, 08:10
|
#1
|
|||
|
Рандомные мини-подвисания в Windows 10
Если посмотрите видео, то прекрасно видно слышно, что периодически такой звук появляется как будто зависло. У меня нечто подобное на Windows 10. Зависон подобный происходит только примерно 2 раза в день, при просмотре видео, аудио, ютуба или в играх. Подвисон очень быстрый меньше половины секунды и всего один раз (то есть не как у того парня в видео много раз и постоянно). Просто напрягает довольно сильно когда слушаешь музыку или смотришь видео и тут бац и звук БЗЗЗЗЗЗЗЗЗЗЗЗЗЗ, а потом сразу же нормально все. Возможно, кто-то сталкивался с подобным и знает решение проблемы? Дрова вроде все ставил новые. В семерке ничего подобного не было.
__________________
  |
|
27.10.2015, 10:41
|
#2
|
||||
|
Re: Рандомные мини-подвисания в Windows 10
Quote:
Дальше уже шаманство, попытки отрубить энергосбережение, встроенную видюху и тд.
__________________
|
|
28.10.2015, 08:22
|
#3
|
||||
|
Re: Рандомные мини-подвисания в Windows 10
По части заиканий звука очень много нареканий на win10, хде-то майки накосячили
 Возможно грядущее обновление поможет... Quote:
Советов много есть разных, дрова от ЗК, дрова на чипсет, и даже переезд на enterprise версию. Например http://forums.overclockers.ru/viewto...8284#p13278284
__________________
 Last edited by Улисс; 28.10.2015 at 08:57. |
|
29.10.2015, 13:26
|
#7
|
|||
|
Re: Рандомные мини-подвисания в Windows 10
Ну там куда ссылочка ведет там 679 страниц. А дрова на сетевую встроенную и звуковую встроенную я уже пробовал переустанавливать самые последние. Или в чем его способ заключается? В том чтобы удалить дрова для лан, звука и сата и поставить их через диспетчер устройств? Чтобы он сам их нашел в интернете?
__________________
|
|
29.10.2015, 14:12
|
#9
|
|||
|
Re: Рандомные мини-подвисания в Windows 10
Мне не показывает рисунок, так как требует авторизации. Сейчас попробую зарегаться тогда у них.
Добавлено через 9 минут Ммм хоть убей не вижу у себя никакого упомнинаия слова chipset. 
__________________
Last edited by Nature_renamed_562435_14022021; 29.10.2015 at 14:12. Reason: Добавлено сообщение |
|
29.10.2015, 14:18
|
#10
|
|||
|
Re: Рандомные мини-подвисания в Windows 10
В других разделах не вижу, в системных устройствах же должно быть вроде. Материнка если что SABERTOOTH 990FX R2.0 . Так что чипсет видимо AMD 990FX ? Если да, то где можно посмотреть или скачать конкретно под него.
__________________
|
|
29.10.2015, 14:23
|
#11
|
||||
|
Re: Рандомные мини-подвисания в Windows 10
Quote:
Дрова на чипсет вообще устанавливал? В комплекте с мамкой должны идти (ну или на сайте производителя мамки)...
__________________
|
|
01.11.2015, 16:52
|
#19
|
||||
|
Re: Рандомные мини-подвисания в Windows 10
Quote:
|
|
02.11.2015, 23:48
|
#22
|
|||
|
Re: Рандомные мини-подвисания в Windows 10
Попробовал щас проверить с помощью программы LatencyMon и вот что выдало.
 Варианты? (почему написано виндовс 8 хз). OS version: Windows 8 , 6.2, build: 9200 (x64) Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0 CPU: AuthenticAMD AMD FX-8370 Eight-Core Processor Logical processors: 8 Processor groups: 1 RAM: 16282 MB total __________________________________________________ __________________________________________________ _____ CPU SPEED __________________________________________________ __________________________________________________ _____ Reported CPU speed: 4014 MHz Measured CPU speed: 1 MHz (approx.) Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. __________________________________________________ __________________________________________________ _____ MEASURED INTERRUPT TO USER PROCESS LATENCIES __________________________________________________ __________________________________________________ _____ The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event. Highest measured interrupt to process latency (µs): 660,286954 Average measured interrupt to process latency (µs): 8,065632 Highest measured interrupt to DPC latency (µs): 656,459943 Average measured interrupt to DPC latency (µs): 3,431407 __________________________________________________ __________________________________________________ _____ REPORTED ISRs __________________________________________________ __________________________________________________ _____ Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal. Highest ISR routine execution time (µs): 228,504235 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 0,096160 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0,121507 ISR count (execution time <250 µs): 607856 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-999 µs): 0 ISR count (execution time 1000-1999 µs): 0 ISR count (execution time 2000-3999 µs): 0 ISR count (execution time >=4000 µs): 0 __________________________________________________ __________________________________________________ _____ REPORTED DPCs __________________________________________________ __________________________________________________ _____ DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution. Highest DPC routine execution time (µs): 67681,722471 Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Highest reported total DPC routine time (%): 0,058838 Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp. Total time spent in DPCs (%) 0,346429 DPC count (execution time <250 µs): 5124005 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 1347 DPC count (execution time 1000-1999 µs): 0 DPC count (execution time 2000-3999 µs): 0 DPC count (execution time >=4000 µs): 0 __________________________________________________ __________________________________________________ _____ REPORTED HARD PAGEFAULTS __________________________________________________ __________________________________________________ _____ Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution. NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit. Process with highest pagefault count: avastsvc.exe Total number of hard pagefaults 302 Hard pagefault count of hardest hit process: 73 Highest hard pagefault resolution time (µs): 59557,17140 Total time spent in hard pagefaults (%): 0,003765 Number of processes hit: 17 __________________________________________________ __________________________________________________ _____ PER CPU DATA __________________________________________________ __________________________________________________ _____ CPU 0 Interrupt cycle time (s): 82,307281 CPU 0 ISR highest execution time (µs): 228,504235 CPU 0 ISR total execution time (s): 9,127338 CPU 0 ISR count: 557733 CPU 0 DPC highest execution time (µs): 67681,722471 CPU 0 DPC total execution time (s): 24,762646 CPU 0 DPC count: 4746870 __________________________________________________ __________________________________________________ _____ CPU 1 Interrupt cycle time (s): 31,308239 CPU 1 ISR highest execution time (µs): 203,113353 CPU 1 ISR total execution time (s): 0,934963 CPU 1 ISR count: 49191 CPU 1 DPC highest execution time (µs): 504,718984 CPU 1 DPC total execution time (s): 1,387932 CPU 1 DPC count: 123986 __________________________________________________ __________________________________________________ _____ CPU 2 Interrupt cycle time (s): 23,317840 CPU 2 ISR highest execution time (µs): 124,397359 CPU 2 ISR total execution time (s): 0,007984 CPU 2 ISR count: 882 CPU 2 DPC highest execution time (µs): 200,794968 CPU 2 DPC total execution time (s): 0,484123 CPU 2 DPC count: 59098 __________________________________________________ __________________________________________________ _____ CPU 3 Interrupt cycle time (s): 25,374342 CPU 3 ISR highest execution time (µs): 156,015197 CPU 3 ISR total execution time (s): 0,000531 CPU 3 ISR count: 50 CPU 3 DPC highest execution time (µs): 216,456153 CPU 3 DPC total execution time (s): 0,281752 CPU 3 DPC count: 28396 __________________________________________________ __________________________________________________ _____ CPU 4 Interrupt cycle time (s): 21,901837 CPU 4 ISR highest execution time (µs): 0,0 CPU 4 ISR total execution time (s): 0,0 CPU 4 ISR count: 0 CPU 4 DPC highest execution time (µs): 204,896861 CPU 4 DPC total execution time (s): 0,531352 CPU 4 DPC count: 53133 __________________________________________________ __________________________________________________ _____ CPU 5 Interrupt cycle time (s): 24,183633 CPU 5 ISR highest execution time (µs): 0,0 CPU 5 ISR total execution time (s): 0,0 CPU 5 ISR count: 0 CPU 5 DPC highest execution time (µs): 227,807673 CPU 5 DPC total execution time (s): 0,605562 CPU 5 DPC count: 51899 __________________________________________________ __________________________________________________ _____ CPU 6 Interrupt cycle time (s): 14,018465 CPU 6 ISR highest execution time (µs): 0,0 CPU 6 ISR total execution time (s): 0,0 CPU 6 ISR count: 0 CPU 6 DPC highest execution time (µs): 228,360239 CPU 6 DPC total execution time (s): 0,350081 CPU 6 DPC count: 32929 __________________________________________________ __________________________________________________ _____ CPU 7 Interrupt cycle time (s): 14,799457 CPU 7 ISR highest execution time (µs): 0,0 CPU 7 ISR total execution time (s): 0,0 CPU 7 ISR count: 0 CPU 7 DPC highest execution time (µs): 196,004983 CPU 7 DPC total execution time (s): 0,309456 CPU 7 DPC count: 29042 __________________________________________________ __________________________________________________ _____
__________________
|
