System Locks up with PCI64 downl

Re-formatted my HD. Uploaded windows 98se plus display drivers and video card driver. As soon as I start to load PCI64 software (from Cd or download), computer locks up. No keyboard or mouse actions. Have to reboot in Safe mode to get anything, but can not see how to disable whatever is locking system up. Booting back in Normal mode - system remains locked. Am not able to use sound card as I am fed up with re-formatting dri've.
HELP
MikH

This is a very old barebones, unfortunately memory support is described as "up to 2GB" and as 1GB sticks weren't commonplace at the time, its possible it might just not work.
1GB should be plenty enough for what this system can handle though.
Have you tried testing the sticks with >>Memtest86<<?

Similar Messages

  • Hermes 650 system locks up with 2GB RAM, 1GB OK

    I have a Hermes 650 system that keeps locking up when system is upgraded to 2GB RAM.  System runs fine with 1GB RAM installed.  I tried 2 different brands of 1GB sticks, but same problem.

    This is a very old barebones, unfortunately memory support is described as "up to 2GB" and as 1GB sticks weren't commonplace at the time, its possible it might just not work.
    1GB should be plenty enough for what this system can handle though.
    Have you tried testing the sticks with >>Memtest86<<?

  • Z68A-G45(B3) System locked up and screen artifact w/ IGP

    CPU: Intel Core i5-2500K (stock)
    Mobo: MSI Z68A-G45(B3) ATX
    RAM: 2X2GB Mushkin Silverline DDR3 PC3-10666 @ 1.5V (stock)
    Video: Intel HD Graphics 3000 (IGP) connected via DVI
    HDD: WD WD4000AAKS 400GB SATA3
    DVD: Sony Optiarc AD-7240S 24X
    PSU: Corsair CMPSU-430CX 430W
    Other: 1 120mm fan and 1 140mm fan
    OS: Windows XP SP3 32bit
    New system build, no OC attempt at all
    Problem:
    System can lock up at random time, even during startup or in BIOS screen.  It accompanied by screen with artifact. (will show pic)
    Testing done:
    Clearing CMOS thru Clear CMOS button, as well as taking out the CMOS batteries out for a minute
    Check voltage in BIOS and they looked fine
    Changing BIOS setting from (Integrated Graphic Adapter) PEG to IGD
    Reseating the CPU, even though the CPU never hit above 37 degree at BIOS screen
    Tested individual RAM module in each slot
    Ran Memory-Z and passed the test;  Didn't tried Memtest86+ because I doubt the system will last the entire run
    Tried replacing the PSU with an Antec Basiq 430W
    Unplugging everything and leaving only the CPU, CPU fan, 1 module of RAM, and HDD
    Observation:
    When system locked up with the artifact on screen, the mouse is dimly lighted and flickered when it's clicked.
    All 4 CPU Phase LEDs lit up, but the three on the right are dimmer than the one on the left and it appears that they are flickering.
    Screen with artifact with vertical and horizontal line
    CPU Phase LEDs where one is bright while the other 3 are dim
    Is the mobo the problem?  I doubt this system will use more than 300W peak without a discrete GPU and no OCing.  Appreciate all the help I can get.  Thanks.

    Quote from: Henry on 06-October-11, 10:12:40
    Re-seat the CPU and check the CPU socket for bent/damaged pins.
     That Corsair PSU should be more than good enough for your rig.
    I re-seated the CPU and checked the socket, no bent/damaged pins.
    Quote from: NovJoe on 06-October-11, 11:18:30
    If resitting the CPU and checking the CPU socket still returns same results, I suggest you test your processor in another board and see if the same artifacts came up.
    Wish I have a spare board to rule one or the other out, but I don't have one.  Is there any other test I can do?  Can putting a discrete card in the system rule out anything?

  • Machine locks up with spinning colored ball while in finder

    Frequently, while doing searches through my photos with Finder and trying to copy a photo from one folder to another the system locks up with the spinning colored ball. How do I kill the action(on my PC it was Control Alt Delete).
    My system is MacBook Pro (Retina, 15-inch, Mid 2014 16 GB)

    4/16/15 9:29:20.870 AM sandboxd[422]: () QuickLookSatelli(852) deny file-issue-extension /Users/richardbost/Library/Caches/com.apple.quicklook.satellite
    4/16/15 9:29:20.875 AM QuickLookSatellite[852]: CGSConnectionByID: 0 is not a valid connection ID.
    4/16/15 9:29:20.875 AM QuickLookSatellite[852]: Invalid Connection ID 0
    4/16/15 9:29:20.894 AM sandboxd[422]: () QuickLookSatelli(852) deny mach-lookup com.apple.nsurlstorage-cache
    4/16/15 9:29:20.918 AM sandboxd[422]: () QuickLookSatelli(852) deny file-issue-extension /Users/richardbost/Library/Caches/com.apple.quicklook.satellite
    4/16/15 9:29:20.958 AM sandboxd[422]: () QuickLookSatelli(852) deny mach-lookup com.apple.nsurlstorage-cache
    4/16/15 9:32:48.410 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/16/15 9:33:19.830 AM WindowServer[141]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    4/16/15 9:33:33.372 AM WindowServer[141]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 14.54 seconds (server forcibly re-enabled them after 1.00 seconds)
    4/16/15 9:33:50.244 AM WindowServer[141]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    4/16/15 9:33:56.847 AM WindowServer[141]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 7.60 seconds (server forcibly re-enabled them after 1.00 seconds)
    4/16/15 9:39:07.867 AM storeaccountd[330]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fb970c28a60> connection from pid 365 with interface <AccountServiceInterface: 0x7fb970c024b0> (PID 365)
    4/16/15 9:39:14.716 AM identityservicesd[272]: ====== IDS Traffic Usage:
    4/16/15 9:39:14.716 AM identityservicesd[272]:     Service: com.apple.madrid
    4/16/15 9:39:14.716 AM identityservicesd[272]:       query-requests: 1
    4/16/15 9:39:14.716 AM identityservicesd[272]:
    4/16/15 9:39:14.716 AM identityservicesd[272]:     Service: com.apple.ess
    4/16/15 9:39:14.716 AM identityservicesd[272]:       query-requests: 1
    4/16/15 9:39:14.716 AM identityservicesd[272]:
    4/16/15 9:39:14.716 AM identityservicesd[272]: ====== Done
    4/16/15 9:43:02.539 AM WindowServer[141]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    4/16/15 9:43:16.540 AM WindowServer[141]: disable_update_likely_unbalanced: UI updates still disabled by application "Finder" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
    4/16/15 9:43:47.331 AM WindowServer[141]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 45.79 seconds (server forcibly re-enabled them after 1.00 seconds)
    4/16/15 9:43:47.337 AM Finder[245]: void CGSUpdateManager::log() const: conn 0xff0b: spurious update.
    4/16/15 9:43:53.480 AM WindowServer[141]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    4/16/15 9:44:07.480 AM WindowServer[141]: disable_update_likely_unbalanced: UI updates still disabled by application "Finder" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
    4/16/15 9:44:11.000 AM kernel[0]: process Finder[245] thread 2577 caught burning CPU! It used more than 50% CPU (Actual recent usage: 53%) over 180 seconds. thread lifetime cpu usage 202.831385 seconds, (195.815528 user, 7.015857 system) ledger info: balance: 90007893139 credit: 202687364411 debit: 112679471272 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 168662847166
    4/16/15 9:44:11.557 AM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[864]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
    4/16/15 9:44:11.558 AM ReportCrash[864]: Invoking spindump for pid=245 thread=2577 percent_cpu=53 duration=170 because of excessive cpu utilization
    4/16/15 9:44:11.996 AM spindump[428]: Saved cpu_resource.diag report for Finder version 10.10.4 (10.10.4) to /Library/Logs/DiagnosticReports/Finder_2015-04-16-094411_Richards-MacBook-Pro.c pu_resource.diag
    4/16/15 9:44:58.297 AM WindowServer[141]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 65.82 seconds (server forcibly re-enabled them after 1.00 seconds)
    4/16/15 9:47:30.693 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/16/15 9:47:30.965 AM com.apple.iCloudHelper[868]: objc[868]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
    4/16/15 9:47:30.995 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/16/15 9:47:31.297 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/16/15 9:48:38.276 AM WindowServer[141]: _CGXSetWindowHasKeyAppearance: Operation on a window 0x2c requiring rights kCGSWindowRightOwner by caller Dashboard
    4/16/15 9:48:38.279 AM WindowServer[141]: _CGXSetWindowHasMainAppearance: Operation on a window 0x2c requiring rights kCGSWindowRightOwner by caller Dashboard
    4/16/15 9:50:12.422 AM pkd[270]: enabling pid=303 for plug-in com.apple.ncplugin.stocks(1.0) 20DD9C99-57EC-42CD-8430-700AD6FC9DA0 /System/Library/Frameworks/NotificationCenter.framework/PlugIns/com.apple.ncplu gin.stocks.appex
    4/16/15 9:50:12.423 AM locationd[80]: Couldn't find a requirement string for masquerading client /System/Library/Frameworks/NotificationCenter.framework/PlugIns/com.apple.ncplu gin.weather.appex
    4/16/15 9:50:12.423 AM locationd[80]: could not get apple languages array, assuming english
    4/16/15 9:50:12.423 AM pkd[270]: enabling pid=303 for plug-in com.apple.ncplugin.weather(1.0) B2A83AE6-90A7-4EE1-99A2-2B95BDCB36A6 /System/Library/Frameworks/NotificationCenter.framework/PlugIns/com.apple.ncplu gin.weather.appex
    4/16/15 9:50:12.424 AM pkd[270]: enabling pid=303 for plug-in com.apple.iCal.CalendarNC(1.0) 2B9E7662-5BEA-4F82-AAD3-C677802923A3 /Applications/Calendar.app/Contents/PlugIns/com.apple.iCal.CalendarNC.appex
    4/16/15 9:50:12.449 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/16/15 9:50:12.535 AM locationd[80]: Location icon should now be in state 'Active'
    4/16/15 9:50:12.577 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/16/15 9:50:12.647 AM locationd[80]: Couldn't find a requirement string for masquerading client /System/Library/Frameworks/NotificationCenter.framework/PlugIns/com.apple.ncplu gin.weather.appex
    4/16/15 9:50:12.648 AM locationd[80]: could not get apple languages array, assuming english
    4/16/15 9:50:12.722 AM networkd[170]: -[NETClientConnection scrubParametersForEntitlements:] client com.apple.ncplu.875 setting source application without entitlement
    4/16/15 9:50:13.336 AM networkd[170]: -[NETClientConnection scrubParametersForEntitlements:] client com.apple.ncplu.875 setting source application without entitlement
    4/16/15 9:50:13.336 AM networkd[170]: -[NETClientConnection scrubParametersForEntitlements:] client com.apple.ncplu.875 setting source application without entitlement

  • HT4436 i have a problem with my Macbook Pro. When i tried to open it, something appeared : "enter your system lock PIN code to unlock this Mac". What should i do?

    i have a problem with my Macbook Pro. When i tried to open it, something appeared : "enter your system lock PIN code to unlock this Mac". What should i do?

    Question is did you lock your Mac from Find my iPhone using iCloud or is the Macbook really yours?
    If you have in fact locked your Mac using Find my iPhone on iCloud then you will need to enter the PIN you have set when you locked the Mac.
    *If you have not iniate the remote Lock then someone else has used your Apple ID and Password to lock your mac.
    Message was edited by: Ammadz

  • OVM manager 3.0.3.546 locked up with message "Please wait while system is initializing"

    Hi ,
    I am receiving this message on any actions on OVM manager.
    and AdminServer.log with this message
    ####<Aug 16, 2013 9:26:16 AM EST> <Warning> <com.oracle.ovm.mgr.model.ModelEngine> <serverneame> <AdminServer> <Odof Tcp Client Thread: /127.0.0.1:54321/101> <<anonymous>> <> <0000K24Ij5W5yWNLuIP5iX1I3MCB000002> <1376609176392> <BEA-000000> <Object 'null<500739>' got an unexpected rollback Lifecycle State.DELETING>
    As soon as this message occur the discovery process is stopped and OVM manager lock up with the "Please wait while system is initializing" message.
    any ideal?

    Perform the following procedure to recover the management functionality OVM manager.
    > 1) stop ovmm service
    > # service ovmm stop
    > 2) backup OVM3DB database
    > # ovm_upgrade.sh --export --dbuser=ovs --dbpass=<ovspassword> --dbhost=<db host> --dbport=<db port> --dbsid=<sid/schema>
    > 2) delete the database OVM3DB
    > # ovm_upgrade.sh --deletedb --dbuser=ovs --dbpass=<ovspassword> --dbhost=<db host> --dbport=<db port> --dbsid=<sid/schema>
    > 3) Restart ovmm service
    > # service ovmm start
    > 4) Login into the manager and re-discover your Servers and  Repositories.
    Back to business

  • Odd System Lock-Ups [XP-Pro SP3]

    Something odd is happening, on my normally, and otherwise stable laptop with XP-Pro SP3.
    I have observed that on Fridays, at about 11:30AM MST/USA, I get system lock-ups. Everything just freezes.
    I have poured over Event Viewer, and nothing is getting launched at about that time. Really nothing in System, or Applications, from about boot-up, other than my Browser (Chrome). Not one Warning, or Error, and little real activity.
    I cannot verify that this happens every Friday (do not remember it on Friday Jan. 13, for instance, but then the Adobe Forum Log-in went down), as I am often out of town. However, and based only on memory, this has now happened about 5 - 6 times, and always late in the morning, and on Fridays.
    Normally, I only have my Browser open, though this time also had Windows Explorer minimized. During this AM, I had PrPro, PrE and Photoshop open at times, but none was open, when the lock-up happened.
    I tend to suspect something is trying to update, but it's not showing in Event Viewer. A few times, there was a Norton Live Update Scan, but those were usually hours before. Those are not download/installs, as I have Live Update to full manual, and the same for all other such utilities.
    Does anyone have any ideas, or perhaps a monitoring utility, that will gather data, better than Event Viewer?
    TIA,
    Hunt

    hmm.... google.... i dont really trust google much....
    i used to have something ( i use xp ) that basically I had total control over when to connect to isp etc and disconnect... but for life of me cant remember what it was. that was years ago.
    now when i start computer it automatically ( partially this is due to isp of verizon ) connects and then gives me control of computer ( is part of boot and load process now ).
    your prob seems to be some kinda scheduled thing is why i was thinking maybe turn stuff ' off ' that might be trying to update or something under the radar ( is part of the system more or less.. components ...)
    this area
    you wont see this related stuff in event viewer type listings ... and gets kinda complicated to me at least.

  • System lock ups when using hard disks

    At first I thought I had the same issue as in this thread however after reading his logs I decided that it is unlikely since the topic opener seems to be getting a bunch of
    Apr 4 17:00:15 daxteriv slim[708]: (Do:882): GLib-CRITICAL **: Source ID 46 was not found when attempting to remove it
    , so I decided to start a new thread.
    I am not getting anything in my logs when I look at them after the crashes. It seems as if whatever is causing the issue makes it impossible to write to the drives so nothing seems out of place until after it's too late, and quite obvious that something is wrong. The sole exception to this was some complaint about ata9.00, however this seems to have been a red haring since the complete removal of this drive solved nothing, though it did make the error go away.
    I have run memtest, and prime95 (in windows since at the time I didn't want to boot my system) both coming back negative. I also checked for SMART errors, particularly UDMA errors. Again, negative.
    Here are some previous threads of mine that I believe to be all related to the same issue:
    https://bbs.archlinux.org/viewtopic.php?id=195449
    https://bbs.archlinux.org/viewtopic.php?id=193937
    https://bbs.archlinux.org/viewtopic.php?id=192704
    [edit3] My previous thought was that this was a btrfs issue, however now I think it may be more hardware related.[/edit3]
    Last night I was writing urandom to a new drive and I woke up in the morning to see that it had stopped prematurely, but not due to lack of space. The system had not locked up completely, which was new, however, as soon as I did something that accessed the disks (tried using the Gnome Dash), all hell broke loose. I immediately hit the power button, which would start a shutdown. I didn't know about REISUB, or I would have tried that. In anycase the shutdown failed and I had to hard reboot.
    The evening before I was playing games just fine and doing normal activities.
    Also, the other day, while booted into the live cd I think it started to crash since it was acting extremely bizarre, but I shutdown, successfully, before it could do more than complain a lot. At the time I was in the middle of scrubbing a btrfs volume after a system lock up. I think, but am not certain, that I saw on my motherboard "A5" which, according to the manual indicates "SCSI reset", but I had an extremely bad viewing angle. I know neither if what I think I saw was correct, nor do I know if the system was again in the process of a meltdown.
    In general there is no activity that seems to be able to instantly trigger this, though in each case, if my memory serves me well, there was a constant stream of data either to or from a HDD.
    My set up is that I have 5 HDDs, and an SSD. One HDD has Windows, my fallback installation of Arch, and daily backups. Another drive, which I just installed a few days ago currently only has single 50GB btrfs partition that is not part of any sort of larger volume. I also have three other drives each with four parttitions each involved in a btrfs volume. At the top is a 175 GB volume in a RAID0 configuration,  after that is a 25GB partiton in RAID1, then a 650GB partion (RAID1), and the remainder of the disk (about 80GB) is in single. The RAID0 is has games on it and sometimes for short term storage (a few hours), the 25GBx3 RAID1 is used for Arch as well my ~/.local, ~/.cache, ~/.thunderbird, ~/.mozilla, and ~/.config. The 50GB partition I mentioned is currently doing the job of this volume, and was not mounted last night, but has been before. The 650GBx3 is used for long term storage of just about everything, in particular ~ is mounted here. The single configured volume is used for downloads, storing ISOs and installers. The SSD is used for caching those partitions used in the RAID0 volume with bcache. I DO NOT think this is a bcache issue since the RAID0 volume has never had any errors.
    My motherboard is a ASUS X79-DELUXE which has the SATA controllers: Intel X79 Express Chipset, Marvell 9230, ASMedia 1061.
    [edit] Oh, I'm on kernel 3.19.2 and btrfs is 3.19.
    [edit2] Also, I converted the RAID0 to a single in case that matters.
    [edit4] I finished scrubbing and copied my "journalctl -b" output to pastebin. I can't see any thing that might raise any flags. http://pastebin.com/WXpbpTuc
    Last edited by nstgc (2015-04-05 16:46:00)

    nstgc : it's hard to tell if your problems are memory related, but memtst often needs multiple passes to detect errors.
    How many passes did you let it make ?
    Is it possible for you to take out say half of the memory chips and see if that changes anything ?
    Last edited by Lone_Wolf (2015-05-22 18:27:04)

  • System Lock-ups. What can be wrong?

    On to more serious issues.. .
    I am experiencing system lock-ups on the brand spanking new computer I just buildt.(Yeah, yeah.. . Anti-static and all other thinkable precautions were taken.. .)
    Needless to say it's annoying the hell out of me. I can't work and I can't play with a situation like this.. .
    The system just hangs and the only solution is to press the reset button.
    This usually happens in games or when scrolling a window. Less frequently it also happens when doing nothing. It only seems like it's getting worse - more frequent that is.
    Are there any known issues with TwinMos RAM and nForce2?
    The RAM and CPU are running on the same clock. The error persists when running the RAM at it's native clock too.
    I'm running Catalyst 4.11 and Bios Information says 113-95702-100.
    The BIOS of the MB has not been flashed by me - as out-of-the-box.
    Nvidia drivers version 5.10.
    No overclocking of any sort of any device.
    I will be running the full monty in Memtest x86 over night, but the RAM DIMM is spanking new and has been handeled with the utmost caution. The first five tests returned nothing wrong.
    Another peculiar hick-up is that sometimes after the lock-up and after I've pressed the reset button the BIOS seems to take forever to detect the IDE devices. If I power off and on again, the IDE detection happens in a snap. Very, very strange.. .
    Edit: I have a sneaking suspicion that it gets worse until I power off/on - after that it will take a longer time for the error to return. I haven't verified this empirically, but I have a hunch.. .
    I really hope there's someone with helpful insight to this problem out there!
    Thank you for your time.

    Woops. Seems like I don't have access rights to the last link.
    It seems like downflashing to B30 is the only way to go for me as I'm having *major* stability issues, even with no overclocking.
    Heck - I even had to reset and reboot the machine when trying to write this post just now!  
    I must say I've never experienced such outrageous instability with any of my other MSI MBs before.. . Not from any other make for that matter. This is just incredible.
    I'll flash it tomorrow (if I can find a damned floppy somewhere). For now I really have to work.
    Fingers crossed!
    Thanks again for great input!

  • Bluescreens and Lock-ups with 2.15.0

    I downloaded the latest driver version, 2.5.0006 today in an effort to try and fix an issue that was intermittently causing the card to stop working (either Vista would tell me no sound device was detected, or there inexplicably would not be any sound what-so-ever).
    Since 'upgrading' to the latest version, I have experienced 2 BSoDs and 2 complete system lock-u
    ps.
    Frustratingly, even the BSoDs themselves are locking up while allocating memory for the crash dump, so I can't get any useful information about what is causing it. Since the only software I've installed in the past month or so - aside from Vista updates - is this sound card driver update, and I haven't seen a BSoD since August of last year, just before nVidia managed to fix an issue with their video card drivers, I am highly suspicious that the crashes are caused by these Creative drivers.
    I have contacted customer support about the issue, but while I am waiting to hear back from them, are any of you running across this issue at all My current plan is to wipe out all the drivers and software and install Daniel_k's latest distribution to try and fix this problem. Does anyone have any other suggestions
    Edit - System specs:
    PC Power & Cooling Silencer 750W
    Intel Core 2 Duo E6700 2.67 GHz
    EVGA nForce4 680i mobo
    4 GB RAM
    BFG nVidia 8800 GTX (x2 in SLi)
    Sound Blaster X-Fi Elite Pro
    Windows Vista Ultimate 64-bit
    While I was updating the post with my system specs, the computer BSoD'd again.
    Edit #2
    And in case you were wondering, no, the driver update did not fix the original issue.
    Message Edited by Emura on 04-2-2008 2:00 AM

    Yeah, sounds like you're getting the same problem as me. I've been having random lockups upon reboot as well as lockups and bluescreens while using the device; listening to music, watching YouTube videos, and playing games.
    Interesting to note that we don't have the same chipset, amount of RAM, video card configuration, processor, or Vista installation.
    It's been about 24 hours since I e-mailed tech support about the issue. They say their average response time is 24 hours, so I'm hoping to see something tomorrow.
    As for overclocking, I haven't overclocked this PC so I don't think that's the issue. I appreciate all the feedback and suggestions that have been given so far!
    Update: I recieved an e-mail from tech support today, and it was exactly the canned auto-response I was expecting. I'll copy and paste parts of it here:
    CLI Support wrote:
    1. If there is an onboard audio on your PC's motherboard, it is
    recommended that you disable onboard audio to prevent any conflicts it
    may cause with the Sound Blaster device.
    CLI Support wrote:
    2. Please follow the steps to uninstall and reinstall the sound card on
    your system by following the instructions in the following knowledge
    base article.
    Title: Uninstalling Sound Blaster Drivers and Applications
    URL: http://us.creative.com/support/kb/ar...asp l=3&sid=72
    CLI Support wrote:
    The only method for obtaining a refund or exchange is through the vendor
    (original place of purchase). We can only accept a returned unit if the
    product is possibly defecti've, in which case an RMA (Return Merchandise
    Authorization) would be issued. The Creative Labs RMA department's
    responsibility is to test and repair/replace defecti've products once our
    technical support agents have determined the product to be defecti've via
    troubleshooting steps.
    CLI Support wrote:
    In the meantime please take the time to browse our latest offerings from
    Creative:
    Stunning design and superior audio reproduction. The Creative HQ-900
    Headphones embody all these and more while deli'vering clear and detailed
    playback for all genres of music. Coupled with its reversible earcups,
    the HQ-900 headphones is great for critical music monitoring and is the
    choice headphones for club DJs and home studio mixers.
    More info about the product in this link:
    http://us.creative.com/products/prod...8&product=7009
    At this point, I'm pretty tired of dealing with this card. The store I bought it from won't take it back for an exchange or refund, and I doubt CL will RMA it, since the 'product' seems to work fine (though IMHO, defecti've drivers = defecti've product). Even if I could get an RMA through CL, they'd only end up sending me another card, which wouldn't fix the driver issues at all.
    I'm going to look around and see if I can find someone interested in buying it, then put that money towards a new card from M-Audio. In the meantime, however, I'll play CLI Support's game and try uninstalling and reinstalling the drivers again. Let's see where that goes.
    Message Edited by Emura on 04-3-2008 0:24 PM

  • Constant stream of lock ups with Lion 10.7.2

    At my wits end since upgrading to Lion (10.7.2).   I get a constant stream of application lock ups (beach ball) on every app I try:  Firefox (8.0.1) , intermitent connectivity to Internet (although I know my connection is good); App  Store unable to connect; iTune unable to connect to store; Parallels Desktop locks up; Outlook (Office Mac 2011) locks up, Time Machine locks up, and more not mentioned.  None of these seem to occur at the same time; it's more like the app that decides to not work is random.  Firefox is good but App Store will not connect;  iTunes is good, but Firefox will not connect. 
    Each time I'm forced to restart or shutdown only to have similar, but not the same, errors after I log back on.  The errors (lock ups) started right after the upgrade and have gotten progressively worse as the days/weeks go by.  At the point now where the PC is completely unreliable.  It's a crap shoot to find out what is working and what is not.
    I've tried about everything mentioned in the forums -- verified/fixed permissions, used Mac OS install DVD to verify/fix HDD issues; no help.
    Prior to upgrade, I had zero issues running SL -- all of this started with Lion. 

    simon57 wrote:
    In any case, shouldn't Software Update recognise what I am running and what is needed to update it successfully?
    To a point. It will inform you of a system update, as with Lion 10.7.2 for example, but that is not the combo update. I set my Systum Updates to install manually, if I see an OS update, I always go to
    http://support.apple.com/downloads/
    And choose the Combo update whice is always a little bigger, but a cumulative install as mentioned. Always appears to be more stable.
    Cheers

  • 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.

  • Random system lock-up or freeze / Linux 3.4

    Hi
    My system seem to regularly lock-up in the linux 3.4[1] series. Whenever this happens, I had to power cycle the system by holding down the power button. Keyboard, numlock, mouse wouldn't work. I'm still looking-out for a pattern that trips this lock-up consistently. The lock-up doesn't happen for days and can happen every other day as well.
    During this lock-up nothing gets captured in the system log too. I parsed 'journalctl -a'. Here is a sample from such a lock-up:
    Jun 30 18:01:01 chaembian /usr/sbin/crond[4747]: pam_unix(crond:session): session opened for user root by (uid=0)
    Jun 30 18:01:01 chaembian /USR/SBIN/CROND[4748]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 30 20:45:03 chaembian kernel: Initializing cgroup subsys cpuset
    Jun 30 20:45:03 chaembian kernel: Initializing cgroup subsys cpu
    I noticed the lock-up around 18:30 and instead of forcing it to shutdown, I thought I would give it sometime to snap out of it. But nothing happened until 20:45, when I forced the restart. The only other anomalies are (picking out their first apperances):
    Jun 25 13:57:33 chaembian kernel: BUG: Bad rss-counter state mm:ffff880115e10a80 idx:1 val:-2
    Jun 25 13:57:34 chaembian kernel: BUG: Bad rss-counter state mm:ffff880115e10a80 idx:2 val:2
    during shutdown
    and
    Jun 10 10:08:57 chaembian kernel: r8169 0000:05:00.0: eth0: link down
    Jun 10 10:08:57 chaembian kernel: r8169 0000:05:00.0: eth0: link down
    Jun 10 10:08:57 chaembian kernel: NOHZ: local_softirq_pending 08
    during boot[2]
    I'm not sure if these precipitate the lock-ups but these are the things that stand out in the logs for my untrained eyes.
    > uname -a
    Linux chaembian 3.4.4-2-ARCH #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 x86_64 GNU/Linux
    Let me know if you require any more information.
    1 - I was a regular -ck patched user. Since the time the series started serving 3.4 series, I was having lock-ups. Since the stock was still at 3.3 then, I was using the stock as I was trying understand the issue from the logs. But ever since stock moved into 3.4, the lock-ups are happening in this as well. Again, since I have not been able to recreate the issue on demand, I'm not able to attribute the regression to 3.4 conclusively.
    2 - A similar issue that was reported from last year will be System lock-ups or software resets, with increased ethernet activity. But the key difference is that my logs have just one instance of this message generated at the time of boot.
    Last edited by chaembian (2012-07-02 04:57:50)

    Yes, that's how I have it setup. Until today's forced power cycling earlier today, the journal had all the entries from June 10th. The system gets proper shutdown daily (there is a power shortage where I live and to counter there is a scheduled, daily power shedding for 1 hour).

  • I am feeling so ripped off right now. I have wanted a Mac for years and believed the hype about it's stability and I have had more trouble with this Imac 2011 than I have ever had with a pc. It locks up with several software products from APP store.

    I am feeling so ripped off right now. I have wanted a Mac for years and believed the hype about it's stability and I have had more trouble with this Imac 2011 than I have ever had with a pc. It locks up with several software products from APP store. I have already had to have a technician to look at it and really couldn't figure out what the deal was.  I was told that the APP store software should give me no problems but the truth is that it locks up on the software. This machine is only 4 weeks old and I am using 37 g on a 1 T hard drive. There is no reason for it to be locking up. Also, when I try to use the help program, it always tells me that I am not connected to the internet even though I have used both the mail program and the browser with no problem just before that. I successfully used the help program on my pc lots of times. I did not need a $2000. plus machine to just get email. I just wanted to unload on somebody that might understand my pain and after checking out this site...I think there is a few of you out there.

    I was told that the APP store software should give me no problems but the truth is that it locks up on the software.
    The apps downloaded from the Mac App Store are written by third party developers, not Apple. If you have problems  with those apps you need to visit the support area for their websites. Launch the App Store, locate the app name. You should see a support link.
    when I try to use the help program, it always tells me that I am not connected to the internet even though I have used both the mail program and the browser with no problem just before that
    Go to ~/Library/Preferences. Move the com.apple.helpviewer.plist file from the Preferences folder to the Trash. Restart your Mac, try the Help menu.
    If you need help finding that file, hold down the Finder icon in the Dock then click: New Finder Window. From the menu bar top of your screen click: Go > Go to Folder. Type this in exactly as you see it here:   ~/Library/Preferences/com.apple.helpviewer.plist    That will take you right to that file.
    (.plist) files stores information about a particular app or in this case, the Help viewer. Often times deleting the .plist file resolves the issue.
    It's fine to "unload"... we understand that you expect your iMac to be stable but there are times when things go awry. That's why we have these forums so that you can you get help.
    You may want to read up on how to repair the disk if necessary or reintsall Lion >  OS X Lion: About Lion Recovery
    Apple - Find Out How - Mac Basics
    How to "switch" from PC to Mac >  Apple - Support - Switch 101
    I'm sorry you feel, "ripped off", but you are using the world's most advanced operating system and it may take some time to adjust to a new OS.   http://developer.apple.com/technologies/mac/

  • Adobe Media Encoder Locking up with AVCHD

    Greetings,
    I have run so many tests on this project I don't know what else to try, so here it goes...
    My system -
    Windows 7
    ASUS P6T mobo
    Core i7 920
    Quadro FX 1800 w/Elemental Accelerator
    PPro Prem Prod CS4
    All current drivers and updates installed
    I have plenty of speed to run AVCHD but upon encoding in AME there is a crash issue.
    Source footage is 10 minutes of AVCHD (.mts) captured at 17Mbps, 1920x1080i, 60i.(I've also tried other AVCHD source footage).
    I run Elemental Accelerator on a Quadro FX 1800 card with the latest version of drivers. The CS4 version is also latest version.
    The footage is edited in PPro. It has several titles, one of which is an AE linked title, but fairly simple.
    The footage is edited as timelapse, sped up between 200-400%, so, it's pretty 'busy'.
    Audio track is standard .wav file
    Upon export, I wanted to make a master file at 1920x1080p, using Elemental H.264...or Elemental MPEG-2.
    I check render at maximum quality....multiplexer is TS. I've tried the preset bitrates, and custom from 12-28kbps.
    Every time I set it to encode, AME locks up....at random times. The entire system locks, no mouse response, and have to do a hard restart.
    I've tried MANY test clips...mostly around 2-5 minutes in length. Sometime the shorter clips will render, but if I go over this length it always locks up.
    I did try bitrates ranging from 12Kbps to 28Kbps....and it did seem once I went over 15Kbps they ran longer or enabled a longer 'attempt' or a successful encode up to 5mins. Still, with those exact settings it locks up on a longer encode.
    I made a successful encode using a non-Elemental preset, but it takes foooreever. 3.5 hours for 10 minutes of footage at 1920x1080p...which seems ridiculously long on a GPU enhanced card. As a comparison, I have a third party encoder (AVS) and it FLIES through the (pre-rendered) footage at blazing speeds with good quality. (Yes, I know that's diff than the first pass encode however).
    I've tried un/reinstalling CS4, Elemental, and all drivers on a CS4 Clean Script for Windows....no help whatsoever. Defragged, ran CCleaner....no help.
    Is my bitrate too low? GPU issues? Voodoo curse?
    Any advice is greatly appreciated.

    Thanks for your response dradeke. Yes, that was one of the fist things I checked. I double checked with Elemental Tech support, and even sent them my project files to see if they could duplicate the crashes but they have not found any issues on their end. I have all the updates to both CS4, EA, Windows.
    I'm at a total loss here...I've even switched the projects to other drives, and tried deleting prefs.

Maybe you are looking for