MSI GTX 970 - Slows down after a period, only PC reboot fixes

I'm having an issue with my new MSI GTX 970 4GB Gaming card.
Playing the Witcher 3 from a fresh boot up using optimised nvidia settings and I get 60fps easily. This remains the case for roughly 20-30 minutes. At which time, my frame rate will drop to ...

Aha, oki. I've noted flobelix to update his archive file to correct it.
QuoteGrabbed version 4.17 from TPU and that worked fine and dandy.
Yeah, i also link people to it directly, general ATI flash guide that i use:
flash guide:
QuoteDecom...

Similar Messages

  • MSI GTX 970 SLI crashing after returning to idle when exiting a game

    Hello,
    I'm writing this after a long process find out what was causing my problem.
    I have no problem running a game, my issue is when I exit and the system enters in idle.
    I don't know if it's drivers problem, a faulty card or any other issue.
     I have a core i7 3930k
    gskill ripjaws 2133mhz 16 gb ram
    gigabyte x78 ud5 motherboard.
    due to case space one of the graphics card is in a pcie x16 slot and the other is in a x8 pcie slot.
    I've always found a solution when a problem appears in my computer. But this time It's anoying the hell out of me.
    Thank you.

    Quote from: Nichrome on 03-November-14, 00:59:19
    Also this part left: >>Posting Guide<<
    Quote from: xmad on 19-January-04, 01:35:53
    Helping to troubleshoot a system from long distance is a challenge. To help us, help you, please make sure to provide as much information as possible about both the problem at hand, what you have already attempted to fix the problem and about your system in general.

  • High CPU using process slowed down after a period of time

    Hi,
    I am running a Finite element commercial solver, our tipical installations are with windows server 2008 but now we were force to move to windows server 2012.
    When we launch the solver, which may be working with up to 20 cores, the CPU usage remains consistent for about 40 minute/1 hour then drops to the usage of only one core without having completed the process, which complete several hours later.
    We already tried putting the power management at High performance, but didn't solve.
    Are there any suggestion regarding where to look at?
    Thanks 
    Raffaello

    Hi,
    First, please make sure your hardware support windows server 2012. I’m not sure what “Finite element commercial solver” is. So I just treat it as a kind of software. Is there
    any compatibility with the software with the new OS?
    Process Monitor may help address the issue.
    http://technet.microsoft.com/en-us/sysinternals/bb896653
    Hope this helps.

  • Msi gtx 970 gaming 4gb lose display and then computer reboots when EXITING games

    When the graphics card is no longer under stress the display will lose signal and usually the computer reboots seconds later. During use, the card performs perfectly. I have a second computer so I have already tried the card with a different motherboard and power supply, with the same problem. There isn't an error message but checking the event log it states a sudden and unexpected loss of power had occurred. My power supplies are both new and gold rated. My drivers are current and the bios is the latest released (the one with the patch for the fans). I'm at a loss to explain the problem and will RMA as a last resort. Any ideas guys? Thanks

    Quote from: JLio01 on 19-December-14, 09:35:32
    Use Afterburner and check "Force Constant Voltage" in their Settings. I think what causes these are the power saving sort of designs for both the mobo and vga, tbh, which makes the voltage more unstable. I think check this would help the problem a bit. Maybe you guys can try.
    I figured that it was an issue with hardware stepping down  to save power and I've forced voltage to remain constant but the crash still happens unfortunately.

  • Msi gtx 970 Fans Randomly Turning On When Idling???

    So basically I have had my msi gtx 970 for a couple weeks and the fans seem to behave as normal? Now once when I was idling I noticed the fans spin up and immediately spin down straight away. So basically now every 30 seconds the fans will spin up and spin straight back down which is weird. The temps are fine and I have checked this using MSi Afterburner. The fans I'm pretty sure are meant to stay off under 65 which it is so why are the fans spinning up. I don't seem to notice it noise wise but I don't know what it is happening. When I check the Fan % in Msi After Burner it doesn't log the fan ramping up but the 'fan tachometer, RPM' section shows it going up and back down, I will link a picture of this. I will link you the youtube video which I highly reccomend watching for a better idea of what's happening. I show you it spin up once and back down then a waiting period and then it doing it again.
    YouTube Video:
    Msi afterburner, Fan tachometer section: http://i.imgur.com/gchIHhF.png

    Quote from: rwcordell on 05-November-14, 04:05:25
    I may have found a problem with MSI's fan settings on these cards.
    Is this the problem? I don't know. But it does not seem to be set correctly IMO.
    As you can see below the fans with the OEM bios are never actually set to 0 rpm. When they are off they are actually being told to spin at 1% power at 23 rpm.
    I have changed mine.
    The fans no longer randomly spin with the new drivers. And I have not had any more problems with one fan not spinning up ( although its too early to declare victory on that problem ).
    My fans now start up at 50c and even when overclocked to 1503MHZ I have not gone over 65c at 68% fan speed.
    Went ahead and copied your settings and everything seems to be working as it should  now. Thanks
    **EDIT**
    Just tested it by getting gpu up to 50c and it seems to work. After it drops below 50 it takes a bit for the red fan to spin back down (stayed around 44% for a good 3-5 mins). After the red fan dropped to 0% the black fan slowly dropped down to 29% and that's where it is sitting right now. I think this is per design though since I remember my gpu doing this even on .16. The cooldown process or something I guess.
    And at the end of this post black fan is back down to 0%. Good call on the problem looks like it's fixed .

  • Can't OC my MSI GTX 970 GAMING

    I had MSI GTX 970 GAMING which OC-ed very well (1540 Mhz boost) but had to return it because of loud coil whine. I bought second MSI card which is silent but can't OC it even by +50 Mhz in Afterburner because it drops gpu clock to default value in Valley benchmark after couple of minutes of testing. Do you know what is the reason of that?

    Quote from: flobelix on 17-October-14, 15:48:18
    Everything has been said above. As the reboot issue is no issue if using working clockrates there is still no problem.
    You really don't see the issue with contributing to a thread about overclocking with the answer "Don't overclock and there isn't a problem"?
    Flobelix, I'm not asking for a refund here.
    I don't want a new card via RMA, and I'm not saying my card is bad in any way.
    If it works at the shipped clocks just fine, then it's clearly fine. That's all that's promised anyway.
    But I didn't come to a forum and post in this topic about overclocking to be shut down for talking about overclocking.
    I'm looking for discussion.
    I already said if someone felt my issue was sufficiently different than the OP I'd happily make a new thread.
    If that's not the case, then I think I'm well within the bounds of exactly what this thread is about.

  • B2 Error with new MSI GTX 970 :(

    Hi there team!
    Just registered to try and get help. I spent around 6 hours researching + trying all the suggestions throughout many different forums, but the B2 error still persists. I am currently running the following spec:
    Mobo - MSI Z68A-G43 (G3), with version 4.30 ( I flashed bios last night and still no help)
    CPU - Intel® Core™ i5-2500K Processor, 3.5GHz etc.etc.
    RAM - Corsair Vengeance 2x4gb at 1333MHz
    GPU - MSI GTX 970 GAMING Twin Frozr V 4GB GDDR5
    PSU - Cooler Master Silent Pro 700W
    I have tried:
    -Taking out the card and using the on-board graphics to flash the bios to later version, No help. (during this process, the B2 error does NOT show up)
    -Upgraded the card to latest nVidia drivers, even uninstalled and re-installed them. No help.
    -Upgraded all the drivers from MSI, i.e. chipset etc. through Live Update 6. No help.
    When the card is in, I cannot even access bios, it just gets stuck at B2 screen for like a minute, and then carries on with the boot process. I am able to play games etc. after the booting, but this error for sure should not be there when the PC boots up. I didn't have any issues with my old GTX 560 TI. I've read different forums saying that it might have something to do with the mobo thinking that something has to be connected to the on-board graphics; or that flashing BIOS helped a lot of users, but not me :(.
    I don't have a second PC to test the card on.
    Literally, I would try anything, please someone just help :(( This card is a beast and I wanna be able to properly use it and not having to worry about this error.
    Thank you very much guys, hope someone can help!

    Quote from: gabe_dimitrov on 08-February-15, 20:40:51
    Man thank you so much! It is finally working!!! Thank you!!!! ))) It is showing correct version in BIOS, does not show B2 error whatsoever, all done! )
    Thanks for your time! You can close thread, but it's very useful for anyone that has this issue!
    Wich version of BIOS do you have installed? Can you OC your processor with new BIOS?

  • MSI GTX 970 not being detected on first PCI-E 3.0 slot of MSI Gaming 5 motherboa

    Hi guys.
    So I recently got myself a new build and some of the components include a MSI GTX 970 Gaming 4G GPU and a MSI Gaming 5 mobo. When installing the GPU to the motherboard I found that for some reason nothing was being displayed on the screen. The screen wouldn't display a no signal message but it would stay black when I booted the PC up. However, when I plugged the GPU into the 2nd PCI-E 3.0 slot it would work and display on the screen. I read on a Tom's Hardware thread of someone with a similar problem and it was recommended to him to check his CPU for bent pins and he later confirmed that was the problem. I have tried the same, but as far as I can tell all of the pins were in their natural state and couldn't find any bent ones.
    But I also discovered something else which really started to confuse me... When I plug in my old GPU (a Gigabyte GTX 560 Ti) into the first PCI-E 3.0 slot, it would work normally?! Why would it work fine with my GTX 560 but not my GTX 970?? I have tried everything. Even stripping the pc down to the most basic parts on a wooden surface and tested everything but it's still the same problem. I have also made sure that the display setting in the BIOS is set to PEG, but it would still not display anything when the GTX 970 is in the first slot, but if I plug the HDMI cable directly into my motherboard, even with the GTX 970 installed on the first slot, it would display normally. Also, in my BIOS it doesn't even detect anything being in the first PCI-E 3.0 slot in the Board Explorer menu. But when I installed it in the 2nd PCI-E 3.0 slot the Board Explorer menu would recognize it, but would say it's running at x8 and not x16. Should I be worried about this?
    My full setup:
    MSI Gaming 5 Motherboard
    Intel i7 4790K
    MSI GTX 970 Gaming 4G
    Kingston HyperX 1333Mhz 8Gb (2x4Gb)
    Corsair RM 750 PSU
    Corsair H80i CPU cooler
    Any advice from you guys on what to do or what the problem could be would be greatly appreciated!

    remove power cord from the PSU and do >>Clear CMOS Guide<<
    also reseat the card into PCI-E slot 1 and make sure its fill very well into the slot
    Quote
    MSI Gaming 5 Motherboard
    full model is..?

  • Server slows down after a while

    Hi all,
    I've a problem with a linux machine which slows down after running for
    some days. It usually handles about 100 request per second and after a
    while it goes down to about 5 requests per second. I'm running WL6.1Sp1
    on Linux with JDK1.3.1 and "-hotspot -ms512m -mx512m". I'm wondering if
    this is related to some problem in my code or maybe rather is a database
    issue. I took a thread dump, and the server looks idle. Does anyone see
    something unusual in this dump? Does it indicate anything else than a
    nearly totally idle server?
    Thanks for your input!
    Daniel
    Full thread dump:
    "process forker" daemon prio=1 tid=0x82fe460 nid=0x5bf6 waiting on
    monitor [0xb75ff000..0xb75ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.UNIXProcessForker.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "process reaper" daemon prio=1 tid=0x82fdde0 nid=0x5bf5 runnable
    [0xb77ff000..0xb77ff8c0]
         at java.lang.UNIXProcessReaper.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "HighPriority TimeEventGenerator" daemon prio=1 tid=0x8148b98 nid=0x5ad6
    waiting on monitor [0xb79ff000..0xb79ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "ListenThread" prio=1 tid=0x679c3c10 nid=0x5ad5 runnable
    [0xb7bff000..0xb7bff8c0]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
         at java.net.ServerSocket.implAccept(ServerSocket.java:243)
         at java.net.ServerSocket.accept(ServerSocket.java:222)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "Thread-2" prio=1 tid=0x83a3b68 nid=0x5ad3 waiting on monitor
    [0xb7dff000..0xb7dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.util.TimerThread.mainLoop(Timer.java:432)
         at java.util.TimerThread.run(Timer.java:385)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
    tid=0x67680b10 nid=0x5ad2 waiting on monitor [0xb7fff000..0xb7fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x676809e8 nid=0x5ad1 waiting on monitor [0xb81ff000..0xb81ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a8b358 nid=0x5ad0 waiting on monitor [0xb83ff000..0xb83ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a873b0 nid=0x5acf waiting on monitor [0xb85ff000..0xb85ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65af9d88 nid=0x5ace waiting on monitor [0xb87ff000..0xb87ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6764bfb8 nid=0x5acc waiting on monitor [0xb89ff000..0xb89ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67951208 nid=0x5acb waiting on monitor [0xb8bff000..0xb8bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67667450 nid=0x5aca waiting on monitor [0xb8dff000..0xb8dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x679819b0 nid=0x5ac9 waiting on monitor [0xb8fff000..0xb8fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6799ade8 nid=0x5ac8 waiting on monitor [0xb91ff000..0xb91ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6765d0b8 nid=0x5ac7 waiting on monitor [0xb93ff000..0xb93ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67903838 nid=0x5ac6 waiting on monitor [0xb95ff000..0xb95ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676688a8 nid=0x5ac5 waiting on monitor [0xb97ff000..0xb97ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676976e8 nid=0x5ac4 waiting on monitor [0xb99ff000..0xb99ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada048 nid=0x5ac3 waiting on monitor [0xb9bff000..0xb9bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6766e550 nid=0x5ac2 waiting on monitor [0xb9dff000..0xb9dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67630ea8 nid=0x5ac1 waiting on monitor [0xb9fff000..0xb9fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65acf508 nid=0x5ac0 waiting on monitor [0xba1ff000..0xba1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada1e8 nid=0x5abf waiting on monitor [0xba3ff000..0xba3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676ed050 nid=0x5abe waiting on monitor [0xba5ff000..0xba5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6762af98 nid=0x5abd waiting on monitor
    [0xba7ff000..0xba7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x676a0838 nid=0x5abc waiting on monitor
    [0xba9ff000..0xba9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6765c0d8 nid=0x5abb waiting on monitor
    [0xbabff000..0xbabff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab6bf8 nid=0x5aba waiting on monitor
    [0xbadff000..0xbadff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676865f0 nid=0x5ab9 waiting on monitor
    [0xbafff000..0xbafff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676dfcb0 nid=0x5ab8 waiting on monitor
    [0xbb1ff000..0xbb1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676120f0 nid=0x5ab7 waiting on monitor
    [0xbb3ff000..0xbb3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67611fb0 nid=0x5ab6 waiting on monitor
    [0xbb5ff000..0xbb5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67699720 nid=0x5ab5 waiting on monitor
    [0xbb7ff000..0xbb7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67926328 nid=0x5ab4 waiting on monitor
    [0xbb9ff000..0xbb9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x6767e820 nid=0x5ab3 waiting on monitor
    [0xbbbff000..0xbbbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab61a0 nid=0x5ab2 waiting on monitor
    [0xbbdff000..0xbbdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676cff58 nid=0x5ab1 waiting on monitor
    [0xbbfff000..0xbbfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765ff60 nid=0x5ab0 waiting on monitor
    [0xbc1ff000..0xbc1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765f958 nid=0x5aaf waiting on monitor
    [0xbc3ff000..0xbc3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=1 tid=0x676f3818 nid=0x5aae waiting on
    monitor [0xbc5ff000..0xbc5ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "TimeEventGenerator" daemon prio=1 tid=0x676ffae8 nid=0x5aad waiting on
    monitor [0xbc7ff000..0xbc7ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=1 tid=0x67646dd8 nid=0x5aac waiting on
    monitor [0xbc9ff000..0xbc9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.ja
    va:57)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=1 tid=0x6767ff00
    nid=0x5aab runnable [0xbcbff000..0xbcbff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=1 tid=0x67929c90
    nid=0x5aaa waiting on monitor [0xbcdff000..0xbcdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=1 tid=0x65aa0b58
    nid=0x5aa9 waiting on monitor [0xbcfff000..0xbcfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=1 tid=0x65a9ed80
    nid=0x5aa8 waiting on monitor [0xbd1ff000..0xbd1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=1 tid=0x679036d0
    nid=0x5aa7 runnable [0xbd3ff000..0xbd3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=1 tid=0x6767fdc0
    nid=0x5aa6 waiting on monitor [0xbd5ff000..0xbd5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=1 tid=0x676680f8
    nid=0x5aa5 waiting on monitor [0xbd7ff000..0xbd7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=1 tid=0x676123e0
    nid=0x5aa4 waiting on monitor [0xbd9ff000..0xbd9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x6766f658
    nid=0x5aa3 waiting on monitor [0xbdbff000..0xbdbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x67647858
    nid=0x5aa2 waiting on monitor [0xbddff000..0xbddff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x67665970
    nid=0x5aa1 waiting on monitor [0xbdfff000..0xbdfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x676426d8
    nid=0x5aa0 runnable [0xbe1ff000..0xbe1ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x65afac38
    nid=0x5a9f runnable [0xbe3ff000..0xbe3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x65aa1088
    nid=0x5a9e waiting on monitor [0xbe5ff000..0xbe5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x6765ef78
    nid=0x5a9d waiting on monitor [0xbe7ff000..0xbe7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=1 tid=0x6764ced0 nid=0x5a9c waiting on monitor
    [0xbe9ff000..0xbe9ff8c0]
         at java.lang.Thread.sleep(Native Method)
         at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionMa
    nagerImpl.java:1546)
         at java.lang.Thread.run(Thread.java:484)
    "Signal Dispatcher" daemon prio=1 tid=0x808d4b0 nid=0x5a9a waiting on
    monitor [0..0]
    "Finalizer" daemon prio=1 tid=0x8086ca0 nid=0x5a97 waiting on monitor
    [0xbf3ff000..0xbf3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
         at
    java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
    "Reference Handler" daemon prio=1 tid=0x80851f8 nid=0x5a96 waiting on
    monitor [0xbf5ff000..0xbf5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
    "main" prio=1 tid=0x804e750 nid=0x5a7c waiting on monitor
    [0xbfffd000..0xbfffd220]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:596)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
         at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=1 tid=0x80821a8 nid=0x5a95 runnable
    "VM Periodic Task Thread" prio=1 tid=0x808c220 nid=0x5a98 waiting on
    monitor
    "Suspend Checker Thread" prio=1 tid=0x808cb68 nid=0x5a99 runnable

    There are several threads like the one below. I would think that they are the
    problem. But I don't know what they are doing - doesn't look like any application
    code.
    Mike
    "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x65afac38 nid=0x5a9f
    runnable [0xbe3ff000..0xbe3ff8c0] at java.net.SocketInputStream.socketRead(Native
    Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
    ) at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24) at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ============================================================
    Daniel Hoppe <[email protected]> wrote:
    Hi all,
    I've a problem with a linux machine which slows down after running for
    some days. It usually handles about 100 request per second and after
    a
    while it goes down to about 5 requests per second. I'm running WL6.1Sp1
    on Linux with JDK1.3.1 and "-hotspot -ms512m -mx512m". I'm wondering
    if
    this is related to some problem in my code or maybe rather is a database
    issue. I took a thread dump, and the server looks idle. Does anyone see
    something unusual in this dump? Does it indicate anything else than a
    nearly totally idle server?
    Thanks for your input!
    Daniel
    Full thread dump:
    "process forker" daemon prio=1 tid=0x82fe460 nid=0x5bf6 waiting on
    monitor [0xb75ff000..0xb75ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.UNIXProcessForker.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "process reaper" daemon prio=1 tid=0x82fdde0 nid=0x5bf5 runnable
    [0xb77ff000..0xb77ff8c0]
         at java.lang.UNIXProcessReaper.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "HighPriority TimeEventGenerator" daemon prio=1 tid=0x8148b98 nid=0x5ad6
    waiting on monitor [0xb79ff000..0xb79ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "ListenThread" prio=1 tid=0x679c3c10 nid=0x5ad5 runnable
    [0xb7bff000..0xb7bff8c0]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
         at java.net.ServerSocket.implAccept(ServerSocket.java:243)
         at java.net.ServerSocket.accept(ServerSocket.java:222)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "Thread-2" prio=1 tid=0x83a3b68 nid=0x5ad3 waiting on monitor
    [0xb7dff000..0xb7dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.util.TimerThread.mainLoop(Timer.java:432)
         at java.util.TimerThread.run(Timer.java:385)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
    tid=0x67680b10 nid=0x5ad2 waiting on monitor [0xb7fff000..0xb7fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x676809e8 nid=0x5ad1 waiting on monitor [0xb81ff000..0xb81ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a8b358 nid=0x5ad0 waiting on monitor [0xb83ff000..0xb83ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a873b0 nid=0x5acf waiting on monitor [0xb85ff000..0xb85ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65af9d88 nid=0x5ace waiting on monitor [0xb87ff000..0xb87ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6764bfb8 nid=0x5acc waiting on monitor [0xb89ff000..0xb89ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67951208 nid=0x5acb waiting on monitor [0xb8bff000..0xb8bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67667450 nid=0x5aca waiting on monitor [0xb8dff000..0xb8dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x679819b0 nid=0x5ac9 waiting on monitor [0xb8fff000..0xb8fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6799ade8 nid=0x5ac8 waiting on monitor [0xb91ff000..0xb91ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6765d0b8 nid=0x5ac7 waiting on monitor [0xb93ff000..0xb93ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67903838 nid=0x5ac6 waiting on monitor [0xb95ff000..0xb95ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676688a8 nid=0x5ac5 waiting on monitor [0xb97ff000..0xb97ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676976e8 nid=0x5ac4 waiting on monitor [0xb99ff000..0xb99ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada048 nid=0x5ac3 waiting on monitor [0xb9bff000..0xb9bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6766e550 nid=0x5ac2 waiting on monitor [0xb9dff000..0xb9dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67630ea8 nid=0x5ac1 waiting on monitor [0xb9fff000..0xb9fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65acf508 nid=0x5ac0 waiting on monitor [0xba1ff000..0xba1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada1e8 nid=0x5abf waiting on monitor [0xba3ff000..0xba3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676ed050 nid=0x5abe waiting on monitor [0xba5ff000..0xba5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6762af98 nid=0x5abd waiting on monitor
    [0xba7ff000..0xba7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x676a0838 nid=0x5abc waiting on monitor
    [0xba9ff000..0xba9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6765c0d8 nid=0x5abb waiting on monitor
    [0xbabff000..0xbabff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab6bf8 nid=0x5aba waiting on monitor
    [0xbadff000..0xbadff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676865f0 nid=0x5ab9 waiting on monitor
    [0xbafff000..0xbafff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676dfcb0 nid=0x5ab8 waiting on monitor
    [0xbb1ff000..0xbb1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676120f0 nid=0x5ab7 waiting on monitor
    [0xbb3ff000..0xbb3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67611fb0 nid=0x5ab6 waiting on monitor
    [0xbb5ff000..0xbb5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67699720 nid=0x5ab5 waiting on monitor
    [0xbb7ff000..0xbb7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67926328 nid=0x5ab4 waiting on monitor
    [0xbb9ff000..0xbb9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x6767e820 nid=0x5ab3 waiting on monitor
    [0xbbbff000..0xbbbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab61a0 nid=0x5ab2 waiting on monitor
    [0xbbdff000..0xbbdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676cff58 nid=0x5ab1 waiting on monitor
    [0xbbfff000..0xbbfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765ff60 nid=0x5ab0 waiting on monitor
    [0xbc1ff000..0xbc1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765f958 nid=0x5aaf waiting on monitor
    [0xbc3ff000..0xbc3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=1 tid=0x676f3818 nid=0x5aae waiting
    on
    monitor [0xbc5ff000..0xbc5ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "TimeEventGenerator" daemon prio=1 tid=0x676ffae8 nid=0x5aad waiting
    on
    monitor [0xbc7ff000..0xbc7ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=1 tid=0x67646dd8 nid=0x5aac waiting
    on
    monitor [0xbc9ff000..0xbc9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.ja
    va:57)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=1 tid=0x6767ff00
    nid=0x5aab runnable [0xbcbff000..0xbcbff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=1 tid=0x67929c90
    nid=0x5aaa waiting on monitor [0xbcdff000..0xbcdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=1 tid=0x65aa0b58
    nid=0x5aa9 waiting on monitor [0xbcfff000..0xbcfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=1 tid=0x65a9ed80
    nid=0x5aa8 waiting on monitor [0xbd1ff000..0xbd1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=1 tid=0x679036d0
    nid=0x5aa7 runnable [0xbd3ff000..0xbd3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=1 tid=0x6767fdc0
    nid=0x5aa6 waiting on monitor [0xbd5ff000..0xbd5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=1 tid=0x676680f8
    nid=0x5aa5 waiting on monitor [0xbd7ff000..0xbd7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=1 tid=0x676123e0
    nid=0x5aa4 waiting on monitor [0xbd9ff000..0xbd9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x6766f658
    nid=0x5aa3 waiting on monitor [0xbdbff000..0xbdbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x67647858
    nid=0x5aa2 waiting on monitor [0xbddff000..0xbddff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x67665970
    nid=0x5aa1 waiting on monitor [0xbdfff000..0xbdfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x676426d8
    nid=0x5aa0 runnable [0xbe1ff000..0xbe1ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x65afac38
    nid=0x5a9f runnable [0xbe3ff000..0xbe3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x65aa1088
    nid=0x5a9e waiting on monitor [0xbe5ff000..0xbe5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x6765ef78
    nid=0x5a9d waiting on monitor [0xbe7ff000..0xbe7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=1 tid=0x6764ced0 nid=0x5a9c waiting on monitor
    [0xbe9ff000..0xbe9ff8c0]
         at java.lang.Thread.sleep(Native Method)
         at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionMa
    nagerImpl.java:1546)
         at java.lang.Thread.run(Thread.java:484)
    "Signal Dispatcher" daemon prio=1 tid=0x808d4b0 nid=0x5a9a waiting on
    monitor [0..0]
    "Finalizer" daemon prio=1 tid=0x8086ca0 nid=0x5a97 waiting on monitor
    [0xbf3ff000..0xbf3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
         at
    java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
    "Reference Handler" daemon prio=1 tid=0x80851f8 nid=0x5a96 waiting on
    monitor [0xbf5ff000..0xbf5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
    "main" prio=1 tid=0x804e750 nid=0x5a7c waiting on monitor
    [0xbfffd000..0xbfffd220]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:596)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
         at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=1 tid=0x80821a8 nid=0x5a95 runnable
    "VM Periodic Task Thread" prio=1 tid=0x808c220 nid=0x5a98 waiting on
    monitor
    "Suspend Checker Thread" prio=1 tid=0x808cb68 nid=0x5a99 runnable

  • MSI GTX 970 Gaming 4G Issues & BIOS Update

     bios.zip (136.34 kB - downloaded 37 times.)
    Hello,
    ever since I bought my GTX 970 I've had about 5 BSOD's while playing CS:GO and GTA:V. I am not sure whether it's a GPU issue or not, but I never had that issue before (at least with CS:GO).
    Tech specs:
    MB: z87-pro
    CPU: i7-4770K
    GPU: MSI GTX 970 Gaming 4G
    OS: Win7 x64 SP1
    latest OS updates
    latest nVidia drivers
    I've been wondering if there's a BIOS update for my GPU? I also tried just today to download MSI Live Update 6 but after executing the installer it displays "This application does not support this platform."
    I've attached my GPU Bios.
    Thanks in advance!

    Quote from: Nichrome on 26-April-15, 03:21:48
    Hi
    With LiveUpdate, don't worry. Many users got issue with it, I believe MSI is aware of this already.
    Is your motherboard running latest BIOS?
    Is it known to work fine with other graphics card??
    Do you have any OC on your CPU/RAM? (RAM OC=more than 1600MHz). Remove and try again.
    What did the BSOD say? Error code?
    Heya, thanks for the reply.
    That's good to know for Live Update, just wanted to let you know. Before my GTX970 I was using an Asus GTS 450 (I know, lame) and used integrated graphics a couple of times but never had BSOD's during games with either of those. I didn't take a note of the BSOD error code, can I find a log somewhere on my system to upload it?
    OC-wise everything is running on stock clock, BIOS is also latest version (2103, according to Asus).

  • Msi gtx 970 coil whine and fsb up to 100

    is this considered normal since the coilwhine occurs when i play medium gpu demanding games
    i dont think fsb 100 should be considered normal?

    CoD:AW is only 'medium demanding' so long as you don't have lots of AA or supersampling enabled. As soon as i ramp up the AA or turn on supersampling, GPU will easily hit 100% and get really hot.
    Also, FB is frame buffer usage, so VRAM/memory usage. CoD deliberately uses 100% of VRAM available to it at any given time - i forget the reasons but all the PC reviews mention this and its beneficial in some way - i suspect its all the pre-loading of textures it does to reduce hitching as you go from area to area.
    So 100% FB is normal, and 100% GPU usage in general may also be, depending on settings.
    As for coil whine, most MSTI GTX 970s seem to suffer with it. My Asus GTX 970 (got it after RMAing my msi one) has none, thankfully.

  • System Slow-Down After Printing

    I recently installed Mountain Lion. Over the last couple of weeks I have noticed a significant operating system (10.8.2) slow down after printing with my Epson R3000 printer. This happens after every printing session. When I say slow-down I mean significant delays and dreading "beachballs" when opening applications, selecting menu items or anything else I should choose to do. I'm left with re-starting the computer to get going normally again.After re-atarting I have gone to "verify permissions" and I get approx "5" pages of permission errors, all associated with the printer library in some fashion or another. I then repair all those permissions and re-start my MacPro. The operating system then works as normal and I can use the computer with no problems (until I start printing again). I mainly use the computer for photo editing with Adobe Photoshop CS6, Adobe Lightroom 4 and Aperture 3.2.
    I did not have this problem before upgrading to Mountain Lion (and then to 10.8.2). I did not get "significant" permission errors before upgrading. Since all printer drivers for this printer are handled now by Apple via the "new" Software Update process I can't even re-download the Epson printer driver and start over. I'm completely at a loss as to what, associated with the printer function, is causing these "significant" permission errors and subsequent operating system slow down. My printer is almost brand new and was working flawlessly before Mountain Lion. Let me be clear though, I can print fine. My problem is the system slow down after using the print function which I am only guessing has something to do with the "5" pages of permission errors after printting photos (with CS6/Lightroom/Aperture).
    Incidently, I am not in any way a computer expert. Verifying and repairing permissions is about all I know how to do that's why I need help. I also just thought I would try the forums first before going to technical support to see what people thought about this.
    Again, I repair the permission errors, re-start my system and all is fine. Any further suggestions would be deeply appreciated.

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • My macbook slows down after using external HDD

    When I use an external drive via usb, my computer really slows down giving me no choice except reboot.
    I watched memory usage with activity monitor. Free memory decreases  by time and inactive memory increases with the same amount and others  don't change much. If I continue using -esp. reading-, free memory comes  below to 100MB and then increases a bit -I think it starts paging  =other applications' memories= to system disk-, then continues to  decrease. Closing the application -that use the external- do not relese  memory from inactive to free but ejecting the external does. After  unplugging and trying to use the other applications, I face very  sluggish performance so that rebooting becomes a better-fast choice.  Both NTFS and FAT partitions produce the same result and I don't have  any other partition.
    If I try to re-read the same file after the external drive stops  spinning (sleeps), it does not start spinning but trying to read another  file makes it start spining. This makes me think about some -overdone-  caching problem, but don't know what causes it and how to turn it off  (Tuxero's caching is already disabled in the preferences, although I  think it is only for writing only).
    I made some research and found nothing specific; they tell to  reinstall the os or format the drive -to HFS+ -. What is causing this?
    Note: All of my drives are in Spotlight's exclusion (privacy) list and using another usb slot did not change a thing.
    My EtreCheck is:
    EtreCheck version: 1.9.11 (43) - report generated June 15, 2014
    Hardware Information:
        MacBook Pro (13-inch, Mid 2009)
        MacBook Pro - model: MacBookPro5,5
        1 2.26 GHz Intel Core 2 Duo CPU: 2 cores
        4 GB RAM
    Video Information:
        NVIDIA GeForce 9400M - VRAM: 256 MB
    System Software:
        OS X 10.8.3 (12D78) - Uptime: 0 days 1:4:54
    Disk Information:
        Hitachi HTS5450 disk0 : (160.04 GB)
            disk0s1 (disk0s1) <not mounted>: 209.7 MB
            Macintosh HD (disk0s2) / [Startup]: 94.62 GB (48.81 GB free)
            Recovery HD (disk0s3) <not mounted>: 650 MB
            BOOTCAMP (disk0s4) /Volumes/BOOTCAMP: 64.57 GB (44.49 GB free)
        HL-DT-ST DVDRW  GS23N 
    USB Information:
        Apple Inc. Built-in iSight
        JMicron Storage 500.11 GB
            BKPFAT (disk1s1) /Volumes/BKPFAT: 443.2 GB (25.08 GB free)
            BKPNTFS (disk1s2) <not mounted>: 56.9 GB
        Apple Internal Memory Card Reader
        Apple Inc. Apple Internal Keyboard / Trackpad
        Apple Computer, Inc. IR Receiver
        Apple Inc. BRCM2046 Hub
            Apple Inc. Bluetooth USB Host Controller
    Configuration files:
        /etc/hosts - Count: 1
    Gatekeeper:
        Anywhere
    Startup Items:
        TuxeraNTFSUnmountHelper: Path: /Library/StartupItems/TuxeraNTFSUnmountHelper
    Launch Daemons:
        [loaded]    com.adobe.fpsaud.plist Support
        [loaded]    com.barebones.authd.plist Support
        [loaded]    com.barebones.textwrangler.plist Support
        [loaded]    com.google.keystone.daemon.plist Support
        [loaded]    com.oracle.java.Helper-Tool.plist Support
        [not loaded]    de.jinx.SmartSleepDaemon.plist Support
        [loaded]    org.macosforge.xquartz.privileged_startx.plist Support
    Launch Agents:
        [loaded]    com.google.keystone.agent.plist Support
        [loaded]    com.oracle.java.Java-Updater.plist Support
        [loaded]    org.macosforge.xquartz.startx.plist Support
    User Login Items:
        GrowlHelperApp
        Google Drive
        witchdaemon
        BetterTouchTool
    Internet Plug-ins:
        JavaAppletPlugin: Version: Java 8 Update 05 Check version
        FlashPlayer-10.6: Version: 12.0.0.38 - SDK 10.6 Support
        QuickTime Plugin: Version: 7.7.1
        Flash Player: Version: 12.0.0.38 - SDK 10.6 Outdated! Update
        o1dbrowserplugin: Version: 5.4.2.18903 Support
        googletalkbrowserplugin: Version: 5.4.2.18903 Support
        Silverlight: Version: 5.1.30317.0 - SDK 10.6 Support
        Unity Web Player: Version: UnityPlayer version 4.1.5f1 Support
        iPhotoPhotocast: Version: 7.0
    Safari Extensions:
        Bing Highlights: Version: 1.0.20
        ClickToFlash: Version: 2.5.1
    Audio Plug-ins:
        AirPlay: Version: 1.7 - SDK 10.8
        iSightAudio: Version: 7.7.1 - SDK 10.8
    iTunes Plug-ins:
        Quartz Composer Visualizer: Version: 1.4 - SDK 10.8
    3rd Party Preference Panes:
        Flash Player  Support
        FUSE for OS X (OSXFUSE)  Support
        GamePadCompanionPrefPanel  Support
        Growl  Support
        Java  Support
        MenuMeters  Support
        SmartSleep  Support
        Tuxera NTFS  Support
        Witch  Support
    Time Machine:
        Time Machine not configured!
    Top Processes by CPU:
            25% firefox
             4% activitymonitord
             4% WindowServer
             1% hidd
             1% BetterTouchTool
    Top Processes by Memory:
        254 MB  firefox
        111 MB  Google Chrome
        66 MB   Sublime Text
        61 MB   mds
        59 MB   Google Chrome Helper
    Virtual Memory Information:
        1.72 GB Free RAM
        1.21 GB Active RAM
        416 MB  Inactive RAM
        425 MB  Wired RAM
        378 MB  Page-ins
        0 B Page-outs

    Thread continues as an OSX discussion here, please do not reply this.

  • Slow down after installing Lion OS

    My Macbook pro later than 2009 model slowed down after installing the new OS Lion
    any suggestions to speed it up

    First suggestion ,there have been a number of identical user questions like yours, in the Lion Community. If you want to talk to other MacBook Pro owners, try the forum they have.
    http://www.apple.com/support/macbookpro
    What you do not need is some gizmo to "speed up" or clean caches etc.
    Maybe you need to make more room on your hard drive, or add more RAM.
    For now, hold down Command-R and run Disk Utility to check the health of your system drive (Lion Recovery Mode)
    http://www.apple.com/support/lion

  • Compleat system slow down after current updates

    Has anyone learned why we all seem to have a compleat system slow down after the current set of updates? Everything works, but is VERY slow to respond. Even iTunes 7.1.1 plays video choppy now. Audio track plays fine however. Odd.
    -Apple //GS

    First of all, try repairing your permissions with Applications> Utilities> Disk Utility. Select the hard drive you're running off of and then click the Repair Permissions button.
    If that doesn't work I'd do an archive and install:
    http://docs.info.apple.com/article.html?artnum=107120
    Then run the combo update(s) instead of the consecutive ones. That seems to be working for a lot of people, but it will probably take a while.

Maybe you are looking for