I hear this is the place to go for BSOD help...

[jpmattis]

Hey All,

I just got a BSOD and I was hoping someone here might be able to help me troubleshoot it. I attached the dump file.

Also, I have recently tested my RAM with Memtest86+ and it is good so bad RAM isn't the issue.

I'm using Win 7 64-Bit.

Thanks for taking a look amd here is what Windows Debugger said:

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

Loading Dump File [C:\Windows\Minidump\042410-20343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e50
Debug session time: Sat Apr 24 12:02:01.342 2010 (UTC - 7:00)
System Uptime: 0 days 14:38:20.514
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5003, fffff70001080000, 5038, d8fdc09}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29771 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000005038
Arg4: 000000000d8fdc09
Debugging Details:
------------------

BUGCHECK_STR: 0x1a_5003
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002b3a5fc to fffff80002acb600
STACK_TEXT:
fffff880`08025878 fffff800`02b3a5fc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00005038 : nt!KeBugCheckEx
fffff880`08025880 fffff800`02af1a53 : 62500000`5eaa9025 00000000`28095121 fffff880`08025a10 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29771
fffff880`08025910 fffff800`02ae749e : 00000000`00000000 00000000`04ee4428 fffff680`00027720 fffffa80`06eea3f8 : nt!MiResolveProtoPteFault+0x1d3
fffff880`080259b0 fffff800`02ae5623 : 00000000`00000000 00000000`04ee4428 00000000`00000000 fffff800`00000000 : nt!MiDispatchFault+0x1de
fffff880`08025ac0 fffff800`02ac96ee : 00000000`00000000 00000000`0000000e 00000000`04d4e501 00000000`00000020 : nt!MmAccessFault+0x343
fffff880`08025c20 00000000`77445ce4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`04d4e310 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77445ce4

STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+29771
fffff800`02b3a5fc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+29771
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29771
BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29771
Followup: MachineOwner
---------

 

[usasma]

Not much information available from the single memory dump file (if you have more, please upload them all). It's a STOP 0x1A error that blames ntkrnlmp.exe. Ntkrnlmp.exe is the kernel (core) of the operating system. If it was to blame there would be many more problems than the occasional BSOD.

How recently did you use Memtest? If it wasn't after the STOP error occurred - please run it again.
Also, please try this free, bootable hard drive diagnostic: HD Diagnostic (read the details at the link)

So, let's try Driver Verifier for starters. Please follow these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 24 15:02:01.342 2010 (GMT-4)
System Uptime: 0 days 14:38:20.514
BugCheck 1A, {5003, fffff70001080000, 5038, d8fdc09}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29771 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  explorer.exe