BSOD playing Crysis Windows 7 x64


  1. Posts : 3
    Windows 7 Ultimate x64
       #1

    BSOD playing Crysis Windows 7 x64


    Hi,

    Got a random BSOD playing Crysis last night, this error only occurs in Crysis, no other games. Had every setting on Very High which was putting a high load on the PC.

    PC Specs:-

    ASUS Sabertooth 990FX Motherboard
    750W True Power Modular PSU
    AMD 1090T CPU
    2x MSI Radeon R6850 Power O/C Edition (in Crossfire) (12.1 Preview Drivers)
    2x WD50000AX 500GB HDD
    SYNAPSE CACHE 64GB SSD
    Windows 7 x64 Ultimate Edition

    All hardware between 2 weeks and 3 months old.

    Bluescreen view:


    ==================================================
    Dump File : 010212-34242-01.dmp
    Crash Time : 02/01/2012 02:22:36
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff880`04820251
    Parameter 3 : fffff880`0a5e58f8
    Parameter 4 : fffff880`0a5e5150
    Caused By Driver : dxgmms1.sys
    Caused By Address : dxgmms1.sys+37dc0
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : dxgmms1.sys+20251
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\010212-34242-01.dmp
    Processors Count : 6
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 275,848
    ==================================================

    Attachment as per sticky thread also included.

    Thanks for any assistance,
    Chris.
      My Computer


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

    Chrisoldinho said:
    Hi,

    Got a random BSOD playing Crysis last night, this error only occurs in Crysis, no other games. Had every setting on Very High which was putting a high load on the PC.

    PC Specs:-

    ASUS Sabertooth 990FX Motherboard
    750W True Power Modular PSU
    AMD 1090T CPU
    2x MSI Radeon R6850 Power O/C Edition (in Crossfire) (12.1 Preview Drivers)
    2x WD50000AX 500GB HDD
    SYNAPSE CACHE 64GB SSD
    Windows 7 x64 Ultimate Edition

    All hardware between 2 weeks and 3 months old.

    Bluescreen view:


    ==================================================
    Dump File : 010212-34242-01.dmp
    Crash Time : 02/01/2012 02:22:36
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff880`04820251
    Parameter 3 : fffff880`0a5e58f8
    Parameter 4 : fffff880`0a5e5150
    Caused By Driver : dxgmms1.sys
    Caused By Address : dxgmms1.sys+37dc0
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : dxgmms1.sys+20251
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\010212-34242-01.dmp
    Processors Count : 6
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 275,848
    ==================================================

    Attachment as per sticky thread also included.

    Thanks for any assistance,
    Chris.
    Hi Chris


    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

    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 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 7 Ultimate x64
    Thread Starter
       #3

    Thanks very much for the response, I will check the RAM in the PC, the Motherboard is 1 week old old so I hope it's not that!

    In your experience could is it possible that it could also be GPU memory? The reason I ask is that the 6800 series GPU's have a known issue in that one of the memory capacitors is not rated high enough (1400 instead of 1600mv). My GPU memory is factory over clocked by MSI to 1100mhz, vanilla 6850's run at 1000mhz.
      My Computer


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

    It might be directX that is causing it but run the tests to be sure.


    Ken
      My Computer


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

    zigzag3143 said:
    It might be directX that is causing it but run the tests to be sure.


    Ken
    Thanks Ken, I will run the tests.
      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 03:12.
Find Us