BSODs and Memory / Video Issues, need help!

Hi all, new to this forum so will start by saying a big hello :)

Ok so, i've been plagued with errors on my machine now for quite some time and finally sick to death of the BSODs and memory / video issues.

Recently i've been having problems playing mainly Bad company 2, where suddenly i'm about to shoot someone and end up instead being given a nice 0x03B or 0x0BE error message. Those are just two of the errors i've encountered as it differs randomly but those seem to be the most common. Also the usual suspect linked to these BSODs is a certain atikmd.sys file (which is to do with the catalyst control centre im aware of), reinstalling the display driver has not fixed this as the BSOD still appears but with a file called aswsnx.sys?? (no results on google)

Not only bad company 2 but other games have started giving the BSOD, i.e. age of empires online and I can't quite put my finger on WHY this is happening.

Alongside this very annoying series of BSODs (which come and go as they please) i'm having issues with my ram where my PC won't recognise all 6GB and list 4GB or 2GB as availble system memory instead! To try and get around this i've removed one of the modules, but that hasn't explained why a module is potentially failing... is it a faulty MoBo?

My specs are:

Windows 7 64bit
Gigabyte X58A-UD3R
i7 920 @ 2.67GHz
4GB OCZ Reaper RAM
ATi HD 5850 2GB vapor X edition

I've also attached the crash dumps for your information.

Many thanks!

bm304 said:

Hi all, new to this forum so will start by saying a big hello :)

Ok so, i've been plagued with errors on my machine now for quite some time and finally sick to death of the BSODs and memory / video issues.

Recently i've been having problems playing mainly Bad company 2, where suddenly i'm about to shoot someone and end up instead being given a nice 0x03B or 0x0BE error message. Those are just two of the errors i've encountered as it differs randomly but those seem to be the most common. Also the usual suspect linked to these BSODs is a certain atikmd.sys file (which is to do with the catalyst control centre im aware of), reinstalling the display driver has not fixed this as the BSOD still appears but with a file called aswsnx.sys?? (no results on google)

Not only bad company 2 but other games have started giving the BSOD, i.e. age of empires online and I can't quite put my finger on WHY this is happening.

Alongside this very annoying series of BSODs (which come and go as they please) i'm having issues with my ram where my PC won't recognise all 6GB and list 4GB or 2GB as availble system memory instead! To try and get around this i've removed one of the modules, but that hasn't explained why a module is potentially failing... is it a faulty MoBo?

My specs are:

Windows 7 64bit
Gigabyte X58A-UD3R
i7 920 @ 2.67GHz
4GB OCZ Reaper RAM
ATi HD 5850 2GB vapor X edition

I've also attached the crash dumps for your information.

Many thanks!

Easy and straight forward. Your Avast. remove and replace with Microsoft Security Essentials and the win 7 firewall.


http://files.avast.com/files/eng/aswclear5.exe


http://www.microsoft.com/security_essentials/

Just to update - I have possibly solved the 0x050 bsod by following this microsoft information page: STOP: 0x00000050 Page_Fault_In_Non-Paged_Area Error After Installing Service Pack 1 (SP1)

After each potential fix I have tested my machine by playing Age of Empires Online..

*Before any changes were made the game will last between 8-15mins before BSOD..

So far this is the workflow:

1# Removed Avast as recommended - ATi BSODs have stopped. Received 0x050 BSOD after updating to SP1.

2# Uninstalled the video card + drivers in safe mode and reinstalled a fresh copy of the amd driver upon restart. Age of Empires now works beyond the initial time span before BSOD.

3# Next BSOD after playing for about 30 - 45mins with an 0x010e error message (video memory management).

Again, attached the third updated Memory dumps for a possibly solution to this.

many thanks!

bm304 said:

Just to update - I have possibly solved the 0x050 bsod by following this microsoft information page: STOP: 0x00000050 Page_Fault_In_Non-Paged_Area Error After Installing Service Pack 1 (SP1)

After each potential fix I have tested my machine by playing Age of Empires Online..

*Before any changes were made the game will last between 8-15mins before BSOD..

So far this is the workflow:

1# Removed Avast as recommended - ATi BSODs have stopped. Received 0x050 BSOD after updating to SP1.

2# Uninstalled the video card + drivers in safe mode and reinstalled a fresh copy of the amd driver upon restart. Age of Empires now works beyond the initial time span before BSOD.

3# Next BSOD after playing for about 30 - 45mins with an 0x010e error message (video memory management).

Again, attached the third updated Memory dumps for a possibly solution to this.

many thanks!

Newest crash still refers to a video problem where it was waiting for a response from all cores and timed out.

