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 during usage/overnight (MEMORY_MANAGEMENT and others)

11 Feb 2012   #1
Nightreaver

Win7 U x64
 
 
BSOD during usage/overnight (MEMORY_MANAGEMENT and others)

So, i build a new system in december, then it started with (memory) errors.

it took me time to figure out that it was necessary to raise VTT CPU to get the memory stable. im between 1.75v - 2.00v now.

it was stable some weeks then i made a windows update and installed latest 290.xx nvidia beta drivers it solved some probs but i think it was the reason for new problems.
so i uninstalled, cleaned and reinstalled official nvidia 285.xx today.


most time it crashes when im not at the pc... sometimes overnight when rendering/simulating things.


specs:
Microsoft Windows 7 Ultimate - Service Pack 1
CPU Typ HexaCore Intel Core i7 Extreme Edition, 3800 MHz (38 x 100)
Motherboard Name Asus P9X79 Deluxe (2 PCI-E x1, 4 PCI-E x16, 8 DDR3 DIMM, Audio, Gigabit LAN)
Motherboard Chipset Intel Patsburg X79, Intel Sandy Bridge-E
Memory 16360 MB (DDR3-1333 DDR3 SDRAM)
DIMM-A1: Corsair Vengeance CMZ16GX3M4A1600C9 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) (8-8-8-22 @ 592 MHz) (7-7-7-19 @ 518 MHz) (6-6-6-16 @ 444 MHz)
DIMM-B1: Corsair Vengeance CMZ16GX3M4A1600C9 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) (8-8-8-22 @ 592 MHz) (7-7-7-19 @ 518 MHz) (6-6-6-16 @ 444 MHz)
DIMM-C1: Corsair Vengeance CMZ16GX3M4A1600C9 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) (8-8-8-22 @ 592 MHz) (7-7-7-19 @ 518 MHz) (6-6-6-16 @ 444 MHz)
DIMM-D1: Corsair Vengeance CMZ16GX3M4A1600C9 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) (8-8-8-22 @ 592 MHz) (7-7-7-19 @ 518 MHz) (6-6-6-16 @ 444 MHz)

BIOS Typ AMI (12/22/2011) (v0906)

Age of system is about 1/2 month now
almost everything is new hardware, except display adapter (NVIDIA GeForce 8800 GTX)

link of files: https://skydrive.live.com/redir.aspx?cid=92c46a745c56ac37&resid=92C46A745C56AC37!141&parid=92C46A745C56AC37!139&authkey=!AEXl5 rfrVysgSz0

have i missed something? tell me plz,

thanks 4 help


