*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0152fa6fc, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f519b6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f02100
fffff8a0152fa6fc
FAULTING_IP:
nt!CmpCleanUpKCBCacheTable+da
fffff800`02f519b6 0fba630414 bt dword ptr [rbx+4],14h
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
[COLOR=#ff0000]BUGCHECK_STR: 0x50[/COLOR]
PROCESS_NAME: TrustedInstall
CURRENT_IRQL: 0
TRAP_FRAME: fffff880091266a0 -- (.trap 0xfffff880091266a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a0078f2de8
rdx=fffffe3f9fffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f519b6 rsp=fffff88009126830 rbp=fffff8a010ec3001
r8=00000000ffffffff r9=0000000000014200 r10=0000000000000000
r11=0000000001ffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!CmpCleanUpKCBCacheTable+0xda:
fffff800`02f519b6 0fba630414 bt dword ptr [rbx+4],14h ds:014d:00000000`00000004=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c7b54c to fffff80002cd31c0
STACK_TEXT:
fffff880`09126538 fffff800`02c7b54c : 00000000`00000050 fffff8a0`152fa6fc 00000000`00000000 fffff880`091266a0 : nt!KeBugCheckEx
fffff880`09126540 fffff800`02cd12ee : 00000000`00000000 fffff8a0`152fa6fc fffffa80`0de92000 fffff8a0`152fa6f8 : nt! ?? ::FNODOBFM::`string'+0x456df
fffff880`091266a0 fffff800`02f519b6 : fffff8a0`143ce948 fffff8a0`12804201 fffff8a0`10ec3010 00000000`00000200 : nt!KiPageFault+0x16e
fffff880`09126830 fffff800`02f5245c : fffff8a0`10ec3010 00000000`00000000 00000000`00000001 fffff800`00000000 : nt!CmpCleanUpKCBCacheTable+0xda
fffff880`091268e0 fffff800`02f520b8 : fffff8a0`128042f0 fffff880`09126b60 000007fe`fd3b3101 fffff8a0`16a35a80 : nt!CmpSearchForOpenSubKeys+0x40
fffff880`09126930 fffff800`02cd2453 : fffffa80`0f655590 000007fe`fd3b3110 00000000`00000000 fffffa80`0dad5f00 : nt!NtUnloadKey2+0x597
fffff880`09126ae0 00000000`77022b9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bedf08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77022b9a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpCleanUpKCBCacheTable+da
fffff800`02f519b6 0fba630414 bt dword ptr [rbx+4],14h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!CmpCleanUpKCBCacheTable+da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
FAILURE_BUCKET_ID: X64_0x50_nt!CmpCleanUpKCBCacheTable+da
BUCKET_ID: X64_0x50_nt!CmpCleanUpKCBCacheTable+da
Followup: MachineOwner
Not the Windows memory diagnostic utility.Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+
BugCheck 3B, {c0000005, fffff80002fc6a9b, fffff8800bc4ed60, 0}
[U][B]Probably caused by : Pool_Corruption[/B][/U] ( nt!ExDeferredFreePool+1df )
Followup: Pool_corruption
[SIZE=3][COLOR=#ff0000][I][B]SYSTEM_SERVICE_EXCEPTION (3b)[/B][/I][/COLOR][/SIZE]
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fc6a9b, Address of the instruction which caused the bugcheck
Arg3: fffff8800bc4ed60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExDeferredFreePool+1df
fffff800`02fc6a9b 4c395808 cmp qword ptr [rax+8],r11
CONTEXT: fffff8800bc4ed60 -- (.cxr 0xfffff8800bc4ed60)
rax=0045004e004f004e rbx=00000000000000c2 rcx=fffffa8006c6b1f0
rdx=fffff8a00aa35770 rsi=0000000000000000 rdi=fffff8a0095f9900
rip=fffff80002fc6a9b rsp=fffff8800bc4f740 rbp=0000000000000000
r8=0000000000000000 r9=fffff8a00aa35670 r10=0000000000000001
r11=fffff8a00aa35680 r12=fffffa8006c6b000 r13=0000000000000000
r14=000000000000000f r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExDeferredFreePool+0x1df:
fffff800`02fc6a9b 4c395808 cmp qword ptr [rax+8],r11 ds:002b:0045004e`004f0056=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [COLOR=#ff0000][U][I][B]aaHMSvc.exe[/B][/I][/U][/COLOR]
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fc61a1 to fffff80002fc6a9b
STACK_TEXT:
fffff880`0bc4f740 fffff800`02fc61a1 : 00000000`00000000 fffff8a0`0941f810 00000000`003ef170 fffff8a0`0941f820 : nt!ExDeferredFreePool+0x1df
fffff880`0bc4f7d0 fffff800`02ea33d4 : 00000000`00000001 00000000`00000000 fffffa80`74536d4d fffffa80`06d37a40 : nt!ExFreePoolWithTag+0x411
fffff880`0bc4f880 fffff800`03135075 : 00000000`00000000 fffff8a0`0a8e5b20 00000000`00000000 00000000`00000146 : nt!ObfDereferenceObject+0xd4
fffff880`0bc4f8e0 fffff800`031a2a18 : fffff8a0`0a8e5b00 00000000`00000001 fffffa80`096661a0 fffffa80`0703f6a0 : nt!AlpcpSectionDestroyProcedure+0x39
fffff880`0bc4f910 fffff800`03137470 : fffff8a0`0a8e5b20 fffffa80`07142b90 fffffa80`0729f150 fffffa80`0729f110 : nt!AlpcpDestroyBlob+0x28
fffff880`0bc4f940 fffff800`031a2a18 : fffff8a0`0ab4a5b0 fffff8a0`0ab78530 fffff8a0`0ab78510 00000000`00000000 : nt!AlpcpRegionDestroyProcedure+0xd0
fffff880`0bc4f970 fffff800`03136faf : 00000000`00000000 00000000`00000000 fffff8a0`00000001 fffff8a0`0ab78530 : nt!AlpcpDestroyBlob+0x28
fffff880`0bc4f9a0 fffff800`031a2a18 : fffff8a0`0ab78510 00000000`00000000 fffff800`0300ae60 00000000`00000001 : nt!AlpcpViewDestroyProcedure+0x30f
fffff880`0bc4fa40 fffff800`0314d21a : fffff8a0`0ab78530 00000000`ffffffff 00000000`ffffffff 00000000`00000000 : nt!AlpcpDestroyBlob+0x28
fffff880`0bc4fa70 fffff800`02e99453 : fffffa80`072f3b50 fffff880`0bc4fb60 00000000`7efd5001 fffffa80`0a2b0350 : nt!NtAlpcDeleteSectionView+0x142
fffff880`0bc4fae0 00000000`770b1ada : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`003ee808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770b1ada
FOLLOWUP_IP:
nt!ExDeferredFreePool+1df
fffff800`02fc6a9b 4c395808 cmp qword ptr [rax+8],r11
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+1df
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff8800bc4ed60 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+1df
BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+1df
Followup: Pool_corruption
AiChargerPlus.sys | 11/8/2010 |
AODDriver2.sys | 3/6/2012 |
AsIO.sys | 8/23/2010 |
AsUpIO.sys | 8/2/2010 |
And perhaps follow that up with the vendor specific disk diagnostic utility from your hard drive manufacturer. Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.Launch an elevated command prompt (StartOrb->All Programs->Accessories->Command Prompt, right click it and choose Run As Administrator) and type
chkdsk C: /R
hit enter and answer Yes “Y” when prompted and reboot.
Let it run all five stages. When complete check the log file in Event Viewer for results (Click the StartOrb and type event viewer and hit enter, expand Windows Logs and highlight / select Application, click Action on the menu bar and select Find and type chkdsk and hit enter.
I'm sorry, I didn't know "memtest" referred to a very specific program. I'm knew to all of these diagnostics. Didn't mean to burst your bubble. Please don't give up on my case just because I didn't fully understand. :/ I'm no computer genius.
Thanks for the info. The settings look fine although I could not tell what the command rate was set to on the single stick that you showed, ideally 2T.
Assuming no mismatch with the other sticks (all are identical in every respect) then those settings (with the exception of the command rate) should be fine.
I'll reiterate again as both Kemical and myself have said before it is vital that you determine if the problems you are experiencing are due to faulty RAM modules or MoBo slots
There were no new dump files evident in your most recent attachment so that leaves us with nothing to add or take away from the diagnostic process.
I'm afraid that until you can get pristine and error free results with memtest86+ then going off on tangents and pursuing other avenues will simply result in us chasing the proverbial wild geese.