SOLVED!!! IRQL_NOT_LESS_OR_EQUAL, onboard AUDIO card on the motherboard!

I think I have solved it now, It was the onboard AUDIO card on the motherboard that made it crash!


ASUS mother board. (NOT USED IN SONAR) When I use the SPDIF output "Windows default audio device" for example other "sounds" like video, You Tube, Audio clips it work perfect. If I use the "ANALOG output" "Windows default audio device" it works too in Windows but not if I work in SONAR in the same time.
 
Of any strange reason SONAR or other software in use in SONAR, must send a attempted to access a memory address which it did not have permission to access conflict with the on board AUDIO card, (that not in use in SONAR either or are config), that cause a conflict in the memory address?

This lead to BSOD. Error Message: IRQL_NOT_LESS_OR_EQUAL

As long I use the SPDIF and set it to "Windows default audio device" everything work perfect, stabel as rock in SONAR.
So far so good! Keep my fingers crossed, I think I nailed this one! Sorry if I caused any confusions!

 
 
 
 
 
 
**************************************************************************
Investigate!!! The NEW UPDATES might have serious MEMORY BUG!!! 

  
  
 
Two blue crash and death now! All my RAID arrays got unsynced twice!
All crashes started after I installed the updates and working in SONAR X1, "hit play" or try to leave sonar project! Critical crash BLUE death, restart!
 
NOTE: Not always, sometimes this happens? I don't know WHY? 
 
I have checked EVENT log files in Windows 7,Critical KERNEL-POWER ID 41, BugcheckCode 209.
 
The bugcheckcode 209 usually points to a defective software or memory. I supect
one of your drivers is defective in the new update?
 
 
 

FastBikerBoy


Freddie, take the guess work away and see this post Written for XP but Vista and Win 7 are almost the same just download the correct version of WinDbg. It'll tell you exactly what is causing it.

Thanks I will do that!

What's the betting what Freddie is seeing is realted to 64 bit

Freddie, 

Not seeing that on my system.  Your title is alarming.  You should check the issue out more fully before pointing at X1 IMO.  

Best, 
Rimshot

Rimshot


Freddie, 

Not seeing that on my system.  Your title is alarming.  You should check the issue out more fully before pointing at X1 IMO.  

Best, 
Rimshot

Thanks for the heads up!

Strange things happening with the PC plugins.


1 I installed the new updates over the original installation 1.0.
2. Stange things start to happen in SONAR. crash , Blue death crash!

3. I uninstalled the both PLUGINS!
4. I made a new install of the SSL 4K + the gate. 1.1 installer
5. SSL comes up in X1 but not the gate?

6. I make a new uninstallation of GATE.
7.  I made a new install of the the gate.

8 Gate wakes up in SONAR X1.
9 Load the SSL and gate, everything works.

10 Load premade preset made with 1.0 version with SSL 4k comp. The visualization of the Meter stops working in the preset?
 
 
conflict with old settings?

Freddie H

Noel Borthwick [Cakewalk
]

Bugchecks are caused by kernel mode crashes not user mode programs so its not SONAR that is crashing your system. SONAR doesn't install any drivers. That crash could possibly be caused by power supply issues (insufficient power to a device). You will have to troubleshoot your drivers.

Thanks! I have UPS + seasonic 650 WATT GOLD PSU so I don't think so?
 
I uninstalled SSL compressor + the gate and re-installed it. Lets see if that work..
Now I don't see the gate anymore in Pro channel?

Check that your CPU FAN (and power supply fan) are actually spinning.   An over heated CPU can do weird things as I suspect you know.  Even with 64 bits ;)

I have done MEMTest + torture test = No errors.
 

So no hardware errors, CPU, MEMORY, PSU, Coolig fine! 
So its a software or other hardware conflict attempted to access wrong memory address.

FastBikerBoy


Freddie - did you run through that post I linked you to? That will tell you exactly what process/driver is causing it.

 
 
I get this random only, like if I hit play in SONAR or close project, delete plugin?
Anyway, I have changed my setup physical + routing recently so I think I know what perhaps cousing this?
I have revert back the routing so let's see if I'm right?
 
"will tell you exactly what process/driver is causing it."
Yes I know, but no I havn't tried it yet. I just read about it briefly. That next up for sure if this doens't help!
Thanks for all the help my friend! I really appreciate it! 

Noel Borthwick [Cakewalk
]

Bugchecks are caused by kernel mode crashes not user mode programs so its not SONAR that is crashing your system. SONAR doesn't install any drivers. That crash could possibly be caused by power supply issues (insufficient power to a device). You will have to troubleshoot your drivers.

