[kmkkid]

Hey,


I recently (like a month ago) purchased a new Intel imac 2.0 Ghz. It came with the standard 512MB of memory, and ran perfectly for that whole month, till I purchased a 1 GB stick of 'corsair' RAM. It took a few tries to get the ram to show up in System Profiler, because I guess it wasnt seated properly, then it ran perfect for a week or so, then BOOM panics every day or so. I tested the memory with techtol deluxe, and memtest, and also apple hardware test, ALL of them verify that the RAM is working properly. Could the RAM still be the cause?! Or did I muck up something else? I've done an archive and install, but the problem still persists. My panic log doesn't suggest anything specific extension wise, so I doubt it's any corrupt or defunct kernel extensions.

It's driving me mad, cause we all know how much of a pain it is to send things back when bought on the net, and I really hate taking the RAM out as the seating of the RAM takes quite some pressure and I'm scared of breaking the ram slots.


I also pondered the idea that maybe I had the mouse in a bad USB port, because I may have changed mouse and keyboard positions after installing the RAM, and it seems the computer would always crash while I was moving the mouse somehow.


Anyways if anyone has any idea of what could be happening, please help a fellow Mac guy out! I'll paste my panic logs, though I doubt anyone can understand it's gibberish.


TIA,

Chris

[kmkkid]

Most recent Panic.log after archive and install:

Code:

Mon Aug  7 21:09:29 2006
panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x4d01e44d, CR3: 0x00d2b000, CR4: 0x000006e0
EAX: 0x4d01e44d, EBX: 0x01641030, ECX: 0x03602ad0, EDX: 0x01641038
ESP: 0x4d01e44d, EBP: 0x1c7e3e98, ESI: 0x034e67d0, EDI: 0x00000001
EFL: 0x00010202, EIP: 0x0014126a, CS:  0x00000008, DS:  0x1c7e0010

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c7e3cf8 : 0x128b5e (0x3bc46c 0x1c7e3d1c 0x131bbc 0x0) 
0x1c7e3d38 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c) 
0x1c7e3de8 : 0x197c7d (0x1c7e3dfc 0x1c7e3e98 0x14126a 0x48) 
0x1c7e3df4 : 0x14126a (0x48 0x4a0010 0x10 0x1c7e0010) 
0x1c7e3e98 : 0x141649 (0x1641030 0x1 0x1c7e3eb8 0x34e67d0) 
0x1c7e3eb8 : 0x3250f7 (0x1641030 0x26 0x0 0x3ad03c) 
0x1c7e3f08 : 0x32528b (0x34e67d0 0x1c7e3f5c 0x1c7e3f4c 0x1) 
0x1c7e3f28 : 0x3464ac (0x34e67d0 0x1c7e3f5c 0x1c7e3f4c 0x1) 
0x1c7e3f78 : 0x36de6c (0x34e67d0 0x35f18ac 0x35f18f0 0x0) 
0x1c7e3fd8 : 0x197ff3 (0x3602d48 0x3602d48 0x1641030 0x4d01e44d) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0080be8

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

[kmkkid]

Panic.log before archive and install:

Code:

Thu Jul 27 05:05:56 2006
panic(cpu 1 caller 0x0019743C): interlock timeout for mutex 0x4285118
Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c7f3c20 : 0x128b5e (0x3bc46c 0x1c7f3c44 0x131bbc 0x0) 
0x1c7f3c60 : 0x19743c (0x3c1104 0x4285118 0x1 0x17e6ea) 
0x1c7f3c90 : 0x194e09 (0x4285118 0x246 0x1c7f3df0 0x161901) 
0x1c7f3ca0 : 0x161901 (0x4285118 0x0 0x0 0x3) 
0x1c7f3df0 : 0x19c868 (0x144e0c8 0xbffff000 0x0 0x3) 
0x1c7f3e70 : 0x197c6c (0x1c7f3e7c 0x1c7f0048 0x10 0x1c7f0070) 
0x1c7f3f34 : 0x11ce9f (0x388ac3c 0xc8 0x0 0x0) 
0x1c7f3f54 : 0x12450b (0xbffff8e8 0x0 0x388ac00 0xc8) 
0x1c7f3fb4 : 0x124604 (0x0 0x1 0x2c9b3000 0x2c9b3000) 
0x1c7f3fd4 : 0x197b19 (0x0 0x0 0x2fc8ac8 0x2c9b3000) Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

Thu Jul 27 22:11:43 2006
panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xfbac8d10, CR3: 0x00d49000, CR4: 0x000006e0
EAX: 0x00000001, EBX: 0x00002da4, ECX: 0x03ce8990, EDX: 0xfbac8d10
ESP: 0xfbac8d10, EBP: 0x1c80be28, ESI: 0x02e716e0, EDI: 0x00d4f148
EFL: 0x00010082, EIP: 0x001919e1, CS:  0x00000008, DS:  0x1c800010

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c80bc78 : 0x128b5e (0x3bc46c 0x1c80bc9c 0x131bbc 0x0) 
0x1c80bcb8 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c) 
0x1c80bd68 : 0x197c7d (0x1c80bd7c 0x1c80be28 0x1919e1 0x190048) 
0x1c80bd74 : 0x1919e1 (0x190048 0x37a0010 0x200010 0x1c800010) 
0x1c80be28 : 0x16121c (0x2e716e0 0x8fe29000 0x0 0x2da4) 
0x1c80bf78 : 0x19c5c6 (0x39f668c 0x8fe29000 0x0 0x5) 
0x1c80bfd8 : 0x197bbb (0x3ce8c08 0x3ce8c08 0x2da4 0xfbac8d10) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0080ad8

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

