BSOD with Audacity 2

[fastenough]

BLUE SCREEN OF DEATH

I am running Windows XP with service pack 3

Audacity 1.2.6 runs with no problems.

However with Audacity 2.0.0 any attempt to record an incoming signal results in BSOD.
(I installed it from the .exe installer )

I had exactly this problem with the 1.3 beta version last May and gave up trying to resolve the problem. See
http://forum.audacityteam.org/viewtopic ... 16&t=56415
Setting to " microsoft sound mapper" made no difference
A colleague of mine said this was known problem so I am surprised it is still in the latest version.
Have you had any other reports of this?

[kozikowski]

No. Not recently.

Audacity uses a lot of computer hardware memory (RAM). It's not unusual for Audacity to be the only program you own that does that. If you have a bad stick of RAM way up in high memory and the computer tries to use it, it could crash your computer.

Computers used to take forever to start because they would do a check of memory at the beginning, but they boot quickly now by skipping the check and also, many people put their computer to sleep rather than starting it each time. So you would never know.

Microsoft makes a very nice memory checker and it's free, but a little rough to use. It volunteers to run itself multiple times and you should do that.

http://oca.microsoft.com/en/windiag.asp

Koz

[kozikowski]

Is this the same computer you were using then?
Koz

[Gale Andrews]

BLUE SCREEN OF DEATH

I am running Windows XP with service pack 3

Audacity 1.2.6 runs with no problems.

However with Audacity 2.0.0 any attempt to record an incoming signal results in BSOD.
(I installed it from the .exe installer )

I had exactly this problem with the 1.3 beta version last May and gave up trying to resolve the problem. See
http://forum.audacityteam.org/viewtopic ... 16&t=56415
Setting to " microsoft sound mapper" made no difference
A colleague of mine said this was known problem so I am surprised it is still in the latest version.
Have you had any other reports of this?

BSOD is common if you have questionable sound devices or sound device drivers. Sound Blasters are known as buggy devices. Are you using SoundBlaster as your default recording and playback device in "Sounds and Audio Devices" in Windows?

The fact that 1.2.6 works could mean that you have old Sound Blaster drivers and you may want to see if you can you get more recent ones:
http://tinyurl.com/5mvmse .

The best way to find out what is causing the BSOD (it isn't Audacity as it does not have the kernel privileges to shut the computer down) is to look at the memory dump.

You can analyse the memory dump fairly easily by downloading WhoCrashed:
http://www.resplendence.com/downloads .

The first time you click the Analyze button to look at the dump, WhoCrashed will ask you to select the path to the Microsoft Debugging Tools for Windows. This is usually in:

C:Program FilesDebugging Tools for Windows .

If you don't have the tools then you can download the required installer by clicking “Download the required file from Microsoft site now”.

If you are not sure where the memory dump is, right-click over My Computer > Properties, which should bring you to "System Properties". Click the "Advanced" tab, and then click "Settings" under "Startup and Recovery".



Gale

[fastenough]

Thanks for these replies - I will try looking at these things. (Yes it is the same Computer).