Performance DROPS with 2nd HD

  • Thread starter Thread starter NashBackslash
  • Start date Start date
When you get DRIVER_IRQL_NOT_LESS_OR_EQUAL that most often indicates a problem with the memory. It could just be that you need to raise your ram timings. Your virtual memory setting [swap file] may be too small. Or you may have registry errors. Try this program. It can fix all types of problems.http://www.majorgeeks.com/TuneUp_Utilities_2006_d3891.html
 
I am downloading that software now, but I am at home right now. I can only go back to the studio in 12 hours' time. Can't wait to try that software out...

I read that sometimes it could just be that my RAM is on its way out.

Is there any way to check whether my RAM is good or not? I have 2 x 512 MB DDR RAM.

Also, how would I "raise my RAM timings"?

I will try raising the swap file size. What's a good setting if I have 1024 MB of RAM?

I just found out that the third parameter in my error states that the error is coming from a read operation, so I can only guess that the soundcards indeed are screwing up when trying to read (play) sounds. Not that it's much help heh...
 
bigwillz24 said:
With a gig of ram I turned off the page file completely...
Click to expand...


Wouldn't that make performance decrease?

I'm on a Pentium 4 2.4 GHz, it's not very fast by todays' standards... I need all the performance I can get...
 
Possibly a stupid question, but you have told Sonar to use the new disk for it's audio folders? Otherwise it may be laboriously copying them into the Sonar Projects folder on the C drive.
 
Jim Y said:
Possibly a stupid question, but you have told Sonar to use the new disk for it's audio folders? Otherwise it may be laboriously copying them into the Sonar Projects folder on the C drive.
Click to expand...

Of course I set the audio folders to my new hard disk.

Anyway, as I said, recording is no longer an issue - MOTU is able to write a lot of huge data to my hard disk pretty quick.

It's just PLAYING (ie reading data) sounds that's the problem.

Anyway, I'm off to try out that analisys software. I hope I can track the problem...
 
NashBackslash said:
Wouldn't that make performance decrease?

I'm on a Pentium 4 2.4 GHz, it's not very fast by todays' standards... I need all the performance I can get...
Click to expand...

Not by my tests.... with that much memory having a page file may actually decrease performance from the way I understand it...

I mean the page file is doing nothing more than acting as memory anyway right?

What are you doing that you're using more than a gig of memory at one time?

Less wear on my HD IMO...
 
Guys, I have had it up to *here* with my current setup. I think I better start finding a way to replace my system. My current concerns are budget right now, but if I absolutely have to, I just HAVE to shell out money to build a new PC rig...

But before I do, I'm going to give this PC one last try. THE REALLY LAST...

I am wondering, could the problem be coming from using two soundcards? I use an Audigy LS to monitor MIDI music coming from the computer, and the MOTU as my main interface.

The Audigy is on IRQ 9, and the MOTU is hooked to a Firewire card on IRQ 11. I even checked the IRQ listing at the screen just before the Windows XP splash screen, and found no conflicts.

I disable the onboard sound because it's full of problems. I really need to be able to hear the MIDI wavetable sounds for things like metronome and stuff.

Next question, would merely replacing the motherboard and CPU help? I am going for an Intel-based chipset because I've had enough with VIA. I also want one with an onboard Firewire port. Should I go this route instead of building a whole new rig? My budget is really, really tight right now... and having the PC restart every god damn time in front of clients isn't really helping my pocket...
 
Remove the SB and see what happens those cards do not get along with any other sound cards period. Wish you would have said something before.
 
Okay, I physically removed the Soundblater Audigy LS from the PCI slot, and did a test run.

I put a 19-track project with heavy plug usage on loop. The kept looping fine, after 10 minutes. Normally, I would have to be very lucky to let it actually play that long!

Anyway, I left the thing running. I am at home right now (the studio is about 3 minutes drive away from my neighbourhood), I hope the thing is still running. If it IS still running... then the Soundblaster Audigy LS was the culprit after all.

If that is the case - no more MIDI metronome for me. :/ I really, REALLY need the metronome. I am tempted to enable the onboard VIA sound device, but I'm guessing it's going to make things worse anyway.

Do consumer/gaming soundcards really just cannot work together with recording audio interfaces? It's not like I'm using any of the audio features from the consumer card. I just need it so that Sonar can play the metronome notes.

I think I'll look around for another brand of gaming soundcard, in hopes that it doesn't fight with my MOTU?
 
