Post by: chriskleeman on June 13, 2015, 10:32:19 AM
In the middle of using my Windows 7 partition with Parallels, the whole video screen flashed horizontal stripes, and went to black. The fans were blazing at the time as well.
There does seem to be some conflict with Adobe Flash running in the Browser (SeaMonkey) and running Parallels at the same time, the computer heats up and the fans run up to about 5000 RPM.
Anyway, I powered off and rebooted, and the MBP booted into Windows. After the log-in screen, the display went into a blue screen, and would not display Windows. So, I rebooted again with the power key, and the MBP booted into Windows again. I powered off, started again with the Option button to choose the Mac Hard Drive, and it took two boots to get the video display working. And when it finally did boot, I'd lost my Desktop picture and it had reverted to one of the stock Mac pictures.
Verified the Disk, repaired Permissions, so far so good.
Any thoughts?
CK
Post by: Paddy on June 13, 2015, 08:55:29 PM
QUOTE(chriskleeman @ Jun 13 2015, 11:32 AM) <{POST_SNAPBACK}>
Had a very strange and fairly terrifying time with my MBP a couple of days ago. Parallels 10.
In the middle of using my Windows 7 partition with Parallels, the whole video screen flashed horizontal stripes, and went to black. The fans were blazing at the time as well.
There does seem to be some conflict with Adobe Flash running in the Browser (SeaMonkey) and running Parallels at the same time, the computer heats up and the fans run up to about 5000 RPM.
Anyway, I powered off and rebooted, and the MBP booted into Windows. After the log-in screen, the display went into a blue screen, and would not display Windows. So, I rebooted again with the power key, and the MBP booted into Windows again. I powered off, started again with the Option button to choose the Mac Hard Drive, and it took two boots to get the video display working. And when it finally did boot, I'd lost my Desktop picture and it had reverted to one of the stock Mac pictures.
Verified the Disk, repaired Permissions, so far so good.
Any thoughts?
CK
In the middle of using my Windows 7 partition with Parallels, the whole video screen flashed horizontal stripes, and went to black. The fans were blazing at the time as well.
There does seem to be some conflict with Adobe Flash running in the Browser (SeaMonkey) and running Parallels at the same time, the computer heats up and the fans run up to about 5000 RPM.
Anyway, I powered off and rebooted, and the MBP booted into Windows. After the log-in screen, the display went into a blue screen, and would not display Windows. So, I rebooted again with the power key, and the MBP booted into Windows again. I powered off, started again with the Option button to choose the Mac Hard Drive, and it took two boots to get the video display working. And when it finally did boot, I'd lost my Desktop picture and it had reverted to one of the stock Mac pictures.
Verified the Disk, repaired Permissions, so far so good.
Any thoughts?
CK
Yikes. Have you checked here: https://forum.parallels.com/forums/parallel...top-for-mac.58/
I use VMWare Fusion, though did have Parallels for a while as part of a bundle, but didn't really use it. Never had it do anything to my Mac OS/video etc.
Post by: chriskleeman on June 13, 2015, 09:13:16 PM
Tonight when we got home from going out to dinner I opened the MPB to find that it was not sleeping any more. I booted up, and it still wants to boot into Windows 7 in default, this is definitely not right.
I'll keep looking and if these issues continue, contact Parallels support again. They were very helpful in reconfiguring the re-install a couple of weeks ago after my Windows partition hosed itself, and am wondering if there's something they did when they helped with the reconfig.
CK
QUOTE(Paddy @ Jun 13 2015, 09:55 PM) <{POST_SNAPBACK}>
QUOTE(chriskleeman @ Jun 13 2015, 11:32 AM) <{POST_SNAPBACK}>
Had a very strange and fairly terrifying time with my MBP a couple of days ago. Parallels 10.
In the middle of using my Windows 7 partition with Parallels, the whole video screen flashed horizontal stripes, and went to black. The fans were blazing at the time as well.
There does seem to be some conflict with Adobe Flash running in the Browser (SeaMonkey) and running Parallels at the same time, the computer heats up and the fans run up to about 5000 RPM.
Anyway, I powered off and rebooted, and the MBP booted into Windows. After the log-in screen, the display went into a blue screen, and would not display Windows. So, I rebooted again with the power key, and the MBP booted into Windows again. I powered off, started again with the Option button to choose the Mac Hard Drive, and it took two boots to get the video display working. And when it finally did boot, I'd lost my Desktop picture and it had reverted to one of the stock Mac pictures.
Verified the Disk, repaired Permissions, so far so good.
Any thoughts?
CK
In the middle of using my Windows 7 partition with Parallels, the whole video screen flashed horizontal stripes, and went to black. The fans were blazing at the time as well.
There does seem to be some conflict with Adobe Flash running in the Browser (SeaMonkey) and running Parallels at the same time, the computer heats up and the fans run up to about 5000 RPM.
Anyway, I powered off and rebooted, and the MBP booted into Windows. After the log-in screen, the display went into a blue screen, and would not display Windows. So, I rebooted again with the power key, and the MBP booted into Windows again. I powered off, started again with the Option button to choose the Mac Hard Drive, and it took two boots to get the video display working. And when it finally did boot, I'd lost my Desktop picture and it had reverted to one of the stock Mac pictures.
Verified the Disk, repaired Permissions, so far so good.
Any thoughts?
CK
Yikes. Have you checked here: https://forum.parallels.com/forums/parallel...top-for-mac.58/
I use VMWare Fusion, though did have Parallels for a while as part of a bundle, but didn't really use it. Never had it do anything to my Mac OS/video etc.
Post by: chriskleeman on June 15, 2015, 02:30:15 PM
Thinking at this point I have a video component related problem to this behavior.
Whenever I restart, the MBP wants to start up in Windows. If I don't remember to hold down the option key, it boots into Windows every time. This is pretty strange all by itself!
Now today, with Parallels not being used, I had a video failure while booted into 10.9.5. More vertical lines, then flashing in and out, then a textured blue screen, then black. I had to turn off the MBP with the power button, and it restarted into Windows. This is where it gets interesting. Windows said it could not boot due to a problem with the "display". Next time it happens, I'll write down the error message in it's entirety.
Could it be that there is something weird going on with the Windows Drivers that Apple installs in Boot Camp? For the life of me I can't figure out why this MBP wants to boot into Windows instead of it's native OS.
Cannot start up to use the Apple Hardware Test by holding down the "D" key, because it eventually wants to boot into Windows. So I used the internet version by holding down the D and option keys. Passed the Hardware Test. There is a more advanced option to test more fully, which I will use sometime later this evening I hope.
I am stumped. I could remove the Windows Partition and start all over again, but it took me a long time to re-install things a couple of weeks ago, and with the video behavior today just using Mavericks and not running Parallels, I'm not thinking that the Windows partition is a part of the problem.
Chris
Post by: gunug on June 15, 2015, 03:02:34 PM
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Post by: chriskleeman on June 20, 2015, 09:25:26 AM
QUOTE(gunug @ Jun 15 2015, 04:02 PM) <{POST_SNAPBACK}>
This thing of not wanting to start up on another OS is more common that you'd think. I have two bootable drives in this Macpro (one with 10.10 and one with 10.6) and they don't always want to change bootable drives the first or second time I try. I've also had trouble getting Windows 7 to start up under Boot Camp; although that was older versions of OS 10!
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Yes John, this strange behavior. I'm going to not run a little app called SMC Fan control and see if there's some conflict there with Mavericks, so far so good.
Yes, the video chip could be going and not wanting to behave when it starts to heat up.
Dunno.
Probably the first thing to do is remove the Windows partition again.
Chris
Post by: Paddy on June 20, 2015, 04:22:42 PM
QUOTE(chriskleeman @ Jun 20 2015, 10:25 AM) <{POST_SNAPBACK}>
QUOTE(gunug @ Jun 15 2015, 04:02 PM) <{POST_SNAPBACK}>
This thing of not wanting to start up on another OS is more common that you'd think. I have two bootable drives in this Macpro (one with 10.10 and one with 10.6) and they don't always want to change bootable drives the first or second time I try. I've also had trouble getting Windows 7 to start up under Boot Camp; although that was older versions of OS 10!
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Yes John, this strange behavior. I'm going to not run a little app called SMC Fan control and see if there's some conflict there with Mavericks, so far so good.
Yes, the video chip could be going and not wanting to behave when it starts to heat up.
Dunno.
Probably the first thing to do is remove the Windows partition again.
Chris
Question: if you're using Parallels, why do you have a Windows partition? Usually, one only does that with BootCamp. Just wondering...mine lives in a Virtual Machines folder in my Documents folder.
Post by: chriskleeman on June 20, 2015, 04:37:22 PM
QUOTE(Paddy @ Jun 20 2015, 05:22 PM) <{POST_SNAPBACK}>
QUOTE(chriskleeman @ Jun 20 2015, 10:25 AM) <{POST_SNAPBACK}>
QUOTE(gunug @ Jun 15 2015, 04:02 PM) <{POST_SNAPBACK}>
This thing of not wanting to start up on another OS is more common that you'd think. I have two bootable drives in this Macpro (one with 10.10 and one with 10.6) and they don't always want to change bootable drives the first or second time I try. I've also had trouble getting Windows 7 to start up under Boot Camp; although that was older versions of OS 10!
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Aren't there video specific things about running Windows 7 on a MAC; you might need a "different" driver for Windows than one supplied by Apple. It could also be the video chip going out on you!
Yes John, this strange behavior. I'm going to not run a little app called SMC Fan control and see if there's some conflict there with Mavericks, so far so good.
Yes, the video chip could be going and not wanting to behave when it starts to heat up.
Dunno.
Probably the first thing to do is remove the Windows partition again.
Chris
Question: if you're using Parallels, why do you have a Windows partition? Usually, one only does that with BootCamp. Just wondering...mine lives in a Virtual Machines folder in my Documents folder.
Paddy, AFAIK, Parallels runs the BootCamp partition at the same time as the Mac OS. You can do a lot of stuff back and forth with the two OS's running at the same time. I mean, maybe I'm missing some big here, but the reason I have Windows installed at all is to run the Proprietary Beverage software we have for work. It's Java based, and does not display properly or work properly with the Mac Java Applet.
Am I missing something here? I've been running Parallels with the BootCamp partition for over 3 years with barely a hiccup until now. But, this machine has never wanted to boot into Windows as the native OS, it's just weird! Normally, if I wanted to boot from Windows, I'd have to hold the Option key and select it. But now, every time I reboot because of the video glitch I have to use the Option key and select the Mac OS or it will try to boot into Windows.
Running Disk Utility from the Recovery Disk verifies the Mad HDD, I don't have an up to date version of TTP or anything else to go any further.
CK
Post by: chriskleeman on June 20, 2015, 08:11:27 PM
CK
Post by: chriskleeman on June 21, 2015, 02:11:41 PM
QUOTE(chriskleeman @ Jun 20 2015, 09:11 PM) <{POST_SNAPBACK}>
So I've removed the Windows partition with BootCamp Assistant, we will see if the video problems persist.
CK
CK
Footnote: Apple Hardware Test (Internet version), extended mode came up with this:
4/MEM/9/40000000: 0x84cdc018
Which is a memory related error message. Still testing, but I'm going to clean and re-seat the memory modules when it's the extended test is finished. Taking a good long while too!
CK
Post by: chriskleeman on June 21, 2015, 02:26:28 PM
Paddy, is this what you mean? I never considered doing this, I just ran it from Boot Camp...
Option 2: Import Windows and your data from Boot Camp into Parallels Desktop:
A virtual machine is created using a separate virtual hard disk that stores an exact copy of the imported Boot Camp partition.
Windows running from Parallels Desktop does not have the limitations listed in Option 1. Boot Camp and Parallels Desktop are separate. Changes you make in Windows while working with your virtual machine are not reflected when you start your Mac in Windows using Boot Camp.
Set Parallels Desktop to use Boot Camp, as described in the steps above.
Right click on the Parallels Desktop icon in the Dock and open Control Center (Virtual Machines list in older versions).
Right click the Boot Camp version of Windows and click Import Boot Camp.
Note: Windows must be shut down.
Click Import.
Locate where you want to store Windows and your data, and then click Choose.
Windows and all your data are imported from Boot Camp. You can still use the original Boot Camp Windows installation, separately from Parallels Desktop.
Important: In order to allow seamless operation between Windows and Mac OS X, Parallels Tools will be installed the first time you start Windows after setting Parallels Desktop to work with Boot Camp. Once Parallels Tools are installed, please restart Windows.
Hmm... feeling a little STOOPID...
CK
Post by: Paddy on June 21, 2015, 03:05:19 PM
QUOTE(chriskleeman @ Jun 21 2015, 03:26 PM) <{POST_SNAPBACK}>
Ahhh...
Paddy, is this what you mean? I never considered doing this, I just ran it from Boot Camp...
Option 2: Import Windows and your data from Boot Camp into Parallels Desktop:
A virtual machine is created using a separate virtual hard disk that stores an exact copy of the imported Boot Camp partition.
Windows running from Parallels Desktop does not have the limitations listed in Option 1. Boot Camp and Parallels Desktop are separate. Changes you make in Windows while working with your virtual machine are not reflected when you start your Mac in Windows using Boot Camp.
Set Parallels Desktop to use Boot Camp, as described in the steps above.
Right click on the Parallels Desktop icon in the Dock and open Control Center (Virtual Machines list in older versions).
Right click the Boot Camp version of Windows and click Import Boot Camp.
Note: Windows must be shut down.
Click Import.
Locate where you want to store Windows and your data, and then click Choose.
Windows and all your data are imported from Boot Camp. You can still use the original Boot Camp Windows installation, separately from Parallels Desktop.
Important: In order to allow seamless operation between Windows and Mac OS X, Parallels Tools will be installed the first time you start Windows after setting Parallels Desktop to work with Boot Camp. Once Parallels Tools are installed, please restart Windows.
Hmm... feeling a little STOOPID...
CK
Paddy, is this what you mean? I never considered doing this, I just ran it from Boot Camp...
Option 2: Import Windows and your data from Boot Camp into Parallels Desktop:
A virtual machine is created using a separate virtual hard disk that stores an exact copy of the imported Boot Camp partition.
Windows running from Parallels Desktop does not have the limitations listed in Option 1. Boot Camp and Parallels Desktop are separate. Changes you make in Windows while working with your virtual machine are not reflected when you start your Mac in Windows using Boot Camp.
Set Parallels Desktop to use Boot Camp, as described in the steps above.
Right click on the Parallels Desktop icon in the Dock and open Control Center (Virtual Machines list in older versions).
Right click the Boot Camp version of Windows and click Import Boot Camp.
Note: Windows must be shut down.
Click Import.
Locate where you want to store Windows and your data, and then click Choose.
Windows and all your data are imported from Boot Camp. You can still use the original Boot Camp Windows installation, separately from Parallels Desktop.
Important: In order to allow seamless operation between Windows and Mac OS X, Parallels Tools will be installed the first time you start Windows after setting Parallels Desktop to work with Boot Camp. Once Parallels Tools are installed, please restart Windows.
Hmm... feeling a little STOOPID...
CK
Actually, not quite. I've never, ever run Boot Camp. Just installed VMWare Fusion, then installed Windows. Did the same when I was using Parallels. There is a reason they call these things virtual machines.
When you install Windows in Boot Camp, it's an actual Windows install, running as the OS on your Mac when you're booted into it. You can't go back and forth between a Windows Boot Camp install and your Mac files/apps etc. without rebooting. If you always ran Windows from Boot Camp, I'm not quite sure why you even had Parallels - it certainly wasn't doing anything.
Now, *some* software for Windows doesn't run as well (in rare cases, at all) in Parallels or VMWare Fusion. Gaming in a virtual machine generally isn't as good an experience, for instance. Anything that is really processor intensive/memory intensive/video intensive may run better in Boot Camp than in a virtual machine (we're talking video editing, AutoCAD etc.) though all of those things continue to improve with each release of Parallels/VMWare and improvements to things like allocation of video memory.
Note to anyone considering VMWare Fusion 7 - VMWare 8 should be out at the end of August/beginning of Sept. if they follow their normal release patterns, so I wouldn't buy 7 now. At the moment, Parallels 10 benchmarks somewhat faster than VMWare Fusion, but these two apps have a history of leapfrogging one another in both features and speed, so I wouldn't assume that this will stay the case necessarily.
Post by: chriskleeman on June 22, 2015, 09:05:46 AM
QUOTE
Actually, not quite. I've never, ever run Boot Camp. Just installed VMWare Fusion, then installed Windows. Did the same when I was using Parallels. There is a reason they call these things virtual machines. wink.gif When you install Windows in Boot Camp, it's an actual Windows install, running as the OS on your Mac when you're booted into it. You can't go back and forth between a Windows Boot Camp install and your Mac files/apps etc. without rebooting.
If you always ran Windows from Boot Camp, I'm not quite sure why you even had Parallels - it certainly wasn't doing anything.
Now, *some* software for Windows doesn't run as well (in rare cases, at all) in Parallels or VMWare Fusion. Gaming in a virtual machine generally isn't as good an experience, for instance. Anything that is really processor intensive/memory intensive/video intensive may run better in Boot Camp than in a virtual machine (we're talking video editing, AutoCAD etc.) though all of those things continue to improve with each release of Parallels/VMWare and improvements to things like allocation of video memory.
If you always ran Windows from Boot Camp, I'm not quite sure why you even had Parallels - it certainly wasn't doing anything.
Now, *some* software for Windows doesn't run as well (in rare cases, at all) in Parallels or VMWare Fusion. Gaming in a virtual machine generally isn't as good an experience, for instance. Anything that is really processor intensive/memory intensive/video intensive may run better in Boot Camp than in a virtual machine (we're talking video editing, AutoCAD etc.) though all of those things continue to improve with each release of Parallels/VMWare and improvements to things like allocation of video memory.
No, I did not run Windows from Boot Camp, only from Parallels. But I installed Windows in a Boot Camp Partition that I ran on a Virtual Machine in Parallels. After doing some digging, Parallels gives you the option to do it either way. But the second option that you described and then what I quoted earlier looks like a much better way to run Windows that having Parallels start it up from the Boot Camp Partition. And according to Parallels gives the user more options than running the Virtual Machine from the Boot Camp Partition. I would guess that when I installed it, I simply followed Option 1.
Here is the link to the support article I found on Parallels: Options 1 and 2
Anyway, it would appear that all of this may be due to the Apple Hardware Test memory message I got (4/MEM/9/40000000: 0x84cdc018) and is the root culprit of all of this weird behavior. Since I cleaned and re-installed the DIMMS the MBP is waking from sleep properly, and is not needing to be re-booted. If the problem comes back, I'll install the old OWC DIMMS and see if that takes care of it.
Crossing my fingers...
Chris
Post by: Xairbusdriver on June 22, 2015, 11:55:59 AM
QUOTE
I cleaned and re-installed the DIMMS
What kind of detergent did you use? Should we scrub against the grain or with it? Did you drip-dry, or just use the delicate setting on a dryer? Enquiring minds (or lack of one?), ya kno... 
Post by: chriskleeman on June 22, 2015, 12:28:49 PM
QUOTE(Xairbusdriver @ Jun 22 2015, 12:55 PM) <{POST_SNAPBACK}>
QUOTE
I cleaned and re-installed the DIMMS
What kind of detergent did you use? Should we scrub against the grain or with it? Did you drip-dry, or just use the delicate setting on a dryer? Enquiring minds (or lack of one?), ya kno... Electronic Contact Cleaner... You should try it sometime!!!
Chris
Seriously, I have come across a "recall" from Apple with these machines which is probably applicable to my MBP. Going to post it in a new thread so anyone who experiences any similar issues on their machine might save some time and $$$. I guess Apple is working from the "If it ain't broke, don't fix it" axiom, but it would be very helpful to know of the possibility of something like this on any given computer made in the time frame in the link below. I've spent hours and hours on this darn thing!
MBP Video Repair
Taking mine into Apple shortly to see if it's one of the ones.
Post by: Xairbusdriver on June 22, 2015, 02:26:29 PM
QUOTE
Electronic Contact Cleaner... You should try it sometime!!!
Well, we do have some 'contact cleaner'! It's sold by <Bausch + Lomb >. But it's not electric or anything, just a liquid, I think. Perhaps I should push a paper clip into a wall socket while holding the RAM? 
QUOTE
Taking mine into Apple shortly to see if it's one of the ones.
They didn't provide a serial number range? 
OK, there is a "Identify your model" section with a "<Check your coverage>" link on your linked page... OTOH, that may be nothing more than an AppleCare contract validity check. BTW, here's <where to find your MBP serial #>, assuming you have access to a fairly powerful magnifying glass.
Post by: Paddy on June 22, 2015, 06:15:20 PM
I've got one of the MBPs in that range - I've not had any video issues lately, but did have some screwy behaviour not long after I got it. And I think it's shut itself down a time or two with no input from me. My warranty is up this summer, but....
QUOTE
The program covers affected MacBook Pro models until February 27, 2016 or three years from its original date of sale, whichever provides longer coverage for you.
So...any more nutso behaviour, and in it goes.
Post by: chriskleeman on July 20, 2015, 02:22:04 PM
Good part is that i finally have my MBP back.
However, Small Dog Electronics had my machine for over 3 weeks and three Technician cycles (only comes to the Rutland VT store on Thursdays).
I was told the second Thursday that my machine was still being tested over the Internet, and that it was a few minutes away from diagnosis. And that someone would be in touch shortly. Really...
No phone calls, no emails from Small Dog during this entire process. Their phone system is an elaborate labyrinth that almost always sends you exactly where you don't want to go even if you've hit the correct extension. So, a week ago Friday, July 10, I went back to the store to speak to a real person after having been given the run around by two different sales associates on multiple occasions. Turns out that my machine was technically "not able to participate" in the recall program, as it passed the standard GPU test, and needed to be sent to Apple for further diagnosis. And if Apple could fix it, there are two levels of repair, either just over $400 or around $1,000 if they determine that you doused the machine in coffee or other liquid. So, I asked if I could get an estimate from Apple, as I've never given my MBP a bath or dropped it hard enough to damage anything. Sure, they said, we'll be in touch after it gets to Apple.
Last Thursday, I actually get a call from someone at Small Dog that my MBP is ready. I call back that afternoon, got run around by the phone system again, got dumped trying to get to the Rutland store, I'm busy selling wine, I give up.
Friday, I finally get a sales associate at the Rutland Store first try. Yes the computer is ready. No, there is no charge. WOO-HOO!!!
So, I go up on Saturday morning and get the computer back. While at Apple, they took out my 2 8GB RAM sticks and put 2 Apple 4GB RAM DIMMS in, but they did send the 16 GB sticks back with the notation of (issues) next to each one. According to the sales associate, they always replace non-Apple RAM no matter what. To their credit, Small Dog put my 16 GB of RAM back in and gave me the 4 GB DIMMS that Apple had installed (for free...)
So now, I've got 16 GB of RAM I can put in my mother's 2011 27" iMac, as I've got 2 more 4 GB DIMMS that I had taken out of the MBP to put in the 16GB of RAM, so happy dance again!
And the best part, they didn't touch the HDD, so I've got everything back to normal.
What did they replace? The Logic Board. Apparently, over time, the heating and cooling apparently breaks down the lead free solder, and since it's a 2 stage graphics system, there's can be quite a bit of temperature variance. I think that the re-installation of Parallels and the associated overheating using the three cores that the Parallels tech set up probably ended in a fait complete. Since this is a refurb, I'm willing to bet that the GPU may have been replaced the first time.
And they replaced my broken little rubber foot on the front left side!
WHEW!!!!
Now I can go play with Parallels and Windows again.
So much fun, so little time...
Chris
Post by: RNKIII on July 20, 2015, 02:39:19 PM
Glad everything (except the time) worked out...
Always wondered what to do with the memory sticks I've accumulated over the last few years...
Bob K. rnkiii
Post by: chriskleeman on July 20, 2015, 03:25:39 PM
QUOTE(RNKIII @ Jul 20 2015, 03:39 PM) <{POST_SNAPBACK}>
Persistence does pay off!!!
Glad everything (except the time) worked out...
Always wondered what to do with the memory sticks I've accumulated over the last few years...
Bob K. rnkiii
Glad everything (except the time) worked out...
Always wondered what to do with the memory sticks I've accumulated over the last few years...
Bob K. rnkiii
Yah, well, don't believe everything you read young Robert! My machine just had a Kernal Panic and restarted itself, one of the indicators of a bad GPU, perhaps Apple did not go as far as they should.
It is possible that one of the 8 GB DIMMS could be causing it, so I guess I'll put in one of the 4's and see if that happens again. And play memory Mambo for a while.
Oh joy, oh rapture..
CK
Post by: RNKIII on July 20, 2015, 04:06:41 PM
Bob K. rnkiii