Mon Jul 31 05:30:38 2006
panic(cpu 0 caller 0x00351703): m_freem_list: m_nextpkt of m_next != NULL
Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c80bb84 : 0x128b5e (0x3bc46c 0x1c80bba8 0x131bbc 0x0) 
0x1c80bbc4 : 0x351703 (0x3dbf18 0x2ef68b0 0x1c80bc04 0x1970c8) 
0x1c80bc04 : 0x356ec3 (0x2e2d0e00 0x297 0x1c80bc44 0x23009e) 
0x1c80bc44 : 0x22cf59 (0x379d9d4 0x106e 0x1 0xe18d8b48) 
0x1c80be14 : 0x22217b (0x2e3bcd00 0x14 0x1c80be54 0x1f6c30) 
0x1c80be54 : 0x223bff (0x2e3bcd00 0x14 0x6 0x0) 
0x1c80bf64 : 0x21125d (0x2e3bcd00 0x2e3bcd00 0x42db5c 0x135798) 
0x1c80bfa4 : 0x1f7871 (0x3594204 0x2e3bcd00 0x2e3bcd34 0x1) 
0x1c80bfd4 : 0x197b19 (0x0 0x0 0x2f323b8 0x134aec) Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

Mon Jul 31 18:53:17 2006
panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0xffffffff, CR3: 0x00d49000, CR4: 0x000006e0
EAX: 0xffffffff, EBX: 0x0165f800, ECX: 0x02fc6850, EDX: 0x0165f808
ESP: 0xffffffff, EBP: 0x1c7f3d18, ESI: 0x1c7f3dbc, EDI: 0x03a38420
EFL: 0x00010206, EIP: 0x0014126a, CS:  0x00000008, DS:  0x1c7f0010

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c7f3b78 : 0x128b5e (0x3bc46c 0x1c7f3b9c 0x131bbc 0x0) 
0x1c7f3bb8 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c) 
0x1c7f3c68 : 0x197c7d (0x1c7f3c7c 0x1c7f3d18 0x14126a 0x2e40048) 
0x1c7f3c74 : 0x14126a (0x2e40048 0x1c7f0010 0x1c7f0010 0x1c7f0010) 
0x1c7f3d18 : 0x141649 (0x165f800 0x1 0x35536b0 0x2e6e648) 
0x1c7f3d38 : 0x121550 (0x165f800 0x1 0x2e6e654 0x11e3c9) 
0x1c7f3d58 : 0x138427 (0x2e44fa0 0x0 0x1c7f3d88 0x12ca81) 
0x1c7f3d88 : 0x152df6 (0x2e6e648 0x1c7f3dbc 0x0 0x0) 
0x1c7f3dd8 : 0x12b389 (0x362dfa4 0x3c313a4 0x0 0x0) 
0x1c7f3e18 : 0x124902 (0x362df00 0x0 0x28 0x1c7f3efc) 
0x1c7f3f28 : 0x193034 (0x1c7f3f54 0x0 0x0 0x0) 
0x1c7f3fd8 : 0x19814b (0x2fc6ac8 0x2fc6ac8 0x165f800 0xffffffff) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff688

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

