975X - 4 GB - Problems with SB X-Fi

Hello together,
I have a problem and really hope you guys can help me (I have no clue how to fix it...).
First of all, my System:
CPU: Intel Core 2 Duo E6600
MB: MSI 975X Platinum Power Up Edition
PSU: be-quite 530 W
Graphic: MSI NX7900GTO
RAM: 4 x 1024 MB DDR2-667 (Infineon)
Sound: Soundblaster X-Fi XtremeMusic
OS: Windows XP SP2 (see below)
After I built in the sound card and booted Windows, several problems appeared:
- Instead of the mouse cursor, a white square is shown
- Some Desktop-Symbols are black
- Some Tray-Symbols are not displayed
- Black squares are shown in the screen
- The System crashes often
When I take out one of the 1024 MB RAMs (no matter which one), the system runs fine again.
To fix the Problem (with 4 GB RAM and sound card) I already tried to install the Creative Drivers and tested the following boot.ini switches:
/usepmtimer
/pae
/maxmem=4096
/maxmem=3072
/maxmem=2048
/3GB /USERVA=2990
How can I fix this problem?
Does anyone have a similiar configuration which works?
Many thanks in advance
--- UPDATE ---
I installed Windows XP 64 Professional & updated my BIOS to Rev. 7.3. Unfortunately, the problem also exists under the 64-bit OS.
Any Ideas?

Quote from: AndiX on 17-November-06, 06:12:42
@Exo: I don't think that this is the Problem: I exchanged the the sound card with a PCI NIC - No problems.
Somehow, replacing a soundcard with a network card does'nt seem to be a good test to me 
You'll be wasting part of your 4 Gigs anyway if you stick to a 32 bit OS, The main reason 64 Bit was created is to overcome this memory limitation...
With 4 gigs physically taken, where will windows put its virtual memory ? Where will your VGA Ram be mapped ? what and where do creative's drivers do in memory ? ...
edit : After reading some posts on other forums it seems X-Fi cards actually do play around with memory mapping

