X58M Instability Issues

Hello and thank you in advance for any help
I have put together a new Windows 7 system with the following components
•   MSI x58M Mother board (vers 3.2 Bios)
•   I7 920
•   4 x 2gig Nanua NT5CB512T4AN-CG DDR3 1333
•   2 x WD 500 gig Sata harddrives in RAID 0
•   Chiefmax 650W Power supply
•   2 x MSI nVidia GeForce 9500GT video cards (not SLI used for 3 monitors)
•   Stock cooling fan
I have not over clocked this system and do not intend to.  Upon first attempt to install windows 7 the installation would stall.  I then installed Windows xp 64 bit and updated BIOS and chip set.  I was then able to successfully install windows 7 64 bit. Shortly after the system began random re-boots with blue screen events, seemingly associated to driver issues.  I have updated every driver possible and still blue screen events.  I have run memtest86 to confirm RAM is okay several times with each stick.  Everything in BIOS is set to default so the RAM is actually not running at 1333 but instead is running at 1066. Thinking this to be the problem I increased the memory ratio to 5 thus making the DRAM frequency 1333.  Upon saving changes and re-booting windows begins to load gets to the black screen with swirling colors with “Windows is starting up” and hangs or re-boots.  I then thought I would manually adjust the DRAM Frequency to 9-9-9-24 with the same results.  I also increased DRAM Voltage to 1.65 and also the RAM manufacturers setting of 1.5 with the same results.  At this point the only way I can get windows to boot successfully is to set base clock to 133 and leave everything else on auto, or I can get it to successfully boot buy changing the Base clock to 166Mhz and leaving everything else on auto but the system remains unstable and re-boots after 10 minutes on Prime95 stress test.  I have tried using one video card.  I have tried running the DDR in Dual Channel. I am about to lose my mind please any advice would be greatly appreciated.

I have this board and want to run 3 monitors. Are you saying you used 2 Geforce cards without SLI and it worked for 3 monitors?
Quote from: threepankeyman on 20-January-10, 05:19:37
Hello and thank you in advance for any help
I have put together a new Windows 7 system with the following components
•   MSI x58M Mother board (vers 3.2 Bios)
•   I7 920
•   4 x 2gig Nanua NT5CB512T4AN-CG DDR3 1333
•   2 x WD 500 gig Sata harddrives in RAID 0
•   Chiefmax 650W Power supply
•   2 x MSI nVidia GeForce 9500GT video cards (not SLI used for 3 monitors)
•   Stock cooling fan
I have not over clocked this system and do not intend to.  Upon first attempt to install windows 7 the installation would stall.  I then installed Windows xp 64 bit and updated BIOS and chip set.  I was then able to successfully install windows 7 64 bit. Shortly after the system began random re-boots with blue screen events, seemingly associated to driver issues.  I have updated every driver possible and still blue screen events.  I have run memtest86 to confirm RAM is okay several times with each stick.  Everything in BIOS is set to default so the RAM is actually not running at 1333 but instead is running at 1066. Thinking this to be the problem I increased the memory ratio to 5 thus making the DRAM frequency 1333.  Upon saving changes and re-booting windows begins to load gets to the black screen with swirling colors with “Windows is starting up” and hangs or re-boots.  I then thought I would manually adjust the DRAM Frequency to 9-9-9-24 with the same results.  I also increased DRAM Voltage to 1.65 and also the RAM manufacturers setting of 1.5 with the same results.  At this point the only way I can get windows to boot successfully is to set base clock to 133 and leave everything else on auto, or I can get it to successfully boot buy changing the Base clock to 166Mhz and leaving everything else on auto but the system remains unstable and re-boots after 10 minutes on Prime95 stress test.  I have tried using one video card.  I have tried running the DDR in Dual Channel. I am about to lose my mind please any advice would be greatly appreciated.

