Multiple Win7 Pro BSOD's (0x1000007e, 0x00000024, 0x0000001e, ...)

Page 1 of 7 123 ... LastLast

  1. Posts : 34
    Windows 7 Pro x64
       #1

    Multiple Win7 Pro BSOD's (0x1000007e, 0x00000024, 0x0000001e, ...)


    I have a custom build desktop that has been crashing (BSOD) almost every night for a while now.

    The hardware and OS I have is this:

    MB: ASUS P8Z68-V Pro (with latest BIOS v1101)
    CPU: Intel i7-2600K (not overclocked)
    RAM: 16GB (4 x Corsair 4Gx4 CMZ16GX3M4A1600C9)
    Graphics: NVIDIA GeForce GTX470
    HDD's: 2 x 1TB WD WD1002FAEX-00Y9A0 and 2 x 1TB Hitachi HDS721010KLA330)
    RAID: all four 1TB HDD's are configured as RAID 10 using the integrated Intel RAID controller, using Intel RST v 10.8.0.1003

    OS: Windows 7 Pro x64 OEM

    The system is about 6 months old, and the OS install is only a few weeks old (I re-installed OS from scratch then).

    A few other things I have done are:

    1. Ran memtest86+ (only one pass, no errors).
    2. I have Norton Internet Security 2012, SUPERAntiSpyware and MalwareBytes Anti-Malware installed, have run full scans with all 3 of them, no malware/virus found.
    3. I use Norton Ghost 15.0 for daily backups to a NAS device.

    I have attached info files as per "BSOD - Posting Instructions".

    Any help is appreciated.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Two issues

    1- Symantec. Remove and replace

    Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


    http://us.norton.com/support/kb/web_...080710133834EN

    Microsoft Security Essentials - Free Antivirus for Windows


    2-Iastor.sys Related to iaStor.sys Intel Matrix Storage Manager driver - ia32.

    Re-install newest version
      My Computer


  3. Posts : 34
    Windows 7 Pro x64
    Thread Starter
       #3

    zigzag3143 said:
    Two issues

    1- Symantec. Remove and replace

    Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


    http://us.norton.com/support/kb/web_...080710133834EN

    Microsoft Security Essentials - Free Antivirus for Windows


    2-Iastor.sys Related to iaStor.sys Intel Matrix Storage Manager driver - ia32.

    Re-install newest version
    Thanks for the reply. I have uninstalled all Norton products I had installed (NIS 2012 and Ghost 15.0). I installed MSE and re-instaled the Intel RST (iaStor.sys) latest driver version 10.8.0.1003.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    pichogve said:
    zigzag3143 said:
    Two issues

    1- Symantec. Remove and replace

    Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


    http://us.norton.com/support/kb/web_...080710133834EN

    Microsoft Security Essentials - Free Antivirus for Windows


    2-Iastor.sys Related to iaStor.sys Intel Matrix Storage Manager driver - ia32.

    Re-install newest version
    Thanks for the reply. I have uninstalled all Norton products I had installed (NIS 2012 and Ghost 15.0). I installed MSE and re-instaled the Intel RST (iaStor.sys) latest driver version 10.8.0.1003.

    Good luck
      My Computer


  5. Posts : 34
    Windows 7 Pro x64
    Thread Starter
       #5

    Had one more crash last night, here is the output from BlueScreen View:

    ==================================================
    Dump File : 021012-14476-01.dmp
    Crash Time : 2/10/2012 3:43:16 AM
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff880`04e6a9c9
    Parameter 3 : fffff880`04107e88
    Parameter 4 : fffff880`041076e0
    Caused By Driver : USBPORT.SYS
    Caused By Address : USBPORT.SYS+21f21
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : USBPORT.SYS+249c9
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021012-14476-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 303,794
    ==================================================

    and I have also attached the dump file.

    Another thing I have done since the last time I posted is, I ran memtest86+ v4.2 and it completed 6 passes with no errors.
      My Computer


  6. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #6

    These crashes were caused by memory corruption/exception (probably a driver).
    Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!


    If you have raid > update its Driver.


    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.
    Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  7. Posts : 34
    Windows 7 Pro x64
    Thread Starter
       #7

    Here is an update.

    I ran memtest86+ v4.2 (booting from CD) for about 13 hours or so, it completed 6 passes and there where no errors reported.

    I am going to try verifier as you suggested.

    Thanks again for the help.
      My Computer


  8. Posts : 34
    Windows 7 Pro x64
    Thread Starter
       #8

    I forgot to mention before, I am not overclocking.

    And during the weekend I also ran diagnostics to all my hard drives just to make sure they were OK. For my Hitachi drives I ran the long test using Hitachi's Drive Fitness Test v4.16 and for my WD drives I ran the long test using Seagate's SeaTools v2.23. All tests ran with no errors.
      My Computer


  9. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #9

    Thank you for reporting back.
    Good luck!
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    Good news on Memtest. Driver verifier?
      My Computer


 
Page 1 of 7 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 13:57.
Find Us