Help with BSOD have minidump debugged

[tweak13]

So after replacing things over and over im at my wits end, a brand new system build and I cant get it to run for a whole day sometimes. Heres what I got from my minidump. Any help appreciated. From what I read a lot of places its more than likely either my pagefile or RAM, does anyone else agree at all with this?


Debugging Details:
------------------


EXCEPTION_RECORD: fffffa60078e8ad8 -- (.exr 0xfffffa60078e8ad8)
ExceptionAddress: fffff80001ce9d37 (nt!RtlInsertElementGenericTableFullAvl+0x0000000000000097)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT: fffffa60078e84b0 -- (.cxr 0xfffffa60078e84b0)
rax=0000000000000000 rbx=fffff88006922b70 rcx=0000000000000000
rdx=0000000000000001 rsi=fffffa800322a568 rdi=0000000000000000
rip=fffff80001ce9d37 rsp=fffffa60078e8d10 rbp=0000000000000000
r8=fffff880060c0030 r9=00000000ffffffff r10=0000000000000001
r11=0000000000000002 r12=fffff8800690a904 r13=0000000000000010
r14=fffffa60078e8dc8 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!RtlInsertElementGenericTableFullAvl+0x97:
fffff800`01ce9d37 4c394008 cmp qword ptr [rax+8],r8 ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 10

PROCESS_NAME: rundll32.exe

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e85080
0000000000000008

BUGCHECK_STR: 0x24

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffffa60010e266f to fffff80001ce9d37

STACK_TEXT:
fffffa60`078e8d10 fffffa60`010e266f : 00010000`00005ae7 fffffa80`044a17d0 00000000`00000000 fffff880`0690a900 : nt!RtlInsertElementGenericTableFullAvl+0x97
fffffa60`078e8d50 fffffa60`010b8d67 : 00010000`00005ae7 fffffa80`044a1700 fffffa60`078e93b0 00010000`00005ae7 : Ntfs!NtfsCreateFcb+0x21f
fffffa60`078e8e30 fffffa60`010de134 : fffff880`068fb660 fffffa60`078e93b0 fffffa60`078e93b0 fffffa80`044a17d0 : Ntfs!NtfsOpenFile+0x1a7
fffffa60`078e9030 fffffa60`0102410d : fffffa80`042d5e50 fffffa80`044a17d0 fffffa60`078e93b0 fffffa60`078e9201 : Ntfs!NtfsCommonCreate+0xb34
fffffa60`078e9230 fffff800`01cd23d1 : fffffa60`078e9320 fffffa80`046ab990 fffffa80`046a4330 fffff800`01d0d850 : Ntfs!NtfsCommonCreateCallout+0x1d
fffffa60`078e9260 fffffa60`0102483a : fffffa60`010240f0 fffffa60`078e9320 fffffa80`042d5e50 fffffa80`044a17d0 : nt!KeExpandKernelStackAndCalloutEx+0x2e1
fffffa60`078e92f0 fffffa60`010dc56d : 00000000`00000000 fffffa60`078e93b0 fffffa80`044a17d0 fffffa80`044a17d0 : Ntfs!NtfsCommonCreateOnNewStack+0x4a
fffffa60`078e9350 fffffa60`00a80e17 : fffffa80`0322a030 fffffa80`044a17d0 fffffa80`046e9000 fffffa80`044a1701 : Ntfs!NtfsFsdCreate+0x1ad
fffffa60`078e94f0 fffffa60`00a9d26c : fffffa80`019fe590 fffffa80`01dce550 fffffa80`044a1700 fffffa60`078e95b0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`078e9560 fffff800`01f36d83 : fffffa80`02e04cc0 fffffa60`078e99e0 00000000`00000045 00000000`00000000 : fltmgr!FltpCreate+0x25d
fffffa60`078e9610 fffff800`01f30a59 : fffffa80`02e04cc0 00000000`00000000 fffffa80`03263610 00000000`00000001 : nt!IopParseDevice+0x5e3
fffffa60`078e97b0 fffff800`01f34944 : 00000000`00000000 fffffa80`046a4101 fffffa80`00000040 00000000`00000000 : nt!ObpLookupObjectName+0x5eb
fffffa60`078e98c0 fffff800`01f032f1 : 00000000`00000080 00000000`0015e628 00000000`00000001 fffff880`05dddaf0 : nt!ObOpenObjectByName+0x2f4
fffffa60`078e9990 fffff800`01cb0df3 : 00000000`00000001 fffffa60`078e9ca0 fffffa80`046a44b0 000007fe`c0000034 : nt!NtQueryAttributesFile+0x134
fffffa60`078e9c20 00000000`77705e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0015e468 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77705e4a


SYMBOL_NAME: PAGE_NOT_ZERO_VISTA

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffffa60078e84b0 ; kb

BUCKET_ID: PAGE_NOT_ZERO_VISTA

Followup: MachineOwner
---------

*** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption.

 

[tweak13]

I have to also add my other crashes returned different results for what caused it, I can upload those too but I didnt want to over do it right away.

 

[ghmage]

Burn a memtest86+ iso to a cd and test the memory.

 

[tweak13]

Ok so I ran a full pass off the tests and I came up with an error exactly as follows:
Does this mean bad RAM?

Tst - 6 Pass - 0 Failing Address - 00072854d1c - 1832.2 mb Good - ffbfffff Bad - ffffffff err-bits - 00400000 Count - 1 Chan - (nothing entered)

 

[ghmage]

It could, or not enough voltage or some other problem. Take out all but one stick and try one at a time. Also reseat the one that you test, blow off any dust.

 

[tweak13]

Voltage has been steady at 2.1 which is what crucial ballistix tracers are spec'd to run at. The Maximus II formula has an LCD screen to look at while the systems running which is where I'm assuming this from. I've replaced the board 2 times and I'm having a pretty hard time thinking its that again, although I guess anythings possible. Thanks much for the help I will repost results tomorrow.

 

[tweak13]

Alright so here are some more results, for confusing peoples sake ill just call it stick a and stick b.

Stick A in memtest gets an error after the second series of test runs.

Stick B in the same slot, no errors after an hour of tests, approx 5 series of runs.

Suggestions?

 

[ghmage]

If you've tried the suspect stick in both slots and it's dust free and all that jazz, it looks to be bad. Shame, but at least you found a problem. You can try to run the system without the bad stick of ram.

 

[tweak13]

Thats actually how Im able to type this right now. Cant say Im too happy its bad, but atleast Its not the MOBO again. I got some Gskill RAM on the way, Ill see how that works. thanks ghmage

 

[tweak13]

Turns out this still isn't fix. I have come to one blue screen since all this testing, minidump reports something different as follows.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffd8, 2, 0, fffff80001c63ec1}

Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+51 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffffd8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001c63ec1, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e40080
ffffffffffffffd8

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExpScanGeneralLookasideList+51
fffff800`01c63ec1 418b41d8 mov eax,dword ptr [r9-28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffffa6001916a20 -- (.trap 0xfffffa6001916a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffff9680 rbx=0000000000000000 rcx=00000000fdfdfff3
rdx=00000000603a7218 rsi=fffffa8000c8f0f8 rdi=fffffa8000c8f040
rip=fffff80001c63ec1 rsp=fffffa6001916bb0 rbp=0000000000000000
r8=00000000603a7218 r9=0000000000000000 r10=0000000000000004
r11=fffffa80035a00c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!ExpScanGeneralLookasideList+0x51:
fffff800`01c63ec1 418b41d8 mov eax,dword ptr [r9-28h] ds:6ce0:ffffffff`ffffffd8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001c6c0ee to fffff80001c6c350

STACK_TEXT:
fffffa60`019168d8 fffff800`01c6c0ee : 00000000`0000000a ffffffff`ffffffd8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`019168e0 fffff800`01c6afcb : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`01da9a50 : nt!KiBugCheckDispatch+0x6e
fffffa60`01916a20 fffff800`01c63ec1 : fffff800`00000000 00000000`00000000 fffff800`02017070 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`01916bb0 fffff800`01c5bf4a : 00000000`00000000 fffff800`01c5b9f0 fffffa80`00c8f000 00000000`00000001 : nt!ExpScanGeneralLookasideList+0x51
fffffa60`01916be0 fffff800`01c5bb0b : fffffa80`00c8f000 00000000`00000008 00000000`00000001 f4156159`00000000 : nt!ExAdjustLookasideDepth+0x2e
fffffa60`01916c10 fffff800`01e8eff3 : fffffa80`00c8f040 00000000`00000080 00000000`00000000 7604653e`00002301 : nt!KeBalanceSetManager+0x11b
fffffa60`01916d50 fffff800`01ca6546 : fffff800`01d8b680 fffffa80`00c8f040 fffff800`01d90b80 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01916d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+51
fffff800`01c63ec1 418b41d8 mov eax,dword ptr [r9-28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ExpScanGeneralLookasideList+51

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+51

BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+51

Followup: MachineOwner

 

[mentalynuts]

I know its new system build but have you checked online to see if any or youre drivers have been updated?Also did you do full reinstall of youre operating system when you built the pc or have you used old hard drive and jut updated it?

 

[tweak13]

I updated everything possible, it was a full reinstall from a brand new HDD.

I did fix it though, and it ended up being faulty RAM (twice). Couldnt run at 1066mhz even though thats what its rated for.

Switched to some reliable G Skill and it worked great. 3 weeks not a problem yet.