New ram sort-of working?

I have a HP probook 450 with 4gig of ram. So today I bought another 8gig of ram and installed it. When I boot up my pc it says the hardware is not supported, but when it boots up and I play a game, for example, I can see my pc performing better. So I was wondering what is up with this.
note new ram card= Adata DDR3 1600 PC3-12800 8gb
This question was solved.
View Solution.

Note that you need DDR3L...low voltage.
You don't provide enough specs on the Adata 8 gig module for us to see if it is 1.5 volt or the correct 1.35 volt memory.
The Adata I found on amazon.com says this:
ADATA Premier Series - Features Affordable Solutions with Outstanding C/P Ratio Performance. The Premier Series 1600 Mbps DDR3 204-Pin (SO-DIMM) are standard pin design modules operating at 1.5 volts
http://www.amazon.com/ADATA-USA-204-Pin-SO-DIMM-AD3S1600W8G11-S/dp/B00DOJNNLW/ref=sr_1_9?s=pc&ie=UTF...
If this is "the Answer" please click "Accept as Solution" to help others find it.

Similar Messages

My new RAM doesn't work with my iMac.

Hello,
I bought new RAM 4GB PC10600 DDR3 1333MHz SO-DIMM to installed in my iMac 3.4 GHz intel core i7, osx lion.
I try to installed it alone without original RAM (2GB * 2 pcs) installed to check how it works.
After press start button, there are 3 beep sounds and iMac won't start.
I try to reset PRAM follow the instruction, but it won't work. Because there are 3 beep sounds alarm immediately after press start.
Does my RAM have a problem?

My iMac has 4 memory slots and I try to installed one by leave 3 slots empty.
By the way this is the 2nd ram I purchased from OWC with same spec as the last one (also same as link above) but different in purchase date (about 2 weeks different).
So now I have 2 GB *2 pcs (come with iMac) and 4GB * 2 pcs from OWC.
So I'm quit sure that this ram is compatible with my iMac because the first one is work.
But I have some notice,
For the 1st RAM I bought from OWC (4GB PC10600 DDR3 1333MHz SO-DIMM), when first installation it also didn't work. I can't start iMac. And after 2 weeks, I try to installed it to my iMac again, now it can operate as normal. What do you think about it?

HT1423 My new RAM doesn't work in my iMAC.

I bought 1067 DDR3 RAM, 2 4GB cards, for my iMAC. But I'm getting the beeps. I bought my RAM through NEWEGG and even states works with iMAC. I am sure I read my iMAC can handle 8GB of RAM but I'm not sure why else I would be getting the beeps. thoughts

They generally mean the RAM is bad or you have a defective slot(s) or you may have damaged a slot when installing the RAM.
I would return the RAM to NewEgg. They are not the best source for compatible RAM. Try buying from:OWC, DataMem or Crucial.
I cannot verify what RAM your computer uses without knowing exactly what model it is or the model identifier from System Profiler.

4 hrs later - Computer shut down after installing new RAM (mid 2007 Imac)

Mid 2007 imac and I installed new Ram. It worked for 4 hrs then the Imac shutdown. The pressed power button but no power. Unplugged and replugged the power cord and 3 beeps sounded. I am wondering if it worked for 4 hrs or so, then why did it would it fail 4 hrs later?
I am running the correct ram because in system profiler under memory - it said that everything was ok.
Any ideas?

or maybe the back tray wasn't tight enough?
I re-installed it now and so far so good.... I pressed tight and in an upwards motion. We'll see what happens

Mac pro put in new ram now none of the ram works

mac pro put in new ram now none of the ram works
it just hangs on restart
the ram worked great for 12 hours then the computer restarted on its own
since then it hangs on restart and never gets to the desktop

It may not have anything to do with the RAM, or it might.
Not enough to go by to say for certain, and the blunt "get new RAM" doesn't address how to troubleshoot or resolve most likely.
Was it installed properly?
How much did you install?
Make? vendor.
Try running with just the new RAM.
Run Apple Hardware Test - boot 'd' key on startup, you may need your OEM Install DVD.
Run Rember and/or Memtest utility to test memory, or TechTool Deluxe.
When a computer restarts on its own it often means there was a kernel panic or something and damage to files, directory, journal and in need of repair, booting off your DVD or another drive to repair the drive, delete some files, turn journaling off and then on.
http://docs.info.apple.com/article.html?artnum=106227
http://www.macmaps.com/kernelpanic.html
http://www.thexlab.com/faqs/kernelpanics.html

New RAM not working

I have a macbook pro 13 inch from mid 2010, with an Intel Core 2 Duo 2.4GHz. I recently got a 1 TB WD Scorpio Blue for it that made a loud buzzing noise and after having the OS installed, wouldn't boot properly. I will be exchange this drive for a new one of the same type because I know it works since it worked in my sister's MBP mid 2009.
I also got some 2x4G of mushkin RAM (996644) for the computer. This is not apple certified but fits all the required specifications. The guy at the store told me that apple approved memory is the same thing just tested on a mac giving them an excuse to charge mor for it so this saved me six bucks. I tried installing both the hard drive and the ram and I got a POST error of one beep which means a RAM problem. I reinstalled the ram and instead of a POST error I got a black screen with no sounds. The LED was on. I put the old RAM in and it worked letting me install the OS. The hard drive had problems so I took it out, put the old one back in and the new RAM in. Same black screen.
Is there any solution here, or is the RAM defective and should I get a new chips?

