Hallo ihr lieben, ich hätte da eine Frage an die Profis. Win 10 läuft prinzipiell recht gut.
Jedoch ist mein Ereignisprotokoll voll mit minütlichen Fehlern und Warnungen. Seit August letzten Jahres 28000 Einträge.
Zweimal in Folge hatte ich Nachts wärend des 3D Rendervorgangs einen Absturz.
Meine Vermutung liegt auf das Speichern der Bilder auf der SSD. Im Dump heisst es "storposrt.sys" und "ntoskrnl.exe" seien schuld.
Die ganzen Fehler im Ereignisprotokoll sind vermutlich garnicht garvierend, aber ich habe sie angehangen, vielleicht erleichtern sie die Fehlersuche. LatencyMon habe ich mal laufen gelassen, da lief alles im grünen Bereich im Ruhestand, aber sobald ich den Intel CPU Test startete oder auch eine Anwendung wie Photoshop öffne, wurde aus dem grünen Bereich eine Warnung (siehe unten).
Der Rechner braucht zum hochfahren sehr lange, um die 3-4 Minuten. Viele Arbeitsprogramme sind installiert. Bis auf Avira und comodo aber keine lästigen tools. System ist frei von Adware und Müll.
Treiberzustand:
Ich habe das aktuelle Intel Chipset Paket installiert. Aktuelle Grafiktreiber. Und Slimdriver sagt alles wäre aktuell.
Mein System in Kurzfassung:
Intel i7 3930k | Thermalright hr-02 macho | Asus P9x79 Pro | 32 GB G.Skill CL10 | be'quiet dark power pro 650w 80+gold | 1TB Samsung Evo SSD(sehr neu) | 250GB Samsung Evo SSD | 250GB OCZ SSD(älter) | 3TB Samsung HD | Logitech G430 & BCC950 & K740 & G502 & G700 | NZXT Phantom | Wacom Intuos 4L Tablet | Logitech BCC950 Kamera
Zotac GTX980 ti AMP! Extreme | 27" EIZO EV2736W | 27" Acer gsync XB270HUbprz
Bericht von LatencyMon:
Solltet ihr noch iregndwas an Infos brauchen oder Tools die laufen lassen muss, einfach sagen, bekommt ihr.
Vielen Dank schonmal fürs lesen.
Jedoch ist mein Ereignisprotokoll voll mit minütlichen Fehlern und Warnungen. Seit August letzten Jahres 28000 Einträge.
Zweimal in Folge hatte ich Nachts wärend des 3D Rendervorgangs einen Absturz.
Meine Vermutung liegt auf das Speichern der Bilder auf der SSD. Im Dump heisst es "storposrt.sys" und "ntoskrnl.exe" seien schuld.
Die ganzen Fehler im Ereignisprotokoll sind vermutlich garnicht garvierend, aber ich habe sie angehangen, vielleicht erleichtern sie die Fehlersuche. LatencyMon habe ich mal laufen gelassen, da lief alles im grünen Bereich im Ruhestand, aber sobald ich den Intel CPU Test startete oder auch eine Anwendung wie Photoshop öffne, wurde aus dem grünen Bereich eine Warnung (siehe unten).
Der Rechner braucht zum hochfahren sehr lange, um die 3-4 Minuten. Viele Arbeitsprogramme sind installiert. Bis auf Avira und comodo aber keine lästigen tools. System ist frei von Adware und Müll.
Treiberzustand:
Ich habe das aktuelle Intel Chipset Paket installiert. Aktuelle Grafiktreiber. Und Slimdriver sagt alles wäre aktuell.
Mein System in Kurzfassung:
Intel i7 3930k | Thermalright hr-02 macho | Asus P9x79 Pro | 32 GB G.Skill CL10 | be'quiet dark power pro 650w 80+gold | 1TB Samsung Evo SSD(sehr neu) | 250GB Samsung Evo SSD | 250GB OCZ SSD(älter) | 3TB Samsung HD | Logitech G430 & BCC950 & K740 & G502 & G700 | NZXT Phantom | Wacom Intuos 4L Tablet | Logitech BCC950 Kamera
Zotac GTX980 ti AMP! Extreme | 27" EIZO EV2736W | 27" Acer gsync XB270HUbprz
Bericht von LatencyMon:
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:10:48 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: WORKSTATION
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., P9X79 PRO
CPU: GenuineIntel Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Logical processors: 12
Processor groups: 1
RAM: 32709 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3363 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): 837,907266
Average measured interrupt to process latency (µs): 3,722855
Highest measured interrupt to DPC latency (µs): 834,862545
Average measured interrupt to DPC latency (µs): 0,942793
_________________________________________________________________________________________________________
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): 133,037169
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,064263
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,070478
ISR count (execution time <250 µs): 317546
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): 6013,706809
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 365.10 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,039048
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 365.10 , NVIDIA Corporation
Total time spent in DPCs (%) 0,126554
DPC count (execution time <250 µs): 2855896
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 12
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 4
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: rundll32.exe
Total number of hard pagefaults 865
Hard pagefault count of hardest hit process: 350
Highest hard pagefault resolution time (µs): 459212,999108
Total time spent in hard pagefaults (%): 0,006130
Number of processes hit: 6
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 9,125617
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 241,671127
CPU 0 DPC total execution time (s): 1,819135
CPU 0 DPC count: 1717463
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 19,710691
CPU 1 ISR highest execution time (µs): 133,037169
CPU 1 ISR total execution time (s): 4,997595
CPU 1 ISR count: 185602
CPU 1 DPC highest execution time (µs): 6013,706809
CPU 1 DPC total execution time (s): 4,454759
CPU 1 DPC count: 477381
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 8,311290
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 176,981861
CPU 2 DPC total execution time (s): 0,366240
CPU 2 DPC count: 71942
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 7,077286
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 99,520666
CPU 3 DPC total execution time (s): 0,037923
CPU 3 DPC count: 16209
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 10,495058
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): 184,257508
CPU 4 DPC total execution time (s): 0,095404
CPU 4 DPC count: 25582
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 10,932537
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): 156,079691
CPU 5 DPC total execution time (s): 0,059116
CPU 5 DPC count: 18772
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 12,158852
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): 259,834671
CPU 6 DPC total execution time (s): 0,116504
CPU 6 DPC count: 33341
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 8,177317
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): 108,694618
CPU 7 DPC total execution time (s): 0,045601
CPU 7 DPC count: 16489
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 9,083419
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 174,377639
CPU 8 DPC total execution time (s): 0,080738
CPU 8 DPC count: 25592
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 13,203460
CPU 9 ISR highest execution time (µs): 89,006244
CPU 9 ISR total execution time (s): 0,483282
CPU 9 ISR count: 131944
CPU 9 DPC highest execution time (µs): 212,870651
CPU 9 DPC total execution time (s): 2,612330
CPU 9 DPC count: 405107
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 10,266132
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 115,913173
CPU 10 DPC total execution time (s): 0,098188
CPU 10 DPC count: 28822
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 9,251352
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 106,476360
CPU 11 DPC total execution time (s): 0,055872
CPU 11 DPC count: 19213
_________________________________________________________________________________________________________
Solltet ihr noch iregndwas an Infos brauchen oder Tools die laufen lassen muss, einfach sagen, bekommt ihr.
Vielen Dank schonmal fürs lesen.
Anhänge
Zuletzt bearbeitet von einem Moderator: