BSOD several times daily

[mbaram]

I am having BSOD several times a day. All the tools i used suggested driver issue. Reinstalled OS several times, little difference.
Please Help!

 

[koolkat77]

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


Loading Dump File [C:\Users\Yusra\Downloads\debug-MOISHA-Sun_03_16_2014__73952_44\031614-26208-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e456d0
Debug session time: Sun Mar 16 14:45:58.146 2014 (UTC + 6:00)
System Uptime: 0 days 4:27:44.596
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, fffff7063fbfa001, 133906, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: fffff7063fbfa001
Arg3: 0000000000133906
Arg4: fffff70001080000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  winlogon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cce727 to fffff80002c77bc0

STACK_TEXT:  
fffff880`0a4d4808 fffff800`02cce727 : 00000000`0000001a 00000000`00041284 fffff706`3fbfa001 00000000`00133906 : nt!KeBugCheckEx
fffff880`0a4d4810 fffff800`02c911f9 : fffffa80`12cc7bc8 fffff6fb`831fdfd0 00000000`00000015 00000000`00000015 : nt! ?? ::FNODOBFM::`string'+0x4ad3
fffff880`0a4d4850 fffff800`02cab144 : fffffa80`05a2d120 00000000`00000003 fffff6fb`831fdfd0 fffff706`3fbfa000 : nt!MiTerminateWsle+0x29
fffff880`0a4d4890 fffff800`02cab3f8 : 00000000`00000003 00000000`00000015 80000001`e0f06863 00000000`0000001c : nt!MiDeleteValidSystemPte+0x1a4
fffff880`0a4d4990 fffff800`02c47c44 : fffffa80`12cc7bc8 00000000`00000001 00000000`00000000 fffffa80`0000001c : nt!MiDeletePteRange+0x291
fffff880`0a4d4a10 fffff800`02c4889e : 00000000`00000001 fffffa80`12cc7830 fffffa80`12cc7830 00000000`00000001 : nt!MiDeleteAllHashMappings+0xe4
fffff880`0a4d4a50 fffff800`02f4c15a : fffff8a0`11448060 00000000`00000001 00000000`00000000 fffffa80`12b32060 : nt!MmCleanProcessAddressSpace+0xa2
fffff880`0a4d4aa0 fffff800`02f306b8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`0a4d4ba0 fffff800`02c76e53 : fffffa80`12cc7830 fffff880`00000000 fffffa80`12b32060 00000000`00000000 : nt!NtTerminateProcess+0x138
fffff880`0a4d4c20 00000000`7770157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ef9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7770157a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4ad3
fffff800`02cce727 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ad3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.