Since receiving my Win 8 HP AMD E1-1200 APU 64 Bit back in September, I began to suddenly get the famous and VERY irritating error. I love to push any computer I use to it's limits and this computer not being the exception, I ran different OS's. I ran various flavors of Linux (Mint, Ubuntu, Manjaro, Opensuse, Scientific Linux among a bunch more) usually off USB memory sticks and on a few occasions, dvd. I noticed that every time I ran Linux and then turned off and on my computer, I would get the irritating beeps and sudden lockups. The machine (sometimes) would reset itself, after Windows gave a vague and hardly useful reason why this happened. Since my computer is an all-in-one, I sometimes move it from room to room, like I would a laptop. After I kept getting these error messages, I thought perhaps (as the error message states) the cable was either loose, defective, or that the hard drive was ready to die. I re-installed Windows more times than I care to remember, spending (wasting actually) so much time on re-installation, only to find the problem creep back up. The most confusing and irritating part of the mystery was that I never received this error under ANY Linux flavor I used.
I kept on using my machine for a few days at a time until the nagging and frankly irritating beeps kept announcing the same problem had come back to haunt me. I tried updating my driver through Windows Update with no success-always told me that the driver was the latest. Then I remembered something that I read a while back-if you are having a problem with either hardware or drivers, check the manufacture to see if they have released an update. So I went to realtek.com and checked here
http://www.realtek.com/downloads
and on the right side clicked on Realtek PCIe FE Family Controller Series Drivers. I then chose to download both the driver installation and diagnostic software. Please note that the software is downloaded in ZIP format. Also note that it is best to create a restore point BEFORE installing any software at ANY time on your computer(s). This way, if things don't work as they should or any better, you can always restore your computer to it's state before you installed said program(s). I do note that that drivers were updated on 6/3/14 and that leads me to a question. Would Microsoft distribute this update to the driver? If not, why not? Looking at a cause/solution for this error, I see a lot of queries, but no answers from Realtek and/or Microsoft.
In short, maybe Windows users cannot depend on the software or Redmond to update software on Windows that the manufacturer has updated. Realtek deserves a slap on the wrist here as well. The driver issue/problems have been around for years-did they wait all this time to either correct the problems/update the driver? As of this moment, after installing the updated) driver, I have had no more beeps/freezes/resets. I hope this finally ends the problems, once and for all.
It's just amazing and Microsoft should pay VERY close attention to the fact that all of the Linux distros that I have tried, have apparently come with the LATEST drivers or at least the correct drivers. Yes, the driver update was issued last month, but why does Microsoft have this problem and states that the driver is updated and Linux distros that have come out in the last 6 months do not have the same problems, with the SAME hardware?
Hope this helps those that have suffered through the pains of resets, freezes, and cryptic screen message from Win8 that you leave you more confused than enlightened as to what caused the problem in the first place.
Remember - always create a system restore point before adding/removing ANY programs in Windows! Better safe than sorry!
Since receiving my Win 8 HP AMD E1-1200 APU 64 Bit back in September, I began to suddenly get the famous and VERY irritating error. I love to push any computer I use to it's limits and this computer not being the exception, I ran different OS's. I ran various flavors of Linux (Mint, Ubuntu, Manjaro, Opensuse, Scientific Linux among a bunch more) usually off USB memory sticks and on a few occasions, dvd. I noticed that every time I ran Linux and then turned off and on my computer, I would get the irritating beeps and sudden lockups. The machine (sometimes) would reset itself, after Windows gave a vague and hardly useful reason why this happened. Since my computer is an all-in-one, I sometimes move it from room to room, like I would a laptop. After I kept getting these error messages, I thought perhaps (as the error message states) the cable was either loose, defective, or that the hard drive was ready to die. I re-installed Windows more times than I care to remember, spending (wasting actually) so much time on re-installation, only to find the problem creep back up. The most confusing and irritating part of the mystery was that I never received this error under ANY Linux flavor I used.
I kept on using my machine for a few days at a time until the nagging and frankly irritating beeps kept announcing the same problem had come back to haunt me. I tried updating my driver through Windows Update with no success-always told me that the driver was the latest. Then I remembered something that I read a while back-if you are having a problem with either hardware or drivers, check the manufacture to see if they have released an update. So I went to realtek.com and checked here
http://www.realtek.com/downloads
and on the right side clicked on Realtek PCIe FE Family Controller Series Drivers. I then chose to download both the driver installation and diagnostic software. Please note that the software is downloaded in ZIP format. Also note that it is best to create a restore point BEFORE installing any software at ANY time on your computer(s). This way, if things don't work as they should or any better, you can always restore your computer to it's state before you installed said program(s). I do note that that drivers were updated on 6/3/14 and that leads me to a question. Would Microsoft distribute this update to the driver? If not, why not? Looking at a cause/solution for this error, I see a lot of queries, but no answers from Realtek and/or Microsoft.
In short, maybe Windows users cannot depend on the software or Redmond to update software on Windows that the manufacturer has updated. Realtek deserves a slap on the wrist here as well. The driver issue/problems have been around for years-did they wait all this time to either correct the problems/update the driver? As of this moment, after installing the updated) driver, I have had no more beeps/freezes/resets. I hope this finally ends the problems, once and for all.
It's just amazing and Microsoft should pay VERY close attention to the fact that all of the Linux distros that I have tried, have apparently come with the LATEST drivers or at least the correct drivers. Yes, the driver update was issued last month, but why does Microsoft have this problem and states that the driver is updated and Linux distros that have come out in the last 6 months do not have the same problems, with the SAME hardware?
Hope this helps those that have suffered through the pains of resets, freezes, and cryptic screen message from Win8 that you leave you more confused than enlightened as to what caused the problem in the first place.
Remember - always create a system restore point before adding/removing ANY programs in Windows! Better safe than sorry!
การแปล กรุณารอสักครู่..
