I'm having the BSOD too :(

[RxDawg]

So I read the stickied BSOD forum post and tried to follow the instructions to the best of my ability. I've attached the two files requested as a zip folder.

So here's the story... have a custom built PC that worked like a champ for about a year. Then slowly I started having some crashing problems. They seem to be fairly random and also when I'm gaming more often than not. I tried updating everything and running all kinds of scans to see if it was a virus. Nothing showed up and it kept crashing. So a few days ago I formated everything and reinstalled windows 7. And I'm still getting the BSOD.

Here is a brief summary of what the BSOD says:
Check for Bios updates.

Try new video hardware.

Disable BIOS memory options such as caching or shadowing.

Technical info:
*** STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF88014B96CEE, 0xFFFFF88004A436A8, 0xFFFFF99004A42F10)

*** dxgmmsl.sys - Address FFFFF88014B96CEE base at FFFFF88014B76000, DateStamp 4d3fa174


This is Windows 7 64bit.

It is an OEM version, although I purchased it through a retailer (didn't know it was OEM or what that meant at the time) and installed it on the computer myself. Not sure if that means anything important or not?

The computer is about a year old and all the hardware with it. It was built from scratch.

The current OS installation is only a few days old, but fully auto updated.

 

[zigzag3143]

So I read the stickied BSOD forum post and tried to follow the instructions to the best of my ability. I've attached the two files requested as a zip folder.

So here's the story... have a custom built PC that worked like a champ for about a year. Then slowly I started having some crashing problems. They seem to be fairly random and also when I'm gaming more often than not. I tried updating everything and running all kinds of scans to see if it was a virus. Nothing showed up and it kept crashing. So a few days ago I formated everything and reinstalled windows 7. And I'm still getting the BSOD.

Here is a brief summary of what the BSOD says:
Check for Bios updates.

Try new video hardware.

Disable BIOS memory options such as caching or shadowing.

Technical info:
*** STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF88014B96CEE, 0xFFFFF88004A436A8, 0xFFFFF99004A42F10)

*** dxgmmsl.sys - Address FFFFF88014B96CEE base at FFFFF88014B76000, DateStamp 4d3fa174


This is Windows 7 64bit.

It is an OEM version, although I purchased it through a retailer (didn't know it was OEM or what that meant at the time) and installed it on the computer myself. Not sure if that means anything important or not?

The computer is about a year old and all the hardware with it. It was built from scratch.

The current OS installation is only a few days old, but fully auto updated.

One probably caused by your video card, the other memory corruption by a drive (also possibly your video driver).

I would re-install the video driver and run memtest

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.



Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

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.

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\041911-21918-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 Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0284e000 PsLoadedModuleList = 0xfffff800`02a8be50
Debug session time: Tue Apr 19 20:29:12.455 2011 (GMT-4)
System Uptime: 0 days 3:47:17.172
Loading Kernel Symbols
...............................................................
.....Image path too long, possible corrupt data.
...........................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88014b96cee, fffff88004a436a8, fffff88004a42f10}

Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88014b96cee, The address that the exception occurred at
Arg3: fffff88004a436a8, Exception Record Address
Arg4: fffff88004a42f10, Context Record Address

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

Image path too long, possible corrupt data.
Image path too long, possible corrupt data.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`14b96cee 488b18          mov     rbx,qword ptr [rax]

EXCEPTION_RECORD:  fffff88004a436a8 -- (.exr 0xfffff88004a436a8)
ExceptionAddress: fffff88014b96cee (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000022)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff88004a42f10 -- (.cxr 0xfffff88004a42f10)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800938f000
rdx=fffffa8007142770 rsi=fffffa8007652120 rdi=fffffa800938f000
rip=fffff88014b96cee rsp=fffff88004a438e0 rbp=fffffa8007654368
 r8=fffffa80070b2a01  r9=0000000000000100 r10=0000000000000000
r11=00000000000000a6 r12=0000000000000082 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22:
fffff880`14b96cee 488b18          mov     rbx,qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af60e0
 0000000000000000 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`14b96cee 488b18          mov     rbx,qword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88014b93ed3 to fffff88014b96cee

STACK_TEXT:  
fffff880`04a438e0 fffff880`14b93ed3 : 00000000`00000000 fffffa80`07652120 00000000`00000082 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22
fffff880`04a43910 fffff880`14bae65d : 00000000`00000100 fffff8a0`02b6dc30 fffffa80`00000000 fffffa80`070b2aa0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`04a43ae0 fffff880`14bae398 : fffff800`03bdc080 fffff880`14badd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04a43cd0 fffff880`14bade96 : 00000000`00000000 fffffa80`0a421610 00000000`00000080 fffffa80`090f9410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04a43d00 fffff800`02b617c6 : 00000000`03285f51 fffffa80`093575e0 fffffa80`06a0dae0 fffffa80`093575e0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04a43d40 fffff800`0289cc26 : fffff800`02a38e80 fffffa80`093575e0 fffff800`02a46c40 fffff880`01234534 : nt!PspSystemThreadStartup+0x5a
fffff880`04a43d80 00000000`00000000 : fffff880`04a44000 fffff880`04a3e000 fffff880`04a43690 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgmms1
7 errors : !dxgmms1 (fffff88014b96351-fffff88014b96f81)
fffff88014b96350  21 *10  8b  81  34  0c  00  00  f7  d0  85  c2  74  04  32  c0 !...4.......t.2.
...
fffff88014b963d0  74  26  45  33  c0  f6  c2  01  74 *17  49  8b  81  38  0c  00 t&E3....t.I..8..
...
fffff88014b96440  89 *8d  24  b8  00  00  00  eb  0b  48  8b  cf  48  89  8c  24 ..$......H..H..$
...
fffff88014b967e0  48 *88  78  18  48  89  78  20  48  8b  d0  8b  ce  ff  15  e5 H.x.H.x H.......
...
fffff88014b96b30  18  49  3b  d6  74  28  41  3b  f6 *74  12  48  8b  07  48  8b .I;.t(A;.t.H..H.
...
fffff88014b96ef0  0f  85  aa  fe  ff  ff  41  80  fe *00  74  18  48  8b  43  70 ......A...t.H.Cp
...
fffff88014b96f80  00 *b8  02  00  00  00  ff  15  54  04  ff  ff  b9  02  00  00 ........T.......

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88004a42f10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

 

[RxDawg]

Thanks for the tips. I was leaning towards the video card too, but you never know. I'll try the driver sweeper and reinstalling the drivers to see if that helps first.

Then I'll try out the memtest you suggested. I did try the repair from my Windows 7 CD. It ran a memory test without any issues, but I think it was a faster test than what you are suggesting.

Again thanks for the suggestions and the quick reply.

 

[RxDawg]

I wanted to give it some time to make sure it was fixed. But the only thing I did was use the driver sweeper program you linked to clean out the video driver. Then I went into safe mode and installed the same video driver software. It's been about a week and so far so good. Interesting that it could of been something so simple as that. But for now, I'm going to report this as fixed. Thanks for the help!

 

[RxDawg]

Well of course I spoke too soon. It's not fixed and I indeed got the BSOD again while in the middle of a game. I'll try the other suggestions and get back to ya.