Register FAQ / Rules Forum Spy Search Today's Posts Mark Forums Read
Go Back   MacRumors Forums > Apple Hardware > Desktops > iMac

Reply
 
Thread Tools Search this Thread Display Modes
Old Mar 31, 2013, 04:13 AM   #1
Payton
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
7 kernel panics in 7 days. Brand new iMac.

I received my new 27'' iMac w/ 1tb Fusion Drive on the 19th of March.

After several days of setup and configuration (I use this in my design practice, and have been eagerly awaiting a new machine while continuing to use my 2007 MacBook Pro as my main machine) I finally started to settle into this new beast. I love the display, it's fast as hell, everything running smoothly.

Come March 25 I get my first kernel panic. Shuts down, starts back up in about 5 seconds which is nice, but still a little unnerving, but I've seen these before very occasionally so I wasn't too worried, until it happened the next day. And the next day, and the next day. So far I've had 7 kernel panics in the last week. Basically one per day.

So, after about the 3rd panic, I began troubleshooting. Disconnecting external drives and peripherals. Disabling menubar apps that might be doing weird things. Disconnecting my second display. None of this has eliminated the problem. So, I tried the Apple Hardware Test. Found nothing. Did the "deep scan" and it also found nothing. I tried physically popping out my RAM sticks and sticking them back in, in case that was the issue.

I tried re-installing the 10.8.3 Update Combo. I'd rather not do a brand new Archive & Install, and would probably rather tote the iMac into Apple before doing so, since either way I'll have to reconfigure the Mac, and if they offered to replace it, I'd still have to wait for a new one to come in since it's BTO.

It seems to panic when the system is under moderately high stress, during a Skype call where I'm sharing my screen and saving files in Photoshop, or just video chatting. Two times it crashed in the middle of a video game, two different games.

So, my troubleshooting has now found nothing conclusive. I have all the panic logs saved, but I don't know how to read them in order to understand what the heck is going on.

My last resort is to try plugging it straight into the wall rather than the surge protector it's been plugged into, but I haven't found much, if any, research that says the power source could be causing a panic like this.

I've dealt with Apple support in the past, and had great results, but I've never had such a pain in the ass issue as this, and I am really going to hate having to set up a brand new machine, so I'd love to just figure it out and not have to deal with Apple.

To conclude…

Does it sound like a bad logic board / hardware issue to anybody?

Have any new 2012 iMac owners with Fusion Drive experienced anything similar?

This guy was "assembled in USA", which gave me even greater confidence in its quality, but maybe our American assemblers aren't quite up to speed, yet?
Payton is offline   0 Reply With Quote
Old Mar 31, 2013, 04:20 AM   #2
simsaladimbamba
Guest
 
Join Date: Nov 2010
Location: located
The part after backtrace until Mac OS version is important, it is located at the top. If you can post those, that would be splendid.

Of course, your logs may differ from below example and even be much longer.
Code:
Backtrace (CPU 1), Frame : Return Address
0xffffff81542a3d50 : 0xffffff8000220702 
0xffffff81542a3dd0 : 0xffffff80004dd8e4 
0xffffff81542a3e20 : 0xffffff80004de8dc 
0xffffff81542a3e70 : 0xffffff80004d2524 
0xffffff81542a3eb0 : 0xffffff800031c800 
0xffffff81542a3f90 : 0xffffff800031d8f2 
0xffffff81542a3fb0 : 0xffffff8000820057 

BSD process name corresponding to current thread: kernel_task
simsaladimbamba is offline   0 Reply With Quote
Old Mar 31, 2013, 04:23 AM   #3
Payton
Thread Starter
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
I'd be happy to post them… would all 7 be helpful?

Quote:
Originally Posted by simsaladimbamba View Post
The part after backtrace until Mac OS version is important, it is located at the top. If you can post those, that would be splendid.

Of course, your logs may differ from below example and even be much longer.
Code:
Backtrace (CPU 1), Frame : Return Address
0xffffff81542a3d50 : 0xffffff8000220702 
0xffffff81542a3dd0 : 0xffffff80004dd8e4 
0xffffff81542a3e20 : 0xffffff80004de8dc 
0xffffff81542a3e70 : 0xffffff80004d2524 
0xffffff81542a3eb0 : 0xffffff800031c800 
0xffffff81542a3f90 : 0xffffff800031d8f2 
0xffffff81542a3fb0 : 0xffffff8000820057 

BSD process name corresponding to current thread: kernel_task
Payton is offline   0 Reply With Quote
Old Mar 31, 2013, 04:24 AM   #4
simsaladimbamba
Guest
 
