View Single Post
21 Mar 2012  

Windows 7 Home Premium 64 Bit

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

Loading Dump File [D:\Kingston\BSODDmpFiles\skribbz14\032012-25630-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`04609000 PsLoadedModuleList = 0xfffff800`0484d650
Debug session time: Tue Mar 20 18:13:46.486 2012 (UTC - 6:00)
System Uptime: 1 days 0:37:07.931
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000009188, a420000000d8c025, fffff680000804f8}

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

Followup: MachineOwner

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

    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000009188
Arg3: a420000000d8c025
Arg4: fffff680000804f8

Debugging Details:

BUGCHECK_STR:  0x1a_403



PROCESS_NAME:  chrome.exe


LAST_CONTROL_TRANSFER:  from fffff8000462dc56 to fffff80004685d40

fffff880`09113678 fffff800`0462dc56 : 00000000`0000001a 00000000`00000403 fffff680`00009188 a4200000`00d8c025 : nt!KeBugCheckEx
fffff880`09113680 fffff800`046b7137 : 00000003`00000000 fffff680`00009188 fffffa80`04c794b0 a4200000`00d8c025 : nt! ?? ::FNODOBFM::`string'+0x3266c
fffff880`09113830 fffff800`046b8ae9 : 00000000`00000000 00000000`01231fff fffffa80`00000000 fffff800`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`091139f0 fffff800`0499bf91 : fffffa80`0749e600 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`09113b10 fffff800`0499c393 : 0000007f`00000000 00000000`01230000 fffffa80`00000001 00000000`0010ea01 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09113bd0 fffff800`04684fd3 : 00000000`00000001 00000000`02800100 fffffa80`04c794b0 00000000`003af130 : nt!NtUnmapViewOfSection+0x5f
fffff880`09113c20 00000000`77bd15ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010e0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bd15ba


nt! ?? ::FNODOBFM::`string'+3266c
fffff800`0462dc56 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3266c

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3266c

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3266c

Followup: MachineOwner
Possible causes are Memory problems... Drivers...

  • If you are overclocking any hardware, please stop.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
My System SpecsSystem Spec