That looks normal. Did it really take three minutes for the USB speed test to complete?
You might want to look for a new network driver. Were you doing anything heavy with Internet Explorer the first time?
All File transfers hang. No virus!
Started by
hmp3
, Jul 08 2017 03:45 PM
#302
Posted 09 November 2018 - 02:53 PM
hmp3
- Topic Starter
-
- Member
-
- 612 posts
Member
The Latency Test didn't complete by itself, I stopped it because you said it should take less than 30seconds.
On IE I only had a light gmail account and newsletter subscription page open.
#303
Posted 09 November 2018 - 02:58 PM
RKinner
-
- Expert
-
- 24,483 posts
Malware Expert
Guess I wasn't clear. Latency Monitor runs until you tell it to stop. Idea was to start it then run the USP speed test then stop Latency Monitor to see if something bad is happening. Expect your network adapter probably needs updating so leave it off while running the speed test.
#304
Posted 09 November 2018 - 03:58 PM
hmp3
- Topic Starter
-
- Member
-
- 612 posts
Member
_________________________________________________________________________________________________________
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:00:16 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: NIV
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK Computer INC., P6T
CPU: GenuineIntel Intel® Core™ i7 CPU 920 @ 2.67GHz
Logical processors: 8
Processor groups: 1
RAM: 12278 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2672 MHz
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): 144.436365
Average measured interrupt to process latency (µs): 4.171025
Highest measured interrupt to DPC latency (µs): 142.903884
Average measured interrupt to DPC latency (µs): 1.862110
_________________________________________________________________________________________________________
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): 45.324102
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.006309
Driver with highest ISR total time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0.011408
ISR count (execution time <250 µs): 3311
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): 104.584581
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0.027559
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 0.044492
DPC count (execution time <250 µs): 14702
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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: msmpeng.exe
Total number of hard pagefaults 4
Hard pagefault count of hardest hit process: 2
Number of processes hit: 1
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0.031073
CPU 0 ISR highest execution time (µs): 15.497754
CPU 0 ISR total execution time (s): 0.003001
CPU 0 ISR count: 1053
CPU 0 DPC highest execution time (µs): 104.584581
CPU 0 DPC total execution time (s): 0.009241
CPU 0 DPC count: 5205
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.010431
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): 0.0
CPU 1 DPC total execution time (s): 0.0
CPU 1 DPC count: 0
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.080937
CPU 2 ISR highest execution time (µs): 45.324102
CPU 2 ISR total execution time (s): 0.003995
CPU 2 ISR count: 190
CPU 2 DPC highest execution time (µs): 61.067740
CPU 2 DPC total execution time (s): 0.003481
CPU 2 DPC count: 387
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.004581
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): 0.0
CPU 3 DPC total execution time (s): 0.0
CPU 3 DPC count: 0
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.010287
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): 12.090569
CPU 4 DPC total execution time (s): 0.000672
CPU 4 DPC count: 326
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.005270
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): 0.0
CPU 5 DPC total execution time (s): 0.0
CPU 5 DPC count: 0
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.005187
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): 0.0
CPU 6 DPC total execution time (s): 0.0
CPU 6 DPC count: 0
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.072359
CPU 7 ISR highest execution time (µs): 7.287425
CPU 7 ISR total execution time (s): 0.007910
CPU 7 ISR count: 2068
CPU 7 DPC highest execution time (µs): 38.330090
CPU 7 DPC total execution time (s): 0.044741
CPU 7 DPC count: 8784
_________________________________________________________________________________________________________
#305
Posted 09 November 2018 - 04:02 PM
RKinner
-
- Expert
-
- 24,483 posts
Malware Expert
We got a few page faults from Windows Defender but 16 seconds isn't that bad. What speeds did it show that time?
#306
Posted 09 November 2018 - 04:05 PM
hmp3
- Topic Starter
-
- Member
-
- 612 posts
Member
started at 4 ended around 1.45mb
#309
Posted 09 November 2018 - 05:06 PM
RKinner
-
- Expert
-
- 24,483 posts
Malware Expert
That's about normal for write. The drop in speed during the write test is something I see on one of my drives too.
What did it say for read?
#311
Posted 09 November 2018 - 07:38 PM
hmp3
- Topic Starter
-
- Member
-
- 612 posts
Member
Write has previously been 16mb, as written in previous posts.
How can it be 16-18 then next test 8-10, then 4-6?
Edited by phickspc, 09 November 2018 - 07:38 PM.
#312
Posted 09 November 2018 - 07:43 PM
RKinner
-
- Expert
-
- 24,483 posts
Malware Expert
That's what we are trying to figure out. We got decent results with the network adapter turned off but we did see Windows Defender sticking its nose in. Can you pause Windows Defender and repeat the test with the network adapter off?
#313
Posted 10 November 2018 - 07:09 AM
hmp3
- Topic Starter
-
- Member
-
- 612 posts
Member
Windows Defender wasn't turned on at all.
I searched for it in Process Explorer, but the only trace it found was svchost and when I paused that the computer froze until I resumed it again.
So I looked in msconfig and unticked it's box in the startup tab, restarted and double checked it was disabled in services.msc (it was disabled).
Disabled Network Adaptor then started the tests.
Test1
Write 3-4mb
Read 14-16mb
_________________________________________________________________________________________________________
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:00:20 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: NIV
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK Computer INC., P6T
CPU: GenuineIntel Intel® Core™ i7 CPU 920 @ 2.67GHz
Logical processors: 8
Processor groups: 1
RAM: 12278 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2672 MHz
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): 606.864930
Average measured interrupt to process latency (µs): 2.258870
Highest measured interrupt to DPC latency (µs): 154.398085
Average measured interrupt to DPC latency (µs): 0.771899
_________________________________________________________________________________________________________
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): 68.610404
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.043724
Driver with highest ISR total time: SCSIPORT.SYS - SCSI Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0.110055
ISR count (execution time <250 µs): 51081
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): 114.602919
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0.122317
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 0.322340
DPC count (execution time <250 µs): 133407
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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: svchost.exe
Total number of hard pagefaults 1873
Hard pagefault count of hardest hit process: 912
Number of processes hit: 7
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0.513620
CPU 0 ISR highest execution time (µs): 14.144835
CPU 0 ISR total execution time (s): 0.106818
CPU 0 ISR count: 35788
CPU 0 DPC highest execution time (µs): 114.602919
CPU 0 DPC total execution time (s): 0.244249
CPU 0 DPC count: 88719
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.195260
CPU 1 ISR highest execution time (µs): 68.610404
CPU 1 ISR total execution time (s): 0.022056
CPU 1 ISR count: 860
CPU 1 DPC highest execution time (µs): 69.402320
CPU 1 DPC total execution time (s): 0.016625
CPU 1 DPC count: 1918
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.169948
CPU 2 ISR highest execution time (µs): 15.163922
CPU 2 ISR total execution time (s): 0.012079
CPU 2 ISR count: 4471
CPU 2 DPC highest execution time (µs): 86.137725
CPU 2 DPC total execution time (s): 0.027743
CPU 2 DPC count: 1510
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.055617
CPU 3 ISR highest execution time (µs): 13.328967
CPU 3 ISR total execution time (s): 0.000013
CPU 3 ISR count: 1
CPU 3 DPC highest execution time (µs): 21.235404
CPU 3 DPC total execution time (s): 0.000407
CPU 3 DPC count: 229
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.088320
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): 6.535928
CPU 4 DPC total execution time (s): 0.000439
CPU 4 DPC count: 236
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.057158
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): 0.0
CPU 5 DPC total execution time (s): 0.0
CPU 5 DPC count: 0
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.085862
CPU 6 ISR highest execution time (µs): 7.194611
CPU 6 ISR total execution time (s): 0.000034
CPU 6 ISR count: 8
CPU 6 DPC highest execution time (µs): 7.382111
CPU 6 DPC total execution time (s): 0.000788
CPU 6 DPC count: 309
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.447745
CPU 7 ISR highest execution time (µs): 7.418413
CPU 7 ISR total execution time (s): 0.037825
CPU 7 ISR count: 9953
CPU 7 DPC highest execution time (µs): 42.717814
CPU 7 DPC total execution time (s): 0.233513
CPU 7 DPC count: 40486
_________________________________________________________________________________________________________
#314
Posted 10 November 2018 - 07:10 AM
hmp3
- Topic Starter
-
- Member
-
- 612 posts
Member
I did a second test as I was puzzled by the high number of page faults. I assume it was because I had just restarted and pc was probably still loading.
Test2
Write 2mb
Read 12-14mb
_________________________________________________________________________________________________________
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:00:17 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: NIV
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK Computer INC., P6T
CPU: GenuineIntel Intel® Core™ i7 CPU 920 @ 2.67GHz
Logical processors: 8
Processor groups: 1
RAM: 12278 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2672 MHz
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): 157.079938
Average measured interrupt to process latency (µs): 3.075916
Highest measured interrupt to DPC latency (µs): 155.164329
Average measured interrupt to DPC latency (µs): 1.086860
_________________________________________________________________________________________________________
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): 53.657934
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.047901
Driver with highest ISR total time: SCSIPORT.SYS - SCSI Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0.095766
ISR count (execution time <250 µs): 38162
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): 124.761228
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0.140507
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.272156
DPC count (execution time <250 µs): 101561
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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: onenote.exe
Total number of hard pagefaults 2
Hard pagefault count of hardest hit process: 1
Number of processes hit: 1
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0.502279
CPU 0 ISR highest execution time (µs): 15.952844
CPU 0 ISR total execution time (s): 0.099366
CPU 0 ISR count: 32959
CPU 0 DPC highest execution time (µs): 124.761228
CPU 0 DPC total execution time (s): 0.262101
CPU 0 DPC count: 81669
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.171653
CPU 1 ISR highest execution time (µs): 53.657934
CPU 1 ISR total execution time (s): 0.014684
CPU 1 ISR count: 547
CPU 1 DPC highest execution time (µs): 78.981287
CPU 1 DPC total execution time (s): 0.011420
CPU 1 DPC count: 1081
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.098282
CPU 2 ISR highest execution time (µs): 8.315868
CPU 2 ISR total execution time (s): 0.000327
CPU 2 ISR count: 93
CPU 2 DPC highest execution time (µs): 45.327096
CPU 2 DPC total execution time (s): 0.000652
CPU 2 DPC count: 120
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.071953
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): 0.0
CPU 3 DPC total execution time (s): 0.0
CPU 3 DPC count: 0
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.053337
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): 0.0
CPU 4 DPC total execution time (s): 0.0
CPU 4 DPC count: 0
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.052028
CPU 5 ISR highest execution time (µs): 8.198353
CPU 5 ISR total execution time (s): 0.000008
CPU 5 ISR count: 1
CPU 5 DPC highest execution time (µs): 6.860778
CPU 5 DPC total execution time (s): 0.000092
CPU 5 DPC count: 46
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.089549
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): 6.601796
CPU 6 DPC total execution time (s): 0.000214
CPU 6 DPC count: 73
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.283790
CPU 7 ISR highest execution time (µs): 8.811377
CPU 7 ISR total execution time (s): 0.017917
CPU 7 ISR count: 4562
CPU 7 DPC highest execution time (µs): 39.836826
CPU 7 DPC total execution time (s): 0.101511
CPU 7 DPC count: 18572
_________________________________________________________________________________________________________
#315
Posted 10 November 2018 - 07:13 AM
RKinner
-
- Expert
-
- 24,483 posts
Malware Expert
Can you pause onenote.exe and try again?
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:
Sign In
Create Account
