Blue screen errors - About 3-4 times a day

[skathari]

Hi, this is one of the blue screen details that just happened a few moments ago. I will post more when it happens again.

Does anyone have any idea on what is causing this?

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041284
BCP2: 0000000001A08001
BCP3: 0000000000000000
BCP4: FFFFF70001080000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\032213-16754-01.dmp
C:\Users\Nikolas - torrents\AppData\Local\Temp\WER-31231-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[skathari]

Here is the attachment

View attachment 262460

 

[Arc]

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.


If memtest comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

----------------------------------------------------------
BSOD ANALYSIS

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff6800005b1f8, 1, fffffa8009c6adc0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6800005b1f8
Arg3: 0000000000000001
Arg4: fffffa8009c6adc0

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f2cabe to fffff80002ed0c40

STACK_TEXT:  
fffff880`0a2f8878 fffff800`02f2cabe : 00000000`0000001a 00000000`00041201 fffff680`0005b1f8 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a2f8880 fffff800`02e9bb91 : fffffa80`0261c0c0 fffff880`00961000 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x13702
fffff880`0a2f88c0 fffff800`02e9b7f3 : fffffa80`09c6adc0 fffffa80`06c1e640 fffffa80`06c1e640 00000000`0b63f000 : nt!MiQueryAddressState+0x2b1
fffff880`0a2f8910 fffff800`031adc74 : 00000000`00000000 00000000`0b640000 fffffa80`09c6adc0 00000000`00000000 : nt!MiQueryAddressSpan+0x73
fffff880`0a2f8980 fffff800`02ecfed3 : ffffffff`ffffffff fffffa80`0f205060 00000000`01b2d5d8 00000000`01b2d428 : nt!NtQueryVirtualMemory+0x382
fffff880`0a2f8a70 00000000`7770154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b2d408 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7770154a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13702
fffff800`02f2cabe cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

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

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

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