Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD at seemingly random times

25 Jun 2014   #1

Windows 7 64 bit
BSOD at seemingly random times

I have been encountering a BSOD at random times, there are times when I play several games, such as everquest, warframe, borderlands 2 (not all at once) that it will BSOD on me, but also during idle times, no programs open etc. I am uploading the dump files. Any help would be appreciated.

Also, I forgot to mention, that sometimes it will crash within 5 minutes, and other times it wont crash for days at a time.

Managed to read it, said it was caused by memory management

Driver IRQL Not less or equal

My System SpecsSystem Spec
27 Jun 2014   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Welcome to the forum.

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

Loading Dump File [C:\Users\Yusra\Downloads\Compressed\AVA-403902-1-Wed_06_25_2014_195404_21\062514-11138-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03e15000 PsLoadedModuleList = 0xfffff800`040586d0
Debug session time: Thu Jun 26 05:37:42.308 2014 (UTC + 6:00)
System Uptime: 0 days 9:35:19.136
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff680007fc400, 48d0000142b0a025, fffffa800b974110}

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

Followup: MachineOwner

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

    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff680007fc400
Arg3: 48d0000142b0a025
Arg4: fffffa800b974110

Debugging Details:

BUGCHECK_STR:  0x1a_41201



PROCESS_NAME:  SearchProtocol


LAST_CONTROL_TRANSFER:  from fffff80003ee69fe to fffff80003e8abc0

fffff880`155d7878 fffff800`03ee69fe : 00000000`0000001a 00000000`00041201 fffff680`007fc400 48d00001`42b0a025 : nt!KeBugCheckEx
fffff880`155d7880 fffff800`03e55b71 : 00000000`00000000 fffffa80`0ec55b50 00000000`00000000 48d00001`42b0a025 : nt! ?? ::FNODOBFM::`string'+0x13702
fffff880`155d78c0 fffff800`03e5580a : fffffa80`0b974110 fffffa80`0c520b30 fffffa80`0c520b30 00000000`ff880000 : nt!MiQueryAddressState+0x2b1
fffff880`155d7910 fffff800`04163d74 : fffff880`00000020 00000000`ff881000 fffffa80`0b974110 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`155d7980 fffff800`03e89e53 : 00000000`00000170 fffffa80`0ec55b50 fffff880`155d7a88 00000000`0018ac98 : nt!NtQueryVirtualMemory+0x382
fffff880`155d7a70 00000000`77bf14ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018ac78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bf14ea


nt! ?? ::FNODOBFM::`string'+13702
fffff800`03ee69fe cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13702

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702

Followup: MachineOwner
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
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   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
27 Jun 2014   #3

Windows 7 Enterprsie 64 bit

I too get such error. pfa dump file

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 2057
Extra information about the problem
BCCode: 1000009f
BCP1: 0000000000000004
BCP2: 0000000000000258
BCP3: FFFFFA800733D040
BCP4: FFFFF800053FF3D0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
My System SpecsSystem Spec

29 Jun 2014   #4

Windows 7 64 bit

Ran through 10 passes, no errors were found.
My System SpecsSystem Spec
29 Jun 2014   #5

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Any new BSOD's?
My System SpecsSystem Spec
30 Jun 2014   #6

Windows 7 64 bit

Just happened overnight
My System SpecsSystem Spec
30 Jun 2014   #7

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Upload new logs.
My System SpecsSystem Spec
30 Jun 2014   #8

Windows 7 64 bit

Newest log
My System SpecsSystem Spec
01 Jul 2014   #9

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Sorry about the delay.

Enable Driver Verifier to see if it catches any misbehaving driver:
My System SpecsSystem Spec
02 Jul 2014   #10


BugCheck A, {1, 2, 1, fffff80003eee437}
A pointer to an invalid address, more specifically an IP misalignment.

The problem is that a function was made to unlink a certain page of memory from a locked list, it's an undocumented function so I don't know too much about it, looks like a singly linked list.

I decided to look at the unloaded modules and Norton anti virus was loaded and unloaded twice.

Unloaded modules:
fffff880`0d806000 fffff880`0d828000   ENG64.SYS
fffff880`0d600000 fffff880`0d806000   EX64.SYS
fffff880`0d822000 fffff880`0d844000   ENG64.SYS
fffff880`0d61c000 fffff880`0d822000   EX64.SYS
My bet is that Norton was the cause for the misaligned Instruction Pointer.

Use Norton's removal tool then replace it with MSE.
My System SpecsSystem Spec

 BSOD at seemingly random times

Thread Tools

Similar help and support threads
Thread Forum
BSOD seemingly random times
hi, was just wondering if any of you could help me looking into this. I had to disable windows automatic updates yesterday as it was hogging my resources and kept failing but still getting BSOD Many thanks aza237
BSOD Help and Support
BSOD at seemingly random times.
Hi all, I've been getting BSOD crashes at apparently random times with no apparent cause. Sometimes it occurs while gaming, sometimes while browsing the web, and sometimes when the PC is sitting idle. DRIVER_POWER_STATE_FAILURE is the usual error code, but I've also had KERNAL_DATA_INPAGE_ERROR a...
BSOD Help and Support
BSOD at seemingly random times
A few months ago, I received a computer secondhand, so I wiped it and installed Windows 7. Now it occasionally BSODs at random times. Sometimes it is when I have already been using the computer for some time, and sometimes it is before Windows is able to fully start up. I cannot discern a...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
BSOD at seemingly random times
Hello, I am new to this forum and I hope you can help me with this. This BSOD has been occuring since a month ago and its been getting more and more frequent. Here's the info: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601. Locale ID: 1033 ...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 22:49.
Twitter Facebook Google+