BSOD while running Sibelius 7

Have you gone to the location specified by the dump file?

Remove the driver in Safe Mode:

• Safe Mode

If the folder which the driver is, can't be found, then you may need to unhide the file:

• File and Folder - Hide or Unhide

I found the location of the driver file (stdriver64.sys) and deleted it, but I still keep getting the BSOD when switching the audio card to my M Audio profire.

Any other thoughts / suggestions?

Many thanks,

Peter

Did you install the driver for Windows 7 64-bit SP1?

M-AUDIO - Drivers and Software Search

Could also please upload the recent dump files and post a screenshot of your Device Manager with the error code showing:

• Screenshots and Files - Upload and Post in Seven Forums

Yes, I did download and install the latest M Audio driver (uninstalled and reinstalled it as well, without success). Attached are the screenshot and a recent crash dump.

Notice that I can't make my computer crash anymore as there is no sound card at all, so I can't switch to the M Audio soundcard in Pro Tools.

Attachment 241745

Attachment 241746

I don't trust using registry cleaner option of any program, trusted or not, they usually lead to further complications.

For the corrupted system file errors run:

• SFC /SCANNOW : Run in Command Prompt at Boot

This is a completely safe process, and will scan for any corrupted files and then attempt to fix them from within Windows, otherwise you may need to perform a Repair Install with a Windows 7 DVD (will provide a link to a .ISO file if needed).

If you feel better having a System Restore point to revert to then:

• System Restore Point - Create

You may want to run a full scan with any AV suite you have installed and then:

• Malwarebytes | Anti-Malware
• Anti-rootkit utility TDSSKiller

Remember to download the free version of Malwarebytes, not the free trail; untick the free trail during the installation.

Code:

BugCheck D1, {13a1ff68, 2, 0, fffff880046131e0}

*** WARNING: Unable to verify timestamp for stdriver64.sys
*** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
Probably caused by : stdriver64.sys ( stdriver64+131e0 )

Followup: MachineOwner
---------

All the BSODS pointed to the same driver (stdriver64.sys), do the BSODs only occur when you try to use Pro Tools or do they occur randomly without any input from yourself?

Code:

Image path: \SystemRoot\system32\DRIVERS\stdriver64.sys
    Image name: stdriver64.sys
    Timestamp:        Fri Mar 18 00:17:45 2011 (4D82A4A9)

Remove Pro Tools and then see if you have any more BSODs:

Code:

Start Menu\Programs\Avid\Pro Tools

Windows may be pointing to that driver if the program uses that driver when you execute the program (just a thought).

Many thanks Bluerobot - found the culprit!

I was a screen video capturing program from NCH software called "Debut Video Software". I had my suspicions as I'd installed it last week, needed something to capture a video screen shot. After I installed it, I found that it had installed several dozen (!) other audio and video programs, which I had already uninstalled.

Bleh - buyer beware. CNet (which I usually trust) had recommended them.

NCH Toolbox - CNET Download.com

Well I'm just happy that I am up and running again. I've been to 'save' this computer by initially just installing Pro Tools, but my primary DAW has been in the shop for months now with broken motherboard so I had no choice.

Thank you blue robot and everyone else! I'll mention you in the credits.

Your welcome :) if you get no more BSODs then you can mark this thread as solved if you like :)