Page 1 of 1

When using this forum to troubleshoot: RULES

Posted: Thu Dec 05, 2019 2:38 am
by valis
Please if you're asking for a technical reason, provide the relevant technical information.

For instance:

"Help! My Scope isn't launching, it just crashes!"

We certainly empathize with your situation, but the following might also be helpful to start a NEW thread with some relevant info like:
  • Windows OS Version? 32 or 64bit?
  • Scope Version? 32 or 64bit?
  • Which DSP Card(s) or XIte are you using?

If this also involves the host system hardware:
  • Motherboard make, model and revision
  • CPU
  • Ram (size & type at least)'
  • Graphics Card
  • What Scope card(s) are installed in your system?
  • additional cards and devices sharing resources and so on (if this seems relevant)

If the issue is with host software
  • Tell us the version of the software
  • Which Scope Driver(s) are you attempting to use?
  • Is this issue easily replicated, or does it only occur with 1 specific project?

Scope Device(s) or Scope issue?
  • Screenshot of your routing page
  • Device Version, if relevant
  • Include any error codes

Even if these details don't seem 100% relevant, it will save us all time as we will 'walk the chain' in terms of troubleshooting and likely ask for these details anyway. Oh yes, hopefully I don't need to add this, BUT: be respectful and remember consider language barriers may be a factor.

Let's call this 'Problem Solving Etiquette' 101...Thanks!

Re: When using this forum to troubleshoot: RULES

Posted: Sat Mar 07, 2020 8:53 am
by valis
If you're having dropouts, we recommend using the DPC Latency reporting tool for your system. Do this at idle and under load.

Sweetwater.com: Solving DPC Latency Issues