Regular BSODs

[DanieleinaD]

Hello

I am getting a lot of BSOD's and would like someone with expertise to look at it for me.

Hope someone can help.

Thanks.

 

[koolkat77]

WElcome to the forum.

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

Memtest should be done overnight.

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


Loading Dump File [C:\Users\USER\Downloads\Compressed\HAL9000-29-11-2014__61422,01\112514-8346-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03008000 PsLoadedModuleList = 0xfffff800`0324b890
Debug session time: Tue Nov 25 08:30:47.702 2014 (UTC + 6:00)
System Uptime: 0 days 5:10:19.483
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 50012f, 2, 50012b}

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

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

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

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  FarCry4.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000310ca4c to fffff8000307dbc0

STACK_TEXT:  
fffff880`08219118 fffff800`0310ca4c : 00000000`0000004e 00000000`00000099 00000000`0050012f 00000000`00000002 : nt!KeBugCheckEx
fffff880`08219120 fffff800`030e84c8 : 00000000`0987f000 fffffa80`0f0938a0 00000000`00000000 fffff880`082193e8 : nt!MiBadShareCount+0x4c
fffff880`08219160 fffff800`033905ed : fffff980`2a8c0000 fffff8a0`0b49be60 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2ba87
fffff880`08219440 fffff800`030a067b : 00000000`09840000 fffffa80`18c04130 00000000`00000000 00000000`09900000 : nt!CcUnmapVacb+0x5d
fffff880`08219480 fffff800`03093039 : fffff980`00000001 00000000`09100000 fffffa80`1d941010 fffffa80`18809440 : nt!CcUnmapVacbArray+0x1bb
fffff880`08219510 fffff800`03367fb2 : 00000000`00000000 00000000`09900000 fffff880`082195e0 fffff880`08219670 : nt!CcGetVirtualAddress+0x38a
fffff880`082195a0 fffff880`012d801f : fffff880`00000000 00000000`00000005 fffffa80`00040000 fffffa80`190a0e01 : nt!CcCopyRead+0x132
fffff880`08219660 fffff880`01001098 : fffffa80`190a0e60 fffffa80`1d8ef728 00000000`00100081 fffffa80`190a0e01 : Ntfs!NtfsCopyReadA+0x18f
fffff880`08219840 fffff880`010048ba : fffff880`08219910 000007ff`f7d30003 000007ff`f7d30000 fffffa80`190a0e00 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`082198a0 fffff880`01022630 : fffffa80`190a0e60 00000000`00000000 fffff880`08219a00 00000000`000ccaa0 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`082198e0 fffff800`03367b39 : fffffa80`190a0e60 fffff880`00000001 fffffa80`1888c080 fffffa80`190a0e60 : fltmgr!FltpFastIoRead+0x1d0
fffff880`08219980 fffff800`0307ce53 : ffffffff`00000004 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
fffff880`08219a70 00000000`7776131a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1642f718 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7776131a


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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