Skip navigation
lclark00
Currently Being Moderated

Gaussian Blur in Photoshop CS5 Corrupting files

Nov 11, 2010 1:37 PM

We just got brand new systems at work less than a month ago and this event has happened twice since then. When using Photoshop CS5 Extended and using Gaussian blur the file becomes blocky and all layers as well as their masks become corrupted with these blocks. Can anyone help or is there any advice?

 

Here are my system specs...

 

Model Name:    Mac Pro
  Model Identifier:    MacPro5,1
  Processor Name:    6-Core Intel Xeon
  Processor Speed:    2.66 GHz
  Number Of Processors:    2
  Total Number Of Cores:    12
  L2 Cache (per core):    256 KB
  L3 Cache (per processor):    12 MB
  Memory:    16 GB
  Processor Interconnect Speed:    6.4 GT/s
  Boot ROM Version:    MP51.007F.B00
  SMC Version (system):    1.39f11
  SMC Version (processor tray):    1.39f11

 

Christmas LIVE Ad (original).jpg

 
Replies 1 2 3 ... 6 Previous Next
  • Currently Being Moderated
    Nov 11, 2010 2:15 PM   in reply to lclark00

    I haven't seen that before, but it looks a bit like an OpenGL drawing issue.

    Could you try disabling OpenGL drawing in preferences, restart, and try again?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 2:54 PM   in reply to lclark00

    Ok, try disabling all third party plugins and try again.

    After that, try disabling the extension plugins, and try again.

     

    If this was a widespread problem, I think we'd be hearing about it from more users.

    So my guess is that it is something to do with your system or configuration.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 11:33 PM   in reply to lclark00

    Boilerplate-text:

    As with all unexplainable Photoshop-problems you might try trashing the prefs (after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed) by pressing command-alt-shift on starting the program or starting from a new user-account.

    System Maintenance (repairing permissions, purging PRAM, running cron-scripts, cleaning caches, etc.) might also be beneficial, Onyx has been recommended for such tasks.

    http://www.apple.com/downloads/macosx/system_disk_utilities/onyx.html

     

    Can you reproduce the issue or is it totally random?

    Apart from that, but Mr.Cox naturally understands more about it than I do, could it be bad RAM?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 19, 2010 7:41 PM   in reply to lclark00

    I'm getting this same issue - or a similar one. It seems to only happen when I run the Gaussian blur command, and during the same process in my workflow. It also seems for me to happen when I have made a selection from a layer above that is a smart object.


    Let me describe the scenario that I have experienced a couple times in the past week. (BTW I just upgraded to CS5 only a couple weeks ago).

     

    Usually I have a document open with dozens or hundreds of layers. The effect that I am executing when this seems to happen is where I have a group of shapes or placed image smart object layer and I'm creating a shadow layer by making a blank layer below said group or image, making a selection from the above group or image, and then filling the selection in the blank layer with a color - which I then run the Gaussian blur filter on, and afterward warp transform to get my realistic looking shadow effect.

     

    But the problem is in seemingly random instances and on seemingly random documents when I run that Gaussian blur, Photoshop freaks out and craps the bed. And by craps the bed I mean deletes pixel data from multiple layers in my document very randomly, and also generates odd bright colors all throughout the document.

     

    You can see the initial freak out in this screen shot from when I just initially selected the Gaussian blur filter from the menu (but had not yet even clicked "OK"): http://cl.ly/3KTx . The strange thing is that I had just run this series of steps on the above layer which in the screen shot you'll see as "Layer 44", and all was well.

     

    Here's a screen shot showing the file after I closed it out, restarted Photoshop, and opened the file back up: http://cl.ly/3K2C . In case you can't tell, data from several layers all over the file is missing and corrupted.

     

    I'm sure I don't have to explain how exasperating this is, as this represents more than a year's worth of work on a client project, no joke. Fortunately I'm mostly done with the actual site build, but that makes the loss of the artwork files of no less consquence - especially seeing as how I'm not ACTUALLY finished and I did in fact need all of that data to complete the project.

     

    Anyhow, some additional details which may or may not be related to the issue:

     

    - The issue seems to happen randomly. As stated above the same steps did not produce the error just a few minutes before.

     

    - I have had this issue with another file this week where I was doing the same processes on another shape.

     

    - It seems that this is occuring when I make the selection from a layer that is a smart object of some type

     

    - I also noticed artifacts in the weird colors (after I tried running the processes again, so not in the above screenshot) that were actually design elements from an entirely different document that I was working with earlier this evening.

     

    - I have filed a bug report.

     

    Dunno what else to describe, but I hope you guys can get this figured out, seriously. I paid way too much for my upgrade to CS5 to have bugs in key software features corrupt my files thank you.

     

    Also, in regards to my system...

     

      Model Name: Mac Pro

      Model Identifier: MacPro4,1

      Processor Name: Quad-Core Intel Xeon

      Processor Speed: 2.26 GHz

      Number Of Processors: 2

      Total Number Of Cores: 8

      L2 Cache (per core): 256 KB

      L3 Cache (per processor): 8 MB

      Memory: 16 GB

      Processor Interconnect Speed: 5.86 GT/s

      Boot ROM Version: MP41.0081.B07

      SMC Version (system): 1.39f5

      SMC Version (processor tray): 1.39f5

     

    Chipset Model: NVIDIA GeForce GT 120

      Type: GPU

      Bus: PCIe

      Slot: Slot-1

      PCIe Lane Width: x16

      VRAM (Total): 512 MB

      Vendor: NVIDIA (0x10de)

      Device ID: 0x0640

      Revision ID: 0x00a1

      ROM Revision: 3386

      Displays:

    Display Connector:

      Status: No Display Connected

    LED Cinema Display:

      Resolution: 1920 x 1200

      Pixel Depth: 32-Bit Color (ARGB8888)

      Main Display: Yes

      Mirror: Off

      Online: Yes

      Rotation: Supported

      Connection Type: DisplayPort

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 20, 2010 1:04 AM   in reply to Joel Glovier

    Hmm, we really need some way to reproduce the problem more reliably so we can test it.

     

    I'd suggest removing or disabling the extension plugins (and certainly all third party plugins) -- but we can't be sure the problem is gone without steps to reproduce it.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 20, 2010 5:11 AM   in reply to Chris Cox

    Chris: I don't use any extensions or third party plugins at all. This is all just Photoshop man.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 20, 2010 5:47 AM   in reply to Chris Cox

    Also, I've gotten the issue on both my MacPro at my home office, and my MacBookPro that take when I go to our company office.

     

    If it helps I'd be happy to share the corrupted file that I got the issue on. It seems that now that the file is corrupted I'm getting the same issue when I run that command again in the same way. (more colors and artifacts) But the file is over 600MB.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 20, 2010 7:07 AM   in reply to Chris Cox

    Here's another lead: I think the issue happens for me when I have created a  masked double line (draw horizontal line with pencil tool, alt+nudge to duplicate and offset the next line by about 4 pixels to replicate the css rule for "border:4px double #anycolor;", then combine the two line layers with cmd+E into one layer, and then mask off a portion of the line).

     

    In both instances this week where I experienced this error, each of the files I was working with had such a layer I had just created.

     

    And further, I was able to find a duplicate copy of the file that was corrupted last night in my trash can because I just happened to copy this file a couple weeks ago onto my external hard drive to take with my to California on a trip. I recovered that version from my trash, and started making the same mods that I was going last night - save the double line step. Now I was not able to reproduce the error. So perhaps that masked double line is a factor?? IDK...

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 20, 2010 12:02 PM   in reply to Joel Glovier

    Photoshop comes with extension plugins (look in the plugins folder).  It would be nice to determine if those are related to the problem or not, but to do that we need a reproduceable case.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 29, 2010 6:55 PM   in reply to Joel Glovier

    I have exactly the same problem, where a multilayer file (about 8 layers) has been so badly corrupted that almost nothing is left and before closing it, flattening produced a bizarre pattern of teselated colour and pattern. when I restarted pscs5 and re-opened the file, most of the image data had disappeared. this is very worrying. although my file does include some gaussian blur, layers that have not had this applied are also affected. my file includes no strokes etc.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 29, 2010 7:15 PM   in reply to gumshoecamus

    Is it exactly the same in that the cause is directly related to Gaussian Blur?

    Or just that the file has become corrupted? (which can be caused by many, many things)

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 29, 2010 7:58 PM   in reply to Chris Cox

    Also, is everyone experiencing this issue on Photoshop CS5 for Mac?

     

    That's where I'm getting the issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 9, 2010 2:39 AM   in reply to Joel Glovier

    Hiya - just to say I've had exactly the same problem in CS5 - I was creating a file with about 6 layers, and applied a layer mask to a couple of the layers, suddenly it freaked out and put coloured blocks and random parts of the image everywhere on all the layers. I wasn't doing anything specific. It had different blocks of of the image in either C M Y or K and has now corrupted the file. I couldn't select and delete these blocks at all. Not sure if this helps at all but perhaps not.

     

    I'm running Extended Photoshop CS5 on a OS X 10.6.5.

     

    Deni James

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 9, 2010 5:26 PM   in reply to denijames

    Hiya - just to say I've had exactly the same problem in CS5 - I was creating a file with about 6 layers, and applied a layer mask to a couple of the layers, suddenly it freaked out and put coloured blocks and random parts of the image everywhere on all the layers.

    The "exact same issue" would require that the problem was caused when you used Gaussian Blur.

     

    Lot of things can cause image corruption: bad RAM, bad hard disk, bad GPU, video card driver bugs, etc.

     

    Also, are you running Photoshop CS5 12.0.2, or a previous build?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 13, 2010 5:55 AM   in reply to Chris Cox

    The "exact same issue" would require that the problem was caused when you used Gaussian Blur.

     

    C'mon Chris, cut us some slack here. Please take your "software programmer" hat off for a second and try to see through the lenses of "average photoshop user". We're giving you the best input we can here, so try to take the bits we are sharing and use your best Sherlock Holmes deduction skills... :-)

     

    So obviously the issue we are all complaining about and trying to report is the way Photoshop is corrupting the files with big randomized colored blocks and missing raster data.

     

    Although exactly when and how it happens is of utmost importance to you in being able to replicate it, consider that perhaps the bug is something broader and more general than a set of steps you might be able to replicate. Perhaps the bug is on a much broader layer of the software...i don't know - that's your job to discover.

     

    Just try to take what we are giving you and find the similarities....

     

    1) It seems everybody is experiencing this on the newly released Photoshop CS5 for Mac, so apparently the issue lies somewhere in the Cocoa porting of the software.

     

    I have never experienced this issue before upgrading to my CS5 Mac copy of Photoshop, and I've used Photoshop since version 6 circa 2000. I used 6 - CS5 on PC and never got this issue. I used CS4 - CS5 on Mac and only got this issue with CS5 Mac, while not doing anything I've never done on any of the past one or two versions - both PC and Mac.

     

    So apparently the issue lies in some layer of your Cocoa implementation of the software features.

     

    2) Regardless of the exact steps or featured used to produce the error, the result of the error to us users appears to be consistent: the users file is corrupted with missing segments of raster data (leaving transparency in the background) and/or parts of the image appear to have low-bit resolution blocks of color inserted, almost as though the color data is being scrambled or misinterpretted (as in this example screenshot from my user case:http://cl.ly/3KTx)

     

    Happy diagnosing. Hope this helps.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 13, 2010 5:48 PM   in reply to Joel Glovier

    1) It seems everybody is experiencing this on the newly released Photoshop CS5 for Mac, so apparently the issue lies somewhere in the Cocoa porting of the software.

    No, because not everyone is experiencing it.

    Also, we have similar complaints with EVERY version of Photoshop. The problem is usually traced to a bad RAM chip, bad hard drive, bad CPU, etc.

     

    To diagnose such a problem, we need steps to reproduce it.

     

    Confusing one set of steps (Gaussian Blur) with other sets of steps (pretty much anything else) is adding confusion, not helping solve the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 13, 2010 5:52 PM   in reply to Chris Cox

    No, because not everyone is experiencing it.

     

    Right - but actually I was referring to everyone HERE on this thread.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 15, 2010 12:58 PM   in reply to lclark00

    Just got the issue again today. I've been working all day on a document with around 200 layers, and many groups. It's a template document for several trading card designs.

     

    I used the Gaussian Blur filter several times already today very successfully, but on my most recent attempt the filter instead deleted most of the data from the layer I was working on, as well as the data from all of the other layers of which that layer was a copy.


    Specifically, I was producing a background texture - or rather modifying the color of a background texture I'd used in several other layers. The original layer was simply a layer that I filled with a color from my swatches (via cmd + delete) and then added a layer style for a certain pattern that I use as a background texture (a custom pattern).


    I wanted to modify this pattern to a darker color instead of the light tan that it is, so on the particular layer I was working on (which is a copy of the original I just referred to) I filled it with my new darker color (again cmd + delete), turned off the layer styles after I realized my pattern was still on, and then set the swatches to two colors that are close but one slightly darker and the other slightly lighter. Then I ran Filter > Add Noise, set to about 10% Gaussian. I then ran Filter > Blur > Guassian Blur at .5 px. Next I created a layer below, filled it with the base color, and set the layer above it to about 65% opacity. Then I merged the two layers together, and attempted to run the Gaussian Blur again.


    That's when Photoshop deleted all (or most) of the data from that layer, and random bits of data from other layers. It also seems to have deleted all the raster data from the other background layers which were similar to that original one I copied it from, as they are all transparent too.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 22, 2010 4:48 AM   in reply to lclark00

    This has happened to us 4 times now on different files and different macs the second time I phoned up Adobe support and was told to delete the photoshop preference. Which worked for a bit but then it happened again. It does seem to have a link with the gaussian blur but other than that, it can happen to anyone on any file? It just takes block chunks from the image changes colours etc..

     

    The studio are looking for answers and i can only dump preferences, replace from backup if there is a saved file as there seems to be little on this subject of corruption.

     

    The updates have done nothing to address the problem.

    Come on Adobe? If you want any files let me know I can give you some..

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 24, 2010 4:33 PM   in reply to robjfrost

    We haven't reproduced the problem at all.

    And we've been running Gaussian Blur and other commands pretty continuously under automation.

     

    There's probably some factor missing -- maybe a plugin, some system configuration (fonts, video card, etc.),

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 28, 2010 11:44 AM   in reply to Chris Cox

    We too are experiencing the same issues. It occurs when we apply a blur to a color block and it happened when we applied a blur to a Vector Smart object. The common theme I am reading about here and other threads is using the blur effect. We tried replicating each step on the file that corrupted (by using a previously saved copy) and we could not get it to replicate. But about an hour later, it happened again. Mac computer 27" Imac Intel Core i3, 8 GB 1333 MHz DDR3, 3.2 GHz, CS5 photoshop, the document had about 10 layers.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 29, 2010 3:39 AM   in reply to lclark00

    I have had this problem on several Macbook Pros (2005 version) and iMacs (2009 version). It is quite random and intermittent. There seems to be no way to reproduce it, but it always happens on files that have several layers, smart objects and layer masks.

     

    Once the file is corrupt, there seems to be no way to rescue it. 

     

    I have never encountered this problem on CS3/CS4, so it must be a bug with CS5.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 4, 2011 10:15 PM   in reply to lclark00

    Hi All,

     

    I'd just like to chime in & say I have been experiencing the same problem with Gaussian Blur & Motion Blur. 

    I'd LOVE to know any ideas for fixing/avoiding this error as it is driving me crazy.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 6:58 AM   in reply to lclark00

    Has anyone found a way to recover their file yet?!?  I've only encountered this problem in CS5 and it's happened on both Mac and PC platforms.  The issue occurs when Gaussian Blur is applied and/or "undone" (command + z or removal of step in the history pallet) to a multi layered file with layer masks peppered throughout.  Of course, Photoshop is most prone to create this corruption issue when you have not yet saved your or the first time and once it goes bad the artwork on any layer with a mask begins to repeat-x.

     

    The only way I can find to avoid this is the obvious "save often".  That said, I've lost some great artwork this past week to this issue that I would really like to get back.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 8:20 AM   in reply to mattkoyak

    -

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 10:51 AM   in reply to Marian Driscoll

    You probably can't recover if the data is corrupt in memory.

     

    But we have not been able to reproduce this problem at all.

    We really need more information about the files, the systems, etc. to see why it is happening for a few users (because it does not seem to be widespread).

    This could come down to a third party plugin issue, a CPU version issue (it's happened before), or a bug with a very rare trigger.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 11:22 AM   in reply to Chris Cox

    Hi What information do you need and I will post it.

     

    I do not use any 3rd party plugins, so that is not an issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 11:28 AM   in reply to Chris Cox

    Like other users, I'm not using any third party plugins and have experienced this issue on a PC with Windows 7 and Windows XP as well as on various Macs running OSX Snow Leopard.  It's is limited to CS5 and can be recreated in any multi-layered document that has not been saved, has layer masks applied to more than one layer and a gaussian blur is applied to a layer and then "undone" or removed using command + z or deletion of the step in the history panel.  Every user in my office can recreate this event.  Once the glitch occurs any layer with a mask becomes corrupt - the more you hide and reveal layers the more the pattern of the glitch repeats.  We've uninstalled, deleted preferences and wiped systems clean before reinstalling and still have the problem occasionally.  Each time, the trigger seems to be the step-back pf undo of gaussian blur to an unsaved document with layer masks.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 1:20 PM   in reply to big_smile

    Let's start with basics:

     

     

    What kind of processor are you using?

     

    What OS version?

     

    What GPU/Video card and is OpenGL drawing on or off?

     

    What plugins (you ruled out third party)?

     

    Have you installed any optional Adobe plugins, or plugins from a previous version of Photoshop?

     

    Have you tried disabling ALL plugins?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 1:21 PM   in reply to mattkoyak

    Every user in my office can recreate this event.

    It's odd that we're getting so few reports, then.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 1:43 PM   in reply to Chris Cox

    I'm the boss so those who would report the issue in my office have to go through me.  I'll get you the rest of the information you requested.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2011 1:48 PM   in reply to Chris Cox

    Help! This is driving me nuts.

     

    Mac OS X 10.6.5

     

    Hardware Overview:

     

      Model Name:     Mac Pro

      Model Identifier:     MacPro5,1

      Processor Name:     6-Core Intel Xeon

      Processor Speed:     2.93 GHz

      Number Of Processors:     2

      Total Number Of Cores:     12

      L2 Cache (per core):     256 KB

      L3 Cache (per processor):     12 MB

      Memory:     24 GB

      Processor Interconnect Speed:     6.4 GT/s

      Boot ROM Version:     MP51.007F.B01

      SMC Version (system):     1.39f11

      SMC Version (processor tray):     1.39f11

      Serial Number (system):     YM041026GWR

      Serial Number (processor tray):     J503900K0BH8B    

      Hardware UUID:     F848BB7F-89F1-5417-B376-C7DA31C7CD32

     

    Adobe Photoshop CS5:

    Version:     12.0

    Last Modified:     22/10/10 6:43 PM

    Kind:     Intel

    64-Bit (Intel):     Yes

     

    Yesterday I installed Eye Candy but the problem has been occurring way before this.

    No other plug ins etc.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2011 11:16 AM   in reply to Chris Cox

    What kind of processor are you using?

    What OS version?

     

    Model Name:    MacBook Pro

     

      Model Identifier:    MacBookPro3,1
      Processor Name:    Intel Core 2 Duo
      Processor Speed:    2.4 GHz
      Number Of Processors:    1
      Total Number Of Cores:    2
      L2 Cache:    4 MB
      Memory:    4 GB
      Bus Speed:    800 MHz
      Boot ROM Version:    MBP31.0070.B07
      SMC Version (system):    1.18f5

     

    What GPU/Video card and is OpenGL drawing on or off?

    NVIDIA GeForce 8600M GT:
      Chipset Model:    GeForce 8600M GT   
      Type:    GPU
      Bus:    PCIe
      PCIe Lane Width:    x16
      VRAM (Total):    256 MB
      Vendor:    NVIDIA (0x10de)
      Device ID:    0x0407
      Revision ID:    0x00a1
      ROM Revision:    3175

     

    Open GL drawing is on


    What plugins (you ruled out third party)?

    No Third Party

     

    Have you installed any optional Adobe plugins, or plugins from a previous version of Photoshop?

    No optional plugins, no previous versions

    I reformatted the Mac and re-intalled a fresh version of CS5, but the problem still remains.

     

    PS... Photoshop needs a one button option, so you can press the button and get a list of all the hardware and software that Photoshop is running on.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2011 5:46 PM   in reply to big_smile

    BigSmile:   Help->System Info

     

    but there are limits on what info it can get, and it's a bit verbose.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 20, 2011 12:52 PM   in reply to lclark00

    I'm on the Photoshop QE team and we are currently working on trying to reproduce this issue.

     

    Some stuff that will help us out:

    -Your system info

    -List of applications you have running

    -Specific information on when the problem occurs (for example, one user was seeing the problem as soon as the Gaussian Blur dialog popped up).

    -Screenshot(s) of your Activity Monitor right after you run into the problem

    -Sample process of Photoshop (In Activity Monitor, click on the Photoshop item in the list, then click on Sample Process at the top of the window)

    -Screenshot of your History panel (~30 steps or so) right after you run into the problem

     

    Please send this information directly to me at jrubbo AT adobe DOT com.

     

    We are also looking to do Connect sessions with people who can easily reproduce this problem. Please contact me if you are interested.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 20, 2011 1:54 PM   in reply to Jeanne Rubbo

    Hi Jeanne,

     

    Pls find attached some screen shots.

    I'm finding at the moment that I can barely use gaussian or motion blur without the error occurring.

     

    I run the standard Adobe suite for print (mostly ai & ps, sometimes id) & mail, calendar, Art files, Acrobat Pro/ Distiller (see attached doc pic)...

    I'll try & send the other info as I create it.

     

    Hardware Overview:

     

      Model Name:     Mac Pro

      Model Identifier:     MacPro5,1

      Processor Name:     6-Core Intel Xeon

      Processor Speed:     2.93 GHz

      Number Of Processors:     2

      Total Number Of Cores:     12

      L2 Cache (per core):     256 KB

      L3 Cache (per processor):     12 MB

      Memory:     24 GB

      Processor Interconnect Speed:     6.4 GT/s

      Boot ROM Version:     MP51.007F.B01

      SMC Version (system):     1.39f11

      SMC Version (processor tray):     1.39f11

      Serial Number (system):     YM041026GWR

      Serial Number (processor tray):     J503900K0BH8B    

      Hardware UUID:     F848BB7F-89F1-5417-B376-C7DA31C7CD32

     

    Thanks,

    Isabella

     
    |
    Mark as:
1 2 3 ... 6 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points