BSOD loading session in pro tools 10.3.7, error 0x000000c5


  1. Posts : 1
    windows 7 64 bit
       #1

    BSOD loading session in pro tools 10.3.7, error 0x000000c5


    Hi got BSOD when I want to loading my saved session in pro tools 10.3.7.

    Here my minidump from bluescreenview

    ==================================================
    Dump File : 100113-20202-01.dmp
    Crash Time : 2013-10-01 23:32:28
    Bug Check String : DRIVER_CORRUPTED_EXPOOL
    Bug Check Code : 0x000000c5
    Parameter 1 : fffff802`00000001
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff800`032089bc
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75b80
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
    Processor : x64
    Crash Address : ntoskrnl.exe+75b80
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\100113-20202-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 292*992
    Dump File Time : 2013-10-01 23:34:18
    ==================================================


    Please help me.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the Forum.
    Code:
    Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
    Debug session time: Wed Oct  2 03:32:28.430 2013 (UTC + 6:00)
    System Uptime: 0 days 4:40:18.616
    BugCheck C5, {fffff80200000001, 2, 0, fffff800032089bc}
    *** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
    BUGCHECK_STR:  0xC5_2
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Norton is a very frequent cause of BSOD's. Please uninstall it and use Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

       Note
    Do not start the trial version of MalwareBytes
    You may also take a look at:

    ------------------------
    Make scans with these tools -

    ------------------------
    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow - read here

    Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
    ------------------------
    Reduce the start-up items, Antivirus software is basically whats required.

    ------------------------
    Code:
    DAEMON Tools Lite	"d:\programy\daemon tools lite\dtlite.exe" -autorun	Kompiutor\Tomek	HKU\S-1-5-21-1928837462-2173985278-3035484289-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
    Daemon Tools (also Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.

    As an alternative:

    If you are overclocking any hardware, please stop and uninstall the software below:

    GPCIDrv64.sys Thu Jul 10 18:58:31 2008 (48760777)
    Gigabyte Easy boost related driver
    Driver Reference Table - GPCIDrv64.sys

    NTIOLib_X64.sys Mon Oct 5 07:28:48 2009 (4AC94BD0)
    MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
    Driver Reference Table - NTIOLib_X64.sys
    ------------------------
    Test and Diagnose RAM Issues with Memtest86+:

       Tip

    • Pay close attention to Part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.


    Let us know the results.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:55.
Find Us