I'm sorry, I don't agree with that - fully!

Yes, the final cause of the crash and blue screen is in kernel mode.

But software can easily still create this and be the actual cause for problem.

#1. I have Vsampler and at one point they changed how they enumerate the supported bitrates and bitdepth and such. Standalone version.

They just threw every possible bitdepth and resolution to drivers and saw if it was accepted.
This cause blue screen since drivers did not see this coming - since these resolution were not listed internally somehow.

Yes, it's good if both drivers and usermode software can handle every situation.

But Vsampler is no doubt the cause of this.

#2. I ran TC Electronics Impact Twin in Sonar 8.5 and ran wdm drivers and enabled one input - and blue screen on w7 i7 x64 machine.

I ran the same thing in Reaper and no problems.
I ran with ASIO in Sonar- no problems either.
Sonar plays back fine too.

Are Sonar to blame or not?

I think it is Sonar problem! You are doing something in a different way.

The IT drivers were not the best or Sonar were not handling it correctly - because playback also had some strange issues with these drivers - I had to start transport 2-3 times usually until it finally ran.

But actually - Reaper ran without any hickups whatsoever.

Either way - Sonar is to blame for the blue screen.

It's making it much too easy for yourself if just blaming drivers.

In my case it was a virtual hardware driver::: Midi Yoke did this to me a couple of years ago. Somehow the file became corrupt. Was way difficult to completely uninstall it.

And:  if it is a memory bit it will only occur when that bit is accessed. You got other programs that use as much ram as Sonar?   Run any memory testers lately.

And, as Ifm wrote, it is possible the updates are talking to the drivers differently. So you may have to install the various audio/midi related drivers and utilities after the updates.

I had to install the USB driver for my midi interface once to stop a stupid from occurring.


J

Freddie H

Noel Borthwick [Cakewalk
]

Bugchecks are caused by kernel mode crashes not user mode programs so its not SONAR that is crashing your system. SONAR doesn't install any drivers. That crash could possibly be caused by power supply issues (insufficient power to a device). You will have to troubleshoot your drivers.

Thanks! I have UPS + seasonic 650 WATT GOLD PSU so I don't think so?
 
I uninstalled SSL compressor + the gate and re-installed it. Lets see if that work..
Now I don't see the gate anymore in Pro channel?

Power supplies go bad Freddie. I've had a few go bad over the years. Including a Seasonic.
 
Edit: Plus UPS's have very little if anything to do with the controlled and regulated voltages going on inside of your PC. The only thing that really matters is the PSU and they can go bad.
 

Freddie H


Investigate!!! The NEW UPDATES might have serious MEMORY BUG!!!

Updates! PC4K S-Type Expander/Gate & Channel Compressor version 1.0.1 might have serious MEMORY issues
http://www.cakewalk.com/Support/kb/reader.aspx/2007013276



Two blue crash and death now! All my RAID arrays got unsynced twice!
All crashes started after I installed the updates and working in SONAR X1, "hit play" or try to leave sonar project! Critical crash BLUE death, restart!

NOTE: Not always, sometimes this happens? I don't know WHY?

I have checked EVENT log files in Windows 7,Critical KERNEL-POWER ID 41, BugcheckCode 209.

The bugcheckcode 209 usually points to a defective software or memory. I supect
one of your drivers is defective in the new update?

I've never been aware of SONAR actually installing any type of device driver before. Is this something new? Please provide evidence.

bapu


That settles it.

I'm going back to 32bits.

Arggh, now you're gonna change everything 

I think I have solved it now, It was the onboard AUDIO card on the motherboard that made it crash!


ASUS mother board. (NOT USED IN SONAR) When I use the SPDIF output "Windows default audio device" for example other "sounds" like video, You Tube, Audio clips it work perfect. If I use the "ANALOG output" "Windows default audio device" it works too in Windows but not if I work in SONAR in the same time.

Of any strange reason SONAR or other software in use in SONAR, must send a attempted to access a memory address which it did not have permission to access conflict with the on board AUDIO card, (that not in use in SONAR either or are config), that cause a conflict in the memory address?

This lead to BSOD. Error Message: IRQL_NOT_LESS_OR_EQUAL

As long I use the SPDIF and set it to "Windows default audio device" everything work perfect, stabel as rock in SONAR.
So far so good! Keep my fingers crossed, I think I nailed this one! Sorry if I caused any confusions!

A 64bit rock?