JDK-4749817 : BSOD in WebStart: Win2k/XP with ATI graphics
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 1.2.0,1.4.1
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_98,windows_2000,windows_xp
  • CPU: x86
  • Submitted: 2002-09-18
  • Updated: 2002-11-26
  • Resolved: 2002-11-26
Related Reports
Duplicate :  
Description

Name: nt126004			Date: 09/18/2002


FULL PRODUCT VERSION :
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)


FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195],
Service Pack 3



EXTRA RELEVANT SYSTEM CONFIGURATION :
ATI Rage Mobility. Latest driver (5.00.2195.5026). The crash
occurs both with DirectX 8.1 and the version supplied by a
stock SP3 Win2k (whatever that is).

A DESCRIPTION OF THE PROBLEM :
As soon as I start Java Web Start by doubleclicking, Windows
crashes with a BSOD. The error is KMODE_EXCEPTION_NOT_HANDLED.

I saw this with 1.4.1rc as well, but thought it was related
to 4713003. I guess I was wrong...

REGRESSION.  Last worked in version 1.4

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Doubleclick on Java Web Start.


REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER WORKAROUND :
The only workaround I've been able to find is to disable all
DirectDraw and Direct3d acceleration in "Display Properties".
(Review ID: 164586) 
======================================================================

Name: nt126004			Date: 09/18/2002


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 2000
[Version 5.00.2195]
Service Pack 3 installed


EXTRA RELEVANT SYSTEM CONFIGURATION :
Compaq Armada M700 laptop, PIII, EPP Bios V1.1, 256MB RAM,
14GB HDD (7GB free), Linksys Wireless Network PC Card V3.0

A DESCRIPTION OF THE PROBLEM :
When I click on the Java Web Start shortcut, the
application opens, and after presenting a lozenge screen
and opening the application window briefly, blue screens,
requiring reboot.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. From Desktop, click on Java Web Start shortcut.
2. Initial Window comes up, then system blue screens


EXPECTED VERSUS ACTUAL BEHAVIOR :
Expected: application to run
Actual: BSOD (blue screen of death)

ERROR MESSAGES/STACK TRACES THAT OCCUR :
*** STOP: 0x0000001E (0xC0000005, 0x8046AEB5, 0x00000000, 0x00000840)
KMODE_EXCEPTION_NOT_HANDLED

***ADDRESS 8046AEB5 base at 80400000, DateStamp 3d366b8b -ntoskrnl.exe

I will supply memory dump and any other details upon request

REPRODUCIBILITY :
This bug can be reproduced always.
(Review ID: 160368)
======================================================================

Name: nt126004			Date: 09/18/2002


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 :
Usual setup

A DESCRIPTION OF THE PROBLEM :
Whenever I start Java WebStart 1.2 Beta (installed along
with JDK/JRE 1.4.1 beta) and choose to exit the program
(through the standard windows close button), my machine
reboots.

My machine spec. are Athlon 1.7 GHz, Windows XP Prof.

I have no idea what the problem might be and I have never
experienced a reboot initiated by a Java Application
(crash?).

REGRESSION.  Last worked in version 1.0.1

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. start up WebStart
2. close the program (either through X in upper right
corner or through taskbar, rightclick on app, choose close)
3. see the machine reboot

EXPECTED VERSUS ACTUAL BEHAVIOR :
machine should continue running instead of rebooting.

REPRODUCIBILITY :
This bug can be reproduced always.
(Review ID: 160633)
======================================================================

Name: nt126004			Date: 09/18/2002


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

FULL OPERATING SYSTEM VERSION : XP with service packs and
critical updates applied


A DESCRIPTION OF THE PROBLEM :
starting the notepad web start sample crahes XP.  At first
the mouse pointer just stops, but then a BSOD arrives.
When my thinkpad reboots it wants to send an error report
to MS becaue of an error in an ati radeon 7500 driver.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. load 1.4.1 Rc onto an xp thinkpad.
2. run notepad sample web start application
3.

EXPECTED VERSUS ACTUAL BEHAVIOR :
notepad would run correctly.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
sorry the bsod shows and then clear the screen a few seonds later.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER WORKAROUND :
don't run web start apps ;-{
(Review ID: 163999)
======================================================================

Name: rmT116609			Date: 09/23/2002


DESCRIPTION OF THE PROBLEM :
Starting Java WebStart from the desktop shortcut causes a blue screen

(Review ID: 164823)
======================================================================

Name: rmT116609			Date: 10/02/2002


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

EXTRA RELEVANT SYSTEM CONFIGURATION :
ATI Radeon Mobility 7500 Video Card

