I have been running 2.0.3, which has proved very stable and reliable. I just upgraded to 2.0.4 and at start-up it does a complete BOD crash. My computer is XP SP3. I tried a fresh install, I tried unselecting all plugin at install, but I still ended with a BOD crash. Reverting to 2.0.3 works fine again. Does anyone have any ideas about getting data from the crash?
I assume you mean BSOD (blue screen of death).
A fresh installation won’t change anything unless you reinstall with the “Reset Preferences” box checked (ticked) when you get halfway though the installer. Please try that if you haven’t done so, but it may not help.
You can install WhoCrashed as described here Audacity Manual to get a user-friendly read out of the computer memory dump. It could be that the new audio interfaces in 2.0.4 are not being handled well by your audio devices (or by their current drivers). If so, WhoCrashed may tell you which device and driver is the problem.
Gale
I too have the same issue. BSOD when I try to run Audacity 2.0.4 on Windfows 7. I have tried using Whocrashed and I get the following analysis each time.
On Sun 08/09/2013 17:24:53 GMT your computer crashed
crash dump file: C:WindowsMinidump90813-52977-01.dmp
This was probably caused by the following module: ksthunk.sys (ksthunk+0x39AB)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044CD9AB, 0xFFFFF880084E3AC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:Windowssystem32driversksthunk.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Streaming WOW Thunk Service
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
@creativitymatters and bblesser: Please try the build in this topic https://forum.audacityteam.org/t/audacity-start-failure-or-blue-screen-on-a-few-machines/30903/1 and let us know here what happens.
Gale
Tried this version and audacity appears to work fine.
Excellent. Thanks for the feedback.
Could you also post the output from “Help menu > Audio Device Info”
Thanks.
There you go
==============================
Default capture device number: 1
Default playback device number: 3
==============================
Device ID: 0
Device name: Microsoft Sound Mapper - Input
Host name: MME
Input channels: 2
Output channels: 0
Low Input Latency: 0.090000
Low Output Latency: 0.090000
High Input Latency: 0.180000
High Output Latency: 0.180000
Supported Rates:
==============================
Device ID: 1
Device name: Microphone (Realtek High Defini
Host name: MME
Input channels: 2
Output channels: 0
Low Input Latency: 0.090000
Low Output Latency: 0.090000
High Input Latency: 0.180000
High Output Latency: 0.180000
Supported Rates:
==============================
Device ID: 2
Device name: Microsoft Sound Mapper - Output
Host name: MME
Input channels: 0
Output channels: 2
Low Input Latency: 0.090000
Low Output Latency: 0.090000
High Input Latency: 0.180000
High Output Latency: 0.180000
Supported Rates:
8000
9600
11025
12000
15000
16000
22050
24000
32000
44100
48000
88200
96000
176400
192000
352800
384000
==============================
Device ID: 3
Device name: Speakers (Realtek High Definiti
Host name: MME
Input channels: 0
Output channels: 2
Low Input Latency: 0.090000
Low Output Latency: 0.090000
High Input Latency: 0.180000
High Output Latency: 0.180000
Supported Rates:
8000
9600
11025
12000
15000
16000
22050
24000
32000
44100
48000
88200
96000
176400
192000
352800
384000
==============================
Device ID: 4
Device name: Primary Sound Capture Driver
Host name: Windows DirectSound
Input channels: 2
Output channels: 0
Low Input Latency: 0.120000
Low Output Latency: 0.000000
High Input Latency: 0.240000
High Output Latency: 0.000000
Supported Rates:
==============================
Device ID: 5
Device name: Microphone (Realtek High Definition Audio)
Host name: Windows DirectSound
Input channels: 2
Output channels: 0
Low Input Latency: 0.120000
Low Output Latency: 0.000000
High Input Latency: 0.240000
High Output Latency: 0.000000
Supported Rates:
==============================
Device ID: 6
Device name: Primary Sound Driver
Host name: Windows DirectSound
Input channels: 0
Output channels: 2
Low Input Latency: 0.000000
Low Output Latency: 0.120000
High Input Latency: 0.000000
High Output Latency: 0.240000
Supported Rates:
8000
9600
11025
12000
15000
16000
22050
24000
32000
44100
48000
88200
96000
176400
192000
==============================
Device ID: 7
Device name: Speakers (Realtek High Definition Audio)
Host name: Windows DirectSound
Input channels: 0
Output channels: 2
Low Input Latency: 0.000000
Low Output Latency: 0.120000
High Input Latency: 0.000000
High Output Latency: 0.240000
Supported Rates:
8000
9600
11025
12000
15000
16000
22050
24000
32000
44100
48000
88200
96000
176400
192000
==============================
Device ID: 8
Device name: Speakers (Realtek High Definition Audio)
Host name: Windows WASAPI
Input channels: 0
Output channels: 2
Low Input Latency: 0.000000
Low Output Latency: 0.003000
High Input Latency: 0.000000
High Output Latency: 0.010000
Supported Rates:
48000
==============================
Device ID: 9
Device name: Speakers (Realtek High Definition Audio) (loopback)
Host name: Windows WASAPI
Input channels: 2
Output channels: 0
Low Input Latency: 0.003000
Low Output Latency: 0.000000
High Input Latency: 0.010000
High Output Latency: 0.000000
Supported Rates:
==============================
Device ID: 10
Device name: Microphone (Realtek High Definition Audio)
Host name: Windows WASAPI
Input channels: 2
Output channels: 0
Low Input Latency: 0.003000
Low Output Latency: 0.000000
High Input Latency: 0.010159
High Output Latency: 0.000000
Supported Rates:
==============================
Selected capture device: 1 - Microphone (Realtek High Defini
Selected playback device: 3 - Speakers (Realtek High Definiti
Supported Rates:
8000
9600
11025
12000
15000
16000
22050
24000
32000
44100
48000
88200
96000
176400
192000
352800
384000
==============================
Available mixers:
==============================
Available capture sources:
0 - Master
==============================
Available playback volumes:
0 - PCM
==============================
Capture volume is native
Playback volume is native
The suggestion to use WhoCrashed to get more information was great, and the professional version for modest $$ is even better. As suggested, a module in the MobilePre sound card driver was the offending party. That is consistent with the forum dialogs. And yes, it appears to have resulted from a change in 2.0.4 which is being examined in the alpha version of 2.0.5. My driver is very old and there is no upgrade available. It may be time to move on.
Worked fine as you suspected it would. Thanks for the effort. Are there any other changed in this 2.0.5 alpha other than this experiment?
Thanks for testing. That 2.0.5 alpha is code-identical to 2.0.4 release, except for the version number and removing WDM-KS.
Gale
Thanks, nothing apparently out of the ordinary there. Just a Realtek motherboard sound device. Did you have any other audio devices connected when you tried 2.0.4?
Gale