Windows XP reiniciando sozinho

belota · 1 de setembro de 2011

Já faz umas 3 semanas que quando uso meu pc ele reinicia de repente, e daí fica reiniciando sem parar antes de ligar ... Quanto mais tempo fico sem usar, mais tempo ele funciona, mas ele reinicia mesmo assim. Eu pesquisei na internet e tudo, já limpei o "ventilador", mas continua acontecendo ... Agora eu baixei aquele programa "WhoCrashed" e (pelo que eu entendi!) tem 6 problemas acontecendo.

System Information (local)

________________________________________

computer name: USUARIO-6F1E416

windows version: Windows XP Service Pack 3, 5.1, build: 2600

windows dir: C:\WINDOWS

CPU: GenuineIntel Intel® Celeron® CPU 420 @ 1.60GHz Intel586, level: 6

1 logical processors, active mask: 1

RAM: 1064550400 total

VM: 2147352576, free: 2037239808

On Tue 5/7/2011 21:48:47 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini070511-01.dmp

This was probably caused by the following module: hpzid412.sys (HPZid412+0xA328)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFF7711328, 0xFFFFFFFFA9600CA0, 0xFFFFFFFFA960099C)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\drivers\hpzid412.sys

product: HP Dot4 Windows 2000

company: HP

description: IEEE-1284.4-1999 Driver (Windows 2000)

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

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: hpzid412.sys (IEEE-1284.4-1999 Driver (Windows 2000), HP).

Google query: hpzid412.sys HP SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Mon 9/5/2011 23:41:17 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini051011-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5C80E)

Bugcheck code: 0x4E (0x8F, 0x37041, 0x37001, 0x0)

Error: PFN_LIST_CORRUPT

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Sistema operacional Microsoft® Windows®

company: Microsoft Corporation

description: Núcleo e sistema do NT

Bug check description: This indicates that the page frame number (PFN) list is corrupted.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 9/5/2011 23:32:21 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini050911-04.dmp

This was probably caused by the following module: sthda.sys (sthda+0x8D87)

Bugcheck code: 0x100000D1 (0x3E0C8D08, 0x2, 0x0, 0xFFFFFFFFAA672D87)

Error: CUSTOM_ERROR

file path: C:\WINDOWS\system32\drivers\sthda.sys

product: IDT Audio

company: IDT, Inc.

description: NDRC

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: sthda.sys (NDRC, IDT, Inc.).

Google query: sthda.sys IDT, Inc. CUSTOM_ERROR

On Mon 9/5/2011 22:57:44 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini050911-03.dmp

This was probably caused by the following module: usbport.sys (USBPORT+0x5507)

Bugcheck code: 0x100000D1 (0x4E1C108, 0x2, 0x0, 0xFFFFFFFFF6AE3507)

Error: CUSTOM_ERROR

file path: C:\WINDOWS\system32\drivers\usbport.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: USB 1.1 & 2.0 Port Driver

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Mon 9/5/2011 21:12:38 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini050911-02.dmp

This was probably caused by the following module: hal.dll (hal+0x4A7F)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8601F4F8, 0xFFFFFFFF8601F518, 0xA04F400)

Error: BAD_POOL_HEADER

file path: C:\WINDOWS\system32\hal.dll

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Hardware Abstraction Layer DLL

Bug check description: This indicates that a pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Mon 9/5/2011 21:05:19 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini050911-01.dmp

This was probably caused by the following module: tcpip.sys (tcpip+0x637)

Bugcheck code: 0x100000D1 (0x454C494A, 0x2, 0x1, 0xFFFFFFFFAA592637)

Error: CUSTOM_ERROR

file path: C:\WINDOWS\system32\drivers\tcpip.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: TCP/IP Protocol Driver

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

e agora eu não sei o que fazer ... se alguém puder me ajudar, agradeço