BSOD again.. Minidump file check?

Page 1 of 3 123 LastLast

  1. Posts : 72
    Windows 7 64-bit
       #1

    BSOD again.. Minidump file check?


    Hello! Once again I got BSOD during boot on desktop. Now when I'm putting minidump to a .zip it says that I can't do that What??? It says "Access denied" whatever I do with that file. I really want to archive it and send here for professionals analyze
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    WIGILOCO said:
    Hello! Once again I got BSOD during boot on desktop. Now when I'm putting minidump to a .zip it says that I can't do that What??? It says "Access denied" whatever I do with that file. I really want to archive it and send here for professionals analyze

    try dragging it to your desktop then zip it
      My Computer


  3. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #3

    Yeah that helped man! Now here is the minidump, would some pro analyze it for me, please? :) I'm getting really frustrated with those bsod on my new computer..
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    WIGILOCO said:
    Yeah that helped man! Now here is the minidump, would some pro analyze it for me, please? :) I'm getting really frustrated with those bsod on my new computer..



    Hi and welcome

    this crash qas caused by fltmgr.sys which is the fille manager in win 7

    I would run a system file check
    Type cmd in search>right click and run as admin>sfc /scannow

    If you are overclocking stop.

    Let us know the results

    Ken





    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\020210-25708-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50
    Debug session time: Tue Feb  2 13:03:35.363 2010 (GMT-5)
    System Uptime: 0 days 0:00:46.659
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff8800109711e, fffff88006647ca0, 0}
    
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::NNGAKEGL::`string'+1087 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8800109711e, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88006647ca0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    fltmgr! ?? ::NNGAKEGL::`string'+1087
    fffff880`0109711e 0fb74818        movzx   ecx,word ptr [rax+18h]
    
    CONTEXT:  fffff88006647ca0 -- (.cxr 0xfffff88006647ca0)
    rax=bffffa8005c9d650 rbx=fffff8a006f76888 rcx=0000000000000000
    rdx=fffffa8004dcc310 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800109711e rsp=fffff88006648680 rbp=fffff8800106d000
     r8=ffffffffffffffff  r9=fffff88006648648 r10=000000000000016e
    r11=fffff8a006f76888 r12=fffffa8004dcc310 r13=0000000000000000
    r14=0000000000000000 r15=fffff88006648850
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    fltmgr! ?? ::NNGAKEGL::`string'+0x1087:
    fffff880`0109711e 0fb74818        movzx   ecx,word ptr [rax+18h] ds:002b:bffffa80`05c9d668=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  csc.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800109711e
    
    STACK_TEXT:  
    fffff880`06648680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1087
    
    
    FOLLOWUP_IP: 
    fltmgr! ?? ::NNGAKEGL::`string'+1087
    fffff880`0109711e 0fb74818        movzx   ecx,word ptr [rax+18h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  fltmgr! ?? ::NNGAKEGL::`string'+1087
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: fltmgr
    
    IMAGE_NAME:  fltmgr.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11f
    
    STACK_COMMAND:  .cxr 0xfffff88006647ca0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::NNGAKEGL::_string_+1087
    
    BUCKET_ID:  X64_0x3B_fltmgr!_??_::NNGAKEGL::_string_+1087
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #5

    Thanks a lot! I have only 1600MHz ddr3 with my mobo and mobo keeped it normally at 1333MHz and I raised It to 1600Mhz because the memory I bought is 1600Mhz. I have the correct bios settings, checked and asked from g.skill support team And prime95 no erros. So I scannow and tell results! Thanks man a lot!
      My Computer


  6. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #6

    It didn't find anything wrong.. what should I do now? :O
      My Computer


  7. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #7

    Someone help please! =)
      My Computer


  8. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #8

    WIGILOCO said:
    Someone help please! =)
    Run the Memory Diagnostic & HD Diagnostic see whether you finding some issues post us the result

    Good Luck,
    Captain
      My Computer


  9. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #9

    I ran the chkdsk without the /r thing. It didn't find anything i think. Should I ran it again with /r parameter?
      My Computer


  10. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #10

    WIGILOCO said:
    I ran the chkdsk without the /r thing. It didn't find anything i think. Should I ran it again with /r parameter?
    Yup.. Also download the Diag Tool and run it :)
      My Computer


 
Page 1 of 3 123 LastLast

  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 19:00.
Find Us