min dator har kraschat 69 ggr sen 23e maj.. får ingen ordning på vad som orsakar krascherna.
jag har som sagt ett extra ramminne i datorn som är av samma storlek och typ som det som redan sitter i. datorn är nyligen formaterad (23e maj) men ändå startar den om sig. omstarterna sker inom 5 min när jag har startat datorn. ofta kör jag igång outlook express, IE, miranda(icq&msn) o winamp direkt + att virusprogrammet AVPersonal autostartas.
Jag har avinstallerat Norton Antivorus 2005 samt daemon tools och kört memtest i 2timmar utan några fel...
är det nån som kan tolka dessa 2 dumpar från igår och se vad som är fel? pleeease
dump1
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini061105-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Jun 11 00:54:18.328 2005 (GMT+2)
System Uptime: 0 days 0:00:22.031
Loading Kernel Symbols
......................................................................................................................................
Loading unloaded module list
.......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1902fe, f78d3a64, f78d3760, 804f64a1}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+9f )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001902fe
Arg2: f78d3a64
Arg3: f78d3760
Arg4: 804f64a1
Debugging Details:
------------------
EXCEPTION_RECORD: f78d3a64 -- (.exr fffffffff78d3a64)
ExceptionAddress: 804f64a1 (nt!RebalanceNode+0x0000001c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00ff010b
Attempt to read from address 00ff010b
CONTEXT: f78d3760 -- (.cxr fffffffff78d3760)
eax=000000ff ebx=e1a424ff ecx=00000000 edx=0000ff01 esi=00ff00ff edi=e1e764e8
eip=804f64a1 esp=f78d3b2c ebp=f78d3b3c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!RebalanceNode+0x1c:
804f64a1 8a4e0c mov cl,[esi+0xc] ds:0023:00ff010b=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from 804fe995 to 804f64a1
STACK_TEXT:
f78d3b3c 804fe995 e1e764e8 e1a364e8 8608e3c8 nt!RebalanceNode+0x1c
f78d3b54 804fe7c4 8608e3c8 e1a364e8 00000000 nt!DeleteNodeFromTree+0x94
f78d3b6c f732d54f 8608e3c8 e1a364e8 8608e260 nt!RtlDeleteElementGenericTableAvl+0x3b
f78d3b94 f730057a 86182008 f78d3bbc f78d3bc7 Ntfs!NtfsDeleteFcb+0x9f
f78d3be0 f7321d00 86182008 8608e100 e1a35820 Ntfs!NtfsTeardownFromLcb+0x1fd
f78d3c38 f72fc759 86182008 e1a358e8 00000000 Ntfs!NtfsTeardownStructures+0x125
f78d3c64 f731f6eb 86182008 01a358e8 00000000 Ntfs!NtfsDecrementCloseCounts+0x9e
f78d3ce8 f7327e13 86182008 e1a358e8 e1a35820 Ntfs!NtfsCommonClose+0x397
f78d3d7c 804e23b5 00000000 00000000 863c3a20 Ntfs!NtfsFspClose+0xe3
f78d3dac 80574128 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f78d3ddc 804efc81 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Ntfs!NtfsDeleteFcb+9f
f732d54f 8b06 mov eax,[esi]
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: Ntfs!NtfsDeleteFcb+9f
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107eea
STACK_COMMAND: .cxr fffffffff78d3760 ; kb
FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsDeleteFcb+9f
BUCKET_ID: 0x24_Ntfs!NtfsDeleteFcb+9f
Followup: MachineOwner
---------
dump2
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini061105-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Jun 11 11:28:48.234 2005 (GMT+2)
System Uptime: 0 days 0:07:02.814
Loading Kernel Symbols
..........................................................................................................................................
Loading unloaded module list
...............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bf8011d7, f6e34a48, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+68 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8011d7, The address that the exception occurred at
Arg3: f6e34a48, Trap Frame
Arg4: 00000000
Debugging Details:
