PFN List Corrupt BSoD

1 year 9 months...

Ah, an extended warranty.

Laptop issues are a little more difficult to debug if they are hardware related. I do not know if yours is hardware related, though. The best way to find out would be to restore to the factory image and see if you still have the same problems.

I restored it with Acer recovery but still having BSoDs.

Well, I got it again. When I was downloading game from Origin, it appeared

Problem Devices:

Code:

Broadcom 802.11n Network Adapter PCI \ VEN_14E4 & DEV_4358 & SUBSYS_E040105B & REV_00 \ 4 & 124A40C8 & 0 & 00E1 This device is disabled.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Kurama\Windows_NT6_BSOD_jcgriff2\030312-25802-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03093670
Debug session time: Fri Mar  2 17:05:48.456 2012 (UTC - 7:00)
System Uptime: 0 days 5:15:02.330
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 79788, 2, 7973f}

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: 0000000000079788, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000007973f, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Origin.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f53d7c to fffff80002ecac40

STACK_TEXT:  
fffff880`0b3a1628 fffff800`02f53d7c : 00000000`0000004e 00000000`00000099 00000000`00079788 00000000`00000002 : nt!KeBugCheckEx
fffff880`0b3a1630 fffff800`02e723ce : 00000000`00000000 fffff680`00078c60 00000000`00000000 00000000`00000801 : nt!MiBadShareCount+0x4c
fffff880`0b3a1670 fffff800`02efcbb7 : 00000000`00000000 fffff680`00078ff8 fffffa80`07857420 fffffa80`07857601 : nt! ?? ::FNODOBFM::`string'+0x33094
fffff880`0b3a1820 fffff800`02eb80ff : fffffa80`00000000 00000000`0f83ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0b3a19e0 fffff800`02ec9ed3 : ffffffff`ffffffff 00000000`03afe3b0 00000000`03afe3a8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0b3a1ae0 00000000`777414fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03afe378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777414fa


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

This is looking more and more like a hardware issue. I do not see anything in your drivers that looks suspicious, and if I were to guess which hardware, I would say either the RAM or the graphics card RAM is causing the problem. Did you ever run the graphics tests I gave in the last step of post #2?

Yeah but I've run Furmark for 15 minutes. I will run it more than 15 minutes.

Well, I can say that GPU becomes very hot when I play game etc.

It can be onboard GPU of Intel because BSoD happens randomly. And I won't be surprised if it is because of RAM

What temperature does the GPU get to?

Well, I saw 99 degree without cooler. (It can be more according to the situation) With cooler, it's around 80s.

Have you checked for dust build-up on the GPU or in the graphics card cooling fan? These can get VERY dusty after a long time of use.

Well, there is a little fan under the laptop. It is dusty but I can't do anything for now.

Alright, let us know when you are able to clean the dust out.

To remove dust, follow the subsequent general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
8. Start the computer and see if performance is better.