Latest post Tue, Jan 31 2012 9:35 AM by warezWally. 14 replies.
Page 1 of 1 (15 items)
Sort Posts: Previous Next
  • Fri, Jan 27 2012 7:52 PM

    BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Hi, trying to get the Trial of MC 6 to run on my PC, MC 5 & 5.5 were running ok before.

    Specs:

    AMD FX 4100 Quad Core 3.6Ghz
    4.00GB RAM
    Windows 7 64-Bit
    Nvidia Quadro FX 1700
    &
    Avid Mbox Mini

    I keep getting BSOD's on the "Initalizing Audio Plugins" part of the load process into Media Composer and the error is something along the lines of "Clock Interrupt on Secondary Processor Not Recieved in Time"... Sorry I can quote it exactly but my writing isn't quick enough.

    Using BlueScreenView I get this data:

    Crash List


    Created by using BlueScreenView

    Dump FileCrash TimeBug Check StringBug Check CodeParameter 1Parameter 2Parameter 3Parameter 4Caused By DriverCaused By AddressFile DescriptionProduct NameCompanyFile VersionProcessorCrash AddressStack Address 1Stack Address 2Stack Address 3Computer NameFull PathProcessors CountMajor VersionMinor VersionDump File Size
    012712-30654-01.dmp 27/01/2012 19:34:46   0x00000124 00000000`00000000 fffffa80`04d208f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a5e4c NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+4a5e4c         C:\Windows\Minidump\012712-30654-01.dmp 4 15 7600 262,144
    012712-33524-01.dmp 27/01/2012 17:43:19   0x00000101 00000000`00000031 00000000`00000000 fffff880`02d63180 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+705c0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+705c0         C:\Windows\Minidump\012712-33524-01.dmp 4 15 7600 287,360
    012712-29796-01.dmp 27/01/2012 15:58:42   0x00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+705c0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+705c0         C:\Windows\Minidump\012712-29796-01.dmp 4 15 7600 287,360
    012712-34694-01.dmp 27/01/2012 00:48:51   0x00000124 00000000`00000000 fffffa80`04cde8f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a5e4c NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+4a5e4c         C:\Windows\Minidump\012712-34694-01.dmp 4 15 7600 262,144
    012712-39421-01.dmp 27/01/2012 00:28:14   0x00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+705c0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+705c0         C:\Windows\Minidump\012712-39421-01.dmp 4 15 7600 262,144

     

    I sometimes get a proper BSOD report, sometimes the System just hangs and then reboots itself. I have tried both WITH & WITHOUT the Avid Mbox Mini (Supported Device, no?) and used the following graphics drivers from Nvidia on the FX 1700:

    190.38
    270.71
    275.89
    276.28
    276.42
    285.62 

    And they have all delivered similar, if not identical results... i.e: all crashing on "Initialzing Audio Plugins".

    I read somewhere that adding a bit of heat to the RAM will help; in the way of an extra 0.100v in BIOS, tried that... no change. I'm not overclocking at all. Any suggestions without having to buy a new graphics card, in theory there is just enough juice to make MC 6 work, right? 

  • Fri, Jan 27 2012 7:53 PM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Ok... my BlueScreenView Copy and Paste didnt come out very well... whats the best way to get that data from A to B?

  • Fri, Jan 27 2012 8:42 PM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    well with a username like that you might not get much help. but i did solve my BSOD problem going on to windows 7 forums and uploading my minump file that was created when i blue screened. usually its a driver problem, one of your drivers are probably not updated, wrong, or corrupt.

  • Fri, Jan 27 2012 9:24 PM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    I have downloaded the free 30 day trial and currently have 27 days left, do i really have to waste time talking about my username ? I dont use warez downloads, a friend of mine did almost religiously so i called him a warez wally (Where's Wally?.. or Waldo if you insist on being mistaken). Its tongue in cheek and,.. yes maybe foresight should've made me change it, I kinda hoped the 1st response wouldnt pick up on it, but hey...

    anyway...


    Which Windows 7 Forum do you speak of? There's quite a few and is that really the best option considering its an issue I'm only having with Avid? I'm not really in the mood to be told by a 12 year old that I need to change my PSU... Which I already HAVE done. 

  • Fri, Jan 27 2012 10:55 PM In reply to

    • Radman
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • UK
    • Posts 911
    • Points 10,620

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Peace Brother!

    Win10 64Bit / HP Z800-XW8200 / 5x Quadro M6000. 48 Gig Ram / Cubix Expander 4 / 2x 32TB SAS JMR Raid unit / Avid Artist | Avid Artist DNxIO. 3x 27"... [view my complete system specs]
  • Sun, Jan 29 2012 10:45 AM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Ok,

    I guess its right for me to excuse my impetuousness. I'm sorry.

    Has no-one else had this issue? is there something I've missed that I should look into?

     

    Chris

  • Sun, Jan 29 2012 10:59 AM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Hi Chris,

    According to the version matrix, 275.89 is the Nvidia driver you want, but since you already tried it with the same result, I'm guessing the driver isn't the problem.

    Just to be sure, check your version of Quicktime and if it's not 7.7, try installing that and see if it helps.

    If the driver and Quicktime are both good, then I'm at a loss to say what might be causing the problem.  AMD processors aren't supported, but I run them and so do tons of other people, so that may or may not be it.  

    Since it crashes at the audio plugins step, what audio card have you got?  Do you have any other audio stuff plugged in or installed?  Even something small like a USB mic or something like that?

    ciao,
    Carl 

    Media Composer 2024.2 w/Symphony/SS/PF options, HP Z-Book G6 17", i7-9850H 2.60GHz, 32gb RAM, NVIDIA Quadro RTX 3000, Blackmagic UltraStudio Mini... [view my complete system specs]

    "There is hardly anything in the world that some man cannot make a little worse and sell a little cheaper, and the people who only consider the price are this man's lawful prey."  - John Ruskin (1819-1900)

     

    Carl Amoscato | Freelance Film & Video Editor | London, UK

  • Sun, Jan 29 2012 6:03 PM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Its a fresh Win 7 Pro x64 install, however I have changed graphics cards since and also installed MC5 and uninstalled it... doubt this should be it.

    I have onboard Motherboard sound and also an Avid Mbox Mini (Which is probably the ONLY supported hardware I'm actually using)... On previous versions of Avid the onboard sound was ignored by the software as long as the Mbox was plugged in.

     And QuickTime is 7.7.1

  • Sun, Jan 29 2012 6:32 PM In reply to

    • vpcmike
    • Top 50 Contributor
    • Joined on Thu, Oct 13 2005
    • Baltimore, MD
    • Posts 1,669
    • Points 20,240

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    How about Wacom tablets or built-in cameras?  Have you tried the on-board sound with current drivers?

    System #1 - Mac Pro 12 Core 2.93, 24 GB RAM, 16 TB ISIS 5000 System #2 - Core i7 2600k, Windows 7, 16 GB RAM, Quadro 4000 System #3 - Dell Precision... [view my complete system specs]
  • Sun, Jan 29 2012 7:25 PM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    No cameras or tablets. Yeah I've tried both with and without the Mbox

  • Mon, Jan 30 2012 10:33 AM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Update...

    I did  bit of googling and found some people were having the same problem with Battlefield 2 (Close relation of Avid right? ha!) so they went to MSCONFIG and set the PC to boot on 1 core. I did the same and Avid 5 worked... did I mention that Avid 5 had the exact same problems too, even after a clean install of Win 7 with the approved and latest drivers? Windows Update decided to have a huge download and struck my computer with what I can only call Update Diarrhoea, mainly security updates, nothing touched the hardware so Im hoping the solution wasnt that simple. 

    I could get Avid 5 working fine on a Geforce 7600GT before, I have yet to re-test that, frankly I'd rather get my Quadro FX 1700 working fine seeing as it doesnt scream of a graphics card issue...

    Now to try that all again on MC 6... 

  • Mon, Jan 30 2012 10:54 AM In reply to

    • BarkinMadd
    • Top 25 Contributor
    • Joined on Fri, Nov 4 2005
    • Ontario, Canada
    • Posts 4,821
    • Points 63,225

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    Did you setup your FX 1700 configuration according to the release notes?

    Does MC 6 work when you use only a single core?

    MC 2021.6 | QT 7.7.9 | Continuum 2021 | Sapphire 2021 | Mocha Pro 2021 | Titler Pro 7.7 | Windows 10 Pro x64 (21H1) | System: Asus x299, i9-7940X (4.1GHz... [view my complete system specs]

    Steve

    ______________________

    www.nelliedogstudios.com

  • Mon, Jan 30 2012 11:21 AM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

  • Mon, Jan 30 2012 11:33 PM In reply to

    • jwrl
    • Top 25 Contributor
    • Joined on Thu, Oct 13 2005
    • Melbourne, Australia
    • Posts 8,460
    • Points 98,575

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    "There have been constant problems getting Avid MC 5 & MC 6 to run".  Interesting way to start that blog.  Hasn't been my experience, but then I don't have MC6.  Nor do I run games software or have Windows update running on my edit system.  Oh, and I don't use an AMD processor.

    I do have MC5x running on an Intel-based system, using an Avid approved display card and Avid approved third-party IO hardware.  I have not only not had "constant problems" getting Avid to run, I've never had problems getting Avid to run on the Windows platform since I started using Windows-based Avids in the Xpress DV days.

    Possibly "I have had constant problems getting Avid MC 5 & MC 6 to run" might have been a more reasonable start to your blog.

    MC 7.0.4 - Asus P6T Deluxe V2 mobo - Intel i7 920 2.66GHz - Windows 7 Ult64 SP1 - nVidia Quadro FX 1800 - 16 Gbyte low latency DDR3 RAM - Internal 8 Tb... [view my complete system specs]
  • Tue, Jan 31 2012 9:35 AM In reply to

    Re: BSOD MC 6 Caused by ntoskrnl.exe & message: clock interrupt error

    You're right, however I have to write an academic blog for university and it has to be in 3rd person. I'll re-phrase it soon.

Page 1 of 1 (15 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller