5 Kernel panics in 4 hours - is my i7 quad Mini at it's end?

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
Hi there,

As mentioned in the title already, I was on vacation for 2 weeks, switched on my system today and after 15 minutes or so, the first kernel panic appeared.
After restarting, I got strange graphic artifacts on both of my screens.
I pulled one of the two 4GB RAM modules (original from Apple).
I just got to copy the log from the last kernel panic just 10 minutes ago (with only 4GB RAM):


Interval Since Last Panic Report: -37 sec
Panics Since Last Report: 1
Anonymous UUID: AD53CAE6-ECD4-40CD-9D65-8DECAF4261D7

Sun Jan 8 23:14:39 2012
panic(cpu 2 caller 0xffffff80002c266d): Kernel trap at 0xffffff7f817690cb, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff8176fc47c5, CR3: 0x000000002a9f1020, CR4: 0x00000000000606e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff80b31ab750, RBP: 0xffffff80b31ab860, RSI: 0x0000000000000001, RDI: 0x0000000000000001
R8: 0x0000000000000007, R9: 0x0000000000000060, R10: 0x0000000000000020, R11: 0x0000000000000060
R12: 0xffffff8018702800, R13: 0xffffff800daa1000, R14: 0x0000000000000000, R15: 0xffffff8176fc47c5
RFL: 0x0000000000010246, RIP: 0xffffff7f817690cb, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0xffffff8176fc47c5, Error code: 0x0000000000000000, Faulting CPU: 0x2

Backtrace (CPU 2), Frame : Return Address
0xffffff80b31ab410 : 0xffffff8000220702
0xffffff80b31ab490 : 0xffffff80002c266d
0xffffff80b31ab630 : 0xffffff80002d7a1d
0xffffff80b31ab650 : 0xffffff7f817690cb
0xffffff80b31ab860 : 0xffffff7f8178fefa
0xffffff80b31ab880 : 0xffffff7f8174c8ee
0xffffff80b31ab8b0 : 0xffffff7f817a86c6
0xffffff80b31ab8e0 : 0xffffff7f817a8b84
0xffffff80b31ab9e0 : 0xffffff7f81753956
0xffffff80b31aba10 : 0xffffff7f817a1296
0xffffff80b31aba30 : 0xffffff7f81757002
0xffffff80b31abb60 : 0xffffff7f81754119
0xffffff80b31abbc0 : 0xffffff80006523be
0xffffff80b31abbe0 : 0xffffff8000652c9a
0xffffff80b31abc40 : 0xffffff800065343b
0xffffff80b31abd80 : 0xffffff80002a3898
0xffffff80b31abe80 : 0xffffff8000223006
0xffffff80b31abeb0 : 0xffffff8000214829
0xffffff80b31abf10 : 0xffffff800021bb58
0xffffff80b31abf70 : 0xffffff80002ae8a0
0xffffff80b31abfb0 : 0xffffff80002d8383
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelHD3000Graphics(7.1.4)[7C2BC719-51AD-39F0-85ED-92590A1E27A4]@0xffffff7f8174b000->0xffffff7f8182afff
dependency: com.apple.iokit.IOPCIFamily(2.6.7)[6D54F06A-46B7-37FC-AF22-DE68DC18A1A3]@0xffffff7f807d9000
dependency: com.apple.iokit.IONDRVSupport(2.3.2)[6517D9A6-58F5-3CFC-B021-C882306150D5]@0xffffff7f80cf6000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[55FF26D3-292D-3B4B-8AB7-1D25C8B4313B]@0xffffff7f80cbe000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
11C74

Kernel version:
Darwin Kernel Version 11.2.0: Tue Aug 9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64
Kernel UUID: 59275DFA-10C0-30B3-9E26-F7B5DFB1A432
System model name: Macmini5,3 (Mac-7BA5B2794B2CDB12)