A DESCRIPTION OF THE PROBLEM :
When I run java web start demo app , system become blue screen and system restart.


(Review ID: 165237)
======================================================================

Name: rmT116609			Date: 10/07/2002


A DESCRIPTION OF THE PROBLEM :

I am having a critical problem with JRE 1.4.1 and/or the J2SE SDK on Windows XP and am hoping you can provide some insight.

Previously I'd had earlier JRE 1.3.1 and 1.4.0 versions installed on this machine.  I removed both of those at the same time with the Windows Add/Remove Programs utility, and then installed the 1.4.1 SDK.  Afterwards, I
launch the "Java Web Start" utility and my machine reliably *reboots* without warning just after I choose any one of the 4 demos and press the run button.  The reboot occurs while a Web Start splash screen is up.  This reboot also occurs when I run the Web Start demos from the java.sun.com Web site (the splash screen is up here, too, when it reboots).

Two other conditions have caused the reboot:

1. When I ran my own Swing Applet through IE 6, it has rebooted 2 times while
I assume the JRE was loading.  Yet this applet has run perfectly without changes
about 6 other times.  It's a simple applet that just puts a Swing button in a container.
The intermittent crash is odd: I hadn't changed the program at all.

2. I installed Forte for Java 4 CE, then launched the program and went to the updates page.  I downloaded 3 updates, okayed their signatures,
and then clicked the finish button.  Immediately the machine rebooted.

Has anything like this been seen before?  I ran a RAM burn- in test to check that
as a possible problem, but the test passed.  These reboots don't happen under
any other applications.



(Review ID: 165392)
======================================================================

Name: rmT116609			Date: 10/07/2002


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

EXTRA RELEVANT SYSTEM CONFIGURATION :
Sony Laptop (PCG-FXA53) with AMD Athlon, ATI Rage Mobility

A DESCRIPTION OF THE PROBLEM :
I have a PCG-FXA53 Sony Vaio Laptop with XP Home edition and jdk 1.4.1 installed.  When I run Netbeans, InstallAnywhere with 1.4.1VM bundle, and a few other apps, I get the blue screen and a reboot.  The blue screen shows
"BAD_POOL_CALLER".  If Load any version of Java prior to jdk 1.4.1, then I do not get any errors and everything runs fine.

I guess I'm not the only one seeing this:
http://forum.java.sun.com/thread.jsp?forum=54&thread=305813&start=0&range=15#1228293


(Review ID: 165398)
======================================================================

Name: rmT116609			Date: 10/10/2002


EXTRA RELEVANT SYSTEM CONFIGURATION :
Machine is Compaq Armada m700 laptop
display adapter ATI RAGE MOBILITY dirver version
5.0.2195.5026

A DESCRIPTION OF THE PROBLEM :
Upon running several swing applications including ArgoUML and JavaWeb Start a blue screen of death occurs before the main window is shown, (normally while the splash screen is being displayed)

*** STOP : 0x0000001E ( 0x00000005, 0x8046AEB5, 0x00000000, 0x00000420)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8046AEB5 base at 80400000, DateStamp 3d366b8b - ntoskrnl.exe

Begining of dump of physical memeory Physical memory dump complete. ....

REGRESSION.  Last worked in version 1.4

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1.Run Java WebStart from desktop

EXPECTED VERSUS ACTUAL BEHAVIOR :
Splash screen appears. Before main applicatin window is displayed blue Screen of death occurs

ERROR MESSAGES/STACK TRACES THAT OCCUR :
*** STOP : 0x0000001E ( 0x00000005, 0x8046AEB5, 0x00000000, 0x00000420)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8046AEB5 base at 80400000, DateStamp 3d366b8b -ntoskrnl.exe

Begining of dump of physical memeory
Physical memory dump complete. Contact your system administrator or technical support group.

(Review ID: 165603)
======================================================================

Name: rmT116609			Date: 10/10/2002


 DESCRIPTION OF THE PROBLEM :
Splash caused a invalid page fault in module KERNAL



(Review ID: 165627)
======================================================================

Name: rmT116609			Date: 10/14/2002


EXTRA RELEVANT SYSTEM CONFIGURATION :
IBM Think Pad A20m: Celeron 500 CPU,128M RAM,
ATI RAGE MOBILITY-M AGP,

A DESCRIPTION OF THE PROBLEM :
I install the J2SDK 1.4.1 and Sun ONE Studio 4 CE. When I run the Sun ONE Studio ,my pc show me a blue screen and reboot. The same thing happen,when I try the Borland JDataStore 6. Then I uninstall the J2SDK 1.4.1 and install J2SDK
1.4.0_02-b02 ,the two program work well.

