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: foobar crashes computer? (Read 11564 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar crashes computer?

The last three or so weeks I have experienced my computer crashing. While playing audio  from the sat receiver or browsing, foobar still open in the background but inactive, the computer would completely freeze picture on the screen, no interaction possible. Computer had to be rebooted after hard shutdown.

Could not find any error message that refers to the shutdown, only a message that rebooting followed unexpected shutdown.
I suspected foobar, because when not activating the player no crash would happen, even after leaving the machine running for two or three days continuously.
As soon after foobar was activated, the crash happened within two - 8 hours.
Today I found rebooting after yesterdays crash the following error message:
after rebooting
Code: [Select]
Log Name:      Application
Source:        Application Error
Date:          3/27/2012 11:10:54 PM
Event ID:      1000
Task Category: (100)
Level:        Error
Keywords:      Classic
User:          N/A
Computer:      petermc
Description:
Faulting application name: foobar2000.exe, version: 1.1.12.0, time stamp: 0x4f6f0f5f
Faulting module name: foobar2000.exe, version: 1.1.12.0, time stamp: 0x4f6f0f5f
Exception code: 0x40000015
Fault offset: 0x00107687
Faulting process id: 0x704
Faulting application start time: 0x01cd0c8d198b4af6
Faulting application path: C:\foobar2000\foobar2000.exe
Faulting module path: C:\foobar2000\foobar2000.exe
Report Id: c6976ac3-789c-11e1-b008-00261883c444
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-03-28T06:10:54.000000000Z" />
    <EventRecordID>18098</EventRecordID>
    <Channel>Application</Channel>
    <Computer>petermc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>foobar2000.exe</Data>
    <Data>1.1.12.0</Data>
    <Data>4f6f0f5f</Data>
    <Data>foobar2000.exe</Data>
    <Data>1.1.12.0</Data>
    <Data>4f6f0f5f</Data>
    <Data>40000015</Data>
    <Data>00107687</Data>
    <Data>704</Data>
    <Data>01cd0c8d198b4af6</Data>
    <Data>C:\foobar2000\foobar2000.exe</Data>
    <Data>C:\foobar2000\foobar2000.exe</Data>
    <Data>c6976ac3-789c-11e1-b008-00261883c444</Data>
  </EventData>
</Event>
Anybody who can help deciphering what happened?
I have my Asus p6 motherboard based PC running foobar2000 for three years now, and this is the first time I experience problems of such a nature.
I  familiar with crashes caused by components, but all my components installed have been running fine now for a long time.
Thanks for any help.

foobar crashes computer?

Reply #1
Update your soundcard drivers.

User applications can't usually crash your computer like that. If they could, malware would be much more dangerous.  However, faulty drivers can, and do (especially on XP). It could be fb2k exposes bugs in those drivers that other software doesn't--especially if you use a non-standard output component.
elevatorladylevitateme

foobar crashes computer?

Reply #2
Hi,
I have updated the soundcard driver (m-audio 1010lt) and it still crashed.
I rum wW7 32 OS.
What do you mean by "non standard output"?
I run foobar asio (the crash also happens in DS mode) directly to the soundcard spdif output. I also tried the spdif output of the mobo through windows mixer - same problem when playback in foobar. No problem with the soundcard when using it for audio replay for any other connected appliance, be it phono preamp, bluray player or sat. receiver.

I will try winamp and see if the problem occurs there too.

foobar crashes computer?

Reply #3
Could this be a hard drive failure?

Have you tried running the manufacturers diagnosis tool on the drive?

EDIT: i reread your post and you say that it only BSODs when FB2k is open\running, it probably still wouldn't hurt to check the drive anyhow
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.

foobar crashes computer?

Reply #4
Hi, just previous to the problem occurring I had checked the hard-drive status using Sea tools and all hard-drives internally and externally, no problems reported. I am at present rechecking.

After that last crash I have had no problems for the last 24hours, having had foobar run in the background, but not playing.

foobar crashes computer?

Reply #5
Couldn't this be a RAM issue. I had something similar (not with foobar2000) but it predominantly affected my browsers. I thought it was a HDD problem (assuming RAM should affect everything), turned out to be a RAM problem. Similar symptoms to what you describe. Just a guess, really.

C.
PC = TAK + LossyWAV  ::  Portable = Opus (130)

foobar crashes computer?

Reply #6
Hi,

I have some excess RAM to what W7 32 can use, in case I want to install W7 64. Windows 32 can only use  1/2 what what I have available (6 GB) and when playing foobar and all other apps I am using on the side  never demand more than about 75% of what is available.
I monitor the RAM and CPU use (which is less than 5% running foobar) and also the CPU temperature and the enclosure temp. Never even close to the threshold of alarm (70C)

foobar crashes computer?

Reply #7
No, I wasn't talking about the amount of RAM you have (i.e. I wasn't suggesting you may not have sufficient RAM), I was suggesting you may have some faulty RAM. Have you tested it? There's plenty of memory test freeware around.