Similar Messages

  • Strange major problem with 975X PowerUp Intel MOBO

    I’m suddenly having a strange major problem with a MSI 975X Platinum PowerUP Edition V2.1 MS-7246 Intel socket 775 motherboard. Previously, it had given me no problems at all.
    It went like this:
    Powered on system in the morning, booting from a cold start.
    Hit DEL key to get into the BIOS.
    Missed the window and the system booted into Windows normally.
    Re-started the system from within Windows.
    Hit DEL key to get into the BIOS and was successful the second time.
    Hit the ENTER key on the first item “Standard CMOS Features”.
    The DATE, TIME and other information was displayed on the next screen, but at this point, the BIOS screen became completely unresponsive to any keyboard input.
    The only thing I could do at that point was to power off.
    Subsequent power on boot-ups resulted in the system always freezing at the BIOS splash screen after the video card sign-on.
    I have switched power supplies, hard drives, keyboards and video cards. I have disconnected everything except the video card, keyboard and one RAM module. I have switched the four RAM modules around and then reduced the RAM to one 256MB module in the proper slot. I even changed the battery on the MOBO, in case it had shorted out and removed and re-seated the BIOS chip. It still halts at the BIOS splash screen.
    The BIOS chip can’t be completely dead, because I powered off and pushed the BIOS reset button on the MOBO to reset the BIOS to the factory defaults. When I re-booted, I could tell that it had actually reset to the factory defaults because I had previously set the BIOS to reboot the system on resumption of power and the factory default was to remain off until the power button was pushed, which was now the default.
    I’m stumped! All I can think of is to get a new pre-programmed BIOS chip and see if that makes any difference, but I’m not sure this system is even worth the expense with no guarantee of success. Any suggestions on how I might get past the BIOS splash screen or do I for sure have a corrupt BIOS chip?

    System specs as per the posting guidelines -
    Board: MSI 975X Platinum PowerUP Edition V2.1 MS-7246 Intel socket 775
    Bios: Version (can’t recall & can’t check since it won’t go past the BIOS splash screen)
    VGA: ASUS EN7600GS nVidia GeForce 7600GS PCI-e 256MB DDR2 (also tried new XFX nVidia
             Geforce 210 PCI-e 2.0 512MB DDR3)
    PSU: Chiefmax 680W ATX (also tried new OCZ 700W ATX)
    CPU: Intel 2.8GHz LGA-775 Core2 Duo Dual-Core Processor
    MEM: 4 x Samsung 512MB 1Rx8 PC2-5300U (2GB total)
    HDD: Seagate Barracuda 250GB SATA2 (also tried Seagate Barracuda 500GB SATA2)
    COOLER: Intel OEM LGA 775 fan/heatsink C25897-001
    OC: No
    OS: Vista Home Premium 32-bit
    I have been through the BIOS reset procedure several times and pretty much as outlined. As I said before, I could tell that it had taken a reset to the factory defaults, because the power on option had changed.

  • [Vista x64] Microphone problems with X-Fi and 2.15 drive

    Hi guys,?I'm having a problem with the 2.5 drivers on my X-Fi Platinum card, under Vista x64. It seems the microphone inputs (both on the card and on the breakout box) have problems, any recordings stutter and pop rapidly, making any recordings (or voice chat)?quite useless. This issue doesn't occur with the 2.3 drivers. Is there any known solution to this problem yet?My system: e6600 CPU, Asus P5W-DH motherboard (975X chipset), 4GB RAM, 8800GTX, X-Fi Platinum. Thanks.

    hey Darkman,
    since I never had this problem with installing this software, I cant really tell whats wrong, but you dont need it anyway to use the x-fi.
    but you may want to try one thing, since it crashes at 27% something may still be in use, so check your task manager and close everything that has CT in its name. then try reinstalling again. If that still doesnt work, try to empty your temp folder, its located in documents and settings/user you are/local settings/temp
    if that still doesnt work, try maybe something stupid, wait a bit longer than usual and keep the install window in the front to watch the process, maybe your pc is just a bit slowed down by other software so it may take longer than normal

  • Massive Sound problems with X-Fi Gamer F. Pro + BF2

    Hi,
    First of all, my system:
    CPU: Intel E6400 (not overclocked)
    Mobo: DFI Infinity 975X/G (most recent BIOS)
    RAM: 2 GB OCZ
    Video: GeForce 7900 GT
    Other PCI card: Netgear W-Lan card
    OS: Win XP 32 Bit SP 2
    I bought a new X-Fi Xtreme Gamer Fatalty Pro. (SB0460) last wednesday. It's working fine except in BF242. The trouble starts when I change the Settings to "X-Fi" and very high sound quality. As soon as I start to load a map I hear some strange scratching noise and sometimes the music disappears. And then all of a sudden something like a soundstorm bursts out of my speakers (http://rapidshare.com/files/527654/Stoergeraeusche.mp3.html for those who would like to hear it). It sounds as if the X-Fi was accessing the BF242 sound database and mixing all kinds of different sounds with some scratching noise. This only happens in gaming mode and only if I turn on "X-Fi" in the BF242 settings. If I choose "hardware" instead (resulting in very high sound quality not beeing available anymore, only high quality) I don't have any problems at all. This leads me to believe that there might be some issues with EAX 5.0. BF242 is the only EAX 5.0 game I own and the only game I'm having problems with.
    I've already deinstalled the drivers and removed all the remains with with "Driver Cleaner". I reinstalled them, I've switched the W-Lan card with the X-Fi, I've removed the W-Lan card completely and I've reinstalled BF242, but without success.
    Is there any solution for this problem or could it be possible that I bought a broken X-Fi?
    Regards,
    Niddi

    I Join the club i have had this problem for ages my games will just freeze and then i get this crazy screetching noise i have never been able to fix the problem its creative all over for you crapy drivers i have had enough of creative and wont be bying one of their cards again try it in a different pci slot or try some different drivers if its still in warranty complain to creative get shirty with them and they might rma it if all else fails goods luck rich

  • 975X Platinum PUE problem

    I'm building a system round the 975X Platinum power up edition, using an Asus ATI X1600Pro 512MB PCI-E Graphics card, Intel PentiumD 945 3.4ghz Lga775 Fsb800 2 X 2m, Corsair 2GB Kit (2x1GB) DDR2 667MHz/PC2-5400 RAM and Western Digital WD5000AAKS 500GB SATA II 7200RPM 16MB Cache - OEM. On first boot up, I got no video signal and after a couple of minutes the machine just shut down and I couldn't get it to reboot.  Have I got a compatibility problem and if so what with?

    Ebuyer Extra Value 500w ATX Power Supply in Blue With Dual Fans sorry no other details on it but am going to get an
    Enermax Liberty 400W Modular ATX2.2 PSU
        Specification     Value                     Main Specification
    General    Device Type    Power supply
       Form Factor    Internal
       Specification Compliance    ATX12V 2.2
       Width    15 cm
       Depth    14 cm
       Height    8.6 cm
    Power Device    Input Voltage    AC 100-240 V
       Input Voltage Range    AC 100 - 240 V
       Frequency Required    50 - 60 Hz
       Output Voltage    +3.3, +5, ±12 V
       Output Connector(s)    4 PIN internal power, 4 PIN mini-power connector, 15 pin Serial ATA power, 6 pin PCI Express power, power 24 pin ATX with detachable 4 pin section
       Power Output Connectors Details    2 x 6 pin PCI Express power ¦ 1 x 4 PIN mini-power connector ¦ 6 x 15 pin Serial ATA power ¦ 6 x 4 PIN internal power ¦ 1 x power 24 pin ATX with detachable 4 pin section
       Power Provided    400 Watt
    Miscellaneous    Features    Fan speed monitoring, 120 mm fan
    Also cleared cmos etc and still no go, once I have changed the PSU will try again, the D-bracket led display didn't seem to make sense as it wasn't listed in the manual.  I'm wondering if I've got a typical ebuyer pup as I have had this sort of problem with Motherboards from them before!
     

  • Core2Quad Q6600 on MSI 975X PowerUp Edition problem

    Hello. I have a problem that is bugging me for about one month.
    I have this configuration with an Intel Core2Quad Q6600 on a MSI 975X PowerUp Edition mainboard, with 4G Ram memory from Kingmax (4x1G DDRII 800 MHz) <The mainboard has the latest bios version 7.7>. I am running on Windows Vista x64 OS and I always get a blue screen after a nonequal period of time. I have remarked that usually it happens when running a media file (e.g. movie, DVD, play mp3) and downloading something from the internet. If I only do one type of operation at a time nothing happens, but if I do both types in the same time... in crashes. I can't figure out what may be the problem I've ran 32 memtests (one with v1.70 and one with v3.4) on each memory on each slot (4 memories x 4 slots) and got no errors. Of course than I ran one single test with both versions of memtest with the full 4G installed and got a lot of errors only on test 8 of them (regardless of the relevancy of 4G on a memtest that is on 32bit).
    I also gave a memory test from the Windows Vista x64 DVD and the system hangs at 37% for hours. I checked the HDD and has no problem.... Now I don't know what else to test anymore in order to see what may be the problem. Is it somehow a problem from the processor?, any incompatibility in the system?
    I saw that when making the regular updates for windows, on one particular update the system crashes giving me the same BSOD that bugs me (note thet the system does this problem imediatly after a clean install with no updates, and after the updates are installed)
    I've installed windows about 5 or 6 times on this configuration. Not once crashed or hanged during installation and in windows... in applications, never hanges or crashes into the same applications... they work just fine... only when I am using some media and downloading.... it happens at a total random time between a few minutes and even one hour. Sometimes if I am lucky I watch an entire movie while downloading and nothing happens... I just don't get it.
    Ah.. and when I get BSODs it never is the same error. Or it's a memory adress (stop error 0x0029940<random at adress 0x41625753<random), or it's a win32.sys, or it's a ntfs.sys, or some other file stored in windows directory.
    Please tell me what should I try? any DOS or Windows programs that may stress the CPU in order to see if it's OK please just help me somehow, any ideea will be good.
    I wonder if anyone from MSI could give me a hint or at least tell me about a software they use currently in order to debug a MB problem (if t's possible to do so).
    Thanks

    Same problems here.
    https://forum-en.msi.com/index.php?topic=112892.0

  • 975x platinum pue problem con raid sata and ide 2

    Blank I have as soon as acquired 975x the platium pue I have a problem with ide2. Configuration:
    2 hdd raptor raid 0 on sata 1 and 2
    2 hdd maxtor on sata Slavic 3 and 4
    1 plextor premium master on ide 1
    1 reader dvd slave on ide 1
    1 plextor px 716a master on ide 2 ide
    the 2 does not come seen in how much has had to disable from bios the jmicron why I could not more make the boot from the raid.
    How I can resolve this problem?

    1. Format a floppy disc in XP and make sure you use the "Create MS-DOS startup disc" - option:
    2. Erase all files on that disc BUT the following:
    COMMAND.COM
    IO.SYS (hidden system file)
    MSDOS.SYS (hidden system file)
    3. Now there should be enough room on the Disc for the Flash Tool and the new BIOS file (copy both onto the disc).
    The flash tool is included in every official BIOS download from the MSI Support Page for your mainboard:
    http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=746&kind=1
    4. Ususally it is a good idea to scan your disc for errors before you use it to flash a new BIOS.
    5. Restart computer, boot from disc and enter flash command followed by BIOS file name:
    AWFL865.EXE W7246IMS.716

  • 975X - Overclocking Processor Problem

    Hey guys, I'm having a problem with my motherboard when I overclock my processor.
    I have a MSI 975X Platinum Power-up Edition motherboard (7.6 BIOS), an E6600, 4GB of G.Skill RAM and Vista x64.  The problem is occurring because I recently updated the BIOS from 7.16 beta to 7.6 so my computer would recognize my 4GB of memory.  I used to be able to overclock my processor (345Mhz x 9 = ~3.1Ghz) just fine, but now when I go over about 334Mhz, the system will just hang. 
    You can find out more info on my problem here:  https://forum-en.msi.com/index.php?topic=113289.0
    (Sorry to the moderators!  My initial problem got fixed and I got carried away.  )
    Any help or advice would be greatly appreciated!

    Provide full details about your PC and put in your signature, example in mine.
    Have you checked the sticky topic yet? ---> https://forum-en.msi.com/index.php?topic=103878.0

  • A problem with threads

    I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
    Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
    My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
    Thank you in advance,
    Lefty

    This was one solution from the socket programming forum, have you tried this??
    public Thread MyThread extends Thread{
         boolean active = true;          
         public void run(){
              ss.setSoTimeout(90);               
              while (active){                   
                   try{                       
                        serverSocket = ss.accept();
                   catch (SocketTimeoutException ste){
                   // do nothing                   
         // interrupt thread           
         public void deactivate(){               
              active = false;
              // you gotta sleep for a time longer than the               
              // accept() timeout to make sure that timeout is finished.               
              try{
                   sleep(91);               
              }catch (InterruptedException ie){            
              interrupt();
    }

  • Problem with Threads and a static variable

    I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
    Code functionality:
    A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
    The problem as far I understand is:
    Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
    Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
    Thanks,
    B.D.
    Code:
    private static volatile boolean bChanged = false;
    private static Thread objMainProcess;
       protected static void Init(){
            objMainProcess = new Thread() {
                public void run() {
                    while( objMainProcess == Thread.currentThread() ) {
                       GetState();
            objMainProcess.setDaemon( true );
            objMainProcess.start();
        public static void initStatusTimer(){
            if(objTimer == null)
                 objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                    public void actionPerformed( java.awt.event.ActionEvent evt){
                              SetState();
        private static void SetState(){
            if( objMainProcess == null ) return;
            synchronized( objMainProcess ) {
                bChanged = true;
                try{
                    objMainProcess.notify();
                }catch( IllegalMonitorStateException e ) {}
        private static boolean GetState() {
            if( objMainProcess == null ) return false;
            synchronized( objMainProcess ) {
                if( bChanged) {
                    SendMessage();
                    bChanged = false;
                    return true;
                try {
                    objMainProcess.wait();
                }catch( InterruptedException e ) {}
                return false;
        }

    Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
    Again as you said, There is a reason I can't call sendMessage() inside setState().
    The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
    Thanks,
    B.D.

  • Problem with threads running javaw

    Hi,
    Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
    troy.

    troy,
    Try and post a minimum code sample of your app which
    does not work.
    When using javaw, make sure you redirect the standard
    error and standard output streams to file.
    Graeme.Hi Graeme,
    I dont understand what you mean by redirection to file? some of my code below.
    The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
    public class Server{
    ServerSocket aServerSocket;
    Socket dianosticsSocket;
    Socket nPortExpress;
    ClientListener aClientListener;
    LinkedList queue = new LinkedList();
    int port = 0;
    int clientPort = 0;
    String clientName = null;
    boolean serverAlive = true;
    * Server constructor generates a server
    * Socket and then starts a client threads.
    * @param aPort      socket port of local machine.
    public Server(int aPort, String aClientName, int aClientPort){
    port = aPort;
    clientName = aClientName;
    clientPort = aClientPort;
    try{
    // create a new thread
    aServerSocket = new ServerSocket(port) ;
    // connect to the nPortExpress
    aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
    // aClientListener.setDaemon(true);
    aClientListener.start();
    // start a dianostic port
    DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
    // System.out.println("Server is running on port " + port + "...");
    // System.out.println("Connect to nPort");
    catch(Exception e)
    // System.out.println("ERROR: Server port " + port + " not available");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
    serverAlive = false;
    System.exit(1);
    while(serverAlive&&aClientListener.hostSocket.isConnected()){
    try{
    // connect the client
    Socket aClient = aServerSocket.accept();
    //System.out.println("open client connection");
    //System.out.println("client local: "+ aClient.getLocalAddress().toString());
    // System.out.println("client localport: "+ aClient.getLocalPort());
    // System.out.println("client : "+ aClient.getInetAddress().toString());
    // System.out.println("client port: "+ aClient.getLocalPort());
    // make a new client thread
    ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
    // start thread
    clientThread.start();
    catch(Exception e)
    //System.out.println("ERROR: Client connection failure");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
    }// end while
    } // end constructor Server
    void serverExit(){
         JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
         System.exit(1);
    }// end class Server
    *** connect to another server
    public class ClientListener extends Thread{
    InetAddress hostName;
    int hostPort;
    Socket hostSocket;
    BufferedReader in;
    PrintWriter out;
    boolean loggedIn;
    LinkedList queue;      // reference to Server queue
    Server serverRef; // reference to main server
    * ClientListener connects to the host server.
    * @param aHostName is the name of the host eg server name or IP address.
    * @param aHostPort is a port number of the host.
    * @param aLoginName is the users login name.
    public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
    hostName = aHostName;
    hostPort = aHostPort;
    queue = aQueue;
    serverRef = aServer;      
    // connect to the server
    try{
    hostSocket = new Socket(hostName, hostPort);
    catch(IOException e){
    //System.out.println("ERROR: Connection Host Failed");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);     
    System.exit(0);
    } // end constructor ClientListener
    ** multi client connection server
    ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
    queue = aQueue;
    addToQueue(this);
    client = aSocket;
    clientRef = aClientListener;
    aDiagnostic = diagnostics;
    } // end constructor ClientWorker
    * run method is the main loop of the server program
    * in change of handle new client connection as well
    * as handle all messages and errors.
    public void run(){
    boolean alive = true;
    String aSubString = "";
    in = null;
    out = null;
    loginName = "";
    loggedIn = false;
    while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
    try{
    in = new BufferedReader(new InputStreamReader(client.getInputStream()));
    out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
    if(aDiagnostic){
    out.println("WELCOME to diagnostics");
    broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
    out.flush();
    else {       
    out.println("WELCOME to Troy's Server");
    broadCastDia("Connect : client "+client.getInetAddress().toString());
         out.flush();
    String line;
    while(((line = in.readLine())!= null)){
    StringTokenizer aStringToken = new StringTokenizer(line, " ");
    if(!aDiagnostic){
    broadCastDia(line);
    clientRef.sendMessage(line); // send mesage out to netExpress
    out.println(line);
    out.flush();
    else{
    if(line.equals("GETIPS"))
    getIPs();
    else{
    clientRef.sendMessage(line); // send mesage out to netExpress
    out.println(line);
    out.flush();
    } // end while
    catch(Exception e){
    // System.out.println("ERROR:Client Connection reset");
                             JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);     
    try{
    if(aDiagnostic){
    broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
    out.flush();
    else {       
    broadCastDia("Disconnect : client "+client.getInetAddress().toString());
         out.flush();
    // close the buffers and connection;
    in.close();
    out.close();
    client.close();
    // System.out.println("out");
    // remove from list
    removeThreadQueue(this);
    alive = false;
    catch(Exception e){
    // System.out.println("ERROR: Client Connection reset failure");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);     
    }// end while
    } // end method run
    * method run - Generates io stream for communicating with the server and
    * starts the client gui. Run also parses the input commands from the server.
    public void run(){
    boolean alive = true;
    try{
    // begin to life the gui
    // aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
    // aGuiClient.show();
    in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
    out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
    while (alive && hostSocket.isConnected()){
    String line;
    while(((line = in.readLine())!= null)){
    System.out.println(line);
    broadCast(line);
    } // end while
    } // end while
    catch(Exception e){
    //     System.out.println("ERRORa Connection to host reset");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
    try{
    hostSocket.close();
         }catch(Exception a){
         JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
    alive = false;
    System.exit(1);
    } // end method run

  • Problem with threads and camera.

    Hi everybody!
    I've a problem with taking snapshot.
    I would like to display a loading screen after it take snapshot ( sometimes i
    have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
    I was trying to use threads but i didn't succeed.
    I made this code:
    display.setCurrent(perform);               
            new Thread(new Runnable(){
                public void run() {               
                    while((!performing.isShown()) && (backgroundCamera.isShown())){
                        Thread.yield();
                    notifyAll();
            }).start();
            new Thread(new Runnable(){
                public void run() {
                    try {
                        this.wait();                   
                    } catch(Exception e) {
                        exceptionHandler(e);
                    photo = camera.snapshot();                               
                    display.setCurrent(displayPhoto);
            }).start();This code is sometimes showing performing screen but sometimes no.
    I don't know why. In my opinion performing.isShown() method isn't working correctly.
    Does anyone have some idea how to use threads here?

    Hi,
    I've finally managed to work this fine.
    The code:
           Object o = new Object();
           display.setCurrent(perform);               
            new Thread(new Runnable(){
                public void run() {               
                    while(!performing.isShown()){
                        Thread.yield();
                   synchronized(o) {
                      o.notify();
            }).start();
            new Thread(new Runnable(){
                public void run() {
                    try {
                        synchronized(o) {
                           o.wait(1);
                    } catch(Exception e) {
                        exceptionHandler(e);
                    photo = camera.snapshot();                               
                    display.setCurrent(displayPhoto);
            }).start();

  • Problem with threads hanging

    We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
    We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
    A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
    =============================================================================================
    "ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
    at java.lang.String.substring(String.java:1446)
    at java.lang.String.substring(String.java:1411)
    at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    =============================================================================================
    String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
    We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
    =============================================================================================
    ----------------- lwp# 44 / thread# 44 --------------------
    ff31f364 lwp_mutex_lock (e3d70)
    fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
    fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
    fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
    0) + 78
    fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
    fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
    fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
    fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
    fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
    fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
    fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
    fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
    fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
    fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
    fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
    fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
    fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
    fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
    fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
    fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
    fee6575c _start   (5941d0, fa1a1600, 0, 0, 0, 0) + 134
    ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
    =============================================================================================
    Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
    From the thread dump:
    "VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
    From the first pstack:
    =============================================================================================
    ----------------- lwp# 2 / thread# 2 --------------------
    fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
    fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
    fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
    fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
    fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
    feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
    feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
    fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
    ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
    =============================================================================================
    Second pstack
    =============================================================================================
    ----------------- lwp# 2 / thread# 2 --------------------
    fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
    fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
    fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
    fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
    fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
    feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
    feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
    fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
    ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
    =============================================================================================
    Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?

    Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there.  Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this. 
    We're using the following memory options:
    -ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
    -verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
    Thanks!
    --Andy                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Problem with threads and ProgressMonitor

    Dear Friends:
    I have a little problem with a thread and a ProgressMonitor. I have a long time process that runs in a thread (the thread is in an separate class). The thread has a ProgressMonitor that works fine and shows the tasks progress.
    But I need deactivate the main class(the main class is the user interface) until the thread ends.
    I use something like this:
    LongTask myTask=new LongTask();
    myTask.start();
    myTask.join();
    Now, the main class waits for the task to end, but the progress monitor don`t works fine: it shows only the dialog but not the progress bar.
    What's wrong?

    Is the dialog a modal dialog? This can block other UI updates.
    In general, you should make sure that it isn't modal, and that your workThread has a fairly low priority so that the UI can do its updating

  • Problem with threads and/or memory

    I'm developing an application where there are 3 threads. One of them sends a request to the other, and if the 2nd can't answer it, it sends it to the 3rd (similar to CPU -> CACHE -> MEMORY). When i run the program with 1000-10.000 requests, no problem occurs. When i run it with 300.000-1.000.000 requests, it sometimes hangs. Is this a problem with the garbage collector, or should it be related to the threads mecanism.
    (note: eache thread is in execution using a finite state machine)

    i had been running the program inside Netbeans.
    Running the jar using the command line outside
    Netbeans i have no more problems... Does Netbeans use
    it's own JVM?Depends how you set it up, but look under the options. There are settings for the compiler and jvm that it uses.

Maybe you are looking for