svedjro
-
Innehållsantal
29 -
Gick med
-
Besökte senast
Inlägg postade av svedjro
-
-
Nu har jag kör ett memtest med ( Memtest-86 v3,5 ) och det verkar vara helt ok.
( Pass complete, no errors )
Jag har faktiskt provat att rucka på grejorna, t ex stänga locket mm men det blir samma problem ändå.
// Roffe
-
Jag tackar för alla tips.
När det gäller värmen så är inte det några problem tror jag eftersom datorn kan stå och gå hur länge som helst när den väl har startat och det är heller aldrig några problem om jag t ex installerat uppdateringar och datorn måste startas om så brukar det funka hur fint som helst.
Och jag har heller inga gula varningstrianglar och dom senaste drivrutinerna är installerade, däremot har jag inte kört memotest på datorn, vet ni något bra program för detta eller finns det inbyggt i windows?
-
Nä, jag gjorde en ren installation på den nya disken, men den beter sig likadant som den gjorde med den gamla disken.
-
Windows XP Pro med SP3
-
Jag har ingen panik, med det är väldigt irriterande eftersom det alltid är i uppstarten som det krånglar, den har aldrig strulat när den väl är i gång, som nu t ex. jag har försökt hitta en nyare BIOS men det verkar inte finnas. Hårddisken är helt ny, eftersom jag trodde det var den som krånglade.
Datorn är:
Fujitsu Siemens
Amilo D 1840W
-
Här är den.
http://sprend.com/download.jsp?FileId=7zPAjr9YmdMDp9F8jFP5
Jag försvinner några timmar men sen är jag tillbaka.
Tack för hjälpen så länge.
Roffe
-
Hoppas att detta blev rätt.
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Användare\Rolf\Skrivbord\Mini021910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\mappfördinasymbolfiler*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Fri Feb 19 07:34:55.203 2010 (GMT+4)
System Uptime: 0 days 0:00:33.890
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1902fe, f69c75a0, f69c729c, 80582f86}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Ntfs.sys ( Ntfs!NtfsReadMftRecord+86 )
Followup: MachineOwner
1: 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: f69c75a0
Arg3: f69c729c
Arg4: 80582f86
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: Ntfs
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48025be5
EXCEPTION_RECORD: f69c75a0 -- (.exr 0xfffffffff69c75a0)
ExceptionAddress: 80582f86 (nt+0x000abf86)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 36bbc401
Attempt to write to address 36bbc401
CONTEXT: f69c729c -- (.cxr 0xfffffffff69c729c)
eax=36bbc401 ebx=866f4100 ecx=80582f84 edx=00000000 esi=00000c00 edi=00000000
eip=80582f86 esp=f69c7668 ebp=f69c7684 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt+0xabf86:
80582f86 0000 add byte ptr [eax],al ds:0023:36bbc401=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from f758cc89 to 80582f86
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f69c7684 f758cc89 865699d8 86705a50 00000c00 nt+0xabf86
f69c76f8 f758cb96 865699d8 866f4100 e1014c60 Ntfs!NtfsReadMftRecord+0x86
f69c7730 f758caed 865699d8 866f4100 e1014c60 Ntfs!NtfsReadFileRecord+0x7a
f69c7768 f757b55a 865699d8 e1014c58 e1014c60 Ntfs!NtfsLookupInFileRecord+0x37
f69c7818 f75e7f7c 865699d8 866f4100 00000001 Ntfs!NtfsSetVolumeInfoFlagState+0x51
f69c7838 f757ba6e 865699d8 866f4100 00000001 Ntfs!NtfsMarkVolumeDirty+0x2e
f69c7850 f7573999 865699d8 c0000102 e16adc00 Ntfs!NtfsPostVcbIsCorrupt+0x19
f69c7874 f75c9683 865699d8 c0000102 e16adc00 Ntfs!NtfsRaiseStatus+0x6d
f69c78dc f758cb96 865699d8 866f4100 e16adc00 Ntfs!NtfsReadMftRecord+0x1a3
f69c7914 f758caed 865699d8 866f4100 e16adc00 Ntfs!NtfsReadFileRecord+0x7a
f69c794c f7592178 865699d8 e16adbf8 e16adc00 Ntfs!NtfsLookupInFileRecord+0x37
f69c7a24 f75a5f80 865699d8 e16adcc0 e16adce0 Ntfs!NtfsWriteFileSizes+0x76
f69c7a9c f75a6160 865699d8 86396660 85eee468 Ntfs!NtfsCommonFlushBuffers+0x17e
f69c7b00 804e13eb 866f4020 86396660 86737030 Ntfs!NtfsFsdFlushBuffers+0x92
f69c7b18 804e13eb 866b3dd0 86396660 80701410 nt+0xa3eb
f69c7b3c 80584c49 866b3dd0 86396660 85eee468 nt+0xa3eb
f69c7bb4 804dd99f 80000760 f69c7c48 f69c7c50 nt+0xadc49
f69c7bc4 804e38b7 badb0d00 f69c7c3c f69c7b98 nt+0x699f
f69c7c50 805e2b8b e16af758 00000000 00000000 nt+0xc8b7
f69c7cd8 805e37c6 e16af758 00000000 e16af758 nt+0x10bb8b
f69c7cf0 805e0e6b e16af701 e1572cd0 00000000 nt+0x10c7c6
f69c7d04 805e0f03 e16af758 00000120 f69c7d64 nt+0x109e6b
f69c7d58 804dd99f 000000f8 0007fcec 7c90e514 nt+0x109f03
f69c7d64 7c90e514 badb0d00 0007fcd4 51794d1b nt+0x699f
f69c7d68 badb0d00 0007fcd4 51794d1b 1a7f5959 0x7c90e514
f69c7d6c 0007fcd4 51794d1b 1a7f5959 00000000 0xbadb0d00
f69c7d70 51794d1b 1a7f5959 00000000 00000000 0x7fcd4
f69c7d74 1a7f5959 00000000 00000000 00000000 0x51794d1b
f69c7d78 00000000 00000000 00000000 00000000 0x1a7f5959
FOLLOWUP_IP:
Ntfs!NtfsReadMftRecord+86
f758cc89 8b431c mov eax,dword ptr [ebx+1Ch]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsReadMftRecord+86
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Ntfs.sys
STACK_COMMAND: .cxr 0xfffffffff69c729c ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: 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: f69c75a0
Arg3: f69c729c
Arg4: 80582f86
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: Ntfs
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48025be5
EXCEPTION_RECORD: f69c75a0 -- (.exr 0xfffffffff69c75a0)
ExceptionAddress: 80582f86 (nt+0x000abf86)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 36bbc401
Attempt to write to address 36bbc401
CONTEXT: f69c729c -- (.cxr 0xfffffffff69c729c)
eax=36bbc401 ebx=866f4100 ecx=80582f84 edx=00000000 esi=00000c00 edi=00000000
eip=80582f86 esp=f69c7668 ebp=f69c7684 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt+0xabf86:
80582f86 0000 add byte ptr [eax],al ds:0023:36bbc401=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from f758cc89 to 80582f86
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f69c7684 f758cc89 865699d8 86705a50 00000c00 nt+0xabf86
f69c76f8 f758cb96 865699d8 866f4100 e1014c60 Ntfs!NtfsReadMftRecord+0x86
f69c7730 f758caed 865699d8 866f4100 e1014c60 Ntfs!NtfsReadFileRecord+0x7a
f69c7768 f757b55a 865699d8 e1014c58 e1014c60 Ntfs!NtfsLookupInFileRecord+0x37
f69c7818 f75e7f7c 865699d8 866f4100 00000001 Ntfs!NtfsSetVolumeInfoFlagState+0x51
f69c7838 f757ba6e 865699d8 866f4100 00000001 Ntfs!NtfsMarkVolumeDirty+0x2e
f69c7850 f7573999 865699d8 c0000102 e16adc00 Ntfs!NtfsPostVcbIsCorrupt+0x19
f69c7874 f75c9683 865699d8 c0000102 e16adc00 Ntfs!NtfsRaiseStatus+0x6d
f69c78dc f758cb96 865699d8 866f4100 e16adc00 Ntfs!NtfsReadMftRecord+0x1a3
f69c7914 f758caed 865699d8 866f4100 e16adc00 Ntfs!NtfsReadFileRecord+0x7a
f69c794c f7592178 865699d8 e16adbf8 e16adc00 Ntfs!NtfsLookupInFileRecord+0x37
f69c7a24 f75a5f80 865699d8 e16adcc0 e16adce0 Ntfs!NtfsWriteFileSizes+0x76
f69c7a9c f75a6160 865699d8 86396660 85eee468 Ntfs!NtfsCommonFlushBuffers+0x17e
f69c7b00 804e13eb 866f4020 86396660 86737030 Ntfs!NtfsFsdFlushBuffers+0x92
f69c7b18 804e13eb 866b3dd0 86396660 80701410 nt+0xa3eb
f69c7b3c 80584c49 866b3dd0 86396660 85eee468 nt+0xa3eb
f69c7bb4 804dd99f 80000760 f69c7c48 f69c7c50 nt+0xadc49
f69c7bc4 804e38b7 badb0d00 f69c7c3c f69c7b98 nt+0x699f
f69c7c50 805e2b8b e16af758 00000000 00000000 nt+0xc8b7
f69c7cd8 805e37c6 e16af758 00000000 e16af758 nt+0x10bb8b
f69c7cf0 805e0e6b e16af701 e1572cd0 00000000 nt+0x10c7c6
f69c7d04 805e0f03 e16af758 00000120 f69c7d64 nt+0x109e6b
f69c7d58 804dd99f 000000f8 0007fcec 7c90e514 nt+0x109f03
f69c7d64 7c90e514 badb0d00 0007fcd4 51794d1b nt+0x699f
f69c7d68 badb0d00 0007fcd4 51794d1b 1a7f5959 0x7c90e514
f69c7d6c 0007fcd4 51794d1b 1a7f5959 00000000 0xbadb0d00
f69c7d70 51794d1b 1a7f5959 00000000 00000000 0x7fcd4
f69c7d74 1a7f5959 00000000 00000000 00000000 0x51794d1b
f69c7d78 00000000 00000000 00000000 00000000 0x1a7f5959
FOLLOWUP_IP:
Ntfs!NtfsReadMftRecord+86
f758cc89 8b431c mov eax,dword ptr [ebx+1Ch]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsReadMftRecord+86
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Ntfs.sys
STACK_COMMAND: .cxr 0xfffffffff69c729c ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> lmvm Ntfs
start end module name
f7566000 f75f2600 Ntfs (pdb symbols) c:\mappfördinasymbolfiler\ntfs.pdb\AA4F4A5C7B1D4663A7E0891479090D8A2\ntfs.pdb
Loaded symbol image file: Ntfs.sys
Mapped memory image file: C:\mappfördinasymbolfiler\Ntfs.sys\48025BE58c600\Ntfs.sys
Image path: Ntfs.sys
Image name: Ntfs.sys
Timestamp: Sun Apr 13 23:45:49 2008 (48025BE5)
CheckSum: 0009586B
ImageSize: 0008C600
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: NT File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
1: kd>
start end module name
f7566000 f75f2600 Ntfs (pdb symbols) c:\mappfördinasymbolfiler\ntfs.pdb\AA4F4A5C7B1D4663A7E0891479090D8A2\ntfs.pdb
Loaded symbol image file: Ntfs.sys
Mapped memory image file: C:\mappfördinasymbolfiler\Ntfs.sys\48025BE58c600\Ntfs.sys
Image path: Ntfs.sys
Image name: Ntfs.sys
Timestamp: Sun Apr 13 23:45:49 2008 (48025BE5)
CheckSum: 0009586B
ImageSize: 0008C600
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: NT File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
1: kd>
start end module name
f7566000 f75f2600 Ntfs (pdb symbols) c:\mappfördinasymbolfiler\ntfs.pdb\AA4F4A5C7B1D4663A7E0891479090D8A2\ntfs.pdb
Loaded symbol image file: Ntfs.sys
Mapped memory image file: C:\mappfördinasymbolfiler\Ntfs.sys\48025BE58c600\Ntfs.sys
Image path: Ntfs.sys
Image name: Ntfs.sys
Timestamp: Sun Apr 13 23:45:49 2008 (48025BE5)
CheckSum: 0009586B
ImageSize: 0008C600
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: NT File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
1: kd>
start end module name
f7566000 f75f2600 Ntfs (pdb symbols) c:\mappfördinasymbolfiler\ntfs.pdb\AA4F4A5C7B1D4663A7E0891479090D8A2\ntfs.pdb
Loaded symbol image file: Ntfs.sys
Mapped memory image file: C:\mappfördinasymbolfiler\Ntfs.sys\48025BE58c600\Ntfs.sys
Image path: Ntfs.sys
Image name: Ntfs.sys
Timestamp: Sun Apr 13 23:45:49 2008 (48025BE5)
CheckSum: 0009586B
ImageSize: 0008C600
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: NT File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
-
Här är dumpfilen!
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Fri Feb 19 07:34:55.203 2010 (GMT+4)
System Uptime: 0 days 0:00:33.890
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded 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: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1902fe, f69c75a0, f69c729c, 80582f86}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : Ntfs.sys ( Ntfs+26c89 )
Followup: MachineOwner
---------
-
Tackar för tipset, jag återkommer med analysen.
-
Hjälp!
Jag har en laptop som bara jäklas när man ska starta den, antingen händer det ingenting eller blir det blåbild. Ibland får man starta tio gånger innan den vaknar till liv, men är den väl har startat så funkar allt helt felfritt. Jag har en dmp fil men den typen av fil går inte att ladda upp här.
Tacksam för svar.
-
Hej svedjro!
Vi får väl försöka hjälpa din Amilo & hitta fram till felet/felen.
Om vi går lite närmare in i detalj på vad som händer vid starten, ger datorn ifrån sig ett felmeddelande av något slag?
Klistra gärna in den informationen här i tråden om där finns ett eller flera error-meddelanden iform av text & siffror.
Beskriv också helst vid vilken skärmsekvens dessa meddelanden dyker upp på skärmen.
En fråga också gällande den nya hårddisken; Lät du skapa en ren ny installation ifrån en XP installationsskiva på disken, eller är XP gjord på denna med hjälp utav en identisk cloning/backup ifrån den gamla hårddisken?
Känner du till hur man använder och eller har tillgång till följande saker, Original XP installations-skiva, Återställningskonsolen, kommando-tolken, sfc/ scannow, bootcfg, boot.ini, fixboot, fixmbr?
Har haft lite att göra så jag har inte hunnit svara.
Jag har gjort en ren installation av XP på den nya disken och det som händer när jag startar datorn är lite olika saker, ibland händer som sagt ingenting, ingen diskaktivitet, ibland börjar skärmen blinka till mycket snabbt med vit bakrund och idag så hände först ingenting men sedan började datorn ge ifrån sig en signal och så stod det 0033 nere i högra hörnet av skärmen, men sedan när jag startar om igen så kan det helt plötsligt funka alldeles utmärkt. Däremot när jag väl fått igång den och installerar någonting eller uppdaterar från Windows uppdate t ex och man måste starta om datorn så verkar det som att den alltid startar riktigt. Jag har försökt att hitta en ny BIOS version men inte lyckats, den versionen jag har idag är 1,05c.
-
Det var många tips, jag får väl börja och kolla BIOS och om det finns någon uppdatering till denna.
-
Jag har en dator som inte vill starta ibland, när jag sätter på den så går alla fläktar igång och det lyser i lamporna men oftast brukar skärmen bli svart och hårddisken har ingen aktivitet. Jag får då hålla inne strömknappen till den stängs av och så får jag sätta på den igen och då brukar den ladda windows en liten bit sedan startar datorn om automatiskt och sedan brukar det funka. Jag trodde att det var hårddisken som det var något fel på så jag har köpt en ny och satt i men det verkar inte hjälpa. jag har även stängt av alla vilolägen mm för det brukar ställa till problem.
Är det någon som har något bra tips så vore jag tacksam.
Datorn är en:
Fujitsu/Siemens AMILO D1840W Notebook
P4 3.2 GHz - 15.4" TFT
1,0Gb RAM
Grafik ATI Mobility Radeon 9600 - 128 MB
Microsoft Windows XP PRO
-
Finns F-Secure med i bilden??
Kolla denna länk i såfall! http://www.alltomxp.se/forum/index.php?showtopic=19050
Mvh
Mats H
Tusen tack för detta tipset, nu funkar allt igen.
-
Kan kolla dessa :
Testa med det här till .Net,,, :
http://support.microsoft.com/kb/923100
Edit : gissar på metod #2.
,,,och testa med det här sedan:
http://support.microsoft.com/kb/910336
Prova att hämta viktiga uppdateringar först,, rekommenderade uppdateringar senare.
Jah har nu testat allt detta men det hjälper inte det heller, om jag startar Windows Install Clean Up tool eller lägg till / ta bort program i kontrollpanelen så finns inte någon NET. Frameworkversion över huvud taget, det kommer ett felmeddelande ( se bild ).
-
Hej!
Jag har fått ett problem när jag skall uppdatera datorn, den hämtar alla uppdteringar men när den försöker installera dom så misslyckas det hela tiden. jag har försökt att installera en åt gången men det hjälper inte, jag fick ett tips att det kan vara NET,Framework som spökar och har avinstallerat detta och provat att installera igen men det blir samma problem. Jag har även försökt att installera Microsoft Update men då får jag felmeddelande också. Jag kör Windows Vista Home Premium och den är original, ingen falsk kopia här inte. Har ni några tips är jag tacksam. Skickar med några printscreen hur det ser ut.
-
Berätta vad det är för nätverkskort du har, vilka drivrutinsversioner du testat samt det exakta felmeddelandet du får när du försöker ansluta. Med dessa uppgifter är det mycket enklare att assistera dig och nå en lösning
Tackar för visat intresse som vanligt. Jag lyckades att få tag på rätt drivrutin till det trådlösa WLAN kortet och då funkade det. Så nu är det frid och fröjd igen. Tack än en gång.
-
Låt oss för stunden bortse alternativet nedgradering och försöka lösa problemet.
Har du installerat Service Packen för Vista?`
Prova ta bort koret i enhetshanteraren och låt Windows installera detta själv och se om detta löser problemet.
Dubbelkolla så du skrivit i rätt lösenord för ditt nätverk, samt att nätverkskortet stödjer den krypterings standad du
satt på din accesspunkt.
Jag har testat allt detta, men det hjälper inte. Det återstår nog bara att gå tillbaks till XP, för då funkade det. Eller har du några mer tips?
-
Hej. Jag har en bärbar dator som hade XP Home installerat och nu har jag installerat en ren Vista Home Premium installation istället, men nu funkar inte det trådlösa nätverket, den hittar nätverket men det står att den inte har någon signalstyrka och att ( nätverkskortets egenskaper matchar inte kraven för det här nätverket). Jag har installerat nya drivrutiner men det verkar inte hjälpa. Vad kan man göra? Kan man nedgradera från Vista till XP igen, och i så fall hur gör man?
-
Tackar för alla svar, jag kör F-Secure Client Security 8.00 build 232 och har aldrig råkat ut för detta problem, men det har faktiskt löst sig ändå. Jag startade om datorn ett par gånger och sista gången så kunde jag inte starta om utan det stod att den installerar uppdateringar och man inte skulle stänga av datorn, men det gjorde jag ändå, och helt plötsligt så kunde alla uppdateringar på windows update instaleras korrekt, förbannat underligt, så nu funkar allt plötsligt igen.
-
När windows update försöker hämta de 9st uppdateringar som finns för min dator så laddar den ner till 31% men sen är det stopp, jag har försökt att ladda ner en åt gången men det hjälper inte. Jag har startat om datorn med windows skivan i och försökt att reparera datorn den vägen men det hjälper inte heller. Det är både säkerhetsuppdateringar och uppdateringar för skräppostfiltret. Det står att den hämtar uppdateringar men det händer ingenting. Detta har alltid funkat förut, vad kan ha hänt? Jag kör Windows Vista Home Premium. Det verkar som om att vid datum 2009-07-17 och framåt har det hänt något för kollar jag på uppdateringshistoriken so är det väldigt många uppdateringar som har status ( misslyckades ).
-
Invänta Service Pack 2 eller läs denna artikel, detta är ett känt problem som rättas till i uppdateringen beskriven i artikeln eller om du väntar in SP2.
http://www.alltomxp.se/smatt-o-gott/office...-stabilare.html
Tackar för ett så snabbt svar. ( Om det fanns ett nobelpris för Microsofts produkter så skulle du ha det. )
-
Denna text kommer upp varje gång jag startar Outlook 2007, jag har provat att reparera Office men det hjälper inte.
"En datafil stängdes inte korrekt senast den användes. Filen genomsöks efter eventuella fel. Prestanda kan påverkas medan kontrollen pågår"
Efter detta kommer det fram ett meddelande om att filen har genomsökts, men sen händer inte mycket mer.
Vad gör man
-
Tackar för ett snabbt svar, jag skall testa detta.
Datorn vill inte starta ibland!
i Allmänna datorfrågor och -diskussioner
Postad
Jag får ta till mig alla tips och återkomma, just nu har man lite annat att göra med all snö som faller, men jag återkommer vad som händer.
Tack än en gång för alla tips!
//Roffe