physical memory dump BSOD. help plese

Hello,
I have problem with physical memory dump for a while. I tried registry cleaners but it didn't work. Can you help me? I attached BSOD rar file like in a tutorial.

HunterNG said:

Hello,
I have problem with physical memory dump for a while. I tried registry cleaners but it didn't work. Can you help me? I attached BSOD rar file like in a tutorial.

Eight of 18 of these were caused by your video driver.

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.

Three others were caused by pool corruption (Memory). Utorrent was present in two of three.

I would run memtest and remove utorrent to test.

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.

I also would run a system file check to verify (and repair) your system files.

SFC /SCANNOW Command - System File Checker

Finally in two Nod32 was the cause (eamonm.sys). I would remove it and replace with Microsoft Security Essentials

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

Let us know if you need further assistance

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\Windows_NT6_BSOD_jcgriff2\102310-13384-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c50000 PsLoadedModuleList = 0x82d98810
Debug session time: Sat Oct 23 13:45:25.671 2010 (GMT-4)
System Uptime: 0 days 8:56:11.045
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8eb16bb1, 89fb99e8, 89fb95c0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f )

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

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: c0000005, The exception code that was not handled
Arg2: 8eb16bb1, The address that the exception occurred at
Arg3: 89fb99e8, Exception Record Address
Arg4: 89fb95c0, Context Record Address

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::ReferenceAllocationForPreparation+f
8eb16bb1 8b31            mov     esi,dword ptr [ecx]

EXCEPTION_RECORD:  89fb99e8 -- (.exr 0xffffffff89fb99e8)
ExceptionAddress: 8eb16bb1 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT:  89fb95c0 -- (.cxr 0xffffffff89fb95c0)
eax=879778f8 ebx=00000000 ecx=00000000 edx=00000002 esi=86d16000 edi=86d16000
eip=8eb16bb1 esp=89fb9ab0 ebp=89fb9abc iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf:
8eb16bb1 8b31            mov     esi,dword ptr [ecx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

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:  00000000

EXCEPTION_PARAMETER2:  00000000

READ_ADDRESS: GetPointerFromAddress: unable to read from 82db8718
Unable to read MiSystemVaType memory at 82d98160
 00000000 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
8eb16bb1 8b31            mov     esi,dword ptr [ecx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8eb1a24c to 8eb16bb1

STACK_TEXT:  
89fb9abc 8eb1a24c 879778f8 00000001 00000000 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf
89fb9bb8 8eb3193e 9fa5d3e0 00000000 84dfe2c8 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x2f6
89fb9d18 8eb3222f 8761c8c8 84e3d130 89fb9d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
89fb9d28 8eb324cc 8761c8c8 82c8c3f1 86d0e788 dxgmms1!VidSchiSubmitQueueCommand+0x61
89fb9d3c 8eb32573 86d0e788 00000000 86d06948 dxgmms1!VidSchiRun_PriorityTable+0x24
89fb9d50 82e5e6d3 86d0e788 af1787a2 00000000 dxgmms1!VidSchiWorkerThread+0x7f
89fb9d90 82d100f9 8eb324f4 86d0e788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

STACK_COMMAND:  .cxr 0xffffffff89fb95c0 ; kb

FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f

BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f

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

thank you. the memory dumps have stopped.

it happened again. help please.