Ir ao conteúdo
  • Comunicados

    • Gabriel Torres

      Seja um moderador do Clube do Hardware!   12-02-2016

      Prezados membros do Clube do Hardware, Está aberto o processo de seleção de novos moderadores para diversos setores ou áreas do Clube do Hardware. Os requisitos são:   Pelo menos 500 posts e um ano de cadastro; Boa frequência de participação; Ser respeitoso, cordial e educado com os demais membros; Ter bom nível de português; Ter razoável conhecimento da área em que pretende atuar; Saber trabalhar em equipe (com os moderadores, coordenadores e administradores).   Os interessados deverão enviar uma mensagem privada para o usuário @Equipe Clube do Hardware com o título "Candidato a moderador". A mensagem deverá conter respostas às perguntas abaixo:   Qual o seu nome completo? Qual sua data de nascimento? Qual sua formação/profissão? Já atuou como moderador em algo outro fórum, se sim, qual? De forma sucinta, explique o porquê de querer ser moderador do fórum e conte-nos um pouco sobre você.   OBS: Não se trata de função remunerada. Todos que fazem parte do staff são voluntários.
Entre para seguir isso  
rxc

Não Sei Qual é O Problema

Recommended Posts

Estou montando um athlon 2.0 xp numa placa-mãe asrock k7s8xe R3, com uma placa de video radeon 9200 + um hd 80gb + 256 ddr 333

sendo ao instalar o windows xp durante a instalação ele dá um erro, o windows desliga vem aquela tela azul com a seguinte mensagem:

kernel_data_impage_error

falando pra rever hardware essas coisas já tentei a placa de video e ela tá ok já troquei a memoria e nada já testei com outro hd e a mesmo coisa acontece

já botei um hd cheio com xp instalado mas ao inicar o xp dá um outro erro com essa tela azul falando pra eu ver seo HD está ok

mas ele esta , estou rodando nele agora

não sei mais o que fazer me ajudemmmm

Compartilhar este post


Link para o post
Compartilhar em outros sites

Este CD que você esta usando pra instalar o Windows!

você já instalou ele outras vezes?

Pode ser o CD o seu problema

você configurou tudo certinho no setup?

Compartilhar este post


Link para o post
Compartilhar em outros sites

já tentei com 2 cds sendo q um deles é o meu aonde já instalei em várias máquinas!!

que configuração do setup!?!?!

não mexi nada em setup nem fiz nenhum tipo de jumpeamento na placa mãe

tem algo a ser feito?!!?

Compartilhar este post


Link para o post
Compartilhar em outros sites

Volto a pedir incarecidamente a ajuda de vocês ontem troquei a placa mãe e nada não sei mais o que fazer estou achando q é alguma configuração..mas não sei me ajudem Dêem uma luz por favor!!! :muro:

Compartilhar este post


Link para o post
Compartilhar em outros sites

achei isso aqui na internet mas não entendi direito se puderem ler e me ajudarem valeu!!

No se si te ayuda esto:

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

This Stop message, also known as Stop 0x7A, indicates that the requested page of kernel data from the paging file could not be read into memory.

Interpreting the Message

The four parameters listed in the message are defined in order of appearance as follows:

1.

Lock type that was held (value 1, 2, 3, or Page Table Entry [PTE] address).

2.

I/O status code.

3.

Current process (virtual address for lock type 3, or PTE).

4.

Virtual address that could not be read into memory.

For information about all possible status codes that might be returned, see the file Ntstatus.h of the Windows 2000 Device Driver Kit (DDK). For information about the DDK, see "Additional Resources" at the end of this chapter.

Resolving the Problem

Stop 0x7A is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

SCSI problems. If the I/O status is C0000185 and the paging file is on a SCSI disk, check the disk cabling and SCSI termination for problems.

Viruses. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. Any Windows 2000 file system can be infected by viruses.

Bad block. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r. For more information about the Recovery Console, see chapter "Repair, Recovery, and Restore" in this book.

Warning If your system partition is formatted with the FAT16 file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from a MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks.

Failing RAM. Another common cause of this error message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.

Also, check that all the adapter cards in the computer, including memory modules, are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Be sure to wipe the cleaned contacts off, removing all cleaning debris, before reinstalling the adapter card into the computer. If compressed air is available, use it to clear out the adapter card slot.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Microsoft periodically releases a package of product improvements and problem resolutions for Windows 2000 called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows 2000 dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed.

Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post-Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows 2000 dialog box. For more information about Service Packs and hotfixes, see "Additional Resources" at the end of this chapter.

Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.

