locked
Windows 7 x64 BSOD RRS feed

  • Question

  • Hi,

    I'm having BSODs twice, once when playing Starcraft 2, and once when wating DVD using MPC-HC, the report from dump file is below

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


    Loading Dump File [C:\Windows\Minidump\082910-47533-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: .sympath SRV*e:\symbols*http://msdl.microsoft.com/download/symbols;SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`05819000 PsLoadedModuleList = 0xfffff800`05a56e50
    Debug session time: Sun Aug 29 14:16:13.935 2010 (UTC + 8:00)
    System Uptime: 0 days 1:33:47.776
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {41287, 8a57b, 0, 0}

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

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

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

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041287, The subtype of the bugcheck.
    Arg2: 000000000008a57b
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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


    BUGCHECK_STR:  0x1a_41287

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  mpc-hc64.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  fffff8800c04b800 -- (.trap 0xfffff8800c04b800)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fff0000000000000 rbx=0000000000000000 rcx=000000000008a533
    rdx=000fffffffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800058a7958 rsp=fffff8800c04b990 rbp=fffff68000064fa0
     r8=0000000000000004  r9=fffff68000064fa0 r10=0000058000000000
    r11=fffff8800c04bc20 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiInitializePfn+0xd8:
    fffff800`058a7958 488bc1          mov     rax,rcx
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80005835b7a to fffff80005889740

    STACK_TEXT: 
    fffff880`0c04b698 fffff800`05835b7a : 00000000`0000001a 00000000`00041287 00000000`0008a57b 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0c04b6a0 fffff800`0588782e : 00000000`00000000 00000000`00000001 00000000`00000700 fffff880`0450d774 : nt! ?? ::FNODOBFM::`string'+0x42ba5
    fffff880`0c04b800 fffff800`058a7958 : 00000000`00000000 00000000`0000002c 00000000`0000002c fffffa80`0a744b60 : nt!KiPageFault+0x16e
    fffff880`0c04b990 fffff800`058a6f4f : fffff680`00064fa0 fffff880`0c04ba40 00000000`00001000 fffffa80`0a217b18 : nt!MiInitializePfn+0xd8
    fffff880`0c04b9d0 fffff800`058a39c6 : 00000000`00000001 00000000`0c9f4000 fffff880`0c04bc20 fffff680`00064fa0 : nt!MiResolveDemandZeroFault+0x1ff
    fffff880`0c04bac0 fffff800`0588782e : 00000000`00000001 00000000`09830000 00000000`0c9f3f01 00000000`00000001 : nt!MmAccessFault+0x5c6
    fffff880`0c04bc20 00000000`77b11995 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0dcaf058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b11995


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+42ba5
    fffff800`05835b7a cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

    FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

    BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

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

    Would appreciate if anyone could hlep and point me to the right direction (who to seek help, ie hw manufacturer?)

    Thanks,

     

    david

    • Moved by Ronnie VernonMVP Sunday, August 29, 2010 12:46 PM Focus (From:Windows 7 Miscellaneous)
    Sunday, August 29, 2010 7:10 AM

Answers

All replies

  •  I'd start by checking memory using Windows Memory Diagnostic and
    memtest86+ (using a longer test, >5 hrs)
     
     
    Do both of the dumps that you have reference 1a : MEMORY_MANAGEMENT?
     
    More information on this error:
     
     

    -- Mike Burr
    • Marked as answer by Leo Huang Tuesday, August 31, 2010 1:36 AM
    Sunday, August 29, 2010 12:51 PM
  • Thanks Mike.

    Will run the test and report back.

    Cheers!

     

    --------------------------------------------------------------

    david

    Sunday, August 29, 2010 1:06 PM
  • Ok, there's no bad rams in my system.  The funny thing is that my 2.6ghz i7 was running at 3.32ghz, 166x20 instead of 133x20, my system was running at stock, only once when I booted and it says overclocking failed and bios was reset, but still it beats me as to how it was overclocked. 

    But anyway, everything is fine now, no more bsod.  And once again, thanks, Mike. 

     

    Cheers!

    david

    Monday, August 30, 2010 11:40 AM