If the old RAM works and the new does not, it makes no sense to keep it. The two most reliable sources for MBP RAM are OWC and Crucial.
Sometimes inexpensive RAM does work but as you can see what you have is a lemon. To a degree the sales person was correct, biut only that Apple does charge a lot for the RAM they sell. I suggest spend a bit more and get the afore mentioned RAM. If you search Amazon.com, the Crucial prices are quite good,
The RAM specifications for a 2010 MBP are: 204-pin PC3-8500 (1066 MHz) DDR3 SO-DIMM.
Ciao.

New RAM problems with my Dual G4 1.25 MDD

Howdy I've had my Dual G4 1.25 MDD for 2 years and love it. I got it with 1GB RAM, thinking I was set. For Christmas I wanted to Upgrade the RAM to 2GB. from My PowerMac G4 Manual I knew I needed 2x 512MB PC2700 DDR333 CL2.5 SDRAM DIMM's.
I went to DealRam (part of DealMac) and found 18004memory.com The price seemed great $39 per stick. I ordered it and within a week got 2x 512MB DIMM's. Problem was it was the Wrong RAM spec. I tried that RAM in my Mac 30 different ways and Everytime the computer either wouldn't boot, or it would suffer Kernel Protection Faults. One time it did boot up but the RAM only recognized as 2x 256MB DIMM's. I called the company, got an RMA and returned the RAM, this time they sent me 2 replacement DIMM's.... for a POWERBOOK, SO-DIMM's. I returned it again and finally Got from them the
2x 512MB PC2700 DDR333 CL2.5 SDRAM DIMM's. They call it Hyperspeed RAM. Anywho, I powered down let the system cool over night and in the morning, popped it open, put the RAM in the 2 open slots DIMM2/J23 & DIMM3/J20. closed it back up and powered up. Everything was snappier, the boot was quicker and I checked About this Mac, it says 2GB. Apple System Profiler showed all 4 DIMM's and I thought everything was fine.
Computer ran great for hours, no issues. Everything seemed quicker. Computer went to sleep overnight, next day woke from sleep and Tried to use iTunes and during an extensive sort for Songs, the system Locked up. Nothing would work. Had to force restart. this time I tried to Run my favorite online Game, WoW and after it loaded and I started to play, within 5 mins the whole game locked up. The audio sound went into a sort of Loop, I couldnt force quit and had to force reboot. This happened several times. I finally decided to Run the Apple Hardware Test. The Quick test locked up after running 2mins. I let it sit for 1hr just in case it was still doing something and the progress bar and time never progressed. So i forced reboot, ran Test again this time as Extended test. at 8 min & 31 sec the test stopped and I got an Error Code, this time I wrote it down "2MEM/2/4: DIMM3/J20."
I guess that DIMM failed. I shutdown, popped open case, and removed DIMM3/J20 leaving the Original 1GB RAM and One of the 512MB Upgrades. I rstarted the Test again and Ran the Extended Test once more. It ran for 27mins & 24 secs and everything passed. So. 1.5GB is better than just 1GB. I powered down and powered back up to try and play WoW. Within 5 mins of loading game to play, everything locked up again.
So I took both of the new RAM out and left the Original 1GB RAM and ran Test everything was great no Errors. Rebooted, and went onto WoW again and was able to play for several hours. I quit game and shut down for night.
I have since Tried the 2x 512MB DIMM's in over 10 different variations in the computer with and without the original RAM and everytime I run a high end program or game (WoW, iTunes, and Photoshop), I get lock ups, crashes, and other screen weirdness.
I dont want to have to Return the Memory again. I am already out over $15 from s/h with RMA's.
PLEASE Any ideas what to do?
1 thing I noticed the RAM gets very very hot, when I've powered down tand removed the new RAM. I wonder if there is a cooling issue?
Anytime I put the Original 1GB RAM in, I dont have problems!

Hi lz3broc,
Sounds very much like faulty RAM to me, I'm afraid. I'm not sure about the temperature it's running at, but if the surrounding DIMMs aren't having a problem then I would definitely point the finger at those new memory sticks not being up to scratch.
If you were convinced it was temperature related then you could always try putting heat spreaders on the memory to help with cooling, but as these stick (semi-permanently) to the RAM then you would never be able to return them.
My personal opinion is that you should send the RAM back and buy two new DIMMs from Crucial Technology. I only ever buy RAM made by them and I've never had a problem with it - it's the same stuff Apple themselves generally use and works a charm every time. Probably not the news you wanted to hear, but that's probably the only way you're going to get a stable machine with 2GB RAM.
Hope that helps,
Andy.
PowerMac G4 Dual 1.50GHz Mac OS X (10.4.4) Liquid Cooled

Ram related kernel panics on a MBP (ram used to work, hardware errors-)

