BSOD Occurring Multiple Times Per Day (no singular cause)

Page 1 of 5 123 ... LastLast

  1. Posts : 25
    Windows 7 64 bit
       #1

    BSOD Occurring Multiple Times Per Day (no singular cause)


    I have had my computer for almost a year now. During that time, I may have experienced the blue screen once or twice. As such, I did not find cause for concern just yet. However, after applying the free upgrade to Windows 10, I began to experience one or two blue screens per day. After about a week, it began to occur more frequently. Uncertain as to the cause, but with the only major change being the upgrade to Windows 10, I backed-up files which I wanted to keep and performed a clean install of Windows 7 Home Premium (64-bit) which I had been using prior to the upgrade. It had been a flawless operating system. Unfortunately, the blue screen issues persist as a daily occurrence. These blue screens can be, but are not always the same. Thus far, I have seen the following:

    1) driver_irql_not_less_or_equal
    2) pfn_list_corrupt
    3) page_fault_in_nonpaged_area
    4) memory management
    5) service system exception

    Because the BSOD doesn't remain on screen, I am not always able to see the long string of numbers or file names before my computer restarts. However, I believe I have seen ataport.sys and netio.sys. Do not quote me on those though. Furthermore, I have ran chkdsk multiple times to test if it was a hard drive issue. I have also ran the memory diagnostic multiple times. Neither have ever found errors. I ran Memtest86+ and it did not find any errors either (ran overnight). My computer specs are:

    Windows 7 Home Premium (64-bit)
    Intel i5-4670 3.40 GHz
    MSI GeForce GTX 770
    Mushkin Stealth Enhanced 8 GB RAM
    WD Blue 1 TB HD
    EVGA 750B2 (750 W) PSU
    MSI Z97-G55 LGA 1150 MOBO

    I have been trying to get this fixed elsewhere and it was suggested that I run drive verifier. I had difficulty getting this to work, but I believe I was able to get at least one DMP file while it was active. I think that it is 101115-21918-01.dmp. I was also asked to include memory.dmp at one point. I never received a response to these queries. I do not know if the DM log collector grabs all of those files so I will include a link where most of this stuff can be found.

    https://onedrive.live.com/redir?resi...t=folder%2czip
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Hi Brothahill666,

    Welcome to the 7forums.

    Please remove MSI software, some are known for causing BSOD's.

    This has come up a few times
    Code:
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 000000000000125d, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88000db185f, address which referenced memory
    Meaning a driver requested data that was corrupted, this indicates memory problems.
    In this case it was the nvidia video driver that requested it, this driver has been flagged in other dumps too but I am not sure if it is due to possible memory corruption or the drivers self.
    Please run MemTest86+ for testing the memory and reinstall the graphics drivers.



    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

       Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia
    Code:
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`048f3000 fffff880`053d6000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 03 03:54:49 2015 (560F3569)
        CheckSum:         00A9E36F
        ImageSize:        00AE3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    I have uninstalled all of the MSI software (no longer installed) and everything Nvidia (then reinstalled) as suggested. I will update the results of said changes in the coming days. As for Memtest86+, I probably ran this in the last week and it returned zero errors after 8+ passes. Should I run this test again? I also have many new DMP files since my initial post. I believe these are from Oct 18 - Oct 20.
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4

    There are a few network drivers flagged.
    Check Intel and Realtek for driver updates.
    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your manufacturer.
    Code:
    *** WARNING: Unable to verify timestamp for iusb3xhc.sys
    *** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
    0: kd> lmvm iusb3xhc
    start             end                 module name
    fffff880`04117000 fffff880`041de000   iusb3xhc   (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
        Image name: iusb3xhc.sys
        Timestamp:        Mon Mar 23 17:28:57 2015 (55103F49)
        CheckSum:         000C7937
        ImageSize:        000C7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
    *** WARNING: Unable to verify timestamp for iusb3hub.sys
    *** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
    0: kd> lmvm iusb3hub
    start             end                 module name
    fffff880`060f2000 fffff880`06156000   iusb3hub   (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\iusb3hub.sys
        Image name: iusb3hub.sys
        Timestamp:        Mon Mar 23 17:28:54 2015 (55103F46)
        CheckSum:         0006D191
        ImageSize:        00064000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    0: kd> lmvm Rt64win7
    start             end                 module name
    fffff880`0445b000 fffff880`0454d000   Rt64win7   (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Thu Jan 15 07:06:44 2015 (54B758F4)
        CheckSum:         000F2322
        ImageSize:        000F2000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`04812000 fffff880`052f5000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 03 03:54:49 2015 (560F3569)
        CheckSum:         00A9E36F
        ImageSize:        00AE3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  5. Posts : 25
    Windows 7 64 bit
    Thread Starter
       #5

    I ran the Intel Driver Update Utility and after a scan, it doesn't list any drivers. I'm not sure what I should be trying to install from RealTek. Is this the correct one (RTL8111DP/EP DASH All-In-One installation kit for Win7/Win8/Win8.1)? After making the previous changes, I still receive various BSOD, but driver_irql_not_less_or_equal does seem to occur most often.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    Sorry, I forgot to add a few things.

    The iusb3 drivers are both USB drivers from Intel.
    The Rt64win7.sys is the Realtek PCIe GBE Family Controller network driver.
      My Computer


  7. Posts : 25
    Windows 7 64 bit
    Thread Starter
       #7

    I've made the next round of suggested changes (Intel, RealTek and Nvidia drivers) and uploading the resulting BSOD DMP files (maybe 16-17 new) as they continue to persist. I did experience something new. My computer restarted itself without the BSOD of death. This has only occurred one time thus far.
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #8

    I need you to do a few things.
    1. Check the frequency of the memory and check if it is supported by the motherboard,
    2. Do the same with the voltage,
    3. Make sure inside the case is no dust and clean the contacts of the ram with rubbing alcohol and a q-tip,
    4. Run MemTest86+ again


    The first 2 are necessary, the 3rd isn't necessary if you already have checked/cleaned it.
    The 4th is for now not necessary too, but more like if everything is done and didn't help.
      My Computer


  9. Posts : 25
    Windows 7 64 bit
    Thread Starter
       #9

    I checked 1, 2 and 3. Everything seems to be in order and BSOD persists. I'll start up Memtest again tonight.
      My Computer


  10. Posts : 25
    Windows 7 64 bit
    Thread Starter
       #10

    Ran Memtest for 9+ passes and found zero errors.
      My Computer


 
Page 1 of 5 123 ... LastLast

  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 04:10.
Find Us