Wine causing lock ups

I play WoW and have been experiencing complete freezes. After the first few times I set up ctrl-alt-backspace in X (using the code provided in the newbie guide on the wiki) but the computer didn't respond next time it crashed. I also can't switch to a different session with alt-F2 ect Compiz is also unresponsive, so the only choice I have is to hit the reset switch, which I really don't want to do. I'd think it was an x or compiz problem but arch runs beautifully for everything else I do with it. I haven't had a single lock up with any other program. Is there any way to configure wine to run so that in the event of a crash it doesn't take my system with it?
using 2.6.30 kernal
Gnome 2.26.2
Compiz-fusion
wine 1.1.24
Last edited by blackfedora (2009-08-10 19:29:09)

just kidding, after serveral days of clean play I experienced lockups in metacity. I've tried playing without add-ons, I've messed around with verious winecfg settings playing windowed versus full screen. Nothing. However, today I found some posts in other forums that suggest that this is a 64 bit Linux problem. Have any other 64 bit arch users experienced similar problems? Would a lose a ton of functionality out of my 2.66 Ghz intel quad core if I switched to 32 bit arch?
::edit:: I'm sorry for the lack of logs but I don't know how to check out a computer once the system has crashed, I can't switch to a different session with alt f2 or anything, it just locks up and replays the last half second of sound. If there are any settings or logs which might be helpful I will gladly post them, I just don't know what they are
Last edited by blackfedora (2009-08-10 19:35:00)

