Solved BSOD when saving file, error 0x50

[thereynolds]

Hi,

I sometimes get a bluescreen error when I try to save a file to the hard drive using a VST Host (musical instrument host) software called brainspawn forte (www.brainspawn.com). This software is a "host" for VST software instruments. The host runs, then loads DLLs that are each other software instruments (i.e. one DLL might be a Piano, the next an organ, then a synth, then a drum machine, all loaded within forte, the host). I'm not sure forte is the cause of the problem, but the bluescreen shows up when I try to save a file I have updated, and it does not show up all the time. When the error does happen, it's always during a file saving operation, but it doesn't happen with every file saving operation. Probably 1% of the time, maybe?

I'm running the software on an Open Labs Neko (www.openlabs.com). This is significant because there are some proprietary Open Labs hardware panels, and drivers to go along with those panels. The problem could be related to these drivers (I'm suspect it could be, but not sure).

Hoping to get some help identifying which program or DLL is causing the blue screen.

Here's my system description:

Open Labs Neko Panels
Gigabyte GA-P55A-UD3 rev 1.0 mobo
8GB memory
Intel i7-870 processor
Windows 7 x64
Crucial C300 256GB SSD (boot disk) connected to Sata3 (6Gb/s) port
Two 2GB HDs running in RAID1 on Sata2 port
One additional HD drive connected to Sata2 port (clone of Crucial C300 SSD)
Several proprietary Open Labs panels connected to USB port on mobo
M-Audio 192 PCI Sound Card
ATI/AMD Radeon Video Card (X550 I think, unremarkable)
Mackie Onyx USB sound card
Touch screen monitor (Galaxy?), plugged into USB for touch feature

Thanks in advance for the assistance!

-Mike

 

[zigzag3143]

Hi,

I sometimes get a bluescreen error when I try to save a file to the hard drive using a VST Host (musical instrument host) software called brainspawn forte (www.brainspawn.com). This software is a "host" for VST software instruments. The host runs, then loads DLLs that are each other software instruments (i.e. one DLL might be a Piano, the next an organ, then a synth, then a drum machine, all loaded within forte, the host). I'm not sure forte is the cause of the problem, but the bluescreen shows up when I try to save a file I have updated, and it does not show up all the time. When the error does happen, it's always during a file saving operation, but it doesn't happen with every file saving operation. Probably 1% of the time, maybe?

I'm running the software on an Open Labs Neko (www.openlabs.com). This is significant because there are some proprietary Open Labs hardware panels, and drivers to go along with those panels. The problem could be related to these drivers (I'm suspect it could be, but not sure).

Hoping to get some help identifying which program or DLL is causing the blue screen.

Here's my system description:

Open Labs Neko Panels
Gigabyte GA-P55A-UD3 rev 1.0 mobo
8GB memory
Intel i7-870 processor
Windows 7 x64
Crucial C300 256GB SSD (boot disk) connected to Sata3 (6Gb/s) port
Two 2GB HDs running in RAID1 on Sata2 port
One additional HD drive connected to Sata2 port (clone of Crucial C300 SSD)
Several proprietary Open Labs panels connected to USB port on mobo
M-Audio 192 PCI Sound Card
ATI/AMD Radeon Video Card (X550 I think, unremarkable)
Mackie Onyx USB sound card
Touch screen monitor (Galaxy?), plugged into USB for touch feature

Thanks in advance for the assistance!

-Mike

Mike

You uploaded the application instead of the date

Try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and which one was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[thereynolds]

Oops. 2nd try, hopefully correct this time. I still followed the original instructions, if this isn't correct, I'll follow the new instructions you posted immediately above. Thanks for your help and your patience.

-Mike

 

[zigzag3143]

Oops. 2nd try, hopefully correct this time. I still followed the original instructions, if this isn't correct, I'll follow the new instructions you posted immediately above. Thanks for your help and your patience.

-Mike

These were Related to MAudioDelta.sys M-Audio Delta PCI driver from Avid Technology, Inc. I would remove it to test.

 

[thereynolds]

Thanks for the help. Is there a place I can learn to make this determination myself, if I have more blue screen crashes?

Thanks very much.

-Mike

 

[zigzag3143]

Thanks for the help. Is there a place I can learn to make this determination myself, if I have more blue screen crashes?

Thanks very much.

-Mike

Mike it is a question of practice.

You can download and run an app called blue screen view (from nirsoft) but it isnt the gold standard.

 

[thereynolds]

I see, Obi Wan! I hope I don't have so many blue screens that I become a master like you! I had found Blue Screen View, but when I reviewed it, I did not conclude the driver that you did. By the way, I think you were correct. I removed that sound card, and used a different sound card, and the problem went away. Not sure if it's ultimately the driver, or a resource conflict (seems in these new systems, it's very difficult to provide a unique IRQ to that card), but it's definitely related to the driver/card you identified.

Thanks again.

-Mike

 

[zigzag3143]

I see, Obi Wan! I hope I don't have so many blue screens that I become a master like you! I had found Blue Screen View, but when I reviewed it, I did not conclude the driver that you did. By the way, I think you were correct. I removed that sound card, and used a different sound card, and the problem went away. Not sure if it's ultimately the driver, or a resource conflict (seems in these new systems, it's very difficult to provide a unique IRQ to that card), but it's definitely related to the driver/card you identified.

Thanks again.

-Mike

Sorry Mike

The gold standard is win debugger. It is more complex and requires you to download symbols but if you want it right, its the tool to use.

Let me know (pm) if you need help.

 

[thereynolds]

Thank you so much for the tip on Win Debugger and for mentioning the symbols. I'm not a programmer, but I was able to find the Win Debugger and within an hour so, successfully run it and see the correct offending driver. I cannot tell you how much I wish I had found out about this years ago... so many blue screens over the years... thanks so much for your help, and for all the help you and others here provide to folks in need. Very cool.

-Mike