Kernel.446580 System Error with PXI-8430 connected

[cirrusio]

Hello all,

I am currently attempting to move a system that is currently running on a Windows OS to the RTOS that ships with the PXI-8110 controller.  After connecting to the controller via MAX and updating software, I rebooted and began getting the error:

System error Kernel.446580: illegal Win32 API called from hardware ISR.

And then some other seemingly random errors upon rebooting (sometimes garbage on the screen, sometimes just the above message twice).  After some investigation, I removed one of my cards, a PXI-8430(2) (two RS-232 ports) and upon reboot I got no errors.  Does anyone have any thoughts as to why I would see this error?  Am I doing something incorrectly?  Or could there be an issue with the card itself?  I am going to try swapping out the card with the same (or similar) card to rule out the latter, but any help would be appreciated.

Cheers, Matt

[Logan_H.]

---

@mtat76 wrote:

I am currently attempting to move a system that is currently running on a Windows OS to the RTOS that ships with the PXI-8110 controller.  

---

Hey mtat76,

You have me a bit confused in your wording. Does this mean that the system you are trying to convert from Windows to RT is not the 8110? If not, what hardware are you using?

My initial thought on this is that there are hardware calls being made that are not quite understood. I have found a few Corrective Action Reports regarding this sort of Kernel error where hardware drivers were not installed on a PXI system.

If there is a Win32 error then it seems to me that there are still some remnants of Windows on this machine that should probably be cleared off with a format if you plan to use an RTOS.

Logan H

[cirrusio]

Thanks for the reply, Logan.  I am just moving from the Windows OS to the RTOS on the same controller (8110).  In retrospect, that information is irrelevant.  The problem is simply that with the 8430 in place I get the above error.  Rebooting multiple times didn't seem to help.  I have since moved over to the 8430(4) and am able to run...sometimes.  The sometimes is that I still appear to be getting this error, but I can reboot and get it to go away.  Sometimes I reboot once and everything comes up roses; other times it takes many many reboots to get this to go away.  And each time the system comes up in a bad state, I can either get the above error or what appears to be some kind of binary dump (garbled characters popping up on the whole screen).  The fact that I have to boot multiple times is completely undesirable as this system will ultimately be headless and it may take time to discern that the state is no good.

The 8110 is a dual boot, so I am not sure what you mean by "clearing off the remnants of Windows";  if I do that I will remove my ability to work in the Windows environment - and this is not desirable.  Any other thoughts might be useful.

Peace, Matt

[Logan_H.]

mtat76,

Ok, that sheds some more light on this. It was originally an 8110 XP controller that you have set up to have a dual boot with RTOS right?

First of all, does this controller have a LabVIEW Real-Time Deployment License as described here? I'm thinking an interesting thing to try would be to format the RT partition using the Real Time PC Utility USB disk as described in this KnowledgeBase. This will give your RT partition a fresh starting point.

Logan H