Join Date: Nov 2010
Location: located
Quote:
Originally Posted by Payton View Post
I'd be happy to post them… would all 7 be helpful?
Probably, as they might differ, or we could see the thread, that causes it all.
simsaladimbamba is offline   0 Reply With Quote
Old Mar 31, 2013, 04:28 AM   #5
Payton
Thread Starter
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
I'll do these each in a separate post, just for ease of identification…

Code:
Mon Mar 25 14:01:26 2013
panic(cpu 3 caller 0xffffff7fa79bd7f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103000000 0xffffff811ac89000 0x0e7200a2, D0, P2/4
Backtrace (CPU 3), Frame : Return Address
0xffffff811a402e00 : 0xffffff802721d626 
0xffffff811a402e70 : 0xffffff7fa79bd7f2 
0xffffff811a402f30 : 0xffffff7fa7aba3b9 
0xffffff811a402f90 : 0xffffff7fa7aba42e 
0xffffff811a403000 : 0xffffff7fa7e22714 
0xffffff811a403190 : 0xffffff7fa7ae0fe8 
0xffffff811a4031d0 : 0xffffff7fa79c5567 
0xffffff811a403280 : 0xffffff7fa79c305a 
0xffffff811a403480 : 0xffffff7fa79c4983 
0xffffff811a403550 : 0xffffff7fa89ea480 
0xffffff811a403690 : 0xffffff7fa89e9f6c 
0xffffff811a4036a0 : 0xffffff7fa89ad868 
0xffffff811a4036b0 : 0xffffff7fa89ad8dd 
0xffffff811a4036c0 : 0xffffff7fa898e95c 
0xffffff811a403700 : 0xffffff7fa899108c 
0xffffff811a403730 : 0xffffff7fa89e414d 
0xffffff811a4037b0 : 0xffffff7fa89cb308 
0xffffff811a403810 : 0xffffff7fa89cbbe9 
0xffffff811a403860 : 0xffffff7fa89cc13c 
0xffffff811a4038d0 : 0xffffff7fa89cc8d1 
0xffffff811a403910 : 0xffffff7fa899834f 
0xffffff811a403a90 : 0xffffff7fa89c8e39 
0xffffff811a403b50 : 0xffffff7fa8996de8 
0xffffff811a403ba0 : 0xffffff80276650c9 
0xffffff811a403bc0 : 0xffffff8027666670 
0xffffff811a403c20 : 0xffffff802766408f 
0xffffff811a403d70 : 0xffffff80272984a1 
0xffffff811a403e80 : 0xffffff8027220aed 
0xffffff811a403eb0 : 0xffffff8027210448 
0xffffff811a403f00 : 0xffffff802721961b 
0xffffff811a403f70 : 0xffffff80272a5dd6 
0xffffff811a403fb0 : 0xffffff80272cdd43 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa7960000->0xffffff7fa7c6dfff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fa77e6000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fa794c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fa7909000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7fa7c7b000->0xffffff7fa7f7ffff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa7960000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fa77e6000
         com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7fa8985000->0xffffff7fa8a51fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa7960000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fa794c000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fa77e6000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fa7909000

BSD process name corresponding to current thread: WebProcess


----------

Code:
Tue Mar 26 11:46:58 2013
panic(cpu 2 caller 0xffffff7f8edbd7f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103000000 0xffffff8101c23000 0x0e7200a2, D0, P2/4
Backtrace (CPU 2), Frame : Return Address
0xffffff8134313500 : 0xffffff800e61d626 
0xffffff8134313570 : 0xffffff7f8edbd7f2 
0xffffff8134313630 : 0xffffff7f8eeba3b9 
0xffffff8134313690 : 0xffffff7f8eeba42e 
0xffffff8134313700 : 0xffffff7f8f222714 
0xffffff8134313890 : 0xffffff7f8eee0fe8 
0xffffff81343138d0 : 0xffffff7f8edc5567 
0xffffff8134313980 : 0xffffff7f8edc305a 
0xffffff8134313b80 : 0xffffff7f8edc40c5 
0xffffff8134313c60 : 0xffffff7f8ed63f3b 
0xffffff8134313df0 : 0xffffff7f8ed62d30 
0xffffff8134313e10 : 0xffffff7f90860286 
0xffffff8134313ef0 : 0xffffff7f90860176 
0xffffff8134313f40 : 0xffffff7f9085f1e7 
0xffffff8134313f60 : 0xffffff800e63dcfe 
0xffffff8134313fb0 : 0xffffff800e6b2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f8ed60000->0xffffff7f8f06dfff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f8ebe6000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f8ed4c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f8ed09000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7f8f07b000->0xffffff7f8f37ffff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f8ed60000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f8ebe6000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff7f9085e000->0xffffff7f9086dfff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f8ebe6000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B39C293C]@0xffffff7f8f794000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f8ed4c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f8ed09000

BSD process name corresponding to current thread: kernel_task


----------

Code:
Interval Since Last Panic Report:  133505 sec
Panics Since Last Report:          3
Anonymous UUID:                    10EDBDE0-B54A-C63F-CEC2-1FC1EA346B29

Wed Mar 27 12:41:38 2013
panic(cpu 1 caller 0xffffff7fa51c47f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103000000 0xffffff8118138000 0x0e7200a2, D0, P2/4
Backtrace (CPU 1), Frame : Return Address
0xffffff8117ceb500 : 0xffffff8024a1d626 
0xffffff8117ceb570 : 0xffffff7fa51c47f2 
0xffffff8117ceb630 : 0xffffff7fa52c13b9 
0xffffff8117ceb690 : 0xffffff7fa52c142e 
0xffffff8117ceb700 : 0xffffff7fa5629714 
0xffffff8117ceb890 : 0xffffff7fa52e7fe8 
0xffffff8117ceb8d0 : 0xffffff7fa51cc567 
0xffffff8117ceb980 : 0xffffff7fa51ca05a 
0xffffff8117cebb80 : 0xffffff7fa51cb0c5 
0xffffff8117cebc60 : 0xffffff7fa516af3b 
0xffffff8117cebdf0 : 0xffffff7fa5169d30 
0xffffff8117cebe10 : 0xffffff7fa6c42286 
0xffffff8117cebef0 : 0xffffff7fa6c42176 
0xffffff8117cebf40 : 0xffffff7fa6c411e7 
0xffffff8117cebf60 : 0xffffff8024a3dcfe 
0xffffff8117cebfb0 : 0xffffff8024ab2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa5167000->0xffffff7fa5474fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fa50d2000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fa5153000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fa5110000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7fa5482000->0xffffff7fa5786fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa5167000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fa50d2000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff7fa6c40000->0xffffff7fa6c4ffff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fa50d2000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B39C293C]@0xffffff7fa5b71000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fa5153000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fa5110000

BSD process name corresponding to current thread: kernel_task


----------

Code:
Interval Since Last Panic Report:  42595 sec
Panics Since Last Report:          1
Anonymous UUID:                    10EDBDE0-B54A-C63F-CEC2-1FC1EA346B29

Thu Mar 28 23:49:28 2013
panic(cpu 2 caller 0xffffff7f855c47f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103400000 0xffffff80f849d000 0x0e7200a2, D0, P2/4
Backtrace (CPU 2), Frame : Return Address
0xffffff80f7f2b500 : 0xffffff8004e1d626 
0xffffff80f7f2b570 : 0xffffff7f855c47f2 
0xffffff80f7f2b630 : 0xffffff7f856c13b9 
0xffffff80f7f2b690 : 0xffffff7f856c142e 
0xffffff80f7f2b700 : 0xffffff7f85a29714 
0xffffff80f7f2b890 : 0xffffff7f856e7fe8 
0xffffff80f7f2b8d0 : 0xffffff7f855cc567 
0xffffff80f7f2b980 : 0xffffff7f855ca05a 
0xffffff80f7f2bb80 : 0xffffff7f855cb0c5 
0xffffff80f7f2bc60 : 0xffffff7f8556af3b 
0xffffff80f7f2bdf0 : 0xffffff7f85569d30 
0xffffff80f7f2be10 : 0xffffff7f87042286 
0xffffff80f7f2bef0 : 0xffffff7f87042176 
0xffffff80f7f2bf40 : 0xffffff7f870411e7 
0xffffff80f7f2bf60 : 0xffffff8004e3dcfe 
0xffffff80f7f2bfb0 : 0xffffff8004eb2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f85567000->0xffffff7f85874fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f854d2000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f85553000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f85510000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7f85882000->0xffffff7f85b86fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f85567000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f854d2000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff7f87040000->0xffffff7f8704ffff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f854d2000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B39C293C]@0xffffff7f85f71000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f85553000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f85510000

BSD process name corresponding to current thread: kernel_task


----------

Code:
Interval Since Last Panic Report:  2880 sec
Panics Since Last Report:          1
Anonymous UUID:                    10EDBDE0-B54A-C63F-CEC2-1FC1EA346B29

Fri Mar 29 02:23:02 2013
panic(cpu 2 caller 0xffffff7f877367f2): NVRM[0/1:0:0]: Read Error 0x006100c0: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103200000 0xffffff80fab15000 0x0e7200a2, D0, P2/4
Backtrace (CPU 2), Frame : Return Address
0xffffff80f9f8bc40 : 0xffffff800701d626 
0xffffff80f9f8bcb0 : 0xffffff7f877367f2 
0xffffff80f9f8bd70 : 0xffffff7f878333b9 
0xffffff80f9f8bdd0 : 0xffffff7f87ab293a 
0xffffff80f9f8bde0 : 0xffffff7f878088d8 
0xffffff80f9f8be00 : 0xffffff7f878bf5ab 
0xffffff80f9f8be70 : 0xffffff7f8771e699 
0xffffff80f9f8bf30 : 0xffffff7f876df0cf 
0xffffff80f9f8bf60 : 0xffffff800703dcfe 
0xffffff80f9f8bfb0 : 0xffffff80070b2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f876d9000->0xffffff7f879e6fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f87644000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f876c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f87682000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7f879f4000->0xffffff7f87cf8fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f876d9000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f87644000

BSD process name corresponding to current thread: kernel_task


----------

Code:
Anonymous UUID:                    10EDBDE0-B54A-C63F-CEC2-1FC1EA346B29

Fri Mar 29 03:12:20 2013
panic(cpu 0 caller 0xffffff7f8a7367f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103000000 0xffffff80fd67d000 0x0e7200a2, D0, P2/4
Backtrace (CPU 0), Frame : Return Address
0xffffff812e91b500 : 0xffffff800a01d626 
0xffffff812e91b570 : 0xffffff7f8a7367f2 
0xffffff812e91b630 : 0xffffff7f8a8333b9 
0xffffff812e91b690 : 0xffffff7f8a83342e 
0xffffff812e91b700 : 0xffffff7f8ab9b714 
0xffffff812e91b890 : 0xffffff7f8a859fe8 
0xffffff812e91b8d0 : 0xffffff7f8a73e567 
0xffffff812e91b980 : 0xffffff7f8a73c05a 
0xffffff812e91bb80 : 0xffffff7f8a73d0c5 
0xffffff812e91bc60 : 0xffffff7f8a6dcf3b 
0xffffff812e91bdf0 : 0xffffff7f8a6dbd30 
0xffffff812e91be10 : 0xffffff7f8c23d286 
0xffffff812e91bef0 : 0xffffff7f8c23d176 
0xffffff812e91bf40 : 0xffffff7f8c23c1e7 
0xffffff812e91bf60 : 0xffffff800a03dcfe 
0xffffff812e91bfb0 : 0xffffff800a0b2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f8a6d9000->0xffffff7f8a9e6fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f8a644000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f8a6c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f8a682000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7f8a9f4000->0xffffff7f8acf8fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f8a6d9000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f8a644000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff7f8c23b000->0xffffff7f8c24afff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f8a644000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B39C293C]@0xffffff7f8b171000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f8a6c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f8a682000

BSD process name corresponding to current thread: kernel_task


----------

Last one…
I have a feeling this might be a little extraneous, but if you're willing to check them out, it's much appreciated.

Code:
Sun Mar 31 01:58:16 2013
panic(cpu 1 caller 0xffffff7fac9367f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103000000 0xffffff811f845000 0x0e7200a2, D0, P2/4
Backtrace (CPU 1), Frame : Return Address
0xffffff813b1a3500 : 0xffffff802c21d626 
0xffffff813b1a3570 : 0xffffff7fac9367f2 
0xffffff813b1a3630 : 0xffffff7faca333b9 
0xffffff813b1a3690 : 0xffffff7faca3342e 
0xffffff813b1a3700 : 0xffffff7facd9b714 
0xffffff813b1a3890 : 0xffffff7faca59fe8 
0xffffff813b1a38d0 : 0xffffff7fac93e567 
0xffffff813b1a3980 : 0xffffff7fac93c05a 
0xffffff813b1a3b80 : 0xffffff7fac93d0c5 
0xffffff813b1a3c60 : 0xffffff7fac8dcf3b 
0xffffff813b1a3df0 : 0xffffff7fac8dbd30 
0xffffff813b1a3e10 : 0xffffff7fae43d286 
0xffffff813b1a3ef0 : 0xffffff7fae43d176 
0xffffff813b1a3f40 : 0xffffff7fae43c1e7 
0xffffff813b1a3f60 : 0xffffff802c23dcfe 
0xffffff813b1a3fb0 : 0xffffff802c2b2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fac8d9000->0xffffff7facbe6fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fac844000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fac8c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fac882000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7facbf4000->0xffffff7facef8fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fac8d9000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fac844000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff7fae43b000->0xffffff7fae44afff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fac844000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B39C293C]@0xffffff7fad371000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fac8c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fac882000

BSD process name corresponding to current thread: kernel_task
Payton is offline   0 Reply With Quote
Old Mar 31, 2013, 05:51 AM   #6
justperry
macrumors 603
 
justperry's Avatar
 
Join Date: Aug 2007
Location: 7 Km South of an active upside down (boat) volcano.
Quote:
Originally Posted by Payton View Post
I'll do these each in a separate post, just for ease of identification…
Code:
Sun Mar 31 01:58:16 2013
panic(cpu 1 caller 0xffffff7fac9367f2): NVRM[0/1:0:0] : Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103000000 0xffffff811f845000 0x0e7200a2, D0, P2/4
Backtrace (CPU 1), Frame : Return Address


0xffffff813b1a3fb0 : 0xffffff802c2b2977 
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fac8d9000->0xffffff7facbe6fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fac844000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fac8c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fac882000
         com.apple.nvidia.gk100hal(8.1)[5122FE48-4118-30A5-8E71-7219C580E7B9]@0xffffff7facbf4000->0xffffff7facef8fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fac8d9000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fac844000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff7fae43b000->0xffffff7fae44afff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7fac844000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B39C293C]@0xffffff7fad371000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7fac8c5000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7fac882000

