Damp Skrevet 12. september 2009 Del Skrevet 12. september 2009 (endret) Jeg aner ikke hva som kan være problemet, har bygd pc til bror og den fryser "tilfeldig". Tror mest sannsynlig at det er et driverproblem, men er ikke sikker. Her er en debug av dumpen fra BSOD: Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: SRV*DownstreamStore*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`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50 Debug session time: Sun Sep 13 11:24:59.419 2009 (GMT+2) System Uptime: 0 days 0:04:26.027 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {200, 2, 1, fffff88001873c99} *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys Probably caused by : hardware ( Rt64win7+13293 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000200, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88001873c99, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 0000000000000200 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpTcbFastDatagram+3a9 fffff880`01873c99 0100 add dword ptr [rax],eax DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800596b750 -- (.trap 0xfffff8800596b750) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000200 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000340 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001873c99 rsp=fffff8800596b8e8 rbp=fffff8800596bb90 r8=000000000fdfb83c r9=0000000000000000 r10=fffffa800483c820 r11=fffffa8005236640 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc tcpip!TcpTcbFastDatagram+0x3a9: fffff880`01873c99 0100 add dword ptr [rax],eax ds:e080:0200=???????? Resetting default scope MISALIGNED_IP: tcpip!TcpTcbFastDatagram+3a9 fffff880`01873c99 0100 add dword ptr [rax],eax LAST_CONTROL_TRANSFER: from fffff80002a8a469 to fffff80002a8af00 STACK_TEXT: fffff880`0596b608 fffff800`02a8a469 : 00000000`0000000a 00000000`00000200 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0596b610 fffff800`02a890e0 : fffffa80`04872e30 00000000`0fdfb83c fffffa80`05248470 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0596b750 fffff880`01873c99 : ffffffff`ffffffa4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0596b8e8 00000000`0fdfb83d : fffff880`018746f5 ffff0000`00000000 fffffa80`05902190 00000000`00000014 : tcpip!TcpTcbFastDatagram+0x3a9 fffff880`0596baa8 fffff880`018746f5 : ffff0000`00000000 fffffa80`05902190 00000000`00000014 00000000`00000010 : 0xfdfb83d fffff880`0596bab0 fffff880`018790ca : fffffa80`04877f00 fffff800`02a97600 fffffa80`0483b901 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5 fffff880`0596bc60 fffff880`01878c17 : fffff880`0513e922 fffffa80`0486e000 00000000`00000000 fffff880`0185c300 : tcpip!TcpMatchReceive+0x1fa fffff880`0596bdb0 fffff880`0185b3c7 : fffffa80`0486e000 fffffa80`04872e30 fffffa80`04879669 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177 fffff880`0596be60 fffff880`0185b499 : fffff880`0596bfe0 fffff880`0196b9a0 fffff880`0596bff0 ffffffff`ffffebac : tcpip!IppDeliverListToProtocol+0x97 fffff880`0596bf20 fffff880`0185b990 : fffffa80`0486e000 bd87bf9e`bdb2bb94 bdc1d418`bdfcc78a fffff880`0596bfe0 : tcpip!IppProcessDeliverList+0x59 fffff880`0596bf90 fffff880`0185a821 : 00000000`00000000 fffffa80`0486e000 fffff880`0196b9a0 00000000`0524b001 : tcpip!IppReceiveHeaderBatch+0x231 fffff880`0596c070 fffff880`01859272 : fffffa80`04c60950 00000000`00000000 fffffa80`0524b001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651 fffff880`0596c270 fffff880`018726ba : fffffa80`0524b010 fffff880`0596c3a0 fffffa80`0524b010 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`0596c350 fffff800`02a9a64a : fffffa80`04ffc7a0 fffff880`05967000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`0596c3a0 fffff880`018720e2 : fffff880`018725e0 fffff880`0596c4b0 00000000`00000002 fffff880`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`0596c480 fffff880`017100eb : fffffa80`052461b0 00000000`00000000 fffffa80`04e671a0 00000000`00000001 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`0596c4f0 fffff880`016d9fc6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`0596c560 fffff880`01653ef1 : fffffa80`04e671a0 00000000`00000002 00000000`00000001 fffff800`02a90dda : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 fffff880`0596c9e0 fffff880`03bc7293 : fffffa80`04fcb000 00000000`00000001 00000000`00000000 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1 fffff880`0596ca30 fffff880`03bb8e4e : fffffa80`04e67100 00000000`00000001 00000000`0000000a fffff880`0596cb60 : Rt64win7+0x13293 fffff880`0596cb10 fffff880`016dee4b : fffff880`00000000 fffffa80`04e671a0 fffffa80`04fcb000 fffffa80`04e67f68 : Rt64win7+0x4e4e fffff880`0596cb60 fffff880`01664bfd : fffffa80`05227388 00000000`0000000a 00000000`00000000 00000000`00000000 : ndis! ?? ::DKGKHJNI::`string'+0x1597 fffff880`0596cbd0 fffff880`0168bb0c : 00000000`00000000 fffffa80`05227388 00000000`00000080 fffffa80`04823260 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd fffff880`0596cc70 fffff800`02d2e166 : 00000000`119160ef fffffa80`04d51b60 00000000`00000080 fffffa80`04d51b60 : ndis!ndisReceiveWorkerThread+0x12c fffff880`0596cd00 fffff800`02a69486 : fffff880`009ec180 fffffa80`04d51b60 fffff880`009f6f40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a fffff880`0596cd40 00000000`00000000 : fffff880`0596d000 fffff880`05967000 fffff880`0596c9c0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: Rt64win7+13293 fffff880`03bc7293 4533d2 xor r10d,r10d SYMBOL_STACK_INDEX: 13 SYMBOL_NAME: Rt64win7+13293 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000200, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88001873c99, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 0000000000000200 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpTcbFastDatagram+3a9 fffff880`01873c99 0100 add dword ptr [rax],eax DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800596b750 -- (.trap 0xfffff8800596b750) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000200 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000340 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001873c99 rsp=fffff8800596b8e8 rbp=fffff8800596bb90 r8=000000000fdfb83c r9=0000000000000000 r10=fffffa800483c820 r11=fffffa8005236640 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc tcpip!TcpTcbFastDatagram+0x3a9: fffff880`01873c99 0100 add dword ptr [rax],eax ds:e080:0200=???????? Resetting default scope MISALIGNED_IP: tcpip!TcpTcbFastDatagram+3a9 fffff880`01873c99 0100 add dword ptr [rax],eax LAST_CONTROL_TRANSFER: from fffff80002a8a469 to fffff80002a8af00 STACK_TEXT: fffff880`0596b608 fffff800`02a8a469 : 00000000`0000000a 00000000`00000200 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0596b610 fffff800`02a890e0 : fffffa80`04872e30 00000000`0fdfb83c fffffa80`05248470 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0596b750 fffff880`01873c99 : ffffffff`ffffffa4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0596b8e8 00000000`0fdfb83d : fffff880`018746f5 ffff0000`00000000 fffffa80`05902190 00000000`00000014 : tcpip!TcpTcbFastDatagram+0x3a9 fffff880`0596baa8 fffff880`018746f5 : ffff0000`00000000 fffffa80`05902190 00000000`00000014 00000000`00000010 : 0xfdfb83d fffff880`0596bab0 fffff880`018790ca : fffffa80`04877f00 fffff800`02a97600 fffffa80`0483b901 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5 fffff880`0596bc60 fffff880`01878c17 : fffff880`0513e922 fffffa80`0486e000 00000000`00000000 fffff880`0185c300 : tcpip!TcpMatchReceive+0x1fa fffff880`0596bdb0 fffff880`0185b3c7 : fffffa80`0486e000 fffffa80`04872e30 fffffa80`04879669 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177 fffff880`0596be60 fffff880`0185b499 : fffff880`0596bfe0 fffff880`0196b9a0 fffff880`0596bff0 ffffffff`ffffebac : tcpip!IppDeliverListToProtocol+0x97 fffff880`0596bf20 fffff880`0185b990 : fffffa80`0486e000 bd87bf9e`bdb2bb94 bdc1d418`bdfcc78a fffff880`0596bfe0 : tcpip!IppProcessDeliverList+0x59 fffff880`0596bf90 fffff880`0185a821 : 00000000`00000000 fffffa80`0486e000 fffff880`0196b9a0 00000000`0524b001 : tcpip!IppReceiveHeaderBatch+0x231 fffff880`0596c070 fffff880`01859272 : fffffa80`04c60950 00000000`00000000 fffffa80`0524b001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651 fffff880`0596c270 fffff880`018726ba : fffffa80`0524b010 fffff880`0596c3a0 fffffa80`0524b010 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`0596c350 fffff800`02a9a64a : fffffa80`04ffc7a0 fffff880`05967000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`0596c3a0 fffff880`018720e2 : fffff880`018725e0 fffff880`0596c4b0 00000000`00000002 fffff880`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`0596c480 fffff880`017100eb : fffffa80`052461b0 00000000`00000000 fffffa80`04e671a0 00000000`00000001 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`0596c4f0 fffff880`016d9fc6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`0596c560 fffff880`01653ef1 : fffffa80`04e671a0 00000000`00000002 00000000`00000001 fffff800`02a90dda : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 fffff880`0596c9e0 fffff880`03bc7293 : fffffa80`04fcb000 00000000`00000001 00000000`00000000 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1 fffff880`0596ca30 fffff880`03bb8e4e : fffffa80`04e67100 00000000`00000001 00000000`0000000a fffff880`0596cb60 : Rt64win7+0x13293 fffff880`0596cb10 fffff880`016dee4b : fffff880`00000000 fffffa80`04e671a0 fffffa80`04fcb000 fffffa80`04e67f68 : Rt64win7+0x4e4e fffff880`0596cb60 fffff880`01664bfd : fffffa80`05227388 00000000`0000000a 00000000`00000000 00000000`00000000 : ndis! ?? ::DKGKHJNI::`string'+0x1597 fffff880`0596cbd0 fffff880`0168bb0c : 00000000`00000000 fffffa80`05227388 00000000`00000080 fffffa80`04823260 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd fffff880`0596cc70 fffff800`02d2e166 : 00000000`119160ef fffffa80`04d51b60 00000000`00000080 fffffa80`04d51b60 : ndis!ndisReceiveWorkerThread+0x12c fffff880`0596cd00 fffff800`02a69486 : fffff880`009ec180 fffffa80`04d51b60 fffff880`009f6f40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a fffff880`0596cd40 00000000`00000000 : fffff880`0596d000 fffff880`05967000 fffff880`0596c9c0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: Rt64win7+13293 fffff880`03bc7293 4533d2 xor r10d,r10d SYMBOL_STACK_INDEX: 13 SYMBOL_NAME: Rt64win7+13293 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000200, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88001873c99, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 0000000000000200 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpTcbFastDatagram+3a9 fffff880`01873c99 0100 add dword ptr [rax],eax DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800596b750 -- (.trap 0xfffff8800596b750) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000200 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000340 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001873c99 rsp=fffff8800596b8e8 rbp=fffff8800596bb90 r8=000000000fdfb83c r9=0000000000000000 r10=fffffa800483c820 r11=fffffa8005236640 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc tcpip!TcpTcbFastDatagram+0x3a9: fffff880`01873c99 0100 add dword ptr [rax],eax ds:e080:0200=???????? Resetting default scope MISALIGNED_IP: tcpip!TcpTcbFastDatagram+3a9 fffff880`01873c99 0100 add dword ptr [rax],eax LAST_CONTROL_TRANSFER: from fffff80002a8a469 to fffff80002a8af00 STACK_TEXT: fffff880`0596b608 fffff800`02a8a469 : 00000000`0000000a 00000000`00000200 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0596b610 fffff800`02a890e0 : fffffa80`04872e30 00000000`0fdfb83c fffffa80`05248470 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0596b750 fffff880`01873c99 : ffffffff`ffffffa4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0596b8e8 00000000`0fdfb83d : fffff880`018746f5 ffff0000`00000000 fffffa80`05902190 00000000`00000014 : tcpip!TcpTcbFastDatagram+0x3a9 fffff880`0596baa8 fffff880`018746f5 : ffff0000`00000000 fffffa80`05902190 00000000`00000014 00000000`00000010 : 0xfdfb83d fffff880`0596bab0 fffff880`018790ca : fffffa80`04877f00 fffff800`02a97600 fffffa80`0483b901 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5 fffff880`0596bc60 fffff880`01878c17 : fffff880`0513e922 fffffa80`0486e000 00000000`00000000 fffff880`0185c300 : tcpip!TcpMatchReceive+0x1fa fffff880`0596bdb0 fffff880`0185b3c7 : fffffa80`0486e000 fffffa80`04872e30 fffffa80`04879669 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177 fffff880`0596be60 fffff880`0185b499 : fffff880`0596bfe0 fffff880`0196b9a0 fffff880`0596bff0 ffffffff`ffffebac : tcpip!IppDeliverListToProtocol+0x97 fffff880`0596bf20 fffff880`0185b990 : fffffa80`0486e000 bd87bf9e`bdb2bb94 bdc1d418`bdfcc78a fffff880`0596bfe0 : tcpip!IppProcessDeliverList+0x59 fffff880`0596bf90 fffff880`0185a821 : 00000000`00000000 fffffa80`0486e000 fffff880`0196b9a0 00000000`0524b001 : tcpip!IppReceiveHeaderBatch+0x231 fffff880`0596c070 fffff880`01859272 : fffffa80`04c60950 00000000`00000000 fffffa80`0524b001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651 fffff880`0596c270 fffff880`018726ba : fffffa80`0524b010 fffff880`0596c3a0 fffffa80`0524b010 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`0596c350 fffff800`02a9a64a : fffffa80`04ffc7a0 fffff880`05967000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`0596c3a0 fffff880`018720e2 : fffff880`018725e0 fffff880`0596c4b0 00000000`00000002 fffff880`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`0596c480 fffff880`017100eb : fffffa80`052461b0 00000000`00000000 fffffa80`04e671a0 00000000`00000001 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`0596c4f0 fffff880`016d9fc6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`0596c560 fffff880`01653ef1 : fffffa80`04e671a0 00000000`00000002 00000000`00000001 fffff800`02a90dda : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 fffff880`0596c9e0 fffff880`03bc7293 : fffffa80`04fcb000 00000000`00000001 00000000`00000000 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1 fffff880`0596ca30 fffff880`03bb8e4e : fffffa80`04e67100 00000000`00000001 00000000`0000000a fffff880`0596cb60 : Rt64win7+0x13293 fffff880`0596cb10 fffff880`016dee4b : fffff880`00000000 fffffa80`04e671a0 fffffa80`04fcb000 fffffa80`04e67f68 : Rt64win7+0x4e4e fffff880`0596cb60 fffff880`01664bfd : fffffa80`05227388 00000000`0000000a 00000000`00000000 00000000`00000000 : ndis! ?? ::DKGKHJNI::`string'+0x1597 fffff880`0596cbd0 fffff880`0168bb0c : 00000000`00000000 fffffa80`05227388 00000000`00000080 fffffa80`04823260 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd fffff880`0596cc70 fffff800`02d2e166 : 00000000`119160ef fffffa80`04d51b60 00000000`00000080 fffffa80`04d51b60 : ndis!ndisReceiveWorkerThread+0x12c fffff880`0596cd00 fffff800`02a69486 : fffff880`009ec180 fffffa80`04d51b60 fffff880`009f6f40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a fffff880`0596cd40 00000000`00000000 : fffff880`0596d000 fffff880`05967000 fffff880`0596c9c0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: Rt64win7+13293 fffff880`03bc7293 4533d2 xor r10d,r10d SYMBOL_STACK_INDEX: 13 SYMBOL_NAME: Rt64win7+13293 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner --------- Endret 14. september 2009 av Farmatyr Lenke til kommentar
Syar-2003 Skrevet 12. september 2009 Del Skrevet 12. september 2009 Ser ut som opphavet hele tiden er IP/TCP-IP. Du kan prøve oppdaterte drivere til nettverkskort/Wlan kontrollere som er initiert. Eller også sjekke om krasj forsvinner med å "disable" alle nettverks kontrollerene i BIOS. Lenke til kommentar
Damp Skrevet 14. september 2009 Forfatter Del Skrevet 14. september 2009 (endret) Er det mulig at det kan være noe galt med minnebrikkene? Den fryser ofte under installasjoner og ved spilling, den fryser ikke når man surfer på nettet. Endret 14. september 2009 av Farmatyr Lenke til kommentar
Mechablast Skrevet 14. september 2009 Del Skrevet 14. september 2009 Er det mulig at det kan være noe galt med minnebrikkene? Den fryser ofte under installasjoner og ved spilling, den fryser ikke når man surfer på nettet. En måte å finne ut det på, kjør memtest86, la den gjerne stå over natten. Du kan også slå av automatisk restart ved systemfeil om du ikke har gjort det alt. Lenke til kommentar
Damp Skrevet 14. september 2009 Forfatter Del Skrevet 14. september 2009 Kjørte nettop memtest 300 errors etter 1 min, vet ikke helt hva alt betyr men det ser dårlig ut Poster et screenshot snart. Lenke til kommentar
Damp Skrevet 14. september 2009 Forfatter Del Skrevet 14. september 2009 Slik ser det ut, her frøs da maskinen: Lenke til kommentar
Mechablast Skrevet 14. september 2009 Del Skrevet 14. september 2009 (endret) Prøv å ta ut alle brikkene, og deretter sette i en og en og teste de for feil. Men du kan også sjekke at minnet får rett spenning. Endret 14. september 2009 av minibig Lenke til kommentar
Damp Skrevet 14. september 2009 Forfatter Del Skrevet 14. september 2009 Skal skjekke begge deler, her er hovedkort og ram hvis noen lurer: ASUS P5Q SE2, P45, Socket-775 Corsair Dominator TWIN2X PC8500 4GB DDR2 Lenke til kommentar
Mechablast Skrevet 14. september 2009 Del Skrevet 14. september 2009 (endret) Undersøkte litt på nett og så at det er en del som har problemer med defekte brikker av denne typen. Noen DOA er også. Endret 14. september 2009 av minibig Lenke til kommentar
Damp Skrevet 14. september 2009 Forfatter Del Skrevet 14. september 2009 Fant den defekte brikken og maskinen kjører som den skal, ser det ut som. Takk for all hjelp! Lenke til kommentar
Mechablast Skrevet 14. september 2009 Del Skrevet 14. september 2009 (endret) Fant den defekte brikken og maskinen kjører som den skal, ser det ut som. Takk for all hjelp! Bare hyggelig. Setter du tråden som løst? Endret 14. september 2009 av minibig Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå