RAM registering wrong MHz

I got PNY 8GB RAM and it said it was 1067 MHz. When I installed it it registered in my MBP as 1333 MHz. The package says its compatible with 1067 MHz and 1333 MHz systems. Will this damage my MBP? I'm wondering if I should send it back and try another brand.

It's working. Just noticed it registering the different MHz under the About This Mac tab.

Similar Messages

  • Commitment registered wrongly

    Hi Experts,
    This problem occurs in a service purchase order with Multiple Account Assignment and the S.-Based IV is marked.
    Commitment is registered wrongly because the system registers double Adjustment by Follow-on document.
    Could you help me please.
    Thanks in advance.
    I attached an image:
    http://subefotos.com/ver/?b3f6ec9a9d33de10de998357f3cd3e0bo.jpg[url]
    José Luis

    Hi,check note 1455122 and 152571

  • AppWorld Email address registered WRONG

    Hello All, 
    First time! And I know I'd sound like a complete **bleep**!  
    The email address I registered in Appworld for my BB Playbook, unfortunately, was mistyped and incorrect. It was fine until i forgot the password and now could not login. I was trying to use another AppWorld login (the one I use for my BB Pearl) unfortunately (again ), the Playbook doesnt allow changes in the registered email address somehow ( or am just really a total **bleep**! ).
    I have already gone through a lot of verification and all, which ends up sending a new password to the email I registered, which i cannot access because I did it wrong. 
    Would appreciate an assistance, please. 
    thank you! 
    Jen 

    Your choices are:
    --Use another email account to create an entirely new BlackBerryID (with which you will lose access to any purchased apps using the "forgotten" first BlackBerryID, or
    --Find the initial email you were sent to confirm the initial BlackBerryID, and in it is a link to click to cancel and delete the account. Click on that, delete the account and then you can use that same email to create an entirely new account.
    Good luck.
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Ram ratio wrong on 865pe

    Can't understand why, but my ram is running at 5:4 of the fsb (fsb 158 ram 396) and i cannot change that setting....even if i select ddr333 or ddr 266!!! 'X('
    My system is msi 865pe -s
    with a p4 2.4b (previously reached 168fsb)
    and 2 sticks (256 + 256)of twinmos pc3200 ram
    I have run every bios version!!!!

    Hi bugsrunner,
    Try setting your CPU Bus clock to 133 and set DRAM Frequency to DDR333. Under your DRAM Timing, set to by SPD and see if it runs at CL2.5-3-3-7-8burst.
    All the Best... :D!!!

  • Würden mir 32 GB DDR4 RAM 3000 MHz "deutlich" mehr Performance in Photoshop, Lightroom und Bridge CC bringen als meine alten 16GB DDR3 RAM 1600MHz?

    Ich würde gerne mehr Geschwindigkeit in PS CC haben und würde im Zuge eines neuen Prozessors & CO den Arbeitsspeicher gerne mit erweitern bzw. optimieren.
    Für mich stellt sich die Frage, ob die neueste Generation DDR4-RAM mit 3000 MHz mich wirklich zum Ziel führen kann oder nicht. Wenn ich einen wirklich merkbaren Geschwindigkeitsschub dadurch bekomme und sich die Photoshop eigenen sowie NIK-Filter schneller verrechnen lassen wäre es mir die Anschaffung wert. Hat schon jemand Erfahrungen mit DDR4 RAM sammeln können? Vielen Dank für ein konstruktives Feedback im Voraus.
    S.Röhler

    Pixel durchkauen ist nun mal an die Routinen gebunden, die das System bietet - das öffnen einer großen Raw-Datei kann nun mal länger dauern, als den Filter drüber zu bügeln und genau so kann es sein, dass das Laden der für eien Zoomstufe gedachten Cache Tiles von der Photoshop-Auslagerungsdatei länger dauert, als wenn man nicht gezoomt hätte und einfach in voller Größe hin- und herschiebt. Wenn überhaupt, kann man eventuell auftretende performanceprobleme und Bottlenecks imemr nur spezifisch lösen, aber dazu müßte man genaue infos haben, was du machst, mit welchen Dateitypen, Auflösungen usw. du arbeitest, wo Dateien gespeichert sind und so weiter. Speed ist ohnehin etwas sehr subjektives. Wie schon gesagt, schnelle Platten bringen viel, eien schnelle Grafikkarte könnte z.B. bei der Raw-Bearbeitung helfen, weil LR und ACR auch GPU-Beschleunigung verwenden. Andererseits kann dir schon ein einziges schlechtes Farbprofil die ganze Performance auffressen. Wie gesagt, der Teufel liegt im Detail...
    Mylenium

  • Kingston 1600 mhz Ram Reading only 1333 Mhz Help?

    My system is a pavilion G6 with the A6 AmD Processor. HP says it can go to 8GB Ram to 1600 mhz. I tried everything and CPU-Z says only 667 x2. It should be 800x2 Any ideas. Reccomendations Thanks

    15 views, no answers? Come on guys.

  • Upgraded to 2x 8gb ram and registered 12gb only on my envy ultrbook 4

    Just change the old 4gb ram with 2x of 8gb ram and only 12 gb ram registered.

    Manual says this:
    Supports up to 16384-GB of system RAM
    Manual
    It is likely an issue of compatibility. Please provide whatever identification by part number that is on the old modules and the new ones and we can try to track it down. 

  • Wrong Memory RAM?

    I Recently bought two sticks of RAM (DDR3 1333 Mhz 8GB AVANT) for My Mac Mini i5! Shortly after that, the Mac SUDDENLY RESTARTS with a Gray SCREEN and a MESSAGE  in MANY LANGUAGES, saying it has to be RESTARTED for an ERROR! then I thought: is posible that RAM is causing the problem? that means that I have to buy an APPLE MEMORY RAM ONLY?

    The RAM may well be the cause of the problem, yes. Apple does not make their own RAM, so no, you do not have to buy from Apple, but not all vendors provide high-quality RAM. You may well just have received defective or out-of-specification memory. If the Mac works correctly with the original RAM, get your memory vendor to replace the DIMMs, and in problems persist, return the RAM for a refund any try RAM from another vendor.
    Regards.

  • Is there a way to define RAM usage of Preview?

    Hello,
    i use Mountain Lion now, but i found an annoying difference comparing to Snow Leo.
    I am an Architect and i have to view and occasionally annotate tens of PDF Drawings a day. The files can be in certain cases quite large (10+ MB). On Snow Leo, viewing a PDF Drawing was smooth and fast independent from the file size, but in exchange it took much RAM, sometimes over 4GB (i have 8GB of RAM).
    Nowadays, on Lion and Mountain Lion, Preview became annoyingly slow when i opened a PDF Drawing. Scrolling, zooming by pinching is also very slow and laggy.
    My question is, if there is a way to extend the memory usage cap of Preview to make it work with PDF Drawings smooth and fast as before.
    Maybe i am wrong, and the 2 things have nothing to do with each other, so if there is any other solution, i would be more than happy to read it here.
    My config is:
    MacBook pro 15" mid 2009
    2,66 GHz dual core
    8gb ram DDR3 1067 MHz
    Thanks in advance:
    Leslie

    Then I'd say it is a hard drive problem as Apple uses the Slow 5400RPM models be default.
    There have been many posts on this forum about Slow PFD scrolling/viewing with no real solution that I remember.
    Take a look at the "More Like This" section to the right on this page.

  • What's wrong with my system? details inside...

    hey all.
    i'm using the k8t Master 2 FAR board with dual opteron 940 (1.8 ghz) chips and 2 gigs ddr ram, ecc registered 266 mhz. the video card is a 256 meg ati 9600. monitor is a 17 inch samsung lcd. power supply is 400 watts.
    when i turn on the system for the very first time, things power up. fans, lights, etc. however, the monitor says "no sync." it's better than n*sync but still not what i want.
    monitor is fine. i plugged it into the vga port on my laptop and it worked perfectly.
    video card is fine, i plugged it into a different system and it worked perfectly.
    now here's the thing: i originally had a refurb motherboard and this is what happened. i called msi and they told me the mobo was probably bad. so, i returned it to new egg and got the same motherboard, but *this one is brand new.* same results, exactly.
    the motherboard is not in a case, it's resting on the non-static bag it came in on a wooden table. the psu is grounded through the grounding prong of the plug, which i'm told is all that's technically needed.
    what the heck is going on?
    thanks all!
    ren

    yeah, it's a socket 940 (not the 748 or whatever the other ones are...), but the chips themselves are the 244 i think (1.8 ghz.)
    power supply is here (it's easier than trying to explain it...):
    http://www.electroseller.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=PS_400W-AGPB-1U&Category_Code=_1U
    what do you think? will i ever play piano again?? *sniff*
    ren

  • Aluminum iMacs RAM question

    Hello all!
    I currently have a Core Duo iMac, one the first Intel ones. My RAM is 667 MHz, I have 2 GB installed. I am using my iMac for working with large sound and image files, so memory and CPU speed are important to me.
    I would like to get a 20" iMac when Leopard comes out, but one thing I am concerned about is that it's memory is still 667 MHz. Please tell me, is it worth waiting for when they switch to faster memory bus? Or do you know if the 800 MHz frontside bus helps somehow?
    Thanks,
    Artemiy.

    Thanks for your reply!
    Yes of course I know it's Intel, and I'd have to wait for their new platform. The thing is I plan to keep that iMac until they release the next OS X version, I am afraid in 1-1.5 years, with my slowly-but-surely growing demands, 667 MHz memory won't suffice. Well, anyway, 667 MHz is about 80 MB per second, still very fast, maybe I am wrong here and increased front side bus and CPU speed would do much more to me!
    Thanks again,
    Artemiy.

  • Kernel Panic after installing 16 GB RAM in 2010 13" MacBook Pro

    Hi
    I have been having some problems with my 2010 13" MacBook Pro.
    After installing 16 GB RAM, made by Corsair, I have had four Kernel Panics so far.
    The thing is that the RAM are 1333 MHz, and my computer only takes 1066 MHz RAM. But I downclocked both the sticks to 1066 MHz, so it should work right? They also passed Memtest86, so I don't know what is wrong.
    I also did a clean install of Mountain Lion, on a brand new hard drive, but I had another Kernel Panic.
    Here is the latest log:
    Interval Since Last Panic Report:  15729 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    BAC8DBFE-5FBB-C8FA-FEFD-161B17915C50
    Fri Feb  1 18:35:33 2013
    panic(cpu 0 caller 0xffffff800c8b7bd5): Kernel trap at 0xffffff7f8e00e501, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0xffffffffffff6cb6, CR3: 0x0000000025a0e000, CR4: 0x0000000000000660
    RAX: 0xffffff7f8e058a80, RBX: 0xffffff81a6245000, RCX: 0x0000000000000001, RDX: 0x0000000000000020
    RSP: 0xffffff81d3adbab0, RBP: 0xffffff81d3adbae0, RSI: 0x0000000020000001, RDI: 0xffffff81a6453000
    R8:  0x0000000000000024, R9:  0x0000000000000000, R10: 0xffffff8031486284, R11: 0xffffff7f8dfb74c8
    R12: 0xffffff81a643f000, R13: 0x0000000000000800, R14: 0xffffff81a660f000, R15: 0x0000000000000000
    RFL: 0x0000000000010a03, RIP: 0xffffff7f8e00e501, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0xffffffffffff6cb6, Error code: 0x0000000000000002, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff81d3adb750 : 0xffffff800c81d626
    0xffffff81d3adb7c0 : 0xffffff800c8b7bd5
    0xffffff81d3adb990 : 0xffffff800c8ce4ed
    0xffffff81d3adb9b0 : 0xffffff7f8e00e501
    0xffffff81d3adbae0 : 0xffffff7f8dfb65f2
    0xffffff81d3adbb30 : 0xffffff7f8dfb7578
    0xffffff81d3adbba0 : 0xffffff800cc665b3
    0xffffff81d3adbbc0 : 0xffffff800cc6718d
    0xffffff81d3adbc20 : 0xffffff800cc64b8f
    0xffffff81d3adbd70 : 0xffffff800c8981e1
    0xffffff81d3adbe80 : 0xffffff800c820aed
    0xffffff81d3adbeb0 : 0xffffff800c810448
    0xffffff81d3adbf00 : 0xffffff800c81961b
    0xffffff81d3adbf70 : 0xffffff800c8a5b16
    0xffffff81d3adbfb0 : 0xffffff800c8ced53
          Kernel Extensions in backtrace:
             com.apple.GeForce(8.0)[2E56ED9A-D848-3795-9E52-56BABDC9000C]@0xffffff7f8dfab000 ->0xffffff7f8e06dfff
                dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f8cf 14000
                dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8cf00000
                dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f8ce72000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f8cebd000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    12C60
    Kernel version:
    Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
    Kernel slide:     0x000000000c600000
    Kernel text base: 0xffffff800c800000
    System model name: MacBookPro7,1 (Mac-F222BEC8)
    System uptime in nanoseconds: 7195773548951
    last loaded kext at 6632145833: com.apple.driver.AppleHWSensor          1.9.5d0 (addr 0xffffff7f8e737000, size 36864)
    last unloaded kext at 74564537026: com.apple.driver.AppleMCP89RootPortPM          1.11 (addr 0xffffff7f8e6bb000, size 24576)
    loaded kexts:
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AudioAUUC          1.60
    com.apple.iokit.IOBluetoothSerialManager          4.0.9f33
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AGPM          100.12.69
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AppleHDA          2.3.1f2
    com.apple.driver.AppleMikeyDriver          2.3.1f2
    com.apple.driver.AppleLPC          1.6.0
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.2.11
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f33
    com.apple.driver.AppleSMCLMU          2.0.2d0
    com.apple.driver.AppleBacklight          170.2.3
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.driver.AppleMCCSControl          1.0.33
    com.apple.GeForce          8.0.0
    com.apple.driver.SMCMotionSensor          3.0.2d6
    com.apple.driver.AppleUSBTCButtons          235.4
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.driver.AppleIRController          320.15
    com.apple.driver.AppleUSBTCKeyboard          235.4
    com.apple.driver.AppleUSBCardReader          3.1.0
    com.apple.iokit.SCSITaskUserClient          3.5.1
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.2.2
    com.apple.driver.AirPort.Brcm4331          602.15.22
    com.apple.iokit.AppleBCM5701Ethernet          3.2.5b3
    com.apple.driver.AppleUSBHub          5.2.5
    com.apple.driver.AppleUSBEHCI          5.4.0
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleUSBOHCI          5.2.5
    com.apple.driver.AppleEFINVRAM          1.6.1
    com.apple.driver.AppleAHCIPort          2.4.1
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.7
    com.apple.driver.AppleACPIButtons          1.6
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.6
    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.1f2
    com.apple.iokit.IOAudioFamily          1.8.9fc10
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.driver.AppleHDAController          2.3.1f2
    com.apple.iokit.IOHDAFamily          2.3.1f2
    com.apple.iokit.IOSurface          86.0.3
    com.apple.iokit.IOBluetoothFamily          4.0.9f33
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.2.0d16
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f33
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleGraphicsControl          3.2.11
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.nvidia.nv50hal          8.0.0
    com.apple.NVDAResman          8.0.0
    com.apple.iokit.IONDRVSupport          2.3.5
    com.apple.iokit.IOGraphicsFamily          2.3.5
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.AppleUSBMultitouch          235.7
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.1
    com.apple.iokit.IOUSBMassStorageClass          3.5.0
    com.apple.driver.AppleUSBMergeNub          5.2.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1
    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.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
    com.apple.iokit.IO80211Family          500.15
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOUSBUserClient          5.2.5
    com.apple.iokit.IOUSBFamily          5.4.0
    com.apple.driver.NVSMU          2.2.9
    com.apple.iokit.IOAHCIFamily          2.2.1
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.driver.AppleEFIRuntime          1.6.1
    com.apple.iokit.IOHIDFamily          1.8.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          344
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.6
    com.apple.iokit.IOPCIFamily          2.7.2
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    System Profile:
    Model: MacBookPro7,1, BootROM MBP71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 16 GB, SMC 1.62f7
    Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1067 MHz, 0x029E, 0x434D5341384758334D314131333333433920
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1067 MHz, 0x029E, 0x434D5341384758334D314131333333433920
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.81.22)
    Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: Samsung SSD 840 Series, 120,03 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24600000 / 2
    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26100000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06600000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06610000 / 5
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x06500000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0x06300000 / 2

    ChFrMo wrote:
    My Mac works just fine. It's just that once in a while, it gets a Kernel Panic. Usually when I'm using Safari, or playing a video.
    I have taken these screenshots:
    http://dl.dropbox.com/u/13478021/Screen%20Shot%201.png
    http://dl.dropbox.com/u/13478021/Screen%20Shot%202.png
    Getting a kernel panic once in a while is not my definition of "My Mac works just fine..."
    You installed the incorrect ram. Get the ram specified for your computer. In theory ram should downclock to the computer's bus speed but in practice this does not always work, as you found out.

  • P35 Platinum stuck with 008D error in boot with newly added OCZ Fatal1ty rams

    Hi,
    I was using 2x1 GB 800 MHZ OCZ vista performance rams without any problem. I just bought 2x1 OCZ Fatal1ty 1066 MHZ rams. In the specification of my P35 Platinum mainboard it tells that it supports 1066 (OC).
    I don't want of course to run all my rams at 1066 MHZ. I just want to run all of them at 800 MHZ.
    However, when I placed all 4 rams in every combinotion on the slots, computer boots but it stuck after the boot screen and there is "008D" in the rightdown corner.
    Interestingly when I just put Fatality rams (2GB)  computer doesn't boot! Only 1xvista perf. Mhz 1xFatal1ty or 1xvista perf. Mhz 1xFatal1ty works but stuck at after the boot screen.
    I tried to enter 5-5-5-15 values and tried to adjust memory voltage to 2.1 V as told in the new ram's specification but doesn't affect. What is your solution? Since new rams do not work among themselves, are they broken or my board doesn't support them?

    If I'm not wrong, your post sounds to me that you are trying to mix the OCZ Vista and OCZ Fatal1ty RAMs on the same board.
    This is highly not recommended as both RAMs are very different in most aspects (Speed, latencies, voltage and made).
    I would suggest that you clear CMOS and choose which set you'll want to boot the system with and settle with that.

  • Imac intel ( i think is a middle 2007) ram 667 for 800 is possible?

    hi i have a little problem ^^
    i have buyed 1 new slot of ram from apple store of 2 gb 800 mhz ddr2 etc etc , i had 2 ram of 1 gb 667mhz ddr2 etc etc (is an i mac intel from middle 2007 if i remember well ), now i have installed 1 of 1gb 667mhz and one of 2 gb 800 mhz.
    now i have buyed another ram 2gb 800 mhz because with snow leopard o would have a total of 4 gb.
    the question is : have i made a stupid thing? because i'm not sure that my imac could support a bank of 800 mhz (i have tryed to install only the ram of 800 mhz but the machine didn't start)
    so help help help i have to know if i have to send back my new ram or i could install it ^^
    ty for help and support
    joey
    p.s: sorry for my bad english.-.-,

    There were two iMac models where the system bus speed and the RAM speed were mismatched: the Mid '07 iMac with bus speed of 800 GHz, but RAM speed of 667 GHz; and the Early '08 iMac, with bus speed of 1066 GHz and RAM speed of 800 GHz. These two machines appear to cause a lot of confusion with Apple employees, because many folks report being misdirected by Apple employees to purchase the incorrect RAM. (Or perhaps misinformed employees of 3rd party Authorized Apple venders. Some folks confuse 3rd party venders of Apple products with being Apple!)
    Those users who have been steered to the wrong RAM speed report that their iMac will usually function with one RAM bar of the faster, incorrect speed, plus one with the correct speed, but that it will not usually function with two RAM bars of the incorrect speed.
    An interesting side fact is that Apple reports both these machines as topped out with a maximum of 4 GB of RAM (2 x 2 GB). However, it is now a well established fact that both machines can address 6 GB of RAM (1 x 2 GB + 1 x 4 GB). This is reported by MacTracker, Other World Computing and a poster here in the iMac Intel forums. Dave has provided screenshots of his Mac's Activity Monitor showing the Mac addressing and allocating the use of 6 GB of RAM. He owns one each of the Mid '07 and the Early '08 and reports that 6 GB of RAM has breather new life into both machines.
    Dah•veed

  • MSI Z77A-G43 RAM Problems

    Hi everybody,
    I have some big problems with my new build:
    Intel Celeron G1610
    MSI Z77A-G43
    2x4gb Corsair Vengeance LD low voltage 1600 mhz 1.35 v dual channel kit
    Seasonic 620w PSU
    Saphire 7850 2gb GDDRAM5
    My system wont work with both ram sticks in. If I only use one of them (it doesn't matter which one) in whatever slot I want, I don't have any problems. However if I use both of them I get bsods or restarts very soon after windows finishes loading. I must also mention that it's almost impossible to install Windows with both Ram sticks in. I almost always get a bsod when the installer is expanding the windows files.
    I must also mention that by default, my motherboard sets my ram to 1333 MHz and 1.5v even if the producer says that the ram should run at 1600 MHz and 1.35 v. If I set them to these values myself in the oc menu, they are reset to the default values again immediately after I get another crash.
    I have the latest bios and drivers and I don't know what else to try: ( any ideas?
    Thank you!

    Hi flobelix and thank you very much for your response. I tried your solution and on the next powerup, my pc didn't crash at all and I ran a couple of games and memory intensive programs.
    However, unfortunatelly, after I closed the PC for a while and restarted it again, the problems came back. The ram timings don't change anymore in BIOS but the system constantly restarts. I ran memtest for 6 hours last night with both sticks of ram in and it did not find any errors so I can't figure out what's wrong.
    Here are a couple of crash dumps:
    On Sun 2/24/2013 7:08:04 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022413-9204-02.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CEF09D, 0xFFFFF88002A11C10, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sun 2/24/2013 7:08:04 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: win32k.sys (win32k!XLATEOBJ_iXlate+0xF104)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CEF09D, 0xFFFFF88002A11C10, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Sun 2/24/2013 7:06:31 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022413-9126-01.dmp
    This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0xC0D8)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003AEA0D8, 0x1, 0x17C)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\drivers\iusb3xhc.sys
    product: USB 3.0 Device Driver
    company: Intel Corporation
    description: Intel(R) USB 3.0 eXtensible Host Controller Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
    Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
    On Sun 2/24/2013 12:55:57 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022413-9188-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x48AB)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880012598AB, 0xFFFFF88002FCB938, 0xFFFFF88002FCB190)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Sun 2/24/2013 12:55:51 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022413-8829-01.dmp
    This was probably caused by the following module: Unknown ()
    Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
    Error: CUSTOM_ERROR
    A third party driver was identified as the probable root cause of this system error.
    Google query: CUSTOM_ERROR
    On Sun 2/24/2013 12:47:27 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022413-10842-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002F2DEA0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sun 2/24/2013 12:40:16 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022413-9516-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sat 2/23/2013 10:32:27 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022313-10030-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002F26C30, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sat 2/23/2013 10:29:40 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022313-9516-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000B9A850, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sat 2/23/2013 10:09:46 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022313-9438-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xB2C22)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D0EC22, 0xFFFFF88006DDA6C8, 0xFFFFF88006DD9F20)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Since I'm desperate, I'm just gonna go ahead and reinstall windows again. During the last successful pc run (after I took your advice), I ran MSI live update and installed the rest of the utility software. Maybe this did something to my drivers.... I'm really reaching the end of my possibilities :(

Maybe you are looking for