New
#11
Antivirus software:Code:avgnt.exe c:\program files (x86)\avira\antivir desktop\avgnt.exe 2480 8 200 1380 2/24/2012 5:31 AM 10.0.13.18 275.16 KB (281,768 bytes) 4/20/2011 10:24 AM avguard.exe c:\program files (x86)\avira\antivir desktop\avguard.exe 2040 8 200 1380 2/24/2012 5:30 AM 10.0.1.59 263.16 KB (269,480 bytes) 4/20/2011 10:24 AM avshadow.exe c:\program files (x86)\avira\antivir desktop\avshadow.exe 2124 8 200 1380 2/24/2012 5:30 AM 1.0.0.6 254.66 KB (260,776 bytes) 4/20/2011 10:24 AM sched.exe c:\program files (x86)\avira\antivir desktop\sched.exe 1772 8 200 1380 2/24/2012 5:30 AM 10.0.0.21 133.16 KB (136,360 bytes) 4/20/2011 10:24 AMCaused by Verifier, as anticipated. Typically, when Verifier blames Windows processes, you either have corrupted Windows files or a hardware problem. This particular crash report points to memory.Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\squat251\new minidump\022512-17565-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`03256000 PsLoadedModuleList = 0xfffff800`0349be90 Debug session time: Sat Feb 25 20:54:51.342 2012 (UTC - 7:00) System Uptime: 0 days 2:18:52.997 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {411, fffff6fc500671f0, 82b0000112d15882, fffff68000032269} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000411, The subtype of the bugcheck. Arg2: fffff6fc500671f0 Arg3: 82b0000112d15882 Arg4: fffff68000032269 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_411 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 TRAP_FRAME: fffff88008b0c860 -- (.trap 0xfffff88008b0c860) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80080a6060 rbx=0000000000000000 rcx=fffff8a00ce3e6a0 rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800034015f7 rsp=fffff88008b0c9f0 rbp=0000000000001000 r8=0000000000000001 r9=fffff80003256000 r10=fffffa800519c3c8 r11=0000000000000003 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!ExAllocatePoolWithTag+0x517: fffff800`034015f7 4c8b4908 mov r9,qword ptr [rcx+8] ds:fffff8a0`0ce3e6a8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032b32dd to fffff800032d6640 STACK_TEXT: fffff880`08b0c508 fffff800`032b32dd : 00000000`0000001a 00000000`00000411 fffff6fc`500671f0 82b00001`12d15882 : nt!KeBugCheckEx fffff880`08b0c510 fffff800`03307a71 : 82b00001`12d15882 fffff6fc`500671f0 0000007f`fffffff8 fffff800`033022a0 : nt! ?? ::FNODOBFM::`string'+0x6061 fffff880`08b0c560 fffff800`032f425f : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`0345abc0 : nt!MiResolveTransitionFault+0x381 fffff880`08b0c5f0 fffff800`032e443b : fffff8a0`021d0b50 00000000`00000000 00000000`00000000 fffff800`03480340 : nt!MiDispatchFault+0x95f fffff880`08b0c700 fffff800`032d476e : 00000000`00000000 fffff8a0`0ce3e6a8 fffffa80`08663300 fffffa80`0519c940 : nt!MmAccessFault+0xe1b fffff880`08b0c860 fffff800`034015f7 : fffff8a0`0cdcd580 00000000`00000003 fffff8a0`00000000 fffff800`03401fbd : nt!KiPageFault+0x16e fffff880`08b0c9f0 fffff800`035d058c : 00000000`00000003 00000000`00000001 fffff880`08b0cca0 fffff880`00000000 : nt!ExAllocatePoolWithTag+0x517 fffff880`08b0cae0 fffff800`0359b86b : 00000000`00000000 00000000`00000120 00000000`00000001 00000000`01544e01 : nt!SeQueryInformationToken+0x49c fffff880`08b0cb70 fffff800`032d58d3 : fffffa80`080a6060 00000000`003321c0 00000000`00000000 fffffa80`08ecf2b0 : nt!NtCompareTokens+0x13b fffff880`08b0cc20 00000000`76d81c0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`00cdeea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d81c0a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+6061 fffff800`032b32dd cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+6061 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a FAILURE_BUCKET_ID: X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061 BUCKET_ID: X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061 Followup: MachineOwner ---------
- Memtest86+ does not always find memory errors the first time it is run. Sometimes it needs to be run a few times for seven passes each to catch memory errors. Also, what memory do you have in the system? Can you download and install CPU-Z and upload screenshots of the CPU, Mainboard, Memory, and SPD tabs? In the SPD tab, upload an image of each slot.
The screenshots can help determine if there is a conflict with your memory or an incompatibility.
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
- I also notice Avira installed on your system which is known to cause crashes on some systems. Please remove Avira through Start Menu -> Control Panel -> Uninstall a program and then run the Avira RegistryCleaner - Download to remove remnants. Replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall, at least to test to see if the system is then more stable.
You may also check out the Good and Free system security combination.
Last edited by writhziden; 26 Feb 2012 at 09:37. Reason: System file check step added