hello all
i have a 2.2GHZ intel core duo 2007 MBP, which once ran Tiger and is now running 10.6.3
I had the NVDIA graphic card break down associated with such models, and it was replaced thanks to the extended care plan, here in Paris, so the logicboard is new- I also got a (technician installed) new HDD, and snowleopard
I originally had the 2 1Gig ram, but 1st got an extra 2Gb of danelec ram, and finally another 2GB- it ran fine for a couple year or so-
then, a few months back I recently started getting kernel panics, on tiger- I fist thought they were HDD related, got a new drive installed by a technician, switched to snow leopard-
yet they continue, and they're apparently RAM related, yet what is odd is that they can be reproduced with any RAM combination involving 2 sticks- the original apple 1Gb + any of the two GB ram sticks, the 2GB ram sticks together in any slot-- it's all the same, the screen goes grey and i'm told to shut down the computer
with one ram stick it works, this avoids the issue- but not always
i've moved the ram around, checked the slots, reset the PRAM,yet the issue is still there.
now i know that I should be using paired ram, and will do so in the next coming months when I can afford it- yet what has happened to make the make the MBP seemingly refuse two sticks of RAM when it didn't before ? are the two sticks dead ? or is there an issue with the slot ?
I'd also need to know that this is not a logicboard issue if it's possible- the logic board was changed due to the NVDIA bug, so it's a year old or so-
I'm running it on the 2GB danelec as I type, no issue, the samsung ram works as well, and so does the 1GB apple ram, in any slot, yet two slots of ram causes the kernel panic crash- the area near the ram slot also seems to get very hot-
I ran the hardware test yesterday, booting from the tiger dvd, which was difficult (possible drive issue)
finally managed to boot into hardware test mode (must be a superdrive issue)
running an extended test with the 4GB of ram in there
first pass found an error :
4MEM/9/40 000 000 : bc13950
running the extended testing
extended testing (1h39 min)
no errors found
ran another quick test
error
4MEM/9/40 000 000 : 6b506C4
another quick test :
no trouble found
another : no trouble found
and a last pass : no trouble found
but i did have two errors...
looking the errors up online didn't give anything so far, any clue as to what might be wrong here ? the RAM used to work fine (i've been using these two sticks for over two years), the kernel panics started happening on tiger- got a new HD drive a month ago, installed snow leopard, - used disk warrior and disk utilities, reset the PRAM and did the other tests and it continues- wether i'm running the computer from the internal drive or an external firewire drive-
running the hardware test, i also got two error messages, but on some passes only
if i look into the RAM status through about this mac, it says it's ok - what's odd is that the hardware test found errors, but not systematically----- I'd really like to know what the error message mean, can anyone help ?
i'm getting more and more kernel panics, unfortunately i live in France, so things are slightly less simple than they would be in other places customer servicewise- ie it might not be as simple as showing up at the new apple stores with this 2007 machine--
I need a stable machine to work on and really can't afford repairs at the moment
i'm really stuck with this, my finances got sucked into the last HDD upgrade (got it done by an official apple retailer, ICLG here in Paris, cost me 300 euros), and I thought things would be stable for a while since the logic board was changed (free of charge, which was a great relief) less than a year ago due to the nvdia bug- and now here I am with this--
anyway, here's the last kernel panic report i got, thanks in advance for your help
ben
Interval Since Last Panic Report: -28202 sec
Panics Since Last Report: 6
Anonymous UUID: FD865E22-C8DD-4791-889D-B5E5B374745E
Tue May 25 18:53:11 2010
panic(cpu 1 caller 0x55507c): "!pageList phys_addr"@/SourceCache/xnu/xnu-1504.3.12/iokit/Kernel/IOMemoryDescriptor.cpp:1 412
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x36413718 : 0x21b449 (0x5ce420 0x3641374c 0x2238a5 0x0)
0x36413768 : 0x55507c (0x5d7af8 0x320 0x36a20b4 0x320)
0x364137e8 : 0x54c208 (0x5f03300 0x3 0x560a200 0x80)
0x364138c8 : 0x54c733 (0x560fd80 0x80 0x54c81c 0x54c94c)
0x364138f8 : 0x129e3ba (0x560fd80 0x36413960 0x36413948 0x36413968)
0x36413988 : 0x12a7d67 (0x560a300 0x5f03300 0x0 0x1000)
0x364139d8 : 0x12a8edb (0x560a900 0x560a300 0x602d100 0x0)
0x36413ab8 : 0x1281448 (0x560a900 0x602d100 0x36413b28 0x36413b24)
0x36413b58 : 0x12a8c63 (0x560a900 0x5e59700 0x2 0x0)
0x36413bb8 : 0x12a9716 (0x560a900 0x560a300 0x36413be8 0xed5570)
0x36413c28 : 0x1298939 (0x560a900 0x36413c5c 0x0 0x54c94c)
0x36413c88 : 0x1296569 (0x560dc00 0xffc1 0x36413da8 0x36413cb8)
0x36413cc8 : 0xedc2cf (0x560dc00 0xffc1 0x36413da8 0x36413d08)
0x36413d28 : 0xebec0e (0x560ca40 0xffc1 0x36413da8 0x36413d68)
0x36413d88 : 0xebedb8 (0x54a2000 0xffc1 0x16 0x305c420c)
0x36413e48 : 0xf0d9f0 (0x54a2000 0x305c420c 0x6 0x3)
0x36413ea8 : 0xf02da0 (0x553cf40 0x1 0x5466c58 0x0)
0x36413f08 : 0x5478e3 (0x54af000 0x553a700 0x1 0x5413300)
0x36413f58 : 0x546914 (0x553a700 0x603969c 0x36413f88 0x227155)
0x36413f88 : 0x546d6e (0x5413cc0 0x6039680 0x36413fc8 0xffffffff)
0x36413fc8 : 0x29e6cc (0x5413cc0 0x0 0x10 0x5a05904)
Kernel Extensions in backtrace (with dependencies):
com.apple.iokit.IOFireWireSerialBusProtocolTransport(2.0.1)@0x12a6000->0x12aafff
dependency: com.apple.iokit.IOFireWireFamily(4.2.6)@0xeb7000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.6.2)@0x127b000
dependency: com.apple.iokit.IOFireWireSBP2(4.0.6)@0x1295000
com.apple.iokit.IOFireWireSBP2(4.0.6)@0x1295000->0x12a5fff
dependency: com.apple.iokit.IOFireWireFamily(4.2.6)@0xeb7000
com.apple.iokit.IOSCSIArchitectureModelFamily(2.6.2)@0x127b000->0x1294fff
com.apple.driver.AppleFWOHCI(4.5.7)@0xefa000->0xf1ffff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x92d000
dependency: com.apple.iokit.IOFireWireFamily(4.2.6)@0xeb7000
com.apple.iokit.IOFireWireFamily(4.2.6)@0xeb7000->0xef9fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10D578
Kernel version:
Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
System uptime in nanoseconds: 38155557254
unloaded kexts:
(none)
loaded kexts:
com.paceap.kext.pacesupport.snowleopard 5.7.2 - last loaded 34201995231
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleHDA 1.8.4fc3
com.apple.driver.AppleUpstreamUserClient 3.3.2
com.apple.driver.AudioAUUC 1.4
com.apple.driver.AirPort.Atheros 422.19.10
com.apple.driver.AppleGraphicsControl 2.8.56
com.apple.driver.AppleBacklight 170.0.16
com.apple.driver.AppleLPC 1.4.11
com.apple.GeForce 6.1.0
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.kext.AppleSMCLMU 1.5.0d1
com.apple.DontSteal_Mac_OSX 7.0.0
com.apple.driver.AudioIPCDriver 1.1.2
com.apple.driver.AppleIntelYonahProfile 14
com.apple.driver.AppleIntelPenrynProfile 17
com.apple.driver.AppleIntelNehalemProfile 11
com.apple.driver.AppleIntelMeromProfile 19
com.apple.driver.ACPISMCPlatformPlugin 4.1.1d0
com.apple.driver.AppleUSBTrackpad 1.8.1b1
com.apple.driver.AppleUSBTCKeyEventDriver 1.8.1b1
com.apple.driver.AppleUSBTCKeyboard 1.8.1b1
com.apple.driver.AppleIRController 303
com.apple.driver.CSRHIDTransitionDriver 2.3.1f4
com.apple.driver.initioFWBridge 2.5.3
com.apple.driver.StorageLynx 2.5.3
com.apple.driver.Oxford_Semi 2.5.3
com.apple.driver.LSIFW500 2.5.3
com.apple.driver.IOFireWireSerialBusProtocolSansPhysicalUnit 2.5.3
com.apple.iokit.SCSITaskUserClient 2.6.2
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.IOAHCIBlockStorage 1.6.1
com.apple.driver.AppleUSBHub 3.9.6
com.apple.iokit.AppleYukon2 3.1.14b1
com.apple.driver.AppleAHCIPort 2.1.1
com.apple.driver.AppleFWOHCI 4.5.7
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBEHCI 3.9.6
com.apple.driver.AppleUSBUHCI 3.9.6
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleACPIButtons 1.3.2
com.apple.driver.AppleSMBIOS 1.5
com.apple.driver.AppleACPIEC 1.3.2
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 104.3.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 104.3.0
com.apple.driver.AppleHDAPlatformDriver 1.8.4fc3
com.apple.driver.AppleHDAHardwareConfigDriver 1.8.4fc3
com.apple.driver.DspFuncLib 1.8.4fc3
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.iokit.IO80211Family 310.6
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.nvidia.nv50hal 6.1.0
com.apple.NVDAResman 6.1.0
com.apple.iokit.IONDRVSupport 2.1
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.0
com.apple.iokit.IOBluetoothSerialManager 2.3.1f4
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.IOAudioFamily 1.7.6fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.AppleHDAController 1.8.4fc3
com.apple.iokit.IOGraphicsFamily 2.1
com.apple.iokit.IOHDAFamily 1.8.4fc3
com.apple.driver.AppleSMC 3.0.1d2
com.apple.driver.IOPlatformPluginFamily 4.1.1d0
com.apple.driver.CSRUSBBluetoothHCIController 2.3.1f4
com.apple.driver.AppleUSBBluetoothHCIController 2.3.1f4
com.apple.iokit.IOBluetoothFamily 2.3.1f4
com.apple.iokit.IOUSBHIDDriver 3.9.6
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.2
com.apple.driver.AppleUSBMergeNub 3.9.6
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.0.1
com.apple.iokit.IOFireWireSBP2 4.0.6
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.2
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.driver.AppleFileSystemDriver 2.0
com.apple.iokit.IOATAPIProtocolTransport 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.2
com.apple.iokit.IOUSBUserClient 3.9.6
com.apple.iokit.IONetworkingFamily 1.9
com.apple.iokit.IOAHCIFamily 2.0.3
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBFamily 3.9.6
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOHIDFamily 1.6.2
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 283
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3.2
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.2 GHz, 2 GB, SMC 1.16f11
Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 128 MB
Memory Module: global_name
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x87), Atheros 5416: 2.0.19.10
Bluetooth: Version 2.3.1f4, 2 service, 2 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: SAMSUNG HM250HI, 232,89 GB
Parallel ATA Device: HL-DT-ST DVDRW GSA-S10N
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd400000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8205, 0x1a100000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x021b, 0x5d200000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000
FireWire Device: OXFORD IDE Device 1, Macpower, Up to 400 Mb/sec
FireWire Device: OEM ATA Device 00, OEM, Up to 800 Mb/sec

