Plz Digi tech Help! Pro tools 9.0 BLUE SCREEN CRASH again

[shamanrock]

Because there are so many postings here, and THANK YOU to all who cared enough to post! I want to share with you the answer to my what seemed like a forever nightmare of a problem. I feel a tad silly to tell you all it was actually something simple. I know after all the blue screen crashes and clean windows 7 install and pro tools 9 installing to have it be this is, reminds me to slow down and dont panic and flip, there is a solution out there waiting to be had!

Oh but I do think all those blue screen crashes still had something to do with my main HD that was over 3 years old Its been replaced as of 3 days ago.

Me always trying to be organized I always keep all separate drivers and how to fix things with my pro tools installers. I had an out of date ilok installer.

The person who truly went out of his way without be asked to do so offered to trouble shoot with me. He pin pointed my problem, pretty quickly! He even helped me to be able to set my buffer size down to 128 sample, I could never go lower than 256 samples. And with more info he shared with me I think once I reset my ram timing in my BIOS correctly I'll be able to work at 64 samples.

His name is Mykhal C.

All I can say is this guy is truly an amazing person to have come into your life!

Thank you SO much Mykhal!

I owe you bigtime!

My deepest & sincerest gratitude to you brother! You ROCK!

All the best

Shamanrock







Digi I just reinstalled all PT n Ilock drivers a clean reinstall of PT 9 at 730am this morning as you can see I havent even slept trying to get PRO TOOLS 9 to work starting two days ago...

Upon Pro Tools 9.0 reboot I get Microsoft register has stopped working.
Then I get Pace reister retrieved an error -529697949.

How am I suppose to NOT blow my stack?

How many clean windows 7 install do you want me to do? This will be my 3rd Windows 7 install if you please dont tell me the solution to your product. I cant afford to keep wasting evey day n night to make your product work. Im in the middle of an album and time is of the essence.


[QUOTE=shamanrock;1784906]HERE I go again.... I had a second blue screen crash loading soundblaster driver... so I deleted soundblaster driver n rebooted I opened pro tools 9.0 it won't open again. Says same as today before I did a clean windows 7 install.
Problem signature:
Problem Event Name: APPCRASH
Application Name: ProTools.exe
Application Version: 9.0.0.121
Application Timestamp: 4cc25876
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16695
Fault Module Timestamp: 4cc7ab86


Plz help!!!!!!!!!!



Heres where I am at. 1st. Ive built a brand new computer and everything inside is brand new and I mean everything not even 4 months old, except my main hard drive which I just replaced three days ago, because I had so many blue screen crashes I thought its my hard drive cause its over 3 years old.
So I replaced it as I just mentioned.

Last night pro tools 9.0 was working this morning it stopped. Ive tried deleting prefs n data base no luck. I reinstalled pt 9 no luck I did a windows 7 repair no luck. I just spent hours doing another windows 7 install from scratch.

I installed explorer 9, adobe flash, quick time, open office, kaspersky. Everything is fine.
Then I installed 3 drivers ilock n driver set up & mbox2 pro driver always with a reboot. Computer is working great.
I just installed Pro Tools 9.0 it installs good, then upon reboot I get a BLUE SCREEN CRASH! I can't believe it.

Before I could shut down computer from total dump in blue screen crash mode my computer rebooted on its own then pro tools finished installing its final phase and now pro tools launches and I hear sound ect...

My concern is Ive been down this road where I had 7 to 8 blue screen crashes in a row within the last couple of months with pro tools 9.0 as Ive posted in the past. I know its gonna blue screen crash on me again.
Please DIGI Tech tell me whats going on? This cant be right with your world class product?


HELP!!!!!!!!

Thank you
Shaman

[shamanrock]

Originally Posted by shamanrock

Ok
Ive taken a deep breath.

Heres where I am at. 1st. Ive built a brand new computer and everything inside is brand new and I mean everything not even 4 months old, except my main hard drive which I just replaced three days ago, because I had so many blue screen crashes I thought its my hard drive cause its over 3 years old.
So I replaced it as I just mentioned.

Last night pro tools 9.0 was working this morning it stopped. Ive tried deleting prefs n data base no luck. I reinstalled pt 9 no luck I did a windows 7 repair no luck. I just spent hours doing another windows 7 install from scratch.

I installed explorer 9, adobe flash, quick time, open office, kaspersky. Everything is fine.
Then I installed 3 drivers ilock n driver set up & mbox2 pro driver always with a reboot. Computer is working great.
I just installed Pro Tools 9.0 it installs good, then upon reboot I get a BLUE SCREEN CRASH! I can't believe it.

Before I could shut down computer from total dump in blue screen crash mode my computer rebooted on its own then pro tools finished installing its final phase and now pro tools launches and I hear sound ect...