BSD process name corresponding to current thread: kernel_task
It's GPU related, now, this does not mean your GPU is having problems, it seems much more likely it's a bug in the display driver.

In all of your 7 reports NVRM is in the first line (Bold-NVRM[0/1:0:0]), and all of them have more or less the same or the same Kernel Extensions in backtrace.

Yours has two GPU's, one is the internal Intel HD 4000 and the other is NVidia I think, the second is a discrete GPU.

Now, what you could do is to download gfxCardStatus and switch to the internal for a day and see if it happens again, and later to the discrete one and try that one for a day, if it crashes remember on which GPU it was on.

Download gfxCardStatus here: gfxCardStatus.
justperry is offline   0 Reply With Quote
Old Mar 31, 2013, 06:00 AM   #7
simsaladimbamba
Guest
 
Join Date: Nov 2010
Location: located
Quote:
Originally Posted by justperry View Post
It's GPU related, now, this does not mean your GPU is having problems, it seems much more likely it's a bug in the display driver.

In all of your 7 reports NVRM is in the first line (Bold-NVRM[0/1:0:0]), and all of them have more or less the same or the same Kernel Extensions in backtrace.

Yours has two GPU's, one is the internal Intel HD 4000 and the other is NVidia I think, the second is a discrete GPU.

Now, what you could do is to download gfxCardStatus and switch to the internal for a day and see if it happens again, and later to the discrete one and try that one for a day, if it crashes remember on which GPU it was on.

