6.1.1 continues to lockup. GETTING DESPERATE...

[31Hz]

Ok, i've left (and answered) posts recently re: 6.1 & 6.1.1 upgrade. well, 6.1.1 is at it again, consistently locking up locking up durig playback after 1. and hour of usage, 2. gradually sooner everytime after until i install AGAIN.

i've done my xp tweaks. I've trashed dae prefs and app data under my username. after crashes, i get .tfx files in my dae folder like:

DigiclikCkRTFact
DigiTmCETCEXFact

and my personal fav:

DigiFkUpF33EFact.

that one sums it up. no kidding.

I actually finally spent a 1/2 day deleting & disabling my raid array (onboard promise controllers) that have always worked fine for 5.3.1 & just stuck em in IDE slots.

my stats (again)

Asus p4b533E MB, 845 chipset.
p4 2.2
1 GB 2700 DDR
maxtor drives (3 60 gig, 1 120 Gig via firewire)
001
installed the ASIO & wavedrivers

I really wish I could get back to work, had to borrow a rig from a friend to finish my sessions. any ANY thoughts are appreciated.

has happened when running reason, but I don't think that's buggy...

thanks 31

[msog]

I guess since you say you have done the XP tweeks, the I assume you have your "page filing" size set to 1024. This is a must with 1gig or more of RAM.

[da BaSsTaRd!]

PT has so many problems related to disk activity. no wonder they limit PT to 32 tracks.

anyway, this won't help you because you're running an intel system, but PT6.1 was locking up on me until i installed a VIA bus mastering utility. the lockups are gone, but now i keep getting 6045 errors. that's not nearly as bad, but still a pain in the buttocks. i believe the only fix for me is to get a new hard drive or promise controller or something.

moral of the story: check disk related things on your setup...

[PDEES]

prior to loading 6.1/6.1.1, I had no issues with my HD errors. Now I must run 1024, level 4 or 8, etc. Yet my systems settings are low. And I am talking about editing just several tracks of drums, not tons of tracks with plug in galore...So I go with the post above about cranking up settings with 1g ram...my 100 Naira worth...

[tele_player]

Not quite a 'must', it's just as good to disable virtual memory completely.

I guess since you say you have done the XP tweeks, the I assume you have your "page filing" size set to 1024. This is a must with 1gig or more of RAM.

[msog]

About the 1024...this is not the hardware buffer size set in the Playback engine. this is a setting within windows xp itself. Right click on "my computer" select "advanced" then select "settings" from the "performance" category (the first one listed) then select "advanced" again. Now, at the bottom right of the screen you'll see a button called "change" under the "virtual memory" section. This will need to be changed to either 1024meg or 0meg...digi suggests one or the other but the 0 setting did not work for me. 1024 did the trick.

Jim

[PDEES]

thanks for the clarification. I will check this out this pm. Saw Rail had done said something similar in another post, but didn't know what he meant by "set the Processor scheduling to Background services"

[31Hz]

Wow, thanks a lot for your response, guys. If nothing else, it keeps me from pulling my hair out!!

RE: VRAM, I locked my page file settings at 1065 for some reason, rather than 1024. I'll move to 1024. Maybe then I'll try 0.

***
I've been holding for support. Their recommendations:
1.try running session on *just* the system drive - see if it's a drive issue
2.move my card to slot 1 (trad the favored slot) I have it in slot 5 so it doesn't share IRQs
3.unhook my midi boxes

they don't know except to keep stripping til i'm naked; just hoped they'd have an answer...

I can consistently get it to crash by running a *small session* w/ 3 midi trax feeding reason, 1 aux track monitoring an external input. I really do think it's a driver conflict.

5.3.1 used to run *FLAWLESSLY*, w/ raid config but no DIGIBASE, TCE trim tool, REWIRE.

looks like another day or 2 of studio time trying to break this down to the lowest common denominator... Suddenly the price of my 001 has tripled w/ my time costs included.

thanks again, as I know many of you have had to do the same thing. I always hoped it wouldn't be me...

Again, any ideas are appreciated and desired! I'm gonna get to the bottom of this.

31hz

[31Hz]

let a session run for a couple hours today (audio drive 1), w/ midi n auxes (outboard feeds), no REASON.

worked fine.

ran a REASON insert, ran an hour, fine too.

my firewire drive was off... hmm. but firewire still enabled.

hm, maybe I can't dupe the prob, but it happened 6 times last night....

back to tests