Possible hardware problem.

A few months back I bought an ipod nano with a dead screen off of ebay. The stereo in my car has an ipod connector and because I can control the ipod through the deck I really didn't need the display to work and welcomed the low price resulting from the defect. Upon it's arrival though, I found that the ipod had another problem which has been impossible to diagnose without a display. What I know for sure is that when the unit is left to idle for a couple minutes, it becomes unresponsive and requires a reset. I don't know if it's freezing up while attempting to shut down or having a hard time turning back on.
My questions are:
1. does anyone know what is causing this, and
2. can it be fixed with a cheap and easy component swap.

Sorry friend, but we are not technical support.... Others are having problems with thier older iPod classics when using iTunes 9 as there is a seperate thread out there regarding this problem. However I don't know if they have come to a resolution.
The only suggestion that I have is to read through that thread and see if any of thier suggestions work. However there is alot to sift through.
Best Regards!

Similar Messages

Looks serious. possible hardware problem. unable to install any OS.

Hi,
Powerbook was working absolutely fine. Stupidly, I attempted to watch a partially (97%) downloaded (with Bittorrent) movie (.wmv -- WM3) in Windows Media Player 9 in full screen mode. Half way through the movie freezes. I try and get out of full screen, nothing changes -- the whole machine is frozen. I restart. During boot there's a serious error -- kernel panic I think -- telling you to restart machine in various languages including Japanese. Restart. Freezes during start up window progress bar. Restart. Freeze.
I start up from the Jaguar disk 1 start up disk, go into Disk Utilties, repair disk -- errors found, and fixed apparently. Restart. Freeze.
I start up from DiskWarrior 4 start up disk and start it on the drive. Step 6: "Overlapped files detected" with a number after, and it starts taking ages. I left DW working for nearly two days until it seemed to have frozen (still on step 6).
I connect the sick PB to an iMac via firewire and start up the PB in disk target mode, the PB's drive appears on the desktop of the iMac and I'm able to easily with no problems copy off all my personal files. At that point I thought all was saved -- I was out of hot water, no further real problems. All I had to do is wipe the drive and reinstall etc.
I reformatted the drive from the iMac choosing to zero aswell. The PB's drive appears on the desktop empty and looking fine.
Start up the PB using Panther retail install disk one click install, it goes through checking the install disk then starts to check the target disk or actually install on the target disk -- at that point kernel panic -- 'restart machine' in various languages including Jap. Start up again using Panther disk, this time choose Disk Utilities to attempt to refromat the drive again, kernel panic before Disk Utilties even gets fully open.
I start up the PB using Jaguar retail install disk one, choose Disk Utilties -- fine. I reformat the drive, this time not bothering with zeroing. Fine. Go through to install Jaguar. Again it checks the install disk fine, then immediately after, kernel panic.
I tried partitioning the drive into two using Disk Utilties on Jaguar start up disk. My thinking was, maybe the start of the drive is damaged. Then tried to install onto partition two: panic. Just to check, tried to install to partition one: panic.
It's a 60GB drive. I installed Jaguar onto it ages ago successfully. The only difference was when doing it ages ago is I used the PB's internal CD/DVD drive. That had since broken and I've been using an external firewire CD/DVD drive -- all the above various Jaguar / Panther attempts were from the external drive. I just received a 2nd hand internal CD/DVD drive I bought on eBay -- I was blindly/stupidly hoping that using an internal CD drive would solve my problem but it hasn't.
What's the problem? It seems as if the initial Windows Movie Player crash has caused this, but that can't be can it? That was a software crash and I've since reformated the drive. There shouldn't be any remnants of that in anyway. So it's a hardware problem? But it was working fine before the crash and nothing has happened to the PB between the crash and now. But there's no two ways about it -- right now the PB seems terminally broken.
Any suggestions how to get my PB working again?
TIA,
John.