Download gfxCardStatus here: gfxCardStatus.
While I agree with you on the GPU part being the problem, most likely due to driver issues, the iMac only has one GPU, namely the dedicated one. There is no IGP like the Intel HD 4000 included with it.
simsaladimbamba is offline   0 Reply With Quote
Old Mar 31, 2013, 06:20 AM   #8
gnasher729
macrumors G5
 
gnasher729's Avatar
 
Join Date: Nov 2005
If you have seven kernel panics in 7 days, your iMac is broken. There's nothing for you to figure out. Return it to the shop and get a replacement. Any time you invest in this is wasted.
gnasher729 is offline   2 Reply With Quote
Old Mar 31, 2013, 06:40 AM   #9
justperry
macrumors 603
 
justperry's Avatar
 
Join Date: Aug 2007
Location: 7 Km South of an active upside down (boat) volcano.
Quote:
Originally Posted by simsaladimbamba View Post
While I agree with you on the GPU part being the problem, most likely due to driver issues, the iMac only has one GPU, namely the dedicated one. There is no IGP like the Intel HD 4000 included with it.
I had this discussion with another User here, it's a while ago, probably 1-2 months, I said there is no HD4000 inside a iMac, he proved me otherwise, all Ivy Bridge have HD4000 in them, I don't have the link right now, I think it was from WikiPedia and it clearly says all of them have IGP.

