笔记本老是自动重启！我该如何办？

wolfgang2001

我的破HP Pavilion tx2500才买来不到5个月又出问题了。

刚买回来，它就有时候没法自动关机。上星期突然黑屏。根本无法打开电脑。没办法，我只好重装了系统。可是没几个小时，电脑总是无缘无故地自动重启。重启后，还会弹出个对话框，告我电脑有问题，见附件

我想关机，有时它只能重新启动，我只好再关一次机。

我下载了很多附件，可还是不管用。

请高手指点，先谢过

Aberlin

纯粹帮顶，这个看高手了

momo_zhang

既然是新买的，赶快维修。。。既然都重新安装过系统，但是毛病依然在，就应该是硬件问题。。。

楼主犯错误了，既然在刚买的时候，就发现了问题，当时就应该退货。。。。

现在已经5个多月了，只能维修了。。。

Nimm2

vista蓝屏还真没怎么见到过，既然官方的不少附件都无法修复，感觉非常可能是硬件问题，赶快送修吧

西瓜啊西瓜

Vielleicht Datenbus wackel kontakt.

wolfgang2001

啊！看来这个破HP真是凶多吉少了。先去维修一下。

谢谢各位。我刚开始还以为是小问题。可现在。。。啥也不说了，眼泪哗哗地奔向维修部。。。

Trois

你点一下那个nach Lösung finden，看看有没有什么结果？说不定是哪个硬件需要升级驱动呢

Trois

重启的话也可能是哪个部件过热了昨天我的电脑还一直自己关机，刚开机就自己断电了
气得我给拆了～发现是cpu的风扇那4个固定的柱子有两个松掉了，固定不稳

blurryblue

90%是软件（驱动）问题，把那3个文件发上来看看。

blurryblue

用WinDbg分析dump文件，可以找到crash的起因。

在这里可以简单学习一下。
http://www.networkworld.com/news/2005/041105-windows-crash.html

以下是节选的分析及处理

Finding out what went wrong is often a simpleprocess, but it isn't always so. At least 50% of the time (often 70%),the debugger makes the reason for a crash obvious. But sometimes theinformation it provides is misleading or insufficient. What do you dothen?


Inconsistent answers

If you have recurring crashes but no clear or consistent reason, it may be a memory problem. Download the free test tool,   Memtest86. This simple diagnostic tool is quick and works great.
Many people discount the possibility of a memory problem, because they account for such a small percentage of system crashes.   However, they are often the cause that keeps you guessing the longest.


The operating system is the culprit

Not likely! As surprising as it may seem, theoperating system is rarely at fault. If ntoskrnl.exe (Windows core) orwin32.sys (the driver that is most responsible for the "GUI" layer onWindows) is named as the culprit, and they often are, don't be tooquick to accept it. It is far more likely that some errant third-partydevice driver called upon a Windows component to perform an operationand passed a bad instruction, such as telling it to write tonon-existent memory. So, while the operating system certainly can err,exhaust all other possibilities before you call Microsoft! The samegoes for debugging Unix, Linux, and NetWare.


Wrong driver named

Often you will see an antivirus driver named as the cause. For instance, after using !analyze –v, the debugger reports a driver   for your antivirus program at the line "IMAGE_NAME". This may well be the case, but bear in mind that such a driver can be   named more often than it is guilty. Here's why: For antivirus code to work it must watch all file openings and closings. To   accomplish this, the code sits at a low layer in the operating system and is constantly working. In fact, it is so busy it   will often be on the stack of function calls that was active when the crash occurred, even if it did not cause it. Because   any third-party driver on that stack immediately becomes suspect, it will often get named. From a mathematical standpoint   it is easy to see how it will so often be on the stack whether it actually caused a problem or not.


Little or no vendor information

Not all vendors include needed information (not even their name!). If you use the lmv command and turn up nothing, look at   the subdirectories on the image path (if there is one). Often one of them will be the vendor name or a contraction of it.   Another option is to search Google. Type in the driver name and/or folder name. You'll probably find the vendor as well as   others who have posted information regarding the driver.