Windows 7 Ultimate 64 bit BSOD IRQL_NOT LESS OR EQUAL??

OK, so its been some time since this started happening, while I'm playing a game in this case mw2 after 3-4 hours of playing all of a sudden the game freezes and I get a BSOD with IRQL_NOT_LESS_OR_EQUAL. Then windows restarts and gives me this:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFFFFFFFFFFFCF
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002ACF99C
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\042310-16046-01.dmp
C:\Users\Sava Gligorin\AppData\Local\Temp\WER-23281-0.sysdata.xml

So can you people help me??? Please!!!! Any ideas why is this happening or how to fix it would be greatly appreciated!!!!!

Capt.Jack Sparrow said:

Hello Welcome to SF !!

I guess the issue is with your Display driver and Network driver. Which the drivers are dated 2005 and 2008. Remove the exisiting drivers completetly. Then reboot and download a fresh copy of nVidia's webisite and install it. Please don't use Windows Update to download the drivers.

Old Drivers

Code:

vm62x64.sys Sat Oct 18 02:31:06 2008
TBPANELX64.SYS Tue Sep 20 17:02:31 2005
NTGLM7X64.sys Mon Dec 08 08:53:19 2008
nvoclk64.sys Fri Oct 13 20:48:17 2006

Bugcheck Analysis

Code:

Use !analyze -v to get detailed debugging information.
BugCheck A, {49, 2, 0, fffff80002a90d5a}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+9a )
Followup: MachineOwner
---------
3: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;
GetPointerFromAddress: unable to read from fffff80002cbb000
THREAD fffffa80065cb060  Cid 0b98.0da4  Teb: 00000000fffdb000 Win32Thread: fffff900c06fbc30 RUNNING on processor 3
Not impersonating
GetUlongFromAddress: unable to read from fffff80002bf9b74
Owning Process            fffffa80066c4b30       Image:         BFBC2Game.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      116207       
Context Switch Count      504629                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000024d0740
Stack Init fffff88008440db0 Current fffff88008440aa0
Base fffff88008441000 Limit fffff88008438000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`009b0b88 fffff800`02a84469 : 00000000`0000000a 00000000`00000049 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b0b90 fffff800`02a830e0 : 00000000`00000000 00000004`3a43f8e7 fffffa80`05865000 fffffa80`05865000 : nt!KiBugCheckDispatch+0x69
fffff880`009b0cd0 fffff800`02a90d5a : 00000004`3a438676 fffff880`009b0e88 00000000`0001c5ef fffff880`02fd7368 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`009b0cd0)
fffff880`009b0e60 fffff800`02a90697 : fffff880`0fe304c0 fffff880`0001c5ef 00000000`00000000 00000000`000000ef : nt!KiTimerExpiration+0x9a
fffff880`009b0f00 fffff800`02a8b065 : 00000000`00000000 fffffa80`065cb060 00000000`00000000 fffff880`0fe7aea0 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`02a8ae7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 (TrapFrame @ fffff880`009b0e70)
fffff880`08440be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
*******************************************************************************
*                                                                             *
*                        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: 0000000000000049, 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: fffff80002a90d5a, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbb0e0
 0000000000000049 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KiTimerExpiration+9a
fffff800`02a90d5a 4d03fd          add     r15,r13
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  BFBC2Game.exe
TRAP_FRAME:  fffff880009b0cd0 -- (.trap 0xfffff880009b0cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000ef rbx=0000000000000000 rcx=000000000001c5ef
rdx=00000000000005a6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a90d5a rsp=fffff880009b0e60 rbp=000000000001c5ef
 r8=0000000000000000  r9=00000000000000c0 r10=00000000000000ef
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nt!KiTimerExpiration+0x9a:
fffff800`02a90d5a 4d03fd          add     r15,r13
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002a84469 to fffff80002a84f00
STACK_TEXT:  
fffff880`009b0b88 fffff800`02a84469 : 00000000`0000000a 00000000`00000049 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b0b90 fffff800`02a830e0 : 00000000`00000000 00000004`3a43f8e7 fffffa80`05865000 fffffa80`05865000 : nt!KiBugCheckDispatch+0x69
fffff880`009b0cd0 fffff800`02a90d5a : 00000004`3a438676 fffff880`009b0e88 00000000`0001c5ef fffff880`02fd7368 : nt!KiPageFault+0x260
fffff880`009b0e60 fffff800`02a90697 : fffff880`0fe304c0 fffff880`0001c5ef 00000000`00000000 00000000`000000ef : nt!KiTimerExpiration+0x9a
fffff880`009b0f00 fffff800`02a8b065 : 00000000`00000000 fffffa80`065cb060 00000000`00000000 fffff880`0fe7aea0 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`02a8ae7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`08440be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiTimerExpiration+9a
fffff800`02a90d5a 4d03fd          add     r15,r13
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!KiTimerExpiration+9a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+9a
BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+9a

Hope this helps.
Captain

OK I will try this now, thank you very much Capt.Jack I'll post back about the results.

Alright so I installed the latest display drivers 197.45 for 9800gt and they are great. As for network drivers I found some other network drivers on the internet , I removed the old drivers and installed the new ones but when I went to check the date of these new drivers in device manager it says 10/17/2008 so are there any newer ones or are these the latest. I got them from here MSI K9N6PGM2-V Driver Download

Capt.Jack Sparrow said:

Gligorin said:

Alright so I installed the latest display drivers 197.45 for 9800gt and they are great. As for network drivers I found some other network drivers on the internet , I removed the old drivers and installed the new ones but when I went to check the date of these new drivers in device manager it says 10/17/2008 so are there any newer ones or are these the latest. I got them from here MSI K9N6PGM2-V Driver Download

Well I guess you could try this one NVIDIA DRIVERS 15.49 WHQL the release date is 2009.10.01

Hope this helps,
Captain

OMG!!! Your RULE!!! Thank you so much!!!!!! Two weeks ago I was searching every forum on the internet just to find the solution for my bsod and then I come here, make a post and bam I get the answer, so thank you for ever Capt.Jack Sparrow I am in your debt! The new drivers are working great!