Now, I think we get this discussion again, don't know what to believe, oh, I actually said they don't have IGP because Apple does not mention it in the specs.

Now I really want to know.

----------

Quote:
Originally Posted by gnasher729 View Post
If you have seven kernel panics in 7 days, your iMac is broken. There's nothing for you to figure out. Return it to the shop and get a replacement. Any time you invest in this is wasted.
What makes you think it is broken, give me evidence that this is the case, it could well be proven to be OS related, would like for the OP to install 10.8.0 and see if it happens there as well.

Look here, another User with similar problems on 10.8.3, got those when he updated the System!
Not an iMac but still.
justperry is offline   0 Reply With Quote
Old Mar 31, 2013, 06:42 AM   #10
simsaladimbamba
Guest
 
Join Date: Nov 2010
Location: located
Quote:
Originally Posted by justperry View Post
I had this discussion with another User here, it's a while ago, probably 1-2 months, I said there is no HD4000 inside a iMac, he proved me otherwise, all Ivy Bridge have HD4000 in them, I don't have the link right now, I think it was from WikiPedia and it clearly says all of them have IGP.

Now, I think we get this discussion again, don't know what to believe, oh, I actually said they don't have IGP because Apple does not mention it in the specs.

Now I really want to know.
Yeah, while I posted that previous post, I also got the vague feeling, that the IB i5s and i7s include the HD 4000 as I was researching the i7-3770. But I did not go any further, as I am a bit tired. Even if the i5 and i7 in the iMac include the HD 4000, it is probably deactivated, as Apple does not mention that IGP on their iMac sites anywhere.
simsaladimbamba is offline   0 Reply With Quote
Old Mar 31, 2013, 06:47 AM   #11
justperry
macrumors 603
 
