Four different BSOD's including C9, C1, D1, and 0x1000007e


  1. Posts : 5
    Windows 7 Ultimate x64
       #1

    Four different BSOD's including C9, C1, D1, and 0x1000007e


    I'm running windows 7 x64 on a custom built machine. All the hardware is about 8 months old aside from the HDD. After a couple of days of trying to figure this out, i'm officially stuck. So far each BSOD has given me a different BC Code. I'm not sure if this is a result of enabling the driver verifier. I ran a disk check, no problems there. I ran a memory diagnostic, again no problems. I've installed updated drivers directly from the manufacturers web site for my PCIE, audio, and GPU. Nothing has fixed the problem.

    My original thought was that it could have something to do with the most recent drivers for my GPU. I tried reverting back to older drivers, but continued to crash. However, driver verifier was still enabled and I read recently that this could cause problems.

    I have not been able to pinpoint anything in particular that happens every time before I crash. It seems to be random. I've been running in safe mode with networking for an hour now with no problems.

    I'm open to any suggestions and would greatly appreciate the help.

    Update: It's been a little over 2 hours of running in safe mode without any issues. I've been casually browsing the web. I don't know for sure, but I believe this would suggest it's a driver issue rather than hardware?


    My Specs are as follows:

    GPU- Zotac GTX 760 2GB
    MOBO- MSI 970A-G46
    RAM- 8GB DDR3
    CPU- AMD FX 6350
    HDD- 300GB 7200RPM



    Details of each BSOD:

    0x000000c9
    DRIVER_VERIFIER_IOMANAGER_VIOLATION
    Caused by: ntfs.sys

    0x000000c1
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
    Caused by: ntoskrnl.exe

    0x000000d1
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Caused by: ndis.sys

    0x1000007e
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Caused by: ntoskrnl.exe
    Last edited by anaxime; 23 Aug 2014 at 11:22. Reason: Providing more info.
      My Computer


  2. Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       #2

    I have proceeded to disable the driver verifier and follow the guide on the site for installing fresh graphics drivers. I installed the previous set of drivers rather than the most recent ones. I am going to continue by running a game and streaming video. I will report my results after an hour of doing so.

    EDIT: After two minutes of a youtube video I got a BSOD when attempting to log into a website. Yet again, it is a different BC Code.

    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`041c2aa0
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+71f00



    EDIT:

    I decided to take a look at the dmp files myself. In three of the dumps "agent.exe" was the process that caused the crash. After some research I discovered it is a part of a program called "InstallShield Update Service". Apparently it is non-essential and has caused problems for others. I went ahead and removed it using a recommended program.

    One of the dumps listed "lsass.exe" to be the process that caused the crash. This however was while driver verifier was running. From what I have read lsass.exe is an essential part of windows. I don't consider it to be the root of the problem. Although from my understanding there is a virus commonly listed as the same name. After running malewarebytes, it would seem this is not the case.

    The first BSOD, 0x1000007e (note that this is the first BSOD I received after formatting and re-installing windows) is still gibberish to me. It lists it as a "VISTA_DRIVER_FAULT" and lists "system" as the process responsible. Being that this has not occurred again, I think it is possible that my original idea of installing older video drivers has fixed that.

    I have been in safe mode for a couple hours again with no problems what so ever. I think it's time to reboot and see if fixing the "agent.exe" problem was the key.
    Last edited by anaxime; 23 Aug 2014 at 14:14.
      My Computer


  3. Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Last update (hopefully). It's been about an hour and a half since I removed "InstallShield Update service" and booted windows normally. So far everything seems to be running smoothly. My crashes were happening within 5-10 minutes of booting, so this is a good sign. I'll give it a whole day of use before I call it fixed.

    If someone could still give a brief look at my dmp files to make sure I'm not missing anything it would be greatly appreciated.
      My Computer


  4. Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Nope, still not fixed. Ran into another BSOD after installing steam. It appears "steamwebhelper" was the problem. This leads me to beleive the underlining problem is still there.

    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`041c2ad0
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe

    Would really appreciate some help with this.


    EDIT: There's clearly an underlining problem here. I'm pretty sure it is a hardware problem at this point. I have received the same memory management issue on both windows 7 and windows 8.1. All drivers are up to date so that can't be the problem either. I can rule out faulty hdd, as I have tried using a different hard drive and had the same problem. I guess it has to be a problem with my RAM at this point, as I have no idea what else it could be. I just moved both sticks of RAM to different slots on my MOBO, and am currently trying to reproduce the BSOD. Assuming this didn't fix it, I remove one stick and try again. Then try with only the other stick.
    Last edited by anaxime; 23 Aug 2014 at 23:11.
      My Computer


  5. Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       #5

    It appears to have been a faulty stick of RAM. After removing it, everything is working as it should.
      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 06:57.
Find Us