Skip to main content

Crash Problems with Pro Tools on Windows XP

My main DAW is Cubase SX3 which is running on a Dual - Dual Core 285 Opteron system, Windows XP Pro, SP2. The system also includes two Lynx AES16 Cards.

I wanted to have the option of a Beat Detective type function for use on tightening up the odd track. I was choosing between PT-LE W Music Prod'n toolkit and Sonar 6. I was hoping that Cubase was going to insert this functionality with the release of Cubase 4 but they didn't

I ended up choosing PT because; (1) it was the DAW that I first started with (2) i still had old PT files that I wanted to access (3) PT is the most common DAW and I thought it would help with any people who brought me PT files to work on.

I chose M-Powered because it was the cheapest way into PT. I chose the M-Audio Transit USB interface ($69). After installing both the interface and PT I started to get some major crashes and mulitple Blue Screens of Death. Error messages included;

IRQL_NOT_LESS_OR_EQUAL

PFN_LIST_CORRUPT

BAD_POOL_HEADER

Anyways I removed a few programs, the drivers for the transit and PT and a couple of other things. After trying variations of software installations I determined that PT 7.1.1 was crashing my system. Everything that I removed in testing is now reinstalled with exception to PT and I am running very smooth. When I install PT - boom - BLue Screen of Death.


Anwyays, any suggestions/probing questions would be greatly appreciated, thanks.

Comments

mark_van_j Wed, 11/15/2006 - 16:03
Issues may involve the following:

- IRQL NOT LESS OR EQUAL:

1) Hard Drives are connected to on board RAID chip on the motherboard. They should be connected to the primary IDE channel. You allso may need to uninstall the RAID drivers.

In one case this was solved by disabling the RAID controller and the onboard soundcard through the BIOS.

2) IRQL is ususally associated with a memory problem ...




- PFN_LIST_CORRUPT

1) This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

Go HERE http://www.techspot.com/vb/topic35103.html and follow the instructions for testing your page file/hdd.

Also, try running your system with just one stick of ram. Try putting the ram in a different dimm slot.



- BAD POOL HEADER

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/1140.asp




I did the research, now you decide what to do... 8)






I have a hunch it might have something to do with the m-audio drivers... There are also 2 references that it might be your RAM... Weird stuff going on here...
x