justperry's Avatar
 
Join Date: Aug 2007
Location: 7 Km South of an active upside down (boat) volcano.
Quote:
Originally Posted by simsaladimbamba View Post
Yeah, while I posted that previous post, I also got the vague feeling, that the IB i5s and i7s include the HD 4000 as I was researching the i7-3770. But I did not go any further, as I am a bit tired. Even if the i5 and i7 in the iMac include the HD 4000, it is probably deactivated, as Apple does not mention that IGP on their iMac sites anywhere.
That's exactly what I said in that discussion/thread, in the end I gave up.
It can be easily tested by someone who has a 2012 iMac.

I will look for that discussion/thread if I can find it I will post it here.
justperry is offline   0 Reply With Quote
Old Mar 31, 2013, 06:49 AM   #12
simsaladimbamba
Guest
 
Join Date: Nov 2010
Location: located
Quote:
Originally Posted by justperry View Post
That's exactly what I said in that discussion/thread, in the end I gave up.
It can be easily tested by someone who has a 2012 iMac.

I will look for that discussion/thread if I can find it I will post it here.
A simple screenshot of System Report > Hardware > Graphics should suffice though, maybe the OP can provide one?
simsaladimbamba is offline   0 Reply With Quote
Old Mar 31, 2013, 07:01 AM   #13
justperry
macrumors 603
 
justperry's Avatar
 
Join Date: Aug 2007
Location: 7 Km South of an active upside down (boat) volcano.
Quote:
Originally Posted by simsaladimbamba View Post
A simple screenshot of System Report > Hardware > Graphics should suffice though, maybe the OP can provide one?
Found the Thread:

help newbie buying first Mac - rMBP 13: IR test and other tips needed

Post #3 and onwards.
justperry is offline   0 Reply With Quote
Old Mar 31, 2013, 12:23 PM   #14
joe-h2o
macrumors 6502a
 
Join Date: Jun 2012
Quote:
Originally Posted by justperry View Post
I had this discussion with another User here, it's a while ago, probably 1-2 months, I said there is no HD4000 inside a iMac, he proved me otherwise, all Ivy Bridge have HD4000 in them, I don't have the link right now, I think it was from WikiPedia and it clearly says all of them have IGP.

Now, I think we get this discussion again, don't know what to believe, oh, I actually said they don't have IGP because Apple does not mention it in the specs.

Now I really want to know.

----------



What makes you think it is broken, give me evidence that this is the case, it could well be proven to be OS related, would like for the OP to install 10.8.0 and see if it happens there as well.

Look here, another User with similar problems on 10.8.3, got those when he updated the System!
Not an iMac but still.
This is the Ivy Bridge CPU in the 27" iMac I have:

http://ark.intel.com/products/68316

It *does not* have an HD4000.
joe-h2o is online now   0 Reply With Quote
Old Mar 31, 2013, 12:33 PM   #15
HenryDJP
macrumors 68020
 
Join Date: Nov 2012
Location: United States
Did the OP install any 3rd party RAM? If so that could be the issue. I always add my own but the right type and quality of the RAM still matter. Bad or wrong RAM is almost always the cause and case of kernel panics.
HenryDJP is offline   0 Reply With Quote
Old Mar 31, 2013, 12:47 PM   #16
snberk103
macrumors 603
 
