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: Bluescreen problem while playing games


25 Jan 2012   #1

Windows 7 x64
 
 
Bluescreen problem while playing games

I did a chkdsk/mem test and all the others typically suggested steps, plus a virus scan with Microsoft Security Essentials (which might not appear on the PERFMON test) and Malwarebytes and they came back fine. My video card driver is current and the Alienware site has a page for my drivers and those are up to date (athough driverfinder found a few things I could update, but when I ran this program in the past and updated drivers, it just caused me problems, because they weren't listed on the Alienware page for my system) .

All my hardware has been the same since I got the computer and I never had bluescreens until recently playing DCUO and then it occured in other games after, that it never had before. I also have had alot of firefox tabs open lately, not sure if that's causing this, but I never had problems for a year or more, before, doing that.

EDIT*** App Crash View showed the Bluescreens I experienced were from : WerFault.exe -Shut down unexpectedly. I read on another page disabling Werfault.exe (not sure how the instructions were different from what I see) could fix it but I don't know. I am just adding this info to assist whoever can help me here. My system also never runs slow or anything. Everything related to performance seems fine when it just suddenly bluescreens.

Is Windows 7 . . .
- 64-bit
- Windows 7
- full retail version
- Alienware

- What is the age of system (hardware)? 1.6
- What is the age of OS installation (have you re-installed the OS?) 1.6/no

zipped files & screenshot of BSOD:


My System SpecsSystem Spec
.

25 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [H:\BSODDmpFiles\Jessicka\Windows_NT6_BSOD_jcgriff2\012512-15459-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`03456670 Debug session time: Wed Jan 25 15:46:02.615 2012 (UTC - 7:00) System Uptime: 0 days 1:36:52.630 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000096, fffff8000329d8f0, fffff8800e59a000, 0} Probably caused by : hardware ( nt!PspReturnQuota+80 ) Followup: MachineOwner --------- 9: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000096, Exception code that caused the bugcheck Arg2: fffff8000329d8f0, Address of the instruction which caused the bugcheck Arg3: fffff8800e59a000, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction. FAULTING_IP: nt!PspReturnQuota+80 fffff800`0329d8f0 6f outs dx,dword ptr [rsi] CONTEXT: fffff8800e59a000 -- (.cxr 0xfffff8800e59a000) rax=000000000000ef3c rbx=0000000000f5ef4c rcx=fffffa800e3a9840 rdx=0000000000f6de88 rsi=0000000000000000 rdi=0000000000000070 rip=fffff8000329d8f0 rsp=fffff8800e59a9e8 rbp=fffffa800e3a9840 r8=0000000000010000 r9=0000000000000070 r10=0000000000000000 r11=fffff8800e59ab38 r12=fffff800034381a0 r13=0000000000000000 r14=0000000000000000 r15=fffffa80116497a0 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!PspReturnQuota+0x80: fffff800`0329d8f0 6f outs dx,dword ptr [rsi] ds:002b:00000000`00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: DCGAME.EXE CURRENT_IRQL: 0 MISALIGNED_IP: nt!PspReturnQuota+80 fffff800`0329d8f0 6f outs dx,dword ptr [rsi] LAST_CONTROL_TRANSFER: from fffffa800e3a9840 to fffff8000329d8f0 STACK_TEXT: fffff880`0e59a9e8 fffffa80`0e3a9840 : fffffa80`09daf260 00000000`00000000 00000000`00000705 00000000`00000000 : nt!PspReturnQuota+0x80 fffff880`0e59aa68 fffffa80`09daf260 : 00000000`00000000 00000000`00000705 00000000`00000000 fffff800`03584d86 : 0xfffffa80`0e3a9840 fffff880`0e59aa70 00000000`00000000 : 00000000`00000705 00000000`00000000 fffff800`03584d86 fffffa80`116497c0 : 0xfffffa80`09daf260 FOLLOWUP_IP: nt!PspReturnQuota+80 fffff800`0329d8f0 6f outs dx,dword ptr [rsi] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!PspReturnQuota+80 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr 0xfffff8800e59a000 ; kb MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
  2. Loading Dump File [H:\BSODDmpFiles\Jessicka\Windows_NT6_BSOD_jcgriff2\010812-15787-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0324d000 PsLoadedModuleList = 0xfffff800`03492670 Debug session time: Sun Jan 8 00:18:54.060 2012 (UTC - 7:00) System Uptime: 0 days 4:42:54.857 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa800dfdc028, b2000000, 10005} Probably caused by : hardware Followup: MachineOwner --------- 8: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa800dfdc028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: DCGAME.EXE CURRENT_IRQL: f STACK_TEXT: fffff880`033eac58 fffff800`03216a3b : 00000000`00000124 00000000`00000000 fffffa80`0dfdc028 00000000`b2000000 : nt!KeBugCheckEx fffff880`033eac60 fffff800`033da513 : 00000000`00000001 fffffa80`0dfed570 00000000`00000000 fffffa80`0dfed5c0 : hal!HalBugCheckSystem+0x1e3 fffff880`033eaca0 fffff800`03216700 : 00000000`00000728 fffffa80`0dfed570 fffff880`033eb030 fffff880`033eb000 : nt!WheaReportHwError+0x263 fffff880`033ead00 fffff800`03216052 : fffffa80`0dfed570 fffff880`033eb030 fffffa80`0dfed570 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`033eae50 fffff800`03215f0d : 00000000`0000000c 00000000`00000001 fffff880`033eb0b0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`033eae90 fffff800`03209e88 : 00000000`4e4a7348 00000000`5305f440 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`033eaec0 fffff800`032c852c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`033eaef0 fffff800`032c8393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`033eb030 fffff800`032c7c00 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff880`0682dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE Followup: MachineOwner ---------
  3. Loading Dump File [H:\BSODDmpFiles\Jessicka\Windows_NT6_BSOD_jcgriff2\010612-16348-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`03454670 Debug session time: Fri Jan 6 02:40:40.585 2012 (UTC - 7:00) System Uptime: 0 days 7:53:40.600 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {2100, e, 1, fffff800032ab6a3} Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+c3 ) Followup: MachineOwner --------- 9: 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: 0000000000002100, memory referenced Arg2: 000000000000000e, IRQL Arg3: 0000000000000001, 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: fffff800032ab6a3, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034be100 0000000000002100 CURRENT_IRQL: e FAULTING_IP: nt!KiIpiProcessRequests+c3 fffff800`032ab6a3 f0838500210000ff lock add dword ptr [rbp+2100h],0FFFFFFFFh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff8800367e980 -- (.trap 0xfffff8800367e980) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000000d0 rbx=0000000000000000 rcx=fffff88003656180 rdx=0000566000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800032ab6a3 rsp=fffff8800367eb10 rbp=0000000000000000 r8=fffff880036611c0 r9=0000000000000000 r10=fffff8800365af00 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac pe cy nt!KiIpiProcessRequests+0xc3: fffff800`032ab6a3 f0838500210000ff lock add dword ptr [rbp+2100h],0FFFFFFFFh ss:0018:00000000`00002100=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000328b1e9 to fffff8000328bc40 STACK_TEXT: fffff880`0367e838 fffff800`0328b1e9 : 00000000`0000000a 00000000`00002100 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx fffff880`0367e840 fffff800`03289e60 : fffffa80`0e832000 00000000`00000000 fffffa80`11bb9378 00000000`00000001 : nt!KiBugCheckDispatch+0x69 fffff880`0367e980 fffff800`032ab6a3 : fffff880`0367eb70 fffff880`0367eb20 fffffa80`00000001 fffffa80`135b0130 : nt!KiPageFault+0x260 fffff880`0367eb10 fffff800`0329683a : fffff880`03656180 fffff880`0367ec70 fffffa80`09d68040 00000000`00000000 : nt!KiIpiProcessRequests+0xc3 fffff880`0367ebf0 fffff800`03283942 : fffff880`03656180 fffff880`00000001 00000000`00000001 fffff880`00000000 : nt!KiIpiInterrupt+0x12a fffff880`0367ed80 00000000`00000000 : fffff880`0367f000 fffff880`03679000 fffff880`0367ed40 00000000`00000000 : nt!KiIdleLoop+0x32 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiIpiProcessRequests+c3 fffff800`032ab6a3 f0838500210000ff lock add dword ptr [rbp+2100h],0FFFFFFFFh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiIpiProcessRequests+c3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!KiIpiProcessRequests+c3 BUCKET_ID: X64_0xA_nt!KiIpiProcessRequests+c3 Followup: MachineOwner ---------
  4. Loading Dump File [H:\BSODDmpFiles\Jessicka\Windows_NT6_BSOD_jcgriff2\122611-18517-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 7600 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03266000 PsLoadedModuleList = 0xfffff800`034a3e70 Debug session time: Mon Dec 26 02:55:52.514 2011 (UTC - 7:00) System Uptime: 0 days 9:42:40.622 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {ffffffffffffffff, 0, 8, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 9: 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: ffffffffffffffff, memory referenced Arg2: 0000000000000000, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: ffffffffffffffff, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350e0e0 ffffffffffffffff CURRENT_IRQL: 0 FAULTING_IP: +3939633862666261 ffffffff`ffffffff ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: DCGAME.EXE TRAP_FRAME: fffff880093a8920 -- (.trap 0xfffff880093a8920) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000090500 rdx=000fffffffffffff rsi=0000000000000000 rdi=0000000000000000 rip=ffffffffffffffff rsp=fffff880093a8ab8 rbp=fffff6800018cd80 r8=0000000000000004 r9=0000098000000000 r10=fffffa8009c01780 r11=fffff880093a8c20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc ffffffff`ffffffff ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032d5b29 to fffff800032d65c0 FAILED_INSTRUCTION_ADDRESS: +3939633862666261 ffffffff`ffffffff ?? ??? STACK_TEXT: fffff880`093a87d8 fffff800`032d5b29 : 00000000`0000000a ffffffff`ffffffff 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx fffff880`093a87e0 fffff800`032d47a0 : 00000000`00000008 fffff800`032f0e43 00000000`31980000 fffff800`0330ea4e : nt!KiBugCheckDispatch+0x69 fffff880`093a8920 ffffffff`ffffffff : fffff800`032f0e43 fffff680`0018cd80 fffff880`093a8b40 00000000`00000000 : nt!KiPageFault+0x260 fffff880`093a8ab8 fffff800`032f0e43 : fffff680`0018cd80 fffff880`093a8b40 00000000`00000000 00000000`00000000 : 0xffffffff`ffffffff fffff880`093a8ac0 fffff800`032d46ae : 00000000`00000001 00000000`00040000 00000000`00000001 00000000`fff68000 : nt!MmAccessFault+0xbf3 fffff880`093a8c20 00000000`657fe31e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`2a8cf890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x657fe31e STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`032d47a0 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 Followup: MachineOwner ---------
  5. Loading Dump File [H:\BSODDmpFiles\Jessicka\Windows_NT6_BSOD_jcgriff2\122211-16333-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 7600 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03209000 PsLoadedModuleList = 0xfffff800`03446e70 Debug session time: Wed Dec 21 23:23:25.558 2011 (UTC - 7:00) System Uptime: 0 days 5:05:53.651 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {fffff8801082ec51, 8000000328429121, fffff88004267f00, b} 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+1090f5 ) Followup: MachineOwner --------- 9: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff8801082ec51, Virtual address for the attempted write. Arg2: 8000000328429121, PTE contents. Arg3: fffff88004267f00, (reserved) Arg4: 000000000000000b, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88004267f00 -- (.trap 0xfffff88004267f00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8801082ec51 rbx=0000000000000000 rcx=fffffa80100f59c0 rdx=fffff88004268600 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880101230f5 rsp=fffff88004268098 rbp=fffffa8010155ac0 r8=0000000000000000 r9=000000000031cb62 r10=0000000000300001 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nvlddmkm+0x1090f5: fffff880`101230f5 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032f99c2 to fffff800032795c0 STACK_TEXT: fffff880`04267d98 fffff800`032f99c2 : 00000000`000000be fffff880`1082ec51 80000003`28429121 fffff880`04267f00 : nt!KeBugCheckEx fffff880`04267da0 fffff800`032776ae : 00000000`00000001 fffffa80`10687000 00000000`00000100 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x4223e fffff880`04267f00 fffff880`101230f5 : fffff880`04268600 fffffa80`1015fac0 fffffa80`106db000 fffffa80`0e6cc000 : nt!KiPageFault+0x16e fffff880`04268098 fffff880`04268600 : fffffa80`1015fac0 fffffa80`106db000 fffffa80`0e6cc000 fffff880`1082ec50 : nvlddmkm+0x1090f5 fffff880`042680a0 fffffa80`1015fac0 : fffffa80`106db000 fffffa80`0e6cc000 fffff880`1082ec50 00000000`00000000 : 0xfffff880`04268600 fffff880`042680a8 fffffa80`106db000 : fffffa80`0e6cc000 fffff880`1082ec50 00000000`00000000 00000000`00000000 : 0xfffffa80`1015fac0 fffff880`042680b0 fffffa80`0e6cc000 : fffff880`1082ec50 00000000`00000000 00000000`00000000 fffff880`10c03f40 : 0xfffffa80`106db000 fffff880`042680b8 fffff880`1082ec50 : 00000000`00000000 00000000`00000000 fffff880`10c03f40 00000000`00000000 : 0xfffffa80`0e6cc000 fffff880`042680c0 00000000`00000000 : 00000000`00000000 fffff880`10c03f40 00000000`00000000 fffffa80`13b7d580 : nvlddmkm+0x814c50 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+1090f5 fffff880`101230f5 ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+1090f5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e391010 FAILURE_BUCKET_ID: X64_0xBE_nvlddmkm+1090f5 BUCKET_ID: X64_0xBE_nvlddmkm+1090f5 Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...
  2. Hardware error. All probability points to hardware incompatibility/failure.
  3. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
  4. Possible cause Drivers...
  5. Possible causes Memory Problems... Drivers...
Thanks to Dave76 for help understanding possible causes.



It is good that you are no longer blindly using driverfinder. Many of the drivers companies like driverfinder suggest are newer are for different hardware and can cause conflicts and more blue screen crashes.



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.
My System SpecsSystem Spec
25 Jan 2012   #3

Windows 7 x64
 
 

I actually ran Memtest86+ the last few days prior to this message. It all was fine.

I just ran furmark and not sure which settings to use, so I went with my full resolution and AA at 2x and when the cards got to about 85, the system shutdown. I probably should mention I'm running SLI. I wonder if two cards for some games is not required? Some games never bluescreen at all from what I can tell.

The VMT test came up no errors though I see this non supported code, here's what the results were:

Code:
Changing video mode to 640x480x16...OK
[1/25/2012 9:59:12 PM] Test started for "Primary Display Driver (NVIDIA GeForce GTX 480)"...
Trying 16bpp RGB:565 mode...OK
Trying 16bpp RGB:555 mode...OK
Trying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode...OK
Trying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)
[1/25/2012 10:10:24 PM] Pass completed (0 errors found).
I thought I'd stop here because the furmark crashed after a few minutes like I said. and because of the SLI configuration. Could it be tied to that somehow?
My System SpecsSystem Spec
.


25 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

I have seen SLI cause issues and those be resolved by removing the bridge. If that works, you should contact the manufacturer of the graphics card and of the motherboard to get troubleshooting steps as to why the SLI bridge is not working as it should.
My System SpecsSystem Spec
25 Jan 2012   #5

Windows 7 x64
 
 

Well with the information I reported above would you suspect it might be SLI? Hardware monitor is showing all my fans working properly. I didn't install driver finder yet but the drivers it suggested I update were a few system and usb.

In the nVidia control panel I can set it to run one card, would that be something to test?

As for the Dell who actually sells Alienware now, my warrenty ran out. I had a big problem with them sending me the wrong pc 3 times in a row before getting this one which still wasn't the correct configuration. They won't talk to me anymore. If I can get this working on my own (limited knowledge in any hardware tech work) I would like that, but I'm almost tempted to buy a new computer anyway. I just dont know where to look. I don't build computers and I have no friends or none of my friends have brothers or anyone who can help me build a computer, so I'd probably go with something like Origin next, it's just costly. Not sure what I need and don't need to run high end games and just the occasionaly blu-ray movie, that can be somewhat cheap, run on this monitor resolution I like.
My System SpecsSystem Spec
25 Jan 2012   #6

Windows 7 Home Premium 64 Bit
 
 

It may also be a dust issue. It seems like your hardware is overheating based on your description of it shutting down during Furmark.

I provide the laptop procedure in case someone with a laptop stumbles across this thread. Similar for warranty information as I imagine yours is up after over a year.

To remove dust, follow the following general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.
  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. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
  5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
  6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
  7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
  8. Start the computer and see if performance is better.
My System SpecsSystem Spec
26 Jan 2012   #7

Windows 7 x64
 
 

I did all that you said. I'm not sure if it's running right or not since the bluescreen is just random. I guess I just have to wait.
My System SpecsSystem Spec
26 Jan 2012   #8

Windows 7 x64
 
 

I ran the 3dmark 2011 tests and the cards temperatures went into the 90s where with the other program the computer shutdown at 80, but maybe because I had burn in selected. So I don't know what else could cause it. I didn't get any bluescreens or shutdowns yet. I'm not sure what other kinds of tests I could run.
My System SpecsSystem Spec
26 Jan 2012   #9

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by Jessicka View Post
I ran the 3dmark 2011 tests and the cards temperatures went into the 90s where with the other program the computer shutdown at 80, but maybe because I had burn in selected. So I don't know what else could cause it. I didn't get any bluescreens or shutdowns yet. I'm not sure what other kinds of tests I could run.
You should probably try Furmark again since it caused the problem most recently.




Did you try Furmark again? Any crashes?
My System SpecsSystem Spec
16 Feb 2012   #10

Windows 7 x64
 
 

Yeah but i played 3 games since on max settings and never got any crashes. then i played some older lower end game and it crashed. Ntkrnl.exe again, and the bluescreen code was completely different from the one above. So it happened once more since my last post but like I said I just played through KoA:Reckoning, Saints Row The Third, Skyrim and the Mass Effect 3 Demo on all high, some of those for 8 hours straight and no crash. Then just the other day I loaded up an older game - Darksiders and it bluescreened with the same reason according to whocrashed and Bluscreenview.
My System SpecsSystem Spec
Reply

 Bluescreen problem while playing games




Thread Tools




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 01:42 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