BSOD after exporting from music DAW

[stuinfinity]

Hi there, I've been getting lots of bsod since around xmas to the point where it was so bad I done a clean install of win 7 x64. and after that I still was continuing to get bsod which that lead me to believe it was hardware related so I removed my ram sticks n tried each one at a time adding them back in t see if it was faulty ram and for around 2 months I thought I had found the problem and that it was one of the ram sticks because I was no longer getting any blue screens.

I'm a music producer and i use fl studio 11 software and now more often than not I am getting a bsod when I export a track when it gets to 100%. I only just tonight finally was able to produce a minidump after using the cmd method shown in one of the threads on here as before I wasnt even after setting it up properly

Anyway I have attached the zip file with the info from the diagnostic tool and I hope someone will be able to help me

thanks in advance

 

[andrew129260]

How are things in safe mode?

Is it only when you use the FL studio software?

What are your full pc specs?

 

[derekimo]

Additionally,

Your dump is pointing to,

[B][COLOR="Blue"]BugCheck 50[/COLOR][/B], {ffffffff89992e20, 0, fffff80002eb0798, 5}

Unable to load image MAudioFastTrackPro.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MAudioFastTrackPro.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioFastTrackPro.sys

Could not read faulting driver name
Probably caused by : MAudioFastTrackPro.sys ( MAudioFastTrackPro+6663 )

Followup: MachineOwner

Driver Reference Table - MAudioFastTrackPro.sys

start             end                 module name
fffff880`06f3b000 fffff880`06f6a000   MAudioFastTrackPro T (no symbols)           
    Loaded symbol image file: MAudioFastTrackPro.sys
    Image path: MAudioFastTrackPro.sys
    Image name: MAudioFastTrackPro.sys
    Timestamp:        [COLOR="Red"]Thu May 23 05:56:01 2013[/COLOR] (519E11E1)
    CheckSum:         00039242
    ImageSize:        0002F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You could try updating that,

M-AUDIO - Drivers and Software Search

A little info on the BugCheck,

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Testing your Ram would be a good idea too.

   Information

MemTest86+

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with MemTest86+

 

[stuinfinity]

i figured it out on my own in the end came to same conclusion as you also found a forum thread with loads of ppl having similar issues with the drivers for win 7 and that interface and i think because the product is a about 5 years old now n avid buying over m-audio avid are not really bothered about doing a proper working no buggy driver for the fast track range

so only option is to buy a new interface which i have done thanks for the reply anyway

 

[derekimo]

You're welcome, glad you found a new interface.