System uptime in nanoseconds: 16988172595774
last loaded kext at 3632468503593: com.apple.filesystems.afpfs 9.8 (addr 0xffffff7f8111e000, size 356352)
last unloaded kext at 141305768376: com.apple.driver.AppleUSBUHCI 4.4.5 (addr 0xffffff7f80ad4000, size 65536)
loaded kexts:
com.paceap.kext.pacesupport.snowleopard 5.8
com.uaudio.driver.UAD2System 6.1.0
at.obdev.nke.LittleSnitch 2.4.4
com.promise.driver.stex 5.0.50
com.apple.filesystems.afpfs 9.8
com.apple.nke.asp_tcp 6.0.1
com.apple.driver.AppleBluetoothMultitouch 66.3
com.apple.driver.AppleHWSensor 1.9.4d0
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.59
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleHDA 2.1.3f7
com.apple.driver.AppleMikeyDriver 2.1.3f7
com.apple.driver.ApplePlatformEnabler 2.0.4d2
com.apple.driver.AGPM 100.12.42
com.apple.driver.AppleUpstreamUserClient 3.5.9
com.apple.driver.AppleMCCSControl 1.0.26
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.2.1
com.apple.driver.AppleLPC 1.5.3
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.5d4
com.apple.driver.AppleIntelHD3000Graphics 7.1.4
com.apple.iokit.SCSITaskUserClient 3.0.1
com.apple.driver.AppleIRController 312
com.apple.driver.AppleRAID 4.0.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 33
com.apple.iokit.IOAHCIBlockStorage 2.0.1
com.apple.driver.AppleFWOHCI 4.8.9
com.apple.driver.AirPort.Brcm4331 512.20.18
com.apple.driver.AppleSDXC 1.1.2
com.apple.iokit.AppleBCM5701Ethernet 3.0.8b2
com.apple.driver.AppleUSBHub 4.5.0
com.apple.driver.AppleAHCIPort 2.2.0
com.apple.driver.AppleUSBEHCI 4.5.5
com.apple.driver.AppleEFINVRAM 1.5.0
com.apple.driver.AppleACPIButtons 1.4
com.apple.driver.AppleRTC 1.4
com.apple.driver.AppleHPET 1.6
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.4
com.apple.driver.AppleAPIC 1.5
com.apple.driver.AppleIntelCPUPowerManagementClient 167.1.0
com.apple.nke.applicationfirewall 3.2.30
com.apple.security.quarantine 1
com.apple.driver.AppleIntelCPUPowerManagement 167.1.0
com.apple.security.SecureRemotePassword 1.0
com.apple.driver.AppleMultitouchDriver 220.62.1
com.apple.driver.IOBluetoothHIDDriver 4.0.1f4
com.apple.kext.triggers 1.0
com.apple.driver.AppleAVBAudio 1.0.0d11
com.apple.driver.DspFuncLib 2.1.3f7
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.iokit.IOFireWireIP 2.2.4
com.apple.driver.AppleUSBAudio 2.8.2f5
com.apple.iokit.IOSurface 80.0
com.apple.iokit.IOBluetoothSerialManager 4.0.1f4
com.apple.iokit.IOSerialFamily 10.0.5
com.apple.iokit.IOAVBFamily 1.0.0d22
com.apple.iokit.IOAudioFamily 1.8.3fc11
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 2.1.3f7
com.apple.iokit.IOHDAFamily 2.1.3f7
com.apple.driver.ApplePolicyControl 3.0.16
com.apple.driver.AppleGraphicsControl 3.0.16
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleSMC 3.1.1d8
com.apple.driver.IOPlatformPluginFamily 4.7.5d4
com.apple.iokit.IONDRVSupport 2.3.2
com.apple.driver.AppleIntelSNBGraphicsFB 7.1.4
com.apple.iokit.IOGraphicsFamily 2.3.2
com.apple.iokit.IOSCSIBlockCommandsDevice 3.0.1
com.apple.driver.BroadcomUSBBluetoothHCIController 4.0.1f4
com.apple.driver.AppleUSBBluetoothHCIController 4.0.1f4
com.apple.iokit.IOBluetoothFamily 4.0.1f4
com.apple.driver.AppleUSBHIDKeyboard 152.3
com.apple.driver.AppleHIDKeyboard 152.3
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.0.1
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.7
com.apple.iokit.IOCDStorageFamily 1.7
com.apple.iokit.IOUSBMassStorageClass 3.0.0
com.apple.driver.AppleUSBMergeNub 4.5.3
com.apple.iokit.IOUSBHIDDriver 4.4.5
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.driver.AppleThunderboltDPOutAdapter 1.5.8
com.apple.driver.AppleThunderboltDPInAdapter 1.5.8
com.apple.driver.AppleThunderboltDPAdapterFamily 1.5.8
com.apple.driver.AppleThunderboltPCIUpAdapter 1.2.1
com.apple.driver.AppleThunderboltPCIDownAdapter 1.2.1
com.apple.driver.XsanFilter 403
com.apple.iokit.IOSCSIParallelFamily 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.0.1
com.apple.driver.AppleThunderboltNHI 1.3.2
com.apple.iokit.IOThunderboltFamily 1.7.4
com.apple.iokit.IOFireWireFamily 4.4.5
com.apple.iokit.IO80211Family 411.1
com.apple.iokit.IOEthernetAVBController 1.0.0d5
com.apple.iokit.IONetworkingFamily 2.0
com.apple.iokit.IOUSBUserClient 4.5.3
com.apple.iokit.IOAHCIFamily 2.0.7
com.apple.iokit.IOUSBFamily 4.5.5
com.apple.driver.AppleEFIRuntime 1.5.0
com.apple.iokit.IOHIDFamily 1.7.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 165.3
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 331
com.apple.iokit.IOStorageFamily 1.7
com.apple.driver.AppleKeyStore 28.18
com.apple.driver.AppleACPIPlatform 1.4
com.apple.iokit.IOPCIFamily 2.6.7
com.apple.iokit.IOACPIFamily 1.4
Model: Macmini5,3, BootROM MM51.0077.B0E, 4 processors, Intel Core i7, 2 GHz, 4 GB, SMC 1.77f0
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353237334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE4), Broadcom BCM43xx 1.0 (5.100.98.75.18)
Bluetooth: Version 4.0.1f4, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci105a,8760, sppci_raid, Thunderbolt@106,0,0
Serial ATA Device: M4-CT256M4SSD2, 256,06 GB
Serial ATA Device: M4-CT256M4SSD2, 256,06 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfa120000 / 5
USB Device: eLicenser, 0x0819, 0x0101, 0xfa123000 / 7
USB Device: iLok, 0x088e, 0x5036, 0xfa121000 / 6
USB Device: AmazonBasics ODD, 0x060f (Joinsoon Electronics Mfg. Co., Ltd.), 0x1007, 0xfa130000 / 4
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8281, 0xfa113000 / 8
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: Duet USB, 0x0c60 (Apogee Electronics Corp), 0x0007, 0xfd130000 / 5
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd120000 / 4
USB Device: Apple Keyboard, apple_vendor_id, 0x0221, 0xfd122000 / 6
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
FireWire Device: UAD2_Satellite_Quad, Universal_Audio, 800mbit_speed