My System SpecsSystem Spec
.
11 Feb 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\BSODDmpFiles\Nightreaver\Windows_NT6_BSOD_jcgriff2\021112-24570-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`03062670 Debug session time: Sat Feb 11 11:02:46.390 2012 (GMT-7) System Uptime: 0 days 5:36:47.591 Loading Kernel Symbols ............................................................... ................................................................ .................................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff70001080000, 349f9, 349fb000693d2} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 00000000000349f9 Arg4: 000349fb000693d2 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: 3dsmax.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800a9f7380 -- (.trap 0xfffff8800a9f7380) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000400 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002eb62f8 rsp=fffff8800a9f7510 rbp=0000000000000001 r8=fffffa8018b24a00 r9=0000000073bca000 r10=0000000000000400 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!MmProbeAndLockPages+0x118: fffff800`02eb62f8 410fb601 movzx eax,byte ptr [r9] ds:d6c0:00000000`73bca000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e2d74c to fffff80002e99c40 STACK_TEXT: fffff880`0a9f7218 fffff800`02e2d74c : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000349f9 : nt!KeBugCheckEx fffff880`0a9f7220 fffff800`02e97d6e : 00000000`00000000 00000000`73bca000 fffff880`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x46f0d fffff880`0a9f7380 fffff800`02eb62f8 : fffffa80`00000000 00000000`00002040 00000000`00000000 fffff800`02fc8350 : nt!KiPageFault+0x16e fffff880`0a9f7510 fffff880`09381a25 : fffffa80`18b23000 00000000`00000000 fffff8a0`00000002 00000000`73890000 : nt!MmProbeAndLockPages+0x118 fffff880`0a9f7620 fffff880`09380bbc : fffffa80`15785ea0 fffff8a0`0d819a70 00000000`00000098 00000000`00400000 : dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0x229 fffff880`0a9f76b0 fffff880`0937b6a0 : fffff8a0`0d819a70 fffff8a0`0d819a70 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::LockAllocationBackingStore+0x80 fffff880`0a9f7720 fffff880`0936faf3 : fffffa80`1928d260 fffffa80`15776000 fffffa80`15776001 fffff880`0936f700 : dxgmms1!VIDMM_APERTURE_SEGMENT::CommitResource+0x1c4 fffff880`0a9f7770 fffff880`0936c763 : 00000000`00000000 fffffa80`17ee1000 00000000`00000000 fffffa80`17a49710 : dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xbb fffff880`0a9f77d0 fffff880`0938665d : 00000000`00000000 fffff8a0`0c7bcf00 fffffa80`00000000 fffffa80`16586d10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xccf fffff880`0a9f79a0 fffff880`09386398 : fffff800`00b96080 fffff880`09385d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`0a9f7b90 fffff880`09385e96 : 00000000`00000000 fffffa80`15f59780 00000000`00000080 fffffa80`1575c010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`0a9f7bc0 fffff800`03134fee : 00000000`fffffc32 fffffa80`1575a620 fffffa80`0cd7f890 fffffa80`1575a620 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`0a9f7c00 fffff800`02e8b5e6 : fffff800`0300fe80 fffffa80`1575a620 fffff800`0301dcc0 fffff880`0443a384 : nt!PspSystemThreadStartup+0x5a fffff880`0a9f7c40 00000000`00000000 : fffff880`0a9f8000 fffff880`0a9f2000 fffff880`0a9f6e10 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 fffff880`09381a25 4c8b1d8cd6fdff mov r11,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`0935f0b8)] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 FAILURE_BUCKET_ID: X64_0x1a_5003_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 BUCKET_ID: X64_0x1a_5003_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 Followup: MachineOwner ---------
  2. Loading Dump File [E:\BSODDmpFiles\Nightreaver\Windows_NT6_BSOD_jcgriff2\020712-19952-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a2670 Debug session time: Mon Feb 6 19:29:18.964 2012 (GMT-7) System Uptime: 0 days 15:47:12.761 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8014b20cd0, fffff80000b9c3d8, fffffa8016254010} *** WARNING: Unable to verify timestamp for asmthub3.sys *** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys Probably caused by : asmthub3.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8014b20cd0, Physical Device Object of the stack Arg3: fffff80000b9c3d8, Functional Device Object of the stack Arg4: fffffa8016254010, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa8016254010 DEVICE_OBJECT: fffffa8014b4f8a0 DRIVER_OBJECT: fffffa8014a81060 IMAGE_NAME: asmthub3.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ecb4aa9 MODULE_NAME: asmthub3 FAULTING_MODULE: fffff8800b7db000 asmthub3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f47cd2 to fffff80002ed9c40 STACK_TEXT: fffff800`00b9c388 fffff800`02f47cd2 : 00000000`0000009f 00000000`00000003 fffffa80`14b20cd0 fffff800`00b9c3d8 : nt!KeBugCheckEx fffff800`00b9c390 fffff800`02ee55fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x34a90 fffff800`00b9c430 fffff800`02ee5496 : fffffa80`16165168 fffffa80`16165168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`00b9c4a0 fffff800`02ee537e : 00000084`52f726e9 fffff800`00b9cb18 00000000`003796de fffff800`03053e48 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9caf0 fffff800`02ee5167 : 00000029`59992dc4 00000029`003796de 00000029`59992dc2 00000000`000000de : nt!KiTimerExpiration+0x1be fffff800`00b9cb90 fffff800`02ed196a : fffff800`0304fe80 fffff800`0305dcc0 00000000`00000000 fffffa80`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_asmthub3.sys BUCKET_ID: X64_0x9F_IMAGE_asmthub3.sys Followup: MachineOwner ---------
  3. Loading Dump File [E:\BSODDmpFiles\Nightreaver\Windows_NT6_BSOD_jcgriff2\020612-21216-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090670 Debug session time: Sun Feb 5 19:02:42.706 2012 (GMT-7) System Uptime: 0 days 10:42:54.827 Loading Kernel Symbols ............................................................... ................................................................ .................................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff88007a46168, fffff88007a459c0, fffff80002e77f69} Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+114 ) Followup: MachineOwner --------- 10: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff88007a46168 Arg3: fffff88007a459c0 Arg4: fffff80002e77f69 Debugging Details: ------------------ EXCEPTION_RECORD: fffff88007a46168 -- (.exr 0xfffff88007a46168) ExceptionAddress: fffff80002e77f69 (nt!RtlSubtreePredecessor+0x0000000000000009) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88007a459c0 -- (.cxr 0xfffff88007a459c0) rax=01008ba0e4b0c466 rbx=0000000000010128 rcx=0000000000010000 rdx=0000000000010128 rsi=fffffa801cf52700 rdi=0000000000000000 rip=fffff80002e77f69 rsp=fffff88007a463a8 rbp=fffffa801cf52708 r8=ffffffffffffffff r9=ffffffffffffffff r10=fffff880009d1080 r11=0000000000010000 r12=ffffffffffffffff r13=fffffa80138f3e90 r14=0000000000002000 r15=0000000000000001 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!RtlSubtreePredecessor+0x9: fffff800`02e77f69 488b4810 mov rcx,qword ptr [rax+10h] ds:002b:01008ba0`e4b0c476=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: msiexec.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fa100 ffffffffffffffff FOLLOWUP_IP: Ntfs!NtfsExtendedCompleteRequestInternal+114 fffff880`04462e84 488b5c2450 mov rbx,qword ptr [rsp+50h] FAULTING_IP: nt!RtlSubtreePredecessor+9 fffff800`02e77f69 488b4810 mov rcx,qword ptr [rax+10h] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff80002eac4c4 to fffff80002e77f69 STACK_TEXT: fffff880`07a463a8 fffff800`02eac4c4 : fffff8a0`12f5a520 00000000`00000000 00000000`00140014 fffff8a0`0b8ce50e : nt!RtlSubtreePredecessor+0x9 fffff880`07a463b0 fffff880`043a2633 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlDeleteNoSplay+0x7c fffff880`07a463e0 fffff880`043a02c8 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`138f3800 : fltmgr!TreeUnlinkNoBalance+0x13 fffff880`07a46410 fffff880`043be2af : 00000000`00000010 fffffa80`138f3800 fffff880`07a46480 fffff880`043c09a1 : fltmgr!TreeUnlinkMulti+0x148 fffff880`07a46460 fffff880`043c0a04 : ffffffff`ffffffff fffffa80`1cd11160 fffffa80`138f3800 fffffa80`1cf52680 : fltmgr!DeleteNameCacheNodes+0x9f fffff880`07a464a0 fffff880`043ce2bf : fffffa80`1cd11160 fffffa80`1cf52680 00000000`00000000 00000000`00000000 : fltmgr!PurgeStreamNameCache+0xc4 fffff880`07a464e0 fffff880`043c5a10 : fffffa80`1a3fbaa0 fffffa80`138f3800 00000000`00000000 fffffa80`1a02d070 : fltmgr!FltpPurgeVolumeNameCache+0x7f fffff880`07a46520 fffff880`043c0b9b : fffffa80`138f3800 00000000`00000000 fffffa80`1a02d070 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04 fffff880`07a46560 fffff880`043a0eca : fffffa80`21e3d460 fffffa80`0d874de0 fffff880`06517180 fffffa80`16309b60 : fltmgr!FltpReinstateNameCachingAllFrames+0x4b fffff880`07a46590 fffff800`02ecb021 : 00000000`00000000 00000000`00000fff 00000000`00000000 ffffc9b3`753cc45d : fltmgr!FltpPassThroughCompletion+0x8a fffff880`07a465d0 fffff880`04462e84 : fffffa80`2511c6f0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`07a466c0 fffff880`044ef20c : fffff8a0`14370bc0 fffffa80`138f6180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x114 fffff880`07a46700 fffff880`04460574 : fffffa80`2511c6f0 fffffa80`25181010 fffff880`07a46801 fffff880`07a46800 : Ntfs!NtfsCommonSetInformation+0xef3 fffff880`07a467e0 fffff880`0439dbcf : fffffa80`25181368 fffffa80`25181010 fffffa80`2511c6f0 fffff880`07a46808 : Ntfs!NtfsFsdSetInformation+0x11c fffff880`07a46860 fffff880`0439c6df : fffffa80`0d874de0 fffffa80`25181010 fffffa80`0d874d00 fffffa80`25181010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`07a468f0 fffff800`031a7063 : 00000000`00000062 fffff880`07a46b60 00000000`00000000 fffffa80`1973af20 : fltmgr!FltpDispatch+0xcf fffff880`07a46950 fffff800`02ec6ed3 : 00000000`00000a10 fffffa80`223e4b60 00000000`032ee288 fffff880`00000062 : nt!NtSetInformationFile+0x91f fffff880`07a46a70 00000000`76d2158a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`032ee268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d2158a SYMBOL_STACK_INDEX: b SYMBOL_NAME: Ntfs!NtfsExtendedCompleteRequestInternal+114 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce792f9 STACK_COMMAND: .cxr 0xfffff88007a459c0 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114 BUCKET_ID: X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114 Followup: MachineOwner ---------
  1. Caused by DirectX, graphics card, or graphics card driver.
  2. Caused by your USB 3.0 device driver being unresponsive to the system asking the USB 3.0 device to shut down or start up again.
  3. Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...
Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
  • If you are overclocking any hardware, please stop.


  • Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts

    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts


  • Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.


  • Code:
    TuneUpUtilitiesDriver64	fffff880`0c589000	fffff880`0c591000	Thu Sep 17 05:54:52 2009 (4ab2238c)	000052de		TuneUpUtilitiesDriver64.sys
    I notice TuneUpUtilities on your system. Please remove the program as it is likely to make your system less stable the more it is used. Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

    In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.


  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log


  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