crashes are continuing - can anyone help out ?
thanks
ben
Interval Since Last Panic Report: 1184223 sec
Panics Since Last Report: 15
Anonymous UUID: FD865E22-C8DD-4791-889D-B5E5B374745E
Fri May 28 21:24:56 2010
panic(cpu 0 caller 0x2a8ac2): Kernel trap at 0x0027a72b, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000004, CR3: 0x00100000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x0000007e, ECX: 0x091f0000, EDX: 0x00000000
CR2: 0x00000004, EBP: 0x56f43378, ESI: 0x048077c4, EDI: 0x00000000
EFL: 0x00010297, EIP: 0x0027a72b, CS: 0x00000008, DS: 0x0d8c0010
Error code: 0x00000002
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x56f43178 : 0x21b449 (0x5ce420 0x56f431ac 0x2238a5 0x0)
0x56f431c8 : 0x2a8ac2 (0x590478 0x27a72b 0xe 0x590642)
0x56f432a8 : 0x29e9a8 (0x56f432c0 0x20b35a20 0x56f43378 0x27a72b)
0x56f432b8 : 0x27a72b (0xe 0x48 0x56f40010 0x10)
0x56f43378 : 0x26c7dc (0x48077c4 0x0 0x6a300dc 0x6a300dc)
0x56f433c8 : 0x26cfd8 (0xd8c6f38 0x0 0x56f43458 0x2339ff)
0x56f433f8 : 0x26d256 (0x47ee6000 0x0 0x0 0x0)
0x56f43418 : 0x26de86 (0xd8c6f40 0x11000 0x0 0x25bdc1)
0x56f43458 : 0x260c3b (0xd8c6f38 0x30f383c 0x0 0x11000)
0x56f43588 : 0x260e32 (0x47ef7000 0x0 0x1 0x0)
0x56f435c8 : 0x259bfe (0x2ba8d74 0x47ee6000 0x0 0x47ef7000)
0x56f43608 : 0x220273 (0x2ba8d74 0x47ee6000 0x10005 0x53c5)
0x56f43628 : 0x22042a (0x47ee6000 0x10005 0x995720 0x10000)
0x56f43648 : 0x9931fa (0x47ee6000 0x10005 0x8115380 0x47ee6004)
0x56f43728 : 0x994941 (0x20000 0x0 0x10000 0x1)
0x56f437b8 : 0x994fb2 (0x9858304 0x20000 0x0 0x10000)
0x56f43c28 : 0x3105ea (0x87c268c 0x8077b00 0x7f1ec24 0x20000)
0x56f43c88 : 0x3121dd (0x20000 0x0 0x10000 0x0)
0x56f43d58 : 0x423e1a (0x56f43dfc 0x56f43dbc 0x87747e0 0x2f797261)
0x56f43dd8 : 0x2fafad (0x56f43dfc 0x3 0x56f43e28 0x57c50e)
0x56f43e28 : 0x2efffc (0x87c268c 0x56f43ec4 0x0 0x56f43f54)
0x56f43e78 : 0x49444a (0x86b6b20 0x56f43ec4 0x1 0x56f43f54)
0x56f43f18 : 0x494a8d (0x56f43f54 0x86b6b20 0xb0183f64 0x0)
0x56f43f78 : 0x4ec84e (0x87cf2a0 0x88fbd90 0x88fbdd4 0x0)
0x56f43fc8 : 0x29eef8 (0x893ee20 0x0 0x10 0x0)
Kernel Extensions in backtrace (with dependencies):
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0.0d1)@0x991000->0x99 6fff
BSD process name corresponding to current thread: firefox-bin
Mac OS version:
10D578
Kernel version:
Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
System uptime in nanoseconds: 2721283483111
unloaded kexts:
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.2 (addr 0x56c88000, size 0x98304) - last unloaded 1855762560735
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 1269444306258
com.apple.driver.AppleHDA 1.8.4fc3
com.apple.driver.AudioAUUC 1.4
com.apple.driver.AirPort.Atheros 422.19.10
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleUpstreamUserClient 3.3.2
com.apple.DontSteal_Mac_OSX 7.0.0
com.apple.GeForce 6.1.0
com.apple.kext.AppleSMCLMU 1.5.0d1
com.apple.driver.AudioIPCDriver 1.1.2
com.apple.driver.ACPISMCPlatformPlugin 4.1.1d0
com.apple.driver.AppleIntelMeromProfile 19
com.apple.driver.AppleLPC 1.4.11
com.apple.driver.AppleBacklight 170.0.16
com.apple.driver.AppleUSBTrackpad 1.8.1b1
com.apple.driver.AppleUSBTCKeyEventDriver 1.8.1b1
com.apple.driver.AppleUSBTCKeyboard 1.8.1b1
com.apple.driver.AppleIRController 303
com.apple.iokit.SCSITaskUserClient 2.6.2
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleFWOHCI 4.5.7
com.apple.iokit.IOAHCIBlockStorage 1.6.1
com.apple.driver.AppleAHCIPort 2.1.1
com.apple.iokit.AppleYukon2 3.1.14b1
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBHub 3.9.6
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleUSBEHCI 3.9.6
com.apple.driver.AppleUSBUHCI 3.9.6
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleACPIButtons 1.3.2
com.apple.driver.AppleSMBIOS 1.5
com.apple.driver.AppleACPIEC 1.3.2
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 104.3.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 104.3.0
com.apple.driver.DspFuncLib 1.8.4fc3
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.iokit.IO80211Family 310.6
com.apple.driver.AppleHDAController 1.8.4fc3
com.apple.iokit.IOHDAFamily 1.8.4fc3
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.0
com.apple.iokit.IOBluetoothSerialManager 2.3.1f4
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.IOAudioFamily 1.7.6fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.IOPlatformPluginFamily 4.1.1d0
com.apple.driver.AppleSMC 3.0.1d2
com.apple.nvidia.nv50hal 6.1.0
com.apple.NVDAResman 6.1.0
com.apple.iokit.AppleProfileFamily 41
com.apple.iokit.IONDRVSupport 2.1
com.apple.iokit.IOGraphicsFamily 2.1
com.apple.driver.CSRUSBBluetoothHCIController 2.3.1f4
com.apple.driver.AppleUSBBluetoothHCIController 2.3.1f4
com.apple.iokit.IOBluetoothFamily 2.3.1f4
com.apple.iokit.IOUSBHIDDriver 3.9.6
com.apple.driver.AppleUSBMergeNub 3.9.6
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.2
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOATAPIProtocolTransport 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.2
com.apple.iokit.IOAHCIFamily 2.0.3
com.apple.iokit.IONetworkingFamily 1.9
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBUserClient 3.9.6
com.apple.iokit.IOUSBFamily 3.9.6
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOHIDFamily 1.6.2
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 283
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3.2
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.2 GHz, 4 GB, SMC 1.16f11
Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 128 MB
Memory Module: global_name
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x87), Atheros 5416: 2.0.19.10
Bluetooth: Version 2.3.1f4, 2 service, 2 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: SAMSUNG HM250HI, 232,89 GB
Parallel ATA Device: HL-DT-ST DVDRW GSA-S10N
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd400000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x021b, 0x5d200000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8205, 0x1a100000