Can anyone say something about it?
Any more details needed?

Thanks

alq.
 

FrankHahn

macrumors 6502a
May 17, 2011
735
2
The KP report indicates that the KPs were probably cause by the following third-party kernel extensions:

com.paceap.kext.pacesupport.snowleopard 5.8
com.uaudio.driver.UAD2System 6.1.0
at.obdev.nke.LittleSnitch 2.4.4
com.promise.driver.stex 5.0.50

Remove them and see if KPs will disappear.
 

LPZ

macrumors 65816
Jul 11, 2006
1,221
1
The KP report indicates that the KPs were probably cause by the following third-party kernel extensions:

com.paceap.kext.pacesupport.snowleopard 5.8
com.uaudio.driver.UAD2System 6.1.0
at.obdev.nke.LittleSnitch 2.4.4
com.promise.driver.stex 5.0.50

Remove them and see if KPs will disappear.
The panic was triggered by an instruction in com.apple.driver.AppleIntelHD3000Graphics.

I'd do a memory test, and maybe check internal temperatures.
 

Mr. Retrofire

macrumors 603
Mar 2, 2010
5,040
451
www.emiliana.cl/en
Hi there,

As mentioned in the title already, I was on vacation for 2 weeks, switched on my system today and after 15 minutes or so, the first kernel panic appeared.
After restarting, I got strange graphic artifacts on both of my screens.
I pulled one of the two 4GB RAM modules (original from Apple).
I just got to copy the log from the last kernel panic just 10 minutes ago (with only 4GB RAM):
You have a lot of third party devices and drivers (kernel extensions). It is very likely, that one of them causes the problems under the "new" OS X Lion. Make sure you've installed all updates for the devices, and that the vendor says that the device driver is compatible with Lion. Some companies provide only Snow Leopard support, so this can be the problem. Or you installed older software, which has Snow Leopard drivers, but of course no Lion drivers.

