BSOD please help

  1.    #1

    BSOD please help


    Hi,

    I put together my new system in about Oct/Nov, and was having some issues with it, I have recently done a completely fresh reinstall of windows (completely zero filled the disk and reinstalled). I have just had a crash with the system when an Ipon was plugged in updating, wasn't watching the computer at the time, but here are the crash reports. Please can someone help me.

    Running a retail version of windows 7 HP 64bit, all the components in my machine were new in Oct, if that makes a difference.

    Thank you
    Dan
      My Computer


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

    DanielR said:
    Hi,

    I put together my new system in about Oct/Nov, and was having some issues with it, I have recently done a completely fresh reinstall of windows (completely zero filled the disk and reinstalled). I have just had a crash with the system when an Ipon was plugged in updating, wasn't watching the computer at the time, but here are the crash reports. Please can someone help me.

    Running a retail version of windows 7 HP 64bit, all the components in my machine were new in Oct, if that makes a difference.

    Thank you
    Dan
    Memory corruption caused by asacpi.sys Please run memtest and remove asacpi.sys
    ASACPI.sys Sun Mar 27 22:30:36 2005
    The 2005 version of this driver is a known BSOD cause.
    Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
    Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
    Download and install it.
    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

    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\Windows_NT6_BSOD_jcgriff2\013011-19921-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;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 Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c43e50
    Debug session time: Sun Jan 30 14:00:26.161 2011 (GMT-5)
    System Uptime: 0 days 7:20:01.317
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8804a81661c, 0, fffff8800182c08d, 5}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    6: 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: fffff8804a81661c, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800182c08d, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cae0e0
     fffff8804a81661c 
    
    FAULTING_IP: 
    afd!AfdFastIoDeviceControl+107d
    fffff880`0182c08d 41399482f0650100 cmp     dword ptr [r10+rax*4+165F0h],edx
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88004762510 -- (.trap 0xfffff88004762510)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000000b rbx=0000000000000000 rcx=fffffa800752eb00
    rdx=000000000001202f rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800182c08d rsp=fffff880047626a0 rbp=fffff88004762ca0
     r8=0000000000000000  r9=0000000000000000 r10=fffff8804a800000
    r11=00000000001f0003 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    afd!AfdFastIoDeviceControl+0x107d:
    fffff880`0182c08d 41399482f0650100 cmp     dword ptr [r10+rax*4+165F0h],edx ds:fffff880`4a81661c=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002af58c1 to fffff80002a76740
    
    STACK_TEXT:  
    fffff880`047623a8 fffff800`02af58c1 : 00000000`00000050 fffff880`4a81661c 00000000`00000000 fffff880`04762510 : nt!KeBugCheckEx
    fffff880`047623b0 fffff800`02a7482e : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0754c061 : nt! ?? ::FNODOBFM::`string'+0x40e8b
    fffff880`04762510 fffff880`0182c08d : fffffa80`07537010 fffff880`047627d0 00000000`00000172 fffffa80`04e5a220 : nt!KiPageFault+0x16e
    fffff880`047626a0 fffff800`02d91473 : 00000000`00000000 fffffa80`0752eb00 00000000`0199f888 00000000`00000001 : afd!AfdFastIoDeviceControl+0x107d
    fffff880`04762a10 fffff800`02d91f66 : fffff880`04762bd8 00000000`00000548 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
    fffff880`04762b40 fffff800`02a75993 : 00000000`00000000 fffffa80`00000000 00000000`00000000 fffffa80`072cbdb0 : nt!NtDeviceIoControlFile+0x56
    fffff880`04762bb0 00000000`7719fdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0199f7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7719fdca
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !afd
    8 errors : !afd (fffff8800182c104-fffff8800182c13c)
    fffff8800182c100  00  00  66  41 *70  0c  24  0f  85  cd  6a  00 *24  41  0f  b6 ..fAp.$...j.$A..
    fffff8800182c110  44  24  02  3c *a4  0f  85  b7  6a  00  00  81 *6b  cf  20  01 D$.<....j...k. .
    fffff8800182c120  00  0f  85  1e *00  00  00  c7  44  24  58  00 *8c  20  0f  33 ........D$X.. .3
    fffff8800182c130  c9  ff  15  e9 *01  fe  ff  84  c0  0f  85  2b *f6  00  00  41 ...........+...A
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  STRIDE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    Followup: memory_corruption
    ---------
      My Computer

  3.    #3

    Thank you for such a fast response zigzag3143, I have just updated the Asus ATK driver (it is now time stamped 2009), and will download the memtest and run it soon.

    Thanks :)
      My Computer


 

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 06:16.
Find Us