Help! Installed new RAM and now screen isn't coming on!

Hi
I'm in a bit of a mess and would be grateful for any help with this one:
I have a Powerbook G3 500mhz Pismo that currently has a 512mb card in the top slot (Kingston PB100/512) that I installed about two years ago with no problems and an original 128mb in the bottom. At Christmas I bought another 512mb for the bottom slot – (Kingston KTA-PBG4/512 - This one is smaller than the first but it was the one reccomended by Kingston on their website for the Pismo).
I have just got round to installing it after backing up my system and I have good instructions on how to do it (I have replaced the HD two years previous with no problems)
Firstly I have to mention that just before I changed the RAM the laptop fell from a small stool (about 1.5feet high) onto carpet due to the unbalancing effect of taking out the battery/CD ROM. It landed on its edge where the power socket is. I immediately put it back together and turned it on to make sure it was ok - it came on fine and there were no problems visually, mechanically or otherwise, so I carried on with the installation.
I installed the new 512mb card in the bottom slot and re-assembled but when I turned it on the screen remained black! From the computer itself, however, it sounded as if it had started up ok – there was the chime and the familiar sound of the hard drive at start up.
To troubleshoot I removed the new RAM card and put back the old RAM as it was – this made no difference. I checked to see if the processor board was firmly in place or if I had dislodged any connectors by mistake within the area that I had worked but this made no difference. I also tried to re-set the parameter RAM and this made no difference.
Because the laptop took a small knock prior to installation, I am not sure if that has caused something to come loose or damage of some kind but as I mentioned I did test it immediately and it worked, so it’s either a delayed reaction or the new RAM card has caused it. – (As mentioned there is a difference between the two 512 cards in both name and size but the smaller size of the newer one I assume just reflects advancement in technology and it was reccomended by Kingston!)
If anybody has any advice on this I would be very grateful (and also, if anybody can point me in the direction of instructions on how to take the pismo apart to get to the connections to the screen that would be great – in case I have to do it)
Many Thanks Barry
PowerBook G3500mhz Mac OS X (10.3.9)