My concern is Ive been down this road where I had 7 to 8 blue screen crashes in a row within the last couple of months with pro tools 9.0 as Ive posted in the past. I know its gonna blue screen crash on me again.
Please DIGI Tech tell me whats going on? This cant be right with your world class product?


HELP!!!!!!!!

Thank you
Shaman

HERE I go again.... I had a second blue screen crash loading soundblaster driver... so I deleted soundblaster driver n rebooted I opened pro tools 9.0 it won't open again. Says same as today before I did a clean windows 7 install.
Problem signature:
Problem Event Name: APPCRASH
Application Name: ProTools.exe
Application Version: 9.0.0.121
Application Timestamp: 4cc25876
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16695
Fault Module Timestamp: 4cc7ab86


Plz help!!!!!!!!!!


SiSoftware Sandra
General Information
Windows System : Microsoft Windows Vista Business Media Center 6.01.7600
Platform Compliance : Win64 x64
Full Name : Windows 7 Professional 6.1.7600
Kernel Type : Multiprocessor Free
BackOffice Components : No
Small Business Components : No
Terminal Services Components : No
Compute Cluster Components : No

Data Execution Prevention (DEP)
Supported by CPU : Yes
Applications Protected : Yes
Drivers Protected : Yes
Virtual Machines and Runtime Engines
.NET Framework : 3.5.30729
.NET Framework : 3.0.30729 (SP2)
Windows Communication Foundation : 3.0.4506
Windows Presentation Foundation : 3.0.6920
Windows Workflow Foundation : 3.0.4203 (SP2)
.NET Framework : 2.0.50727 (SP2)
Default Key Applications
Web Browser : Internet Explorer 9.00.7600.16385
Address Book : Address Book 6.01.7600.16385
Session Settings
Time Since Start-Up : 18 minutes(s) 9 seconds(s)
OS Properties
Debug Version : No
Security Present : No
Remote Terminal Session : No
Boot Features
Boot Type : Normal
Automatic Update
Active Service : Yes
Regional Settings
User Default Locale : 1033
Country : United States
Language : English (United States)
Currency : $
Time Zone : Pacific Daylight Time
ANSI Code Page : 1252
OEM Code Page : 437
Operating System Folders
Windows Folder : C:\Windows
System Folder : C:\Windows\system32
Programs Path : C:\Program Files
Programs Path : C:\Windows\system32;C:\Windows;C:\Windows\System32 \Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\; C:\Program Files (x86)\QuickTime\QTSystem\;
Temporary Folder : C:\Windows\TEMP
Performance Tips
Tip 1300 : Enter your company name or "Home" instead of "Unknown".
Tip 1324 : .NET Framework 1.1 not installed. Install to run legacy .NET applications.
Tip 1327 : Java Runtime Engine not installed. Install it to run the current Java applications.
Tip 2 : Double-click tip or press Enter while a tip is selected for more information about the tip.

[albee1952]

Starting a new thread every other day for the same problem is not going to help you(or anybody else). BSOD can be caused by a lot of things, and most of them are not Pro Tools. Its time to start writing down what the BSOD screen says and googling it. Maybe you have a bad stick of RAM? Or maybe a bad motherboard? Personally, I don't think you need help from Avid. I think you need help from a serious PC expert. BTW, this is not the part of the Sandra report folks need to help. Look at some other posts to find out the right style of report and re-read the instructions in the Help us Help you thread. One thing I would do is remove all the RAM and try one stick in slot #1(not always the first slot so read the booklet). If that boots and runs okay(probably won't run PT), then try the next stick until all have shown you that they will let the machine boot, and all in roughly the same amount of time. Then I would run memtest on the system to test all the RAM(a freebie utility). I still don't like that I read Vista Media Center in that report.

[Russell Smith]

Although like Albee stated above , your BSOD is likely due to a hardware issue and NOT Pro Tools you are using an unsupported operating system and to be honest one that is not suited at all to audio production.

Also if you get a chance to post the correct portion of the Sandra report I am sure we can have a look at it for you.

[shamanrock]

Originally Posted by Russell Smith

Although like Albee stated above , your BSOD is likely due to a hardware issue and NOT Pro Tools you are using an unsupported operating system and to be honest one that is not suited at all to audio production.

Also if you get a chance to post the correct portion of the Sandra report I am sure we can have a look at it for you.

Russel what do you mean unsupported? I asked Avid from the start when pro tools 9 was coming out to please give me motherboard and processor thats compatible. You know what Avid told me? Sorry theres only specs posted on Avids site for HD users! And to go to the Avid forum and see what other people are using!

