BSOD at random times. Different types of Errors but mainly 0x0000007E

Page 3 of 3 FirstFirst 123

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

    Nispar101 said:
    This is the driver I got from their site though. So it must use the Atheros driver. Does that mean I'm doomed to blue screens? I haven't got one for a while now *knock on wood* but I have a feeling they will return.

    There are a few options if the crashes continue.

    Install the driver in compatibility mode


    To install in compatibility mode right click the installer, go to properties, then compatibility. Choose the appropriate OS

    Compatibility Mode



    Try a different device.


    Have you tried this driver http://support.netgear.com/app/answers/detail/a_id/18818/~/wna1100-release-software---version-1.1.4.32
      My Computer


  2. Posts : 14
    Windows 7 Home Premium 64bit.
    Thread Starter
       #22

    Well, I have no other devices to try that offer the wireless capability I need. Yes I have tried that driver, it is the one currently installed. I did get a new crash this morning though. Here it is...
      My Computer


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

    Nispar101 said:
    Well, I have no other devices to try that offer the wireless capability I need. Yes I have tried that driver, it is the one currently installed. I did get a new crash this morning though. Here it is...

    Newest crash

    Probably caused by your athrx.sys driver again.
      My Computer


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

    I had multiple crashes again yesterday all with the NETGEAR device unplugged. Would that driver still be loaded even while unplugged? Also I noticed 2 of the blue screens blame dxgmms1.sys, not sure what that means. I just think it's odd that all of these blue screens are not the same error and are almost always different now.
      My Computer


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

    Nispar101 said:
    I had multiple crashes again yesterday all with the NETGEAR device unplugged. Would that driver still be loaded even while unplugged? Also I noticed 2 of the blue screens blame dxgmms1.sys, not sure what that means. I just think it's odd that all of these blue screens are not the same error and are almost always different now.

    BSOD's are always a combination of things. The atheros driver was still installed in the crash (in the snip). Once it was removed the BSOD's were related to memory corruption.

    Now that the atheros issue is resolved we can look at this one.




    These crashes were caused by memory corruption/exception (Cx05) 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-7 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 (Windows Drivers)
      My Computer


 
Page 3 of 3 FirstFirst 123

  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 11:30.
Find Us