/me clenches fists, and is really about to explode, but tries real hard to resist from screaming his lungs out...

...... $#@%#@^$#%!!!!!

The problem is not coming from the Audigy LS. Even without it, the restarts STILL happen.

Earlier today, I had a client from the government sector who wants to do a voice over for one of their projects. I think you can imagine the f#@ked up experience I went through, even though it was just a dumb vocal recording session.

We spent about 4 hours to complete the thing. I can say that 1 hour of that time is really taken by the bloody system restarts. YES, the god damn reboots took up ONE HOUR of the session.

The client did pay the full four hours, but out of all honesty, he really shouldn't have. I, for one, am very VERY embarassed because the thing would restart frequently while we were doing our mixing and edits. Not just that - the system actually restarted twice while RECORDING - we lost two precious takes from that!

I was lucky because the client was patient and understanding, but things like this should NEVER happen. I don't want to gamble with my recordings anymore god dammit!

I am going to try apply for a loan to buy parts for a new rig the next morning. I don't know if I'll succeed or not, but I really have to scrap my current setup - I've got more projects coming, and I really don't want to put up with SHIT anymore. Yes, this is all nothing but a PILE OF SHIT to me. I've gotta get the new system ASAP... I just HAVE to... argh...

What I really pray to God is that I hope that the fucked-up-ness of my shitty recording life will just STOP... I mean, you can imagine how depressed I'll be if, even with the new rig, shit STILL happens, and I find out that the REAL bloody culprit is the god damn MOTU unit itself... if it really IS that... then I think I'm going to kill myself... no, I think I'll close my studio, sell my gear and quit the whole PC recording crap and go back to game design...

Yours sincerely,

A Very Tormented Victim of PC DAW Nightmares
 
is it still BSODing on the portcls.sys? Google that error and see what you find. It is a audio driver which usually relates to on board sound so make sure the onboard sound is turned off in your bios

And BTW, welcome to the nightmarish world of VIA chipsets. I went through the same bullshit for years until I went out and got a intel chipset and you know what? No problems since.

Via should just change their name to DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
You still have not checked your error logs.

right-click on My Computer
select Manage
select Event Viewer

Look under System and Application events for error messages. List them here and maybe we can help then.
Don't do this and you're only describing the symptom, which is pretty useless.
 
How about we not just blame it on VIA chipsets. I have had 6 motherboards at least now with VIA chipsets that all have run just fine. Poor implementation of a VIA chipset, maybe, but not the chipset itself which is at fault. The only problem I have had was a certain VIA chipset motherboard did not work with my MOTU PCI324 card. However, that card was known to be very picky and have issues. In fact, I blame MOTU much more so than I would blame the chipset.
 
xstatic said:
How about we not just blame it on VIA chipsets. I have had 6 motherboards at least now with VIA chipsets that all have run just fine. Poor implementation of a VIA chipset, maybe, but not the chipset itself which is at fault. The only problem I have had was a certain VIA chipset motherboard did not work with my MOTU PCI324 card. However, that card was known to be very picky and have issues. In fact, I blame MOTU much more so than I would blame the chipset.
Click to expand...
Agreed. I have had the same experience. FWIW, as far as I can tell, the problem with VIA shipsets is that they're not intel chipsets :) Some HW only gets tested/certified against 100% intel systems. I have never had any issue with via chipsets other than the fact that certain audio hardware gear have issue with them.
 
Ahem... well I'm sorry for that rather immature and unecessary anger in my last post. But I really couldn't help it... the last project with the government people was a very, VERY embarrassing experience for me. Never have I felt so humiliated and so awkward before. It was very ironic because my system did the most restarts on that project. I... argh, I really just don't want to think about it anymore! MUST ERASE MEMORY...

Anyway, okay, I'll do just that - I'll bring home copies of system and application logs. However, I do remember at some point, I turned off file paging, so some errors might not have been logged.

I really hope that when I post the logs, it would reveal useful information to you, and you can help me track where the problem is really coming from...

I'll be back...
 
Is there onboard sound on the mainboard? Make sure it is turned off
 
Just to add on to altitude909's great suggestion, you might have to disable this in the BIOS. It was one of the first things I did on my Dell when I installed my M-Audio Delta 44. Onboard soundcards suck! :D

altitude909 said:
Is there onboard sound on the mainboard? Make sure it is turned off
Click to expand...
 
You must log in or register to reply here.
Back
Top