|
|
#1 |
|
Kernel panics ... cause?
Last week I made two decently big changes to my new mini ... I installed a BootCamp partition and installed new RAM. Now, in the past week, I've had two kernel panics. Is it more likely this is from the RAM or the partition?
|
|
|
|
0
|
|
|
#2 |
|
Post the kernel panic report you get to see upon restart.
About "You need to restart your computer" (kernel panic) messages Resolving Kernel Panics Mac OS X: How to log a kernel panic The cause is more likely to be the RAM. Maybe tell us what exact RAM you have.
__________________
This is not
|
|
|
|
0
|
|
|
#3 |
|
put the original ram back in and see if the problem goes away.
|
|
|
|
0
|
|
|
#4 |
|
Yep, it's the RAM. Get it exchanged asap!
|
|
|
|
0
|
|
|
#5 |
|
It is not your partition. It should be your new ram.
Test it with memtest86+ for atleast 10 passes. (10 hours) If your ram is really bad it should give a error in the first passes. That way you know for sure if your ram is defect. Use the bootcd version of memtest86+. Last edited by Snowcake; Nov 14, 2012 at 08:47 PM. |
|
|
|
0
|
|
|
#6 |
|
99% that it is RAM... Try with the original sticks...
|
|
|
|
0
|
|
|
#7 |
|
it is ram - 100 percent - try original ram, or only new one - had similar with imac - old ram did not work with new - so i bought for new modules and problem was solved .. if you dont trust us, try apple hw test and run extensive one - it will give you error code
|
|
|
|
0
|
|
|
#8 |
|
You can also try running memtest+. Errors will eventually show up. Then return those modules as they're clearly faulty!
__________________
2012 Mac Mini |
|
|
|
0
|
|
|
#9 |
|
that does not need to be truth - I had imac original 4GB module, added another from iceberg and problem occured... tryed another iceberg, no change, then swapped apple original for another iceberg and since then, 18 months without any problem... my conclusion, some modules work together, some not
|
|
|
|
0
|
|
|
#10 | |
|
Quote:
__________________
2012 Mac Mini |
||
|
|
0
|
|
|
#11 |
|
|
0
|
|
|
#12 |
|
You should've gone to Apple and have them replace them then.
__________________
2012 Mac Mini |
|
|
|
0
|
|
|
#13 |
|
Whenever you install new ram, the first thing you should do is test it. Single user utilities are preferable, as they tend to test a greater portion of ram. Whatever the test, run it at least 5 cycles. If any errors arise, RMA the memory. Test replacement ram too. RAM is extremely cheap these days, so I get the feeling that quality control may have slipped somewhat.
__________________
Legend has it that a bad GPU driver killed Intel's father. To this day intel can't bring themselves to write a good one. |
|
|
|
0
|
|
|
#14 | |
|
Quote:
I have read that people had weird problems and and the errors showed up in the 9th cycle. After replacing the ram, no more weird problems and ram tested good. |
||
|
|
0
|
|
|
#15 |
|
We can argue over how many. There's no real magic number to it. You're slightly more likely to turn up an error if you run it 100 cycles. In most cases errors capable of causing kernel panics turn up early enough. I just suggest setting it for a number of cycles and letting it run overnight.
__________________
Legend has it that a bad GPU driver killed Intel's father. To this day intel can't bring themselves to write a good one. |
|
|
|
0
|
|
|
#16 |
|
|
0
|
|
|
#17 | |
|
Quote:
More than 15 has no use. |
||
|
|
0
|
![]() |
|
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
All times are GMT -5. The time now is 01:47 AM.








Linear Mode
