Random BSOD


  1. Posts : 5
    Windows 7 Ultimate x64
       #1

    Random BSOD


    Hello,
    i'm having random bsod on my pc since I bought it an year ago. 2 weeks ago I did a fresh Windows 7 Ultimate x64 install and i had 2 bsod (MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL)
    First I thought it was a hard drive issue, then a faulty driver from my pci wifi card, but now I have no idea.

    Hope some one could figure this out, thanks in advance

    Is Windows 7 . . .
    - x64
    - the original installed OS on the system? No
    - an OEM or full retail version? full retail version
    - What is the age of system (hardware)? 1 year
    - What is the age of OS installation (have you re-installed the OS?) re-installed 2 weeks ago
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

       Warning
    Upgrade your Kaspersky product, use version 2011
    http://www.kaspersky.com/productupdates
    Code:
    kl1.sys        fffff880`04a4d000    fffff880`04f76000    0x00529000    0x4a9d0591    01/09/2009 15:29:21                
    klbg.sys        fffff880`01be4000    fffff880`01bf2000    0x0000e000    0x4ad607d5    14/10/2009 21:18:13                
    klif.sys        fffff880`01795000    fffff880`017f2000    0x0005d000    0x4b0e453f    26/11/2009 13:07:11                
    klim6.sys        fffff880`012a8000    fffff880`012b2000    0x0000a000    0x4aae1f02    14/09/2009 14:46:26                
    klmouflt.sys        fffff880`0522a000    fffff880`05234000    0x0000a000    0x4ac61e75    02/10/2009 19:38:29

       Information
    ASACPI.sys the 2005 version is a huge cause of BSOD's
    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.
    Code:
    ASACPI.sys        fffff880`04400000    fffff880`04408000    0x00008000    0x42476c4c    28/03/2005 06:30:36
       Information
    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    You can use MagicDisc as an alternative.

    Code:
    sptd.sys        fffff880`0108a000    fffff880`011b1000    0x00127000    0x4bbd315c    08/04/2010 05:29:00
    Test RAM if BSODs continue to occur
    RAM - Test with Memtest86+
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa8026a06160, 2, 1, fffff80002d522a6}
    
    Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa8026a06160, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002d522a6, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecf0e8
     fffffa8026a06160 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`02d522a6 480fb328        btr     qword ptr [rax],rbp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880035d28e0 -- (.trap 0xfffff880035d28e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8007506010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d522a6 rsp=fffff880035d2a70 rbp=00000000fa800a89
     r8=fffff880035d2aa0  r9=0000000000000002 r10=0000000000000000
    r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`02d522a6 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`07506010=ffffff98d3ffe0ff
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c9dbe9 to fffff80002c9e640
    
    STACK_TEXT:  
    fffff880`035d2798 fffff800`02c9dbe9 : 00000000`0000000a fffffa80`26a06160 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`035d27a0 fffff800`02c9c860 : fffffa80`062c0548 fffff880`035d29e0 fffffa80`062c0540 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`035d28e0 fffff800`02d522a6 : fffffa80`0656fde0 00000000`00000000 fffffa80`07484b30 fa800a89`ef9004c0 : nt!KiPageFault+0x260
    fffff880`035d2a70 fffff800`02d092f1 : fa800a89`ef9000c0 00000000`00000000 fa800a89`ef9000c0 fffff800`02f951ad : nt!MiReleaseConfirmedPageFileSpace+0x86
    fffff880`035d2af0 fffff800`02f3ff3b : fffffa80`0a89ef10 00000000`00000000 00000000`00088081 fffffa80`0a67d110 : nt! ?? ::FNODOBFM::`string'+0x2bd1d
    fffff880`035d2bc0 fffff800`02ceb8b1 : fffffa80`0a89ef18 00000000`00000001 00000000`00000000 8c048c04`00000631 : nt!MiSegmentDelete+0x7b
    fffff880`035d2c00 fffff800`02ceb76d : 00000000`00000000 00000000`00000080 fffffa80`0550b740 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
    fffff880`035d2cc0 fffff800`02f3bcce : e448e448`32d132d1 9ae59ae5`46e346e3 b373b373`7d1c7d1c 5b565b56`bcc3bcc3 : nt!MiDereferenceSegmentThread+0x10d
    fffff880`035d2d40 fffff800`02c8ffe6 : fffff880`009b2180 fffffa80`05568b60 fffff880`009bd0c0 5b565b56`bcc3bcc3 : nt!PspSystemThreadStartup+0x5a
    fffff880`035d2d80 00000000`00000000 : fffff880`035d3000 fffff880`035cd000 fffff880`035d27f0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`02d522a6 480fb328        btr     qword ptr [rax],rbp
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+86
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    
    BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thank you for the quick response, I updated the ASACPI.sys driver but I don't know which program installed the sptd.sys driver since i'm currenly using MagicDisc and I never installed Alcohol nor Deamon tools.

    I'll keep you informed if any other bsod ocurrs
      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 09:04.
Find Us