Note: LucasForums Archive Project
The content here was reconstructed by scraping the Wayback Machine in an effort to restore some of what was lost when LF went down. The LucasForums Archive Project claims no ownership over the content or assets that were archived on archive.org.

This project is meant for research purposes only.

Lego Star Wars II - Windows error.

Page: 1 of 1
 mcramsey
06-24-2007, 2:04 AM
#1
PC version.

Episode IV, Chapter 1: Secret Plans.

The 1st mission.

"After the short movie, the Princess will no longer be in your party. Use R2-D2 to open the door into the next room and run over to the cranes operating the cockpit"

When I use R2-D2 to enter the room...windows error pop up.


My system info:

Operating System: Windows XP Professional
System Manufacturer: NVIDIA
Processor: AMD Athlon(tm) XP 1900+, MMX, 3DNow, ~1.6GHz
Memory: 1024MB RAM
Page File: 282MB used, 2179MB available
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 6800 GS
Manufacturer: NVIDIA
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.8412 (English)
DDI Version: 9 (or higher)
-------------
Sound Devices
-------------
Description: Realtek AC97 Audio
Driver Name: ALCXWDM.SYS
Driver Version: 5.10.0000.5210 (English)
 LucasForumFreak
06-24-2007, 8:20 PM
#2
What does the Windows error say??
 mcramsey
06-25-2007, 2:31 AM
#3
What does the Windows error say??

The one that say:

"Lego Star Wars II...need to be closed"

Then there's two(2) buttons that says:

"Send Report" and "Don't Send"
 LucasForumFreak
06-25-2007, 9:32 AM
#4
Try reinstalling the game. It may just be a random glitch, and will be fixed when re-installed.
 mcramsey
06-25-2007, 1:04 PM
#5
Try reinstalling the game. It may just be a random glitch, and will be fixed when re-installed.

This is the error:

http://img511.imageshack.us/img511/5894/untitledqz6.jpg)
 DarthMaulUK
07-21-2007, 1:46 PM
#6
Need a more detailed report of your dxdiag really. Try grabbing the latest drivers from Nvidia, new ones are out now. See if that fixes it
Page: 1 of 1