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/freeze when playing games

24 Feb 2012   #1

Microsoft Windows 7 Ultimate 64-bit
 
 
BSOD/freeze when playing games

I started getting this today for some reason. My setup had been the same for the last 6 months or so and out of nowhere while playing a game I had installed for a month I instantly got a BSOD. I tried updating my gfx drivers but didn't really help much at all.

I also get some random errors when trying to load them up now after a few BSODs (i.e. explorer.exe stops working then restarts, desktop manager error etc.)

My specs:
Windows 7 x64
Gigabyte MA770
Nvidia Geforce GTX 560 ti
Phenom II x4 940

No OCing involved

Here are the dump files

My System SpecsSystem Spec
.

24 Feb 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Based on the behavior you describe, check for file data corruption:
My System SpecsSystem Spec
24 Feb 2012   #3

Microsoft Windows 7 Ultimate 64-bit
 
 

sfc is still running atm but on my check disk, I didn't find any problems at all
My System SpecsSystem Spec
.


24 Feb 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by dashx4 View Post
sfc is still running atm but on my check disk, I didn't find any problems at all
Let us know the outcome. In the meantime, I finished analyzing the .dmp files. I would also appreciate it if you followed the http://www.sevenforums.com/crashes-d...tructions.html to provide us with more information for determining the root of the crashes.



