Pc reiniciando sozinho

[mmlx 0]

Olá

Meu pc esta reiniciando a todo momento q paro de mexer nele, é so nao mexer no mouse ou no teclado q ele reinicia, antes era a qualquer momento

 

mesmo depois de limpar as memorias, a proposito ja passei o memtest86 e nao deu erro nenhum

 

desconfio q seja da fonte, pois é uma fonte generica com total maxima 220w, mas gostaria de confirmaçao antes de gastar qq coisa, pq o pc ja esta velho e pretendo investir em um novo no final do ano, a fonte tb faz muito barulho ao ligar, barulho do cooler, q conforme entra no windows carrega os programas o barulho diminui...

 

de qq forma aki esta a configuraçao do meu pc e os erros coletados pelo whocrashed, me ajudem por favor.....

 

 

Tipo de Computador ACPI Multiprocessor PC

Sistema operacional Microsoft Windows XP Professional

Service Pack do Sistema Operacional Service Pack 3

 

Tipo de processador Intel Pentium 4, 3000 MHz (15 x 200)

Nome da Placa Mãe MSI MS-7104

Chipset da Placa Mãe VIA CN700 / P4M800 CE / P4M800 Pro / VN800

Memória do Sistema 1014 MB (PC3200 DDR SDRAM)

DIMM1: Kingston K 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)

DIMM2: Kingston K 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)

Tipo de BIOS Award (09/19/06)

 

Adaptador gráfico VIA/S3G UniChrome Pro IGP (8 MB)

Acelerador 3D VIA/S3G UniChrome Pro

Monitor Proview 772K [17" CRT] (610201315)

 

Adaptador de som Realtek ALC655 @ VIA AC'97 Enhanced Audio Controller

 

Controladora IDE VIA Bus Master IDE Controller - 0571

Controladora "Storage" VIA SATA RAID Controller

Disco rígido ST340824A (40 GB, 7200 RPM, Ultra-ATA/100)

Disco rígido ST380011A (80 GB, 7200 RPM, Ultra-ATA/100)

Disco rígido ST3802110A (80 GB, 7200 RPM, Ultra-ATA/100)

Status dos discos rígidos SMART OK

 

 

WhoCrashed

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Fri 26/8/2011 06:05:20 GMT your computer crashed

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

uptime: 00:46:34

This was probably caused by the following module: win32k.sys (win32k+0xEC01)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x1204, 0xFFFFFFFFF4A80BA8, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\win32k.sys

product: Sistema operacional Microsoft® Windows®

company: Microsoft Corporation

description: Driver Win32 multiusuário

Bug check description: This indicates that a kernel-mode program 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.

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 Fri 26/8/2011 06:05:20 GMT your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

uptime: 00:46:34

This was probably caused by the following module: win32k.sys (win32k+0x610BA)

Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x1204, 0xFFFFFFFFF4A80BA8, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\win32k.sys

product: Sistema operacional Microsoft® Windows®

company: Microsoft Corporation

description: Driver Win32 multiusuário

Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error

 

handler did not catch.

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 Thu 25/8/2011 19:07:27 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082511-06.dmp

uptime: 00:06:16

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

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF804E02A8, 0xFFFFFFFFF4C20B8C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

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 a kernel-mode program 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.

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

 

identified at this time.

 

 

On Thu 25/8/2011 18:56:03 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082511-05.dmp

uptime: 00:06:17

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

Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

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 a kernel-mode driver attempted to access pageable memory at a process IRQL

 

that was too high.

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

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

 

identified at this time.

 

 

On Thu 25/8/2011 18:44:38 GMT your computer crashed

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

uptime: 00:10:05

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

Bugcheck code: 0x50 (0xFFFFFFFFFFFFD108, 0x1, 0xFFFFFFFF86260085, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

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 invalid system memory has been referenced.

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

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

 

identified at this time.

 

 

On Thu 25/8/2011 18:31:35 GMT your computer crashed

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

uptime: 00:16:19

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

Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF80042000, 0x0, 0x0)

Error: UNEXPECTED_KERNEL_MODE_TRAP_M

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 a trap was generated by the Intel CPU and the kernel failed to catch this trap.

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 which cannot be

 

identified at this time.

 

 

On Thu 25/8/2011 17:10:06 GMT your computer crashed

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

uptime: 00:11:15

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

Bugcheck code: 0xA (0x608632FB, 0xFF, 0x0, 0xFFFFFFFF80705537)

Error: IRQL_NOT_LESS_OR_EQUAL

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 Microsoft Windows or a kernel-mode driver accessed paged memory at

 

DISPATCH_LEVEL or above.

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

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

 

identified at this time.

 

 

On Thu 25/8/2011 11:20:10 GMT your computer crashed

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

uptime: 00:06:18

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

Bugcheck code: 0xA (0x54, 0x1C, 0x1, 0xFFFFFFFF804E1642)

Error: IRQL_NOT_LESS_OR_EQUAL

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 Microsoft Windows or a kernel-mode driver accessed paged memory at

 

DISPATCH_LEVEL or above.

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

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

 

identified at this time.

 

 

On Wed 24/8/2011 13:57:56 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082411-10.dmp

uptime: 00:06:12

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

Bugcheck code: 0xD1 (0x6, 0x5, 0x0, 0xFFFFFFFFF75507E1)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

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 a kernel-mode driver attempted to access pageable memory at a process IRQL

 

that was too high.

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

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

 

identified at this time.

 

 

On Wed 24/8/2011 13:46:36 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082411-09.dmp

uptime: 00:06:17

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

Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF80042000, 0x0, 0x0)