Mon Jul 31 21:43:13 2006
panic(cpu 1 caller 0x0019CADF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000014, CR3: 0x00d49000, CR4: 0x000006a0
EAX: 0x035ef444, EBX: 0x00000000, ECX: 0x0c010000, EDX: 0x00000000
ESP: 0x00000014, EBP: 0x1c73bd48, ESI: 0x035ef438, EDI: 0x00000000
EFL: 0x00010293, EIP: 0x001640d5, CS:  0x00000008, DS:  0x1c730010

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c73bbe8 : 0x128b5e (0x3bc46c 0x1c73bc0c 0x131bbc 0x0) 
0x1c73bc28 : 0x19cadf (0x3c18e4 0x1 0xe 0x3c169c) 
0x1c73bcd8 : 0x197c7d (0x1c73bcec 0x1c73bd48 0x1640d5 0x190048) 
0x1c73bce4 : 0x1640d5 (0x190048 0x2e70010 0x2c9b0010 0x1c730010) 
0x1c73bd48 : 0x168cab (0x35ef438 0xc010000 0x0 0x1c73be08) 
0x1c73be28 : 0x160ea1 (0x1c73bf80 0xc010000 0x0 0x1) 
0x1c73bf78 : 0x19c5c6 (0x35ef438 0xc010000 0x0 0x1) 
0x1c73bfd8 : 0x197bbb (0x351b4f8 0x351b4f8 0x0 0x14) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffeed8

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

Fri Aug  4 11:44:22 2006
panic(cpu 1 caller 0x0019CADF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0xff3771b0, CR3: 0x00d2d000, CR4: 0x000006a0
EAX: 0xff3771b0, EBX: 0x01643ad0, ECX: 0x040f1ad0, EDX: 0x01643ad8
ESP: 0xff3771b0, EBP: 0x1c833dd8, ESI: 0x00000100, EDI: 0x00000080
EFL: 0x00010202, EIP: 0x0014126a, CS:  0x00000008, DS:  0x1c830010

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x1c833c38 : 0x128b5e (0x3bc46c 0x1c833c5c 0x131bbc 0x0) 
0x1c833c78 : 0x19cadf (0x3c18e4 0x1 0xe 0x3c169c) 
0x1c833d28 : 0x197c7d (0x1c833d3c 0x1c833dd8 0x14126a 0x190048) 
0x1c833d34 : 0x14126a (0x190048 0x1640010 0x10 0x1c830010) 
0x1c833dd8 : 0x12d780 (0x1643ad0 0x1 0x0 0xc0000000) 
0x1c833e08 : 0x12d7a1 (0x390 0x1 0xfffec000 0x0) 
0x1c833e28 : 0x15b1b5 (0x390 0x34440d4 0x21c09000 0x0) 
0x1c833e68 : 0x15cc19 (0x4 0x8 0x1 0x1) 
0x1c833e98 : 0x139519 (0x385ae18 0x4 0x0 0x0) 
0x1c833ee8 : 0x32f467 (0x2e521b0 0x1 0x1c833f08 0x0) 
0x1c833f18 : 0x32fa21 (0x381adac 0x344b5dc 0x1c833f48 0x320c89) 
0x1c833f48 : 0x32fb9d (0x344b5dc 0x1 0x1c833f78 0x1) 
0x1c833f78 : 0x36de6c (0x344b5dc 0x382765c 0x38276a0 0x0) 
0x1c833fd8 : 0x197ff3 (0x40f1d48 0x40f1d48 0x1643ad0 0xff3771b0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0182be8

Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun  7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


*********

[ghporter]

I'd say it's less likely that the RAM is "bad" and more likely that it's not well installed. No knock against you - those slots are supposed to be VERY hard to install the SODIMMs in. I'd start by REMOVING the Corsair piece and then reinstalling it both very carefully and very firmly.

And Corsair is a good company-they stand behind their products. If it does turn out to be bad, they will no doubt replace it.

[kmkkid]

So even if it's installed wrong it can be verified correctly? And it could still cause inconsistant panics? I'm just worried it may be another hardware problem. Is there any way I could have damaged a RAM slot, and that cxould be causing the panics?

Thanks for your input so far!

I also did an SMU reset today to see if that helps at all.

[kd]

How long did you run memtest for? I've had sticks of memory with marginal bits that would only fail once every few hours. Run it overnight.

[kmkkid]

Well I resinstalled the RAM, this time it feels like they clicked in a lot further than before. Let's hope that's all it was.

[ghporter]

If it's not fully inserted in the socket, it may not consistently stay connected, which can leave you with problems-lost data, rereads and so on. It can work, but it won't necessarily work well. It sounds like you have reinstalled them so that they're really well seated this time. I'm rooting for you on this!

[kmkkid]

*Update*


The panics didn't stop even after numerous tests, reinstallation, and OS reinstalls, so I got fed up, took out the stick and everything is A.O.K so far (knock on wood). So I've sent an RMA request to the retailer, and hopefully I get a replacement stick with no hastles. Too bad I have to pay for the extra in shipping now, so much for a low priced stick of RAM. *sigh*


I just hope it isn't the one RAM slot that's screwed up, I'm not fiddling with it anymore, so if the next stick causes crashes, I might have to look into having my beautiful problem-free iMac sent away for repairs

I'll update as the events unfold

[Tomchu]

If the RAM is seated improperly (ie. not all the way), then the system simply will not POST, or will POST but will not find the new RAM. It won't fail intermittently. It's not like a misaligned magnetic head recording to audio tape or something.

And yes, there have been cases in my experience where a stick of RAM would pass rigorous MemTest86+ testing, but a few minutes of using an operating system resulted in regular crashes. It has to do with compatibility rather than errors in the RAM.

[kmkkid]

Compatibility? I made sure it's the exact same spec as apple says I should use And other people have said the corsair brand works fine in their macs.

[Tomchu]

In your case it might very well be a bad stick, but sometimes even RAM that has the same basic specs as what the manufacturer says you need will not work. It probably has to do with the values of the other timings in the RAM's SPD tables.

Just yesterday I had such a problem with an Athlon 64 system. MemTest86+ past with flying colours after about 8 hours of testing, but as soon as I tried to install XP, the installer bluescreened. I checked the timings and voltages again and again. Eventually I popped in RAM from the same company with slightly lower ratings, and it works just fine.