Please can any1 help me with the blue screen?
 Minidump.zip ( 38.25k ) Number of downloads: 10

3 types of BSODs take turn to ruin my life, please help me. Sent to ASUS for repair but they just formatted the laptop for me and the BSODs are still persistent.

1st one:
Microsoft ® Windows Debugger Version 6.2.9200.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092712-26754-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a0e50
Debug session time: Thu Sep 27 20:07:49.481 2012 (UTC + 8:00)
System Uptime: 0 days 0:06:12.026
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {48, 2, 1, fffff80002f85b1f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

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: 0000000000000048, 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: fffff80002f85b1f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b0e0
GetUlongFromAddress: unable to read from fffff8000310b198
0000000000000048 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiIdentifyPfn+26f
fffff800`02f85b1f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff8800af154b0 -- (.trap 0xfffff8800af154b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0200000000000020
rdx=000000000004fb24 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f85b1f rsp=fffff8800af15640 rbp=fffffa8009ee4b90
r8=000000000004f4e5 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nt!MiIdentifyPfn+0x26f:
fffff800`02f85b1f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ed2ca9 to fffff80002ed3740

STACK_TEXT:
fffff880`0af15368 fffff800`02ed2ca9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0af15370 fffff800`02ed1920 : 00000000`42506650 02000000`00015b18 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0af154b0 fffff800`02f85b1f : 00000000`00000000 02000000`00019493 00000000`000018c0 fffff800`0319a35b : nt!KiPageFault+0x260
fffff880`0af15640 fffff800`02f867cb : 00000000`00000000 00000000`00000020 fffffa80`043927f0 fffffa80`04392000 : nt!MiIdentifyPfn+0x26f
fffff880`0af156e0 fffff800`032e5595 : fffffa80`04392000 fffff880`0af15c60 fffff880`0af157b8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`0af15720 fffff800`0322a8b8 : 00000000`00000006 00000000`00000000 fffffa80`04392000 fffff800`02e63001 : nt!PfpPfnPrioRequest+0x115
fffff880`0af15770 fffff800`031d13c3 : 00000000`00000000 fffff800`02e63000 fffffa80`040103a0 fffff880`0af15801 : nt! ?? ::NNGAKEGL::`string'+0x472ad
fffff880`0af15800 fffff800`031d21e5 : 00000000`02e5b648 00000000`0004fe80 00000000`02e5b6a0 00000000`076666c8 : nt!ExpQuerySystemInformation+0x11c2
fffff880`0af15ba0 fffff800`02ed2993 : 00000000`00000000 00000000`03a37c60 fffffa80`04a91601 00000000`03e4e700 : nt!NtQuerySystemInformation+0x4d
fffff880`0af15be0 00000000`777800ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02e5b5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777800ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiIdentifyPfn+26f
fffff800`02f85b1f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiIdentifyPfn+26f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

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: 0000000000000048, 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: fffff80002f85b1f, address which referenced memory

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


WRITE_ADDRESS: 0000000000000048 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiIdentifyPfn+26f
fffff800`02f85b1f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff8800af154b0 -- (.trap 0xfffff8800af154b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0200000000000020
rdx=000000000004fb24 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f85b1f rsp=fffff8800af15640 rbp=fffffa8009ee4b90
r8=000000000004f4e5 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nt!MiIdentifyPfn+0x26f:
fffff800`02f85b1f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ed2ca9 to fffff80002ed3740

STACK_TEXT:
fffff880`0af15368 fffff800`02ed2ca9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0af15370 fffff800`02ed1920 : 00000000`42506650 02000000`00015b18 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0af154b0 fffff800`02f85b1f : 00000000`00000000 02000000`00019493 00000000`000018c0 fffff800`0319a35b : nt!KiPageFault+0x260
fffff880`0af15640 fffff800`02f867cb : 00000000`00000000 00000000`00000020 fffffa80`043927f0 fffffa80`04392000 : nt!MiIdentifyPfn+0x26f
fffff880`0af156e0 fffff800`032e5595 : fffffa80`04392000 fffff880`0af15c60 fffff880`0af157b8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`0af15720 fffff800`0322a8b8 : 00000000`00000006 00000000`00000000 fffffa80`04392000 fffff800`02e63001 : nt!PfpPfnPrioRequest+0x115
fffff880`0af15770 fffff800`031d13c3 : 00000000`00000000 fffff800`02e63000 fffffa80`040103a0 fffff880`0af15801 : nt! ?? ::NNGAKEGL::`string'+0x472ad
fffff880`0af15800 fffff800`031d21e5 : 00000000`02e5b648 00000000`0004fe80 00000000`02e5b6a0 00000000`076666c8 : nt!ExpQuerySystemInformation+0x11c2
fffff880`0af15ba0 fffff800`02ed2993 : 00000000`00000000 00000000`03a37c60 fffffa80`04a91601 00000000`03e4e700 : nt!NtQuerySystemInformation+0x4d
fffff880`0af15be0 00000000`777800ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02e5b5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777800ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiIdentifyPfn+26f
fffff800`02f85b1f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiIdentifyPfn+26f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

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


2nd one:
Microsoft ® Windows Debugger Version 6.2.9200.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092712-30669-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Thu Sep 27 17:18:31.660 2012 (UTC + 8:00)
System Uptime: 0 days 0:43:15.206
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 240ed, 2, baec}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000240ed, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000000baec, 0

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


BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002f5b38c to fffff80002ecb740

STACK_TEXT:
fffff880`037166b8 fffff800`02f5b38c : 00000000`0000004e 00000000`00000099 00000000`000240ed 00000000`00000002 : nt!KeBugCheckEx
fffff880`037166c0 fffff800`02e7b51d : fffffa80`00bf2b00 00000000`00000001 00000000`0003fb90 fffff800`02ed99fd : nt!MiBadShareCount+0x4c
fffff880`03716700 fffff800`02edf59e : fffff800`03057e00 fffff880`03716950 00000000`00000000 00000000`0000000b : nt! ?? ::FNODOBFM::`string'+0x20403
fffff880`037168f0 fffff800`02f4da5e : fffff800`03057e00 fffff880`00000001 00000000`00000001 fffff880`03716b70 : nt!MiAgeWorkingSet+0x47e
fffff880`03716aa0 fffff800`02edfee2 : 00000000`00000a25 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`03716b40 fffff800`02ee0173 : 00000000`00000008 fffff880`03716bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03716b90 fffff800`0316fc06 : fffffa80`03fec9e0 00000000`00000080 fffffa80`03fbb380 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03716d00 fffff800`02ea9c26 : fffff880`009e8180 fffffa80`03fec9e0 fffff880`009f2fc0 fffff880`10170bcc : nt!PspSystemThreadStartup+0x5a
fffff880`03716d40 00000000`00000000 : fffff880`03717000 fffff880`03711000 fffff880`037166d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`02f5b38c cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiBadShareCount+4c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c

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

3rd one:
There's 1 more called memory management or something like that, but no minidump file for now, because these 3 take turn to happen, i need to wait til it happens again to get the minidump.

Please help, anyone

This post has been edited by TendouSouji: Sep 27 2012, 09:25 PM

Any BSOD professionals out there know what causes these BSODs? Tell me if you need additional infos. Thanks


Attached thumbnail(s)