BSODs random since build - various bugcheckcodes

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 14
    Windows 7 64bit
    Thread Starter
       #11

    I have moved the video card to another slot and I have not received any further notices of the video driver failing since my last report. Also the system appeared to be much more stable, however, it crashed again last night.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 4105
    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000005
    BCP2: FFFFF80002F8D16A
    BCP3: FFFFF88009561C40
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
    Last edited by dagaraelder; 07 Mar 2014 at 18:32.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #12

    Follow the Blue Screen of Death (BSOD) Posting Instructions. Upload the data in your next post.
      My Computer


  3. Posts : 14
    Windows 7 64bit
    Thread Starter
       #13

    I have moved the video card to another slot and I have not received any further notices of the video driver failing since my last report. Also the system appeared to be much more stable, however, it crashed again last night.
      My Computer


  4. Posts : 14
    Windows 7 64bit
    Thread Starter
       #14

    I have removed the NVidia card and am still getting BSOD.
    Updated DMP zip file attached. Thanks.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #15

    If you dont supply the adequate data to us, it is problematic to us to assist you. Run SF diag tool, zip and upload ALL the data.

    Because, the latest BSOD is caused by iaStor.sys, and apparently (from the last supplied data), iaStor is disabled in your computer.

    Without the required data, we cannot see what is going on there.
      My Computer


  6. Posts : 14
    Windows 7 64bit
    Thread Starter
       #16

    Yes, of course. Here is the updated data. Thanks.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #17

    Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

    1. Right click on "my computer" icon and click "manage" on the context menu.
    2. It will open the "computer management" window.
    3. Select "Device Manager" in the left pane, It will list all the existing devices up.
    4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
    5. Select one Intel device item under it, right click, uninstall.
    6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
    7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

    The recent BSODs are storage related.
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff80002c6eac5, 0, ffffffffffffffff}
    
    Probably caused by : fileinfo.sys ( fileinfo!FIPreCreateCallback+1ad )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 24, {c08a5, 0, 0, 0}
    
    Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 50, {fffff78140000b08, 0, fffff80002cc0d21, 5}
    
    *** WARNING: Unable to verify timestamp for iaStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
    
    Could not read faulting driver name
    Probably caused by : iaStor.sys ( iaStor+5208b )
    
    Followup: MachineOwner
    ---------
    And one of them is specifically pointing to Intel Rapid Storage.
      My Computer


  8. Posts : 14
    Windows 7 64bit
    Thread Starter
       #18

    Done. Thanks.
      My Computer


  9. Posts : 14
    Windows 7 64bit
    Thread Starter
       #19

    Arc----The crashes continue. On the blue screen they all say "special pool detected memory corruption." I have run memtest86+ many times. The last time for about 9 hours. No errors reported. The crashes started soon after the build. I am wondering if I have a defective motherboard.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #20

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


 
Page 2 of 3 FirstFirst 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 06:09.
Find Us