Drivers that may be outdated:
Code:
Neo_0090	fffff880`040e1000	fffff880`040e6a00	Thu May 01 22:58:09 2008 (481a9f61)	00012d88		Neo_0090.sys
Rt64win7	fffff880`0406a000	fffff880`0409c000	Thu Feb 26 02:04:13 2009 (49a65b0d)	000361a5		Rt64win7.sys
Neo_0090.sys (unknown device... If this does not sound familiar, it may be malware related)
Rt64win7.sys



Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\dashx4\022412-19234-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`03294670 Debug session time: Fri Feb 24 18:39:30.983 2012 (UTC - 7:00) System Uptime: 0 days 0:02:25.232 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {ffffffffffffff8a, b, 1, fffff88013450144} Unable to load image \SystemRoot\system32\DRIVERS\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 : hardware ( nvlddmkm+221144 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: ffffffffffffff8a, memory referenced Arg2: 000000000000000b, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88013450144, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fe100 ffffffffffffff8a CURRENT_IRQL: b FAULTING_IP: nvlddmkm+221144 fffff880`13450144 104889 adc byte ptr [rax-77h],cl CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: firefox.exe TRAP_FRAME: fffff88009ebbf10 -- (.trap 0xfffff88009ebbf10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8005b2b000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88013450144 rsp=fffff88009ebc0a8 rbp=0000000000000000 r8=0000000000000001 r9=0000000000000000 r10=0000000000000010 r11=0000002247133bd4 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nvlddmkm+0x221144: fffff880`13450144 104889 adc byte ptr [rax-77h],cl ds:8600:ffffffff`ffffff8a=?? Resetting default scope MISALIGNED_IP: nvlddmkm+221144 fffff880`13450144 104889 adc byte ptr [rax-77h],cl LAST_CONTROL_TRANSFER: from fffff800030cb1e9 to fffff800030cbc40 STACK_TEXT: fffff880`09ebbdc8 fffff800`030cb1e9 : 00000000`0000000a ffffffff`ffffff8a 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx fffff880`09ebbdd0 fffff800`030c9e60 : 00000000`00000140 fffffa80`05117410 00000000`00000000 fffffa80`05b2b000 : nt!KiBugCheckDispatch+0x69 fffff880`09ebbf10 fffff880`13450144 : fffff880`134da018 fffffa80`05b2b000 fffffa80`05c36890 fffffa80`05b86000 : nt!KiPageFault+0x260 fffff880`09ebc0a8 fffff880`134da018 : fffffa80`05b2b000 fffffa80`05c36890 fffffa80`05b86000 fffffa80`05008600 : nvlddmkm+0x221144 fffff880`09ebc0b0 fffffa80`05b2b000 : fffffa80`05c36890 fffffa80`05b86000 fffffa80`05008600 fffffa80`05b86000 : nvlddmkm+0x2ab018 fffff880`09ebc0b8 fffffa80`05c36890 : fffffa80`05b86000 fffffa80`05008600 fffffa80`05b86000 fffff880`1341e812 : 0xfffffa80`05b2b000 fffff880`09ebc0c0 fffffa80`05b86000 : fffffa80`05008600 fffffa80`05b86000 fffff880`1341e812 fffffa80`05b2b000 : 0xfffffa80`05c36890 fffff880`09ebc0c8 fffffa80`05008600 : fffffa80`05b86000 fffff880`1341e812 fffffa80`05b2b000 fffffa80`05b2b000 : 0xfffffa80`05b86000 fffff880`09ebc0d0 fffffa80`05b86000 : fffff880`1341e812 fffffa80`05b2b000 fffffa80`05b2b000 00000000`00000000 : 0xfffffa80`05008600 fffff880`09ebc0d8 fffff880`1341e812 : fffffa80`05b2b000 fffffa80`05b2b000 00000000`00000000 fffffa80`05008680 : 0xfffffa80`05b86000 fffff880`09ebc0e0 fffffa80`05b2b000 : fffffa80`05b2b000 00000000`00000000 fffffa80`05008680 fffff8a0`0c202000 : nvlddmkm+0x1ef812 fffff880`09ebc0e8 fffffa80`05b2b000 : 00000000`00000000 fffffa80`05008680 fffff8a0`0c202000 00000000`00000001 : 0xfffffa80`05b2b000 fffff880`09ebc0f0 00000000`00000000 : fffffa80`05008680 fffff8a0`0c202000 00000000`00000001 fffff880`09ebc520 : 0xfffffa80`05b2b000 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+221144 fffff880`13450144 104889 adc byte ptr [rax-77h],cl SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+221144 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\dashx4\022412-20108-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03011000 PsLoadedModuleList = 0xfffff800`03256670 Debug session time: Fri Feb 24 18:26:54.776 2012 (UTC - 7:00) System Uptime: 0 days 6:10:49.056 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck DE, {2, fffff8a00e812ca8, fffff8a00ed12ca9, 1021538c0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d8a1 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* POOL_CORRUPTION_IN_FILE_AREA (de) A driver corrupted pool memory used for holding pages destined for disk. This was discovered by the memory manager when dereferencing the file. Arguments: Arg1: 0000000000000002 Arg2: fffff8a00e812ca8 Arg3: fffff8a00ed12ca9 Arg4: 00000001021538c0 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xDE PROCESS_NAME: IDMan.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800030444bd to fffff8000308dc40 STACK_TEXT: fffff880`08dd9a28 fffff800`030444bd : 00000000`000000de 00000000`00000002 fffff8a0`0e812ca8 fffff8a0`0ed12ca9 : nt!KeBugCheckEx fffff880`08dd9a30 fffff800`0305c532 : 00000000`00000000 fffffa80`07ed5e00 00000000`00000000 fffff880`08dd9c00 : nt! ?? ::FNODOBFM::`string'+0x2d8a1 fffff880`08dd9b20 fffff800`0305d495 : fffffa80`07ea2258 fffff800`032044f0 00000000`00000000 fffff800`00000000 : nt!CcPurgeCacheSection+0x172 fffff880`08dd9b90 fffff800`030b4a32 : fffffa80`07ed5e00 fffff800`032044f0 00000000`00000001 fffffa80`07ed5e00 : nt!CcPurgeAndClearCacheSection+0x75 fffff880`08dd9c40 fffff880`0143ecb0 : 00000000`002d4000 00000000`002d4000 fffff8a0`0e4fec70 fffffa80`04c5f180 : nt!CcSetFileSizesEx+0x2c6 fffff880`08dd9cc0 fffff880`014b737c : 00000000`00000000 7fffffff`ffffffff 00000000`000002d4 fffff880`08dda701 : Ntfs!NtfsSetBothCacheSizes+0x50 fffff880`08dd9d20 fffff880`014a54d9 : fffff880`08dda730 fffffa80`075e5740 00000000`00000001 00000000`00000000 : Ntfs!NtfsDeleteAllocation+0x2cc fffff880`08dd9e00 fffff880`014a62e6 : fffff880`08dda730 00000000`00000001 fffff980`15b21c38 00000000`00000001 : Ntfs!NtfsDeleteAllocationFromRecord+0x16d fffff880`08dd9ec0 fffff880`014c7033 : fffff880`08dda730 fffff8a0`0e4feb40 fffff8a0`0e548140 fffff880`08dda1c8 : Ntfs!NtfsDeleteFile+0x346 fffff880`08dda140 fffff880`01435cc9 : 00000000`00000000 fffff8a0`00000000 fffff880`08dda690 00000000`00006000 : Ntfs!NtfsCommonCleanup+0x1653 fffff880`08dda550 fffff800`0309a618 : fffff880`08dda690 fffff800`031bcfbd fffffa80`0618e880 00000000`00000002 : Ntfs!NtfsCommonCleanupCallout+0x19 fffff880`08dda580 fffff880`01435d42 : fffff880`01435cb0 fffffa80`04608598 fffff880`08dda900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8 fffff880`08dda660 fffff880`014d4a04 : fffff880`08dda730 fffff880`08dda730 fffff880`08dda730 00000000`43434646 : Ntfs!NtfsCommonCleanupOnNewStack+0x42 fffff880`08dda6d0 fffff880`010acbcf : fffff880`08dda730 fffffa80`08241c10 fffffa80`08241fb0 fffffa80`07f06010 : Ntfs!NtfsFsdCleanup+0x144 fffff880`08dda940 fffff880`010ab6df : fffffa80`04b3b8e0 00000000`00000000 fffffa80`03c84000 fffffa80`08241c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`08dda9d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpDispatch+0xcf STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+2d8a1 fffff800`030444bd cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2d8a1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xDE_nt!_??_::FNODOBFM::_string_+2d8a1 BUCKET_ID: X64_0xDE_nt!_??_::FNODOBFM::_string_+2d8a1 Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\dashx4\022412-19515-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03260670 Debug session time: Fri Feb 24 12:14:41.408 2012 (UTC - 7:00) System Uptime: 0 days 1:02:16.062 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6566346566346262 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Steam.exe CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88003192b78 -- (.exr 0xfffff88003192b78) ExceptionAddress: fffff8000305e2a4 (nt!EtwEventEnabled+0x0000000000000024) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88003192c20 -- (.trap 0xfffff88003192c20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80050ad050 rbx=0000000000000000 rcx=7fffffffffffffff rdx=fffff800031d3210 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000305e2a4 rsp=fffff88003192db8 rbp=000000000000141b r8=0000000000000000 r9=0000000000000064 r10=0000000000000063 r11=fffff88003163180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!EtwEventEnabled+0x24: fffff800`0305e2a4 44394150 cmp dword ptr [rcx+50h],r8d ds:b530:80000000`0000004f=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000308f5fe to fffff80003097c10 STACK_TEXT: fffff880`03191c58 fffff800`0308f5fe : 00000000`00000400 fffff880`01936b8f fffff880`031923d0 fffff800`030c3830 : nt!KeBugCheck fffff880`03191c60 fffff800`030c34fd : fffff800`032a171c fffff800`031dec30 fffff800`0301b000 fffff880`03192b78 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`03191c90 fffff800`030c22d5 : fffff800`031e2028 fffff880`03191d08 fffff880`03192b78 fffff800`0301b000 : nt!RtlpExecuteHandlerForException+0xd fffff880`03191cc0 fffff800`030d3361 : fffff880`03192b78 fffff880`031923d0 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x415 fffff880`031923a0 fffff800`030972c2 : fffff880`03192b78 fffff880`03163180 fffff880`03192c20 fffffa80`0551e758 : nt!KiDispatchException+0x135 fffff880`03192a40 fffff800`03095bca : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`063c0c50 : nt!KiExceptionDispatch+0xc2 fffff880`03192c20 fffff800`0305e2a4 : fffff800`031865cc fffffa80`0003a76b fffffa80`05601060 fffff880`03163180 : nt!KiGeneralProtectionFault+0x10a fffff880`03192db8 fffff800`031865cc : fffffa80`0003a76b fffffa80`05601060 fffff880`03163180 fffff800`0312c646 : nt!EtwEventEnabled+0x24 fffff880`03192dc0 fffff800`031880df : 00000002`8f727f73 00000000`0000ae19 00000000`0000b8af fffffa80`00000064 : nt!PpmEventTraceRecordedUtility+0x3c fffff880`03192e60 fffff800`031b2b62 : 00000000`00000064 00000000`00000000 00000002`8f727f73 00000002`75d03a38 : nt!PpmPerfRecordUtility+0x21f fffff880`03192ed0 fffff800`030a30ac : fffff880`03163180 fffffa80`0003a781 fffffa80`05601060 00000000`00000081 : nt!PpmPerfAction+0x22 fffff880`03192f00 fffff800`0309a765 : 00000000`00000000 fffffa80`07880b60 00000000`00000000 fffff800`031b2b40 : nt!KiRetireDpcList+0x1bc fffff880`03192fb0 fffff800`0309a57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`095efbf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`0308f5fe 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
  4. Loading Dump File [D:\Kingston\BSODDmpFiles\dashx4\022412-27222-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`032a0670 Debug session time: Fri Feb 24 10:33:15.513 2012 (UTC - 7:00) System Uptime: 0 days 0:06:04.167 Loading Kernel Symbols ............................................................... ................................................................ ................................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff8801357fde0} Unable to load image \SystemRoot\system32\DRIVERS\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+2e3de0 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff8801357fde0 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: plugin-contain CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800030d71e9 to fffff800030d7c40 STACK_TEXT: fffff880`031d9ce8 fffff800`030d71e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`031d9cf0 fffff800`030d56b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`031d9e30 fffff880`1357fde0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 00000000`009b0a48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x2e3de0 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+2e3de0 fffff880`1357fde0 c3 ret SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+2e3de0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e7b7204 FAILURE_BUCKET_ID: X64_0x7f_8_nvlddmkm+2e3de0 BUCKET_ID: X64_0x7f_8_nvlddmkm+2e3de0 Followup: MachineOwner ---------
  5. Loading Dump File [D:\Kingston\BSODDmpFiles\dashx4\022412-20592-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a8670 Debug session time: Fri Feb 24 10:25:51.738 2012 (UTC - 7:00) System Uptime: 0 days 0:00:41.003 Loading Kernel Symbols ............................................................... ................................................................ ................................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, fffff98008064001, 34a5, fffff780c0000000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041284, A PTE or the working set list is corrupt. Arg2: fffff98008064001 Arg3: 00000000000034a5 Arg4: fffff780c0000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41284 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800031375a7 to fffff800030dfc40 STACK_TEXT: fffff880`033936f8 fffff800`031375a7 : 00000000`0000001a 00000000`00041284 fffff980`08064001 00000000`000034a5 : nt!KeBugCheckEx fffff880`03393700 fffff800`031038e7 : 00000000`000034a5 fffff880`033938f0 fffffa80`06360010 fffffa80`06fd4050 : nt! ?? ::FNODOBFM::`string'+0x4ac3 fffff880`03393740 fffff800`033f0c39 : fffff980`08064000 fffff8a0`030782c0 00000000`00000000 00000000`00000000 : nt!MmUnmapViewInSystemCache+0x208 fffff880`03393a20 fffff800`0310342b : 00000000`00000000 fffffa80`03b6d020 00000000`00000000 00000000`00140000 : nt!CcUnmapVacb+0x5d fffff880`03393a60 fffff800`03124a08 : 00000000`00000001 fffffa80`06fd4050 fffffa80`07008600 fffffa80`06fd4000 : nt!CcUnmapVacbArray+0x1bb fffff880`03393af0 fffff800`031252fe : fffffa80`07008620 fffffa80`07008620 fffff880`009e8180 fffffa80`06fd4000 : nt!CcDeleteSharedCacheMap+0x154 fffff880`03393b50 fffff800`03125938 : fffff800`032e1800 fffff880`03393c58 fffffa80`07719c10 fffff800`032e18b8 : nt!CcWriteBehind+0x54e fffff880`03393c00 fffff800`030ea001 : fffffa80`03c114f0 fffff800`033d6901 fffff800`032e18c0 00000000`00000005 : nt!CcWorkerThread+0x1c8 fffff880`03393cb0 fffff800`0337afee : 00000000`00000000 fffffa80`03c42040 00000000`00000080 fffffa80`03b8b400 : nt!ExpWorkerThread+0x111 fffff880`03393d40 fffff800`030d15e6 : fffff880`03163180 fffffa80`03c42040 fffff880`0316dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03393d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4ac3 fffff800`031375a7 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ac3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3 BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3 Followup: MachineOwner ---------
  1. Caused by your display card or display card driver.
  2. Could be related to hard disk errors or hard disk file system corruption. Other possible cause is Drivers...
  3. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
    Thanks to JMH for helping with my understanding of this crash.
  4. Possible causes are Memory problems... Hardware... Lack of Windows updates... Drivers...
  5. Possible causes are Memory problems... 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 by doing your normal routine after each step 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 can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.
  • If you are overclocking any hardware, please stop.


  • 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.


  • Monitor temperatures during the following tests Use the following programs to monitor the temperature.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
My System SpecsSystem Spec
25 Feb 2012   #5

Microsoft Windows 7 Ultimate 64-bit
 
 

It looks like it's my RAM. memtest found an error though not sure which stick it is. I switched the slots up and still getting bsod and it doesn't exactly tell me which one it is (I did get a system_service_exception once but that's it).

Also something I forgot to mention. Before my first bsod, my system wouldn't boot up completely after turning it off overnight so I figure it might be my RAM settings since I had to manually input the timings + voltage. Had set them back to auto and it boots up just fine.
My System SpecsSystem Spec
25 Feb 2012   #6

Windows 7 Home Premium 64 Bit
 
 

If you are getting crashes frequently enough, you could just run your system with one RAM module, see if it crashes, move the module to another slot, see if it crashes, etc. If the module does not work in any slots, it may be bad. Test the other module the same way.

If they both crash in all slots, then we should consider other troubleshooting steps, but first try that method.

Remember to use safe ESD steps.

Also: System Info - See Your System Specs step 7 would help us out a lot.
My System SpecsSystem Spec
25 Feb 2012   #7

Microsoft Windows 7 Ultimate 64-bit
 
 

Both RAM just got me a bsod on the 1st and 2nd slot. Not sure if it's a RAM or mobo issue now.
also edited profile with specs
My System SpecsSystem Spec
25 Feb 2012   #8

Windows 7 Home Premium 64 Bit
 
 

The crashes may have been due to lack of RAM. 64-bit requires 2 GB, so if you have two 1 GB modules, you will need to test them individually with Memtest86+ to determine which is bad.
My System SpecsSystem Spec
25 Feb 2012   #9

Microsoft Windows 7 Ultimate 64-bit
 
 

I have a 2x2 gb ram (4gb total). Now testing the 3rd slot and so far this is the most stable one I got with 1+ hour of not getting any bsod just from browsing.
My System SpecsSystem Spec
25 Feb 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Ah okay, makes sense. Keep us updated how the third slot works out.
My System SpecsSystem Spec
Reply

 BSOD/freeze when playing games





Thread Tools



Similar help and support threads for2: BSOD/freeze when playing games
Thread Forum
Freeze and BSOD when playing games on Facebook BSOD Help and Support
BSOD and occasional screen freeze (especially when playing games) BSOD Help and Support
Freeze when usually playing games. BSOD Help and Support
Solved BSOD or freeze while playing games BSOD Help and Support
W7 64 bit FREEZE when playing games or net BSOD Help and Support
Computer freeze when playing all games ! BSOD Help and Support
Freeze when playing games Gaming

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:47 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33