BSOD Playing SWTOR, Error IRQ not less than or equal

[jubei415]

I've had my first 2 crashes with windows 7 in the last 24 hours. Haven't had any for at least a year.

stats:
Intel core i7 2600k
8GB corsair memory
Intel 530 124gb SSD drive
WD Black 1TB backup drive
Geforce GTX 580 1.5gb Video card


Win7 64bit, OEM ( I Assume as it came with the machine when I bought it from co-worker )

system is about.. 5 months old
Have not had to do a reformat on it

 

[writhziden]

[list=1]
[*]
Loading Dump File [F:\BSODDmpFiles\jubei415\Windows_NT6_BSOD_jcgriff2\021212-15288-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0321e000 PsLoadedModuleList = 0xfffff800`0345be50
Debug session time: Sun Feb 12 07:02:44.687 2012 (GMT-7)
System Uptime: 0 days 0:15:25.592
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 6, 8, 0}

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+52481d )

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: 0000000000000000, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c60e0
 0000000000000000 

CURRENT_IRQL:  6

FAULTING_IP: 
+60b9952f02d3dd48
00000000`00000000 ??              ???

PROCESS_NAME:  swtor.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff88008d65510 -- (.trap 0xfffff88008d65510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8006715000
rdx=fffffa8008677000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff88008d656a8 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff88008d65680 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000328f469 to fffff8000328ff00

FAILED_INSTRUCTION_ADDRESS: 
+60b9952f02d3dd48
00000000`00000000 ??              ???

STACK_TEXT:  
fffff880`08d656a8 fffff880`1054481d : fffff880`00000000 fffffa80`08ff6690 00000000`00000000 00000000`00001000 : 0x0
fffff880`08d656b0 fffff880`00000000 : fffffa80`08ff6690 00000000`00000000 00000000`00001000 00000000`00000008 : nvlddmkm+0x52481d
fffff880`08d656b8 fffffa80`08ff6690 : 00000000`00000000 00000000`00001000 00000000`00000008 fffff880`10273f1f : 0xfffff880`00000000
fffff880`08d656c0 00000000`00000000 : 00000000`00001000 00000000`00000008 fffff880`10273f1f 000000d7`812c4e90 : 0xfffffa80`08ff6690


STACK_COMMAND:  .trap 0xfffff88008d65510 ; kb

FOLLOWUP_IP: 
nvlddmkm+52481d
fffff880`1054481d ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvlddmkm+52481d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+52481d

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+52481d

Followup: MachineOwner
---------


[*]
Loading Dump File [F:\BSODDmpFiles\jubei415\Windows_NT6_BSOD_jcgriff2\021212-16114-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03200000 PsLoadedModuleList = 0xfffff800`0343de50
Debug session time: Sun Feb 12 06:46:31.408 2012 (GMT-7)
System Uptime: 7 days 4:12:57.314
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88008a0892b, 1, fffff880101668eb, 0}

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

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+13b8eb )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff88008a0892b, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880101668eb, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034a80e0
 fffff88008a0892b 

FAULTING_IP: 
nvlddmkm+13b8eb
fffff880`101668eb c88d9424        enter   948Dh,24h

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008a11c50 -- (.trap 0xfffff88008a11c50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000390 rbx=0000000000000000 rcx=fffffa800b684000
rdx=fffffa8009126000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880101668eb rsp=fffff88008a11de0 rbp=fffffa8009126000
 r8=fffffa800b4930a0  r9=0000000000000001 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x13b8eb:
fffff880`101668eb c88d9424        enter   948Dh,24h
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032f11e4 to fffff80003271f00

STACK_TEXT:  
fffff880`08a11ae8 fffff800`032f11e4 : 00000000`00000050 fffff880`08a0892b 00000000`00000001 fffff880`08a11c50 : nt!KeBugCheckEx
fffff880`08a11af0 fffff800`0326ffee : 00000000`00000001 00000000`c00000e8 fffff880`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`08a11c50 fffff880`101668eb : 00000000`c00000e8 fffffa80`09126000 00000000`c00000e8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`08a11de0 00000000`c00000e8 : fffffa80`09126000 00000000`c00000e8 00000000`00000000 00000000`001619ac : nvlddmkm+0x13b8eb
fffff880`08a11de8 fffffa80`09126000 : 00000000`c00000e8 00000000`00000000 00000000`001619ac 00000000`00000038 : 0xc00000e8
fffff880`08a11df0 00000000`c00000e8 : 00000000`00000000 00000000`001619ac 00000000`00000038 fffff880`025f0000 : 0xfffffa80`09126000
fffff880`08a11df8 00000000`00000000 : 00000000`001619ac 00000000`00000038 fffff880`025f0000 00000000`0000c000 : 0xc00000e8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+13b8eb
fffff880`101668eb c88d9424        enter   948Dh,24h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+13b8eb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68

FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+13b8eb

BUCKET_ID:  X64_0x50_nvlddmkm+13b8eb

Followup: MachineOwner
---------
[/list]

1. Due to your display adapter (graphics card) driver.
2. Due to your display adapter (graphics card) driver. Other possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.

• If you are overclocking any hardware, please stop.
  
  
  
• Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
  
• If you continue to have crashes after updating/re-installing your display card drivers... Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Start logging the temperature through sensor-only mode when the computer first starts, and let it run during stress or until a crash occurs.
  
  Save the CSV file in a place you will remember, and then compress the CSV file to a zip file and upload to here for us to analyze by following the steps in http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.
  
  
  
  Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Monitor temperatures using HWINFO.​