Similar Messages

  • USB 3 Instability Issues - Windows 8.1 - Windows 8, The USB 3 Stack Is Unstable On Multiple PCs And Many Devices

    The USB 3 stack is unstable in Windows 8.1 and Windows 8. I was hoping the upgrade to Windows 8.1 would improve the stability but no.
    On two different motherboard systems I have had the same experience with 64 bit Windows 8 Pro and Windows 8.1 Pro compatibility with various USB 3.0 devices and hubs including:
    An AFT PRO-57U front panel card-reader/hub, various Anker, Syba multiport hubs, and these are just a few I have tried, there are many more.
    Symptoms are the same.
    For example: the AFT PRO-57U slots are enumerated correctly as drive letters in Windows 8.1.
    Then the drives (the PRO-57U slots) disappear, then reappear, then disappear, and reappear and so on. This happens consistently and the cycle time to disappear/reappear varies from 10 seconds to 10 minutes.
    The Windows Device Manager shows the devices appearing and disappearing as enumerated devices. I have tried many trial and error methods to solve this, uninstalling and reinstalling USB motherboard drivers, different cables to the AFT PRO-57U device different
    USB 3 ports for the devices and many more...
    One of the hubs I bought specifically because it has the latest chip and firmware: Anker® USB 3.0 9-Port Hub + 5V 2.1A Smart Charging Port with 12V 5A Power Adapter [VIA VL812-B2 Chipset and updated Firmware 9081] This hub FAILs to enumerate some external
    HDDs and other devices.
    To troubleshoot I have tried many things:
    I have disabled Windows Power Options, USB Selective Suspend.
    I have disabled power options for each and every USB device in Windows Device Manager
    I have uninstalled the Asus AI Suite 3 software and the issues remain.
    I have tried BIOS settings for Legacy USB devices on and off and the issues remain.
    I have tried BIOS setting for xHCI Mode - Auto, Smart Auto, On, Disabled
    I have updated to the latest Intel chipset drivers 9.4.0.1026
    I have all the latest BIOS, drivers, firmware, devices, - anything that is involved with the USB 3 stack.
    Etc. etc. etc...
    I have contacted Asus, Gigabyte Intel, AFT, Anker Syba, etc. and they are all finger pointing.
    I have tried so many trial and error methods to solve the problem and I have run out of ideas.
    It is clearly an unstable USB 3 stack and I am not sure who is responsible although I suspect Intel chipset drivers. 
    USB 2 is fine BTW. All devices work correctly when plugged into USB 2 ports.
    From what I can tell, the entire USB 3 environment is a problematic P.O.S.
    If anyone has any ideas I am willing to try anything I have not already tried.
    Thanks,
    Michael Downs
    P.S.  Here is my system information. I have all the latest BIOS, updates, drivers and etc. for all devices.
    ASUS Maximus VI Formula w/ BIOS 1002
    Intel Core i7-4770K  BX80646I74770K      
    G.Skill Trident X 16GB (2 x 8GB) DDR3 2400 Model F3-2400C10D-16GTX
    Samsung 840 Pro 256GB  SSD Seagate Constellation CS ST3000NC002 3TB 7200 RPM 64MB
    EVGA GeForce GTX 760 ACX 2GB 256-bit GDDR5  
    Corsair Carbide Series 330R Mid-tower Case
    Corsair RM850 850W 80 Plus GOLD Certified
    Cooler Master Seidon 240M - Liquid CPU Water Cooler
    Pioneer 15X BD-R SATA Blu-ray Burner BDR-2208
    AFT PRO-57U All-in-one USB 3.0 5.25" Media Card Reader
    Then there is a similar system with the exact same USB 3 issues:
    Gigabyte - GA-Z77X-UP4TH
    Intel i7 3770K
    etc.
    mdd

    Hey, I hope this helps you out a bit... I have had the same issue on my Asus K55A notebook with Win8.1 Pro x64 from the beginning! Thru my extensive research I found something interesting and the possible cause to all this! What I found was that by design
    the xHCI Host Controller has virtual HS 2.0 Ports linked to the 3.0 Ports... Enabling compatibility with 2.0 devices ok... What happens is that the xHCI stack is unstable just like you say... The ONLY WAY I was able to fix the problem was by unlocking the
    UEFI/BIOS to allow me full access to USB Configurations... I had to disable 2 of the HS ports under the xHCI Controller since I have only 2x 3.0 ports... This allowed 3.0 devices to be enumerated correctly under the xHCI stack and 2.0 devices now were enumerated
    under the EHCI 2.0 stack... That's what worked in my case... I'm still digging around for more info about this issue because I find it so odd that no one discovered this when designing xHCI stacks and drivers at MS for Win8/8.1 x64... I hope I shed some light
    on this issue... Good luck and keep us posted!
    Hi, Sebastian. I have the same problem but i'm getting crazy trying to solve it. Can you help me to unlock the UEFI to access full USB config? and give me some suggestions on how to solve the problem?
    My mail is roquen(at)gamail(dot)com
    Thanks in advance!

  • MSI Neo2 Platinum (Winchester3200) - strange instability issue in Windows

    My specs:
    Winchester 3200 CPU
    MSI Neo2 Platinum 1.4 bios
    2 x 512 Kingston PC4000 3-3-3-8-1
    Gainward 5900Xt GS
    Seagate 160Gb SATA on SATA port 3
    The problem seems quite odd to me, so I decided to post here. Generally, the PC is stable, passes more than an hour of Prime95, 3d marks run fine etc.. but in Windows (XP Sp1) I'm getting this annoying issue: when I let the system run idle for a while, with none or some windows open but no programs active, my computer literally freezes. I can move the mouse, but i can't open any windows or click any buttons. Still, the keyboard is responding so I hit ALT + CTRL + DEL and get the Windows Security window. There I click on the Task Manager and all i get is an empty desktop, with the wallpaper but no icons or any activity whatsoever.
    Any suggestions? Thanks in advance.

    Quote from: Lorex on 10-March-05, 21:43:00
    Nope.. And I hardly believe it's a software issue. Will try a fresh install of XP today, nut the reason of such strange behaviour escapes me :] Cmon people, any ideas ?
    If you problem isn't related to software, then the only other thing that comes to mind is that overclocking is the culprit.  I'm not overclocking anything (except my 3d card, and that only slightly) and have no such problems with my K8N Neo2.  You describe a strange problem, certainly, and in my own experience such behaviors--system runs great in some normal situtations but in others it doesn't--have always been related to overclocking of some kind.  If you aren't overclocking anything then it's probably software induced.  Good luck!
     

  • What's with the instability?

    Wow, what a bummer this is! I got away from iMovie mostly because of it's instability. I thought sure FCPX would be more stable, but this 10.0.7 either locks up my computer so I have to do a force shutdown, or it Quits while I'm viewing the import window. I have no apps running, just FCP... still el crasho.
    The lockup seems to occur during background rendering activity. Is this modus operandi for FCP, or is there something I should be looking into to prevent these breakdowns?
    I do have a 4 plugins from FCPEffects. I suppose I could remove them to see if they're causing the hiccups. I'll have to redo a bunch of transitions after tho....

    check your installed fonts! Applications > Font Book > File > Validate Fonts. (You'd be surprised how easy it is to end up with a corrupt font... even one you've been using on a regular basis for years.) Also Check for Duplicates (two of the same font installed at the same time is really not good in Mac OS... never has been.)
    Almost nothing kills a mac app faster than a bad font. Just scanning down the Font menu over a bad font will evaporate FCPX (and Motion.) ]
    Oh... for the background rendering thing: check to make sure none of the clips you add to the storyline has those "tell tale" green (or just empty - they'll appear black) frames at the beginning or end. "Dead" frames will get the renderer really good and stuck. The solution immediately is to turn off background rendering, check all your clips and trim those bad areas out. Then you can turn bg rendering back on. If you use "third party" stock footage, quite frequently those dead frames end up on the front and back ends of the clips you get.
    ... not sayin' these two issues will fix your woes -- just be aware they can be part of your problems. (PS - they would account for your iMovie instability issues as well... [Core OS issues])

  • Network Disk / Air Disk Issues

    After recently upgrading the external hard drives at my workstation, I decided to try and use one of my Maxtor 5000DV drives as a networked drive - plugged into my AirPort base station.
    I'm a guy who has used the Mac since it's inception in 1984 - one reason being that stuff "just works."
    Of course, as we all know, that's not necessarily true. Some features, especially new ones, just DON'T. It's almost as if we're just beta testing stuff for Apple. If they can make it work over time, then they finally evolve it into something great, and if they cannot, it simply vanishes never to be mentioned again.
    I feel that's where I am with this feature of AirPort.
    I have called SIX different manufacturers of external hard drives. NOT ONE will tell me their product does or does not work when connecting to AirPort. What they will say is that it "should" work, and that they do not warranty it will work because the drives are not intended to be used in this manner.
    (1) My networked drive just disappears. I cannot reconnect to it unless I go into the sharing tab for the disk in APU, turn off sharing, reset, then go back in and turn it back on. Then the disk will be available, for a while. But it is not stable and always stops working at some point. I guess Apple forgot to mention instability issues when using this feature as a selling point for the product.
    (2) If not all drives are going to work, then shouldn't there be a list of compatible drives out there? If Apple understands the engineering of this product, then they should know what makes a hard drive compatible, or they should offer their own solution.
    I would appreciated any assistance that anyone can offer on this subject. I really need to make this work.

    If that's why TM is not supported, then it must be a serious technical issue. However, the product remains "current", and is still being sold with the stated USB Drive feature-set. If it's that serious, then the USB Drive claims should be pulled, or at least Apple should provide a complete list of verified Hard-Drives that *fully support* that feature.
    I believe this is exactly why someone in another post stated that he "felt like he was a beta-product tester for Apple." A very unusual claim, in my personal experience at least-- but one that should still be treated with integrity and compassion by Apple.
    There's an awful lot of AEBS users out there!

  • Live Stream Issues with FP 11.2

    We're seeing lots of bugs within the NetStream when connecting live streams and publishing/playing the stream via direct peer connections.
    Specifically when attaching a new Camera the receiving peer can no longer see the video stream. Also when toggling publish(bull) publish(streamName) from the publisher side and similarly toggling play(null) and play(streamName) from the subscriber side the streams don't play (render video) anymore even though i can see through the netwrok that the bytes are coming through.
    Along with this we seem to be getting new kinds of NetStatus errors ever since we started testing - "NetConnection.Call.BadVersion" was one we've seen but can't make any sense out of given we're using DIRECT peer to peer connections for the netstream classes.
    Lastly on general we're seeing lots of instability issues with on the h264settings applied to the nestream is this still in BETA? Instibility = crashing browser mostly when showing multiple video such as in a group video chat.
    Are any of you seeing this as well?

    Hi Damorgan,
    As you suggested, I did fresh 11.2.0.2 installation and find the mentioned components are valid from v$registry.
    Only desupported component is UltraSearch that I was asked to remove during upgrade and I did so.
    COMP_NAME VERSION STATUS
    OLAP Catalog 11.2.0.2.0 VALID
    Spatia 11.2.0.2.0 VALID
    OLAP Analytic Workspace 11.2.0.2.0 VALID
    Also the metalink note: ID 270588.1 indicates that mentioned components exists for 11gR2.
    DBUA was asking to install these component prior upgrading. My first note has that DBUA instruction.
    Is there any way to select mentioned components with "software only" installation prior upgrading?
    Thanks.

  • Check your PCI latency, may cause issu

    I , for the most part in my bios had PCI lat at 32. It was stable and no issue.
    Since getting a ZS i had a few instability issues.
    I then set PCI latency back to 64 and all seems fine now.
    If you dont have this option ( your Mobo must be old man ) then get PCI tweak tool from guru3d.com and set it to 64. If its already at 64 try 32 or 28. Have a play with it.
    Its just a thought but hey, if it works all the better then.

    Oh, i am no expert on PCI late ( someone correct me if I am wrong ) but its the time it takes for a device to send info/data to and from along the bus. When a device is needed it takes priority over others. Sometime having it set to 32 will force a device to use the bus even if it is not requested, thus instability.
    Hope it hel
    ps.

  • System instability with 3000+ and Mega 180

    My systems keep restarting in Windows when I change the FSB clock speed to 166 in the BIOS... I have an Athlon XP Barton 3000+ 333 FSB and a Mega 180 computer with 512 MB ram.  I suspect the CPU is not getting enough voltage supplied to it, necessitated by the increased clock speed; however, there is no option in the BIOS to adjust the CPU voltage.  I know some other users are using the 3000+ but does anyone know how to solve this issue?  In the meantime I've had to bump the clock speed down to 100 Mhz, leaving me with an underclocked 3000+ running at a mere 1.3 ghz :( No bueno, amigo!
    This shouldn't even be an issue because the motherboard states support for the 3000+ but it is causing my frustration to no end... any help would be greatly appreciated.
    Thanks everyone...
    P.S.  I have Windows XP Pro, SP1, latest nForce drivers, temperature is running around 55º C, and I even closed the MSI hardware monitor to make sure it wasn't giving false diagnostics, but the system still restarts .. I've reinstalled windows multiple times, still happening.. it has to be a hardware issue.

    He didn't say directly; however, he did allude to the fact that a lot of instability issues were caused by the ram settings in the bios.  I would venture to guess the auto detect function for the ram in the bios works with the supported ram manufacturers, but my ram is made by SpecTek... had to go on their site and get the values from a pdf... and then the values are in nanoseconds instead of clock cycles like the bios requires so I'll have to convert those values somehow... what I did do was play around with the values and bump the delay from 2.5 to 3 and that seemed to fix the stability issue...  this helps in the meantime before I figure out the exact value for each ram setting in the bios.. at least it doesn't restart anymore!

  • MSi z87-gd65 OC Genie and RAM frequency issues

    Hey all,
    I just built a new computer (my first build), and am quite glad with the capabilities of the machine. However, whenever I try to turn on OC Genie or bump up my ram speed to 2400 MHz(I believe this is the native speed, but the motherboard puts it down to 1333MHz) the system fails to boot, and sometimes hangs in a rebooting cycle. Eventually, the motherboard gives an error on the screen saying that the changes made have failed and was restored to default settings, and to press f1 or f2.
    I admit I am a complete novice at overclocking, and probably do not know what I did wrong. I've updated the bios, cleared cmos, and tried both bios A and B, but have got the same results. I was hoping I could get some help on this forum and learn new workarounds! Any help is greatly appreciated.
    My Build:
    i7-4770k @ stock frequency
    MSi z87-gd65
    Corsair H100i
    SeaSonic Platinum SS-860XP2 860W 80 Plus Platinum Certified
    Samsung 840 Evo SSD 256 gb
    Corsair Vengeance Pro 2400MHz CMY16GX3M2A2400C11R

    Quote from: phantom24 on 19-October-13, 08:56:19
    Hey man, thanks for replying. The first thing I tried, before overclocking, was to enable XMP from the UFEI. When i enabled it, the board would show that memory was OC'd to 2400MHz and bumped up to 1.65 voltage. This is all shown prior to rebooting. When I would reboot the computer however, the system would fail to boot and I would get the same error saying all "overclocking failed, reset to default settings". I believe that my ram is the cause for my inability to overclock. I found out that motherboard is not compatible with it at extreme speeds. The max speed I can get out of my ram is 2133MHz with no problem whatsoever in rebooting. This is without changing the voltage of the ram( keeping it at 1.5v) . If I change the ram voltage, I'm pretty sure it would fail to boot.
    Yeah good luck with OCing and please let me know if you find anything useful. I'm afraid that this forum does not have much to offer, so you may want to try some other forums.
    Jms and Xfx are right. By default mine booted to at 1600mhz. I enabled XMP and it brought it to the rated speed of 2133mhz. I'm not trying to overclock my ram further than the rated speed. Pointless to me, considering I'm coming from a rig that had ddr2 with 800mhz. As you can see in my pic, the one with blue LEDs is the 7.5 year old build. Still going strong. Anyhow, if you do overclock, make sure you disable the XMP. That way you can eliminate another possible instability issue. I'm a member of a few forums, and I was suprised to see these forums not respond very well. For the guys who did respond, I thank you! You may also want to check out overclock.net   There's are plenty of people there and "clubs" you can be a part of. I'm finding a lot of useful information there. Most people won't get mad about noob questions unless you do like me and ask the same ones in multiple threads lol! Hop on over there and check it out. My name there is Scotty Mac.

  • A Few Anomalies

    After waiting a long time I was finally able to upgrade my iMac and install Aperture. For the most part I am pleased with A3 except for getting used to certain anomalies and instability issues encountered in this early version.
    I have used iPhoto for as long as it has been out, but wanted more power to handle my growing image collection. I started taking digital pictures with a Kodak DC 120 camera (anyone interested in an antique?) so some of my older pictures are pretty low resolution, and I still shoot with an older Canon PowerShot. I say this because I believe it contributes to one of the anomalies I have run into in A3.
    Magnification - on most of my photos I am able to magnify the image as expected, but on my older lower resolution images A3's magnify behaves strangely. For some reason A3's magnify tool will not work. In iPhoto the same image magnifies correctly. I called Apple about this but they were unable to explain it or help. The only suggestion made was that low res images may not be able to be magnified, however I can find no documentation of this.
    *Red Eye Tool* - I struggled with getting this tool to work, but after much experimentation I discovered that the size of the cursor is the crucial factor. If the cursor is to small the red-eye effect tool will not work at all. Increasing the size of the cursor solves the problem. Even after discovering this, photos with red eye are poorly corrected in A3, while in iPhoto the correction is excellent.
    *Inconsistent application of tool effects* - when using the adjustment tools I find that the way they are applied to the image is not consistent. Most of the tools show the immediate effect of the tool, except for the Red-eye tool and the Crop tool. With these two tools you have to exit the tool or click on some other tool to see the effect applied. This took some getting use to, because at first it appeared that the tools did not work. In iPhoto, these tools use an apply button so you do not have to exit the tool to see it applied.
    *Strange interface* - I use keywords extensively, and love the keyword generator feature of nested keywords. This is very helpful in organizing keywords. What is a little strange is the clunky way one has to apply them. The drag and drop method is cumbersome. the buttons which you can display at the bottom of the window is much better, but groupings are limited to 20 buttons, so you end up using the drag and drop method. The search window for keywords lists all of your keywords in one huge alphabetical list and all organization you did in the keyword generator is lost. This seems very strange. Why use nesting of keywords if you can't see the nesting when you need to do a search? It also seems strange that when a nested keyword is applied its related keywords are ignored. For example if I create a nest as follows People>Extended Family>Grandfather Arvid>Bud's family, and apply the keyword _Bud's family_ to a photo, all the higher categories are ignored and only the keyword _Bud's family_ is applied. If I want the other keywords to also apply I have to shift click on the group and drag it over, again the advantage of nesting is lost. Seems like this good idea was not fully developed in A3
    *Unexpected crashes, and lock-ups* - I have experienced several crashes of A3 when using tools or editing things like keywords. When this happens the notify Apple box appears and I send it to Apple with my comment, relaunch the program and continue to work. I never seem to loose data so that is a plus. I have also had a couple of lock-ups when the spinning wheel of death appears on the screen. This happened when the program was trying to update thumbnails. I keep the activity monitor open so I can see what is going on. I have had to force quit the program and relaunch.
    It appears that A3 is in serious need of an update, but that is not unexpected with this being the 3.0 version. On the whole the program works very well and I am pleased with it. The program is very fast in its 64bit mode, even if, as I have read in this discussion, the iMac boots into 32bit. I am anxiously awaiting an update from Apple.

    No version of DW will manage links that are embedded in
    javascript - is that
    what you mean?
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Hendersonville" <[email protected]> wrote
    in message
    news:f0j0fp$nlp$[email protected]..
    > There are a few anomalies with templates in Dreamweaver
    Version 4 such as
    > using DHTML addressing. Have these been fixed in Version
    8?

  • Safari is slooowwww after HD upgrade

    I just upgraded my 400mHz Pismo to a 100 Gb Hard drive with a 16 MB cache. It spent a few weeks in an external Firewire enclosure - being partitioned, having Tiger installed and transferring settings, folders, files, etc. I was able to boot from it, and use it fully, so I figured it was time to go ahead and make the swap.
    After doing so, all seemed okay except that Safari is having a really hard time loading pages. I should also mention that it is connecting and loading pages correctly, it’s just doing it excruciatingly slowly. I’m connected to the internet via a third-party wireless card (Sonnet Aria Extreme) and all Airport and Network settings seem to be in order. Before swapping drives, I copied all my old Safari bookmarks over to the new drive and again, everything looks like it should be okay, but my tabs give me the pinwheel icon for minutes on end (even when loading one page at a time) and it acts as if I’ve simply got a slow dialup connection. If I boot from my old drive (now in the enclosure) and open it's Safari, no problem - even multiple tabs load as quickly as ever.
    Is there anything I can do to optimize it? I mean, I’m fully updated via Software Update, but should I reinstall Safari or something?
    Powerbook G3 Firewire (2000 Pismo)   Mac OS X (10.4.3)   100 Gb internal HD, 1 Gig RAM

    I appreciate the reply, but that post's been up for almost a month, with no input from anyone. No big deal - some get responses, some don't. But I'm not "happy complaining", I'm happy when things work as they should. I've been proactive about trying to remedy the situation, of course. I just figured I'd close that question down, seeing as how doing a search for "crash" or "slow" in the Safari discussions returns an abundance of similar posts. I'm certainly not alone on this one.
    It seems that Safari has some major instability issues in Tiger. A lot of people have reported them, and a lot of people have been drawing blanks as to what's causing them. I for one, first noticed it when my clean install of Tiger on a new HD had more Safari problems than the old one that was cluttered with cookies, add-ons, etc. After finally getting it to connect, there was a progressive decline in loading and response time, until finally, Safari would just "close unexpectedly" in the middle of a session, or even give the same error when I would close the program voluntarily.
    I've cleared caches, trashed prefs, removed plug-ins, repaired permissions, and run Disk Doctor - pretty much anything that's been suggested in the Safari Discussions, and nothing. I'm sure Apple is aware of the problem, and given the choice, I'd prefer to use Safari, but it's become virtually useless. I'd love to pore over the problem until a solution becomes apparent, but I need to stay productive. Until there's an update or a less temporary fix becomes available, I'll just have to use Firefox to scan these forums.
    We'll see if 10.4.4 helps...
    Powerbook G3 Firewire (2000 Pismo)   Mac OS X (10.4.3)   100 Gb internal HD, 1 Gig RAM

  • 865PE Neo2-FIS2R and Geil memory problem

    With 512MB (2x256) of Corsair XMS 3700, the system is perfectly stable (runs 24/7 crunching for UD, also have done Prime95 torture test).
    With 1-GB (2x512) of Geil PC4000 Ultra Platinum, the system is very unstable.  It usually won't even boot fully into Windows without a BSOD (which vary) or if it does get into Windows it crashed soon thereafter.
    If I put the Corsair memory back in (like I have them right now, to be able to use the system to post this message), the system is back to 100% stable, so it seems to be entirely a memory-related problem.
    MSI 865PE Neo2-FIS2R (MS-6728)
    Intel P4 2.4C 800FSB (HT enabled) @ 3.19-GHz
    AVC Sunflower 2 HSF
    420-W PS
    Windows XP Pro SP1a
    BIOS settings:
    Dynamic OC Disabled
    Performance mode Slow
    DRAM Freq 266
    CPU Bus 266
    DDR Clock 354
    AGP/PCI 67/34
    CPU vCore 1.6000
    DDR volts 2.70
    AGP volts 1.50
    SPD Disabled
    3-4-4-8, 4 burst
    Have run MemTest standard test on the Geil modules individually and as a pair, and have tried different slots.  Testing thus far shows no errors when each module is installed separately, but when used in a pair there are sometimes errors shown.
    Have tried the modules in slots 1,3 and slots 2,4 with no difference.
    Have tried setting DDR voltage from 2.70 up to 2.85v for the Geil (approved up to 2.9v) with no apparent change in stability.
    Have tried changing Spread Spectrum setting between enabled and disabled.  Disabled seems to be better, but problem remains.
    Have tried using SPD disabled with settings listed above, and SPD enabled (which sets timings at 2.5-4-4-8,8).
    Edit: I'd asked for advice, but then realized that the very limited timeframe in which I could return the Geil would expire if I waited beyond business hours today.  So I've RMA'd the Geil and have ordered a 1-GB Corsair TwinX XMS 3700 pack instead.

    I've had similar problems to you but with Corsair TwinX LL's and if you read back a month in this forum you will see others have also with various memories on the 865 FISR.
    The fix I found was Kingston memory but others have had problems with Kingston.    There was a thread running a week or two ago attempting to document successful memory mobo combinations.
    Bottom line, stick with what works on your mobo until MSI fix the incompatability/instability issues.

  • Programs crash in one of the Windows 7 Accounts

    First of all, if you are reading this, I’m sorry it’s so long winded. But the issue is complex and I wanted to provide enough details to allow the best of solutions.
    I have two accounts in my Windows 7 Home Premium equipped Satellite L505D laptop. They are Administrator and Owner. I run in the Owner account. I have experienced several issues that have been blamed on problems with the Owner account.
    The worst issue is that the PC freezes up if I don’t turn on Silent mode in Norton Internet Suite 2010. If it’s not in Silent mode, the computer freezes up every time. Believing it to be a Norton issue, I spent literally more than 30 hours with Norton techs until the issue was escalated to a senior tech. After several more conversations and trials and errors, he suggested that I switch to Administrator mode and see if the machine freezes with Silent mode turned off. It didn’t freeze up at all. Therefore, it’s Norton’s opinion that there is an issue with "permissions" in the Owner account.
    A similar problem is that three or four other programs freeze up. They don’t cause the PC to stop working—only the program stops working. Of them, two are programs that are not on the Windows 7 compatibility list. Knowing they are not on the compatibility list, I installed them anyway and they work with no problem other than they sometimes freeze up. The other program that stops working is MS Outlook 2003, which is on the compatibility list, but it sometimes stops working, too.
    A final problem is that in the Owner account, I sometimes can not access files on my desktop PC via my LAN using Windows Explorer. I can always access the files from the Administrator account. In the Owner account, I’m unable to access the files about 1/3 of the time. But if they are accessible, they remain assessable until I turn off one or both of the PCs. When I reboot, it’s always a question whether I can access the files. However, even though I may not be able to view the files in Explorer, I have access to the files from within programs as long as it’s a recently opened file. For example, if I recently worked on a document in Microsoft Word on my laptop and the file is on the desktop PC, I can open the file from the laptop even though I can’t see the file with Windows Explorer. That is true of any program and any file as long as the file is listed in the recent files list of the program. If it’s not on the list and Explorer isn’t working, then I don’t have access to the file.
    I have had four or five conversations with Toshiba support techs since Norton gave me their opinion. Three said that I need to so a System Recovery. Two of the calls were today and the first one said that I could delete the Owner account and set up a new account. This would be a lot less time consuming than doing a complete recovery and I was hopeful it would resolve the issue. He was going to walk me through the procedure and we were disconnected. When I called back, the different rep discouraged me against replacing the Owner account. He suggested using a Restore Point. If that didn’t work, follow it with a System Repair. If that didn’t work, then the next step is full System Recovery. I checked the restore points and I have nothing newer than August and the problem dates back several months.
    So here are my questions: 1. Should I expect that replacing the current Owner account with a new Owner account will resolve the issue? 2. Could the issue be caused by the installation of programs that are not on the Win 7 compatibility list? 3. If the older programs do cause an operating system instability issue could that by resolved by an upgrade from Windows 7 Premium to Windows 7 Professional, which would allow me to run Windows XP in virtual machine mode?
    I would appreciate your input.
    Thank you.
    Dan
    Solved!
    Go to Solution.

    1. So you have problems in both the Owners and the newly minted Danny account….
    Jerry, yes the problem is with the Owner’s acct and has been all along. And it’s in the new account, Danny, which I created at your suggestion. As to whether they were created as "Standard" user accounts, I have to confess that I have no idea. You see, I have never had an appreciation for "Accounts" and, therefore, have never learned about their significance. So when I bought my Toshiba, I didn’t create any account. Although I have since learned that it came with two accounts, all I did was turn it on and start loading programs. I only learned about the Administrator account being separate from the Owner account in my many conversations with Norton. I have used the Owner account all along not by any design on my part. It was because it booted up in the Owner account.
    2. Worth tearing Norton out by its roots…
    I’ve been anti-Symantec for years. I just haven’t found Internet Security Suite that is rated as highly overall. I’ve been thinking about removing it to see if this problem would go away. I didn’t  because the senior tech support person convinced me it is a Windows "Permissions" issue. His viewpoint was more plausible because of the occasional freeze up of other programs (but the PC itself doesn't freeze up with them).
    3. There are dozens of Satellite L505Ds…
    Oops…I thought you were just asking for confirmation of the L505D nomenclature. The complete info is L505D-S5983, part number PSLV6U-00J001.
    4. Bingo. You got that right. I've hung around CompuServe since 1980…
    I was a CompuServe user long before their unfortunate acquisition by AOL. I had a couple of IDs over the years. I don’t remember the long term one. My current ID is DannySall. I logged into the WUGNET forum and found one of my postings from last May to which you replied. Outlook 2003 wouldn’t retain its password. I sent a reply to you on July 25 to say that I resolved the issue by deleting an account.
    5. Because of your Microsoft knowledge and connection, I'd like to ask you about something else. I have a few programs that are not on the Windows 7 compatibility list. I figured I had nothing to lose and tried installing them anyway. I was able to install all but one of them. They run with no problem. My question is this: Is it possible that installing non-compatible programs can damage the operating system and cause the problems I have?
    Thank you for all your time and suggestions.
    Dan

  • Why are animated GIFs still broken?

    https://discussions.apple.com/thread/1229922 <-- this
    'nuff said, this has been a problem ever since Preview lost its ability to animate GIFs. It may be a WebKit problem (i.e. yeah, Apple, just go ahead and let yourself off the hook...right), but regardless, how come it has not been addressed sooner? Safari chokes after about 4 frames of animation; if the GIF loops, it starts over fresh, but it chokes again.
    I am using 10.5.8, but I am aware this is still a problem for all 10.6 OSes and iOSes. I don't know about Safari for Windows; not relevant at the moment.
    Why is this still a problem after three-and-a-half years of Safari development have passed?

    Well, here are the issues I have run into.
    1) Gifs load half way and then animate on the base but not on the top.
    2) Gifs animate waaaaaaay too fast.
    I have found no solution for the 1st issue, and it does not always occur.
    As for the second one it has to do with browsers all reading the "0 delay" setting of the animation at uniquee speeds. Most round it to 10/100th of a sec, while Safari loads it at 3/100th resulting in a faster images, but a non-standard speed. Which ***** since I am running animations that follow using a set time out only to have safari throw everything off. I think one other browser runs at something like 6/100ths so Safari is not the only one. Faster could be nice if they all got on the same page, but as they are it is pointless. Pretty much meaning if you want an animated gif you have to avoid the "0 delay setting at all costs, and pretty much anything under 1/10th because it will not display the same in many browsers. It could be this fast speed in Safari that is causing the loading and instability issues with sime.

  • Switching between VTs kills Xorg and GDM restarts

    Hi,
    since yesterday I noticed some sort of severe problem of my system.  I am still trying to locate the reason why this all happens.
    My problem looks like this: Every time I switch from X to a VT everything looks fine. But once I want to switch back to X, it dies completely and GDM restarts.
    So far so bad, first I thought GDM is creating this and downgraded it to 2.22. That didn't help, so back up to date.
    But I activated its debug modus to receive this output:
    Oct 5 10:05:10 t23 acpid: client 3785[0:0] has disconnected
    Oct 5 10:05:10 t23 acpid: client connected from 3785[0:0]
    Oct 5 10:05:10 t23 acpid: 1 client rule loaded
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmWelcomeSession: child (pid:3808) done (status:1)
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSimpleSlave: Greeter exited: 1
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): slave finished
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmWelcomeSession: De-registering session from ConsoleKit
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmWelcomeSession: Stopping D-Bus daemon
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: sending signal 15 to process -3807
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSimpleSlave: Stopping simple_slave
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSlave: Stopping slave
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSlave: Disconnected from display
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSimpleSlave: Stopping greeter
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GreeterServer: Stopping greeter server...
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionDirect: Closing session
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: Stopping job pid:3833
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: sending signal 15 to process 3833
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: Waiting on process 3833
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: process (pid:3833) done (status:1)
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: Wait on child process failed
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: SessionWorkerJob died
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionDirect: Disposing session
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionDirect: Closing session
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmServer: Stopping server
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: sending signal 15 to process 3785
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmServer: Waiting on process 3785
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: process (pid:3785) done (signal:6)
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmServer: Server died
    Oct 5 10:05:11 t23 gdm-session-worker[3833]: DEBUG(+): GdmSessionWorker: obj_path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local method=Disconnected
    Oct 5 10:05:11 t23 gdm-session-worker[3833]: DEBUG(+): GdmSessionWorker: Got disconnected from the server
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSignalHandler: Removing handler 10: signum=11 0x80536e0
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSlave: Stopping slave
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): Slave finished
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: slave (pid:3784) done (status:0)
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Slave exited: 0
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Finishing display: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Unmanaging display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: unmanage display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Killing slave
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Disposing slave proxy
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Killing slave
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmLocalDisplayFactory: static display status changed: 0
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Managing display: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: manage display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Preparing display: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: prepare display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: creating xauth directory /var/run/gdm/auth-for-gdm-XXXXXX
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: chowning /var/run/gdm/auth-for-gdm-XBcN2s to 120:120
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: creating /var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: chowning /var/run/gdm/auth-for-gdm-XBcN2s/database to 120:120
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: chmoding /var/run/gdm/auth-for-gdm-XBcN2s to 0711
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmLocalDisplayFactory: static display status changed: 1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Running command: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Started slave with pid 3859
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): Enabling debugging
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 1: signum=15 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 15 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 2: signum=2 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 2 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 3: signum=4 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 4 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=7 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 7 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 5: signum=8 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 8 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 6: signum=1 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 1 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 7: signum=11 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 11 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=6 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 6 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 9: signum=10 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 10 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 10: signum=12 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 12 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Registering /org/gnome/DisplayManager/Slave1
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: starting slave
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Starting slave
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Creating proxy for /org/gnome/DisplayManager/Display1
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Got display ID: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:12 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Setting slave bus name::1.50 on display :0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 11: signum=10 0x80536e0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Starting X server process: /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-XBcN2s/database -nolisten tcp vt9
    Oct 5 10:05:12 t23 gdm-simple-slave[3860]: DEBUG(+): GdmServer: Opening logfile for server /var/log/gdm/:0.log
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Started X server process 3860 - waiting for READY
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Started X server
    Oct 5 10:05:12 t23 acpid: client 3785[0:0] has disconnected
    Oct 5 10:05:12 t23 acpid: client connected from 3860[0:0]
    Oct 5 10:05:12 t23 acpid: 1 client rule loaded
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: handling signal 10
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Found 2 callbacks
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: running 10 handler: 0x80536e0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: running 10 handler: 0x804d1b0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Got callback for signal 10
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Got USR1 signal
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Done handling signals
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Got USR1 from X server - emitting READY
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Server is ready - opening display :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Connected to display :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Requesting timed login details
    Oct 5 10:05:14 t23 gdm-binary[3373]: DEBUG(+): GdmSlave: Got timed login details for display :0: 0 '(null)' 0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Got timed login details: 0 0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Running greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Creating greeter for :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Running helper /usr/lib/ConsoleKit/ck-get-x11-display-device --display :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Got tty: '/dev/tty9'
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Trying script /etc/gdm/Init/:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script /etc/gdm/Init/:0 not found; skipping
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Trying script /etc/gdm/Init/Default
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Running process: /etc/gdm/Init/Default
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: XAUTHORITY=/var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: X_SERVERS=/var/gdm/:0.Xservers
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: LOGNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: PWD=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: HOME=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: DISPLAY=:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: PATH=/usr/local/bin:/usr/bin:/bin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: SHELL=/sbin/nologin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: RUNNING_UNDER_GDM=true
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: USER=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: USERNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Process exit status: 0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: Creating D-Bus server for greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: D-Bus server listening on unix:abstract=/tmp/gdm-greeter-LPWxSRoX,guid=6a268b231fa1c460f956c0f500000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Creating greeter on :0 /dev/tty9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Starting welcome...
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Running welcome_session process: /usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Registering session with ConsoleKit
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Opening ConsoleKit session for user:120 x11-display:':0' x11-display-device:'/dev/tty9' remote-host-name:'' is-local:1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Starting D-Bus daemon
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Cannot access '/etc/sysconfig/i18n'
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: WINDOWPATH=9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: DISPLAY=:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XAUTHORITY=/var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LOGNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_VERSION=2.32.0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: HOME=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LANG=en_GB.utf8
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/lib/perl5/core_perl/bin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PWD=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: SHELL=/sbin/nologin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GVFS_DISABLE_FUSE=1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: RUNNING_UNDER_GDM=true
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USER=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USERNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XDG_SESSION_COOKIE=55a05d047ffc8a00c35d0e0047eda69e-1286269514.940105-1594411165
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_GREETER_DBUS_ADDRESS=unix:abstract=/tmp/gdm-greeter-LPWxSRoX,guid=6a268b231fa1c460f956c0f500000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3878]: DEBUG(+): GdmWelcomeSession: Setting up run time dir /var/run/gdm/greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3878]: DEBUG(+): GdmWelcomeSession: Changing (uid:gid) for child process to (120:120)
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Started D-Bus daemon on pid 3882
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Cannot access '/etc/sysconfig/i18n'
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_SEAT_ID=Seat1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: WINDOWPATH=9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: DISPLAY=:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XAUTHORITY=/var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LOGNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_VERSION=2.32.0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: HOME=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LANG=en_GB.utf8
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/lib/perl5/core_perl/bin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PWD=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: SHELL=/sbin/nologin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GVFS_DISABLE_FUSE=1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ZckquHbw5o,guid=bb2af808d623ae703f9916fa00000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GCONF_DEFAULT_SOURCE_PATH=/etc/gconf/2/path
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: RUNNING_UNDER_GDM=true
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USER=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USERNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XDG_SESSION_COOKIE=55a05d047ffc8a00c35d0e0047eda69e-1286269514.940105-1594411165
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_GREETER_DBUS_ADDRESS=unix:abstract=/tmp/gdm-greeter-LPWxSRoX,guid=6a268b231fa1c460f956c0f500000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3883]: DEBUG(+): GdmWelcomeSession: Setting up run time dir /var/run/gdm/greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3883]: DEBUG(+): GdmWelcomeSession: Changing (uid:gid) for child process to (120:120)
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: WelcomeSession on pid 3883
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Creating new session
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Creating D-Bus server for session
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: D-Bus server listening on unix:abstract=/tmp/gdm-session-UgKEyrlf,guid=3f8d34c80542f206f87332a000000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Setting display device: /dev/tty9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Registering /org/gnome/DisplayManager/Session1
    Oct 5 10:05:15 t23 gnome-session[3883]: Bonobo-WARNING: Bonobo must be initialized before use
    Oct 5 10:05:15 t23 gdm-simple-greeter[3905]: DEBUG(+): Enabling debugging
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: Handing new connection
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: greeter connection is 0x9699308
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Greeter connected
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Starting conversation
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionWorkerJob: Starting worker...
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionWorkerJob: Running session_worker_job process: /usr/lib/gdm/gdm-session-worker
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionWorkerJob: : SessionWorkerJob on pid 3908
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=GetDisplayId
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): greeter_server_message_handler: destination=(null) obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=GetDisplayId
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): Enabling debugging
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSessionWorker: connecting to address: unix:abstract=/tmp/gdm-session-UgKEyrlf,guid=3f8d34c80542f206f87332a000000198
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Handing new connection
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: worker connection is 0x969ac90
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Emitting conversation-started signal
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: session conversation started
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Requesting timed login details
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 1: signum=15 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 15 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 2: signum=2 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 2 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 3: signum=4 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 4 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=7 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 7 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 5: signum=8 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 8 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 6: signum=1 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 1 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 7: signum=11 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 11 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=6 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 6 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 9: signum=10 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 10 signals
    Oct 5 10:05:16 t23 gdm-binary[3373]: DEBUG(+): GdmSlave: Got timed login details for display :0: 0 '(null)' 0
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Got timed login details: 0 0
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): Invalid NULL username for auto/timed login
    Once I switch back, GDM reloads and I get the same output with GDM stating nothing why this happened.
    I looked through all log files without finding anything obvious. My problem is, that I am not sure if it is GDM doing this or some buggy configuration of a programme doing rubbish...
    Some helpful advice will be nice.
    Regards,
    Simon

    Problem solved temporarily:
    I downgraded all X.org packages related to the recent update for xorg-server 1.9. Since then GDM doesn't seam to crash. Otherwise I noted that 1.9 is not much of a matured release yet. I read many instability issues here.
    Btw, would a mod like to move this thread to update issues? This thread will better fit in that section.
    Thanks
    Last edited by ss2 (2010-10-07 14:40:32)

Maybe you are looking for