It's intalled. So it turns out I was lying when I said "The only difference was when doing it ages ago is I used the PB's internal CD/DVD drive." -- I forgot to mention there was no AirPort card in the PB when I installed Jag ages ago.
Also a small note: it seems an internal CD drive was necessary in the end. When the Panther install restarted and requested disk 2 I couldn't get it to recognize disk 2 from the external drive -- had to use the internal one to continue (although I didn't spend too much time/effort trying to get the external one to work but on the face of it it didn't seem to). (Although I can imagine there may be a way of installing stuff from disk 2 after having customized the install to not require anything from disk 2 for the first main automated install possibly? I may sell the internal CD/DVD drive if so as otherwise it was a waste of money).
Having installed Panther I put the AirPort card and the 2nd memory back in and started up -- all's apparently OK, but of course there's good reason not to be convinced of that. I didn't customize the Panther install as I wanted (because I didn't expect it to work). Not sure if I dare try wiping and reinstalling.
Obviously I'd feel happier knowing what the problem was/is. Looks like the AirPort card had something to do with it. But even when that was out the PB couldn't start from OS9. When formatting the drive (from OS X installer software) I'm sure I had the OS9 check box ticked. Even if I hadn't it wouldn't stop the OS9 CD working would it?; the hard drive just wouldn't appear once started up from the OS9 CD.
So I now have Panther up and running with both bits of memory in and the AirPort card in. I haven't messed around with/in Panther at all yet but on the face of it it seems fine.
Any ideas what the problem was/is? Any suggestions how to find out? Should I just ignore it and forget it ever happened (and cross my fingers and hope I never need to mess around with OS installs again)? Would be nice to know what's going on though. For a start it looks like if ever I want to install OS9 on it I won't be able to -- which actually may be something I want to do in the future possibly.
Thanks.

Speed - Possible Hardware Problem?

Greetings,
My laptop is a Satellite L655-S5058 running Windows 7 (64) and is approx. 3.5 years old. I recently noticed severe speed/response issues and none of the usual fixes were working. So I did a complete recovery, basically restoring it to its "out-of-box" condition. After doing that, the only thing I did was apply all the outstanding "urgent" MS updates to bring it back to date. I haven't restored any of my personal data or reinstalled any new programs...and it's STILL painfully slow, just like it was before. So now I"m wondering if there's a hardware component that could be causing this. I ran a diag using the built-in Toshiba utility, but it looks like a very quick test and it found no problems. I also used the WMD I downloaded from Microsoft to test the memory, but that found no problems.
Any ideas what else it could be? Is there a better utility I can download to test the hardware more thoroughly? I haven't been able to find anything.
Thank you in advance for any assistance.
Solved!
Go to Solution.

Satellite L655-S5058
When the hard disk is failing, multiple reads and writes must be made for success.
Check a drive for errors - check for both file and physical errors
-Jerry

Any suggestions for possible hardware problem with 8320

Having a problem with 8320. Phone seems to be scrolling by itself. Making the scrolling noise and mouse is moving by itself. Unfortunately when this happens, I can't do anything else involving the trackball. I have cleaned the trackball and updated the software hoping that it would help. It hasn't. To the best of my knowledge the phone has never taken any sort of shock from dropping. Any suggestions, aside from purchasing a new phone?

Lisa ~ Welcome to the Support Communities. Go here:
http://www.apple.com/support/iphone/essentials/
...and scroll down to the Basic Troubleshooting section. Click on the article entitled iOS: Not responding or does not turn on.

CD ejection/possible hardware problem?