12 Feb 2012   #3
Nightreaver

Win7 U x64
 
 

so, i got some new bsod ... i havent done anything of your notes yet, but i will a soon as there is a little time to do so.

ive included the new dumps, together with the old ones. (ive tried to install windbg myself, but setup gives me an error during installing)

the error is high priority... the 2/3 can wait cause just happend one time so far... the other multiple times a day .

so, are all caused by the same error? i cant change the display card easily, because its connected to the watercooling system. so if it's damaged... there must be a way to proof it, to force the error/crash.

i getting crazy "rectangles" on my screen when i open taskman with ctrl+alt+del.

i cant use memtest86 to test memory... because it gives me a lot of error outside physical memory amout, so i now, there are a kind of "fake" errors.. but i cant filter out fake from true... i havent seen any other errors so far.


so will someone please analyze the dumps again, to give a better option where to start?

thank you


PS: i use tuneup for starting services "on demand", is there another way to do that?
PPS: May i install daemontools without the sptd driver?
My System SpecsSystem Spec
.

13 Feb 2012   #4
Nightreaver

Win7 U x64
 
 

can someone pls debug those dumps, so i can look into myself... what it was caused by and so on?! (like in 2nd port maybe shorter)


thx
My System SpecsSystem Spec
13 Feb 2012   #5
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
021212-20467-01.dmp
BugCheck 4E, {99, 1c6cf3, 2, 40eb32}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
PFN_LIST_CORRUPT (4e)
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  3dsmax.exe
Bug Check 0x4E: PFN_LIST_CORRUPT
Code:
021312-19390-01.dmp
BugCheck 1A, {41790, fffffa800c7b9f90, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
MEMORY_MANAGEMENT (1a)
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  3dsmax.exe
Bug Check 0x1A: MEMORY_MANAGEMENT
Code:
021312-25428-01.dmp
BugCheck 1A, {5003, fffff70001080000, 188e91, 188e8f00301d22}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46f0d )
MEMORY_MANAGEMENT (1a)
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  3dsmax.exe
Bug Check 0x1A: MEMORY_MANAGEMENT
My System SpecsSystem Spec
15 Feb 2012   #6
Nightreaver

