LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

system error kernel.446901

I have a PXI Chassis with a PXI-8196 Controller running Labview RT.  Whenever I try and boot up (without a startup.vi loading right now) I get a "System Error Kernel.446901  Bad Exception Disposition"
 
This error message comes a few seconds after it seems to fully boot.
 
Anyone have a clue what this one means?
 
0 Kudos
Message 1 of 3
(4,068 Views)

Hi DCSmith,

I've done some looking into this, and the only thing I was able to find is that this error can occur if your PXI controller has been subjected to continous rebooting.

The notes from the Corrective Action Request (CAR) being worked on by R&D:

Continuous rebooting a PharLap target can get it in a bad state with the following error: "System error KERNEL.446901: Bad exception disposition" printed on the screen repeatedly until eventually it reboots on its own.

This doesn't seem entirely the same as what you are seeing.  If I understood you correctly, you are receiving the error only once after the boot completes?  Are you able to work with the controller afterwards or does the error lock up the system?  Have you already attempted to format the controller and see if that clears this up?

Regarding the CAR (#43070), it is being worked on but, let me know if your issue seems unrelated so that we can attempt to find you a work-around or a solution.

David_B
Applications Engineer
National Instruments
0 Kudos
Message 2 of 3
(4,043 Views)
David,
Thank you for your response and for taking the time to look into this for me.  I have been so busy that I forgot to come back here and post what happened.
 
I did call our local NI Field Engineer and we submitted a service request.  After spending some time looking at several different things, we determined that there must have been a bad sector on the hard drive.  We formatted the hard drive and re-installed Pharlap and everything is ok now.
 
You are correct with your findings and the description of the problem.  I believe the system was "hung-up" a couple of times (2 or 3) running a VI that got into a sort of endless loop that wouldnt timeout and it was manually rebooted to get it back to a steady state.
 
Hopefully this will help someone else if they run into this one!
 
Thanks again,
Daryl
0 Kudos
Message 3 of 3
(4,036 Views)