Random BSOD MEMORY_MANAGMENT

Sl4y

New Member
#1
Hi, This is my first post so not expecting anyone to go out of their way. But any advice would be greatly appreciated.;)

I have removed all CPU OC and bios tweaks but still haven't managed to eliminate this problem. Memory isnt OC'd.

BSOD can occur randomly but generally 'seems' to happen when opening a random program ie. VLC, firefox etc

Even though my pc crashed less than an hour ago, I don't have a mini dump newer than 12/28/11.

Hopefully this will be enough info to generate some ideas! Let me know if extra details are required. Cheers!
 


Attachments

Sl4y

New Member
#2
This is killing me :/ anychance someone has had a look see yet?
 


Trouble

Noob Whisperer
#3
This is killing me :/ anychance someone has had a look see yet?
If that is truly the case, then I would expect more than a single dump file that is practically two months old.
DUMP:
Code:
BugCheck 116, {fffffa800cf754e0, fffff88004d1f51c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\[B][U][COLOR=#ff0000]VirtuWDDM.sys[/COLOR][/U][/B], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]VirtuWDDM.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [U][B][COLOR=#ff0000]VirtuWDDM.sys[/COLOR][/B][/U]
[U][B][COLOR=#ff0000]Probably caused by : VirtuWDDM.sys ( VirtuWDDM+851c )[/COLOR][/B][/U]
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cf754e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004d1f51c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP: 
VirtuWDDM+851c
fffff880`04d1f51c 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`06c86a48 fffff880`04ebe000 : 00000000`00000116 fffffa80`0cf754e0 fffff880`04d1f51c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06c86a50 fffff880`04e91867 : fffff880`04d1f51c fffffa80`0a681000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06c86a90 fffff880`04ebde0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0cf754e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`06c86b40 fffff880`04f8cec1 : fffffa80`0ce23d50 00000000`00000080 00000000`00000000 fffffa80`0a4a4410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`06c86bc0 fffff800`03535fee : 00000000`01d42089 fffffa80`0a2a1b60 fffffa80`07928040 fffffa80`0a2a1b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`06c86c00 fffff800`0328c5e6 : fffff800`03410e80 fffffa80`0a2a1b60 fffff800`0341ecc0 fffff880`01228384 : nt!PspSystemThreadStartup+0x5a
fffff880`06c86c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
VirtuWDDM+851c
fffff880`04d1f51c 4883ec28        sub     rsp,28h
SYMBOL_NAME:  VirtuWDDM+851c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: VirtuWDDM
IMAGE_NAME:  VirtuWDDM.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4dfe17bc
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_VirtuWDDM.sys
BUCKET_ID:  X64_0x116_IMAGE_VirtuWDDM.sys
Followup: MachineOwner
So you need to attend to that first
VirtuWDDM.sys 6/19/2011 Associated with Lucidlogix virtu update, uninstall or as a last resort rename extension from .sys to .OLD
Additionally
RTCore64.sys 5/25/2005 RivaTuner if it's not RivaTuner then you're on your own because there are many third party products that use that driver to access CPU data/registers to set voltages and such (CPUGenie, RMClock, etc.,) same deal update, uninstall or rename.
FNETURPX.SYS 10/3/2008 FNet Turbo HDD USB Driver (maybe) Welcome to PQI Website again update, uninstall or rename.
GEARAspiWDM.sys 5/18/2009 from here Driver updates - GEAR Software
All of the above with the exception of the one that actually seems to be causing the BSOD pre-date Windows 7 RTM and should be addressed.
Additionall if Blue Screens continue:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Good luck
Randy
 


Sl4y

New Member
#4
Sorry to bump this thread again,

I just wanted to pop in and THANK RANDY for taking the time to help! Haven't had a single BSOD since I followed his instructions. So as we say in Australia, cheers Randy you're a bloody legend mate!!!!:D
 


Trouble

Noob Whisperer
#5
You're welcome. And thank you for posting back and updating your thread with that information. It is always good to hear back and learn that you have managed to resolve your problem.
Thanks for joining our community and we hope to continue to see you around the forum.
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.