Diagnostic Options

The options on this page:

Screenshots: invaluable information, shows the radio, bandwidth, selected options, layout. Invaluable!

Logfile: copious information generated as the program is running, usually the key information is generated when the program starts, this shows your computer capability. All errors are logged here.

DebugView: additional information only of interest when debugging the program.

System Diagnostics: utilises the DirectX Diagnsotics program (part of Windows) which lists your CPU model, RAM, display information.

GPU-Z: excellent utility for monitoring your graphics processing.



Update Your Drivers

If you get a crash while starting the program make sure you have the latest drivers installed, especially the NVIDIA drivers if you are using a NVIDIA graphics card. A  recent Windows 7 problem was resolved by installing the latest NVIDIA drivers, card was a GT 730M,


To take a screenshot just click on the small camera icon in the Quick Access Toolbar (top left of program) or the icon in the Home / Extras pane of the ribbon bar.

When you have the screenshot you can attach it to (not embed it in)  an e-mail in the Groups.io forum.


The logfile is accessed from the ribbon bar's Tools tab. The logfile is displayed using your default text file browser from which you can save to a disk file for forwarding to developers.


Logfile entries are also sent to the debugger output. By default you will not be using a debugger, however DebugView from Windows Sysinternals is an excellent free utility which lets you monitor the debug output.

For more information about DebugView please visit the DebugView hompage. An example DebugView session is shown below.

It is recommended to start DebugView before this software so that you will see all logfile entries.

Please Wait :: Error Reports

If you see a small 'Please Wait' window followed by a BugTrap error report please upload the contents of the error report to the cloud, for example with one of these free providers:

Then send an e-mail to simon@sdr-radio.com with the link to the uploaded files. All object and symbol files used by preview kits are stored so that the crash dumps can be successfully analysed.



"GPU-Z is a lightweight system utility designed to provide vital information about your video card and graphics processor. " TechPowerUp GPU-Z

Make sure the PCI-E bandwidth speeds is as fast as it should be. For example:

Use the sensors page to monitor the load:

Reddit Article

A very interesting article on Reddit. The bottom line - worth reading:

My personal GPU is a GTX 970 and recently I checked these figures and instead of my speeds being at x16 - my native speed was only at x8. The solution to fix this was an odd one. My motherboard only hosts three PCI-E slots: two 3.0 and one 1.0. I had my GTX 970 installed in one of those 3.0 slots (this was correct) and I had my Sound Card installed in the other 3.0 slot (this was the problem). For some reason when devices were installed in BOTH 3.0 slots - the computer cut the bus interface bandwidth of both devices IN HALF - almost as if the computer thought I was trying to run an SLI setup.

The fix was to simply move my Sound Card from the 3.0 slot to the much smaller 1.0 slot and reboot (which free'd up my remaining 3.0 slot). Once this was done, I checked in GPU-Z and Nvidia's CP and my card bandwidth was at it's full potential (PCI-E 3.0 x16) and it SHOWED. My FPS in games went up dramatically and everything was much better.

Link to the full article.


If you have problems, here's a checklist:

  1. If you have a NVIDIA graphics card make sure you have the latest NVIDIA drivers (more information on this page)
  2. If the software is slow, sluggish then:
    • look at the CPU Features (this page) and try with a lower bandwidth (sample rate) when starting the radio
    • look at CPU and Memory in the Options windows (more information on this page)
    • check your hardware meets the recommended minimum (see the FAQ page)
  3. When reporting an error:
    • screenshots are invaluable:
      • console - shows your settings and configuration
      • CPU and Memory - shows the CPU and memory load
    • there's more information in the logfile than you may think
    • don't forget to provide the make and model of radio you are using
  4. If you get a crash follow the steps in Error reports (this page)

Please do not send e-mail direct to the development team, instead use the Groups.io forum.

CPU Features

When the program starts the features of your CPU are listed in the logfile.

Of particular interest are the Streaming SIMD Extensions, ideally your CPU will have SIMD Extensions 4.1 and 4.2; more modem CPUs also have AVX and possibly AVX2. The software uses these extension sets to maximise the processing efficiency. If your CPU does not support SIMD Extensions 4.1 and 4.2 then it's quite old and should only be used at lower bandwidths, typically less than 1 MHz.

Some interesting links for the inquisitive:

A full listing from an i5-3570 system:

Features: [X] MMX ..... Intel Architecture MMX
Features: [X] SSE ..... Streaming SIMD Extensions
Features: [X] SSE2 .... Streaming SIMD Extensions 2
Features: [X] SSE3 .... Streaming SIMD Extensions 3
Features: [X] SSE3S ... Streaming SIMD Extensions 3 (supplemental)
Features: [X] SSE4.1 .. Streaming SIMD Extensions 4.1
Features: [X] SSE4.2 .. Streaming SIMD Extensions 4.2
Features: [X] AVX ..... Advanced Vector Extensions 1 instruction set
Features: [_] AVX2 .... Advanced Vector Extensions 2 instruction set
Features: [X] The operating system supports AVX
Features: [_] The processor supports MOVBE instruction
Features: [X] AES instruction
Features: [X] PCLMULQDQ instruction
Features: [X] Read Random Number instructions
Features: [X] Float16 instructions
Features: [_] ADCX and ADOX instructions
Features: [_] The RDSEED instruction
Features: [_] The PREFETCHW instruction
Features: [_] Knights Corner instruction set

CPU and Memory Usage

To see the CPU and memory usage select Options from the Tools pane in the ribbon bar. let the software run for up to ten seconds so that the values become more-or-less stable, then dlick the camera button at the bottom left to take a screenshot.

An example is shown below:

System Diagnostics

The DirectX Diagnostics Tool provides a very usable summary of your computer. You can start this program either by:

  1. entering dxdiag in the Windows search window, or
  2. selecting DirectX Diagnostics from the Tools pane of the ribbon bar.

An example of the output is shown below.