C.
PC = TAK + LossyWAV  ::  Portable = Opus (130)

 

foobar crashes computer?

Reply #8
No, I wasn't talking about the amount of RAM you have (i.e. I wasn't suggesting you may not have sufficient RAM), I was suggesting you may have some faulty RAM. Have you tested it? There's plenty of memory test freeware around.

C.



Thanks for the hint. Retesting the hard drives with the Sea Tool tested ok. Next I will test the Ram with the windows tool mtinst.

However - for the last three days I kept foobar playing and also in the background without playback. No further problems....
Confused near the Alaska Highway...

foobar crashes computer?

Reply #9
No, I wasn't talking about the amount of RAM you have (i.e. I wasn't suggesting you may not have sufficient RAM), I was suggesting you may have some faulty RAM. Have you tested it? There's plenty of memory test freeware around.

C.



Thanks for the hint. Retesting the hard drives with the Sea Tool tested ok. Next I will test the Ram with the windows tool mtinst.

However - for the last three days I kept foobar playing and also in the background without playback. No further problems....
Confused near the Alaska Highway...



I've been having the same problem for around 9 months. Dell Latitude E5510. I'm an engineer, using computers for 25 years now including a few years doing PC repair and diagnostic work. I've isolated the problem to occur only when Foobar is open.