Similar Messages

  • PSU causing lock ups when gaming? K9A2 Platinum

    I am having black screen and occasionally grey screen lock ups when Im playing games. It can happen within 10 minutes or up to an hour. I have to press the power button to restart and dont get any windows errors or blue screen. I have no issues when watching videos or just tooling around. My PSU is a OCZ600MXSP and Im thinking its not up to spec. I have everything running stock. Is it likely my PSU doesnt cut it or is the black/grey screen freeze thing an cpu/gpu overheating issue?

    All of my drivers are up to date (I do use driver sweeper as well). It happens pretty much in all games, from BFBC2 and TF2 to some crappy kid game my son plays online (Wizard 101?). Im not sure what the temps are under load but at idle they are good (cant recall what exactly they were but were in the proper temp range). My monitor has just finally died as Im typing this on my laptop (bad caps on power board  ) so Ill test the temps while gaming when I can hook it up to my big LCD.
    Could the lock up with no blue screen/error report indicate a component overheating?

  • USB CAUSING LOCK-UPS

    Hi,
      30-40% of the time when I use my front usb it will cause Win XP to lock up and I have to hit the reset button.  Has anyone else experienced this and also any remedies?  It happens with my scanner, gamepad and ipaq.  Setup=Win XP prof w/ service pack 1, KT3ultra2, AMD 1600xp, power supply is 400 watts.  
    Thanx

    Hi Maesus,
      I have AMI bios version 3.31a.  I can't find the usb version on XP (I only know how to get to it on Win 98SE).  It's the one that came with Win XP.  If it matters, the VIA driver I'm using is v4.42.  Lastly the USB connectors are the ones built into the front panel of my case.  I wired it up according to the manual.  
      Again, the unusual thing is when it doesn't lock-up everything works fine.
    Thanx again for your help

  • Keyboard viewer causing lock ups

    Keyboard viewer is causing me some headaches. I have a handicapped user who can better use a mouse than a keyboard, and needs to use keyboard viewer. However, after enabling keyboard viewer, if they user logs out of the computer, and logs in again later he gets constant pinwheels. The keyboard viewer does not show up, but if I look at the international menu it gives me the "hide keyboard viewer" option.
    If I open up a terminal and run top, I see that every time I click on something, move a window, or interact with anything the kernal_task jumps from 1% cpu to 8% for 15-30 seconds, and beachballs. Then kernal_task will drop back down to normal levels and the system begins responding again until something else is done.
    If I go to the international menu and hide the keyboard viewer before logging out, and then log back in, I am able to turn it on and use it just fine. The problem only occurs when keyboard viewer is left showing, and the user logs out. So there is a work around, but sometimes he'll forget to hide it and logs out, causing problems next time he logs in.
    This only occurs when using mobile accounts. If set up a local account on the computer, it isn't a problem. If I remove the computer/account from all management and synchronization it still happens. It will occur on any computer the user logs into if they enable keyboard viewer.
    Any thoughts?

    Thanks for that BDAqua,
    I will take a look at that software. I am little reluctant to go third party in that I am a student and can't dictate which Apple mac I am using at my college. They frown on installing third party software. So I am really looking for a solution that is already on the OSX. I tried sticky keys but I can't seem to make it work on the Keyboard Viewer. (I am also surprised that the caps lock does not work normally on Keyboard viewer). I can't believe I am the only one that has only mouse input of text!
    So my question remains, will modifier keys be operable with a single click on Keyboard Viewer, and will a macro key be operable /definable for specifically modifier keys in keyboard viewer?
    TIA

  • PCI-e wireless card causes lock ups Z87 MPower MAX

    I've already asked this question once, but was part of an epic essay that I've decided to break down into smaller more manageable chunks (as unsurprisingly that one got no replies).
    I've got an ASUS PCE-A66 wireless ac pci-e card. Had absolutely no issues with it in my old Z77 board, but I seem to be having a lot of issues with it in my new Z87 MPower MAX. System was locking up like mad when I was trying to install the drivers at first. Had to rip out the WiFi/Bluetooth/WiDi module to get the drivers installed but the system randomly hangs on boot up? Don't get the issues with the card unplugged and don't always get it with it plugged in, but there seems to be some form of conflict with it that I can't resolve. Has anyone else had any such issues with any PCI-e add in cards on this motherboard?
    Specs are:
    i7 4770k
    MSI MPower MAX using .128 bios (will try the .131 later)
    2x4GB Corsair Dominator Platinum 2400
    Coolermaster Silent Pro Hybrid 1050w
    EVGA NVidia GTX 780 SC ACX
    Windows 8 Pro 64bit

    Yes, old system was Win8 Pro 64 bit too and the drivers are Windows 8 certified. As I say though, I had no issues with it on the old build? Even got a replacement sent out by Amazon in case the card itself was damaged  Did initially try to do a warm update of the hardware into the same OS installation but didn't play well so did a full re-install in the end. Tried standard and UEFI installs (just in case) and after a problem with my OCZ Vector 2 not being recognised I bought a new Samsung 840 Pro so was a virgin SSD installed on to as well.
    I'll raise it directly with MSI but just wanted to know if anyone else had experienced anything similar with any wireless cards in this mobo.
    Cheers for the reply though 

  • Audigy 2 on Neo2 Platinum causes LOCK UPs/BSODs!!! Help!

    I have a videocard with a HUGE, I mean HUGE custom CPU heatsink attached to it.  This leaves me only ONE slot available for my Audigy 2.  And that slot is the last slot 5, orange color.  
    Its the ONLY ONE AVAILABLE.  I read on these forums about some incompatibility of Audigy 2 with MSI Neo2 Platinum.  Thats what I have.  I tried several later and older BIOSes including the official one and the latest beta one.
    Still, when I play UT2004 or some other games that demand EAX/Hardware 3D sound - I get a dark blue BSOD without a message (its like a non-WinXP BSOD, its a hardware BSOD as I call it, dark blue color).  It comes with a sqeeking sound.  I have to restart my PC afterwards.  
    It happens after 3-4 minutes of playing.
    When I REMOVE the soundcard - everything is fine, NO BSOD.  
    I tried different Audigy 2 drivers, but they all give the same result.  This did not happen on my old ASUS A7N8X-Deluxe 2.0, and the soundcard was in PCI Slot 5 as well.  I tried to format, and etc., - same thing if the soundcard is in the PCI slot!  
    I have PCI lock ENABLED (AGP set to 67Mhz, and PCI LOCK DETECTION set to ENABLED).
    How do I fix this problem?

    Quote
    Originally posted by MonarchX
    I have PCI lock ENABLED (AGP set to 67Mhz, and PCI LOCK DETECTION set to ENABLED).
    When you said that you have PCI lock enabled and PCI lock detection enabled, were you talking about the same thing?  If not, where in the BIOS is the PCI lock? I could only find PCI Lock Detection.

  • Saffplg.js is causing lock ups in firefox

    I have firefox 24.2 and it keeps locking up with a saffplg.js error. I am running windows 7 professional and McAfee.

    Also see...... https://support.mozilla.org/en-US/questions/748889

  • MSI VN220GT MD1G|GeForce 220 GT - causing lock ups/screen freezes

    Hi, I've been searching everywhere for my problem, and the things I find usually are left unanswered :(
    I recently upgraded my old graphics card (GeForce 7300 GT) to the GeForce 220 GT, at that time I was using Windows XP SP3. Everything went fine then, I downloaded the newest driver from nVidia (195.62) and restarted, everything went smoothly.
    It was then my computer started to freeze, to the point where I can't do anything (mouse/keyboard unresponsive). I am forced to force reboot. This freezing usually happens randomly when there's nothing to provoke the problem.
    So I decided to upgrade to the new Windows 7. I did everything it told me to and everything went very well. But the problem still occurs, but more often, and around 30 minutes after logging in. I got the Windows 7 32 bit version of the new nVidia driver (195.62) and installed it. Did nothing. I have also tried to update windows which also did nothing.
    These forum threads ask the same question I am now asking:
    http://forums.nvidia.com/index.php?showtopic=109833
    http://vip.asus.com/forum/view.aspx?SLanguage=en-us&id=20091113065624625&board_id=14&model=CG5270&page=2&count=17
    I am currently posting this in safe mode, very frustrated too. Help would be greatly appreciated, I have no where else to find answers :S

    Quote from: ZSDE on 14-January-10, 23:31:55
    I did some more research on the net and it seems this PSU is labelled under many different names. I found a Portuguese site that did the test for this unit and then used the google translator tool.
    refer to http://www.clubedohardware.com.br/artigos/1818/1
    Some translated extracts:
    The Coletek is a national brand aimed at the OEM market, or its source is aimed at companies that assemble PCs They have a separate brand for products geared to the retail market, the C3Tech. Today we test the model LC-8460BTX S (which, despite its name, is an ATX and not a BTX) that is sold as a source of 450 W. Really?.....
    ....Speaking of curiosity, in Figure 7 you can see the marking of the type of fuse in the circuit board of the source. All sources bring this information. But the curious thing here is that the marking indicates that for a source from 150 to 200 W a 5 A fuse should be used and to a source from 230 to 300 W from a 6.3 A fuse should be used. As this power supply uses a fuse of 6.3 A, we have a source between 230 and 300 W, according to their own existing markup on the printed circuit board thereof. As the manufacturer can turn that into 450 W on the label of the source is a magic that Mr. M can not explain.....
    ....The Coletek LC-S 8460BTX burned when trying to draw about 225 W (which would be our test number seven). So the most you can pull it was about 190 W (which would be our test of 200 W). More information and video on the next page.
    So I recommend that you perhaps translate the whole article to get the full results. In your case, I believe the PSU should be the first place where you should try something a bit more realistic before you do anything else.
    Quote from: Henry on 15-January-10, 08:09:28
    For a system with a 220 installed PSU with +12V~30A minimum is recommended. My recommendation is to get nothing less than a quality PSU such as a Corsair VX450W +12V~33A. That junk PSU is typical of the worthless ones that are often provided by case manufacturers and examples of similar units that can be purchased for as little as $10 (USD) on eBay.
    Thank-you so much guys, you've most likely have just diagnosed and gave me a solution for my problem
    At first I never knew all PSU's were different, and that my new graphics card could handle whatever I had in my system at the moment.
    I don't think I will bother checking my PSU if my current PSU is a Okia or a Xion, I may as well upgrade the thing anyway
    Just some things I need cleared up though:
    Firstly, is it the Corsair VX450W that I would want to buy and install to run my card? Is it affordable?
    And secondly, are PSU's hard to install/upgrade? Where can I find a guide/tutorial for this kind of thing?

  • Verify Disk results, confusing.. Can they be the cause of system lock ups?

    I have been experiencing strange freezes on my Mac Pro 2008 system.
    My boot disk is a 50% full 128GB SSD from Crucial and is running beautifully fast however for the past couple of weeks my system often freezes for anything from 3 seconds to 30 seconds and then the Finder restarts.
    After the Finder restarts everything continues running smoothly. As if nothing ever happend, no error reports, no apps crashed, nothing.
    I have verified disk permissions and verified the disk itself in Disk Utility but I am not quite sure what these results mean and if they could be the cause of these random lock ups.
    here are the results:
    Verify permissions for “Boot Disk”
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    Group differs on "private/etc/hostconfig", should be 0, group is 20.
    Permissions verification complete
    Verifying volume “Boot Disk”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Missing thread record (id = 5888152)
    Incorrect number of thread records
    Checking multi-linked files.
    Checking catalog hierarchy.
    Invalid volume directory count
    (It should be 184294 instead of 184295)
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Boot Disk was found corrupt and needs to be repaired.
    Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
    I would really appreciate it if someone that knows their way around this stuff could help me troubleshoot this.
    As for the problem of the system locking up it does not happen in the same application consistently.
    Often it happens in Firefox but it could equally often happen when working in Photoshop, browsing files in the Finder or trying to access the Spotlight search via the keyboard shortcut.
    When the system locks up I get the spinning beach ball and I can still move the mouse and click and even still access CMD+TAB app switcher, switch spaces and all those things, just applications become non responsive.
    If you need any more details please let me know.
    Thanks for reading,
    Jannis

    These are innocuous errors that you may safely ignore. However the disk error is a problem. Do the following:
    Repairing the Hard Drive
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • Finding the cause of total hardware lock-ups

    The new build has been running reasonably well, and I've done no major optimizing so far, and no overclocking (yet). However, I've been having infrequent and seemingly random system lock-ups that would appear to be hardware related.
    Last night was about the fourth or fifth of these. I had been working on and off throughout the day on a 4-camera multicamera project, and having no issues at all. This was a TOTALLY different multicam experience than I've had with CS4, where MC was hardly usable. Anyway, I was going to make my last few edits of the night when the system locked up--I had just started playing back a sequence when it happened. No hard drive activity, no keyboard/mouse interaction, no bluescreen--the audio that had started playback, however, got caught in a short loop and made an annoying racket. The only way to return to normal was to hard reboot with the power button depressed. No error or fault is logged in the Windows event logs, beyond the reboot which is recorded as something like, "Your system restarted, probably due to you turning it off... don't do that." The actually fault that perpetuates such a drastic action is not recorded. My initial thoughts were that the RAM has a bad chip somewhere, so I've run a memory test for over 8 hours now, and had 0 errors reported. There were no lock-ups, either--the system has been just humming along that whole time. This obviously does not rule out the RAM, but doesn't make it easy to say it's the problem, either. The only "tweak" I've made to the system is the RAM, and that's by setting the DRAM frequency to 1600MHz; nothing else has been altered in the BIOS.
    The last two lock-ups occured in one day, when I was attempting to export to an H.264 file, through the AME queue, with hardware MPE enabled. At different points in the export, the system locked, with similar results as above. After the second lock-up, I disabled GPU acceleration in PPro, and the export completed just fine. Interesting, I thought. However, I'd done other hardware MPE-assisted exports earlier that day and in previous days, with no lock-ups.
    As mentioned, I'd encountered at least one other hard freeze, and if I remember correctly, I was in Premiere but not doing anything. I'd walked away from the system for a little while, came back, and it was Living Dead on my return. I hadn't been rendering, importing, playing back, or anything else.
    I've been checking my temps with HWmonitor, and there isn't anything out of the ordinary as far as I'm aware. I'm really not stressing the system much, pretty basic and rudimentary edits. The memory test has now done about 600% coverage, and no errors. The bizarre coincidence is that these lock-ups occur when I'm in one of the Adobe programs--but I've never seen software cause a lock-up such as this before.
    So... where do I go from here? The lock-ups seem to completely happen at random, with no particular instigation. Is there some sort of other monitor software I can run in the background that might indicate hardware failures that Windows is not able to catch?
    I'm hoping you hardware gurus can shed some light on this bizarre predicament... thanks in advance for your insight.
    ADDENDUM:
    It would seem to make sense to post my hardware... duh:
    ASUS P6X58D
    i7-930
    OCZ  Gold 12GB (6 x 2GB) DDR3 1600 (PC3 12800)
    GIGABYTE GeForce GTX  480
    COOLER MASTER HAF 932
    COOLER MASTER Silent Pro 1000W
    Western  Digital VelociRaptor 150GB (system drive)
    HITACHI 500GB 7200  RPM SATA 3.0Gb/s
    4x SAMSUNG Spinpoint F3 1TB  7200 RPM SATA 3.0Gb/s (running RAID 5 with onboard controller)
    Noctua NH-D14 CPU Cooler

    Well, I really wanted Jeff's suggestion to be the solution, but alas, troubles remain. And it would appear that something far more sinister is happening than flaky codecs or software.
    The good news is that I can now reliably repeat the lock-up, each and every time. The bad news is that the lock-up occurs whenever I attempt an export. I'm trying to get a 75-minute multicamera edit onto a DVD, and the moment the actual encode begins, the system goes into a hard hang. I have a number of audio clips that are being used, and I see "Adobe Premiere Pro is preparing audio for export" or something like that, and then once the video processing begins, it's curtains.
    At first, I thought it was something with the hardware MPE--I'm using a GTX 480 with the hack. Editing works well--remarkably well. Encoding is a different issue, altogether, and it doesnt' matter whether I start the export with the Queue button or the Export button. I tried disabling GPU acceleration, and at first, I thought I had solved the mystery--the encode actually began and progressed for about 30 seconds. However, inevitably it would seem, I got the same hard hang.
    The first couple "hangs" were actually system restarts; the Windows desktop would disappear, and moments later, I was back at POST. I then disabled the "Automatically restart" option in Windows, and after doing that, I simply ended up with a frozen system and desktop. I'm not sure those are coincidental, actually; I'm going to test that again this morning to see if I get the restart or the hang.
    I've been checking out my temperatures with HWMonitor, and as far as I can tell, I'm not going off the charts with temperatures. Temperatures do climb (I have HWMonitor as I start the encode) for both the CPU cores and GPU, but nothing drastic, and there is no way that it's getting too hot in the 5 seconds that the encode is running before the hang. What about the power supply? I can see wattages for the CPU fluctuating drastically as the encode tries to begin, which I would gather is SOP for the operation of a computer, but is it possible that I am getting too much/too little juice? I've got a 1000W Cooler Master PSU, the components you see listed above, and 6 hard drives--this would seem to be more than sufficient to me (for my current use), but undoubtedly, the system is pulling more watts as it starts to work harder. Unfortunately, there is nothing I can really disconnect to test this theory, since I need all of the components and hard drives connected to do anything.
    I'm at a total loss, guys, and I'm more than a little frustrated because I've got a pretty expensive paperweight sitting in my office. Unfortunately, I live in a pretty rural area, so finding a trustworthy computer tech locally is a challenge, so I'm hoping that you tech-savvy folks can through out some places to look.
    Help me, Obi-Wan Kenobi... you're my only hope...
    Thanks, all...

  • Multiple Panics, Lock Ups and Freezes

    My MacBook Pro running 10.8.3 has been having some random shut downs and lock ups lately, the latest of which took the internal boot drive totally offline. I was able to recover it after booting to my external recovery drive and running DiskWarrior 4 as Disk Utility simply said I needed to repair the drive before mounting it, but then said it was unrepairable after attempting to do so.
    After the DiskWarrior repair, the Mac booted from it's internal drive like there was nothing wrong, but an hour or so later, I had another lock up where everything froze up and was unresponsive and then after a restart I got another hour or so before it shut itself down and then restarted itself, so I'm obviously less than thrilled with the situation.
    This is the factory drive which came with the MacBook Pro when purchased new in January of this year, so I have a hard time believing the drive is physically bad, though I guess anything is possible. Another thing that has me thinking it's not the hardware is that the machine runs fine when booted to the external recovery drive and has no errors or any of the symptoms I've been experiencing.
    Anyway, I've been looking at the panic reports, but I'm honestly not well versed in what any of this means, so I'm hoping one of the experts can chime in and maybe point me in the right direction as I'm running out of ideas :/
    Interval Since Last Panic Report:  2467 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    BBC20339-6AE8-82EA-4368-DCBBCC912FF4
    Anonymous UUID:                    BBC20339-6AE8-82EA-4368-DCBBCC912FF4
    Thu May  2 13:44:42 2013
    panic(cpu 6 caller 0xffffff8025cb7e95): Kernel trap at 0xffffff7fa741c064, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x0000000000000010, CR3: 0x00000000443ae021, CR4: 0x00000000001606e0
    RAX: 0x0000000000000001, RBX: 0xffffff81c60a6000, RCX: 0xffffff8048c44000, RDX: 0xffffff81f7773a38
    RSP: 0xffffff81f7773b60, RBP: 0xffffff81f7773b60, RSI: 0x0000000000000000, RDI: 0x0000000000000000
    R8:  0x0000000000000000, R9:  0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
    R12: 0xffffff81c60a6000, R13: 0x0000000000000000, R14: 0x0000000000000002, R15: 0x0000000000000000
    RFL: 0x0000000000010246, RIP: 0xffffff7fa741c064, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x6
    Backtrace (CPU 6), Frame : Return Address
    0xffffff81f7773800 : 0xffffff8025c1d626
    0xffffff81f7773870 : 0xffffff8025cb7e95
    0xffffff81f7773a40 : 0xffffff8025ccd4dd
    0xffffff81f7773a60 : 0xffffff7fa741c064
    0xffffff81f7773b60 : 0xffffff7fa7405d64
    0xffffff81f7773bb0 : 0xffffff7fa7405cba
    0xffffff81f7773bd0 : 0xffffff7fa73e17ae
    0xffffff81f7773c00 : 0xffffff7fa62b03a0
    0xffffff81f7773c40 : 0xffffff7fa62b030f
    0xffffff81f7773c60 : 0xffffff7fa62b575c
    0xffffff81f7773cf0 : 0xffffff7fa62ade50
    0xffffff81f7773d20 : 0xffffff7fa62feb8b
    0xffffff81f7773d70 : 0xffffff8026032e7b
    0xffffff81f7773dc0 : 0xffffff80260634f7
    0xffffff81f7773e30 : 0xffffff8025c97fef
    0xffffff81f7773e80 : 0xffffff8025c20aed
    0xffffff81f7773eb0 : 0xffffff8025c10448
    0xffffff81f7773f00 : 0xffffff8025c1961b
    0xffffff81f7773f70 : 0xffffff8025ca5dd6
    0xffffff81f7773fb0 : 0xffffff8025ccdd43
          Kernel Extensions in backtrace:
             com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000->0xffffff7fa62dbfff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
             com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa62fb 000->0xffffff7fa6608fff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa62e7000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000
             com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7fa73de000 ->0xffffff7fa74aafff
                dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa62 fb000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa62e7000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    12D78
    Kernel version:
    Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
    Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
    Kernel slide:     0x0000000025a00000
    Kernel text base: 0xffffff8025c00000
    System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)
    System uptime in nanoseconds: 187720354206
    last loaded kext at 185678984299: com.apple.driver.AudioAUUC          1.60 (addr 0xffffff7fa768f000, size 32768)
    loaded kexts:
    com.kaspersky.nke          1.0.1d41
    com.kaspersky.kext.klif          3.0.0d23
    com.apple.driver.AudioAUUC          1.60
    com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AGPM          100.12.87
    com.apple.driver.ApplePlatformEnabler          2.0.6d1
    com.apple.driver.X86PlatformShim          1.0.0
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AppleHDAHardwareConfigDriver          2.3.7fc4
    com.apple.driver.AppleHDA          2.3.7fc4
    com.apple.GeForce          8.1.0
    com.apple.iokit.IOBluetoothUSBDFU          4.1.3f3
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.driver.AppleMikeyDriver          2.3.7fc4
    com.apple.nvidia.NVDAStartup          8.1.0
    com.apple.driver.SMCMotionSensor          3.0.3d1
    com.apple.driver.AppleSMCLMU          2.0.3d0
    com.apple.driver.AppleIntelHD4000Graphics          8.1.0
    com.apple.driver.AppleIntelFramebufferCapri          8.1.0
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.3.0
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleMuxControl          3.3.0
    com.apple.driver.AppleBacklight          170.2.5
    com.apple.driver.AppleMCCSControl          1.1.11
    com.apple.driver.AppleUSBTCButtons          237.1
    com.apple.driver.AppleIRController          320.15
    com.apple.driver.AppleUSBTCKeyEventDriver          237.1
    com.apple.driver.AppleUSBTCKeyboard          237.1
    com.apple.driver.AppleFileSystemDriver          3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.iokit.SCSITaskUserClient          3.5.5
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.3.1
    com.apple.driver.AppleUSBHub          5.5.5
    com.apple.driver.AppleSDXC          1.4.0
    com.apple.iokit.AppleBCM5701Ethernet          3.6.0b1
    com.apple.driver.AirPort.Brcm4331          614.20.16
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.driver.AppleAHCIPort          2.5.1
    com.apple.driver.AppleUSBEHCI          5.5.0
    com.apple.driver.AppleUSBXHCI          5.5.5
    com.apple.driver.AppleEFINVRAM          1.7
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleACPIButtons          1.7
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.7
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.kext.triggers          1.0
    com.apple.driver.DspFuncLib          2.3.7fc4
    com.apple.iokit.IOAudioFamily          1.8.9fc11
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.nvidia.gk100hal          8.1.0
    com.apple.NVDAResman          8.1.0
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.driver.AppleThunderboltEDMSink          1.1.8
    com.apple.driver.AppleThunderboltEDMSource          1.1.8
    com.apple.driver.AppleThunderboltDPOutAdapter          1.8.9
    com.apple.driver.X86PlatformPlugin          1.0.0
    com.apple.driver.AppleHDAController          2.3.7fc4
    com.apple.iokit.IOHDAFamily          2.3.7fc4
    com.apple.iokit.IOAcceleratorFamily          30.14
    com.apple.iokit.IOSurface          86.0.4
    com.apple.iokit.IOBluetoothFamily          4.1.3f3
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.IOPlatformPluginFamily          5.3.0d51
    com.apple.driver.AppleSMBusPCI          1.0.11d0
    com.apple.driver.AppleGraphicsControl          3.3.0
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.iokit.IONDRVSupport          2.3.7
    com.apple.driver.AppleSMBusController          1.0.11d0
    com.apple.iokit.IOGraphicsFamily          2.3.7
    com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
    com.apple.driver.AppleUSBMultitouch          237.3
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.driver.AppleUSBMergeNub          5.5.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.5
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
    com.apple.driver.AppleThunderboltNHI          1.6.3
    com.apple.iokit.IOThunderboltFamily          2.2.6
    com.apple.iokit.IOUSBUserClient          5.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IO80211Family          522.4
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOAHCIFamily          2.3.1
    com.apple.iokit.IOUSBFamily          5.5.5
    com.apple.driver.AppleEFIRuntime          1.7
    com.apple.iokit.IOHIDFamily          1.8.1
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220.2
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          345
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.7
    com.apple.iokit.IOPCIFamily          2.7.3
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    System Profile:
    Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f173
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.16)
    Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Serial ATA Device: APPLE HDD TOSHIBA MK7559GSXF, 750.16 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS31N
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 6
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 8
    Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f173
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.16)
    Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Serial ATA Device: APPLE HDD TOSHIBA MK7559GSXF, 750.16 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS31N
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 6
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 8

    1. This comment applies to malicious software ("malware") that's installed unwittingly by the victim of a network attack. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
    OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.
    2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user, but internally Apple calls it "XProtect." The malware recognition database is automatically checked for updates once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
    The following caveats apply to XProtect:
    It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
    It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
    3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
    Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
    It can easily be disabled or overridden by the user.
    A malware attacker could get control of a code-signing certificate under false pretenses, or could find some other way to bypass Apple's oversight, or the oversight could fail in a particular case due to human error.
    For most purposes, applications recognized by Gatekeeper as signed, including App Store products, can be considered safe. Note, however, that at least one trojan for iOS (not for OS X) was briefly distributed by a developer in Russia through the iTunes App Store. That store is under the same oversight by Apple as the Mac App Store, so the protection shouldn't be considered absolute. App Store products may prompt for access to private data, such as your contacts. Think before granting that access. OS X security is based on user input. Never click anything reflexively.
    4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is presumably effective against known attacks, but maybe not against unknown attacks. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
    5. Beyond XProtect, Gatekeeper, and MRT, there’s no evidence of any benefit from other automated protection against malware. The first and best line of defense is always your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
    That means, in practice, that you never use software that comes from an untrustworthy source, or that does something inherently untrustworthy. How do you know what is trustworthy?
    Any website that prompts you to install a “codec,” “plug-in,” "player," "extractor," or “certificate” that comes from that same site, or an unknown one, is untrustworthy.
    A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
    Pirated copies or "cracks" of commercial software, no matter where they come from, are unsafe.
    Software of any kind downloaded from a BitTorrent or from a Usenet binary newsgroup is unsafe.
    Software that purports to help you do something that's illegal or that infringes copyright, such as saving streamed audio or video for reuse without permission, is unsafe. All YouTube "downloaders" are in this category, though not all are necessarily harmful.
    Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. If it comes from any other source, it's unsafe.
    Even signed applications should not be trusted if they do something unexpected, such as asking for permission to access your contacts or your location for no apparent reason.
    6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
    Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
    Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it — not JavaScript — in your browsers.
    Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.
    Follow the above guidelines, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself from malware.
    7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. If you need to be able to detect Windows malware in your files, use the free software  ClamXav — nothing else.
    Why shouldn't you use commercial "anti-virus" products?
    Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
    In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
    By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
    8. ClamXav doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
    ClamXav is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
    A Windows malware attachment in email is usually easy to recognize. The file name will often be targeted at people who aren't very bright; for example:
    ♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
    ClamXav may be able to tell you which particular virus or trojan it is, but do you care? In practice, there's seldom a reason to use ClamXav unless a network administrator requires you to run an anti-virus application.
    9. The greatest harm done by security software, in my opinion, is in its effect on human behavior. It does little or nothing to protect people from emerging threats, but if they get a false sense of security from it, they may feel free to do things that expose them to higher risk. Nothing can lessen the need for safe computing practices.
    10. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.

  • Pages '08 lock ups

    A couple months ago, I started having issues with Pages '08. It would lock up while I was typing, or even something as simple as scrolling the page down. All I would get was the little rainbow wheel and a locked up document. At first I thought it was just the one file I was working on, but now it happens all the time. It locks up so bad sometimes that it forces a restart of the computer. No other programs are having this issue. Should i just reinstall Pages '08 from the disc or what. Cause this has made my main wordprocessing program completely useless. I'm on Mac OSX 10.5.8

    Update:
    Well I think I got it figured out. For some reason, the spell checker was causing the problem. I've always had it set to "Check spelling as you type", but for some reason that is now causing Pages to lock up. So my work around is to simply turn off the "Check Spelling as you type" option, and now there are no more lock ups.

  • Total lock-ups with fan running - translate system.log file please!?

    Hi, all. My late 2005 2.3 gig dual G5 has been experiencing random lock ups for as long as I can remember. My system is up to date and I have tested each pair of the 5 gigs of ram that I have and the system freezes with each pair. It can happen at any time, when I am doing absolutely nothing, for example, overnight. I am at my wits end!
    Here's the system log file for the latest freezes. Can anyone tell me what's going on here??? I really need to get to the root of this problem. Thanks so so much in advance.
    Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_Reconnect: connect on /Volumes/Macintosh HD failed 89.
    Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Macintosh HD, flags 524288, pid 62
    Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: Started\n
    Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: This service performs licensing functions on behalf of FLEXnet enabled products.\n
    Apr 12 18:01:06 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 18:01:49 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 18:08:29 Marc-Weinbergs-Computer diskarbitrationd[69]: SDCopy [1056]:36091 not responding.
    Apr 12 18:16:18 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 18:16:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 19:24:12 Marc-Weinbergs-Computer ntpd[191]: time reset -0.650307 s
    Apr 13 01:05:45 Marc-Weinbergs-Computer ntpd[191]: time reset -0.496917 s
    Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
    Apr 13 07:15:03 Marc-Weinbergs-Computer postfix/postqueue[1778]: warning: Mail system is down -- accessing queue directly
    Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
    Apr 13 15:53:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 13 15:53:54 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 13 22:15:48 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Apr 13 22:15:47 localhost mDNSResponder-108.6 (Jul 19 2007 11: 33:32)[63]: starting
    Apr 13 22:15:48 localhost kernel[0]: vmpagebootstrap: 506550 free pages
    Apr 13 22:15:47 localhost memberd[70]: memberd starting up
    Apr 13 22:15:49 localhost kernel[0]: migtable_maxdispl = 70
    Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.FTATASil3132E" from archive.
    Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.Sil3112DeviceNub" from archive.
    Apr 13 22:15:49 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Apr 13 22:15:49 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Apr 13 22:15:49 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
    Apr 13 22:15:49 localhost kernel[0]: AppleKauaiATA shasta-ata features enabled
    Apr 13 22:15:49 localhost kernel[0]: DART enabled
    Apr 13 22:15:47 localhost DirectoryService[75]: Launched version 2.1 (v353.6)
    Apr 13 22:15:49 localhost kernel[0]: FireWire (OHCI) Apple ID 52 built-in now active, GUID 001451ff fe1b4c7e; max speed s800.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:48 localhost lookupd[71]: lookupd (version 369.5) starting - Sun Apr 13 22:15:48 2008
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: Extension "com.microsoft.driver.MicrosoftKeyboardUSB" has no kernel dependency.
    Apr 13 22:15:49 localhost kernel[0]: AppleSMUparent::clientNotifyData nobody registed for 0x40
    Apr 13 22:15:49 localhost kernel[0]: Security auditing service present
    Apr 13 22:15:49 localhost kernel[0]: BSM auditing present
    Apr 13 22:15:49 localhost kernel[0]: disabled
    Apr 13 22:15:49 localhost kernel[0]: rooting via boot-uuid from /chosen: 82827EDF-0263-3B93-BEED-4B114E820B85
    Apr 13 22:15:49 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Apr 13 22:15:49 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@9/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@0/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/ST3320620AS Media/IOApplePartitionScheme/AppleHFS_Untitled1@10
    Apr 13 22:15:49 localhost kernel[0]: BSD root: disk0s10, major 14, minor 12
    Apr 13 22:15:49 localhost kernel[0]: jnl: replay_journal: from: 8451584 to: 11420160 (joffset 0x952000)
    Apr 13 22:15:50 localhost kernel[0]: AppleSMU -- shutdown cause = 3
    Apr 13 22:15:50 localhost kernel[0]: AppleSMU::PMU vers = 0x000d00a0, SPU vers = 0x67, SDB vers = 0x01,
    Apr 13 22:15:50 localhost kernel[0]: HFS: Removed 8 orphaned unlinked files
    Apr 13 22:15:50 localhost kernel[0]: Jettisoning kernel linker.
    Apr 13 22:15:50 localhost kernel[0]: Resetting IOCatalogue.
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 3
    Apr 13 22:15:50 localhost kernel[0]: NVDANV40HAL loaded and registered.
    Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::start 1
    Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::end 1
    Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - entry
    Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - calling adjust
    Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::adjustThermalProfile start
    Apr 13 22:15:50 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
    Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:78
    Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:79
    Apr 13 22:15:51 localhost lookupd[86]: lookupd (version 369.5) starting - Sun Apr 13 22:15:51 2008
    Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 21611008 to: 7857152 (joffset 0x952000)
    Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 673280 to: 24382976 (joffset 0x952000)
    Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 3890176 to: 6294016 (joffset 0x7d01000)
    Apr 13 22:15:51 localhost diskarbitrationd[69]: disk0s10 hfs 82827EDF-0263-3B93-BEED-4B114E820B85 NewestSeagate /
    Apr 13 22:15:52 localhost kernel[0]: NVDA,Display-A: vram [90020000:10000000]
    Apr 13 22:15:52 localhost mDNSResponder: Adding browse domain local.
    Apr 13 22:15:53 localhost kernel[0]: hfs mount: enabling extended security on Maxtor
    Apr 13 22:15:53 localhost diskarbitrationd[69]: disk1s3 hfs 0DBE2113-B1F5-388F-BF70-2E366A095330 Maxtor /Volumes/Maxtor
    Apr 13 22:15:54 localhost kernel[0]: NVDA,Display-B: vram [94000000:08000000]
    Apr 13 22:15:54 Marc-Weinbergs-Computer configd[67]: setting hostname to "Marc-Weinbergs-Computer.local"
    Apr 13 22:15:54 Marc-Weinbergs-Computer /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
    Apr 13 22:15:56 Marc-Weinbergs-Computer diskarbitrationd[69]: disk2s3 hfs 971CABB3-C211-38FC-8E91-6B4F8EA5FA20 B08-09-07 /Volumes/B08-09-07
    Apr 13 22:15:56 Marc-Weinbergs-Computer loginwindow[110]: Login Window Started Security Agent
    Apr 13 22:15:57 Marc-Weinbergs-Computer kernel[0]: AppleBCM5701Ethernet - en1 link active, 1000-Mbit, full duplex, symmetric flow control enabled
    Apr 13 22:15:57 Marc-Weinbergs-Computer configd[67]: AppleTalk startup
    Apr 13 22:15:57 Marc-Weinbergs-Computer TabletDriver[119]: #### GetFrontProcess failed to get front process (-600)
    Apr 13 22:15:59 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
    Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
    Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
    Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
    Apr 13 22:16:01 Marc-Weinbergs-Computer lookupd[123]: lookupd (version 369.5) starting - Sun Apr 13 22:16:01 2008
    Apr 13 22:16:01 Marc-Weinbergs-Computer kernel[0]: HFS: Removed 2 orphaned unlinked files
    Apr 13 22:16:01 Marc-Weinbergs-Computer diskarbitrationd[69]: disk3s3 hfs CDA8BCC5-0CE4-33E8-A910-4B0952DBC230 FullBU-09-07 /Volumes/FullBU-09-07
    Apr 13 22:16:04 Marc-Weinbergs-Computer configd[67]: target=enable-network: disabled
    Apr 13 22:16:05 Marc-Weinbergs-Computer configd[67]: AppleTalk startup complete
    Apr 13 22:16:09 Marc-Weinbergs-Computer TabletDriver[237]: #### GetFrontProcess failed to get front process (-600)
    Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: exited with exit code: 253
    Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: 9 more failures without living at least 60 seconds will cause job removal
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0L6LR', reports it is functioning at a temperature of 95.0F (35C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0L6LR', appear to still be available. (Total Available: 36) (Use Attempts: 0)
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0LGS4', reports it is functioning at a temperature of 100.4F (38C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0LGS4', appear to still be available. (Total Available: 36) (Use Attempts: 0)
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '9RV000FC', reports it is functioning at a temperature of 95.0F (35C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '9RV000FC', appear to still be available. (Total Available: 36) (Use Attempts: 0)
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', reports it is functioning at a temperature of 89.6F (32C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', appear to still be available. (Total Available: 63) (Use Attempts: 0)
    Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
    Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
    etc.

    Hi-
    The machine seems to be having trouble with loading certain drivers, but, as this isn't a crash log, and doesn't show the "hang-up" or freeze, it's hard to tell.
    Noted possibilities are:
    -Microsoft keyboard (possible USB power problem)
    -firmtek driver (from archive) questionable due to the "archive" annotation
    -Wacom tablet driver, causing system problems
    Running in Safe mode without freezes would help to determine if one of these drivers is the problem.
    Other possibilities are outdated drivers, or simply a need to reinstall the OS.
    If unnecessary, removing the driver(s) would be a good idea.
    External USB and Firewire devices are all suspect, should all be disconnected, revert to Apple keyboard, and test system performance. Adding one device at a time, and testing each will be necessary to clear each device.
    I have experienced system trouble when a Wacom tablet was not connected, but the driver was left installed.
    Disabling the driver from Startup items may be necessary to test without the Wacom tablet connected.

  • System lock-ups after upgrading to Tiger

    This topic was previously posted in 'Installation & Setup'.
    After 3 days (and 18 views) I got no replies.
    Maybe that forum was not appropriate, so I decided to try it in this forum.
    About 4 months ago I exchanged my 80 GB Hd in favor of an 200 GB Maxtor 6L200P0. One day later I upgraded OS X 10.3.9 to Tiger (retail DVD).
    At that time I experienced a frequent (several times a day) lock-up of my system.
    No messages, nothing, not even after powering down and restarting.
    After some time I figured out that the lock-ups occurred on Internet access. Clicking on a link in Safari, posting messages on Discussions. Even Mail locked the system a few times. Also Corripio (artwork and lyrics finder for iTunes) caused the system to lock.
    After that, I decided to perform an Archive & Install (first time after almost 4 years of using this Mac). Except from having to re-install a number of 3rd party apps. the system seemed to perform well. No lock-ups were experienced for a few weeks.
    Problem solved, I thought.
    Although far less frequent than before, I do experience those annoying lock-ups a few times a week.
    Here are my questions:
    What could be the cause of the lock-up?
    Is is advisable to perform a Clean Install? What advantage do I have of, it opposite to performing an A&I. I'm reluctant to perform a clean install at the moment, because I haven't found a few serials of commercial and shareware applications yet ( I know, I should have written them down :-/ )
    Any hints/tips to track down the exact cause?
    TIA
    M
    P.S. ( I do have a bootable complete backup of my HD on an Maxtor Onetouch II )

    Hi, M.
    1. You wrote: "What could be the cause of the lock-up?"The number of potential causes range from disk corruption or bad applications to serious hardware problems, such as a defective logic board.
    2. You wrote: "Any hints/tips to track down the exact cause?"I suggest treating the "lock up" problem — better described as a "freezes and hangs" problem — similar to a kernel panic as the basic troubleshooting and hardware testing steps are virtually the same. See my "Resolving Kernel Panics" FAQ.
    It provides a comprehensive roadmap which you should follow from beginning to end, in the order specified in the FAQ.
    2. You wrote: "Is is advisable to perform a Clean Install? What advantage do I have of, it opposite to performing an A&I."The term "Clean Install" does not apply in Mac OS X. That is obsolete Mac OS 9 terminology. The closest Mac OS X equivalent to a "Clean Install" is an Archive and Install with the Preserve User and Network Settings option, which it sounds like you've already tried once previously, but you may want to try again as part of the troubleshooting process I outlined above. See my "General advice on performing an Archive and Install" FAQ for some important tips on this process.
    The other options are:
    • Archive and Install without the Preserve User and Network Settings option: This reinstalls the OS and wipes out both your accounts and your network configuration, but preserves the previous System folder.
    • Erase and Install: Erases the hard drive, i.e. Macintosh HD, and reinstalls the OS from scratch, preserving nothing: your accounts, network settings, and everything else on the drive are deleted.
    Of those two, and since you have a bootable backup, the second (Erase and Install) would be the second-to-last thing you would try, the last being taking the machine in for service.
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X
    Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • P7N SLI Platinum lock-ups

    My specs:
    Q6600 stock speed
    Kingston HyperX pc8500 2x 1gb. I manually set it to it's rated timings, voltage and frequency. I have also tried different ram, from Exceleram and it makes no difference.
    2x Asus EN8800GT 512mb cards (tried using just one card too, tried switching to a different 8800gt card from sparkle too, no change.)
    HDD: Have tried several hard drives, pata and sata from probably all the manufacturers, i dont see why i need to post their specs since they problem persists nomatter what hdd i use.
    Windows XP SP3 proffessional.
    nothing else is in the system, i removed every piece of hardware, like sound card, optical drive, etc. to isolate the problem.
    Power supply: Thermaltake ToughPower 700W
    BIOS Version: the beta bios posted on this forum that supposedly fixes the video corruption bug (it doesnt). Also tried 1.0 and 1.1
    The problem:  random lock-ups. Sometimes it doesnt happen for 2 days and then BAM! Its happening every 15 minutes now. It might stop happening for another 12 hours and start locking up again. It only ever happens when im working in 2d applications like browsing, using messenger or IRC, watching videos on youtube or in a media player, or just moving files around or anything mundane like that.  it once happened when i wasnt touching the keyboard or mouse at all, i was waiting for some files to finish copying over LAN.  I also get the famous video corruption but it is EXTREMELY rare, like once a month.  It crashed the last time the video corruption appeared, once i tried to click the player to pause, the system crashed.  The system will never lock up while playing games, i play medieval II total war for days without any problems.  The store i bought the p7n from tested it for me and they said it worked fine, but they used an ATI card so that may be a clue?  Then again, they are really incompetent and didnt run the right set of tests, and ignored what i had told them about the nature of the crashes.
    Detailed description of the events:  System freezes, first everything except the mouse is frozen but if i try to click with the mouse, it freezes too and the screen flashes a black screen every few seconds.  it never recovers and i have to shut it down by holding the power button for several seconds.  some of the 2d graphics in windows get corrupted with artifacts, and the mouse does get heavily corrupted usually.
    What i've tried:
    I thought the mobo was defective but it isnt, i got a new mobo from the store and it has the same problem. 
    Tried working my way through every combination of memory timings, frequencies and voltages that i thought might make a difference but it has no difference on the crashes.
    All the hardware works perfectly in my Asus P5N32-E SLI motherboard (i bought this msi mobo for some different reasons that i wont go into here), so theres nothing wrong with any of my components.
    The only item i've not had the oportunity to switch with a different one is the power supply, but again, it works perfectly with all other motherboards that i've tried.
    Is this possibly related to the video corruption bug?  Does anyone have any idea when the next bios release is due? Please help, it sucks to buy an expensive motherboard that just doesnt work. i'll have to buy a 3rd sli mobo if I cant fix this.
    PS:  Is it not possible to regulate fan speed for sysfans connected to the mobo's fan connectors? My asus mobo had great fan speed controls in the bios, if this one doesnt have any such options, i call that ridiculous.

    I appreciate your effort, guys. I've tried running the memory in 800mhz and on auto timings and on some other timings too (i was kinda desperate and i messed around with the memory configuration for days with no success), and tried auto volt (it gets set to 1.8 which the memory is rated for at 800mhz) and tried 1.9 and 2.0 and 2.1 and 2.2 and i've tried completely different memory modules too that i borrowed, and tried running in single channel with both modules and running just 1 module.  none of these experiments had any effect on the crashes :\.  But don't you think this could be related to the video corruption bug? I always thought it was, since this problem doesnt seem to happen for me when there is an ATI card in the system.  Not that my 8800gt cards are defective in any way either, they are rock solid on my other motherboard. 
    I have one more theory, some weird inexplicable compatibility problem between this particular PSU and this particular mobo. Think it's a possibility? The psu is the only thing i have not switched out for another component, every other component i have switched for another one that was known to be working fine.
    also, there is the extremely distant possibility that the issue is caused by an issue that the mobo might have with BOTH the kingston and the excelleram modules that i tried, however this seems far-fetched. but this problem is a fact and SOMETHING is causing it. i've eliminated almost everything i can think of.

Maybe you are looking for