After having purchased/given the iMac to my Mom in December 2011, the slot drive is now deciding to act up on us after only 3 separate CD uploads to iTunes (Why it took us soo long to upload, who knows?!! Anyway...) This happened this past friday...
Every time I tried to eject the CD I would hear a rthymic knocking of plastic(?) on metal that lasts about 3 seconds each time.
I search the forums for solutions and tried whatever I could find.
-- force eject, no go
-- Terminal prompt, no go
-- holding down the mouse during start up, no go
Seeing as we have a tendency to let the computer go into sleep rather than shutting down, I shut it down and left it off for over 12 hours. Upon booting it up again, it still wouldn't eject and again I got the rthymic knocking (of what I am assuming is a CD knocking against the metal housing??).
I was messing around with the CD/slot drive today and decided to press on the metal housing on the slot drive, and voilå!, it popped out!
(If you are looking at the slot drive, I'm pressing on the left hand side of the drive, about 1/4 of the way down from the top)
Since then I've uploaded 3 more CD (from our personal collection, no stickers on them), and it's this 4th (current) one that decides it's not going to cooperate...
So again, I'm making an assumption that I just have to hit the right spot to get it to pop out. Now the next question is-- is this a hardware issue/defect?
It has not been banged/dropped or otherwise man-handled since my Dad & I purchased it... seeing as how I'm the most technologically knowledgable person in the family, I do all the work for the rents, what is causing it to act up so?
I am about to call up my Local Genius bar & ask for help, however, I'd rather try to fix it myself before I trek across the river to the nearest Apple Store...
Any suggestions?

Contact Apple Service, iMac Service or Apple's Express Lane. Do note that if you have AppleCare's protection plan and you're within 50 miles (80 KM) of an Apple repair station, you're eligible for onsite repair since yours is a desktop machine. If you don't have it, get it before contacting Apple. It's the cheapest insurance policy you can get for a desktop machine.

When updating to Mountain Lion I get this measageThis disk has S.M.A.R.T. errors. This disk has hardware problem that can't be repaired. Back up as much data as possible and replace the disk.

When updating to Mountain Lion I get this measage
This disk has S.M.A.R.T. errors. This disk has hardware problem that can’t be repaired. Back up as much data as possible and replace the disk.
never had this before download of Mountain Lion.

As others have stated, this is a potentially catastrophic event. Consider yourself lucky, as hard drives usually just fail wihtout warning. Your disk could die at any time. This is a mechanical / physical failure, not software related.
Going forward, I would suggest utilizing a utility that monitors SMART status, which you obviously don't have, such as SpeedTools.

Possible NIC hardware problem?

Hi,
I have two sun servers, both solaris 9, that act as firewalls.
I have installed only OS Core. The firewall software is Checkpoint.
These two servers are in cluster (checkpoint xl).
I have many other sun servers configured in this way that work perfectly.
But with these two servers I have a lot of network problems.
For instance, if I issue a nestat -rn I see a lot of entries (about one hundred!!). Do you know what this happens?
My security admins think that there could be a nic hardware problem.
How can I be sure that the network cards are ok?
If I run, on both servers, from ok prompt:
test net
I get
rejecting alloc-mem?
What does this mean?
The servers are:
- SUNFIRE V120
- SUNFIRE V240
Can you help me?
Thanks,
Tarek

I would just like to make the point that even though you may have great stability with a number of systems without applying firmware and OS patches, it does not mean that the system you are currently experiencing these issues with will not benefit from firmware upgrade. Some of the systems may have different component revisions that require firmware upgrade. Some of the features that are included in firmware upgrades can improve asr ( automatic system recovery ), hardware diagnosability, hardware integrity and generally improves chances of discovering and isolating faults. So it would be a good idea to implement a plan to upgrade all your systems with the patest firmware.
I would put this system on alert and make a service call with Sun, asr ( automatic system recovery ) can detect early signs that a component is failing and just clearing the disk from asr should not be the only step taken here, the disk may need to be replaced.
I am currently looking through the internal hand book for some references for you, there should be some good spectrum stuff that I can point you to, I'll update shortly.
One more thing, when you were configuring Solaris for FW-1, there are a number fo kernel parameters to change, misconfiguration of any of these parameters could be a cause for FW-1 to report errors.
On the output from netstat -rn, I wouldn't worry about that too much, if the system is a gateway for a large number of hosts it will probably have an enrty for all networks being visted by hosts on the client side.

For the second time (I've been to the Genius Bar once already) my WiFi isn't working on my iPhone 4S. This is really infuriating and costly!!! I see others have the same issues. Can't Apple do anything about this? It's obviously a hardware problem!

For the second time (I've been to the Genius Bar already once with this) my Wifi isn't working. They gave me a new iphone last time, but the new one has the same issue as the old one, I'm guessing. I've tried resetting the network but that doesn't work.
I see others have this issue too.
If this is a hardware problem why doesn't Apple fix it? Or do I just have to wait another year for another upgrade?
Currently it's not costing me anything - yet - because I've got the Apple Warranty but this is totally frustating!!! I bought the original phone (which has been replaced in July 2012. The new phone (without working Wifi) is a month old.
Will try Restore via ITunes before (I will invariably) have to return to the Genius Bar for another Iphone 4S unless someone has an ingenius solution here?..?

sematson wrote:
If this is a hardware problem why doesn't Apple fix it? Or do I just have to wait another year for another upgrade?
For what reason, other than making yourself look foolish, would you ask questions that we users could not possibly answer as we're NOT Apple?
Basics from the manual are restart, reset, restore from backup, restore as NEW. Nothing more "ingenius" to suggest than these steps that Apple has outlined in the manual. If these steps don't work, then go back to the Apple store.

"DPC_watchdog_violation" happens almost everyday, tried re-installing, is this a hardware problem?

Hello, I'm from Hong Kong. You guys must be wondering why I'd post in a foreign forum instead of local one - I cant find any support from my local forum. I cant even find this model form my local Website.
First of all, I brought this laptop (Envy 14) in 2013 from my so called "University Notebook Scheme". But once I got my first Envy, problem arised - my screen keeps flashing. I went back to the store and replaced it with a new one. Yet, this "new one" keeps having "DPC_watchdog_violation" almost everyday, no matter what Im doing - browsing the Net, using iTunes, even when Im using Microsoft Office for my assignments.
I've tried many solutions suggested: updating software & drivers, and reinstalling the windows; nothing works. Instead, more problem arised throughout these 2 years: my screen starts to flash, sometimes I cant even turn my computer on (power button on with a black, turned on, screen). I cant update my windows - "Failure configuring Windows updates, Reverting changes" and got stuck in the update loop.
I'm scared to do anything with this laptop now, even typing this "problem discription". I stored every files into the Dropbox for safety purposes. I save my Word documents every minutes, try to run as less programme as I could.
I've been wondering if this is a hardware problem, a serious one. Some of my classmates also got this Laptop from the University Scheme as well, most of them reported with the same issue (especially for the screen/display issue). With the notorious HP's repair and warranty service, I'm discouraged to sent my Laptop to them. I've even heard that I'll be charged even I'm still under warranty.
P.S. sorry if I have made any grammatical mistakes.

Additional Information for my Laptop (from WhoCrased):
System Information (local)
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: HP ENVY 14 Sleekbook, Hewlett-Packard, 198C
CPU: GenuineIntel Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8351010816 total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 27/02/15 7:02:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022715-19390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 27/02/15 7:02:39 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x770DB)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation DPC_WATCHDOG_VIOLATION
On Fri 27/02/15 3:22:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022715-15015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 26/02/15 7:39:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022615-33093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 16/02/15 9:27:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021615-23328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 14/02/15 9:37:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021415-28265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 28/01/15 3:01:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012815-19171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 27/01/15 2:44:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012715-33937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 23/01/15 3:33:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012315-63484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 20/01/15 5:31:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012015-18734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

3g is not working but 2g is fine - could this be a hardware problem?

Just recently updated to IOS6 and now can't get 3g, but I also dropped my phone at the same time.
I've tried all the resets and changed SIM and the issue is definitely with the handset either hardware or software installed on it.
Is it possible that I've dammaged the 3g antenna? I get 2g fine, and wifi fine, so I guess my question is does the iPhone have seperate antennas for 3g?
Thanks
Dave

It very likely could be a hardware problem.
Are you certain that you did not simply disable 3G? Check Settings > General > Network > Enable 3G to ensure it is ON.

I downloaded OS Mountain Lion 10.8... and when I was getting ready to install I get "This disk has S.M.A.R.T. errors. This disk has a hardware problem that can't be repaired. I have read some of the same comments below. Why?

I was trying to install OS X Mountain Lion 10.8... and I got an error saying, "This disk has S.M.A.R.T. errors. This disk has a hardware problem that can't be repaired. I saw several other questions below of people having the same or similar problems. Does this mean that my hard drive is about to crash? I plan to head to the place I purchased and have it checked out. I backed up my data a couple of days ago. Any comments?

Yes, S.M.A.R.T. is a built-in diagnostic on the hard drive, and it is reporting a problem that may cause it to fail.
You can see the same status in Disk Utility, and possibly get more info. Run Disk Utility and select the DRIVE in the sidebar. Be sure to select the DRIVE and not the volume indented below it. At the bottom of the window, there is a field for S.M.A.R.T. Status. If there is no problem, it should say Verified.
You can also do a Get Info on the drive (File -> Get Info) in Disk Utility, and the Info window provides more detailed information (toward the bottom) about what is being checked.

Is this a hardware problem?

I have had my Iphone 4 for a couple months now. When I updated it to ios 5.0 I didn't have any problems with it. At first, then after awhile I noticed that it started doing this really weird thing. Sometimes, I could be either using an app, or not doing anything at all and it just be on the home screen, and suddenly the screen would sort of pause and the blinking circle would show up, and maybe last 30 seconds - 1 minute, and then my lock screen asking for my passcode would pop up. I didn't think anything of it, because like I said, it was sort of random and I figure it was just something that happened sometimes, like with computers. Then recently, as in this past weekend, I noticed it was doing it more often (I was out of town and using the phone a lot more than I have in the past) and realized it was doing it more often. I had asked the guy at my AT&T store if he knew what was wrong with it, said he never heard of a phone doing that and to update to 5.0.1 and if it still did to call Apple support. So yeterday, i called Apple support and told him what was going on, he also seemed ot have no idea of this problem, told me to update to 5.0.1 and if it still did it, to call back. So I updated, it seemed to work at first but then it's been doing it again, and even more. Such as its noon as I'm writing this and I swear its done it already six times since I woke up 6-7 hours ago. That's just when I notice it. if it's plugged in, either to the computer or the wall, the way I realize its done that is because it'll beep, like when you connect it. My main question is, has anyone ever heard of, or expereinced this problem? Is it a hardware problem? Software? Update? Something I did? The phone works wll enough for what I need it for, and I'll be happy with that, as long as it keeps working (again, I've only had it two months, so I can't upgrade for a little over a year).
Is it possible that this could be a water damage result, as I may have gotten some water on the phone by accident? (Another eason I'm asking about other issues). There are no signs of corrosion or anything anywhere on the phone. So I'm just curious about any help any one could provide. thanks!

Just to update, I took my phone to AT&T (since my nearest Apple store is two hours away and before making a drive wanted to see if they could help). Two different guys looked at the phone and tried different things and both said they thought it was something in the software and it turned out the problem was something in the settings. We reset ALL settings and so far it's gone nearly 36 hours without doing it ONCE (and it was doing it like, every 10-15 minutes). so I hoping that that means its totally fixed the problem. So I'm still not sure exactly what it was, but I'm glad to know that all I had to do was push one button that saved me a two hour drive as well as $149 (if not possibly more).

Troubleshooting Airport-Hardware Problems

Hello - I am wondering if anyone knows of a way to test if the airport card itself is malfunctioning or if there is possibly a different hardware problem.
Several months ago I believe my ethernet port got fried in a lightning storm (because my router, modem and ethernet port in my PC all got fried). I've been solely using my airport card since.
A couple days ago that didn't work either. I am able to connect wirelessly with my new iMac, so it doesn't seem that the problem is with my router. I cannot connect at any of my other wireless spots either.
Before I try to buy a new airport card, I'd like to find out if there's a way to test the hardware.
I have tried reinstalling the OS by doing a Archive and install, but that didn't seem to do any good.
Thanks.

Hi, Steve. Does System Profiler "see" your Airport card? If not, the first thing to make sure of is that your Airport card cage is securely connected to your logic board. That connection tends to work loose over time, especially in Tibooks that are picked up and transported frequently.
Go to this page for easy instructions on removing the Airport card from a Tibook. As soon as you get the bottom cover off the machine, the card is right in front of you. First remove it gently from its slot or cage, then reseat it firmly. Finally, press down hard on the rectangular tab at the end of the ribbon cable that's attached to it — that's its connector to the logic board, and that's what most often works loose. If yours is loose at all, you'll feel it click softly into place as you press on it. Then put the bottom cover back on and test again to see whether System Profiler sees the card. Post back with results.

New Drive has a Hardware Problem?

Hi,
The old hard drive in my iMac finally failed (it was a Seagate with a known issue, but I never got it replaced). Today I put in a brand new drive, exactly same model as the old, but I still get the S.M.A.R.T. error "This Drive has a Hardware Problem that can't be Repaired".
Any clue what could possibly be wrong? I may have misplaced the EMI foam slightly (after some time, the fan spins up), but could that really be the cause? There were no fan problem with the old drive installed.
I follewed this iFixIt guide:
http://www.ifixit.com/Guide/iMac+Intel+27-Inch+EMC+2309+and+2374+Hard+Drive+Repl acement/1634/1
Thanks!
Michael Knudsen

I don't understand the SMART report, but unless you got a replacment directly from Apple, it wouldn't have been an exact replacment. That drive, even if it's the same model, has to have a special firmware for the internal temperature sensor and that's only available from Apple. If you've read the OWC blog for the late 2009s that says that you ony need to replace the drive with one from the same manufacturer in order to use the same sensor cable, I believe that's not correct.
The spinning up can be cured by using the free SSD FAN Control. But no idea if that's related to the SMART error. I only know about the temp sensor issue related to this. If this doesn't fix it, maybe you got a bad drive or the problem is located elsewhere, maybe on the SATA controller on the logic board. No idea.
http://exirion.net/ssdfanctrl/

Treo 650- Can't get service after trip to Thailand & use of different SIM card - AT&T says it is a hardware problem

I have used my Treo 650 for years in the US. I've also taken it to other countries (Africa, Europe) and used SIMS purchased there for service while in those locations. Upon returning to the US after each trip, I've always been able to use my US SIM to get my US service back.
However, I went to Thailand in November and used a SMILE SIM and another Thailand SIM, both of which worked in Thailand. Unfortunately, upon returning to the US, my US SIM won't work for getting service any more. (I am using my US SIM in a Nokia phone in the meantime, and it is working. When I put the SIM into my Treo, it will transfer the text messges, but will not connect to my service provider, AT&T.)
I called AT&T and they said it was a hardware problem. I suspect it might be a "lock" problem with one of the Thailand companies. Is it possible that the Thai company locked my cell phone?
So my question is, how can I fix this? Whatever the problem is, I'd sure like my service back! Please help!!
Post relates to: Treo 650 (Unlocked GSM)

I don't think a SIM card can lock your phone. Did you let them do anything with the keyboard?
Can you try with a friend's AT&T or T-Mobile SIM card and see whether either will work?
Edit: You can ask about Thai mobile phone company issues on this board: Internet & Technology @ Paknam Web Thailand Forums
Message Edited by Jeffro on 02-26-2009 12:07 AM

Possible hardware problem.

Similar Messages

Maybe you are looking for