Sporadic BSOD, Memory Managment/IRQL Related

[MichMAK2]

Pretty straight forward, my custom built Windows 7 Professional x64 rig has been BSOD crashing sporadically the past few weeks.

Using the BlueScreenView tool I see the BSODs tend to be Memory Management or IRQL_NOT_LESS_OR_EQUAL related. I assume this means I have a RAM or Video Driver issue, but if I knew what the problem was I would not be asking for help. I do not know where to begin troubleshooting, so hopefully someone with more expertise than I can show me the path forward.

Most of the BSODs have occurred while I have been playing World of Warships. There have been a few when I have not, including one failure while my PC idled overnight.

I cannot think of any recent changes, after about a dozen BSODs, I checked my video Drivers and updated them to the latest release. I installed a bunch of Windows updates that had accumulated. BSOD happened again tonight, so.... driver updates did not fix the issue. I ran Windows Memory Diagnostic and no errors were reported.

Please help.

 

[ICIT2LOL]

Hello and welcome Mich I have only just looked at the last dump and I think you need to do a memtest

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008886, The subtype of the bugcheck.
Arg2: fffffa8004aad050
Arg3: fffffa800f6f7050
Arg4: 0000000000000504
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_8886
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
CURRENT_IRQL:  2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff800030e9d8c to fffff800030d88c0
STACK_TEXT:  
fffff880`0afdd7e8 fffff800`030e9d8c : 00000000`0000001a 00000000`00008886 fffffa80`04aad050 fffffa80`0f6f7050 : nt!KeBugCheckEx
fffff880`0afdd7f0 fffff800`030f6466 : fffffa80`072a2840 00000000`00000050 00000000`00000008 fffff880`0afdda10 : nt!MiUnlinkPageFromLockedList+0x19c
fffff880`0afdd870 fffff800`030e5af9 : 00000000`00000000 00000000`12870000 00000000`0018e457 fffff800`00000000 : nt!MiDispatchFault+0x7a6
fffff880`0afdd980 fffff800`030d69ee : 00000000`00000001 00000000`12870000 00000000`00000901 00000000`01d61e00 : nt!MmAccessFault+0x359
fffff880`0afddae0 000007fe`f3068e71 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`12a29b50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f3068e71
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+19c
fffff800`030e9d8c cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+19c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  556356e8
IMAGE_VERSION:  6.1.7601.18869
IMAGE_NAME:  [COLOR=red]memory_corruption[/COLOR]
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c[/COLOR]
BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x1a_8886_nt!miunlinkpagefromlockedlist+19c
FAILURE_ID_HASH:  {fc253285-88ba-0bda-058c-156e3cc2cb8c}
Followup: MachineOwner
---------

Follow my ditty in your case it might be long and tedious

MEMTEST

The memtest you will need to make a bootable disk / stick andset the BIOS to boot from the optical or USBand it will take a fair time torun- some leave it overnight. see the attached document.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

But one thing is very important you must let the test run for at least 8passes any less and the findings are no good. Now if errors come upstraight away then you can stop it - see my pics. Now if there are errors andyou have more than one stick of RAM in then you will need to test each stick ieremove the sticks and replace stick 1 in slot 1 and test no errors do thesame in slot 2 with stick 1 no errors then repeat the process with stick 2 -that will show up the faulty stick - the other thing is it could be a faultyslot but most unusual. With more than two sticks the process is even longer asone may realize.

It is a very lengthy and tedious process but worth it if youhave errors.
Before you do that do this it could be just a matter of reseating the sticks an / or cleaning the contacts in both.

SLOT CLEANING

Now as for the slots toclean them use a strip of old credit card (or any card thin enough some arebetter than others ) about 1/2 inch wide nip the corners off one end - preferably round them offhold a piece of thin lint free cloth over theend dab on some form of alcohol - isopropyl alcohol (what we swab the skin withbefore an injection) is good and GENTLYswipe along the slots.

This can also be done for the GPU slot/s andalso the contacts of the sticks or cards - not the stick but some lint freecloth of course. See my pic for the sick but please be very gentle doing it ifyou are in any doubt - please ask before doing it but I use this all the timeand have yet to damage anything

 

[MichMAK2]

Thank you for the detailed reply, ICIT2LOL. I ran the MEMTEST overnight, as advised, and sure enough, there were multiple failures on the first pass. I am going to proceed this week with testing the individual ram sticks, I am not sure how long it will take to run the 8 passes on 1 unit, so I may have to spread the testing out over a few days.

Question: I noticed that my MEMTEST stopped after 1 pass last night. Is the default settings for the test to run continuously until I interrupt the test, or is the Default set to 1 pass and I need to change the settings?

 

[ICIT2LOL]

No mate the default is to keep on going and like I said it is VERY tedious and it may
not be the sticks either. But at least something has come out the try.