Strange hardware problems, possibly interrelated

This is an odd constellation of problems, some of which I understand and some I don't.
Problem 1: I think my iBook is overheating - if I don't use it in front of a window with a fan going, it randomly locks up on me. I'm hoping it's a problem with the fan, but I need more feedback before I take the thing apart again. What else could cause an iBook to overheat?
Problem 2: I can't move it while it's on unless I'm extremely careful about it. If I do, when I settle in my new location I discover that my trackpad works but that nothing can be clicked on. A restart fixes it, but still. I'm thinking a loose connection somewhere, but again I'd like more information before I start disassembly. Any information on what causes such a fault?
Two things happened to the computer recently that may or may not have anything to do with it - I upgraded the hard drive to a seagate perpindicular 80gb drive which might be mucking about with the internal temperature, and I slipped on discarded food in the subway and dropped my laptop bag hard on its corner. It's pretty well padded and it woke from sleep just fine, but that might have something to do with it as my problems started soon after. Apart from normal usage, I haven't mucked about with it much since, and a full drive wipe and reinstall hasn't solved the problem.
Any advice would be greatly appreciated.

update:
I've also noticed that squeezing the case to the left of the trackpad immediately causes the freezing problem listed about. bizarre.
Still. suggestions, anyone?

Similar Messages

  • XFI "no supported hardware" problem possible solut

    I purchased my xfi about 4 months ago & has worked flawlessly until 2 days ago. Kept giving me the dreaded "no supported hardware" error along with BSOD's, etc... . Tried all the possible solutions in the FAQ, updated bios, changed, diff pci slot, reinst xp,?on & on...no luck. Was about to go return the card when I stumbled on this link selling the card:?http://www.scan.co.uk/Products/Produ...oductID=42270II noticed this at the botom of the ad:Please note: On some systems it is advisable to connect the XFi Card to a Floppy Dri've Power Connector in order to give maximum performance, this is done using the 4 pins on the top edge of the card. As this is an OEM card it does not come with a cable for this but most power supplies are fitted with a spare floppy power connector.
    So figuring i had nothing to lose i plugged it in & lo & behold it all works perfectly again. I found nowhere in manual or help about plugging this in but I thought sharing this might help someone. Maybe it will fry my card eventually but it seems to have solved my problem for now. I suspect that maybe my pci bus isnt providing enough voltage for the card now but everythig seems fine. Oh, here is my general specs:?Gigabyte Socket 939 AGP Motherboard, Athlon64 3500+ CPU, Nvidia 6800GT AGP, 550W Power Supply

    I purchased my xfi about 4 months ago & has worked flawlessly until 2 days ago. Kept giving me the dreaded "no supported hardware" error along with BSOD's, etc... . Tried all the possible solutions in the FAQ, updated bios, changed, diff pci slot, reinst xp,?on & on...no luck. Was about to go return the card when I stumbled on this link selling the card:?http://www.scan.co.uk/Products/Produ...oductID=42270II noticed this at the botom of the ad:Please note: On some systems it is advisable to connect the XFi Card to a Floppy Dri've Power Connector in order to give maximum performance, this is done using the 4 pins on the top edge of the card. As this is an OEM card it does not come with a cable for this but most power supplies are fitted with a spare floppy power connector.
    So figuring i had nothing to lose i plugged it in & lo & behold it all works perfectly again. I found nowhere in manual or help about plugging this in but I thought sharing this might help someone. Maybe it will fry my card eventually but it seems to have solved my problem for now. I suspect that maybe my pci bus isnt providing enough voltage for the card now but everythig seems fine. Oh, here is my general specs:?Gigabyte Socket 939 AGP Motherboard, Athlon64 3500+ CPU, Nvidia 6800GT AGP, 550W Power Supply

  • 4800 SE strange hardware problem...

    Hi, thanks in advance and sorry for my poor english. This is my problem: my computer suddenly shutted down and now the motherboard doesn't seem to recognize the graphic card (MSI TI4800SE). The strange thing is that i've tried plugging the card in some different  new pc's and it works perfectly but in many other pc's it doesn't allow to start the computer,:bonk:seems to might be a compatibility protocol error from the card hardware?¿?¿? I bought it for less than two years ago and it doesn't show physical damages.
    I also tried to plug other video card in my system and no problems have encountered.
    I'd like to know if someone more have the same problem with this msi model or if could help me in this case.....

    thanks very much for your reply. I will answer your question: the systems where i tested the card are running cards of the same and different calibre that my computer. I didn't pay attention if the motherboards were different, and i think that it may be probably a compatibility error to some motherboards. I have an Asus P4S8X.
    By the way, one of the motherboards where i plugged the card to tested it were a new MSI and didn't work too.
    I know that all seems strange, but i need a cheap solution... i paid 240€ for the card and i can't believe this.

  • 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.

  • Strange connection problems -- software or hardware?

    I've been experiencing some strange connectivity problems of late, and am wondering if it's a software or hardware issue. I'm running OS-X 10.4.11, and have noticed web-associated "drop-outs" occurring. When I'm browsing, any of the following will happen:
    1. the pages will periodically stop loading, or will take forever to load a few final images.
    2. the page will load with a different format (completely unformatted, like a throwback to Mosaic!).
    3. the page won't load at all, and will instead give me either a "DNS error" message, or will default to my ISP's "We couldn't resolve your page" message.
    4. Nothing out of the ordinary happens.
    Throughout this process, the connection strength is 100%.
    It seems this happens with both Firefox and Safari. Is this an issue with driver software, or is my Airport Card giving out? My computer is about 3 years old.

    I have been having intermittent connection problems on several computers over many years now. We have 12 eMacs, all purchased within a few months of each other, all with 10.4.11. Some computers have almost perfect internet connection, but some are constantly losing connection. If the user just waits a few minutes, the network just comes back or if they open system preferences and renew the DHCP lease it comes back as well. We have tried replacing cables, reloading the operating system, repairing permissions, reseting safari... We are all connecting through ethernet cables through wall jacks then to a switch that is connected to our router. Our DSL provider claims it can't be wiring or a problem on their end or they would see it and we would all have problems. I am not super computer literate... Any suggestions for what I should check on the 4 or so computers that are having lots of connection problems?
    Thanks for any words of wisdom!!!

  • 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.

  • Extremely strange hardware(?) problem

    I have had this Powerbook G4 1.33GHz for 2 years and until now I never had any problems. A couple weeks ago the system just ground to a halt. I had to restart manually. I have had to do this before, only this time, the system gave me a big NO symbol on startup. I tried restarting several more times with the same results. Finally I booted off from the Tiger DVD and uh for a while it didn't detect the startup hard disk (and when it did, it was running very slowly).
    It was going so slow that the disk utility couldn't run, so I just shut it off and left it for a while. When I tried again, it booted up and loaded the OS just fine. I ran the disk utility and it claimed nothing was wrong.
    This problem has been persisting in the following form:
    For a long period of use, the computer will be fine. As it begins to reach higher temperatures (130 degrees F or so according to my sensor utilities) it starts to stall on very mundane tasks like typing. The stall is just the display of the animated pinwheel and apps stop responding. These stalls appear to coincide with disk accesses (I have been monitoring my Activity Monitor).
    I seem to be able circumvent a slowdown/stall by lifting or tilting the computer at funny angles or jostling it a little. This is what makes me think it's some kind of hardware problem.
    I tried resetting PRAM/NVRAM, the PMU, everything. I don't know what else to try short of reinstalling the OS (which I hear is a bad idea if you have the most recent updates, which I do). Are there any utilities I can get to monitor my fans or my hard disk? Is there any way to diagnose this problem short of taking the computer in and being charged a lot of money?
    Other background:
    I don't know if this is pertinent, but before this started happening, I had trouble with my power cord being frayed and stopping working. I replaced it with a 65W since that is apparently what my model is supposed to use--however I bought it used and it came with the 45W cord. Could the new cord be having some bad effect? I'd used other people's 65W cords before with no problems.
    Powerbook G4   Mac OS X (10.4.8)   1.25 GB RAM, 50 GB HD

    I have a friend who has a similar (slightly later)
    Powerbook. He has the 1.5GHz and I have the 1.33GHz.
    Do you think these have a close enough similarity?
    Try it and see, as it will run or not run.
    As other discussion noted, you want to keep roughly 10% of your hard drive empty, for system files. Erasing the disk and reinstalling OS X really is, however, a last resort. As Joeuu mentioned, you can try freeing up some space to see if that helps. If your system isn't on 24x7, there's a chance some of the Apple scripts which do log maintenance may not have run. If you download MacJanitor or OnyX, both can run the scripts for you, which can free up a little disk space if they haven't been run for awhile. MacJanitor is at http://personalpages.tds.net/~brian_hill/macjanitor.html and OnyX is at http://www.titanium.free.fr/pgs/english.html . OnyX does much more than MacJanitor, however, they both will run the daily/weekly/monthly scripts for you.
    I'm not sure I'd agree it's not a hardware problem just yet. If you can run the Apple hardware test, or TechTools, and it comes up clean, with no issues, then you might go down a different path.

  • Strange shutdown problem

    Hi,
    Last night, I had a strange shutdown problem on my iMac G5 (revB, 20", 2.0 Gig), with 1 Gig RAM, running 10.4.4 with all updates. I had had the computer on most of the day, using it off and on. I shut it down, and left the room. When I came back about an hour later, the fans were running (not rapidly, just at the normal speed they run when the computer is running), but the screen was blank, and the "sleep" light was not on. The computer wouldn't respond to any moving the mouse or to keyboard input. I finally shut it down by holding the power button until the fans shut down. Upon restart, everything was normal, and after using it for a few minutes, I was able to shut it down normally. Has anyone else seen this sort of behavior, and is it normal ? Or am I about to have more problems.
    Thanks in advance,
    Dave Fritzinger
    Honolulu, HI

    Hi Dave,
    By the sound of it your computer has "hung" during the shutdown process, but at a point in the process where the system's temperature control mechanisms were still operating (otherwise the fans would be running flat out). My guess in this case is that it was probably actually a finder crash.
    Various things can prevent proper shutdown. Often USB or FW devices are to blame. USB adsl modems , some scanners and hubs and the occasional printer driver seem to be common causes. Software can be responsible too, though - background virus or drive checkers are probably the most common, but far from the only possible causes ( I seem to remember "SpringCleaning" causing this problem when people moved to Tiger 10.4.2 for example) .
    New software or hardware are therefore the first things to look for.
    If you haven't installed anything completely new then one possibility may be that something you are using is not compatible with the latest OS update, and needs an upgrade to a driver. Its also possible that this is a "one off" glitch caused by a temporary problem , but if it happens again I'd be taking careful note of anything that you were using in the previous session.
    You might also want to use the Console (in Utilities folder) to look at your system and crash logs.
    Cheers
    Rod

  • Strange nasty problem using a caldigit S2VR

    Hi Guys,
    Ok, this is a really strange problem, and I have been tearing my hair out for a couple of days. I have a powermac g5 dual 2Ghz. I got the sata raid from caldigit with a pcix sata card. i installed everything - the sata card in slot 4. I can log into their utility create the raid, then format the drives in disc utility no problem. As soon as I try to transfer some large files (3.2gb) though, after between 100mb and 2bg of transfer its suddenly stops. The drive stops responding and I can't connect to it via the util. After a few minutes, the I get an ejection warning from finder. Does anyone have any ideas? We have ruled out any hardware issues with the drive itself, but it seems to me it's more the pci card issue. Any know problems with pci on G5?
    thanks for your time
    ursula

    The drive problem I was referring to involved disks connected to the Mac SATA bus not through a card so that shouldn't have anything to do with it. Exactly which model of dual 2.0 do you have. If I remember correctly there are a few different flavors. Mine is a rev A dual 2.0 and I don't have any PCI-x problems. I'm not aware of wide spread problems with PCI. I wiould run the Apple Hardware Test to try to rule out the possibility of a hardware problem on your Mac itself. Then I would try all of the usual stuff, reset PMU, reset nvram, repair permissions, erase or repair the disk with Disk Utility. I would try reseating the card. You could even go so far as to reinstall your system. But before I went that far I'd try to get Caldigit to send you another card.
    Another thought....you said the card is in slot 4? Don't G5's have three PCI slots? Or is the slot for the video card counted as slot one? Not in front of a Mac right now so i can't look. Have you tried moving the card to a different slot?

  • Strange wifi problem on a brand-new MacBook Pro

    Hey there, I'm new here. Desperation has got the better of me, and I hope I can get some advice.
    So, last sunday I bought a brand new 13" MacBookPro with 2.8g i7 processor and 10.7.2 OS (I can't update to 10.7.4 because System Update tells me the download has been tampered with or corrupted after I waited 2 hours for it to finish, but I'm trying a direct download from the website). Here's the exact product: http://www.amazon.com/Apple-MacBook-MD314LL-13-3-Inch-VERSION/dp/B005CWIZ4O/ref= sr_1_5?ie=UTF8&qid=1340301247&sr=8-5&keywords=macbook+pro+13
    Everything is all perfect except for a strange wifi problem. Note that the wifi does not turn-on or off, it doesn't disconnect after 'sleep', it doesn't get less speed, it doesn't constantly leave a preferred connection (once I chose my home wifi it always connects to it no problem). The wifi bar is always full. What is wrong is that the internet is kinda 'glitchy'. The best metaphor I can think of is that it's like a car that has to be pushed down the road before the engine can start. Please, bear with me because this is kinda hard to explain and I'm not good at tech lingos.
    One of the symptoms is browsing can get really slow and inconsistent, almost as if the wifi gets turned off in the middle of browsing. For example: if I look something up on Google and then open 5 new tabs, probably only 2 or 3 of those tabs will eventually load while the other two will not get past the long 'http:.......google.....etc etc' address and will eventually show one of those 'error loading page because there's no Internet connection' notice. This happens a lot. Sometimes I have to refresh/retry loading a page a couple of times before it finally loads, then usually everything will get back to normal and I will be able to open multiple tabs with no problem, but in a couple of minutes I would try to open another site and the problem will start again.
    So I tried to see how it does with downloading using iGetter. Fortunately I also have a Macbook (white-plastic casing one) and my brother has an old 2006 MacbookPro so I can compare. With those two older Apples iGetter starts receiving data in less than 8 seconds after I click Start, while my brand-new Macbook Pro can take up to 15-20 seconds, sometimes it doesn't even start at all and I have to re-click the start button. But once the download actually starts (on my new MacBook Pro), it downloads like normal, it doesn't stop and the speed is also as good as I can get. Strange huh? Hence, like a car that has to be pushed before the engine starts.
    I also tried 'speed testing' from a website with all 3 laptops. On my old MacBook and my brother's MacBook pro, once I click 'begin test' it takes only a couple of seconds of 'ping' before the download/upload speed measurements start, but with my new MacBook Pro (just like with iGetter) it takes up to almost a minute before the measurements start, sometimes it won't start at all and I have to re-start the test.
    Well, thanks for reading. And hope you can help me shed some light into this. Because it is really preventing me from really enjoying my new MacBook Pro. And if this is most likely a hardware problem, I'd better get back to the store and try to get it replace or something while it's only been 5 days. *cheers*

    Hey guys.. Thanks for the replies. Unfortunately, I bought the MacBook in Indonesia where there are no such thing as an AppleCare. The only option is to leave the Apple product to one of the 'Authorized Apple care centre' and have whoever do whatever to it without guarantee of success. As for returning it and getting a brand new one, I also don't know if there is such a deal here, but that's actually a good idea, will try to go to the store tomorrow. Although, I'm worried that the problem might be with OSX Lion or something and getting a new one won't help.
    mark75090, I've tried resetting the router when I first noticed te problem, didn't work though. I've checked my new MacBook's wi-fi (option+click wifi bar) and it says 'PHY Mode: 802.11g', so does my MacBook and the old MacBook Pro. I don't know what those mean though, and I don't know whether or not my router is an N., can you tell me more please.. I have tried with the other two turned off, and only the new MacBook using the wi-fi but the problem persists. I have also tried connecting directly to the router, but as I described, the problem is too subtle for me to notice the difference.
    Also, if I create a brand new Wi-Fi connection in network preferences and connect to my router through the new Wi-Fi profile, the problem seems to be gone for an hour or so, then it always comes back though. I have also just finally installed 10.7.4, but it doesn't help either.

  • 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.

  • Yoga 2 Pro Webcam suddenly stopped working....(not a hardware problem!)

    Hi everyone,
    I've had the yoga 2 pro for about a year now - took a little bit of fiddling to get it working just right (clean OEM win 8.1 install and installing drivers in the right order etc) but I had it working just perfect then....
    About a week ago the webcam stopped working during a skype call. I tried reinstalling the drivers etc and messed around for 2 days trying to get it working again. The LED light comes on when it's engaged and it says it's present and working in device manager but I get no picture on skype or any other program.
    I reinstalled windows 8.1 from scratch in the hope that this would solve it but same issue.
    So I assumed it was a hardware fault and thought stuff it!
    But then last night I installed Windows 7 32 bit on VMWare to run some of the older 32 bit programs and the webcam works perfectly within this virtual OS!! So it doesn't seem to be a hardware problem after all.
    I've tried everything - installing the bison & Liteon drivers from the Lenovo website, installing the generic win 8 drivers etc but NOTHING WORKS!!
    Can  you help? I just want to get this thing working again!!
    THANKS!

    Unfortunately I've reinstalled the driver after uninstalling it from the device manager 10 times. I also formatted and reinstalled, but that didn't fix anything.
    The camera works for the camera app + the webcam test online. I've tried rollback on the drivers, and installing earlier versions of skype with no luck.
    Very strange, all it does is show the loading sign, and never loads. 
    This is the desktop version of skype btw. I'm going to try it with the non-dekstop version tonight and see if it works. 
    EDIT: Is there any other camera source besides 'Lenovo EasyCamera'? Their are two drivers on the drivers page, which one is recommended?

Maybe you are looking for