How lame is that? And look where I'm stuck at now in the middle of recording my album, which by the way I sing, write the songs, play all the instruments and engineer, if this is not enough now I have to be computer trouble shooter when Avid should have posted from the get go whats frigin compatible.
Just like 3 years ago I built my computer to digis requirements they had me at the time build a dinosour computer that I lived with for three years and still had all sorts of problems to overcome one by one as I did...

[shamanrock]

Originally Posted by albee1952

Starting a new thread every other day for the same problem is not going to help you(or anybody else). BSOD can be caused by a lot of things, and most of them are not Pro Tools. Its time to start writing down what the BSOD screen says and googling it. Maybe you have a bad stick of RAM? Or maybe a bad motherboard? Personally, I don't think you need help from Avid. I think you need help from a serious PC expert. BTW, this is not the part of the Sandra report folks need to help. Look at some other posts to find out the right style of report and re-read the instructions in the Help us Help you thread. One thing I would do is remove all the RAM and try one stick in slot #1(not always the first slot so read the booklet). If that boots and runs okay(probably won't run PT), then try the next stick until all have shown you that they will let the machine boot, and all in roughly the same amount of time. Then I would run memtest on the system to test all the RAM(a freebie utility). I still don't like that I read Vista Media Center in that report.

Thanks Ill try with the ram 1st, all I know is everything is pretty darn new in every part of my computer...

[Darryl Ramm]

Originally Posted by shamanrock

Russel what do you mean unsupported? I asked Avid from the start when pro tools 9 was coming out to please give me motherboard and processor thats compatible. You know what Avid told me? Sorry theres only specs posted on Avids site for HD users! And to go to the Avid forum and see what other people are using!

/*whining snipped*/.

I think people are confused by your Sandra report that both reports Windows Vista (i.e. the unsuitable for recording comment) and Windows 7 x64 (quite suitable). This has already been touched on elsewhere. If you've properly installed or upgraded to Windows 7 then you should be OK.

As others have mentioned please post the usual Sandra report in future.

And as others have mentioned you need to focus on the blue screen error, and start by hunting that down elsewhere. The error messages or crash dumps often can point quickly to a problem (e.g. a faulty controller or device driver). This is part of the responsibility you take on when you build your own Windows machine. I've had to install Windows debug kernels with symbols, collect crash dumps, pick through things to work out what's wrong. While building your own PC likely works most of the time I think it is a fantasy to assume you can always just plug things together and they will work and when they don't its somebody else's fault -- like Avid who you seem to be blaming for something that may have nothing to do with them.

What _exactly_ is the BSOD message you get. All of it, text and addresses etc... Is it always exactly the same (addresses and all).

Darryl

[albee1952]

Originally Posted by shamanrock

Thanks Ill try with the ram 1st, all I know is everything is pretty darn new in every part of my computer...

New doesn't mean much. Anyone that has built a dozen or more computers has likely run into a bad mobo, bad RAM, bad power supplies and more. Sometimes things just break

[critza]

Id also like to see the "proper" sandra report.

Start Sandra > Favourites Tab > Create Report > Click Next until you come to File Types and choose Format .txt > Save the report where you can acess it easily and when it´s finished, just open the txt document and copy paste it into your thread here.
Please provide what Soundcard you are using and what driver it has.


This will give you a good start.

[shamanrock]

Originally Posted by Darryl Ramm

I think people are confused by your Sandra report that both reports Windows Vista (i.e. the unsuitable for recording comment) and Windows 7 x64 (quite suitable). This has already been touched on elsewhere. If you've properly installed or upgraded to Windows 7 then you should be OK.

As others have mentioned please post the usual Sandra report in future.

And as others have mentioned you need to focus on the blue screen error, and start by hunting that down elsewhere. The error messages or crash dumps often can point quickly to a problem (e.g. a faulty controller or device driver). This is part of the responsibility you take on when you build your own Windows machine. I've had to install Windows debug kernels with symbols, collect crash dumps, pick through things to work out what's wrong. While building your own PC likely works most of the time I think it is a fantasy to assume you can always just plug things together and they will work and when they don't its somebody else's fault -- like Avid who you seem to be blaming for something that may have nothing to do with them.

What _exactly_ is the BSOD message you get. All of it, text and addresses etc... Is it always exactly the same (addresses and all).

Hi & thank you.

During blue screen crash it says

IRQL not less or equal blue screen error

I will shortly post a sandra report.

I also just ran a mem test for 6 hours i got no faulty errors.

I would like you to know I get when pro tools 9.0 wont launch

APPS CRASH
Also Ive gotten this twice when pt 9.0 is in final phase of rebooting after clean install.

Microsoft register server has stopped working.
also pace register returned an error - 529697949.

Shaman

Darryl