My first impression was, that it is a IGP (HD 3000) problem, but that is probably wrong, because third party kernel extensions (device drivers) can (over-) write data of other kernel extensions in the kernel space.

I would do the following, to exclude hardware problems:
1. Shutdown the Mac and disconnect all external devices.
2. Install a fresh copy of Mac OS X on a USB HDD or flash drive (>= 16 GB). Then use this copy to start the Mac.

If your Mac shows no hardware problems with this configuration, you know it is a software (device driver) problem.
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
Thanks for all the input.
Just to add one more thing that is quite interesting:
I started the HW test last night and after a while running the test,
the same graphic artifacts appeared. I then had to force power off my Mini
with the power switch.
Any ideas if that can still be faulty RAM?
Or is it really related to the HD3000?
I suppose in the HW test environment that is being loaded,
there are no 3rd party drivers etc. loaded or am I wrong?
Other than that, I was running this system for about 3 months
without any problem and I did not change anything, nor updates
of any software.
Pretty depressing.

alq.
 

philipma1957

macrumors 603
Apr 13, 2010
6,271
191
Howell, New Jersey
How old is your mini? Do you have applecare?
if he has an i7 quad core mini it can't be older then july 2011. if he purchased it from a real dealer he should have coverage. brazil honors apple care. my opinion is his ram is bad. he has the quad core and it uses the ddr3 ram 512mb of the 8gb ram placed in it. I would run the mac with 1 stick in one slot and see what happens. if it crashes I would move the same stick to the second slot if it crashes. I would take that stick out and put it on the side. I would do the same tests with the second stick. if it crashes in both slots I would send the mac in for repair.

If one of the sticks is good then the ram is the problem. if both sticks work in one slot but not the other then the slot is bad. maybe it is just one ram stick and it will be an easy fix.


one more thing make sure your fan is spinning... Apple has sent me 4 machines with loose fans causes lots of crashes
 

GoCubsGo

macrumors Nehalem
Feb 19, 2005
35,753
142
Thanks for all the input.
Just to add one more thing that is quite interesting:
I started the HW test last night and after a while running the test,
the same graphic artifacts appeared. I then had to force power off my Mini
with the power switch.
Any ideas if that can still be faulty RAM?
Or is it really related to the HD3000?
I suppose in the HW test environment that is being loaded,
there are no 3rd party drivers etc. loaded or am I wrong?
Other than that, I was running this system for about 3 months
without any problem and I did not change anything, nor updates
of any software.
Pretty depressing.

alq.
Did you add more ram by chance? What is running now on the machine? For example, when my mac boots I am automatically running iStat menus, the drop box extension, weather bug, and then anything that normally starts up with any mac. The first thing I'd do is remove those third party apps and then see what happens.
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
@LPZ - the link doesn't work here

@jessica. - no, it's a BTO 8GB from Apple directly. As mentioned before, I also got the graphic artifacts when running the hardware test module. I do not believe that in this mode any 3rd party stuff is loaded. Anyhow, back home from work started the machine up, was running fine for about 30 minutes and again the graphic artifacts (without the kernel panic message). Now I restarted without anything plugged in (except Thunderbolt, HDMI and my USB-Audio interface (Apogee Duet 2). Oh, of course, the keyboard is also plugged in (original Apple).

I hope it's not any serious hardware stuff. Of course I do not have any warranty, because I exchanged the stock drives with 2 SSD's.

For those who are interested how it looks like: 8d6f9f72.jpg

Any other hints & tips are very welcome.

alq.
 

LPZ

macrumors 65816
Jul 11, 2006
1,221
1
@LPZ - the link doesn't work here

alq.
Works for me. Here's the main content:

