ram ou software.

[dio_123]

Boa tarde,
Perciso de ajuda urgente no seguinte problema.

Tenho um insys W76sua só que estava a dar uns problemas de bluescreen com win7 ultimate e resolvi formatar e instalar o windows 7 profissional.
Depois instalar as minhas coisas e fazer o windows updates e o problema continua.
Então fiz o memtest por boot com os 2 pentes juntos uma vez que as rams tem garantia e a tampa está selada, e o memtest não detectou nenhum erro. Fiz 2 vezes mas nao detectou nenhum erro.

O que poderá ser?


MEMORY_MANAGEMENT


Technical Information:

*** STOP: 0x0000001a (0x0000000000041287, 0x0000000000000058, 0x0000000000000000,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff80002874540 base at 0xfffff80002804000 DateStamp
0x4f558ca0

Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Diogo\Desktop\Minidump\042212-32968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02868000 PsLoadedModuleList = 0xfffff800`02aa5e50
Debug session time: Sun Apr 22 16:01:03.379 2012 (UTC + 1:00)
System Uptime: 0 days 0:41:32.052
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41289, 7fefd9ba001, 997, a00000000020070}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a89 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041289, The subtype of the bugcheck.
Arg2: 000007fefd9ba001
Arg3: 0000000000000997
Arg4: 0a00000000020070

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR: 0x1a_41289

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: taskhost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002930a29 to fffff800028d9f00

STACK_TEXT:
fffff880`034a6988 fffff800`02930a29 : 00000000`0000001a 00000000`00041289 000007fe`fd9ba001 00000000`00000997 : nt!KeBugCheckEx
fffff880`034a6990 fffff800`02960c75 : 00000000`07008001 fffffa80`03dd1490 fffff880`034a6ca0 fffffa80`03dd1490 : nt! ?? ::FNODOBFM::`string'+0x4a89
fffff880`034a69d0 fffff800`02bbea91 : fffff880`00000010 00000000`00000001 fffffa80`064fa360 fffff800`00000001 : nt! ?? ::FNODOBFM::`string'+0x53100
fffff880`034a6ac0 fffff800`028d9153 : 00000000`00000ba8 fffffa80`05d75710 00000000`03e25d00 00000000`0328ece8 : nt!NtQueryVirtualMemory+0x67f
fffff880`034a6bb0 00000000`774400ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0328ecc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774400ea


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4a89
fffff800`02930a29 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4a89

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a89

BUCKET_ID: X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a89

Followup: MachineOwner
---------

 

[ptfuzi]

virose, disco, algum file danificado, temps, pode ser tanta coisa...

 

[dio_123]

virose não é que instalei 2 vezes o windows 7 professional e o windows xp, e acontece em ambos.
Já trocei de disco e acontece a mesma coisa.

Uma coisa que acontece é que se excutar o memtest pelo windows aparece várias mensagens deste tipo
> > Memory Errors Detected !
> > Copying between 36f8071 and 36f8060a did not result in accurate copy.

E depois clicar ok começa o teste com 10 erros.

Se executar o memtest pelo boot não detecta nenhum erro.

No memtest se for a configuration memory sizing e se escolher BiIOS -Std ou probe aparece logo 20 erros e crasha tenho de desligar o pc a força.