BSOD when I play Mabinogi, 0x0000001e

Page 1 of 3 123 LastLast

  1. Posts : 21
    Windows 7 Home Premium 64bit
       #1

    BSOD when I play games, 0x0000001e


    Here's my problem:
    Ever since last week, whenever I played the game Mabinogi (by Nexon), my computer would BSOD a few minutes into the game. I tried everything, but it wouldn't go away. So I reformatted my computer in hopes that it would fix. After it was reformatted and set up, I redownloaded the game and started playing. It worked fine for an hour or two, until-SURPRISE!- There was a BSOD. This has happened every time since I started playing again, and I don't know what to do. Before I reformatted, the BSOD I got was an Unexpected Kernel Trap one, but now I'm getting this one.
    What do I do?

    System Spec:
    Windows 7 is x64, the original installed OS, and this system is two or three years old.

    Edit: Bluescreen isn't only in Mabinogi, it's in any game I play.
    Last edited by hrrrkiki42; 20 Apr 2012 at 19:18.
      My Computer


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

    Simple. Your Norton 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
    Last edited by zigzag3143; 20 Apr 2012 at 23:41.
      My Computer


  3. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Oh, gosh. I would have never guessed.
    All right, removed and replaced. If anything happens, I'll post here.
      My Computer


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

    All right I got another one, also during a game. Dump attached.
      My Computer


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


    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 a 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 Verifer

    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.

    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).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    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 "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like.
    From my limited experimentation it makes the BSOD's come faster.
    - 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.

    If you are using win 8 add these

    - Concurrency Stress Test
    - DDI compliance checking

    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 (an estimate on my part).

    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.

    Thanks to JGriff2 & Usasma.
    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Driver Verifier

    Using Driver Verifier (Windows Drivers)
      My Computer


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

    hrrrkiki42 said:
    Oh, gosh. I would have never guessed.
    All right, removed and replaced. If anything happens, I'll post here.

    In addidtion to JMH's suggestions please remove Related to EagleX64.sys HackShield Driver (AMD64) from AhnLab, Inc. AT least to test.
      My Computer


  7. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Memtest reported no errors, and the dump is attached.
      My Computer


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

    hrrrkiki42 said:
    Memtest reported no errors, and the dump is attached.
    Verifier enabled but didnt catch the driver keep running it,
      My Computer


  9. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Okay, I got two more. One came on startup and one came while gaming.

    Edit: I just got another one without verifier, attaching it here in case it helps.
    Last edited by hrrrkiki42; 22 Apr 2012 at 10:03.
      My Computer


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

    hrrrkiki42 said:
    Okay, I got two more. One came on startup and one came while gaming.

    Edit: I just got another one without verifier, attaching it here in case it helps.
    Two verifier enabled but both point to an OS file. Usually not the real culprit. Just to check lets run a system file check

    SFC /SCANNOW Command - System File Checker

    How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
      My Computer


 
Page 1 of 3 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 16:44.
Find Us