Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Faulty memory?

17 Dec 2009   #1
Rothel

Windows 7
 
 
BSOD Faulty memory?

Ive been getting BSOD's for months now. every time i take it back to be looked at under warranty they say that its all fine hardware wise and theres nothing wrong with it.
It started constanly blue screening this morning so i have formatted and have a fresh install of windows 7 on with no updates and no drivers.
it then blue screened while i was out side. ive uploaded the mem dump file.
if anyone could take a look at it and let me know what they find that would be amazingly helpful.


My System SpecsSystem Spec
.

18 Dec 2009   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Rothel View Post
Ive been getting BSOD's for months now. every time i take it back to be looked at under warranty they say that its all fine hardware wise and theres nothing wrong with it.
It started constanly blue screening this morning so i have formatted and have a fresh install of windows 7 on with no updates and no drivers.
it then blue screened while i was out side. ive uploaded the mem dump file.
if anyone could take a look at it and let me know what they find that would be amazingly helpful.
Hi and welcome. Little doubt about what caused this crash. You were runnning winsat, and the video driver folded

I would re install the video driver
run a system file check to verify and repair your system files
dl memtestx86 and run it for several hours

Good Luck

Ken J+


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\121809-13291-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02805000 PsLoadedModuleList = 0xfffff800`02a42e50
Debug session time: Thu Dec 17 23:07:27.535 2009 (GMT-5)
System Uptime: 0 days 1:50:36.111
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880041dba6c, fffff88005676af0, 0}

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

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880041dba6c, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88005676af0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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::xWaitForAllEngines+a4
fffff880`041dba6c 483901          cmp     qword ptr [rcx],rax

CONTEXT:  fffff88005676af0 -- (.cxr 0xfffff88005676af0)
rax=000000000003cf15 rbx=fffffa8005728000 rcx=00fff8a008227fd0
rdx=fffffa800561f000 rsi=fffff8a0082243a0 rdi=fffffa8005728000
rip=fffff880041dba6c rsp=fffff880056774d0 rbp=0000000000000001
 r8=fffffa80057293a8  r9=0000000000000001 r10=0000000000000018
r11=0000000000000000 r12=0000000000000000 r13=0000000000000003
r14=0000000000000000 r15=00fff8a008227fd0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0xa4:
fffff880`041dba6c 483901          cmp     qword ptr [rcx],rax ds:002b:00fff8a0`08227fd0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  WinSAT.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880041dba6c

STACK_TEXT:  
fffff880`056774d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0xa4


FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+a4
fffff880`041dba6c 483901          cmp     qword ptr [rcx],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88005676af0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+a4

BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+a4

Followup: MachineOwner
---------
[IMG]file:///C:/Users/K/AppData/Local/Temp/moz-screenshot-2.png[/IMG][IMG]file:///C:/Users/K/AppData/Local/Temp/moz-screenshot-3.png[/IMG]
My System SpecsSystem Spec
Reply

 BSOD Faulty memory?




Thread Tools





Similar help and support threads
Thread Forum
Is my RAM faulty? Various BSOD
Hi, I have been experiencing a number of issues with my PC lately. Specs below: Windows 7 64 bit Home Premium Intel 4670K Haswell CPU Gigabyte Z87X-OC Motherboard
Hardware & Devices
Recurring BSOD - Memory_Management (Faulty SSD?)
Hi all, this is my first post on W7 forum's so give me heads up on protocol if anything is missed. ----------------------------------------------------------------------------------- Short story: Computer has been giving me BSOD's increasingly at random over the last 3 weeks. BSOD has...
BSOD Help and Support
Can a faulty power supply course BSOD?
Hi Can a faulty power supply course BSOD? Thx
BSOD Help and Support
BSOD, faulty driver
Hello guys, as you know I'm new to this forum and was seeking help on an issue that has been stressing me out and none of the troubleshooting I have done has really helped me clearly. The driver that is causing my bsod is affiliated with the process ntoskrnl.exe. I don't really know what driver...
BSOD Help and Support
Faulty Graphics card replaced and Still Getting BSOD
Hi there For a few weeks now i have had a few BSOD's One being irql_not_less_or_equal_too But that i have tracked down to a faulty graphics card which the manufacture has now replaced (Ati 5870 Hd) The machine seemed to be running fine and then last night i got " A driver has overrun a...
BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 12:44.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App