the blue screen of DEATH

[phasing]

pah o update a bios nao resolveu.. vou tentar ver os minidumps dps post novidades

edit:


pah nabia o que tinha de copiar por isso passei tudo:S:S


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


Loading Dump File [C:\WINDOWS\Minidump\Mini051907-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri May 18 18:15:25.406 2007 (GMT+1)
System Uptime: 0 days 2:00:40.098
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image Ntfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ea1dcd00, 0, f7b7574f, 2}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for sr.sys
Unable to load image KLIF.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for KLIF.SYS
*** ERROR: Module load completed but symbols could not be loaded for KLIF.SYS
Probably caused by : KLIF.SYS ( KLIF+13036 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ea1dcd00, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: f7b7574f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: ea1dcd00

FAULTING_IP:
Ntfs!NtfsCheckValidAttributeAccess+218
f7b7574f 3b437c cmp eax,dword ptr [ebx+7Ch]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from f7b76013 to f7b7574f

STACK_TEXT:
9c7223cc f7b76013 9c722850 e2f5fcc8 00000080 Ntfs!NtfsCheckValidAttributeAccess+0x218
9c722460 f7b763d1 9c722850 87ec51bc 89870100 Ntfs!NtfsCommonCreate+0xd31
9c7224b8 f7b76297 9c722850 87ec5008 87ec51bc Ntfs!NtfsOpenAttributeInExistingFile+0x3f9
9c7225c4 f7b767b8 9c722850 87ec5008 87ec51bc Ntfs!NtfsOpenAttribute+0x31e
9c7226ac f7b75f51 9c722850 87ec5008 87ec51bc Ntfs!NtfsUpcaseName+0x2d
9c72282c f7b76e42 9c722850 87ec5008 9c722980 Ntfs!NtfsCommonCreate+0xb17
9c7229d8 f7456f70 87ec5008 9c722bfc 89870020 Ntfs!NtfsAreHashNamesEqual+0x107
9c7229f8 9cc00036 87ec5008 9c722bfc 898745f0 sr!SrFastIoQueryOpen+0x40
WARNING: Stack unwind information not available. Following frames may be wrong.
9c722a08 9c722b00 9c722cc0 002ce618 80581c97 KLIF+0x13036
9c722a0c 9c722cc0 002ce618 80581c97 87ec5008 0x9c722b00
9c722b00 8056c063 898c5030 00000000 88194008 0x9c722cc0
9c722b78 8056f2a8 00000000 9c722bb8 00000040 nt!CmpQuerySecurityDescriptorInfo+0x1d
9c722bcc 805842b8 00000000 00000000 bf80ea01 nt!ObQueryDeviceMapInformation+0x79
9c722d54 804dd99e 0012f274 0012f23c 0012f2a0 nt!CmpSetValueKeyExisting+0x45
9c722d78 00000000 00000000 00000000 00000000 nt!ZwQueryEvent+0x13


STACK_COMMAND: kb

FOLLOWUP_IP:
KLIF+13036
9cc00036 ?? ???

SYMBOL_STACK_INDEX: 8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: KLIF

IMAGE_NAME: KLIF.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4533613c

SYMBOL_NAME: KLIF+13036

FAILURE_BUCKET_ID: 0x50_KLIF+13036

BUCKET_ID: 0x50_KLIF+13036

Followup: MachineOwner

 

[phasing]

parece.m que ja resolvi o problema.. testei cada um dos dimms no socket um e davam bsod pus no socket 2 e ja n tem problema.. hhii.. maravilha.. o problema e que talves a board esteja a dar o berro

 

[WindWalker]

Limpa o slot da memória com um pincel ou assim. Pode ser pó acumulado que leva a mau contacto.

Quando encaixares a memória nesse slot abana-a um pouco para os lados para garantir um melhor contacto.

Isto se quiseres continuar a usar esse slot

 

[phasing]

Limpa o slot da memória com um pincel ou assim. Pode ser pó acumulado que leva a mau contacto.

Quando encaixares a memória nesse slot abana-a um pouco para os lados para garantir um melhor contacto.

Isto se quiseres continuar a usar esse slot

boa ideia.. vou fazer ja isso bgd

 

[phasing]

nao da.. e do socket mesmo.. limpei aquilo direitinho.. e reparei que tava com uma cena branca .. ja estava todo feliz que tinha resolvido o problema mas deu bsod com 2min de video.. agora pus no socket 2 e ja esta direita:S.. e da maneira que começo a investir num pc novo( C2D)

abc e obrigado a todos pelas ajudas..

penso que podem fechar o topico!