Win7 U x64
 
 

I left firefox open over night, with some sites open. and left some simulations running.

today i found out that some files written from memory to disc, are corrupted and some images on sites i left open looked weired.
so do windows windows/programs sometime that why they crash.

I also get a warning that the display driver was resettet because it has crashed

---------
so, ive tested the memory a third time, and found (for this time 1) module that was throwing erros... i removed it and everything seem okay, atleast for this.

now ive got the problems with the direct/display error.
ive run furmark without problems so far, maybe directx error?

any howto for a CLEAN directx/nvidia install? thanks
My System SpecsSystem Spec
04 Mar 2012   #7
Nightreaver

Win7 U x64
 
 

Memory Error came from the Memory Kit that i have used. I use another one now, and everthing works perfectly. memtest86 wasn't able to detect it correctly every time. it only found the error 1 out of 4 times.

display error came from damaged graphics adapter, it is a 8800GTX so its very old, baking helped a lot at least in windows and with the crashes, but i'll buy a new one in the next days.

thank you.
My System SpecsSystem Spec
04 Mar 2012   #8
writhziden

Windows 7 Home Premium 64 Bit
 
 

Glad you found both errors; very nice troubleshooting! In the future, if you find you really do need to re-install DirectX, see Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details to do so.
My System SpecsSystem Spec
Reply

 BSOD during usage/overnight (MEMORY_MANAGEMENT and others)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD or other crash Overnight
