Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Foobar2000 BSOD Win7 64bit? (Read 6632 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar2000 BSOD Win7 64bit?

Hi my Win 7 64 bit blue screens when foobar has been left idle for some time.
I have ipod component.
Cant see any crash information from foobar itself ...


It's happened about 8 times now...

Directory of C:\Program Files (x86)\foobar2000\components

2/06/2012  20:06    <DIR>          .
2/06/2012  20:06    <DIR>          ..
7/06/2012  19:36          359,424 foo_albumlist.dll
7/06/2012  19:36          299,008 foo_cdda.dll
7/06/2012  19:35          483,328 foo_converter.dll
2/06/2011  22:17        1,858,048 foo_dop.dll
7/06/2012  19:36          276,480 foo_dsp_std.dll
7/06/2012  19:35        1,417,216 foo_input_std.dll
7/06/2012  19:35          286,720 foo_rgscan.dll
7/06/2012  19:36          915,456 foo_ui_std.dll
0/05/2012  18:48        1,579,008 foo_upnp.dll
6/08/2010  23:04            1,599 licence.txt
            10 File(s)      7,476,287 bytes
              2 Dir(s)  165,826,600,960 bytes free


The Windows crash dump reports

1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000004070012, Memory contents of the pool block
Arg4: fffffa800ed85ec0, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS:  fffffa800ed85ec0

FREED_POOL_TAG:  AfdL

BUGCHECK_STR:  0xc2_7_AfdL

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  foobar2000.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800037b8be9 to fffff8000368e1c0

Foobar2000 BSOD Win7 64bit?

Reply #1
You could upload the minidump if you want someone to take a look at possible cause, but you can rule out foobar2000 immediately. Only broken hardware or bugs in kernel level code (drivers) can cause BSODs. Check for updated BIOS and drivers, especially sound card drivers (unless you use Microsoft's native High Definition Audio drivers).

 

Foobar2000 BSOD Win7 64bit?

Reply #2
Moved out of Support accordingly.

Foobar2000 BSOD Win7 64bit?

Reply #3
Moved out of Support accordingly.


It's not really 'off-topic' is it? If anything it might help point others in the correct direction to check their sound drivers.

Foobar2000 BSOD Win7 64bit?

Reply #4
Audio Hardware is a bit of a stretch, but OK, whatever.

Foobar2000 BSOD Win7 64bit?

Reply #5
Are you sure that this happens only with Foobar2000?
If the soundcard is UAA compatible then you could try uninstalling the soundcard driver and all software related to the soundcard and let Windows install a generic driver for it like 'High Definition Audio Device'.

Also run memtest from www.memtest.org to see if there is any problem with the memory.

Foobar2000 BSOD Win7 64bit?

Reply #6
The problem isn't Foobar, its PC hardware - possibly your PC's audio interface's power management. Time to update its driver.

Foobar2000 BSOD Win7 64bit?

Reply #7
As i systematically have the same problem and google led me here i'll raise the problem once again:

i have two pc

tablet samsung ativ pro 700t1c - windows8 64bit
and samsung r519 notebook, windows 7 64bit

eventually bsod occurs ONLY IF music is played through foobar AND pc's are connected via usb to Marantz sa11s3 in DAC mode. Audio properties do not matter - this happens on both mp3 and flac in 16/44 to 24/192.

Playback with Marantz on other media players doesn't cause bsod, as well as playback through foobar with default audio card, so it seems to me it is a software problem.


Core (2013-06-14 09:44:34 UTC)
    foobar2000 core 1.2.8
foo_albumlist.dll (2013-02-11 11:28:58 UTC)
    Album List 4.5
foo_audioscrobbler.dll (2012-08-20 11:49:44 UTC)
    Audioscrobbler 2.3.1
foo_cdda.dll (2013-03-07 09:48:32 UTC)
    CD Audio Decoder 3.0
foo_converter.dll (2013-06-14 09:09:50 UTC)
    Converter 1.5
foo_dsp_eq.dll (2013-02-11 11:28:58 UTC)
    Equalizer 1.0
foo_dsp_std.dll (2013-06-14 09:10:08 UTC)
    Standard DSP Array 1.3
foo_input_monkey.dll (2014-02-22 21:24:22 UTC)
    Monkey's Audio Decoder 2.1.7
foo_input_std.dll (2013-06-14 09:44:34 UTC)
    Standard Input Array 1.0
foo_rgscan.dll (2013-06-14 09:09:54 UTC)
    ReplayGain Scanner 2.2
foo_ui_std.dll (2013-06-14 09:44:34 UTC)
    Default User Interface 0.9.5


thanks in advance.

Foobar2000 BSOD Win7 64bit?

Reply #8
Its a driver problem with your PC.  Try updating your audio drivers.  Alternatively, you can also try changing the audio output mode in foobar to a different interface. This may also work around buggy drivers.