Random BSOD in every week.


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    Random BSOD in every week.


    It happens once a week but it happened twice today. I really wonder what causes that because only a month of warranty time left. Please ask if any more information if needed. Thanks.
      My Computer


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

    Please attach a full report
    https://www.sevenforums.com/crashes-d...tructions.html

    ASACPI.sys the 2005 version is a huge cause of BSODs

       Information
    Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    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 12th 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)

    Code:
    ASACPI.sys        fffff880`06ed1000    fffff880`06ed9000    0x00008000    0x42476c4c    28/03/2005 06:30:36
    Remove any Asus software such as PC Probe or Smart Doctor
    Uninstall any Deamon Tools software

    Stop any Overclocking if any.
    Code:
    AsIO.sys        fffff880`03adf000    fffff880`03ae5000    0x00006000    0x4a768bb4    03/08/2009 11:03:16                
    AsUpIO.sys        fffff880`03ad9000    fffff880`03adf000    0x00006000    0x4a515fb2    06/07/2009 06:21:38
    Code:
    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: 0000000000001100, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002ca4442, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecb100
     0000000000001100 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiProcessExpiredTimerList+72
    fffff800`02ca4442 803818          cmp     byte ptr [rax],18h
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002f8b450 -- (.trap 0xfffff88002f8b450)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000001100 rbx=0000000000000000 rcx=fffffa8004b30c00
    rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ca4442 rsp=fffff88002f8b5e0 rbp=0000000000055165
     r8=fffff88002f65301  r9=0000000000000003 r10=0000000000000065
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!KiProcessExpiredTimerList+0x72:
    fffff800`02ca4442 803818          cmp     byte ptr [rax],18h ds:00000000`00001100=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c981e9 to fffff80002c98c40
    
    STACK_TEXT:  
    fffff880`02f8b308 fffff800`02c981e9 : 00000000`0000000a 00000000`00001100 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f8b310 fffff800`02c96e60 : fffffa80`063d5620 fffff880`06e7d783 fffffa80`04db9d28 fffffa80`04b30c20 : nt!KiBugCheckDispatch+0x69
    fffff880`02f8b450 fffff800`02ca4442 : fffffa80`04b30c20 fffffa80`05d0a908 fffffa80`05d0a908 00000000`00000102 : nt!KiPageFault+0x260
    fffff880`02f8b5e0 fffff800`02ca437e : 0000000c`a8a5f596 fffff880`02f8bc58 00000000`00055165 fffff880`02f66228 : nt!KiProcessExpiredTimerList+0x72
    fffff880`02f8bc30 fffff800`02ca4167 : 00000004`f6203ac2 00000004`00055165 00000004`f6203a3b 00000000`00000065 : nt!KiTimerExpiration+0x1be
    fffff880`02f8bcd0 fffff800`02c9096a : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`06e7ddb0 : nt!KiRetireDpcList+0x277
    fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiProcessExpiredTimerList+72
    fffff800`02ca4442 803818          cmp     byte ptr [rax],18h
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiProcessExpiredTimerList+72
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72
    
    BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72
    
    Followup: MachineOwner
    ---------
      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 22:34.
Find Us