Join Date: Oct 2007
Location: An Island in the Salish Sea
Quote:
Originally Posted by gnasher729 View Post
If you have seven kernel panics in 7 days, your iMac is broken. There's nothing for you to figure out. Return it to the shop and get a replacement. Any time you invest in this is wasted.
Quote:
Originally Posted by justperry View Post
.....
What makes you think it is broken, give me evidence that this is the case,......
It's broken. The seven kernel panics is the evidence. The OP has done all the first steps - disconnected peripherals and reloaded the OS. The time spent trying to diagnose a problem that probably not fixable by the OP is likely already approaching the time needed to reconfigure a new machine. And there is no guarantee that the time spent trying to fix this issue won't be totally wasted because it turns out to be a hardware issue.

In experience, intermittent problems... like this one ... tend to be hardware related. The OP still has a couple of days to return the iMac without even having to explain why. After that they will need to demonstrate that it is borked. Which, with kernel panics, is not usually hard to do.

@OP - take it back. You have paid for Apple's excellent customer service, you may as well use it now that you need it. I do understand not wanting to ... but I really doubt you are dealing with something you can fix, and therefore anything you are doing now really is a waste of time.

Good Luck.
__________________
My friends, love is better than anger. Hope is better than fear. Optimism is better than despair. So let us be loving, hopeful and optimistic. And we'll change the world. - Jack Layton
snberk103 is offline   1 Reply With Quote
Old Mar 31, 2013, 02:17 PM   #17
Payton
Thread Starter
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
First off, thanks everyone for your help.
I'll be taking this thing into Apple tomorrow. Not looking forward to waiting, and then setting everything up again, but it will be good to (hopefully) acquire a reliable machine.

And, just for clarification purposes, it does not appear that I have the integrated intel graphics. Late 2012 iMac 27'':

Payton is offline   0 Reply With Quote
Old Mar 31, 2013, 03:45 PM   #18
Payton
Thread Starter
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
Now, since I'm more than likely going to be saying goodbye to this iMac tomorrow, I'd like to wipe the hard drive. Lots of saved passwords, iMessages, and client information already on this thing…

However, I'd save the .panic logs first and keep them safe.

Tomorrow will be day #13 or #14 since I received the iMac, depending on if you count the day I received it, so I'm still within the ability to "return" the computer without question…

but do you think wiping the drive will inhibit the Genius Bar employees from feeling like they can sufficiently "test" the device?

I'm going to be pretty firmly asking for a new iMac regardless, so I guess I shouldn't worry about it?
Payton is offline   0 Reply With Quote
Old Mar 31, 2013, 04:12 PM   #19
joe-h2o
macrumors 6502a
 
Join Date: Jun 2012
You don't need to nuke and pave it, but you can just make a new admin account and log into it, then delete your old account from within that new account using the System Preferences pane.

One of the options you can use is a secure erase (which will take bloody ages, depending on how much data you have), but generally just using the regular "delete this account" option will be sufficient.

They'll then be able to test the system with a fresh account in as close to new state as possible.
joe-h2o is online now   1 Reply With Quote
Old Mar 31, 2013, 10:43 PM   #20
justperry
macrumors 603
 
justperry's Avatar
 
Join Date: Aug 2007
Location: 7 Km South of an active upside down (boat) volcano.
Quote:
Originally Posted by snberk103 View Post
It's broken. The seven kernel panics is the evidence. The OP has done all the first steps - disconnected peripherals and reloaded the OS. The time spent trying to diagnose a problem that probably not fixable by the OP is likely already approaching the time needed to reconfigure a new machine. And there is no guarantee that the time spent trying to fix this issue won't be totally wasted because it turns out to be a hardware issue.

In experience, intermittent problems... like this one ... tend to be hardware related. The OP still has a couple of days to return the iMac without even having to explain why. After that they will need to demonstrate that it is borked. Which, with kernel panics, is not usually hard to do.

@OP - take it back. You have paid for Apple's excellent customer service, you may as well use it now that you need it. I do understand not wanting to ... but I really doubt you are dealing with something you can fix, and therefore anything you are doing now really is a waste of time.

Good Luck.
Bold, no he didn't, he said he reapplied 10.8.3, he did not reinstall OS X, at least this is from what I read.
If the OP just reapplied the Combo update and left all the stuff which He imported from a backup or whatever he can still have the same problems.

Quote:
Originally Posted by Payton View Post
First off, thanks everyone for your help.
I'll be taking this thing into Apple tomorrow. Not looking forward to waiting, and then setting everything up again, but it will be good to (hopefully) acquire a reliable machine.

