By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,984 Members | 1,461 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,984 IT Pros & Developers. It's quick & easy.

.NET application hanging operating system

P: n/a
_
We have developed a .NET application that runs fine on most of our
Windows XP systems. There are two systems in particular that lock up
quite frequently, but only when running our application.

The computer is in an unusable state when the OS freezes. Some
symptoms include an unresponsive mouse cursor and unresponsive
keyboard lock LEDs. The only way out is the reset button.

I'd like to know why this is happening, but I don't know how to find
out why. How can I figure this one out? What tools should I be using
to diagnose the problem?
Jul 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi,

Are you using third party components?

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

<_> wrote in message news:u6********************************@4ax.com...
We have developed a .NET application that runs fine on most of our
Windows XP systems. There are two systems in particular that lock up
quite frequently, but only when running our application.

The computer is in an unusable state when the OS freezes. Some
symptoms include an unresponsive mouse cursor and unresponsive
keyboard lock LEDs. The only way out is the reset button.

I'd like to know why this is happening, but I don't know how to find
out why. How can I figure this one out? What tools should I be using
to diagnose the problem?

Jul 21 '05 #2

P: n/a
_
Hey, thanks for responding!

No, we are not using third party components. We are using entirely our
own code and the .NET framework 1.1.

On Wed, 28 Jan 2004 21:33:31 +0100, "Miha Markic [MVP C#]" <miha at
rthand com> wrote:
Hi,

Are you using third party components?


Jul 21 '05 #3

P: n/a
If you are not using unsafe code (non-managed) I would suspect that the
problem is computer related - IOW not in your hands.
Maybe some hardware problem, OS problem or some other problem.

I would suggest you the following.
Try to recreate the problem.
If you find how to trigger the freeze you'll know better what to look for.
Anyway, no managed app should freeze the OS.
The only such possibility could be that you have some code in class
finalizers? Do you?

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com
<_> wrote in message news:lr********************************@4ax.com...
Hey, thanks for responding!

No, we are not using third party components. We are using entirely our
own code and the .NET framework 1.1.

On Wed, 28 Jan 2004 21:33:31 +0100, "Miha Markic [MVP C#]" <miha at
rthand com> wrote:
Hi,

Are you using third party components?

Jul 21 '05 #4

P: n/a
_
On Thu, 29 Jan 2004 20:21:21 +0100, "Miha Markic [MVP C#]" <miha at
rthand com> wrote:
Try to recreate the problem.
This is difficult, but easy. There seems to be no specific thing we
can do in our app to make it happen. It's pretty much random, but only
when our app is loaded. Our app can just be sitting there and the
system will lock up. The machine will run for weeks otherwise.

Personally, I think it's a .NET thing and an Abit 8363-686A(KT7, KT7A,
KT7-RAID, KT7A-RAID) motherboard thing. The two machines that have
this problem have the same model motherboard. It's the component that
is different from the other working machines, but common to the ones
having problems. We have another machine with the same board that we
can try it on. I'd also like to try a much simpler .NET app and see if
it'll lock up the system too. Could also be a 4-in-1 driver thing as
well. We still have to do these tests.

Anyway, no managed app should freeze the OS.
I totally agree. Our app has no unsafe code. Completely managed.

The only such possibility could be that you have some code in class
finalizers? Do you?


We do have code in some finalizers, but if it's there all it does is
call:
this.Dispose();

But it's managed, and it works on all the other machines. Could
something like this really be the culprit?

Hey, thanks again for your assistance.

Jul 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.