For more troubleshooting information about the 0x7A Stop message, refer to the Microsoft Knowledge Base link , using the keywords winnt and 0x0000007A. For information about this resource, see "Additional Resources" at the end of this chapter.

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

by RID501

Compartilhar este post


Link para o post
Compartilhar em outros sites

tente ver a freqüência do processador, qual a memoria que você. utiliza.

Compartilhar este post


Link para o post
Compartilhar em outros sites

já testei a o leitor sim!! e NADA!!!!

a freqüência do preocessador tá correta já testei!!!!

a memória jha troquei mas ppor uma de mesmo marca!!

pode ser a marca da memória...é uma dessas genéricas!!!

será q se eu pegar uma memória de outra marca pode funcionar??

eu instalei o 2000 e 98 nele e foi liso ..o problema no aparece na instalação do xp mesmo!!! =/

Compartilhar este post


Link para o post
Compartilhar em outros sites

O win Xp é realmente bem "sensivel" à memoria ram , qualquer problema ele "detecta" facilmente

teste com uma memoria de melhor qualidade, como uma samsung, é barata e quebra um galhao

teh mais! :-BEER:-BEER:-BEER

Compartilhar este post


Link para o post
Compartilhar em outros sites
Guest Dirceu Ferri

você tem o manual da placa?

Compartilhar este post


Link para o post
Compartilhar em outros sites

tenho sim.... pqz?

eu pensei nessa hipótese de trocar a memória por uma de outra marca pra ver no q dá!!!

vou tentar isso valeu

Compartilhar este post


Link para o post
Compartilhar em outros sites

Só pode ser memória... o windows XP é bem sensível à memória mesmo... tente trocar por uma memória de melhor qualidade e/ou trocar o slot onde a memória está encaixada.

Compartilhar este post


Link para o post
Compartilhar em outros sites
Postado Originalmente por rxc@20 maio 2004, 11:00

achei isso aqui na internet mas não entendi direito se puderem ler e me ajudarem valeu!!

No se si te ayuda esto:

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

This Stop message, also known as Stop 0x7A, indicates that the requested page of kernel data from the paging file could not be read into memory.

Interpreting the Message

The four parameters listed in the message are defined in order of appearance as follows:

1.

Lock type that was held (value 1, 2, 3, or Page Table Entry [PTE] address).

2.

I/O status code.

3.

Current process (virtual address for lock type 3, or PTE).

4.

Virtual address that could not be read into memory.

For information about all possible status codes that might be returned, see the file Ntstatus.h of the Windows 2000 Device Driver Kit (DDK). For information about the DDK, see "Additional Resources" at the end of this chapter.

Resolving the Problem

Stop 0x7A is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

SCSI problems. If the I/O status is C0000185 and the paging file is on a SCSI disk, check the disk cabling and SCSI termination for problems.

Viruses. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. Any Windows 2000 file system can be infected by viruses.

Bad block. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r. For more information about the Recovery Console, see chapter "Repair, Recovery, and Restore" in this book.

Warning If your system partition is formatted with the FAT16 file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from a MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks.

Failing RAM. Another common cause of this error message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.

Also, check that all the adapter cards in the computer, including memory modules, are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Be sure to wipe the cleaned contacts off, removing all cleaning debris, before reinstalling the adapter card into the computer. If compressed air is available, use it to clear out the adapter card slot.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Microsoft periodically releases a package of product improvements and problem resolutions for Windows 2000 called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows 2000 dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed.

Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post-Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows 2000 dialog box. For more information about Service Packs and hotfixes, see "Additional Resources" at the end of this chapter.

Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.

For more troubleshooting information about the 0x7A Stop message, refer to the Microsoft Knowledge Base link , using the keywords winnt and 0x0000007A. For information about this resource, see "Additional Resources" at the end of this chapter.

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

by RID501

:muro:

Vou tentar:

Troque seus pentes de meória ou até mesmo baixe a velocidade deles ....

Deve estar havendo alguma imcompatibilidade na hora da leitura de dados, que podem estar tanto nas memórias como no processador .... (cache)

Faça um teste substituindo os pentes de memória e se não resolver, tente o processador!!! :joia:

[]'s

:-BEER:bandeira:

Compartilhar este post


Link para o post
Compartilhar em outros sites

Crie uma conta ou entre para comentar

Você precisar ser um membro para fazer um comentário

Entre para seguir isso  





Sobre o Clube do Hardware

No ar desde 1996, o Clube do Hardware é uma das maiores, mais antigas e mais respeitadas publicações sobre tecnologia do Brasil. Leia mais

Direitos autorais

Não permitimos a cópia ou reprodução do conteúdo do nosso site, fórum, newsletters e redes sociais, mesmo citando-se a fonte. Leia mais

×