BSOD probable cause is all over the place


  1. Posts : 35
    Windows 7 64bit
       #1

    BSOD probable cause is all over the place


    Hi all, I have never had a month without a BSOD. Every time I analyze the dump file, the probably cause is different. All I want is a stable Windows machine that I don't have to worry about when I go to bed. Is that too much to ask?

    anyway, system info:

    Windows 7 64 bit
    RAM: G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500)
    HDD: all over the place but 2x RAID0 arrays
    CPU: Intel Core 2 Duo E8400 Wolfdale 3.0GHz LGA 775 65W
    MoBo: GIGABYTE GA-EP45C-UD3R LGA 775 Intel P45
    PSU: 700W

    I built this box In September of 2009 (2 yrs ago)

    As always, your expert help and advice is appreciated!
      My Computer


  2. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #2

    Fill in your 'System Specs' in the lower left corner of any of your posts, this will help us analyze your system.
    Use this link to find your system specs.
    Speccy Free System information Utility

    Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
    For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
    How to Post a Screenshot in Seven Forums

    Have you been checking your temperatures?
    Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
    Let us know the minimum and maximum temps you get.

    Have you updated all your motherboard drivers from the Gigabyte support site?

    You last crash STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
    Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
    The minidump is blaming memory corruption.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 0000000000000090, 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: fffff80003f8afcf, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004112100
     0000000000000090 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiIdentifyPfn+26f
    fffff800`03f8afcf f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  fffff8800883c4a0 -- (.trap 0xfffff8800883c4a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0400000000000020
    rdx=0000000000072b3b rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003f8afcf rsp=fffff8800883c630 rbp=fffffa8008757170
     r8=0000000000072b48  r9=0000000000000001 r10=0000000000000042
    r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!MiIdentifyPfn+0x26f:
    fffff800`03f8afcf f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003edf1e9 to fffff80003edfc40
    
    STACK_TEXT:  
    fffff880`0883c358 fffff800`03edf1e9 : 00000000`0000000a 00000000`00000090 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0883c360 fffff800`03edde60 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`000261da : nt!KiBugCheckDispatch+0x69
    fffff880`0883c4a0 fffff800`03f8afcf : 00000000`00063332 fffffa80`05954438 00000000`42506600 fffff800`041cb73f : nt!KiPageFault+0x260
    fffff880`0883c630 fffff800`03f8bc7b : 00000000`00000000 00000000`00000004 fffffa80`05954450 fffffa80`05953000 : nt!MiIdentifyPfn+0x26f
    fffff880`0883c6d0 fffff800`042f07e5 : fffffa80`05953000 fffff880`0883cc60 fffff880`0883c7a8 00000000`00000000 : nt!MmQueryPfnList+0xbb
    fffff880`0883c710 fffff800`042334c8 : 00000000`00000006 00000000`00000000 fffffa80`05953000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
    fffff880`0883c760 fffff800`041e9bd3 : 00000000`00000000 00000000`00000000 00000000`00002000 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x4810d
    fffff880`0883c7f0 fffff800`041ea449 : 00000000`00f5b748 fffff800`03eebf58 00000000`00f5b7a0 00000000`00000001 : nt!ExpQuerySystemInformation+0x1193
    fffff880`0883cba0 fffff800`03edeed3 : 00000000`012a86a8 fffff880`0883cc60 00000000`012a0ce0 00000000`01b23c90 : nt!NtQuerySystemInformation+0x4d
    fffff880`0883cbe0 00000000`7764167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00f5b678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7764167a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiIdentifyPfn+26f
    fffff800`03f8afcf f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiIdentifyPfn+26f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
    
    BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
    
    Followup: MachineOwner
    ---------
    Run memtest86+ for a minimum on 7 full passes with all RAM cards installed, best to run overnight.
    Stop the test if you get any errors.
    RAM - Test with Memtest86+

    Soluto is mentioned in the crash report, uninstall Soluto for testing purposes or you can re-install a new updated version.

    Old or problematic drivers:

    Code:
    adfs.SYS     Fri Jun 27 04:52:37 2008 - Adobe File System Driver
    Update this driver or uninstall for testing purposes.

    Code:
    ElbyCDIO.sys Wed Feb 18 01:11:23 2009 - CD copy/clone app
    Update program version or uninstall.


    Code:
    iaStor.sys   Fri Jun 05 09:53:40 2009 - Intel Storage drivers
    Update to the latest version at the Intel site.


    Code:
    PxHlpa64.sys Tue Dec 11 07:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs)
    Update program version or uninstall.


    Code:
    VClone.sys   Sat May 23 07:08:37 2009 - VirtualCloneCD Driver by Elaborate Bytes AG
    Update program version or uninstall.
    Last edited by Dave76; 03 Feb 2012 at 12:03.
      My Computer


  3. Posts : 35
    Windows 7 64bit
    Thread Starter
       #3

    Thank you very much for this guide. I will follow accordingly.
      My Computer


  4. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #4

    Let us know if you have any questions and your progress.
      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 15:49.
Find Us