This has happened a few times now, once while I was out to lunch. I haven't ever seen the BSOD, so I'm not completely certain that's what occurred, but I have a feeling someone here might be able to help anyway. This computer has changed hands a few times. A while after I started using it, I...
BSOD Help and Support
BSOD after I left it on overnight, need help!
I was downloading some stuff and I left it overnight. In the morning, I went to turn it off and go to school. It worked fine in the morning as well, I even surfed the web bit. When I returned after school, I turned on my computer I put in my password and when I got to my desktop, after 3 seconds,...
BSOD Help and Support
BSOD, High memory usage programs, Memory_management
When I'm playing armed assualt 2 operation arrowhead (when it mostly happens) my computer will crash giving me a memory_management error I'm not sure how to find more details about the errors specifically. all of my information is in the files attached :)
BSOD Help and Support
Overnight BSOD
Basic Spec - x64 - the original installed OS on the system? - YES - an OEM or full retail version? Full Retail? tech friend installed for me... before he went on vacation... - What is the age of system (hardware)? - 6days - What is the age of OS installation (have you re-installed the...
BSOD Help and Support
BSOD overnight crashes
Hi, My system is homebuilt, CPU, motherboard, memory etc. have all been in use for at least 2 years. A few months ago I installed a 60GB SSD as my system drive. I have Windows 7 Ultimate 64 bit installed. For the most part everything seems to work quite well. Since installing the SSD I have an...
BSOD Help and Support
Overnight BSOD's
I recently built a new machine and have been having difficulties with BSOD's overnight. They happen when I have stepped away from the computer for an extended period of time. I can stress the heck out of the system during the day and as long as the computer is active it is fine, but as soon as it...
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 09:08.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App