To start up into Safe Mode (to Safe Boot), do this:

Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
During startup in Mac OS X v10.4 through Mac OS X v10.6.8, you will see "Safe Boot" on the login window, which appears even if you normally log in automatically. During startup in Mac OS X v10.2 through v10.3.9, you will see "Safe Boot" on the Mac OS X startup screen.

To leave Safe Mode, restart the computer normally, without holding any keys during startup.
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
ok, thanks.

Update from my side - Mini hung up even after pulling all ext. hardware.
After that I pulled the HDMI cable which connects one 24" display.
Since then I am running fine only with the second display (23") through my Pegasus R6 and Mini Displayport to DVI adapter.
I will continue using the Mini with only one display hooked up through Thunderbolt. If this works out to be running fine, I will try to connect only the HDMI connected Display tomorrow.
Any ideas what causes that strange behavior?
Since I got my Mini I was running it with 2 displays without any problems and
now this :(

alq.
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
Update 2:

I was restarting the Mini again today, same config as yesterday.
Graphic artifacts again after 20 mins.
After forced power down and restarting, the Mini did not start anymore.
3 beeps and thats it.
RAM defect?

alq.
 

philipma1957

macrumors 603
Apr 13, 2010
6,271
191
Howell, New Jersey
Update 2:

I was restarting the Mini again today, same config as yesterday.
Graphic artifacts again after 20 mins.
After forced power down and restarting, the Mini did not start anymore.
3 beeps and thats it.
RAM defect?

alq.
3 beeps is the ram. bring it in for applecare
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
3 beeps is the ram. bring it in for applecare
I would, if I did not swap the original HD's for SSD's..

Thanks anyway for confirmation.
Today I will try to put the 8GB of my '11 Macbook Pro into the Mini.
Hoping for success

alq.
 

jamesryanbell

macrumors 68020
Mar 17, 2009
2,171
93
I would, if I did not swap the original HD's for SSD's..

Thanks anyway for confirmation.
Today I will try to put the 8GB of my '11 Macbook Pro into the Mini.
Hoping for success

alq.
Why not just put the original ones back in before you take it in? (HUGE no-no to sell those if you ever consider using AppleCare...hope you didn't do that)
 

calderone

macrumors 68040
Aug 28, 2009
3,679
86
Seattle
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Put the original drives back in and get it sorted with Apple.
 

Fishrrman

macrumors P6
Feb 20, 2009
18,046
5,984
Suggestion (may help, may not):

Remove the RAM, then reseat it, then try again.

The RAM modules may be ok, but not properly seated...
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Put the original drives back in and get it sorted with Apple.
It is a little bit more complicated as it seems.
I bought my Mini in my home country in Europe, but I am living in Brazil.
And to be honest, for a price tag of EUR 45,- I am not willed to go through all this stuff. IF it is really "just" broken RAM.

alq.

----------

Suggestion (may help, may not):

Remove the RAM, then reseat it, then try again.

The RAM modules may be ok, but not properly seated...
Thanks for the hint, but I tried already everything with the RAM:
1st module in first slot, in second slot.
2nd module in first slot, in second slot.

The funny thing was only that the Mini started, but hung up after a while with the graphical problems posted above..
The 3x beeping happened only once during all the kernel panics and graphical hickups.
But now the Mini doesn't start anymore and keeps just beeping..

I really hope it's just the RAM

alq.
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
Guess what guys - I put in the RAM from the Macbook Pro and it kept beeping!
After that I put in again one of the original RAM modules in the 2nd slot (the one
that is closer to the bottom cover) and until now it's running.
Let's see for how long....

alq.
 

philipma1957

macrumors 603
Apr 13, 2010
6,271
191
Howell, New Jersey
Guess what guys - I put in the RAM from the Macbook Pro and it kept beeping!
After that I put in again one of the original RAM modules in the 2nd slot (the one
that is closer to the bottom cover) and until now it's running.
Let's see for how long....

alq.
well that sounds like a bad slot. I do think applecare works in brazil even if you purchased in europe, but you need the oem hdds and oem ram.
 

alq

macrumors member
Original poster
May 6, 2011
80
8
Panamá
well that sounds like a bad slot. I do think applecare works in brazil even if you purchased in europe, but you need the oem hdds and oem ram.
I will check that. I'll be in Europe again in Feb, so I can pick up the original HD's that I left in my house there.
Thanks

alq.