Constant random BSoDs

[scheng12]

I built a computer around November and it hasn't ever been running perfectly since. I installed a legitimate version of Windows 7 64 bit. I've been using WhoCrashed to figure out what happened but it's not completely clear on the causes. There used to be occasional overheats that I've fixed and recently it's just been driver crashes. Hopefully someone can help me figure this out.

 

[Maguscreed]

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: fffff6ffffffdf80, memory referenced
Arg2: 0000000000000000, 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: fffff800030e44be, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033000e0
 fffff6ffffffdf80 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiDispatchFault+de
fffff800`030e44be 488b1c29        mov     rbx,qword ptr [rcx+rbp]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome --no-sa

TRAP_FRAME:  fffff88003b2f820 -- (.trap 0xfffff88003b2f820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffbf00000420 rbx=0000000000000000 rcx=fffff68000000000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030e44be rsp=fffff88003b2f9b0 rbp=0000007fffffdf80
 r8=ffffffffffbf0000  r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiDispatchFault+0xde:
fffff800`030e44be 488b1c29        mov     rbx,qword ptr [rcx+rbp] ds:5963:fffff6ff`ffffdf80=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c7ca9 to fffff800030c8740

STACK_TEXT:  
fffff880`03b2f6d8 fffff800`030c7ca9 : 00000000`0000000a fffff6ff`ffffdf80 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03b2f6e0 fffff800`030c6920 : 00000000`00000000 00000000`00bfe490 fffff700`01080000 00000000`00000014 : nt!KiBugCheckDispatch+0x69
fffff880`03b2f820 fffff800`030e44be : 00000000`00000000 00000000`00bf6d78 fffff680`00005fb0 fffffa80`058d9928 : nt!KiPageFault+0x260
fffff880`03b2f9b0 fffff800`030e2743 : ffffffff`ffffff00 00000000`00bfe490 fffff880`03b2fc20 fffff680`00000000 : nt!MiDispatchFault+0xde
fffff880`03b2fac0 fffff800`030c682e : 00000000`00000000 00000000`05d22c00 00000000`00000001 00000000`057fea9c : nt!MmAccessFault+0x343
fffff880`03b2fc20 00000000`68ff2e72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0043f0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x68ff2e72


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+de
fffff800`030e44be 488b1c29        mov     rbx,qword ptr [rcx+rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+de

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiDispatchFault+de

BUCKET_ID:  X64_0xA_nt!MiDispatchFault+de

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

Seeing a lot of memory corruption errors.
We'll have a look at drivers in a bit here, but first let's scan the memory with memtest 86
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html <--- instructions.

This is best done overnight, letting it make 6-8 passes

 

[scheng12]

OK thanks for the help. I will let it run tonight and get back to you tomorrow morning

 

[scheng12]

I ran the tests with both RAM pieces in and it came up with a few errors. I didn't have time to test them individually yet but I will do so within the next few nights since I am extremely busy during the day. Is there any way to take a look at the drivers in the meantime?

 

[Maguscreed]

If you came up with memory errors, there's not much point in messing with the other stuff while the ram is questionable. The crashes would more than likely continue no matter what we did in the driver department.