Really irritating BSOD!! Help needed

AurA · 21 Feb 2011

Hellos to evry1 seeing this thread. Now to my problem.

Getting the same BSOD over and over again ,especially while playing games like Bad Company 2 ,namely the dreaded "dxgmms1.sys" error along with the message PAGE_FAULT_IN_NON-PAGED_AREA or something in the similar terms. Happens after 10-15 mins of Gaming.

System details:
Windows 7 x64 is the original installed OS and an OEM version

- Age of system hardware: 10 Months
- What is the age of OS installation :same as no reinstalls of Windows done.

All required files are attached. Help would be gr8tly appreciated.

PS: Removed Norton Internet Security after being told to do so by many seven forums mods and users. Just using Windows defender until system is stable again.
PS2: Did a driver sweep and installed latest available catalyst drivers (11.2)
PS3:ran a sfc /scan and results showed no problems.

zigzag3143 · 21 Feb 2011

AurA said:

Hellos to evry1 seeing this thread. Now to my problem.

Getting the same BSOD over and over again ,especially while playing games like Bad Company 2 ,namely the dreaded "dxgmms1.sys" error along with the message PAGE_FAULT_IN_NON-PAGED_AREA or something in the similar terms. Happens after 10-15 mins of Gaming.

System details:
Windows 7 x64 is the original installed OS and an OEM version

- Age of system hardware: 10 Months
- What is the age of OS installation :same as no reinstalls of Windows done.

All required files are attached. Help would be gr8tly appreciated.

PS: Removed Norton Internet Security after being told to do so by many seven forums mods and users. Just using Windows defender until system is stable again.
PS2: Did a driver sweep and installed latest available catalyst drivers (11.2)
PS3:ran a sfc /scan and results showed no problems.

These were caused by the directX portion of your video driver. As a first step re-install using these.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Then I would remove Symantec which may in fact be causing the third problem and replace it with Microsoft Security Essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

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

The third problem is Memory corruption. Run memtest to check yours

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. 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.

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\022211-20280-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03290e50
Debug session time: Mon Feb 21 15:59:12.107 2011 (GMT-5)
System Uptime: 0 days 0:18:05.168
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa80840b6ac0, 0, fffff880045bcce5, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa80840b6ac0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880045bcce5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fb0e0
 fffffa80840b6ac0 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`045bcce5 488b02          mov     rax,qword ptr [rdx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880067eb750 -- (.trap 0xfffff880067eb750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880067eb908 rbx=0000000000000000 rcx=fffffa80067af000
rdx=fffffa80840b6ac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045bcce5 rsp=fffff880067eb8e0 rbp=fffffa8007719920
 r8=fffffa8003fd7601  r9=0000000000000000 r10=0000000000000000
r11=000000000000011d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19:
fffff880`045bcce5 488b02          mov     rax,qword ptr [rdx] ds:1a10:fffffa80`840b6ac0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031428c1 to fffff800030c3740

STACK_TEXT:  
fffff880`067eb5e8 fffff800`031428c1 : 00000000`00000050 fffffa80`840b6ac0 00000000`00000000 fffff880`067eb750 : nt!KeBugCheckEx
fffff880`067eb5f0 fffff800`030c182e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`067eb750 fffff880`045bcce5 : 00000000`ffffd978 00000000`0000000a fffffa80`067a9000 fffffa80`067aa9c0 : nt!KiPageFault+0x16e
fffff880`067eb8e0 fffff880`045b9ed3 : 00000000`00000000 fffffa80`03f1b308 00000000`000000bc 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffff880`067eb910 fffff880`045d465d : 00000000`00000000 fffff8a0`0c45df30 fffffa80`00000000 fffffa80`03fd7650 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`067ebae0 fffff880`045d4398 : fffff800`04477080 fffff880`045d3d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`067ebcd0 fffff880`045d3e96 : 00000000`00000000 fffffa80`06f5f9f0 00000000`00000080 fffffa80`06796410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`067ebd00 fffff800`03367c06 : 00000000`03424481 fffffa80`064b1a10 fffffa80`039cf040 fffffa80`064b1a10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`067ebd40 fffff800`030a1c26 : fffff800`0323de80 fffffa80`064b1a10 fffff800`0324bc40 fffff880`0121abf0 : nt!PspSystemThreadStartup+0x5a
fffff880`067ebd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`045bcce5 488b02          mov     rax,qword ptr [rdx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

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

0: kd> lmvm dxgmms1
start             end                 module name
fffff880`0459c000 fffff880`045e2000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: C:\Symbols\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Mon Jul 13 19:38:32 2009 (4A5BC578)
    CheckSum:         0004AD44
    ImageSize:        00046000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    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.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

AurA · 22 Feb 2011

zigzag3143 said:

These were caused by the directX portion of your video driver.

How can i uninstall the directX as well so that i can make a clean install of it??

DeanP · 22 Feb 2011

Leave the DirectX - do the graphics driver as Zigzag3143 (Ken J) requested.

AurA · 22 Feb 2011

Ok. Already did the 1st 2 steps as requested before i posted here :)
Now for the mem-test :crossed-fingers:

DeanP · 22 Feb 2011

Good luck. Just to let you know it can take some time. So don't stare at the screen for about 5 or 6 hours straight without getting yourself a break - might be best to get fresh air while it is testing your RAMs.

AurA · 22 Feb 2011

DeanP said:

Good luck. Just to let you know it can take some time. So don't stare at the screen for about 5 or 6 hours straight without getting yourself a break - might be best to get fresh air while it is testing your RAMs.

hahaha

No worries. Did memtest long back once on my old computer too. Cheers :)

AurA · 22 Feb 2011

Ok so far memtest has run 3 passes with no errors .will let it go on for 2 more passes.

so wat is my next step?

Sent using tapatalk

AurA · 22 Feb 2011

ran 5 passes. no errors.