Random BSOD in all new machine, INTERRUPT EXCEPTION NOT HANDLED


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    Random BSOD in all new machine, INTERRUPT EXCEPTION NOT HANDLED


    Hey guys,

    I just bought my new PC (separate pieces), assembled it and it runs great. I am running a full retail 7 Ultimate x64 on a AMD Phenom II 1090T 3.2Ghz, with 8Gb (dual channel 4Gb) 1600Mhz, Asus M5A99X EVO, two commonly set HDs (500Gb system and 80Gb backup), a XFX Radeon HD7970 Black Edition and a XFX Core Edition 750w PSU to supply them all.

    Everything ran smoothly at first, but after I was done with the Windows instalation/update and started to install my own stuff, I started to get some weird random BSODs. Not too frequent so i could not set a pattern to the crashes, but it was like once a day for like 3 or 4 days now. Those crashes happen when I am on Windows, surfing the web, listening to music and using IMs. I haven't got any crashes when playing games, which makes me discard my CPU, VGA and memory. But, since I'm no genius and I am having some trouble with those crashes (such as losing work and stuff like that), I thought I could call in for some help from you guys.

    What I could make out of the BSODs was the string INTERRUPT_EXCEPTION_NOT_HANDLED, and It was only the last time It happened, since the other times i couldn't even read and the system was already rebooting.

    I am attaching the dump files and the system health report.

    Hope you guys can help me... Been trapped in a crappy PC my whole life and, now that I have a little monster, I cannot benefit from all of its features entirely.

    I thank you all who take a bit of your time to try and help me in advance.

    Cheers!
      My Computer


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


    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 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.
      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 15:36.
Find Us