.




FULL PRODUCT VERSION :
java version "1.4.1-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-beta-b14)
Java HotSpot(TM) Client VM (build 1.4.1-beta-b14, mixed mode)

FULL OPERATING SYSTEM VERSION :
Microsoft Windows XP [Version 5.1.2600]

EXTRA RELEVANT SYSTEM CONFIGURATION :
ATI Radeon AGP graphics card 7200
Driver: ati2dvag.dll ver: 6.13.10.6071 (English)
DirectX 8.1 (4.08.01.0810)

A DESCRIPTION OF THE PROBLEM :
Windows XP freezes (hangs) on Java application exit. I
experience this consistantly on all applications that take
advantage of image drawing functions. I have not been able
to reproduce on other Java applications. Application runs
fine but Windows XP freezes indefinitely on exit. Once
while running an application using drawImage() to a panel
I entered a Windows blue screen complaining of an infinite
loop in the video driver. Sometimes the program will exit
normally if you simply start and exit with small drawing
activity, but a reasonable amount of image drawing
activity seems to cause Windows XP to hang on exit. While
difficult to pinpoint (since you are left with no errors
while your machine reboots), it is probably due to a new
incompatibility between the java runtime and video driver.
I do not have this problem with any JDK previous to the
1.4.1 beta release.

REGRESSION.  Last worked in version 1.4

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Compile and run attached program (or any other java
application with sufficient image placement activity).
2. Select "Open Image..." from the File menu and select a
*.jpg format image that would fit onscreen at full size.
For example, a 640 x 480 image is fine.
3. Click on different locations of the loaded image to
scramble the 'pieces', observing that the draw
functionality is working. Scramble the image pieces, as
this seems to be the source of the freeze on application
exit.
4. Exit the application and watch Windows freeze.

EXPECTED VERSUS ACTUAL BEHAVIOR :
Java runtime should gracefully exit, as it almost always
has on previous releases of the JVM. Instead, Java appears
to be the cause of Windows freezing on exit.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
There are no error messages, nor output from the JVM.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
package scratch;
// Freeze.java	William Dubel	June 30, 2003

import java.io.*;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.awt.image.*;
import java.util.ArrayList;
import java.util.Collections;
import javax.swing.border.TitledBorder;

public class Freeze extends JFrame  {
	private JMenuItem newGame, quit, about;
	private JMenu fileMenu;
	private JPanel puzzleArea, puzzleGrid;
	private JMenuBar bar;
	private JFileChooser fileChooser = new JFileChooser();
	private Container c;
	private int tiles = 25;
	private ArrayList pieces = new ArrayList();
	private Game currentGame;
	private MouseHandler mouseHandler = new MouseHandler();
	private ItemHandler itemHandler = new ItemHandler();