And, just for clarification purposes, it does not appear that I have the integrated intel graphics. Late 2012 iMac 27'':

Image
Ah, thanks for the screenshot.

Quote:
Originally Posted by Payton View Post
Now, since I'm more than likely going to be saying goodbye to this iMac tomorrow, I'd like to wipe the hard drive. Lots of saved passwords, iMessages, and client information already on this thing…

However, I'd save the .panic logs first and keep them safe.

Tomorrow will be day #13 or #14 since I received the iMac, depending on if you count the day I received it, so I'm still within the ability to "return" the computer without question…

but do you think wiping the drive will inhibit the Genius Bar employees from feeling like they can sufficiently "test" the device?

I'm going to be pretty firmly asking for a new iMac regardless, so I guess I shouldn't worry about it?
You can switch FilVault2 on, then make a new Admin account and delete the original User, nobody will ever be able to recover the Data.

Quote:
Originally Posted by joe-h2o View Post
You don't need to nuke and pave it, but you can just make a new admin account and log into it, then delete your old account from within that new account using the System Preferences pane.

One of the options you can use is a secure erase (which will take bloody ages, depending on how much data you have), but generally just using the regular "delete this account" option will be sufficient.

They'll then be able to test the system with a fresh account in as close to new state as possible.
Be careful with secure wipe on an SSD, not so good for it.
justperry is offline   0 Reply With Quote
Old Mar 31, 2013, 10:53 PM   #21
Payton
Thread Starter
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
Thanks for the tip on FileVault.

I actually did go ahead and completely re-install OS X and it didn't help. Made a new admin account and it didn't make a difference either. It's gotta be hardware-related. Seems to be the gfx card, just from the situations it's happening.
Payton is offline   0 Reply With Quote
Old Mar 31, 2013, 11:02 PM   #22
justperry
macrumors 603
 
justperry's Avatar
 
Join Date: Aug 2007
Location: 7 Km South of an active upside down (boat) volcano.
Quote:
Originally Posted by Payton View Post
Thanks for the tip on FileVault.

I actually did go ahead and completely re-install OS X and it didn't help. Made a new admin account and it didn't make a difference either. It's gotta be hardware-related. Seems to be the gfx card, just from the situations it's happening.
Probably but I also say this, there seem to be a lot of GPU related problems in the last OS X version, could still be driver related.
Or even Firmware mess up, or the kernel.
justperry is offline   0 Reply With Quote
Old Apr 1, 2013, 04:21 AM   #23
Payton
Thread Starter
macrumors member
 
Join Date: Nov 2006
Location: Portland, OR
Quote:
Originally Posted by justperry View Post
Probably but I also say this, there seem to be a lot of GPU related problems in the last OS X version, could still be driver related.
Or even Firmware mess up, or the kernel.
Yep. Either way my **** ain't working… Time for some help from Apple, because I need it to work.
Payton is offline   0 Reply With Quote
Old Apr 1, 2013, 07:25 AM   #24
Nyy8
macrumors 6502
 
Join Date: Jun 2011
Location: New England
Looks like it's time for a new machine! Return it now while you still have the chance to get a new one, and like the other guy said... 7 kernel panics in 7 days? Your crap ain't working
__________________
iPad 2 16GB, iPhone 5S Space Grey 16GB,
iMac 21.5 inch, 2.5 GHz Core i5, 4GB RAM, 500GB HD
Nyy8 is offline   0 Reply With Quote

Reply
MacRumors Forums > Apple Hardware > Desktops > iMac

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Similar Threads
thread Thread Starter Forum Replies Last Post
Two Kernel Panics in two days!! gguerini OS X 10.8 Mountain Lion 0 Jun 5, 2013 10:53 AM
Need help with Kernel Panics jwolf6589 OS X 10.8 Mountain Lion 4 May 12, 2013 04:04 PM
Getting lots of kernel panics/random reboots these days MoodyM OS X 10.8 Mountain Lion 2 May 9, 2013 01:34 PM
iMac kernel panics Jimmy Guphanti iMac 1 Nov 23, 2012 06:10 PM
Early 2008 iMac continues to have kernel panics.. Any help? (log inside) wishman35 iMac 3 Sep 30, 2012 04:29 PM

Forum Jump

All times are GMT -5. The time now is 09:46 AM.

Mac Rumors | Mac | iPhone | iPhone Game Reviews | iPhone Apps

Mobile Version | Fixed | Fluid | Fluid HD
Copyright 2002-2013, MacRumors.com, LLC