 | |
| |
| 25 Feb 2012 | #1 |
| | BSOD playing SpaceMarine (and others), error unknown Hi everyone! I just found this forum, it seems like a great resource. I've been getting BSOD's for the last couple of days. They seem most common when playing SpaceMarine or Dawn of War II, though I got one or two playing Skyrim as well. I have not installed any new hardware recently. I did update my sound drivers (integrated RealTek HD Audio on an MSI motherboard) but I had to roll them back because they stopped my sound from working. Basic machine specs (as per the instruction thread) Windows 7 x64, retail upgrade version The machine hardware is varying degrees in age; my chip is around 4 years old. The mobo is about 2 years old, hard drives about 2 years old, graphics and peripherals about 1 year old. I did a full reinsstall of the OS about a year ago (upgrade from XP) As I wrote in the title, didn't have time to write down the actual error code, though I'm fairly certain that first one ended in an "a". The machine reboots too fast for me to get it written down. Anyways, here's to hoping someone has an idea, and thanks! |
My System Specs | |
| 25 Feb 2012 | #2 |
| | Multiple incorrect process faults and hardware bugchecks, more than likely a driver fault, but it could be memory related as well. Three tests I'd like you to run: Quote: Chkdsk:
Memtest: Read the following to test your memory for errors. Driver Verifier: Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver. Quote: nvm62x64.sys - nvm62x64 Fri Oct 17 17:01:06 2008 (nVidia Ethernet Networking Driver (nForce chipset driver). Update here. Code: *******************************************************************************
* *
* 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: 0000004493388939, memory referenced
Arg2: 0000000000000002, 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: fffff800030c3983, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fe100
0000004493388939
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiIdleLoop+73
fffff800`030c3983 f0480fba6b3000 lock bts qword ptr [rbx+30h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f8bbf0 -- (.trap 0xfffff88002f8bbf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000449338892a rbx=0000000000000000 rcx=0000000000000002
rdx=00010fe100000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030c3983 rsp=fffff88002f8bd80 rbp=0000000000000000
r8=0000000000000000 r9=000000000027bcce r10=000000000000e0ad
r11=fffffa80068f8901 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiIdleLoop+0x73:
fffff800`030c3983 f0480fba6b3000 lock bts qword ptr [rbx+30h],0 ds:00000000`00000030=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030cb1e9 to fffff800030cbc40
STACK_TEXT:
fffff880`02f8baa8 fffff800`030cb1e9 : 00000000`0000000a 00000044`93388939 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f8bab0 fffff800`030c9e60 : fffffa80`0b0e2002 00000000`00000000 fffff880`02f65c60 fffff880`02f63180 : nt!KiBugCheckDispatch+0x69
fffff880`02f8bbf0 fffff800`030c3983 : fffff880`02f63180 fffff880`00000000 00000000`00000000 fffff880`0f002db0 : nt!KiPageFault+0x260
fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x73
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiIdleLoop+73
fffff800`030c3983 f0480fba6b3000 lock bts qword ptr [rbx+30h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiIdleLoop+73
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xA_nt!KiIdleLoop+73
BUCKET_ID: X64_0xA_nt!KiIdleLoop+73
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffeda013495d78, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80003085770, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003305100
ffffeda013495d78
FAULTING_IP:
nt!ExWaitForUnblockPushLock+0
fffff800`03085770 48895c2408 mov qword ptr [rsp+8],rbx
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: DOW2.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800691b950 -- (.trap 0xfffff8800691b950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80042c4d20 rbx=0000000000000000 rcx=fffff8a00af0c330
rdx=fffff8800691bb30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003085770 rsp=fffff8800691bae8 rbp=fffff8800691bc00
r8=fffff8a00ae31000 r9=0000000000000010 r10=0000000000000820
r11=00000000002e81c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ExWaitForUnblockPushLock:
fffff800`03085770 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:fffff880`0691baf0=fffffa800735ba60
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000307d347 to fffff800030d2c40
STACK_TEXT:
fffff880`0691b7e8 fffff800`0307d347 : 00000000`00000050 ffffeda0`13495d78 00000000`00000001 fffff880`0691b950 : nt!KeBugCheckEx
fffff880`0691b7f0 fffff800`030d0d6e : 00000000`00000001 ffffeda0`13495d78 fffff8a0`0349bc00 fffff8a0`03507080 : nt! ?? ::FNODOBFM::`string'+0x44711
fffff880`0691b950 fffff800`03085770 : fffff800`033c92e6 fffffa80`0735ba60 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0691bae8 fffff800`033c92e6 : fffffa80`0735ba60 00000000`00000000 00000000`00000000 fffff800`030da74f : nt!ExWaitForUnblockPushLock
fffff880`0691baf0 fffff800`033bbb35 : 00000000`00000000 00000000`00000002 fffffa80`03ce2570 fffff880`0691bc01 : nt!ObReferenceObjectByHandleWithTag+0x356
fffff880`0691bbc0 fffff800`030d1ed3 : fffffa80`03f6db60 00000000`0000081c 00000000`00000000 00000000`00000000 : nt!NtSetEvent+0x75
fffff880`0691bc20 00000000`75092e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`32b7f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75092e09
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExWaitForUnblockPushLock+0
fffff800`03085770 48895c2408 mov qword ptr [rsp+8],rbx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ExWaitForUnblockPushLock+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x50_nt!ExWaitForUnblockPushLock+0
BUCKET_ID: X64_0x50_nt!ExWaitForUnblockPushLock+0
Followup: MachineOwner
*******************************************************************************
* *
* 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: fffffa800593c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, 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: System
CURRENT_IRQL: f
STACK_TEXT:
fffff800`00ba8a98 fffff800`03615a3b : 00000000`00000124 00000000`00000000 fffffa80`0593c028 00000000`b2000040 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`031a7513 : 00000000`00000001 fffffa80`04c908b0 00000000`00000000 fffffa80`04c90900 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`03615700 : 00000000`00000728 fffffa80`04c908b0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03615052 : fffffa80`04c908b0 fffff800`00ba8e70 fffffa80`04c908b0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03614f0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`03608e88 : 00000000`2fdc92af fffff800`00b9ca28 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`0309552c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`03095393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff800`0309c7a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9c900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x260
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89986e509, Reserved
Arg2: b3b7465eec03b45f, Reserved
Arg3: fffff80003142e4a, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030c9c40
STACK_TEXT:
fffff880`031af5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9986e509 b3b7465e`ec03b45f fffff800`03142e4a : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: BAD_STACK
Followup: MachineOwner
*******************************************************************************
* *
* 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: fffffa8005bbc8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031bd6f0 fffff800`032e0c59 : fffffa80`05bbc8d0 fffffa80`03cfa040 00000000`00000012 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`031c0f57 : fffffa80`05bbc8d0 fffff800`0323b2b8 fffffa80`03cfa040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`031285d5 : fffff800`0329cae0 00000000`00000001 fffffa80`05a4c150 fffffa80`03cfa040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`030a5001 : fffff880`011aae00 fffff800`031285b0 fffffa80`03cfa000 f7bfdfba`efafffff : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`03335fee : 00000000`00000000 fffffa80`03cfa040 00000000`00000080 fffffa80`03c6f890 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`0308c5e6 : fffff880`02f63180 fffffa80`03cfa040 fffff880`02f6dfc0 dfbffcff`f75fdfff : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bcb40 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner |
| My System Specs |
| 27 Feb 2012 | #3 |
| | Hey I just wanted to say thanks for this! Work interfered and I haven't had time to work on my home PC, but once I do this I will let you know how it turned out. I appreciate the help! |
| My System Specs |
| . |
| |
| 27 Feb 2012 | #4 |
| | My pleasure  |
| My System Specs |
| 17 Mar 2012 | #5 |
| | Hi all! I was finally home long enough to start trying these solutions this weekend. First things first -- since it was waaaaay overdue, I wiped my drive and did a clean reinstall of Windows 7. I figured, since I needed to do it anyways, I should do it before trying all of the above listed solutions since a reinstall might fix the problem of a bad driver or something similar. Unfortunately, I got another BSOD while playing Mass Effect 3 this morning, an "IRQL greater or less than" error. A few questions: 1) Should I bother to run chkdsk if I just reformatted/reinstalled? 2) What do I do after Driver Verifier is set to run? I understand I'm supposed to wait for another BSOD, but after that happens, what do I do? Is there a log I should check, somewhere? Thanks for your help and patience. ETA: I should add that the driver epeen advised me to update is now properly updated. I used Nvidia's driver scan app, and it correctly identified my motherboard and video card. So I don't think that's the issue, though I suppose it could still be. Now that I think of it, I'll redo the dump collection and post it here . . . |
| My System Specs |
| 21 Mar 2012 | #6 |
| | Hello, very sorry for my inactivity and lack of response.. I have been very busy. The dump you've provided is a D1 bugcheck, typical IRQL NOT LESS OR EQUAL stop code. The culprit.... take a guess... it's nvlddmkm.sys, which is yet again the nVidia video driver. Have you tried a DIFFERENT driver version that the one you were crashing with previously? For example, when you reinstalled Windows, did you go right to the same driver version that you had installed prior to reinstalling Windows? If so, for curiosity's sake try an older version, perhaps a version BEFORE the newest (assuming you're updated to the latest drivers, which you should be). I checked your drivers list and your nVidia driver is dated 2011, which I can only assume that's definitely not the last time nVidia has put out drivers. Code: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\031712-20546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: 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 Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4fe90
Debug session time: Sat Mar 17 12:19:51.082 2012 (UTC - 4:00)
System Uptime: 0 days 13:05:41.369
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff80050c8e600, 2, 0, fffff80050c8e600}
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+816e0 )
Followup: MachineOwner
---------
0: 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: fffff80050c8e600, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80050c8e600, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e8
fffff80050c8e600
CURRENT_IRQL: 2
FAULTING_IP:
+3438386532376262
fffff800`50c8e600 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c840 -- (.trap 0xfffff80000b9c840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80081a8820
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80050c8e600 rsp=fffff80000b9c9d8 rbp=0000000000000410
r8=0000000000000000 r9=000000000000001f r10=00000000000002d4
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff800`50c8e600 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c89be9 to fffff80002c8a640
FAILED_INSTRUCTION_ADDRESS:
+3438386532376262
fffff800`50c8e600 ?? ???
STACK_TEXT:
fffff800`00b9c6f8 fffff800`02c89be9 : 00000000`0000000a fffff800`50c8e600 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c700 fffff800`02c88860 : fffff880`0f435a48 fffffa80`05d5e000 fffffa80`06db45d0 fffffa80`06db45d0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c840 fffff800`50c8e600 : fffff880`0f36d6e0 00000000`00000000 fffffa80`06db45d0 00000000`000004ec : nt!KiPageFault+0x260
fffff800`00b9c9d8 fffff880`0f36d6e0 : 00000000`00000000 fffffa80`06db45d0 00000000`000004ec fffffa80`05de9420 : 0xfffff800`50c8e600
fffff800`00b9c9e0 00000000`00000000 : fffffa80`06db45d0 00000000`000004ec fffffa80`05de9420 00000000`00000000 : nvlddmkm+0x816e0
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+816e0
fffff880`0f36d6e0 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm+816e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+816e0
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+816e0
Followup: MachineOwner
--------- |
| My System Specs |
 |
BSOD playing SpaceMarine (and others), error unknown problems?
| Thread Tools | |
| Similar help and support threads for: BSOD playing SpaceMarine (and others), error unknown | ||||
| Thread | Forum | |||
| BSOD playing games, error unknown 0x000000000. | BSOD Help and Support | |||
| Unknown BSOD , Happened only while playing Battlefield 3 | BSOD Help and Support | |||
| BSOD playing various games, unknown (and seemingly different) reasons | BSOD Help and Support | |||
| BSOD while playing,reason unknown | BSOD Help and Support | |||
| BSOD. error Custom built computer. error unknown between 0 or 1077... | BSOD Help and Support | |||
All times are GMT -5. The time now is 08:02 AM.
