BSOD MEMORY_MANAGEMENT

[BigwillG]

Hello, I have been having a problem with my 1st build computer. When i first made this computer nothing was wrong, but after i installed a Windows again. it started giving bsod with memory management, i have no idea what to do here are my specs

Intel Core i7 2600k cpu
ASUS maximus IV Extreme-z
EVGA 460 SLI
16 gb ddr3

 

[passion8059]

Had same problem with my system.

You'll have to run memtest stick by stick to see if you have a duff stick if not need to check memory setting in bios to check right voltage frequency etc.

 

[BigwillG]

Alright, will do thanks

 

[BigwillG]

ok i ran memtest, this is the sight i downloaded it from http://www.memtest86.com/ i ran 3 memtest programs but when i get to the third i get and error and it refers me to and FAQ question number 2 what do i do now?

 

[BigwillG]

Should i just read the manual on my Bios to see how much i bump it up?

 

[mikeburr]

Hi,

MEMORY_MANAGEMENT may indicate driver related corruption issues,

0x1A MEMORY_MANAGEMENT

You may need to enable driver verifier and analyze the verifier enabled dumps to get more information

Enable Driver Verifier

If you would like help analyzing the dumps, please upload them to skydrive and post a link. They are typically in c:\windows\minidump\ or a kernel/full memory dump may exist at c:\windows\memory.dmp

How to upload to skydrive

 

[BigwillG]

Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WD-20111211-2034.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
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03454000 PsLoadedModuleList = 0xfffff800`03699670
Debug session time: Sun Dec 11 22:34:46.919 2011 (GMT-6)
System Uptime: 0 days 6:13:51.500
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8013c44010, fffff8800f3e0354, 0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+156354 )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8013c44010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3e0354, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+156354
fffff880`0f3e0354 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`05da34f0 fffff880`0ff425f7 : fffffa80`13c44010 fffff880`0ff8eec4 fffffa80`13c44010 fffff880`0ff10843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`05da3a10 fffff880`0ff432bc : fffff8a0`12da21e0 fffff8a0`12da21e0 00000000`00000080 fffffa80`13c44010 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`05da3a60 fffff880`0ff176b3 : 00000000`00000001 fffffa80`10f00000 00000000`00000000 fffff880`000000d2 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`05da3a90 fffff880`0ff43e0f : fffffa80`10efb658 ffffffff`fffe7960 fffffa80`13c44010 fffff880`0f237dc0 : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`05da3b40 fffff880`0f237ec1 : fffffa80`124287b0 00000000`00000080 00000000`00000000 fffffa80`10efb010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`05da3bc0 fffff800`0376bfee : 00000000`04d68133 fffffa80`10f19060 fffffa80`0d0745f0 fffffa80`10f19060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`05da3c00 fffff800`034c25e6 : fffff800`03646e80 fffffa80`10f19060 fffff800`03654cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05da3c40 00000000`00000000 : fffff880`05da4000 fffff880`05d9e000 fffff880`05cf2a30 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+156354
fffff880`0f3e0354 ?? ???

SYMBOL_NAME: nvlddmkm+156354

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da

FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys

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



this is what i got, i think its the Graphics Card drivers

 

[mikeburr]

This indicates that the system was unable to recover after Windows detected a possible hang with the video card. One possibility is that the NVidia driver needs to be upgraded/downgraded, another possibility is that the video card/driver doesn;t play well with TDR and TDR needs to be disabled (note that the system will hang if the video card times out and will not bug check)

http://mikemstech.blogspot.com/2011/12/troubleshooting-0x116-videotdrerror.html