Message boards :
Number crunching :
Stability problems in Windows 8
Message board moderation
Author | Message |
---|---|
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Hello, I ran this computer http://setiathome.berkeley.edu/show_host_detail.php?hostid=3806561 for roughly 6 monts with one GPU without any significant issues once I removed the other GPU last spring. Now I added another 670 to the stack and over time I get some DPC stalls again. Now even ntoskrnl.exe. The mouse and GPU freezes periodically for a second or so. The triggering combination seems to be: 1) running AP GPU 2) fully loaded CPU 3) Internet Explorer running 4) Windows 8 OS 5) at least 2 GTX cards installed. Either there is a problem with the OS or then there might be some problem with the Motherboard. All the GPU's work fine alone or in other computers in multiple GPU setups. Anyone experiencing similar problems with similar setup? Event Log: Error 19.10.2013 11:01:12 nvlddmkm 14 None Error 18.10.2013 23:36:15 nvlddmkm 14 None Error 18.10.2013 17:32:58 nvlddmkm 14 None Error 16.10.2013 5:36:50 nvlddmkm 14 None Error 21.8.2013 7:24:26 nvlddmkm 14 None Error 10.3.2013 12:42:18 nvlddmkm 14 None Error 10.3.2013 11:21:47 nvlddmkm 14 None Error 10.3.2013 11:17:55 nvlddmkm 14 None Error 9.3.2013 22:40:28 nvlddmkm 14 None Error 9.3.2013 19:16:05 nvlddmkm 14 None Warning 19.10.2013 11:04:03 Display 4101 None Warning 19.10.2013 11:03:53 Display 4101 None Warning 19.10.2013 11:03:49 Display 4101 None Warning 19.10.2013 11:01:53 Display 4101 None Warning 19.10.2013 11:01:38 Display 4101 None Warning 19.10.2013 11:01:25 Display 4101 None Warning 19.10.2013 9:11:51 Display 4101 None Warning 16.10.2013 9:06:08 Display 4101 None Warning 16.10.2013 9:06:02 Display 4101 None Warning 16.10.2013 9:05:13 Display 4101 None Warning 16.10.2013 8:46:24 Display 4101 None Warning 16.10.2013 8:44:48 Display 4101 None Warning 16.10.2013 8:39:35 Display 4101 None Warning 16.10.2013 8:33:51 Display 4101 None Warning 16.10.2013 8:20:04 Display 4101 None Warning 16.10.2013 8:00:56 Display 4101 None Warning 16.10.2013 7:44:30 Display 4101 None Warning 16.10.2013 7:32:44 Display 4101 None Warning 16.10.2013 7:20:43 Display 4101 None Warning 16.10.2013 7:13:45 Display 4101 None Warning 16.10.2013 7:02:21 Display 4101 None Warning 16.10.2013 6:41:12 Display 4101 None Warning 16.10.2013 6:29:42 Display 4101 None Warning 16.10.2013 6:18:23 Display 4101 None Warning 16.10.2013 6:04:23 Display 4101 None Warning 16.10.2013 5:52:40 Display 4101 None Warning 16.10.2013 5:40:07 Display 4101 None Warning 27.9.2013 20:08:27 Display 4101 None Warning 27.9.2013 20:08:19 Display 4101 None Warning 27.9.2013 20:08:15 Display 4101 None Warning 21.8.2013 21:51:59 Display 4101 None Warning 21.8.2013 18:04:05 Display 4101 None Warning 21.8.2013 17:28:25 Display 4101 None Warning 21.8.2013 15:58:38 Display 4101 None Warning 21.8.2013 12:42:57 Display 4101 None Warning 21.8.2013 9:31:18 Display 4101 None Warning 10.3.2013 14:14:05 Display 4101 None Warning 10.3.2013 13:19:49 Display 4101 None Warning 10.3.2013 9:24:17 Display 4101 None Warning 10.3.2013 9:18:01 Display 4101 None |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
The triggering combination seems to be: Did you already tried to free 1-2 CPU cores? (i.e. to run 1-2 less CPU tasks) (as I understand "fully loaded CPU" means you run 8 CPU tasks?) Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0 |
Now I added another 670 to the stack and over time I get some DPC stalls again. Is the PSU up to par? Gruß Gundolf |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Power Supply is Corsair 650 HX 80 Plus Silver..... Actual consumption is always below 400W. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Meaning CPU load is 95-100%. 4 cores for CPU and 4 for GPU. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Have you tried installing 8.1 yet? It installs a completely new OS. If there is something wrong with your system, that should fix it. You might want to run Malwarebytes first though, I've discovered Window's 8 built-in Malware protection isn't all that great... |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Meaning CPU load is 95-100%. 4 cores for CPU and 4 for GPU. How many AP instances are you running on your GPU`s ? With each crime and every kindness we birth our future. |
Bojan Send message Joined: 28 Feb 04 Posts: 15 Credit: 12,006,153 RAC: 4 |
Meaning CPU load is 95-100%. 4 cores for CPU and 4 for GPU. Probably you running 2 AP task on each GPU, thats OK, but isnt OK that your CPU is on 100% all the time. So, free one more cpu core that your system will be stable when you running all AP task. When no AP task would available you can go easely with max 6 CPU core. EDIT: can anyone tell me how to change forum language to english becuse i cant see now a half function here and some words are wrong translated...thanks. |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
A 650PSU is not enough for a fully loaded i7-3770K CPU + 2x670 (even at stock speeds), it could even works and the total mean consumption could be at 400W but the problem could apears only then your GPU/CPU need's an aditional spike in the 12V power rail. A single 670 (with no OC) needs a minimim of a 500WPSU and uses up to 170W, that´s "could be" the source of your problem. For a 2x670 GPU hosts you must go for no less than 750W Gold PSU or even more if you going to use your hosts at full capacity (24/7 crunching). A 650W PSU could work but the question is for who long? and wierds things happens when the PSU can´t handle the GPU power hungry. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Power Supply is Corsair 650 HX 80 Plus Silver..... Actual consumption is always below 400W. I'd put your system details into the Corsair Power Supply finder, and the Asus Power Supply Calculator, when i tried your system details in the Corsair version it said 750Watt minimum, while the Asus version said 900Watts (assuming two memory sticks, a HD and a DVD writer, two USB devices and two fans) http://www.corsair.com/us/learn_n_explore/?psu=yes http://support.asus.com/powersupply.aspx Claggy |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
EDIT: can anyone tell me how to change forum language to english becuse i cant see now a half function here and some words are wrong translated...thanks. Go to front page of website http://setiathome.berkeley.edu/index.php Main dark-blue navigation bar, right hand side, below 'Goodsearch' link. Takes you to Languages. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
My prime suspect is now on some of the PCI Express lanes not functioning properly. The MB is an ASRock WS. So if I use a certain setup that invokes a "corrupt lane" I get stalls etc. The reason for this is that I found setup with populating: PCIe1 and PCIe4, with the speeds PCI-E x16 3.0 and PCI-E x4 2.0 respectively. functional for over 24 hours without problems. The following setups have proven problems. PCIe1 and PCIe3, with the speeds PCI-E x8 3.0 and PCI-E x8 3.0 respectively PCIe1 and PCIe5, with the speeds PCI-E x16 3.0 and PCI-E x16 3.0 respectively PCIe1 and PCIe7, has not been verified, yet. --------------------------------- From the user manual: 2.6 Expansion Slots (PCI Express Slots) There are 7 PCI Express slots on this motherboard. PCIE slots: PCIE1 / PCIE5 (PCIE 3.0 x16 slot) is used for PCI Express x16 lane width graphics cards, or to install PCI Express graphics cards to support CrossFireXTM or SLITM function. PCIE3 / PCIE7 (PCIE 3.0 x16 slot) is used for PCI Express x8 lane width graphics cards, or to install PCI Express graphics cards to support CrossFireXTM or SLITM function. PCIE2 (PCIE 3.0 x16 slot) is used for PCI Express x16 lane width graphics cards. PCIE4 (PCIE 2.0 x16 slot) is used for PCI Express x4 lane width graphics cards or ASRock Game Blaster. PCIE6 (PCIE 2.0 x1 slot) is used for a PCI Express x1 lane width card, such as a Gigabit LAN card, SATA2 card, etc. PCIE Slot Configurations PCIE1 PCIE2 PCIE3 PCIE5 PCIE7 Single Graphics Card N/A x16 N/A N/A N/A Two Graphics Cards in x16 N/A N/A x16 N/A CrossFireXTM or SLITM Mode Three Graphics Cards in x8 N/A x8 x16 N/A 3-Way CrossFireXTM or 3-Way SLITM Mode Four Graphics Cards in x8 N/A x8 x8 x8 4-Way CrossFireXTM or 4-Way SLITM Mode 1. In single VGA card mode, it is recommended to install a PCI Express x16 graphics card in the PCIE2 slot. 2. PCIE1, PCIE3, PCIE5 and PCIE7 slots will be disabled if PCIE2 slot is occupied. 3. In CrossFireXTM mode or SLITM mode, please install the PCI Express x16 graphics cards in PCIE1 and PCIE5 slots. Both these two slots will work at x16 bandwidth. 4. In 3-Way CrossFireXTM or 3-Way SLITM mode, please install the PCI Express x16 graphics cards in PCIE1, PCIE3 and PCIE5 slots. PCIE1 and PCIE3 will work at x8 bandwidth, while PCIE5 works at x16 bandwidth. 5. In 4-Way CrossFireXTM or 4-Way SLITM mode, please install the PCI Express x16 graphics cards in PCIE1, PCIE3, PCIE5 and PCIE7 slots. All these four slots will work at x8 bandwidth. 6. Please connect a chassis fan to the motherboard’s chassis fan connector (CHA_FAN1, CHA_FAN2 or CHA_FAN3) when using multiple graphics cards for better thermal environment. 7. Only PCIE1, PCIE2, PCIE3, PCIE5, PCIE6 and PCIE7 slots support Gen 3 speed. To run the PCI Express in Gen 3 speed, please install an Ivy Bridge CPU. If you install a Sandy Bridge CPU, the PCI Express will run only at PCI Express Gen 2 speed. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
...PCIE1 / PCIE5 (PCIE 3.0 x16 slot) is used for PCI Express x16 lane I've been convinced nVidia has a problem with Windows 8 since I installed Windows 8 and booted to Black Flashing Screens. nVidia just waved their hands and blamed it on M$. Hopefully, Windows 8.1 will fix things... |
ML1 Send message Joined: 25 Nov 01 Posts: 20283 Credit: 7,508,002 RAC: 20 |
Windows 8 and booted to Black Flashing Screens. ... OK... So got to ask... How can you have a 'black' flash? Black on black is still black as in still no colour/light to 'flash' with... (Is that the new blue-screen-of-death but something that can't be seen?? :-( ) Good luck, Martin See new freedom: Mageia Linux Take a look for yourself: Linux Format The Future is what We all make IT (GPLv3) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Windows 8 and booted to Black Flashing Screens. ... Easy. The monitor turns itself off every second or two giving the appearance of 'Flashing' or 'Flickering'. When the monitor is on, all you see is the cursor and a Black Screen. Then it goes off...then on...then off... Google it. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Update: I ran now the 2 GTX670 in PCIe buses 3 and 5. For a long while (week) it seemed stable, but when I got it crunching one Astropulse WU and one Multibeam WU on same GPU I encountered problems. Error 30.10.2013 20:41:58 nvlddmkm 14 None Error 29.10.2013 4:41:41 nvlddmkm 14 None Error 28.10.2013 15:06:11 nvlddmkm 14 None Error 19.10.2013 11:01:12 nvlddmkm 14 None Warning 30.10.2013 21:19:39 Display 4101 None Warning 30.10.2013 21:17:44 Display 4101 None Warning 30.10.2013 21:05:05 Display 4101 None Warning 30.10.2013 20:50:54 Display 4101 None Warning 29.10.2013 11:52:49 Display 4101 None Warning 29.10.2013 11:52:45 Display 4101 None Warning 29.10.2013 11:52:13 Display 4101 None Warning 29.10.2013 11:51:47 Display 4101 None Warning 29.10.2013 11:31:06 Display 4101 None Warning 29.10.2013 11:17:09 Display 4101 None Warning 29.10.2013 10:52:37 Display 4101 None Warning 29.10.2013 10:48:39 Display 4101 None Warning 29.10.2013 10:24:41 Display 4101 None Warning 29.10.2013 9:59:43 Display 4101 None Warning 29.10.2013 9:35:59 Display 4101 None Warning 29.10.2013 9:05:21 Display 4101 None Warning 29.10.2013 8:40:50 Display 4101 None Warning 29.10.2013 8:17:05 Display 4101 None Warning 29.10.2013 6:24:23 Display 4101 None Warning 29.10.2013 4:43:04 Display 4101 None Warning 28.10.2013 16:18:50 Display 4101 None Warning 28.10.2013 16:18:46 Display 4101 None Warning 28.10.2013 16:18:20 Display 4101 None Warning 28.10.2013 16:17:55 Display 4101 None Warning 28.10.2013 15:07:07 Display 4101 None Warning 27.10.2013 14:54:18 Display 4101 None Warning 27.10.2013 14:54:13 Display 4101 None Warning 27.10.2013 14:54:10 Display 4101 None Warning 19.10.2013 11:04:03 Display 4101 None |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Just checked GPU Z: Card 1: has now full 16 lanes of PCIe in use while Card 2: has only 8 lanes. Card 1: EVGA 670 standard, Card 2: EVGA 670 FTW. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Switched the 670 FTW from slot 3 to another machine. Seems to work fine there. Installed another 680 GTX into slot 1 and ran it together with standard GTX 670 in slot 5. Situation went for the worse... _________________________________________________________________________________________________________ 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. Also one or more ISR 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:06 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: XERXES OS version: Windows 8 , 6.2, build: 9200 (x64) Hardware: ASRock, Z77 WS CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Logical processors: 8 Processor groups: 1 RAM: 16341 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 3500,0 MHz Measured CPU speed: 2127,0 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. _________________________________________________________________________________________________________ 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): 7242627,045824 Average measured interrupt to process latency (µs): 18,188028 Highest measured interrupt to DPC latency (µs): 7242607,443712 Average measured interrupt to DPC latency (µs): 16,752402 _________________________________________________________________________________________________________ MEASURED SMI, IPI AND CPU STALLS _________________________________________________________________________________________________________ The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled. Highest measured SMI or CPU stall (µs) 11,702754 _________________________________________________________________________________________________________ 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): 50441,254286 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 1,012740 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 1,182672 ISR count (execution time <250 µs): 6199310 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-999 µs): 44 ISR count (execution time 1000-1999 µs): 647 ISR count (execution time 2000-3999 µs): 146 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): 290181,002857 Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.18 , NVIDIA Corporation Highest reported total DPC routine time (%): 0,65890 Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in DPCs (%) 0,423603 DPC count (execution time <250 µs): 3458785 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 122 DPC count (execution time 1000-1999 µs): 13 DPC count (execution time 2000-3999 µs): 20 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: mmc.exe Total number of hard pagefaults 1510 Hard pagefault count of hardest hit process: 885 Highest hard pagefault resolution time (µs): 150176,941714 Total time spent in hard pagefaults (%): 0,174873 Number of processes hit: 19 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 113,571081 CPU 0 ISR highest execution time (µs): 50441,254286 CPU 0 ISR total execution time (s): 57,335946 CPU 0 ISR count: 6200256 CPU 0 DPC highest execution time (µs): 50649,808571 CPU 0 DPC total execution time (s): 18,248903 CPU 0 DPC count: 2925547 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 1,420216 CPU 1 ISR highest execution time (µs): 0,0 CPU 1 ISR total execution time (s): 0,0 CPU 1 ISR count: 0 CPU 1 DPC highest execution time (µs): 2006,213714 CPU 1 DPC total execution time (s): 0,097673 CPU 1 DPC count: 45470 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 7,785740 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): 290181,002857 CPU 2 DPC total execution time (s): 1,730631 CPU 2 DPC count: 254116 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 4,927838 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): 317,039143 CPU 3 DPC total execution time (s): 0,053659 CPU 3 DPC count: 38867 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 4,584513 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): 316,7140 CPU 4 DPC total execution time (s): 0,065876 CPU 4 DPC count: 40826 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 5,058538 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): 316,904571 CPU 5 DPC total execution time (s): 0,067707 CPU 5 DPC count: 42690 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 5,014937 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): 317,2060 CPU 6 DPC total execution time (s): 0,135418 CPU 6 DPC count: 54458 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 4,647503 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): 1919,2120 CPU 7 DPC total execution time (s): 0,136427 CPU 7 DPC count: 56984 _________________________________________________________________________________________________________ The GTX680 was running fine in similar machine with Windows7. Have to try to switch motherboards and recheck. That should tell if problem is in Windows8 or if the problem is in the motherboard.... |
Wiggo Send message Joined: 24 Jan 00 Posts: 34744 Credit: 261,360,520 RAC: 489 |
If you are not using the NVIDIA High Definition Audio outputs on those cards then try disabling them to see if that helps. Cheers. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Hello, I made the switch between the two computers. Swapped identical items: CPU, motherboard, cooler, memory. The rest stayed the same. Display adapters, PSU, chassis, Drives etc. So far it looks like the Win8 setup looks fine and the Win7 setup has DPC spikes and issues. The Win7 system with the HW from Win 8 has problems. To me it looks more like a HW issue. It has to be either: 1) Motherboard 2) CPU 3) Memory which I doubt..... Look at the Win 8 now with the HW from the Win7 system: _________________________________________________________________________________________________________ CONCLUSION _________________________________________________________________________________________________________ Your system appears to be suitable for handling real-time audio and other tasks without dropouts. LatencyMon has been analyzing your system for 0:11:04 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: XERXES OS version: Windows 8 , 6.2, build: 9200 (x64) Hardware: ASRock, Z77 WS CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Logical processors: 8 Processor groups: 1 RAM: 16341 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 3500,0 MHz Measured CPU speed: 2101,0 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. _________________________________________________________________________________________________________ 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): 397,016379 Average measured interrupt to process latency (µs): 3,913632 Highest measured interrupt to DPC latency (µs): 154,183959 Average measured interrupt to DPC latency (µs): 2,439926 _________________________________________________________________________________________________________ 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): 364,467143 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 1,552003 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 1,825015 ISR count (execution time <250 µs): 13155285 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-999 µs): 491 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): 434,316571 Driver with highest DPC routine execution time: ndis.sys - NDIS 6.30 driver, Microsoft Corporation Highest reported total DPC routine time (%): 0,712017 Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.18 , NVIDIA Corporation Total time spent in DPCs (%) 0,803979 DPC count (execution time <250 µs): 4794855 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 113 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: taskhostex.exe Total number of hard pagefaults 1992 Hard pagefault count of hardest hit process: 521 Highest hard pagefault resolution time (µs): 1941044,423143 Total time spent in hard pagefaults (%): 1,526699 Number of processes hit: 25 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 126,175545 CPU 0 ISR highest execution time (µs): 364,467143 CPU 0 ISR total execution time (s): 97,010918 CPU 0 ISR count: 13155776 CPU 0 DPC highest execution time (µs): 434,316571 CPU 0 DPC total execution time (s): 40,812208 CPU 0 DPC count: 4294954 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 0,437260 CPU 1 ISR highest execution time (µs): 0,0 CPU 1 ISR total execution time (s): 0,0 CPU 1 ISR count: 0 CPU 1 DPC highest execution time (µs): 182,648571 CPU 1 DPC total execution time (s): 0,109968 CPU 1 DPC count: 52673 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 0,655787 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): 173,999143 CPU 2 DPC total execution time (s): 0,340717 CPU 2 DPC count: 69334 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 0,408822 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): 324,2580 CPU 3 DPC total execution time (s): 0,139394 CPU 3 DPC count: 58598 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 1,402076 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): 290,026286 CPU 4 DPC total execution time (s): 0,71260 CPU 4 DPC count: 134640 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 0,840355 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): 127,643429 CPU 5 DPC total execution time (s): 0,112922 CPU 5 DPC count: 53020 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 0,778769 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): 195,387143 CPU 6 DPC total execution time (s): 0,359175 CPU 6 DPC count: 71595 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 0,826342 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): 126,019429 CPU 7 DPC total execution time (s): 0,149495 CPU 7 DPC count: 60154 _________________________________________________________________________________________________________ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.