BSOD - Minidump help requested


  1. Posts : 20
    Win 7 HP 64-bit
       #1

    BSOD - Minidump help requested


    Many thanks in advance for this.

    Experienced my first BSOD today on a new machine. See specs for details.

    Single hardware change made since purchase was swapping the supplied drive for a Velociraptor 320GB 10K. No previous issues until today.

    Only significant system action taken yesterday was installation of MagicISO.

    Circumstances/action:

    • Boot - BSOD after Windows Logo - PAGE FAULT IN NON PAGED AREA
    • Rebooted into Windows normally (after prompting)

    Obviously not urgent but am uncomfortable letting these things pass on such a new machine...

    Appreciate the help.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Welcome!

    It appears as if Acronis is causing the problem. Try uninstalling it, and see if the problem happens again. Or you could just leave it alone, and if it happens again, remove Acronis.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\Desktop\021010-20498-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\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 Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50
    Debug session time: Wed Feb 10 04:13:27.798 2010 (GMT-5)
    System Uptime: 0 days 0:00:29.922
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffffffffffffe9, 0, fffff80003157fb9, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\tdrpm251.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for tdrpm251.sys
    *** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys
    
    Could not read faulting driver name
    Probably caused by : tdrpm251.sys ( tdrpm251+4c0c8 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffffffffffffe9, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80003157fb9, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ab0e0
     ffffffffffffffe9 
    
    FAULTING_IP: 
    nt!ObpQueryNameString+51
    fffff800`03157fb9 410fb64718      movzx   eax,byte ptr [r15+18h]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88002aeaf90 -- (.trap 0xfffff88002aeaf90)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88002aeb218 rbx=0000000000000000 rcx=0000000000000001
    rdx=fffffa80089e43f0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003157fb9 rsp=fffff88002aeb120 rbp=0000000000000001
     r8=0000000000000080  r9=fffff88002aeb280 r10=fffff80003002888
    r11=fffff88001c843c0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!ObpQueryNameString+0x51:
    fffff800`03157fb9 410fb64718      movzx   eax,byte ptr [r15+18h] ds:15ac:00000000`00000018=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ef41e4 to fffff80002e74f00
    
    STACK_TEXT:  
    fffff880`02aeae28 fffff800`02ef41e4 : 00000000`00000050 ffffffff`ffffffe9 00000000`00000000 fffff880`02aeaf90 : nt!KeBugCheckEx
    fffff880`02aeae30 fffff800`02e72fee : 00000000`00000000 00000000`00000000 fffffa80`03cd0000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
    fffff880`02aeaf90 fffff800`03157fb9 : fffffa80`0876ec20 fffffa80`0896675b 00000000`00000000 fffff800`02fa74d3 : nt!KiPageFault+0x16e
    fffff880`02aeb120 fffff800`031590ba : 00000000`00000001 fffffa80`089e43f0 fffffa80`00000080 fffff880`02aeb280 : nt!ObpQueryNameString+0x51
    fffff880`02aeb220 fffff880`01cc90c8 : fffff880`00000009 00000000`00000001 00000000`00000001 00000000`00000000 : nt!ObQueryNameString+0xe
    fffff880`02aeb260 fffff880`00000009 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000080 : tdrpm251+0x4c0c8
    fffff880`02aeb268 00000000`00000001 : 00000000`00000001 00000000`00000000 00000000`00000080 fffff880`02aeb380 : 0xfffff880`00000009
    fffff880`02aeb270 00000000`00000001 : 00000000`00000000 00000000`00000080 fffff880`02aeb380 fffffa80`0876eba0 : 0x1
    fffff880`02aeb278 00000000`00000000 : 00000000`00000080 fffff880`02aeb380 fffffa80`0876eba0 fffff880`01cd0a0b : 0x1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tdrpm251+4c0c8
    fffff880`01cc90c8 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  tdrpm251+4c0c8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tdrpm251
    
    IMAGE_NAME:  tdrpm251.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a72f8d9
    
    FAILURE_BUCKET_ID:  X64_0x50_tdrpm251+4c0c8
    
    BUCKET_ID:  X64_0x50_tdrpm251+4c0c8
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 20
    Win 7 HP 64-bit
    Thread Starter
       #3

    Many many thanks for that! really appreciate it.

    Will follow your advice. I've only got acronis on there as Home Premium doesn't allow back up to network drives (which is what I need!). Gah; I knew there would be a catch to HP but should have checked more carefully.

    Many thanks again.
      My Computer


  4. Posts : 20
    Win 7 HP 64-bit
    Thread Starter
       #4

    Ah... looks like Acronis and Win 7 are not playing nicely for lots of people.

    Conclusion: Goodbye Acronis and back to looking for a decent auto-backups solution.

    thanks again. Mind at rest.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:41.
Find Us