New
#1
Windows 7 x64 crashes
Happens a lot, can't figure out what the problem is. Attaching the dmp file, if somebody can help i'd appreciate it.
Happens a lot, can't figure out what the problem is. Attaching the dmp file, if somebody can help i'd appreciate it.
The probable cause of this crash was memory management.
I would
download memtestx86 and run for 5 passes
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\021310-17628-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50 Debug session time: Sat Feb 13 07:58:44.077 2010 (GMT-5) System Uptime: 0 days 0:10:45.918 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff70001080000, e76, 9b500001c6a} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3690c ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 0000000000000e76 Arg4: 000009b500001c6a Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800916d940 -- (.trap 0xfffff8800916d940) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=00000000045a0000 rdx=fffffa8009181060 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002d981cc rsp=fffff8800916dad0 rbp=fffff8800916dca0 r8=0000000000000000 r9=00000000045b9000 r10=0000000fffffffff r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!NtLockVirtualMemory+0x2fc: fffff800`02d981cc 8b01 mov eax,dword ptr [rcx] ds:0028:00000000`045a0000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cf3db6 to fffff80002c7ef00 STACK_TEXT: fffff880`0916d6c8 fffff800`02cf3db6 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00000e76 : nt!KeBugCheckEx fffff880`0916d6d0 fffff800`02c98f23 : ffffffff`ffffff00 fffff880`0916d780 00000000`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x3690c fffff880`0916d7e0 fffff800`02c7cfee : 00000000`00000000 ffffffff`ffffffff 00000000`04570000 00000000`00000000 : nt!MmAccessFault+0x343 fffff880`0916d940 fffff800`02d981cc : ffffffff`ffffffff fffff880`0916dca0 00000000`00000002 00000000`000007ff : nt!KiPageFault+0x16e fffff880`0916dad0 fffff800`02c7e153 : fffffa80`091c3060 00000000`0236f540 00000000`0236f548 00000000`003d77d0 : nt!NtLockVirtualMemory+0x2fc fffff880`0916dc20 00000000`776d0d1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0236f508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776d0d1a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+3690c fffff800`02cf3db6 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3690c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+3690c BUCKET_ID: X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+3690c Followup: MachineOwner ---------
sorry for the late reply, i did the memtest. it failed. im gonna run a memtest individually for each stick to see if its a stick problem or if its the mobo itself.
So I've been playing around with it for a while, did memtest on each stick, didnt fail. I did memetest on all 4 sticks, now it didnt fail. Now I'm attaching more dmp files. Anybody can help?
Hi and welcome HS
If these are after your testing your memory you still have the same problem. How long did you run memtest for?
You might also want to run a system file check to verify and repair you system files
type cmd in search>right click and run as admin>sfc /scannow
Ken
Code:030210-13041-01.dmp 3/2/2010 6:30:45 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa7f`e4d51d48 00000000`00000005 00000000`00000000 fffff880`0fe43f13 nvlddmkm.sys nvlddmkm.sys+1df13 x64 C:\Users\K\Desktop\New folder (3)\030210-13041-01.dmp 4 15 7600 030310-13743-01.dmp 3/3/2010 8:02:09 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`06d60b40 00000000`00000001 fffff800`02f837e3 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\030310-13743-01.dmp 4 15 7600 030310-15381-01.dmp 3/3/2010 6:22:39 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`ffffffff 00000000`00000000 fffff880`041c22eb 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\030310-15381-01.dmp 4 15 7600 030410-13447-01.dmp 3/4/2010 8:23:19 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff89e`02cc6f00 00000000`00000008 fffff89e`02cc6f00 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\030410-13447-01.dmp 4 15 7600 030510-14211-01.dmp 3/5/2010 9:50:38 PM SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0x000000c1 fffff980`02bacc10 fffff980`02bac100 00000000`00c503e8 00000000`00000023 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\030510-14211-01.dmp 4 15 7600 030510-14804-01.dmp 3/5/2010 9:49:14 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa00`06991160 00000000`00000002 00000000`00000000 fffff800`0311ba96 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\030510-14804-01.dmp 4 15 7600 030710-14383-01.dmp 3/7/2010 1:35:35 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa28`09ba11f4 00000000`00000002 00000000`00000000 fffff800`02cb3924 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\030710-14383-01.dmp 4 15 7600 030810-15163-01.dmp 3/8/2010 5:42:11 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000000 00000000`00000005 00000000`00000001 fffff880`0fe34f07 nvlddmkm.sys nvlddmkm.sys+1df07 x64 C:\Users\K\Desktop\New folder (3)\030810-15163-01.dmp 4 15 7600 031010-13306-01.dmp 3/10/2010 8:31:33 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`0318c728 fffff880`0318bf80 fffff880`012ec023 Ntfs.sys Ntfs.sys+96023 x64 C:\Users\K\Desktop\New folder (3)\031010-13306-01.dmp 4 15 7600 031010-13338-01.dmp 3/10/2010 10:58:17 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`014d00bf fffff880`093be570 00000000`00000000 ndis.sys ndis.sys+30bf x64 C:\Users\K\Desktop\New folder (3)\031010-13338-01.dmp 4 15 7600 031010-13369-01.dmp 3/10/2010 11:35:42 AM PFN_LIST_CORRUPT 0x0000004e 00000000`00000002 00000000`001ed04e 00000000`0022ffff 00000000`00000001 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\031010-13369-01.dmp 4 15 7600 031010-14601-01.dmp 3/10/2010 9:44:07 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00008884 fffffa80`048fd1a0 fffffa80`04825d10 00000000`00000502 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder (3)\031010-14601-01.dmp 4 15 7600
Those dumps are after the test passed, I did 5 passes for all the sticks. So your telling me all those dumps are all memory related?
My guess is just a bad connection on the memory contacts. With an earth strap on, use a pencil eraser on the gold contacts on each memory stick until they gleam.