locked
Win 7 64 bit kept blue screen... RRS feed

  • Question

  • Can any expert help to analyze the minidump files?

    My system is a new i5-750 on Asus P7P55D, 8GB 1333Mhz ram and 2 x Seagate 1TB disk on Raid 1. However, it runs far slower and unstable than my 4yr old E6600 which just decommissioned 2 weeks ago due to mobo failure...

    Had the IDE DVD-R/W detached, and updated with Intel latest RST drivers, but problem persists...

    Minidump:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005, fffff80002acaf6e, fffff8800372c7d8, fffff8800372c040}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ADDITIONAL_DEBUG_TEXT: 
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80002a57000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt+73f6e
    fffff800`02acaf6e 4d895cc3f0      mov     qword ptr [r11+rax*8-10h],r11

    EXCEPTION_RECORD:  fffff8800372c7d8 -- (.exr 0xfffff8800372c7d8)
    ExceptionAddress: fffff80002acaf6e (nt+0x0000000000073f6e)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff8800372c040 -- (.cxr 0xfffff8800372c040)
    rax=f3e78721e14b5804 rbx=fffffa8006cec458 rcx=fffffa8006cec4d0
    rdx=fffff8800372cd10 rsi=fffffa8006cec350 rdi=0000000000000000
    rip=fffff80002acaf6e rsp=fffff8800372ca10 rbp=5351413050373956
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000002
    r11=fffffa8006cec458 r12=2020202020202020 r13=fffff8800372cd00
    r14=fffff88003164180 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
    nt+0x73f6e:
    fffff800`02acaf6e 4d895cc3f0      mov     qword ptr [r11+rax*8-10h],r11 ds:002b:9f3c338f`11298468=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x7E

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002acaf6e

    STACK_TEXT: 
    fffff880`0372ca10 00000000`00000000 : fffff880`0372ca80 0010c837`3fff0c5a 0000003f`00000000 20202020`00000000 : nt+0x73f6e


    FOLLOWUP_IP:
    nt+73f6e
    fffff800`02acaf6e 4d895cc3f0      mov     qword ptr [r11+rax*8-10h],r11

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt+73f6e

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntoskrnl.exe

    STACK_COMMAND:  .cxr 0xfffff8800372c040 ; kb

    BUCKET_ID:  WRONG_SYMBOLS

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

     

    Thursday, July 22, 2010 4:06 PM

Answers

  • EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    You should check your RAM for errors.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, July 22, 2010 10:30 PM
  • Hi,

     

    You may run the Memory Diagnostics Tool or a third party tool, Mentest86+ to check the memory.

     

    Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    In addition, I also would like to suggest you update the BIOS and the hardware drivers for Windows 7 to improve the stability.

     

    If the issue persists, please upload more minidump files for our further research.

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, July 26, 2010 6:41 AM

All replies

  • EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    You should check your RAM for errors.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, July 22, 2010 10:30 PM
  • Hi,

     

    You may run the Memory Diagnostics Tool or a third party tool, Mentest86+ to check the memory.

     

    Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    In addition, I also would like to suggest you update the BIOS and the hardware drivers for Windows 7 to improve the stability.

     

    If the issue persists, please upload more minidump files for our further research.

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, July 26, 2010 6:41 AM