Random BSODs while playing World of Warcraft


  1. Posts : 3
    Windows Ultimate 64 Bit
       #1

    Random BSODs while playing World of Warcraft


    Hello,
    My name is Maria and I got a problem with my Boyfriends computer. We both were playing yesterday World of Warcraft, but then he got a Bluescreen. Since I am the only one in this house who has a lot of experience with Computers, I said I gonna fix it. The computer started crashing with:
    SYSTEM_THREAD_EXCEPTION_NOT_ HANDLED
    The file that caused the crash was dxgmms1.sys
    Bug Check Code: 0x1000007e
    Since it was a DirectX File I thought it was the Video Card drivers, so I updated them.
    Joined World of Warcraft again. After 20 minutes it crashed again. This time it was:
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Crash caused again by dxgmms1.sys AND ntoskrnl.exe
    Bug Check Code: 0x00000d1
    I thought OK, may he doesn't likes that driver, so I created a Restore Point and updated all out of date drivers and of course I changed the Video Card Driver again. After that I joined World of Warcraft again, the computer did run fine like 30 minutes long. Then it crashed again:
    MEMORY_MANAGEMENT
    Caused by ntoskrnl.exe
    Bug Check Code: 0x000001a
    I thought may it's really the RAM or the Hard Disk so I did run 2 different Memory tests, a various bunch of times. I used Memtest86 and The Windows Memory Diagnostic Tool.
    I left him the whole night on, in normal usage(no Games) and it didn't crashed.
    I start to think the Video card is faulty or the motherboard. I attached the Dumpfiles.

    Thanks for help,
    cheers

    Oh damn forgot the System Spec of his computer
    OS. Windows 7 Ultimate 64 Bit RETAIL
    CPU: AMD Athlon 2 x2 250 350 GHz
    Video Card(GPU): Nvidia Geforce 520
    Memory: 4 GB
    Mainboard: Asus
    Age of Build: N/A, may 2,5 years
    Age of OS: N/A 1/2-1 year
    Last edited by Nosferatu; 20 Dec 2011 at 11:38. Reason: Pressed by accident enter to early...
      My Computer


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

    These were related to: Hardware (RAM) Zero Page corrupted.

    These crashes were caused by memory corruption (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!!!



    1-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+



    2-Driver verifier

    I'd suggest that you first backup your data 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"
    - 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 (an estimate on my part).

    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.
    Driver Verifier - Enable and Disable


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  3. Posts : 3
    Windows Ultimate 64 Bit
    Thread Starter
       #3

    I was already testing the comp before with Memtest86 and Windows Memory Diagnostic Tool, but cause you asked for it, I did run the test again. No errors, all passed, tested every RAM rig solo and both together. So it's something else then the RAM.
    I did the Driver Verifier thing. Windows crashed right at the start up. I couldn't choose safe mode so I chosen Start Up Repair. Windows started normally. I checked the Minidump and in there was the crash I've got with the Driver Verifier.
    DRIVER_VERIFIER_IOMANAGER_VIOLATION
    Bug Check Code: 0x00000c9
    Caused by: dtsoftbus01.sys AND ntoskrnl.exe

    I don't know what else to do, I am at my wit's end.

    Attached last dumpfile,
    cheers for support
      My Computer


  4. Posts : 3
    Windows Ultimate 64 Bit
    Thread Starter
       #4

    UPDATE
    Found out dtsoftbus01.sys is from Daemon Tools, so I uninstalled Daemon Tools and started Windows with the Verifier again.
    No crashes until now, I keep him running and having my eye on it.
      My Computer


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

    Nosferatu said:
    UPDATE
    Found out dtsoftbus01.sys is from Daemon Tools, so I uninstalled Daemon Tools and started Windows with the Verifier again.
    No crashes until now, I keep him running and having my eye on it.
    Daemon tools is a known cause of BSOD's
      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 01:11.
Find Us