BSOD after installation win7 64bit

[aldymrvica]

Sorry, if this is a duplicate thread.
I'm so frustating about this bsod.

I just bought a PC, and it use win7 64bit
and, it getting bsod IRQL NOT LESS OR EQUAL

I read many thread about this, and still can't fix my problem

so, I decided to make this thread and attach minidump file

hope you guys can help me

Best Regards,

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[aldymrvica]

which one of these files that you mean?

anyway, i just reinstalled win 7 64bit?
but, bsod is still happen?

so, I upload another minidump file and sf diagnostic
hopefully these are the right files that you need

thanks for your help

 

[Arc]

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
____________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff80002eb3150}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002eb3150, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c5100
GetUlongFromAddress: unable to read from fffff800030c51c0
 0000000000000010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02eb3150 f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  avast_free_ant

TRAP_FRAME:  fffff8800897f660 -- (.trap 0xfffff8800897f660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
rdx=0000000000000050 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eb3150 rsp=fffff8800897f7f0 rbp=fffffa8003ecec50
 r8=fffff800030c8500  r9=fffffa800c5d0000 r10=fffffa800c5d03b8
r11=fffff80003008e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiReplenishPageSlist+0xc0:
fffff800`02eb3150 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8d169 to fffff80002e8dbc0

STACK_TEXT:  
fffff880`0897f518 fffff800`02e8d169 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0897f520 fffff800`02e8bde0 : fffffa80`0c5d0988 00000000`0000003d fffffa80`012cfb70 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0897f660 fffff800`02eb3150 : fffff880`0897f950 00000000`00000000 fffff800`03008e80 fffff780`00000320 : nt!KiPageFault+0x260
fffff880`0897f7f0 fffff800`02eb190f : fffffa80`0c5d0398 00000000`00000017 fffffa80`03316c50 00000000`00000017 : nt!MiReplenishPageSlist+0xc0
fffff880`0897f860 fffff800`02e9b044 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`0897f980 fffff800`02e8bcee : 00000000`00000001 00000000`05a59000 00000000`fffdb001 00000000`021a7682 : nt!MmAccessFault+0x1224
fffff880`0897fae0 00000000`001a7276 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`004ce3bc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1a7276


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02eb3150 f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

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