BSOD on wondows 7 64-bit

[Zethen]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFFA7F847054C9
BCP2: 0000000000000001
BCP3: FFFFF88004932AB4
BCP4: 0000000000000007
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Seems to only happen when I run a full screen application, any assistence would be appreciated

View attachment 56616

 

[Capt.Jack Sparrow]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFFA7F847054C9
BCP2: 0000000000000001
BCP3: FFFFF88004932AB4
BCP4: 0000000000000007
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Seems to only happen when I run a full screen application, any assistence would be appreciated

View attachment 56616

Hello Welcome to SF,

I guess the issue is with your Direct X driver (dxgmms1.sys). First download the Display drivers from vendors website then Remove the Display driver completely disconnect from the Internet and install the drivers from the Download NOT from Windows update. Reinstall your Driect X.

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Update the Following Driver

RTL85n64.sys Tue Oct 03 08:06:17 2006
ALCWDM64.SYS Fri Oct 13 11:55:09 2006
nvmfdx64.sys Tue Jan 16 06:21:05 2007

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: fffffa7f847054c9, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88004932ab4, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac30e0
 fffffa7f847054c9 
FAULTING_IP: 
dxgmms1!VidSchiCaptureProcessName+44
fffff880`04932ab4 4885c9          test    rcx,rcx
MM_INTERNAL_CODE:  7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
CURRENT_IRQL:  0
FOLLOWUP_IP: 
dxgmms1!VidSchiCaptureProcessName+44
fffff880`04932ab4 4885c9          test    rcx,rcx
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  dxgmms1!VidSchiCaptureProcessName+44
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidSchiCaptureProcessName+44
BUCKET_ID:  X64_0x50_dxgmms1!VidSchiCaptureProcessName+44

Hope this helps,
Catpain

 

[Stevy22]

Yes dude Captain is always right.... FOllow the steps, you will be GTG

 

[Zethen]

I uninstalled and reinstalled my graphics card driver but went to went to install the end-user runtime for directx and as I had already installed it before it just stated there were no new updates. I am still getting the same BSOD error, anything I did wrong or anything else to try?

 

[Capt.Jack Sparrow]

I uninstalled and reinstalled my graphics card driver but went to went to install the end-user runtime for directx and as I had already installed it before it just stated there were no new updates. I am still getting the same BSOD error, anything I did wrong or anything else to try?

Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

You could also Run free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

If everything comes clean the follow this link http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html and Enable Driver Verifier

Good Luck,
Captain