Usually the crash occurs over night or over the weekend, I've only been present when it occurred three times. Once when foobar was playing music but the other two times I wasn't even actively using the computer and no music was playing. It BSOD and then reboots. At that point the hard drive would not be recognized (BIOS doesn't even see it) until I cycle power to the computer. I've been told the hard drive behavior could be Windows corrupting the MBR as it crashes and is a symptom not the cause.

The BSOD happens so unexpectedly and quickly that all I've been able to record from the BSOD is "KERNEL_DATA_", probably "KERNEL_DATA_INPAGE_ERROR".

I've set windows to produce a dump file and not reboot after a BSOD but then, as it happened even this morning, I just come in to work to find a blank screen and have to cycle power to the laptop. No dump file to be found. I've left my laptop on for weeks without foobar running and no problems. If foobar is on, anywhere from 1-3 days and I'm guaranteed to come in to work and find my computer crashed.

I've run all the memtest and hard drive tests out there. I've run the Dell diagnostics multiple times and because it passes those tests Dell refuses to replace any hardware because they're convinced it's software. At first I was adamant that a hard drive problem existed but after all my testing I have admit it appears related to foobar somehow.

I've used foobar on multiple machines for many years now. One thing odd about this particular computer is a glitch/pause in music playback when the screensaver activates. No fancy 3D screensaver, just a blank screen. Not normal for a machine built in the last 10 years and no flying toasters. The screensaver glitch might explain why I see this happen most often over night when no active computing is being done.

My power settings have the monitors being turned off after 25 minutes and the hard drives power down after 60 minutes.

Any help or insight would be appreciated. I've done so many Internet searches trying to solve this and have come up empty.

foobar crashes computer?

Reply #10
I cannot offer any technical knowledge over the suggestion to check sound card drivers, but here is a shot that might -- if it applies -- support the conjecture that it might be fb2k-related: try Peter's Boom player, http://perkele.cc/software/boom . I do not know of its internals, but I can only assume that it shares some of the codebase. Should it happen that Boom and fb2k are the only applications that seemingly bring the system down, then it would be more reason to be suspicious.

foobar crashes computer?

Reply #11
I am having the same problem since updating a couple months ago. Previously I was using v0.9.x I think...since I 'upgraded' this has been occurring. The funny thing is if I never open foobar my computer runs fine with no freezing. But if I open foobar and then close it (or just not have it playing) my computer freezes solid...If I leave foobar playing indefinitely everything is fine as well.
I have a hard time believing this is hardware related, and I am not looking for an older version of foobar to download again
b

foobar crashes computer?

Reply #12
Have you tried updating your audio drivers?

foobar crashes computer?

Reply #13
I've experienced the same problem under Win 7 on an Acer 7740-6656.

It also has periodic glitches when both graphics and sound are operating; it has Intel HD graphics which share system memory somehow.

Trying to figure out what's going on, coming up dead ends. The computer freezes mid-sound and repeats that sound ad infinitum, and it happens too fast for anything to get written to logs. It's like it causes a hardware freeze itself and the OS never even gets a shot at it.


foobar crashes computer?

Reply #14
If I was having an issue with some_app possibly being the cause of my computer freezing, then I would. . .

Install a program named Process Hacker . . . during setup, allow it to install the kernel driver and allow it to replace Windows Task Manager.

I would maximize Process Hacker window before I start foobar2000. Then run foobar2000 and carefully keep my eye on Process Hacker window especially the columns: "CPU", "I/O Total", and "Private Bytes" . . . . . if you double-click on a process name then a Properties page will open giving a lot of useful information.

This observation of all process activities on your system via the Process Hacker window will also give you feedback about the general state of your system . . . . is your system a bloatware infested piece of shit which has a ridiculous amount of unnecessary services, drivers and apps always on and madly competing for resources . . . . is there a rogue app which has locking handles on files and directories when foobar2000 runs . . . . and so on and so on.

Sooner or later, looking constantly at the Process Hacker window, you will discover a pattern . . . and from there you can commit to some test actions . . . for instance, before running foobar2000, select some "suspect" and "unnecessary" processes and 'Terminate' them . . . . Try terminating the anti-virus app (if you can), and terminate any services it also has running . . . . and so on and so on.

(I am a Windows XP user) . . . . Have you tried running MSCONFIG? (Start->Run->msconfig). Choose 'Diagnostic Startup' and reboot your computer and try running foobar2000 in that state.

Also, try uninstalling a driver (or drivers) you suspect may cause this and reboot and run foobar2000 again . . . . you have nothing to lose.

foobar crashes computer?

Reply #15
This is happening to me now too, like stavrogan above. After updating to the latest foobar version (1.2.9), I will periodically get complete system lockups while music is playing. Keyboard nor mouse will respond and the speakers will play a constant tone (from whatever song was playing) requiring me to manually turn off the PC.

Error log lacks any information because it apparently isn't able to detect the crash happening.

As a test I left my PC on for 3 days (as well as did some gaming), and it never crashed until I at last did an hour of running foobar. I've reverted to a previous version to see if it is fixed.

Sorry I can't give any specific information, but like I said, the W7 event logs lack any warnings after the crash outside of the standard "PC didn't shut down correctly" message.

Windows 7 Home Premium
i5 3550
8GB ram
GTX570
Mobo: Gigabyte Z77MX-D3H
integrated audio

foobar crashes computer?

Reply #16
This is happening to me now too, like stavrogan above. After updating to the latest foobar version (1.2.9), I will periodically get complete system lockups while music is playing. Keyboard nor mouse will respond and the speakers will play a constant tone (from whatever song was playing) requiring me to manually turn off the PC.

Error log lacks any information because it apparently isn't able to detect the crash happening.

As a test I left my PC on for 3 days (as well as did some gaming), and it never crashed until I at last did an hour of running foobar. I've reverted to a previous version to see if it is fixed.

Sorry I can't give any specific information, but like I said, the W7 event logs lack any warnings after the crash outside of the standard "PC didn't shut down correctly" message.

Windows 7 Home Premium
i5 3550
8GB ram
GTX570
Mobo: Gigabyte Z77MX-D3H
integrated audio


I started getting this recently too:

i5-3550
8gb ram
amd 280x
mb: biostar tz68a+
realtek audio with latest drivers.
win 8.1 64-bit

same symptoms as you describe, after playing music for a while I will sometimes get a total soundloop freeze requiring a reboot. I've had this happen twice, and both times after rebooting foobar wouldn't even open, saying the theme file could not be read, so I had to reinstall and re-configure it (I'm not using a bunch of crazy components either, just default ui + smplaylist)

I'm able to play bf4 for hours on end with no crashes or anything, so I don't think I've got unstable ram or anything like that.

foobar crashes computer?

Reply #17
Had the original poster, or the others with problems,  tried uninstalling and then reinstalling foobar? It might also be informative if they run a clean version which has had no components added.
Quis custodiet ipsos custodes?  ;~)

foobar crashes computer?

Reply #18
NVM, it did it today when I didn't have foobar open, so gotta be somethin else in my case