Error: UNEXPECTED_KERNEL_MODE_TRAP_M

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 a trap was generated by the Intel CPU and the kernel failed to catch this trap.

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 which cannot be

 

identified at this time.

 

 

On Wed 24/8/2011 13:24:08 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082411-08.dmp

uptime: 02:06:47

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

Bugcheck code: 0xA (0xFFFFFFFFC000D380, 0x2, 0x0, 0xFFFFFFFF804E8C53)

Error: IRQL_NOT_LESS_OR_EQUAL

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 Microsoft Windows or a kernel-mode driver accessed paged memory at

 

DISPATCH_LEVEL or above.

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

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

 

identified at this time.

 

 

On Wed 24/8/2011 11:17:01 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082411-07.dmp

uptime: 00:11:08

This was probably caused by the following module: alcxwdm.sys (ALCXWDM+0xA1C62)

Bugcheck code: 0x100000D1 (0xBDE1398, 0x2, 0x0, 0xFFFFFFFFF5CCF643)

Error: CUSTOM_ERROR

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

product: Windows ® WDM driver for Realtek AC'97 Audio(HRTF data Copyright 1994 by MIT Media Lab)

company: Realtek Semiconductor Corp.

description: Realtek AC'97 Audio Driver (WDM)

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: alcxwdm.sys (Realtek AC'97 Audio Driver (WDM), Realtek Semiconductor Corp.).

Google query: alcxwdm.sys Realtek Semiconductor Corp. CUSTOM_ERROR

 

 

 

 

On Wed 24/8/2011 11:05:35 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082411-06.dmp

uptime: 00:06:12

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

Bugcheck code: 0x100000D1 (0x56D96380, 0x2, 0x0, 0x56D96380)

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.

 

 

On Wed 24/8/2011 10:59:04 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini082411-05.dmp

uptime: 00:06:10

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

Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF80042000, 0x0, 0x0)

Error: UNEXPECTED_KERNEL_MODE_TRAP_M

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: TCP/IP Protocol Driver

Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.

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 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 Wed 24/8/2011 10:52:35 GMT your computer crashed

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

uptime: 00:06:15

This was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0)

Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFF4C2059C, 0xFFFFFFFFF4C20298, 0xFFFFFFFFF7460127)

Error: NTFS_FILE_SYSTEM

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

Bug check description: This indicates a problem occurred in the NTFS file system.

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.

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

83 crash dumps have been found and analyzed. Only 15 are included in this report. 7 third party drivers have been

 

identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these

 

drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

 

epfwndis.sys (ESET Personal Firewall NDIS filter, ESET)

 

eamon.sys (Amon monitor, ESET)

 

alcxwdm.sys (Realtek AC'97 Audio Driver (WDM), Realtek Semiconductor Corp.)

 

unknown

 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the

 

errors that have been reported for these drivers and include the brand and model name of your computer as well in the

 

query. This often yields interesting results from discussions from users who have been experiencing similar problems.

 

 

Read the topic general suggestions for troubleshooting system crashes for more information.

 

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing

 

your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products

 

that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a

 

piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the

 

model name and brand of your computer may help you investigate this further.

[Edvan 30]

Seja bem vindo ao Fórum Imasters mmlx!

 

1º Vamos verificar a temperatura do processador e as voltagens da fonte.

 

vamos lá.

 

Conferindo a temperatura do processador e as voltagens da fonte:

 

A forma mais simples de conferir a temperatura do processador e as voltagens da fonte é através do setup da placa mãe ou usando o programa AIDA64, vejamos como acessá-lo.

 

Link:

http://forum.imasters.com.br/topic/439373-tutorial-verificando-as-temperaturas-de-seu-computador/

 

Conferindo temperatura e voltagens pelo setup:.

 

Ao ligar a máquina fique pressionando a tecla DEL*, a tela que aparece é o setup do micro, procure pela opção Hardware Monitor ( ou semelhante ), lá aparecerá a temperatura do processador ( CPU ) e as voltagens da fonte ( +3,3V, +5V, +12V ).

 

* = Na maioria das placas mães se acessa o setup pressionando a tecla DEL, caso a sua seja diferente, ao ligar o micro preste atenção se não aparece nenhuma instrução, ou verifique no manual.

 

Sabendo-se a temperatura do processador, confira no site abaixo se a temperatura está normal ou se o processador está tendo um superaquecimento, consequentemente causando reinicializações e travamentos.

 

http://mysite.verizon.net/pchardwarelinks/

 

Existe um tolerância para a variação nas voltagens da fonte, essa tolerância é de 5%, sendo assim são toleradas as seguintes variações nas voltagens:

 

+3,3V

 

Mínimo: +3,14V

Máximo: +3,47

 

+5V

 

Mínimo: +4,75V

Máximo: +5.25V

 

+12V

 

Mínimo: +11,4V

Máximo: +12,6V

 

Se qualquer uma das linhas ( +3,3V, +5V, +12V ) variar mais do que 5%, recomendo a troca da fonte o mais rápido possível, de preferência por uma de potência real. Uma fonte que distribui de forma incorreta as voltagens, além de causar travamentos e reinicializações, podem causar danos permanentes aos outros periféricos da máquina.

 

Link:

http://forum.imasters.com.br/topic/378654-conferindo-a-temperatura-do-processador-e-as-voltagens-da-fonte/