Randomly Getting A BSOD

[soulgoodguy]

Hi Guys, I'm suddenly getting some random BSODs can you please help

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 13321

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC000001D
BCP2: 00000000002AD942
BCP3: 0000000000000002
BCP4: 0000000FFFFFFF00
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110613-32916-01.dmp
C:\Users\soulgoodguy\AppData\Local\Temp\WER-157498-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

UPdated: I have included the dmp file.

 

[koolkat77]

MSINFO32:

• Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter> Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
  

  • Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

• Virus Check:
  • Make scans with these tools below:
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  • Reduce the start-up items. This will help avoid software conflicts:
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7
• System File Checker
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    • Link to full tutorial: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
• Run Disk Check in Windows 7
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
    • Link to full tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html
• Test and Diagnose RAM issues with MEMTEST86+
  • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
    • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Check for heating issues using Speccy or HWmonitor
  • HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
  • Speccy - System Information - Free Download
    • Please upload a summary tab using Speccy. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html
• Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
  • Then test your Hard Drives (s) running a Hard Drive Diag.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, 2ad942, 2, fffffff00}

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

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: 00000000002ad942, The address that the exception occurred at
Arg3: 0000000000000002, Parameter 0 of the exception
Arg4: 0000000fffffff00, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+0
00000000`002ad942 ??              ???

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003323738 to fffff800032d8bc0

FAILED_INSTRUCTION_ADDRESS: 
+0
00000000`002ad942 ??              ???

STACK_TEXT:  
fffff880`0a2b8f08 fffff800`03323738 : 00000000`0000001e ffffffff`c000001d 00000000`002ad942 00000000`00000002 : nt!KeBugCheckEx
fffff880`0a2b8f10 fffff800`032d8242 : fffff880`0a2b96e8 00000000`a14da121 fffff880`0a2b9790 fffffa80`01ee74e0 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0a2b95b0 fffff800`032d639f : fffff880`0a2b9790 fffff800`0348ab02 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a2b9790 00000000`002ad942 : fffff800`032e964c fffff880`0a2b93d0 00000000`002ad8a0 00000000`002ad880 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0a2b9928 fffff800`032e964c : fffff880`0a2b93d0 00000000`002ad8a0 00000000`002ad880 00000000`002ad3b0 : 0x2ad942
fffff880`0a2b9930 fffff800`032f54f3 : 00000000`000a4d1a 00000000`77a28e40 fffff680`003bd140 fffffa80`05fdc628 : nt!MiUnlinkPageFromLockedList+0x3ec
fffff880`0a2b99b0 fffff800`032e5179 : 00000000`00000000 00000000`77a28e40 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0a2b9ac0 fffff800`032d6cee : 00000000`00000000 00000000`77a28e40 00000000`fffdb001 00000000`002ade90 : nt!MmAccessFault+0x359
fffff880`0a2b9c20 00000000`77a28e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0011e1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a28e40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+487ed
fffff800`03323738 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+487ed

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!_??_::FNODOBFM::_string_+487ed

BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!_??_::FNODOBFM::_string_+487ed

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

 

[soulgoodguy]

Thanks! I'll post the results when I am done ASAP!