SpottyFox,
It sounds like you are properly seating the CPU card from your description, so I don't believe that is your problem. I am glad you checked the pins (I should have mentioned that as the next step if the reseating did not help). I cannot answer whether anything was damaged from your description of the pins; I have read where others have realigned bent pins with success so maybe your mileage will vary.
Start up your Pismo, then shine a flashlight directly into the display; if you can see data being written to the display, just the backlight is refusing to light. If this is the case, check the inverter board connections. The inverter is under the clutch cover and powers the fluorescent backlight in the display. Enlarge the bottom picture in this link to see the inverter:
http://www.ifixit.com/Guide/Mac/PowerBook-G3-Pismo/Inverter-Page-10-Inverter
Check connections at each end of the inverter. Disassembly is not as extensive as this guide suggests. Support the back of the display, then remove the main battery, optical drive, lay the keyboard on its face on the palm rest, heat shield, and clutch cover...that's it.
http://www.ifixit.com/Guide/6.0.0.html
You might also connect the Pismo to an external display; failure here would suggest a more serious problem.

Installed new RAM now computer wont start up

I just installed 2GB of RAM in my iMac and removed the 512mb card it had originally.when i pressed the power button it beeps fast a few time then the fan starts working really fast. The screen doesnt turn on only the sleep light blinks as the fan runs. I replaced one of the new cards with the original 512mb card and it starts but when i check the memory the slot where the new 1GB card appears "empty" why could this be? did i install incorrectly?

When you install new RAM you have to push much harder than you think you should. You won't damage the RAM, but you have t give a mighty push to seat it, make sure you hear a click.

Strange issue with RAM upgrade: It works but it doesn't! Please help.

