PT10, Blue Screen of Death on startup

[NickRyanAudio]

Had PT10 running on computer running fine but would freeze and/or run very slow due to being only 2 Gigs of DDR2 1066 RAM. So did major overhaul, basically new computer.

ASUS M5A97 motherboard
8 Gigs DDR3 1866 Ram
AMD FX6100 6-core CPU 3.3Ghz.
Vantec Firewire PCIe card

Did a fresh install of Windows 7 64x. Presonus Firestudio running fine and Pace ilok drivers installed. But PT10 will load plug ins, then when loading AIR plug ins (none specific, different each time) I will get BLOD and computer will restart.

I've already tried the IEEE 1394 legacy driver trick and still doesn't work.

Does anyone have other suggestions?

[imdrecordings]

BSOD's are hardware related.
What BSOD code is your PC throwing?
Example: 0x00000??

[albee1952]

Are there plugins in the session or is this happening when opening Pro Tools, but before you open a session? If PT opens but sessions crash it, try holding the SHIFT key while opening sessions. That will disable all plugins(make them inactive). If that works, then its a plugin that needs to be removed or updated. Otherwise, I would check Pace Interlok drivers. Posting a Sandra report on the new computer might also help.
Help us Help You - READ THIS Before Posting!

[NickRyanAudio]

What BSOD code is your PC throwing?

I'm headed up to the studio tonight to check that out, is there a website that I can enter that code in, to see what piece is causing the crash?

And it's a Clean install, no session.

[imdrecordings]

Dropping that code into Google usually get's you right to the fix or a detailed explanation of the problem or reason for the BSOD.
Are you overclocking ram or CPU?
Also, what interface are you using?

Originally Posted by NickRyanAudio

I'm headed up to the studio tonight to check that out, is there a website that I can enter that code in, to see what piece is causing the crash?

And it's a Clean install, no session.

[NickRyanAudio]

The code on the bottom of the BSOD is:
*** STOP: 0x00000101

I'm searching google for what this code means now. I'm not overclocking, using Presonus Firestudio (drivers recent and tested using Reaper, google chrome, and standard windows noises; all works fine)

I'm reading that the code is CPU based, that a processor core on a multi-core system stops responding. I checked AMD for drivers/patches for the FX6100 but I'm only finding a couple things for non-specific processors that aren't labeled about what they do, and I don;t think blindly installing drivers and patches will be any better.

[Lefthook77]

I'm having the same issue... different mobo but same processor. Not good...

Originally Posted by NickRyanAudio

Had PT10 running on computer running fine but would freeze and/or run very slow due to being only 2 Gigs of DDR2 1066 RAM. So did major overhaul, basically new computer.

ASUS M5A97 motherboard
8 Gigs DDR3 1866 Ram
AMD FX6100 6-core CPU 3.3Ghz.
Vantec Firewire PCIe card

Did a fresh install of Windows 7 64x. Presonus Firestudio running fine and Pace ilok drivers installed. But PT10 will load plug ins, then when loading AIR plug ins (none specific, different each time) I will get BLOD and computer will restart.

I've already tried the IEEE 1394 legacy driver trick and still doesn't work.

Does anyone have other suggestions?

[beemerbuckeye]

I am having the exact same problem with that processor. It has made it to various points when loading plugins, but always fails somewhere in the "Air" plugins. Things that I have tried so far include:

Disabling Turbo Boost (BIOS)
Disabling C6 Support (BIOS)
Disabling C1e Support (BIOS)
Using Legacy 1394 Drivers
Running as Administrator
Changing Processing priority to background services
Making sure all drivers are the most up to date
Changing power management settings in Windows
Updating BIOS, and system drivers

I have ran stress tests using Prime95 to make sure that the system is working fine, all hardware performs fine through these tests.

The BSOD states "A clock interrupt was not received within the allotted time".

Essentially, one of the processing threads is becoming non responsive on a core, and eventually this leads to the BSOD. I have thought about setting processing affinity on ProTools.exe to use only one processor core, but have not tried it yet. It would seem that would be counter-productive, as I am sure Pro Tools would crawl with only one core available.

[Lefthook77]

Just tried single processor affinity... no go.

[beemerbuckeye]

Downloaded AMD Overdrive which also provides access to the Core Boost stuff and disabled it. Also need to disable the Cool & Quiet stuff. All of this changes the clocking frequency, so the thought was to get the processor to run stable at its advertised frequency. However, the system is still freezing while loading pro tools. I have seen it freeze up, and I have seen it hang then Blue Screen. Doing some more troubleshooting, running games and benchmarking applications to try to narrow it to a Pro Tools issue, or see if it in fact is hardware (CPU) related.