You may want to revert back to a driver that worked or remove whatever updates affect the video subsystem

Avast is gone completely.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050811-22963-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eace90
Debug session time: Sun May  8 11:08:56.455 2011 (GMT-4)
System Uptime: 0 days 0:45:48.654
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {23, 2, 75, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+262 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000023, The subtype of the bugcheck:
Arg2: 0000000000000002
Arg3: 0000000000000075
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x10e_23

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880015e422f to fffff80002ce7640

STACK_TEXT:  
fffff880`091cc5f8 fffff880`015e422f : 00000000`0000010e 00000000`00000023 00000000`00000002 00000000`00000075 : nt!KeBugCheckEx
fffff880`091cc600 fffff880`02d87c2a : fffffa80`05a5f000 fffffa80`05a5f000 00000000`00000002 00000000`00000100 : watchdog!WdLogEvent5+0x11b
fffff880`091cc650 fffff880`02d8aaaf : 00000000`00000075 00000000`00000000 fffffa80`000034a5 fffff8a0`03eb1700 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x262
fffff880`091cc750 fffff880`02d86d61 : 00000000`00000000 00000000`00000000 fffff8a0`03eb1700 00000000`00080000 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`091cc790 fffff880`02d93cf0 : 00000000`00000000 00000000`00000000 fffff8a0`03eb1700 fffff880`02d87770 : dxgmms1!VIDMM_GLOBAL::DiscardAllocationInternal+0x2d
fffff880`091cc910 fffff880`02d89cf2 : fffffa80`0578b870 fffff8a0`03eb1700 00000000`00000000 fffff880`02d85500 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x530
fffff880`091cca80 fffff880`02d96ebb : fffff8a0`0ac8c1a8 fffff8a0`0a4fb8b8 fffff8a0`0a4fb800 fffffa80`0578b910 : dxgmms1!VIDMM_GLOBAL::PurgeAllocation+0x3a
fffff880`091ccad0 fffff880`02d6554a : fffffa80`fffff3eb 00000000`00000000 fffff8a0`0ac8c010 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::PurgeContent+0x133
fffff880`091ccb30 fffff880`02ca17a1 : fffffa80`05a4a000 fffffa80`05a4a000 00000000`00000080 00000000`00000000 : dxgmms1!VidMmPurgeAllSegments+0x66
fffff880`091ccba0 fffff880`02ca06bd : 00000000`00000001 fffffa80`05a4a000 00000000`00000000 fffff880`000000b5 : dxgkrnl!DXGADAPTER::PurgeSegments+0x95
fffff880`091ccbd0 fffff880`02ccce0f : fffffa80`05a3fa58 ffffffff`fffe7960 fffffa80`042ab4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0xf9
fffff880`091ccc80 fffff880`02d9bec1 : fffffa80`03dc2010 00000000`00000080 00000000`00000000 fffffa80`05a3f410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`091ccd00 fffff800`02f84cce : 00000000`04f6acc1 fffffa80`0578ba10 fffffa80`036ceb30 fffffa80`0578ba10 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`091ccd40 fffff800`02cd8fe6 : fffff880`009e9180 fffffa80`0578ba10 fffff880`009f40c0 2c307830`2c307830 : nt!PspSystemThreadStartup+0x5a
fffff880`091ccd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+262
fffff880`02d87c2a c78424100100005acbffff mov dword ptr [rsp+110h],0FFFFCB5Ah

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+262

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x10e_23_dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+262

BUCKET_ID:  X64_0x10e_23_dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+262

Followup: MachineOwner
---------

7: kd> lmvm dxgmms1
start             end                 module name
fffff880`02d64000 fffff880`02daa000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: C:\Symbols\dxgmms1.sys\4CE799C146000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Sat Nov 20 04:49:53 2010 (4CE799C1)
    CheckSum:         00047A89
    ImageSize:        00046000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Solved.

Removed SP1 which stops the 0x010e bluescreens linked with the display adapter, so just the memory issue to fix now.

After testing each module individually, one of the modules bluescreens after around 15mins during a game (the other two modules work fine), so just need to get that sorted with OCZ now.

Just wanted to say a big Thankyou to ZigZag for your support! :)

cheers.

bm304 said:

Solved.

Removed SP1 which stops the 0x010e bluescreens linked with the display adapter, so just the memory issue to fix now.

After testing each module individually, one of the modules bluescreens after around 15mins during a game (the other two modules work fine), so just need to get that sorted with OCZ now.

Just wanted to say a big Thankyou to ZigZag for your support! :)

cheers.

My pleasure and hope the memory issue is just as quick to resolve. Feel free to ask if you need help with it.