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's whenever I play games


20 Jan 2012   #1

Windows 7 Home Premium 64-bit (6.1, build 7601)
 
 
BSoD's whenever I play games

My PC seems to run fine as long as it isn't doing any CPU-requiring jobs such as playing games.

This may be caused by dust inside my cabinet, which I won't dare to open since it'll cancel my insurance. I'd like to avoid getting it repaired since they'll do anything they can to charge me money for sending them a "working" computer.

Windows 7 64-bit Home Premium
Original OS and OEM
PC is from April 2009
OS was re-installed when repair was needed in the summer of 2011

I don't know if this helps or not but I guess it can't hurt:

BCCode: 19
BCP1: 0000000000000020
BCP2: FFFFFA80061A18B0
BCP3: FFFFFA80061A1EB0
BCP4: 000000000460A490
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

My System SpecsSystem Spec
.

20 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\012012-17440-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03403000 PsLoadedModuleList = 0xfffff800`03648670 Debug session time: Fri Jan 20 13:18:29.184 2012 (UTC - 7:00) System Uptime: 0 days 0:41:11.917 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, fffffa80061a18b0, fffffa80061a1eb0, 460a490} GetPointerFromAddress: unable to read from fffff800036b2100 Probably caused by : memory_corruption ( nt!MmDeleteTeb+10f ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000020, a pool block header size is corrupt. Arg2: fffffa80061a18b0, The pool entry we were looking for within the page. Arg3: fffffa80061a1eb0, The next pool entry. Arg4: 000000000460a490, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: fffffa80061a18b0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800035adcae to fffff8000347fc40 STACK_TEXT: fffff880`0a31c9d8 fffff800`035adcae : 00000000`00000019 00000000`00000020 fffffa80`061a18b0 fffffa80`061a1eb0 : nt!KeBugCheckEx fffff880`0a31c9e0 fffff800`03755e37 : fffffa80`06153720 fffffa80`06153720 fffffa80`6c646156 00000000`00000000 : nt!ExDeferredFreePool+0x12da fffff880`0a31ca90 fffff800`0376d026 : fffff880`0a31cf90 fffffa80`06153720 00000000`c0000008 fffff6fc`40050530 : nt!MmDeleteTeb+0x10f fffff880`0a31cb20 fffff800`0376bfa2 : fffffa80`0615f470 fffffa80`06153720 fffff880`0a31cfc0 fffff880`0a31cd00 : nt!PspInsertThread+0x786 fffff880`0a31cca0 fffff800`0376fe35 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`0a31d4d0 : nt!PspCreateThread+0x246 fffff880`0a31cf20 fffff800`0347eed3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateThreadEx+0x25d fffff880`0a31d670 fffff800`0347b470 : fffff800`037725b4 00000000`00000000 00000000`00000000 fa8007fd`19380460 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0a31d878 fffff800`037725b4 : 00000000`00000000 00000000`00000000 fa8007fd`19380460 fffffa80`086c2460 : nt!KiServiceLinkage fffff880`0a31d880 fffff800`03473b52 : fffff880`00000072 fffff880`0a31db28 00000000`00000001 00000000`00000000 : nt!RtlpCreateUserThreadEx+0x138 fffff880`0a31d9a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpWorkerFactoryCreateThread+0x92 STACK_COMMAND: kb FOLLOWUP_IP: nt!MmDeleteTeb+10f fffff800`03755e37 488d4c2430 lea rcx,[rsp+30h] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!MmDeleteTeb+10f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x19_20_nt!MmDeleteTeb+10f BUCKET_ID: X64_0x19_20_nt!MmDeleteTeb+10f Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\012012-19718-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`03652670 Debug session time: Fri Jan 20 12:07:21.920 2012 (UTC - 7:00) System Uptime: 0 days 6:11:45.528 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 18, {0, fffffa8005a66580, 2, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49d71 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* REFERENCE_BY_POINTER (18) Arguments: Arg1: 0000000000000000, Object type of the object whose reference count is being lowered Arg2: fffffa8005a66580, Object whose reference count is being lowered Arg3: 0000000000000002, Reserved Arg4: ffffffffffffffff, Reserved The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object the driver calls a kernel routine to increment the reference count of the object. When the driver is done with the pointer the driver calls another kernel routine to decrement the reference count. Drivers must match calls to the increment and decrement routines. This bugcheck can occur because an object's reference count goes to zero while there are still open handles to the object, in which case the fourth parameter indicates the number of opened handles. It may also occur when the object’s reference count drops below zero whether or not there are open handles to the object, and in that case the fourth parameter contains the actual value of the pointer references count. Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x18 PROCESS_NAME: League of Lege CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000342a944 to fffff80003489c40 STACK_TEXT: fffff880`09a253e8 fffff800`0342a944 : 00000000`00000008 00000000`00000000 fffffa80`05a66580 00000000`00000002 : nt!KeBugCheckEx fffff880`09a253f0 fffff800`037807b9 : fffff880`09a25c60 fffff880`09a256e0 00000000`00000000 fffff880`00000006 : nt! ?? ::FNODOBFM::`string'+0x49d71 fffff880`09a25450 fffff800`037ad4cd : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`75212400 : nt!ObpWaitForMultipleObjects+0x2d3 fffff880`09a25920 fffff800`03488ed3 : fffff880`09a25c60 fffffa80`054d2c00 fffff880`00001f80 fffff800`03485887 : nt!NtWaitForMultipleObjects32+0xec fffff880`09a25b70 00000000`75212e19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`116cf0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75212e19 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+49d71 fffff800`0342a944 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+49d71 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+49d71 BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+49d71 Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\012012-19016-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03459000 PsLoadedModuleList = 0xfffff800`0369e670 Debug session time: Fri Jan 20 05:54:52.067 2012 (UTC - 7:00) System Uptime: 0 days 0:52:52.799 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800034d88e2, fffff8800a508ee0, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800034d88e2, Address of the instruction which caused the bugcheck Arg3: fffff8800a508ee0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!SwapContext_PatchXRstor+0 fffff800`034d88e2 0fae29 xrstor [rcx] CONTEXT: fffff8800a508ee0 -- (.cxr 0xfffff8800a508ee0) rax=0000000000000001 rbx=fffff8000364be80 rcx=fffff8800a509dc0 rdx=0000000000000000 rsi=fffffa8007081660 rdi=fffffa80062a4b60 rip=fffff800034d88e2 rsp=fffff8800a5098c0 rbp=fffff8800a509d70 r8=fffffa800604a0e8 r9=0000000000000000 r10=fffffffffffffffe r11=0000000000200246 r12=000000007ef62000 r13=000000000ac9fd20 r14=fffffa800604a060 r15=fffff80000b96080 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00210202 nt!SwapContext_PatchXRstor: fffff800`034d88e2 0fae29 xrstor [rcx] Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: League of Lege CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800034d88e2 STACK_TEXT: fffff880`0a5098c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXRstor CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff800034d8803 - nt!SwapContext_PatchXSave+2 [ 01:21 ] fffff800034d88e4 - nt!SwapContext_PatchXRstor+2 (+0xe1) [ 09:29 ] fffff800034d8aa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf) [ 01:21 ] fffff800034d8b86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3) [ 09:29 ] 4 errors : !nt (fffff800034d8803-fffff800034d8b86) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT_LARGE STACK_COMMAND: .cxr 0xfffff8800a508ee0 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE Followup: memory_corruption ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\012012-19110-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03466000 PsLoadedModuleList = 0xfffff800`036ab670 Debug session time: Thu Jan 19 14:46:33.691 2012 (UTC - 7:00) System Uptime: 0 days 0:40:59.424 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {848, 2, 0, fffff800034e5791} Probably caused by : memory_corruption Followup: memory_corruption --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000848, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800034e5791, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003715100 0000000000000848 CURRENT_IRQL: 2 FAULTING_IP: nt!SwapContext+11 fffff800`034e5791 807e4900 cmp byte ptr [rsi+49h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0xA PROCESS_NAME: SearchIndexer. TRAP_FRAME: fffff88008a36df0 -- (.trap 0xfffff88008a36df0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff88008a370c0 rbx=0000000000000000 rcx=0000000000000000 rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000 rip=fffff800034e5791 rsp=fffff88008a36f80 rbp=fffffa80098756a0 r8=fffffa800843c3d8 r9=0000000000000000 r10=fffffffffffffffd r11=fffffa80059d8948 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!SwapContext+0x11: fffff800`034e5791 807e4900 cmp byte ptr [rsi+49h],0 ds:1f80:00000000`00000049=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034e21e9 to fffff800034e2c40 STACK_TEXT: fffff880`08a36ca8 fffff800`034e21e9 : 00000000`0000000a 00000000`00000848 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`08a36cb0 fffff800`034e0e60 : fffff800`03658e80 fffffa80`0934db60 fffff800`0344d3c0 fffff880`009f0180 : nt!KiBugCheckDispatch+0x69 fffff880`08a36df0 fffff800`034e5791 : 00000000`00000001 00000000`00000000 00000000`00000001 00001f80`00a30120 : nt!KiPageFault+0x260 fffff880`08a36f80 fffff800`034e54da : 00000000`00000000 ffffffff`fffffffe fffff880`07fa7c10 00000000`00000002 : nt!SwapContext+0x11 fffff880`08a36fc0 fffff800`034e7f32 : fffffa80`098756a0 fffffa80`098756a0 00000000`00000000 00000000`00000008 : nt!KiSwapContext+0x7a fffff880`08a37100 fffff800`034e744a : fffff880`0f43071b fffffa80`079c2000 fffffa80`00000000 fffffa80`0571d010 : nt!KiCommitThreadWait+0x1d2 fffff880`08a37190 fffff800`037d977f : 00000000`00000003 fffff880`08a374e0 00000000`00000001 00000000`00000006 : nt!KeWaitForMultipleObjects+0x272 fffff880`08a37450 fffff800`037d9aee : fffffa80`05510001 fffffa80`06a88640 00000000`00000001 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294 fffff880`08a37920 fffff800`034e1ed3 : fffffa80`098756a0 00000000`072ce8a8 fffff880`08a37b88 00000000`00000000 : nt!NtWaitForMultipleObjects+0xe5 fffff880`08a37b70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff800034e5803 - nt!SwapContext_PatchXSave+2 [ 01:21 ] fffff800034e58e4 - nt!SwapContext_PatchXRstor+2 (+0xe1) [ 09:29 ] fffff800034e5aa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf) [ 01:21 ] fffff800034e5b86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3) [ 09:29 ] 4 errors : !nt (fffff800034e5803-fffff800034e5b86) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT_LARGE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE Followup: memory_corruption ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\011912-19063-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`03694670 Debug session time: Thu Jan 19 13:24:39.868 2012 (UTC - 7:00) System Uptime: 0 days 1:44:20.601 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8800f226161, fffff88004df0668, fffff88004defec0} Probably caused by : hardware ( dxgmms1!VIDMM_GLOBAL::StartPreparation+35 ) Followup: MachineOwner --------- 1: 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800f226161, The address that the exception occurred at Arg3: fffff88004df0668, Exception Record Address Arg4: fffff88004defec0, 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::StartPreparation+35 fffff880`0f226161 0233 add dh,byte ptr [rbx] EXCEPTION_RECORD: fffff88004df0668 -- (.exr 0xfffff88004df0668) ExceptionAddress: fffff8800f226161 (dxgmms1!VIDMM_GLOBAL::StartPreparation+0x0000000000000035) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000c0000001 Attempt to read from address 00000000c0000001 CONTEXT: fffff88004defec0 -- (.cxr 0xfffff88004defec0) rax=fffffa8006458790 rbx=00000000c0000001 rcx=fffff8a00f4b8d50 rdx=fffff8a00d40b260 rsi=000000000000004f rdi=fffffa8008688000 rip=fffff8800f226161 rsp=fffff88004df08a0 rbp=fffff8a00d40b260 r8=fffffa800755fd20 r9=0000000000000001 r10=0000000000000000 r11=000000000000004f r12=0000000000000000 r13=0000000000000000 r14=fffffa800755fd30 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 dxgmms1!VIDMM_GLOBAL::StartPreparation+0x35: fffff880`0f226161 0233 add dh,byte ptr [rbx] ds:002b:00000000`c0000001=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT 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: 0000000000000000 EXCEPTION_PARAMETER2: 00000000c0000001 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036fe100 00000000c0000001 FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::StartPreparation+35 fffff880`0f226161 0233 add dh,byte ptr [rbx] BUGCHECK_STR: 0x7E MISALIGNED_IP: dxgmms1!VIDMM_GLOBAL::StartPreparation+35 fffff880`0f226161 0233 add dh,byte ptr [rbx] LAST_CONTROL_TRANSFER: from fffff8800f21de34 to fffff8800f226161 STACK_TEXT: fffff880`04df08a0 fffff880`0f21de34 : 00000000`c0000001 00000000`0000004f 00000000`00000000 fffffa80`086397a0 : dxgmms1!VIDMM_GLOBAL::StartPreparation+0x35 fffff880`04df08d0 fffff880`0f23865d : 00000000`00000000 fffff8a0`0d40b260 fffffa80`00000000 fffffa80`0755fd30 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x3a0 fffff880`04df0aa0 fffff880`0f238398 : fffff800`048a5080 fffff880`0f237d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`04df0c90 fffff880`0f237e96 : 00000000`00000000 fffffa80`08f8b010 00000000`00000080 fffffa80`08639010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`04df0cc0 fffff800`03766fee : 00000000`02815718 fffffa80`08636210 fffffa80`0548bb30 fffffa80`08636210 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`04df0d00 fffff800`034bd5e6 : fffff800`03641e80 fffffa80`08636200 fffff800`0364fcc0 fffff880`0121e384 : nt!PspSystemThreadStartup+0x5a fffff880`04df0d40 00000000`00000000 : fffff880`04df1000 fffff880`04deb000 fffff880`04df0640 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::StartPreparation+35 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr 0xfffff88004defec0 ; kb MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\011912-21840-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03454000 PsLoadedModuleList = 0xfffff800`03699670 Debug session time: Thu Jan 19 11:05:20.949 2012 (UTC - 7:00) System Uptime: 0 days 1:35:25.681 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff960001a0c59, fffff880045fdb70, 0} Probably caused by : hardware ( win32k!UserSessionSwitchLeaveCrit+41 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c000001d, Exception code that caused the bugcheck Arg2: fffff960001a0c59, Address of the instruction which caused the bugcheck Arg3: fffff880045fdb70, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: win32k!UserSessionSwitchLeaveCrit+41 fffff960`001a0c59 c4 ??? CONTEXT: fffff880045fdb70 -- (.cxr 0xfffff880045fdb70) rax=fffff900c01d7f0c rbx=0000000000000001 rcx=fffffa80086ea880 rdx=fffff8000364b450 rsi=00000000000001c6 rdi=0000000000575de9 rip=fffff960001a0c59 rsp=fffff880045fe550 rbp=000000000000022d r8=0000000000000000 r9=000000000000000d r10=fffff80003454000 r11=fffff880045fe550 r12=0000000000000000 r13=000000000008008b r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 win32k!UserSessionSwitchLeaveCrit+0x41: fffff960`001a0c59 c4 ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 MISALIGNED_IP: win32k!UserSessionSwitchLeaveCrit+41 fffff960`001a0c59 c4 ??? LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960001a0c59 STACK_TEXT: fffff880`045fe550 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!UserSessionSwitchLeaveCrit+0x41 FOLLOWUP_IP: win32k!UserSessionSwitchLeaveCrit+41 fffff960`001a0c59 c4 ??? SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!UserSessionSwitchLeaveCrit+41 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr 0xfffff880045fdb70 ; kb MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\zuiaki\Windows_NT6_BSOD_jcgriff2\011212-21746-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0344d000 PsLoadedModuleList = 0xfffff800`03692670 Debug session time: Thu Jan 12 11:56:55.618 2012 (UTC - 7:00) System Uptime: 0 days 0:10:35.351 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960001a3fef, fffff880038ea080, 0} Probably caused by : win32k.sys ( win32k!TimersProc+73 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff960001a3fef, Address of the instruction which caused the bugcheck Arg3: fffff880038ea080, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!TimersProc+73 fffff960`001a3fef 8b5348 mov edx,dword ptr [rbx+48h] CONTEXT: fffff880038ea080 -- (.cxr 0xfffff880038ea080) rax=000000000f99a027 rbx=ffffffffffffffe8 rcx=000000000009b1d1 rdx=000000000000012d rsi=000000007fffffff rdi=0000000000000000 rip=fffff960001a3fef rsp=fffff880038eaa60 rbp=0000000000000010 r8=fffffa8008708bb8 r9=0000000000000000 r10=fffffffffffffffd r11=0000000000000000 r12=0000000000000000 r13=fffff960003c44e0 r14=0000000000000002 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203 win32k!TimersProc+0x73: fffff960`001a3fef 8b5348 mov edx,dword ptr [rbx+48h] ds:002b:00000000`00000030=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff960001a4ae7 to fffff960001a3fef STACK_TEXT: fffff880`038eaa60 fffff960`001a4ae7 : 00000000`00000000 fffff960`003c4cb0 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x73 fffff880`038eaab0 fffff960`0013511c : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000360 : win32k!RawInputThread+0x9ab fffff880`038eab80 fffff960`001b539a : fffffa80`00000002 fffff880`038c8f00 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58 fffff880`038eabb0 fffff800`034c8ed3 : fffffa80`08805060 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36 fffff880`038eabe0 000007fe`fdb31eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`004bfdb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdb31eea FOLLOWUP_IP: win32k!TimersProc+73 fffff960`001a3fef 8b5348 mov edx,dword ptr [rbx+48h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!TimersProc+73 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdcd5a STACK_COMMAND: .cxr 0xfffff880038ea080 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!TimersProc+73 BUCKET_ID: X64_0x3B_win32k!TimersProc+73 Followup: MachineOwner ---------
If you are overclocking anything, please stop.
  1. Possible cause is Drivers...
  2. Possible causes are Memory problems... Drivers...
  3. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...
  4. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
  5. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
  6. See 3.
  7. See 3.
Thanks to Dave76 for help understanding possible causes.
  • 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).


  • Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

    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.


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

  • Let Verifier run until you get a few .dmp files to upload and have been instructed to disable it.


Disable Verifier before the next steps.

My System SpecsSystem Spec
Reply

 BSoD's whenever I play games




Thread Tools



Similar help and support threads for2: BSoD's whenever I play games
Thread Forum
BSOD or freezing when trying to play games BSOD Help and Support
BSOD When I play most of my games. BSOD Help and Support
Solved BSOD 116 when attempting to play games BSOD Help and Support
Solved BSOD only when I play MMO games BSOD Help and Support
BSOD when trying to play games (code d1) BSOD Help and Support
BSOD everytime I try to play any games. BSOD Help and Support
BSOD when I play games 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 02:15 AM.
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