Hello Everyone,
I have a very strange issue with my iMac since upgrading my RAM from 4 to 12 gig. When I first installed the new RAM it booted up and ran great. The next time I went to boot the iMac up it swtiched on but didn't get as far as the first white boot up screen. I tried turning it off and on a few times using the power on/off button but still no success. I decided to remove the RAM and reseat it. The computer then booted up again fine. Here's the problem though: when I went to switch my iMac on the next day it wouldn't boot up. Again, I took the RAM out and put it back in and the iMac booted up fine. I've checked the status of the RAM in the system profiler and it reports that everything is OK. So, I'm at a loss. Obviously, I don't want to go through this process every time I want to start up my Mac. Any ideas/solutions would be very gratefully received.
Many thanks in advance.

I completely agree with you. It will be one of the 3 issues you outline. The machine was bought brand new and has never given me a problem. It is just the introduction of the new RAM that has started a problem. However, I did just risk a restart and it booted up fine. I don't know if a restart is any different to shutting down and then pressing the on/off button to start the computer. Maybe my last reseating has done the trick or maybe my thinking is flawed because restarting involves a different process to booting up by pressing the on/off button. I don't know.
In the part of the world I'm sitting in it's night time now so I will leave the diagnostics running and check the results in the morning. I hope the issue is now resolved anyway. This sort of thing takes me back to my dark PC days although in this case I know it's probably not the Mac's fault.
Thanks again. Very much appreciated.

Suspend to ram doesen't work

