BSOD Random Occurrences(4E, 1A are main error codes)

You're welcome. Let us know how things go with the integrated graphics. Hopefully it will help to narrow down the cause with the system running with the simplest/minimal hardware and then adding things back one at a time.

Okay I got a BSOD and I forgot I had two RAM sticks in(my bad). I'll attach the minidump anyways. Now I have one stick in and we will go from there.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Xed\Minidump\Minidump.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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`03254650
Debug session time: Thu Apr 12 21:20:21.537 2012 (UTC - 6:00)
System Uptime: 0 days 2:01:12.349
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1868d1, 2, 1868be}

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

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

3: 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: 00000000001868d1, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000001868be, 0

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


BUGCHECK_STR:  0x4E_99

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  msseces.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000311510c to fffff8000308cc80

STACK_TEXT:  
fffff880`063cce18 fffff800`0311510c : 00000000`0000004e 00000000`00000099 00000000`001868d1 00000000`00000002 : nt!KeBugCheckEx
fffff880`063cce20 fffff800`03034f39 : 00000000`00000000 fffff680`00001810 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`063cce60 fffff800`0305c873 : fffffa80`0c137630 fffff700`00000ddc 0000007f`fffffff8 fffff8a0`01425170 : nt! ?? ::FNODOBFM::`string'+0x32971
fffff880`063ccef0 fffff800`0305d942 : fffffa80`0c137630 fffffa80`00000000 fffff8a0`00000458 fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`063cd7a0 fffff800`0336187a : fffff8a0`0761d060 fffff880`063cdae0 00000000`00000000 fffffa80`0c2a0b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`063cd7f0 fffff800`03344d5d : 00000000`40010004 80000001`a823b801 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`063cd8f0 fffff800`0307f7da : 00000000`002ad048 fffffa80`0c2a0b60 ffffffff`ffffffff 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`063cd920 fffff800`0307fb20 : 00000000`0033e5e0 fffff880`063cd9a0 fffff800`03344cc8 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`063cd9a0 fffff800`0308aef4 : 00000000`00000000 00000000`002ad048 00000000`00000001 00000000`0033e5e0 : nt!KiInitiateUserApc+0x70
fffff880`063cdae0 00000000`76f8bedc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x2b4
00000000`0020f960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f8bedc


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Proceed with one RAM module at a time. The crash is pointing to possible driver issues or memory problems...

Okay. After leaving one RAM module in for about two days and no BSOD(Even when downloading two huge files) I assumed this RAM must be good. So this morning I switched them out and surly enough not even ten minutes after boot up, BSOD. I did get a different error than usual; but, still a BSOD occurred. I'm going to attach the minidump file still in hopes it points to memory corruption. Waiting for your reply. Hopefully this solves my BSOD problems.

Okay thanks for your help usasma and writhziden for finally finding the issue causing my BSODs. And another question. Since I can hopefully assume that the RAM stick is bad. When I put back in my graphics card should I delete the Intel vga drivers and then install my Nvidia drivers. Or does it not matter that I have them installed. And finally...Again thank you both for the help for finding the issue for BSODs.

You may need to disable or uninstall the Intel graphics drivers, but I have also seen systems that ran fine with Intel graphics and NVIDIA or ATI installed. You will have to see whether they cause conflicts and make a decision from there.

Okay I'll try that. Thanks for help with the BSOD. I'm going to keep this forum open until I have finally replace my RAM to ensure final system stability. And again, thank you.

You're welcome. We'll be subscribed to the thread, so post back whenever you have the new RAM.

Okay, the finale(hopefully). Got new RAM and so far no issues whatsoever. Only problems I had at one point was random artifacts that was quickly resolved after removal of the Intel graphics drivers. And to finish things on what would seem a good note. I installed the AI suite from ASUS which got rid of the PCI simple controller not having any drivers for it. Thank you writhziden and usasma for help your great help over the past 3 weeks to help resolve my BSODs. It's awesome to have a PC that is more stable. And good luck helping other people to debug whats wrong with their PC. :)