	public Freeze() {
		super("ImageTest");
		c = getContentPane();

		fileChooser.setFileSelectionMode(JFileChooser.FILES_ONLY);

		setJMenuBar(bar = new JMenuBar());
		(fileMenu = new JMenu("File")).setMnemonic('F');
		(newGame = new JMenuItem("Open
Image...",'N')).addActionListener(itemHandler);
		(quit = new JMenuItem("Exit",'x')).addActionListener
(itemHandler);
		fileMenu.add(newGame);
		fileMenu.add(quit);
		bar.add(fileMenu);

		(puzzleGrid = new JPanel()).setLayout(new GridLayout(1, 1));
		puzzleGrid.setSize(300,300);

		(puzzleArea = new JPanel()).setLayout(new FlowLayout());
		puzzleArea.add(puzzleGrid);
		puzzleArea.setBorder(new TitledBorder("Click on image to
scramble"));

		c.add(puzzleArea,BorderLayout.CENTER);
		setSize(500,400);

		addWindowListener( new WindowAdapter()	{
			public void windowClosing( WindowEvent e ) {
				System.exit(0);
			}
		}   );
	}

	private class MouseHandler extends MouseAdapter {
		private int first = -1;
		public void mousePressed(MouseEvent e)  {
			if (first<0 || first >= tiles)  {
				for (int n=0; n<tiles; n++) if (e.getSource()
==pieces.get(n))
				{
					((Piece)pieces.get(first =
n)).setSelected(true);
					((Piece)pieces.get(first)).repaint();
				}
			}
			else    {
				for (int n=0; n<tiles; n++)
					if (e.getSource()==pieces.get(n))   {
						((Piece)pieces.get(n)).repaint
();
						((Piece)pieces.get
(first)).setSelected(false);

						puzzleGrid.removeAll();
						Collections.swap(pieces,
first, n);

						for (int i=0; i<tiles; i++)
puzzleGrid.add((Piece)pieces.get(i));
						puzzleGrid.validate();
					}
				first = -1;
			}
		}
	}

	private class ItemHandler implements ActionListener {
		public void actionPerformed( ActionEvent e )    {
			if (e.getSource()==newGame) {
				int answer = -1;
				if (answer!=JOptionPane.CANCEL_OPTION)  {
					int result = fileChooser.showOpenDialog
(c);
					if (result!
=JFileChooser.CANCEL_OPTION) {
						File filename =
fileChooser.getSelectedFile();

						currentGame = new Game
((filename), tiles);

						puzzleArea.remove(puzzleGrid);
						puzzleGrid = new JPanel();
						puzzleGrid.setLayout(new
GridLayout(currentGame.getRows(), currentGame.getCols()));

						pieces = new ArrayList();
						for (int i=0; i<tiles; i++) {
							Piece temp = new Piece
(currentGame, i+1);
							temp.addMouseListener
(mouseHandler);
							pieces.add(temp);
							puzzleGrid.add(temp);
						}
						puzzleGrid.setSize(	(int)
currentGame.getSize().getWidth(),
									
				(int)currentGame.getSize().getHeight()	);
						puzzleArea.add(puzzleGrid);
						pack();
						puzzleGrid.validate();
					}
				}
			}
			if (e.getSource()==quit)        {       System.exit
(0);         }
		}
	}

	public static void main(String [] args) {
		JFrame puzzlegame = new Freeze();
		puzzlegame.setVisible(true);
	}
}

class Game  {
	private ImageIcon imageObject;
	private int complexity;

	public Game(File filename, int complexity)  {
		this.complexity = complexity;
		imageObject = new ImageIcon(filename.getPath());
		try	{ while (imageObject.getImageLoadStatus()
==MediaTracker.LOADING) Thread.sleep(10); }
		catch(InterruptedException ie)	{	ie.printStackTrace();
				}
	}

	public Image getImage()					{	return
imageObject.getImage();	}

	public Dimension getSize()				{
		return new Dimension(imageObject.getIconWidth
(),imageObject.getIconHeight());
	}

	public int getRows()	{
		return (int)Math.sqrt(complexity);
	}

	public int getCols()	{
		return getRows();
	}
}

class Piece extends JPanel implements Runnable  {
	private Dimension size;
	private Image mini;
	private int order;
	private MediaTracker loader;
	private boolean selected = false;

	public Piece(Game currentGame, int tile)    {
		size = new Dimension((int)(currentGame.getSize().getWidth
()/currentGame.getCols()),
									(int)
(currentGame.getSize().getHeight()/currentGame.getRows()));
		mini = currentGame.getImage();

		CropImageFilter cropFilter =
			new CropImageFilter(	(((tile%currentGame.getCols()!
=0) ? tile%currentGame.getCols()
									
		: currentGame.getCols())-1)*(int)size.getWidth(),

									
	(int)((Math.ceil((double)tile/currentGame.getCols())-1)*size.getHeight
()),
									
	(int)size.getWidth(),
									
	(int)size.getHeight());

		mini = createImage(new FilteredImageSource(mini.getSource
(),cropFilter));
		order = tile;

		loader = new MediaTracker(this);
		loader.addImage(mini, order);
		new Thread(this).start();
	}

	public void run()   {
		try
		{	while (loader.statusID(order, true)!
=MediaTracker.COMPLETE) Thread.sleep(20);	}
		catch(InterruptedException ie)		{
	ie.printStackTrace();		}
		repaint();
	}

	public Dimension getPreferredSize()		{		return
size;				}
	public boolean isSelected()				{
	return selected;			}
	public void setSelected(boolean yes)	{		selected = yes;
			    }

	public void paintComponent(Graphics g)  {
		Graphics2D g2 = (Graphics2D)g;

		if (loader.statusID(order, true)!=MediaTracker.COMPLETE)    {
			GradientPaint gp = new GradientPaint(0.0f, 0.0f,
Color.lightGray,
				   (float)size.getWidth(), (float)
size.getHeight(), Color.darkGray);
			g2.setPaint(gp);
			g2.fillRect(0, 0, (int)size.getWidth()-1, (int)
size.getHeight()-1);
		}
		else    {
			g2.drawImage(mini, 0, 0, (int)size.getWidth(), (int)
size.getHeight(), this);
			if (selected)
			{
				g2.draw3DRect(1, 1, (int)size.getWidth()-3,
(int)size.getHeight()-3, false);
				g2.draw3DRect(0, 0, (int)size.getWidth()-1,
(int)size.getHeight()-1, false);
			}
		}
	}
}
---------- END SOURCE ----------

Release Regression From : hopper-beta
The above release value was the last known release where this 
bug was known to work. Since then there has been a regression.

(Review ID: 158715) 
======================================================================

Use -Dsun.java2d.noddraw=true
This prevents our use of DirectX for rendering and apparently (according to the
submitter) avoids whatever the freeze problem is.  

The flag
	-Dsun.java2d.d3d=false
is also worth trying (and a better, less constraining flag to use), but the
user has not yet been able to verify whether this avoids the bug since the
publicly release build is currently b14, which does not yet fully implement
the d3d=false functionality.

 xxxxx@xxxxx  2002-07-23


-Dsun.java2d.d3d=false doesn't avoid the problem with 1.4.1-beta-b14. However, this option helps to avoid problem with 1.4.1_01-bo1.
 xxxxx@xxxxx  2002-10-31

 Still can't reproduce this problem.  Targetting it for mantis.

This seems very card-specific.  We have tried it on very similar platforms,
including XP with the Radeon 7200 VE (a variation on the 7200 that lacks the
geometry engine) and have still not seen the crash here.  We need to pick up
the exact same card and see if that helps reproduce the problem.  The user
has only seen the problem on the one machine with this configuration, although
they did test with 2 different drivers (the original XP driver as well as a
more recent ATI driver) and both drivers produced the bug.

 xxxxx@xxxxx  2002-07-23

The user does not experience the freeze when running with the noddraw flag.
It is also worth trying the sun.java2d.d3d=false flag (but the user needs
a later build past the 1.4.1 b14 build they are running with now to try
this flag).
 xxxxx@xxxxx  2002-07-23

I am finally able to reproduce this problem.  I installed a Radeon 7500 with
driver version 5.13.1.6043 and I now get either a hang or a Blue Screen Of 
Death upon app exit.  

Note the workarounds: both the noddraw=true and d3d=false flags prevent the
problem from occurring.  Thus the problem must be somewhere in our 
d3d usage.

One strange thing I noticed during my debugging so far was that the 
creation of d3d devices fails with the error E_NOINTERFACE (0x80004002).
This is curious for two reasons: 
	- I don't know why we would fail, or why failing that call 
	(CreateDevice) would fail with that error (it is not even spec'd
	to return that error).
	- Since we fail creating the device, we should not be using
	d3d to render anything (lpSurface for those DDrawSurface objects
	is NULL).  So there should be very little interaction with d3d
	that gets us into trouble (except, presumably, these calls to
	CreateDevice).

 xxxxx@xxxxx  2002-08-29

The error I was getting above (E_NOINTERFACE) was erroneous; this was actually
an error I was getting when trying to create a d3d device on my secondary 
device when running multimon.  Since that other device is a Matrox Mill II,
which does not support d3d, getting an error during d3d device creation 
is not too surprising.

I disabled my second monitor to reduce the confusion and still consistently
blue-screen upon app exit.  I no longer get any ddraw/d3d errors during device
creation (or at any other time).  And I can step, using the debugger, all the
way through the exit from DllMain during PROCESS_DETACH, so there is nothing
obvious that is causing this problem.  Presumably we are trouncing on memory
somewhere, but I don't have any leads yet.  It is worth trying to reproduce
this problem in a native app to narrow it down.

 xxxxx@xxxxx  2002-09-03

I have attached a test case which is a purely native app that shows the
problem.  Apparently the problem is that we create too many d3d devices.
Currently, whenever we want d3d capabilities on a ddraw surface, we create
a d3d device for that surface.  The DirectX docs suggest that having one
d3d device per ddraw object (not per ddraw surface) is a better way to
go for performance reasons; the context switching inherent in multiple d3d
devices is too expensive.  They do not happen to mention that having too many
devices can also hang the system (this is presumably a driver bug that we
just happened to bump into on these ATI boards).

Although the real fix for the crash lies with ATI (I don't think the OS
should crash because of what we are doing), we can and should fix the problem
in our code by moving to a system of sharing a single d3d device, as suggested
by the DirectX documention.

There are issues with this approach, such as:
	- we need to do a SetRenderTarget whenever we are rendering into 
	a new ddraw surface since the single d3d device may currently be
	set to a different render target.
	- in addition to changing the rendering target, we also need to
	update the viewport if the dimensions of the new surface differ
	from the previous one.
	- we need to lock around accesses to this shared device since we 
	have potential multi-threaded rendering issues when rendering to
	different surfaces.

The test case (4713003.ManyD3dDevices.zip.Z) is a zipped project file from
a DevStudio application.  You can either run the app in the Debug folder
directly or build the application and run it within DevStudio.  
By changing the "NUM_OFFSCREEN_SURFACES" variable at the top of
DDHelloWorld.cpp you can affect the crash.  I found that the crash only
occurred when this value was greater than 8 (the value is currently set to
9 in that file).

Forwarding the bug to the engineer currently working on the single-device
approach.

 xxxxx@xxxxx  2002-09-06

Workaround & eval does not help applets targeting the plug-in 
because we cannot ask clients to goto JPI control panel & 
enter -Dsun.java2d.noddraw=true !  Applet deployers *really* 
need per-applet control of this property (since 2D cannot 
promise fault-free ddraw rendering on all desktops).

This happens with me as well on a win2k machine with same 
video card.  It happens almost everytime any java app exits 
and completely halts computer.

I´ve found a bug with a similar problem. I´ve got an ATI Rage 
Mobility 128 and problems with version 1.4.1beta too. I can't 
Graphic's drawImage on non scaled images, however, if i scale 
them it works. Using the flag
-Dsun.java2d.noddraw=true prevents the error.

It seems thet this problem happens also with ATI´s Radeon 
AIW (quite familiar with 7200 i think ( uses same drivers ) ) 
and at least for me is always reproducable just by running 
SwingSet2 and exiting from it. This freeces my computer 
completely.  This happens with both 1.4.1 beta and RC, with 
1.4.0_xx there is no such problems. ( and this is tested with 
two similiar computers ( another with W2K another with XP , 
other parts are the same ). 

Same problem on Win2K (SP2) with ATI 7500 and
ati2dvag.dll ver: 5.13.01.6071 and DirectX 8.1

Still producing this bug, with Windows XP, j2sdk1.4.1RCb19, 
ATI Radeon 7200 DDR card, and latest ATI Driver Build 
6.13.10.6118 7.74-020709A-004733C Posted August 01, 2002.

I've seen (what is possibly) a variant of this: Win2k sp2
with rage mobility and directx 8 crashes completely as soon
as I try to start WebStart from jdk1.4.1-rc. The only
"solution" I've found is to reduce "Hardware acceleration"
under "Troubleshooting" in "Display" in the Win2k settings.

Hello, I am able to reproduce the problem, too. Same
configuration as original problem report, but j2sdk
1.4.1-rc, german Windows XP Professional. The problem occurs
with Sun One Studio 4 CE on exit. ***But only in 32 bit
color depth mode***. Changing to 16bit "solves" the problem.
-Dsun.java2d.noddraw=true also "solves" the problem.

Hello, I am able to reproduce the problem, too. Same
configuration as original problem report, but j2sdk
1.4.1-rc, german Windows XP Professional. The problem occurs
with Sun One Studio 4 CE on exit. ***But only in 32 bit
color depth mode***. Changing to 16bit "solves" the problem.
-Dsun.java2d.noddraw=true also "solves" the problem.

Well .... sorry again ;-)
The problem didn't go away as stated, it still is there even
with the new ATI driver. Seems you have to click around a
while before exiting the app hangs the system.
Even lowering the acceleration for one step doesn't work and
I don't want to make my system too slow...
Giving up with this now, using noddraw=true.

First of all, sorry for double posting my last comment, my
router dropped connection and my browser misbehaved.

Now, I downloaded ATI driver 6.13.10.6118 for Windows XP
(all parts) and installed and the problem went away.

We can reproduce this too, using an ATI Radeon Mobility
card. Java Web Start hangs at startup, using 100% CPU.
Applets just the same. Using 1.4 rc. Verified on three
different machines. 

We can also reproduce this, with XP and a Radeon 7000 card 
and a Java application (BotBox Personal Assistant which uses 
a lot of swing code).

This bug hasn't been fixed at all in 1.4.1FCS, has it? I'm
getting an immediate BSOD as soon as I open an image in the
example program. Starting Web Start gives the same result.
I'm using ATI Rage Mobility P, latest driver.

I've just uninstalled 1.4.1 FCS from my ibm a31, it uses a 
mobilty radeon 7500.

We have a large number of IBM Thinkpads a22m model 
number 2628-txg with mobility 128, within our company and 
have the same blue screen of death with the 1.4.1 FCS so 
this still needs to be fixed.

We cannot use 1.4.1 for our thin client, using Java Web Start 
before this is fixed, We regard this as a major bug, even if 
some blame can be put on a bad driver from ATI, our 
customers will experience the Blue Screen of death by using 
our Java Client.

Well, the latest driver (6.3.10.6114) I was speaking about 
and available from IBM, still seems to have some problems. 
I'm using a swing application the freezes are occurring again.

Update to my last comment: The ATI driver update didn't 
install correctly and xp was still using an old ati driver. The 
bug is fixed with the 6.3.10.6114 ati driver which is available 
from ibm. I had to initiate the update manually through the 
hardware control panel.

I seem to have a related problem. My swing apps crash if
there is a JToolbar used in the gui - the frame starts up
but does not get updated.. instead my system starts to slow
down bit by bit and will crash eventually after moving
around the mouse for some time. This happens every time now
that I installed 1.4.1.. on 1.4.0_01 it worked fine. There
are no problems if I remove the JToolbar out from the code.

Starting the app with '-Dsun.java2d.d3d=false' also fixes
the problem.

Oddly enough another 'workaround' is to ctrl-alt-del to the
'Windows Security' screen right after the jframe appears (or
the jframe borders.. since content isn't updated) and
returning to the desktop... the jframe has updated it's
content.. showing the jtoolbar and other other components 
and the app works fine.

I'm using Win2k with sp6 and a PowerColor Evil Kyro graphics
card. The problem appeared in hopper-rc (didn't test the
beta) and still exists in 1.4.1.. 

I have the same problem on XP machine with ATI RadeON 
7500 card. My laptop with an NVIDIA GeForce4 440 Go 
doesn´t have this problem.

-Dsun.java2d.noddraw=true
or
-Dsun.java2d.d3d=false

Sorry but this is not an option that is viable or an exceptable 
solution for our client

My users may be experiencing this problem. Since we are 
launching via Java Web start my only option appears to be 
adding -Dsun.java2d.noddraw=true (sun.java2d.d3d is not 
passed through) to the jnlp file, thereby disabling DirectDraw 
for everyone using the application.

Happens on my ATI 8500LE too.

I'm sorry. TNT MX is not. only ATI

Seems I'm the first to encounter the problem on Win98, 
second edition, old ATI card (ATI Rage 128 GLAGP) JRE1.4.1 
FC. I have a swing image editing app. 
Popps up an error in DDHELP when I close the app. When I 
later log off from the desktop I get an win 3.1 style white 
error message box and then I can only do a hard reset.
It's not always reproducilble though, but happens quite a lot 
of times, sometimes even after a fresh reboot.
I have absolutley no problems with this graphics card for all 
the rest of programs I'm using here - so I'm quite sure it is 
due to the JRE and it did not happen with 1.4.0 which I was 
using before.

This happens with our team on win2k machenes.
System hang up after gui app ran consitently
JDK1.4.1FCS
ATI 7200, TNT MX

Just changed IBM thinkpad to A31 with ati mobility 7500 and 
still the same problem under XP sp 1

I am experiencing the same problem on my workstation and 
notebook computers. One is using an ATI Radeon 7500 and 
the other an ATI Radeon 7500 Mobile. My colleague with an 
ATI Radeon VE does not experience the problem.

Me again, see first post a bit up.
This is what I get as details in the error box when I shut 
down my swing app (sorry german version, but we all now 
this message content):

DDHELP verursachte einen Fehler durch eine ungültige Seite
in Modul ATI3DRAA.DLL bei 0177:b00cf15c.
Register:
EAX=00000001 CS=0177 EIP=b00cf15c EFLGS=00010202
EBX=bff7b9c9 SS=017f ESP=0089fd0c EBP=84c78000
ECX=0089ff88 DS=017f ESI=00000000 FS=5def
EDX=000000a0 ES=017f EDI=8448b304 GS=0000
Bytes bei CS:EIP:
8b 77 04 8b 6f 0c 6a 48 56 ff d3 85 c0 75 13 8b 
Stapelwerte:
00000003 b00ff88c 0089fd50 0089fd48 b0100120 84c78000 
b00cf67b 00000003 0089fd50 b00f8da0 84484f00 56668e08 
0089fd48 b00f8da0 56660000 fffbf471 

I'm experiencing it under Win2K SP3 w/ an ATI Radeon 
7000/VE and the currently released 1.4.1 (build 1.4.1-b21).

Have the same problem with Windows Me and ATI Radeon 
7000 graphics card. Have gone back to JDK 1.4.0_02

Experience system freeze with J2RE 1.4.1 FCS on Win2K SP3 
with ATI Radeon upon closing Java Swing app. Works on 
1.4.0_02.

I have a similar problem on Win98 with Voodoo 3, but the
system hangs just after loading java.awt.Rectangle class so
I'm not sure if that's the same bug or only a similar one

Still crashing with 1.4.1_01...

Is there any way to achieve the equivalent of
-Dsun.java2d.noddraw=true for every application (including
applets and webstarts)?

I have run into this one. Suprisingly, it happened while editing
some Java code in IDEA, my favorite java IDE. It obviously 
uses java2D under the hood. I've tryied running the test 
program and it failed in the exact same way described. This 
bug is real! I can't believe it, this is the first time Java has 
brought down my entire OS. My machine runs Windows 2000 
Service Pack 3, and has a Radeon 7200 Graphics card using
driver version 5.13.1.6071. I am downloading ATIs newest 
driver as I speak to see if it fails the same way.

Ok, just tested the latest ATI drivers for my card. A small 
improvement! Before, the system completely hung and I could 
not interact with anything (except the Reset button). Now, 
everything freezes. but you can still move the mouse (its 
jerky but it works). Shame that you still can't click on 
anything, but its an improvement! Sun, can you give any 
indication when this bug will be fixed?

Aaahhh, what a nightmare!  We'd *really* like to move our 
apps/applets to 1.4.1 (using 1.3.1 now) but how can we if 
something like this is around?

Re: "Is there any way to achieve the equivalent of
-Dsun.java2d.noddraw=true for every application (including
applets and webstarts)?" -

1.4.1 Webstart apps can put the noddraw prop in their JNLP 
file (see forums, etc. for details).  But, you'll be forcing 
*everyone* running the app to run with slow 2D...

Savvy plug-in *users* can put the sun.java2d.noddraw 
runtime param in their JPI control panel, BUT this is totally 
UNWORKABLE for JApplet deployers (esp. those with no 
control of desktop hardware, drivers, etc... Eg. most of us:)

Seems, at minimum, JPI applet deployers need control of 
java2d props at HTML tag/param level in order to consider 
rolling out under 1.4.1.  Would *also* be nice if JRE could 
detect where it cannot reliably render & automatically revert 
to noddraw, etc.  Regardless, deployers need control of props 
affecting the succesful use of their apps & applets.

BTW, we do see less platforms with these GUI problems in the 
move from 1.4.1 Beta -> FCS.

Win2000, ATI Radeon 7200, JDK 1.4.1:

My machine freezes whenever I terminate a 1.4.1 GUI 
application. (E.g., Sun ONE Java IDE). I installed the newest 
ATI device driver, as well as DirectX 8.1. That didn't help.

Have the same Problem on my ATI Mobile M6 on Win2K as well
as XP (jdk1.4.1, DirectX 8.1) 

I understand that Sun doesn't generally want to comment on 
the status of upcoming patches, but in this case they should 
make an exception.  I would guess that an enormous number 
of potential customers are affected (I know that my firm 
certainly is).  I think we'd all appreciate an estimate of when 
this will be fixed, so that we can plan the deployment of 
software that depends on the fixes and other improvements in 
1.4.1.

If it will take a long time to fix this properly, Sun should 
release a new version 1.4.1_02 that automatically turns off 
ddraw for ATI card users.

I would *really* appreciate this one being fixed.  If I turn off 
d3d and noddraw, then I can work on my Dell Latitude but we 
cannot actually ship an application based upon JDK 1.4.1 until 
this is fixed!

We do realize that this is a very important bug to many
customers and it's scheduled to be fixed in 1.4.1_02.

Dmitri Trembovetski
Java2D Team

i have the same problem on a Thinkpad A31p  with ATI Mobility 
FireGL 7800 and Win2000.Still freezing with 1.4.1_01

I am having the same problem using a Mobility Radeon 7500 
on my IBM Thinkpad A31, running Windows 2000 Pro.  This 
just started happening yesterday on a Swing app I'm working 
on.

I have a Matrox Millenium II adapter on Win2K sp2
and I am experiencing problems if I don't use the
"-Dsun.java2d.noddraw=true" switch.

Without the switch the graphics are corrupted.
A small block appears to follow the cursor around the 
panel corrupting everything in its wake.

I just installed JDK 1.4.1 final and... I suddenly have the same 
problem. Applications that worked smoothly with JDK (JRE) 
1.4.0 cause my Windows XP Pro crash on exit (jEdit, 
NetBeans and others) every time.
Workaround - I had to go back to JDK 1.4.0  :-(((
My configuration: Dell Inspiron 8100 with Mobility Radeon 
7500 (latest drivers) & Windows XP Professional.

The latest beta drivers from ATI (intended for use with the
Lord of the Rings game) fix the Java problem. The next
official driver release will include the fix.

I must say that I agree with tpistor.  Sun's web page 
recommends 1.4.1_01 for all new users, but there's an 
excellent chance that the user will have an ATI card and will 
experience crashes when they run Java programs.  This user 
may be unwilling to try Java again in the future.

Sun should withdraw 1.4.1 (move it back to beta status) if 
they cannot release a fix immediately.  I will again recommend 
the release of a version 1.4.1_01a which is identical to 
1.4.1_01 except that it always behaves as if 
sun.java2d.noddraw=true for users with ATI cards.

I have got the same problem (with 1.4.1_01)
(or at least using the work around
solve my problem of blue and or black screen)

I'm using a Compaq Armada with W2K
and ATI RAGE MOBILITY AGP ...

On a Compaq Presario 2701US with Mobility graphics card the 
error was not occuring until I updated the driver for the video 
card.  Now crashes every time.  Maybe this is a clue.

SUN:  Basically, you have no shippable version of 1.4.1.  This 
bug should be #1 priority since you are hurting your own 
reputation by blue-screening computering around the world.

I have had this happen to me on my Radeon All-In-Wonder 
7500 AGP.  Have two video cards in this machine : The ATI 
card and a Voodoo 3 2000 PCI.

Running Windows 2000 (SP3), JVM 1.4.1_01.

Win2k JRE 1.4.1._01, Dell Laptop with ATI RAGE MOBILITY-M1 
AGP2X video card.  Crashes first time any Java GUI app is 
run.  Computer blue screens briefly then reboots 
automatically.  I have tried -Dsun.java2d.noddraw=true from 
within while debugging, seems to work but I haven't done 
much testing.  

Fixed in mantis? Please tell me that I don't have to wait for 
1.4.2 for this fix.
We couldn't release on 1.4 because of a DnD bug and on 
1.4.1 or 1.4.1_01 because of this bug, when are we going to 
have a VM that we can release on?

My dell laptop hangs on application exit, Windows 2k.
Mobility Radeon 7500C.

Is this closed because disabling directdraw "fixes" it?
What is the real solution here?

tremobovesky;

Is JDK 1.4.1_02 == Mantis?

I was under the impression Mantis was JDK 1.4.2 (to be 
released 'early' in 2003).

This is kind of a critical bug, any ideas of an approximate date 
for the fix?

1.4.1_02 will be available sometime in the first quoter of 2003.

.. quarter, that is.

Mantis is 1.4.2. But this fix will be integrated into the
next 1.4.1 update release (1.4.1_02) as well.

Dmitri Trembovetski
Java2D Team

It appears that the latest drivers on ATI's site (released
November 14, 2002) fix their bug.  

I haven't even tested a full day yet, so take this with a
grain of salt.

I am trying to learn J2ME. I am using an IBM T30 notebook, 
with the ATI Radeon 7500 card that and have downloaded 
latest drivers from IBM. I don't know how to configure my 
Studio 4 or the Java plug-in to use the -D option as 
described in the work around. I must say that I am a not an 
absolute beginner with JAVA, but this unexpected bug is 
taking up my precious after work hours. JDK 1.0.4 is very 
disappointing.

khhong1800;

For Studio, go to the folder where bin directory in your 
installation, and edit the ide.cfg file.

There you'll see something like this;

-jdkhome "C:\j2sdk1.4.1" -J-Xmx96m -J-Xss1024k -J-
Xms24m -J-Xverify:none

Add the -D flags to that line, I think that should work. These 
are the startup parameters, so this has to be the right place.

Now, for Java Plugin;

Go to Control Panel
Double Click on "Java Plugin" icon
Click on the Advanced tag
Then add the "-D" flags on the "Java Runtime Parameters" 
field.

I think that should work.

+==============================

Now is my turn for a question, maybe somebody from Sun can 
suggest a solution.

We deploy our app with Webstart. We have some customers 
experiencing this problem, we can set the flags in the JNLP, 
but then EVERYBODY gets those flags. Seems to me our only 
clean option is to create a second JNLP_bsod_fix and have 
users with the problem link to that? Not a nice solution.

Thanks for the quick replies (trembovetski), however this is a 
very critical bug. If you guys have fixed it already, I think it 
justifies releasing a _01a or _02 version as soon as possible. 
We need 1.4.1 because of the DnD fix, so please, please, 
please, consider having a quick release with this fix!

I have experienced this problem on an IBM Thinkpad A31. The 
most recent IBM video driver version is 5.13.1.6114 and it 
does not fix this problem. It's not possible to install ATI's 
reference driver on a laptop, so I can't verify if ATI's 
version .6200 driver fixes this problem. 

I have verified that the problem does not occur in JRE 
1.4.0_03. For me this is the most acceptable workaround for 
now.

I have a webpage with a summary of the information about 
this bug here:

http://mozart.chat.net/~jeske/unsolicitedDave/thinkpad_ati_j
ava_bug.html

I am using ThinkPad A30p and Windows XP.  I asked IBM(in 
Japan) if they had some plans to fix this bug about the driver 
they provided.  IBM's answer was:

* IBM has no plans to fix it.
* The developer(ATI?) has no plans to fix it for ThinkPad 
users.

It annoys ThinkPad users.

Also happens with my Dell Latitude C640 with ATI Radeon
Mobility 7500. 
Is there an early access version of the JDK 1.4.1_02 with
the  bug fix?

From my point of view disabling Direct Draw hardly is a fix. I 
seriously hope that this can be fixed in a proper way later.

It's already been fixed guys, check out the status of the bug.

My only comment was if they can release this sooner rather 
than later, it seems like it's a critical bug.

What is the policy on these types of bugs? I would think a 
_03 release would be appropiate for this.

This also occurs with the internal video support in Compaq 
Evo computers.  We cannot use 1.4.x until this is fixed.  

Driver info:
Intel 82845G/GL Graphics controller
version 6.13.1.3119

fixed my asss. Java stinks so bad.

got this on win95:
DDHELP caused an invalid page fault in
module NVDD32.DLL at 017f:b00d9834.
Registers:
EAX=fff8e147 CS=017f EIP=b00d9834 EFLGS=00010286
EBX=b011c240 SS=0187 ESP=0105fd14 EBP=db2100c0
ECX=0105fd3c DS=0187 ESI=db2100c0 FS=704f
EDX=00018ce4 ES=0187 EDI=fff8e147 GS=0000
Bytes at CS:EIP:
8b 6e 0c 83 f8 ff 74 09 39 46 20 0f 85 dc 00 00 
Stack dump:
0105fd44 b011c240 0105fd44 b011c240 fff8e147 56668e01
56668e08 0105fd3c 97cc1cb0 56660000 fff8e147 00000000
0105fd84 baab964a b011c240 fff8e147 
when trying to exit netbeans latest.
also get similar whenever exiting JWS.
this is a P1 bug & the fix should be released ASAP.

I'm getting the same problem with a humble ATI XPERT 98 RXL 
(using XP). I start a Swing application and it will work for a 
few seconds and then the system restarts. No BSOD or 
anything.

I have seen this problem on windows 2000 with a "Trident
Cyberblade XP" video card.  Machine hard locks with JRE
1.4.1; I was using Version 1.4.0 previously and did not
experience the problem.  Why is the bug closed?  Is there a
new JRE out that does not have this problem with multiple
display adapters?

I am also having this problem on my IBM ThinkPad T30 with 
an ATI Mobility Radeon 7500 card. This is a major hinder on 
my j2se and j2me development. I would just like to point out 
that I am experiencing a similar problem to this when 
compiling in the J2ME Toolkit 2.0. Hopefully the new version 
will also fix this. In the mean time, does anyone have a work-
around for the J2ME Wireless Toolkit?

When exiting a Swing app, I get the following error message:

"Ddhelp has caused an error in <unknown>.
 Ddhelp will now close."

No details.

I am also a thinkpad t30 user with a Mobility Radeon 7500. 
This really isn't a jre bug, but a video driver bug... it
shows up in Mozilla also. IBM has said that they are aware
of the problem, but won't give any specifics about any
updates to the drivers. I encourage any other thinkpad users
to submit fix requests to IBM, if enough of us complain
maybe they'll do something about it.

Installing the current video card driver (version 6.13.10.6218) 
from the ATI website seems to have fixed this problem for 
me.  I have a desktop machine with a radeon VE card, XP 
pro, and jdk 1.4.1_01.

On my system (laptop Compaq Armada E500, video card ATI 
RAGE MOBILITY AGP, Driver version 5.0.2195.5033), with W2K 
SP2 most of application cause a SYSTEM STOP with the 
following message:
(*** STOP: 0x0000001E (0xC0000005, 0x8046AEB5, 
0x00000000, 0x00000420)
KMODE_EXCEPTION_NOT_HANDLED

*** Address 8046AEB5 Base at 80400000, dateStamp 
3d366b8b - ntoskrnl.exe)
Use of -Dsun.java2d.noddraw=true flag solves the problem 
(hope :-) ).

Partly correct! Workaround helps for plugin and Jar or Class 
files. But there is no way to start DeployTool of J2EE 1.4. 
Apparently LauncherBootstrap starts a new VM vithout 
passing the noddraw option! (and trial and error is a pain 
when each time you reboot W2K!!)

I have been having this same problem.  Very frustrating.  If 
anyone has any help, please e-mail me.

I've experienced a total system freeze when using the
1.4.1_01 JDK with NetBeans 3.4 on Windows 2000 SP3 on an IBM
T30 notebook (ATI Mobility Radeon 7500).

The IDE would shut down fine (so it seemed) and a few
seconds later the taskbar and start menu would stop
responding, and then a few seconds after that the whole
machine would freeze.  I had to unplug it and remove the
battery to reboot.

Nasty!

Note: ifyou can't disable the use of ddraw by java prior to
installing it, you can still disable the use of ddraw by the
system,  install java,  set the -Dsun.java2d.d3d=false in
the plugin control panel, and then enable ddraw in the
system again.

The ddraw can be disabled by either running "Program
Files/DirectX/Setup/dxsetup" application, or in the Display
Properties panel: click 'Advanced' button, then go to
'Troubleshoot' tab, and set the slider on the second mark
from the left.

Dmitri Trembovetski
Java2D Team

I just started learning Java.  I installed the Studio ONE IDE 
and came across this kind of problem.  I have an Nvidia 
GeForce 256 AGP card.  Using the flags reported in this thread 
did nothing.  (The IDE would not even open with these 
flags.)  I disabled DirectDraw, and I stopped getting the page 
fault whenever I exist the IDE.

How can this be listed as closed when 1.4.1_02 hasn't been 
released yet?

Since Sun's Java implementation is now being forced into 
Windows XP, I'd like to have one that doesn't crash my 
machine.

Will there be a new release of Sun ONE Studio when 1.4.1_02
is released? I get blue screens when running Sun ONE studio, 
and I need to use SOS for education purposes.
Please sun, make sure you rectify the problem with SOS as 
well, when you fix the problem with the SDK.

 - the bug gets marked as closed when the fix is integrated
into a release's workspace, even though the release is not
out yet

 - SOS won't need a new update once we roll out the jdk with
the fix -
  you'll just need to install this new jdk release and run
the ide
  with it. 
  The SOS download with bundled JDK will probably be
repackaged to have the latest jdk included (I'll have to
follow up on this, though)

  In the meantime, you can workaround the problem by running
  SOS with -Dsun.java2d.d3d=false parameter - edit
  Program Files/s1studio/ce/bin/ide.cfg, and add that parameter.

  You might also need to set this parameter in the project
settings, to make sure that the IDE runs your app with
d3d=false as well.

Basically, until the you get the release with the fix on
your machine, you should run any java app with that
parameter only.

Unfortunately, currently there's not a centralized location
where you'd set this option so all java instances would pick
it up automatically. You'd have to set it at least in
  - Java Plug-In control panel
  - in the SOS config file
  - in the project settings in SOS, so the IDE wouldn't run
your app w/o this option
  - set it for any app you're running from console

We're working on a centralized mechanism for things like
this for our next major release.

Dmitri Trembovetski
Java2D Team

FYI: 1.4.1_02, which contains the fix for this bug (among
many others), is expected to ship at the end of  Feb'03.

Dmitri Trembovetski
Java2D Team

Typo : my previous driver was 6.13.10.6166, not 
6.13.10.6218.

Had the same problem on XP with JRE 1.4.1_01 and ATI 
Radeon 7000 card with driver 6.13.10.6218. After installing 
the latest driver (6.14.01.6255) the problems went away.

Where did you find that driver?
Was it a mobility card?

My symptoms are slightly different than everyone else's and none of the workarounds mentioned seem to work for me.

I have ATI Radion 7000 Series with latest driver, 6.14.01.6255 and JDK1.4.1_01. 

Intellij IDEA, Borland Optimizeit and Java Plug-in Control Panel all exhibit same symptoms. I click and the process freezes during startup. CPU at 98 percent. I have to kill process via Task Manager.

In Intellij, splash screen never appears. In Optimizeit, I it freezes at splash screen.

Also, these symptoms are very random. It seems to work correctly more often after fresh reboot, but not all the time. Also, I've developed weird tricks, like copying and pasting a shortcut to the App sometimes enables the App to start. 

I am tempted to replace my video card! How frustrating!

Also, I have heard similar problems at my work place on a variety of machines. The workarounds mentioned here don't work.

Actually, one unmentioned workaround seems to work for me, which is to run in 256 colors, but I don't like this. It's ugly.

I really hope JDK1.4.1_02 fixes the problem. Given how unreproducible and how varied the symptoms, I am worried the JDK team will find it difficult to validate.

This is where I found the latest drivers :
http://www.ati.com/support/driver.html

I must confess this made me bang my head on the wall...
Now since there is a workaround, more questions to it: for
Java WebStart we can set this environment variable:
"JAVAWS_VM_ARGS=-Dsun.java2d.d3d=false". Does a similar
variable exist for java.exe and javaw.exe? Or do we have
another option of setting "-Dsun.java2d.d3d=false" system wide?

I am completely disgusted by the response to this issue.

On my computer (Compaq Laptop), this bug completely 
crashes my PC. 

I cannot update my ATI driver, because apparently with ATI 
Mobile chips, you MUST use drivers provided by Compaq, and 
they updated their drivers.

SUN considers this issue fixed, but the fix is NOT HERE. I 
don't have access to your early developer releases. This is 
ridiculous! In terms of the workarounds, apparently you must 
set variables for EVERY SINGLE Java program you run. This is 
stupid because I will have to undo each and every one of 
those settings the second that the new Java SDK comes 
out.  

I am frustrated and disgusted by the lack of response for 
something which isn't a "minor inconvenience", but a 
SHOWSTOPPER bug. If Microsoft released a Windows that 
would CRASH on startup every time you run it on certain 
Laptops, they'd be out of business quickly. 

Bug is present on an a Dell Optiplex GX260 (Intel video 
chipset)

Workaround addressed problem ok.

in a couple of weeks? Last I heard it was in february. 
Hmm..let me see....
GregorianCalendar gc = new GregorianCalendar();
gc.add(Calendar.DATE,7*2);
System.out.println("1.4.1_02 ready "+gc.get(Calendar.MONTH)
+", at the earliest".

We're on march now, aren't we. Why do you need to delay 
the release further? How long can you wait til we all start 
using .NET?

Regarding the problems with Intel card. It looks like you've
stepped into bug 4812026. Again, the drivers/os issue,
unfortunately. We're working on a workaround.

From what we know, installing SP1 for WindowsXP should fix
the problem.

Dmitri Trembovetski
Java2D Team

> If Microsoft released a Windows that would CRASH 
> on startup every time you run it on certain Laptops..

Not trying to be sarcastic, but that is exactly what they've
done.
The problem _is_ with the OS/video drivers, we just happen to
trigger it.

We understand your frustration, but there's not much we can
do now.
The 1.4.1_02, which contains the fix, should be out in a
couple of
weeks. Until then, you can disable d3d acceleration in the
windows
troubleshooting dialog (Display Properties/Settings/Advanced/
Troubleshoot - set the slider to the second point from the
left).
Or use DxDiag app to disable d3d acceleration only. 
This way you won't have to set the -Dsun.java2d.d3d=false
for every 
app.

Dmitri Trembovetski
Java2D Team

If I read all post here this bug is really a HUGE problem. I can 
understand that Sun maybe underestimated the dimensions of 
the bug in the beginnig as it seemed to only affect very 
special ATI graphic card configurations. But now it seems it 
affects a lot of different ATI cards on nearly all Windows OSs 
(Win 95 -Win XP). I don't know ATI's market share, but at 
least in Germany they seem to be in ervery second new 
computer (including mine). So, in a pessimistic scenario every 
second user with 1.4.1 hits this bug! It is hard to think of any 
better way to damage Java's reputation.
I cannot believe Sun is still offering 1.4.1 incl. the bug as the 
JRE for the masses on it's webpage. After half a year! Offer 
1.4.0_03, if it takes longer to fix it.

Dmitri,

Thank you for taking your time to address my concern. 

First, let me point out that this is not a Microsoft related bug 
like you've stated (without sarcasm). This bug has to do with 
an ATI driver not conforming to the published DirectX API. 
The irony here is that ATI have "passed the buck" in terms of 
updating mobile drivers to the separate laptop vendors. For 
example, on my laptop, I am simply unable to upgrade my 
driver because Compaq has not released any new video 
drivers. I am a very heavy computer user - I program for a 
living, and use a LOT of computer applications. Since Java 
1.4.1_01 is the only application that I've ever seen that's 
affected by this driver issue, I can see Compaq and other 
vendors not giving a lot of hoot about the problem. The ball is 
apparently in your court, and you've dropped it. You cannot 
go out on a limb and say that "Microsoft broke it" because 
nothing else is broken other than your software.  I've had the 
displeasure of dealing with faulty API specs from time to time. 
There are ways around the issue.

Now the fact that this issue dates back to some time in July 
and still no fix has been released is a HUGE discredit to SUN. 

Also, a couple more data points on the bug: Turning  D3D off 
in dxdiag did not fix the problem - Java programs would no 
longer crash on startup, but they WOULD crash the computer 
completely when you try to exit. I had to turn off DirectDraw 
completely for the problem to go away. I run a Compaq 
Presario 2110, with an ATI RS320 U1 Mobility IGP Radeon.

Still awaiting a solution,

Greg Sherman
Senior Programmer/Analyst
ESI Computer Solutions

I have the same hang on an Acer Laptop (TravelMate 427LC, 
ATI Mobility Radeon 7500 1024x768-32 bit, driver , win2k and 
win XP, JDK 1.4.1_01, all service packs & fixes) exiting any 
Swing application. Suggested workaround (-
Dsun.java2d.noddraw=true) doesn't work at all.

The bug was submitted in july, it took you two and a half 
months to identify it. Now 5 months later, you say the bug is 
fixed, still you are not releasing the new improved SDK 1.4.1. 
If you are awaiting the correction of other bugs, why don't 
you release a 1.4.1_03 shortly after, with more updates?

The ATI bug is critical to many of your users, and frankly, 
you don't seem to take us all that seriously. Using almost half 
a year to fix a vital bug!

Utterly disapointed!
PS: The workaround doesn't work. No more blue screen, but a 
freeze instead.

Reproduced this problem on Win2K using an ATI Radeon
All-in-Wonder (original version, no number like the 7500),
latest video drivers (Catalyst 3.1), JRE 1.4.1_01 and the
editor Jedit (www.jedit.org). 

FYI: http://java.sun.com/j2se/1.4.1/ReleaseNotes.html

1.4.1_02, which has a fix for this bug, is out today,
02/27/2003.
Please let us know if it doesn't fix the problem for some reason
on your configuration. The earlier we know, the better.

Dmitri Trembovetski
Java2D Team

It worked!  However, I couldn't just install the 1.4.1_02 
version over the 1.4.1_01, that didn't work.  I had to uninstall 
1.4.1_01 then re-install 1.4.1_02.

Hoooray!
Finally I can use SOS!

Initial tests w/ 1.4.1_02 look good here. Tested on ATI 
machines that rebooted w/ _01 every time on JPI init. Works 
like a charm with _02. THANK YOU!

It doesn't work for me. 

I still get the blue screen and reboot when starting 
JavaWebStart. I uninstalled 1.4.1_01, rebooted and installed 
1.4.1_02. 

So whatever fix was made it doesn't help on Dell Latitude 
H500GT...

The fix has worked perfectly on my Thinkpad A30p with ATI 
mobility radeon under Win2K.  I uninstalled the evil 1.4.1_01 
before installing the wonderful 1.4.1_02 and have been 
happily running heavy duty Java apps that use the 1.4 direct 
draw feature.  No crashes or complete system freezes 
anymore.  Java is back on track. Thanks Java2D team. :-) :-)

I still got BSOD even with 1.4.1_02 when starting Java Web
Start.
My environment is as follows.

Machine: Sharp Mebius (sold only in Japan)
Graphics: ATI RAGE Mobility-M PCI
version: 5.0.2195.5011
Driver version: M6.12.1-T05

The fix worked as promised. 

Thank you.

To anyone still seeing the crash bug after installing 1.4.1_02:
We'd like to get more information about the problems you
are seeing and the system configurations that you are using.
Please send us email at java2d-comments@sun.com.  The fix 
for this bug should have nailed the problem, and apparently 
did for most users.  So whatever problem is still there for 
some of you is news to us and we want to track it down.
Thanks,
Chet Haase.
Java2D

I'm still having a problem .... sometimes.  I develop using
NetBeans 3.4.1 and have plugged in JTest 4.5.2.  When I
attempt to run JTest from NetBeans, I encounter the problem
when I try and close JTest.  The computer appears to
'freeze'.  I can move my mouse for maybe 20 seconds, am
unable to click on anything, and then the mouse freezes and
I'm forced to restart.

I have an ATI video card driver version 6.13.10.6178.  I'm
running Windows 2000 5.00.2195 SP 3.

Using a Fujitsu Simens P4 PC with Win2K sp2 jre1.4.1_02 I see 
the same problem as I did with jre1.4.1_01. The graphics chip 
is a Intel 82845G Graphics Controller and the driver version is 
6.13.01.3413. The bug manifests itself by rebooting the 
machine when running any Java Swing GUI. As we are 
deploying on thousands of PCs we are stuck with 1.4.0 until 
the problem is resolved.

Running Dell Dimension 4550 with ATI Radeon 9700, driver 
6.13.10.6143. Java 1.4.1_02-b06 (and previous). Freezes 
when attempting debug on First Example (colorswitch).

Thanks everyone for the updates. 

A couple of suggestions to those having problems even with
1.4.1_02:
 1. This is an obvious one, sorry, but we've already
confirmed that it was the cause of the problem for some
people. Prior to installation of the new jre/sdk, please
uninstall previous jdk's, including JavaWebStart. Note that
it doesn't get uninstalled automatically when you uninstall
jre/sdk. This is to make sure you're using the updated bits
instead of the old ones. Also, make sure your IDEs are using
the latest jdk as well.

 2. If you're having problems with JavaWebStart only (apps
started from command line console work fine), you may be
running into bug 
   4812026: J2D caused Java Web Start to crash Windows XP HOME
   First, try installing the latest Service Pack for XP. If
it doesn't help, try the following crude workaround: remove
splash images from Program Files/Java Web Start/resources -
those .jpg files. 

Dmitri Trembovetski
Java2D Team

I uninstalled ws, jre and jdk before installing 1.4.1_02. The 
Swing client I tested with was started from the command line.

According to the information written in BugID  4749817,
I uninstalled Jbuilder8(jre1.4.1_01) and j2re1.4.1_02,
and installed in the order j2re1.4.1_02 ->
Jbuilder8(j2re1.4.1_01).

With this installation order, BSOD did not appear.

However, when I installed in the order JBuilder8 ->j2re1.4.1_02,
JavaWebStart uses j2re1.4.1_01 included in JBuilder8,
and BSOD appeared. 
I do not know the reason why JWS persist in using j2re in
JBuilder8.

When I try to run the demo's included in 1.4.1_02 I get errors.
SwingSet2.jar produces the splash screen, and that's all.
I have to terminate javaw.exe from the task manager to
stop it.
SwingSet2.html works though.

Might have something to do, with me having installed JRE1.3.1
for use as an applet plugin?

Double-clicking the other jars produces a error "Main class 
not found"
?

I am using a NEC Versa S260 notebook computer with an ATI 
display card, Windows XP Home Edition, JDK version 1.4.1_02 
and Netbeans 3.4

The problem occurs when I close Netbeans 3.4, the screen 
just freezes and I was forced to power off & power on my 
computer again.. 

no blue screens or whatever..

sorry about my last message, ironically jdk 1.4.1_02 works 
perfectly for my NEC Versa S260... absolutely no problem, 
thanks Java2D :)

I get the same problem with Thinkpad A31 which uses ATI 
Radeon 7500.  Support people at IBM keep telling me it is 
something I installed rather than driver.  Problem is not Java 
specific - spider Solitaire is enough to trigger it and I doubt 
that is Java.  Will try 1.4.1_02 and IBM released new driver 
today - will try that.

I have a HP pavilon laptop with windows Xp professional (ver 
5.1 ,service pack 1) and i have installed sun one studio (IDE/1 
spec=1.43.3.1 impl=021108 VM:Java HotSpot Client VM 
1.4.4_01-b-01).The system freezes after about 1