(Review ID: 165687)
======================================================================

Name: rmT116609			Date: 10/16/2002


A DESCRIPTION OF THE PROBLEM :
It crashed with "Windows Blue-screen of Death" whenever I tried to execute any application using the JDK "1.4.1_01".  This includes running the Java WebStart Application Manager that comes pre-installed with the JDK_1.4.1.

 To confirm this, I used JBuilder 7 to compile a sample application (dbSwing->Buttons) application.  It crashedeach time I run the compiled application when using JDK_1.4.1.  Furthermore, I proved that the same sample
application works perfectly fine when I chose to compile using JDK_1.3.1_b24 (that comes with JBuilder 7) instead.

The bug is consistent and reproducible.


(Review ID: 165867)
======================================================================

Comments
WORK AROUND An easy workaround for a normal Java application would be to run without d3d support: java -Dsun.java2d.d3d=false The workaround for WebStart is a bit more involved, because WebStart is started from native code, not the command line. The best workaround is to put the same d3d command-line flag in the application's jnlp file: <property name="sun.java2d.d3d" value="false/> This property tag goes in the resources section: <resources> <property .../> </resources> See the JNLP specification, section 4.2 (setting system properties) for more information. Another option is to set the JAVAWS_VM_ARGS environment variable, as in: set JAVAWS_VM_ARGS=-Dsun.java2d.d3d=false Note that you must either run javaws in the same command-tool that you use to set the variable or you must set the variable system-wide so that Web Start picks it up when executed from the desktop.
11-06-2004

EVALUATION This problem could be related to bug 4713003. In that bug, our allocation of several d3d Devices (one per ddraw surface) causes a problem in the ATI driver or hardware and we end up crashing or hanging when the app exits. What is not clear yet is whether this crash/hang could also occur at application startup, which at least some of the submitters have seen with Java WebStart. It is also not clear yet what all of the vdeio cards/drivers are that are in use by the submitters; I will include that information here as we gather it. ###@###.### 2002-09-23 Information on systems that do and don't fail: 1) Desktop: fails on webstart exit (bug 4713003) but not on app startup OS: Win2k, SP2 Graphics: ATI Radeon 7500 Driver: ati2dvag.dll 5.13.1.6043 DirectX: 8.1 2) Dell laptop: doesn't fail on app startup or exit OS: Win2k, SP2 Graphics: ATI Rage Mobility-M AGP2X Driver: ati2drab.dll 5.0.2195.4045 DirectX: 8 3) IBM Thinkpad: Webstart fails on startup OS: WinXP, SP1 Graphics: ATI Rage Mobility-M AGP Driver: ati2drab.dll 6.13.10.5779 DX: 8.1 4) ATI Radeon mobility, hang/crash on startup OS: XP, SP1 Graphics: ATI Mobility Radeon 7500 Driver: ati2dvag.dll 6.13.10.6114 DirectX: 8.1 5) Win2k OS: Win2k, SP3 Graphics: ATI Rage Mobility AGP Driver: ati2drab.dll 5.0.2195.5033 DirectX: 8.1 6) Win2K OS: Win2k, sp3 Graphics: ATI Rage Mobility AGP Driver: ati2drab.dll 5.0.2195.5026 DirectX: 7 7) Win2k OS: Windows 2000 (version 5.0 Service Pack 3 (Build 2195)) Graphics: ATI RAGE MOBILITY-M1 AGP2X Driver: ati2drab.dll version 5.0.2195.5040 DirectX: DirectX 8.1 or greater 8) WinXP OS: Windows XP (version 5.1 (Build 2600)) Graphics: ATI RAGE MOBILITY-M1 AGP Driver: ati2drab.dll version 6.13.10.5779 DirectX: DirectX 8.1 or greater ------------------------------------- More info about blue-screening on ATI cards: I discovered the source of one system crash which doesn't seem like it's the cause of the crash-at-startup problem, but does seem to validate our findings that all of these crashes are related to interaction with d3d devices. In our latest code, we now create only one d3d device (this is the fix for 4713003). On DisplayModeTest (a fullscreen regression test), I see a blue-screen system crash every time I run the app. The crash appears to be caused by using a d3d device that was created with the primary surface on a surface that is created after a switch to fullscreen mode. The fix to this problem appears to be restoring the primary surface and recreating the d3d device. ###@###.### 2002-09-26 Verified that the current build of 1.4.2 (which has the fix to 4713003) fixes this bug. Closing this one as duplicate of 4713003. The first public releases that will have this fix are 1.4.2 (Beta and, eventually, FCS) and 1.4.1_02. ###@###.### 2002-11-26
26-11-2002