Hi. I would like to ask for your advice. I have problem with suspend to ram. In order to have nvidia drivers i had to install newest kernel, 3.12.xx. I found that suspend to ram doesen't work. I put my computer in sleep mode by typing
sudo systemctl suspend
, everything works, computer goes in sleep mode but after resume from it, after wake up i have only black screen with unblinking cursor on the left upper corner of screen. I can't kill x, can't do anything in tty, only hard reset.
I removed nvidia drivers in order to check older kernel, and found that with nouveau drivers kernel 3.9 works, i can suspend and resume. I did another thing. I installed clean Arch, updated it with pacman -Syu, and installed nvidia drivers - the same problem with resuming from suspend. So on fresh and updated system i removed nvidia again, installed old kernel with nouveau - suspend works with resume.
Could somebody help me? Maybe you can point me to a solution? I would like to have nvidia drivers installed and working suspend with resume from suspend to ram.
I checked pm-suspend.log:
http://pastebin.archlinux.fr/478611
I don't see anything wrong here. I asked on polish site about kernel 3.12, and with Ubuntu they said it works. Why on Arch only kernel 3.9 works with resuming from suspend to ram and olny when there are no nvidia drivers (because they need new kernel, i could even use old but i'm not so exprienced to compile kernel myself, won't do that, and with downgrade script from AUR i didn't found nvidia driver for older kernels. There are old kernel, even 3.0.xx but only nvidia drivers from 325 that they need 3.12 kernel).
My spec is AMD X4 955, NVIDIA GTX260, 4GB ram. Arch is x32, kernel 3.12.5.1 (other don't work with resume too, only 3.9 with nouveau).
Last edited by firekage (2013-12-22 12:33:45)

I will try it, but i don't think that this "fix" will really help me - i installed newest driver, installed binary driver from nvidia website on kernel 3.9.8.1 and resuming from suspend to ram works. With newer kernel it just doesen't so if this would be a nvidia MSI problem than i would have it also on kernel 3.9.8.1 where i installed newest drivers ( i installed binary because i don't know which package from aur would work with this kernel, and on aur thare are only drivers from 325, no older).
Edit - just as i said. Doesen't work. It is not related to nvidia because it happens on nouveau. It is kernel fault.
Last edited by firekage (2013-12-25 02:25:34)

[SOLVED} Suspend to ram does not work (with sleep, s2ram, pm-utils)

Hi.
I would like to ask for one thing: i can't suspend to ram or resume from suspend to ram.
I treid to check over www in order to find some help, some solutions, and how to fix that. Unfortunately, i found these:
https://forums.opensuse.org/showthread. … 13-2/page2
https://bugzilla.opensuse.org/show_bug.cgi?id=913105
https://forums.opensuse.org/showthread. … S-13-1-x64
Bug 91921 - WD 2TB Caviar black causes hard lock on resume S2RAM
https://bugzilla.kernel.org/show_bug.cgi?id=91921
In fact, when i was researching of this problem i wanted to check if my graphic card and memory are failing so a did few changes (removed memory stick and so one) but in doing this i removed almost all of my hard disk drives because i didn't want to hurt them with many reboots or resets.
What did i find? It is strange, kernel version is not important because i checked most of them.
I removed 2x2TB Seagate F14 series along with 4x3TB WD Green. Then i checked s2ram, it went to suspend, and resumes correctly. Everything works. I put it to sleep with s2ram -f -a 1. Works
I attached my 4x3TB WD Green drives. I put computer to sleep with s2ram...it causes hard lock, black screen, i could do only poweroff by powerbutton. s2ram -f -a 1 causes freez. Sometimes, but not constantly, s2ram -f -a 3 -p is being able to suspend...(mostly it does a freez, hard lock computer) but sometimes it is able to put it to a sleep, but resume just freezes everyting - no blinking cursor, no blinking num lock led and so on.
I know that you would suggest me to check logs - this is the main problem. Logs for pm-suspend works when i suspend or resume without WD drives attached. When i have them connected, i'm not able to check pm-logs because computer hangs, freezes and logs are not being stored/writed to pm-suspend.log and pm-powersave.log.
Could somebody help? Point me to a solution? I can't check logs because there are not any when freezing occurs. I checked openSuse thread and many others and for other systems there were some kernel fixex, patches.
They wrote that WD blacks are at fault because they don't have APM. Well, in fact my WD Green have APM with very aggresive factory settings: they park heads over 8 seconds not being used. I disabled it in firmware but disabling it is not the point and not the problem. People have the same problem even with APM and parking heads on other WD drives, i found it that some have it with WD Red's drives and even with very old 320GB WD Blue series - what is more funny, i have 640GB AAKS blue from WD and with this drive i can suspend or resume - APM on this drive is also unavilable, like in Green series because i changed it with wdidle with prebootable cd. I can't supend or resume with 3TB WD Greens.
BTW - suspend to disk, with pm-utils and uswsusp works ok, in 100% every time. (i had to add "shutdown method = shutdown" to /etc/suspend.conf from uswsusp package).
On Windows machine it works. Can suspend, can resume, can hibernate.
Last edited by firekage (2015-03-07 03:27:28)

Hm, sometimes i found myself astonished because some things just does not work at all on one machine, while the other one has no problem at all. I was trying to find why suspend to ram won't work at all...and while i was searching i found one topic that was leading to upower dbus. Similar problem with upower i found, by coincidence, on Manjaro forum.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
this command above returns all the time:
Error org.freedesktop.DBus.Error.UnknownMethod: Method "Suspend" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I tried this:
sudo systemctl enable acpid.service
sudo systemctl --system daemon-reload
sudo systemctl restart systemd-logind
As soon as i enabled and started acpid.service...my supend to ram, from kde, works like a charm, without graphic problem, or freezing.
There is few question: why on my desktop suspend doesen't work out of the box, when even archwiki says it should? Why on my netbook machine (Acer AOD270) that has the same package installed it works out of the box? Why on my desktop machine acpid.service was not enabled, was not started and was not running while on the notebook it does?
Anyway...i fixed it by a big coincidence because on Fedora forum somebody has problem with suspend to ram with nvidia GTX750 and this card was new like my card (GTX660). He posted the same problem with upower that i posted in quotes and because of this i found another thing on Manjaro forum and that was it!
BTW - this problem, i now think, is not related to my WD drives because it works with them. I think that there was another one ugly thing that broke my suspend to ram ability - bios of my motherboard (so called uefi bios with support for old one) has no option for S1-S5 stated (like the previous motherboards had) and only have ASPM...and ASPM is in my opinion broken but i will try to veryfi it one again later.
Last edited by firekage (2015-03-07 03:29:20)

Power Mac G5 Refuses to start with new RAM!

I have a Power Mac G5 Dual 1.8GHz June 2004. I know I read somewhere online that it takes 1GB sticks of RAM, and that it has to be dual channel. I went to Best Buy today and got myself 2 sticks of 1GB DDR PC3200 "Compatible with 400/333/266MHz" Dimms, and installed them in pairs. When I start them with or without my old memory, my mac starts up, makes no noises, but the fromt white LED light blinks 2 times, and does this repeadedly until I shutdown and install the old 512MB sticks. I need to get this new RAM to work in here, I just paid $112 total for 2 sticks, and I am not ready to go back to the store yet. Is there something I am missing here? Something I am not doing right?
New RAM Specs:
1GB DDR Dimm,Q PNY Technologies, PC3200 "Compatible with 400/333/266MHz"
I need to get this to work on my machine! Thanks for any help.

Is there something I am missing here?
Not all RAM is created equal and seldom does over the counter PC RAM work in a G5.
Buy and install ONLY guaranteed Mac compatible RAM.
http://eshop.macsales.com/shop/memory/PowerMac-G5-Memory
BTW, you paid too much.
When I start them with or without my old memory, my mac starts up, makes no noises, but the fromt white LED light blinks 2 times,
That means "Incompatible RAM types".
http://support.apple.com/kb/ht1547
I am not ready to go back to the store yet.
Go back to the store.

Content Search Web Part - Sorting not working

I recently tried the new Content Search Web Part for which i see tremendous potential. I wanted to use it to show a certain type of pages and that was not a problem (i added a url as the source where i got the pages from). I mapped the correct fields so
that it showed image, title and modified date. I then tried the advanced mode and told it to sort by the modified date, however any way I tried to apply this sort it just would not save my settings and reverted back to the default sorting. Is there anything
else you need to do to get Sorting to work?
/Anders

I hadn't tried looking with REST, but that's a good suggestion.
In the interim, I found this on TechNet:
http://technet.microsoft.com/en-us/library/jj679902.aspx#BKMK_MapCPtoRefinableMP<o:p></o:p>
When you search for a crawled property, you may find two crawled properties
that represent the same content. For example, a site column of type Text named
Color will during crawl discover two crawled properties: ows_Color and
ows_q_TEXT_Color. Crawled properties that begin with either ows_r<four
letter code>, ows_q<four letter code>, or ows_taxId are automatically
created crawled properties. When you select a crawled property to map to a
refinable managed property, make sure that you don't map the automatically
created crawled property. Instead, always map the crawled property that begins
with ows_.
So clearly (as clearly as the doc makes it) I need to use ows_ArticleStartDate. I've made sure that crawled property is the one I'm using, but I'm still not seeing any effect.
As for the sorting model, that only seems to be relevant for Rank sorting, right?
M.
Sympraxis Consulting LLC -
Marc D Anderson's Blog - @sympmarc -
jQuery Library for SharePoint Web Services (SPServices)

New ram sort-of working?

Similar Messages

Maybe you are looking for