BSOD out of nowhere

[Ermandfa]

Had this computer for 2.5 years and not one BSOD. Starting today I had 6 BSOD's alone. All of these errors had the message DRIVER_IRQL_NOT_LESS_OR_EQUAL.

I'm attatching the dmp files.

 

[richc46]

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL Usual causes: Device driver

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\RN8VXO2R\Minidump[1]\092610-19905-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Sun Sep 26 22:53:01.931 2010 (GMT-4)
System Uptime: 0 days 0:37:01.570
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4, b, 0, fffff8800ff146d2}
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 : hardware ( nvlddmkm+f76d2 )
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: 0000000000000004, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800ff146d2, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f040e0
 0000000000000004 
CURRENT_IRQL:  b
FAULTING_IP: 
nvlddmkm+f76d2
fffff880`0ff146d2 d818            fcomp   dword ptr [rax]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  hl2.exe
TRAP_FRAME:  fffff880095c4770 -- (.trap 0xfffff880095c4770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=00000000002cb2df
rdx=00000000095c4900 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800ff146d2 rsp=fffff880095c4900 rbp=fffffa8004247010
 r8=0000000000000001  r9=0000000183f5fce6 r10=fffffa8005d28ae0
r11=fffff880095c4710 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nvlddmkm+0xf76d2:
fffff880`0ff146d2 d818            fcomp   dword ptr [rax] ds:34c8:00000000`00000004=????????
Resetting default scope
MISALIGNED_IP: 
nvlddmkm+f76d2
fffff880`0ff146d2 d818            fcomp   dword ptr [rax]
LAST_CONTROL_TRANSFER:  from fffff80002ccd469 to fffff80002ccdf00
STACK_TEXT:  
fffff880`095c4628 fffff800`02ccd469 : 00000000`0000000a 00000000`00000004 00000000`0000000b 00000000`00000000 : nt!KeBugCheckEx
fffff880`095c4630 fffff800`02ccc0e0 : 00000000`000003d0 00000001`83f5c55e fffff880`095c4990 fffff880`03f6df76 : nt!KiBugCheckDispatch+0x69
fffff880`095c4770 fffff880`0ff146d2 : 00000000`002cb2df 00000001`83f5c55e 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`095c4900 00000000`002cb2df : 00000001`83f5c55e 00000000`00000000 00000000`00000000 fffffa80`04eec000 : nvlddmkm+0xf76d2
fffff880`095c4908 00000001`83f5c55e : 00000000`00000000 00000000`00000000 fffffa80`04eec000 fffffa80`0425b0b0 : 0x2cb2df
fffff880`095c4910 00000000`00000000 : 00000000`00000000 fffffa80`04eec000 fffffa80`0425b0b0 fffffa80`05d28ae0 : 0x1`83f5c55e
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nvlddmkm+f76d2
fffff880`0ff146d2 d818            fcomp   dword ptr [rax]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nvlddmkm+f76d2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys
BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys
Followup: MachineOwner
---------

Suggestions:

Update Driver.
Nvlddmkm.sys
Productname: NVIDIA Compatible Windows Vista Kernel Mode Driver
Description: NVIDIA Compatible Windows Vista Kernel Mode Driver,
Company: NVIDIA Corporation
If overclocking restore normal settings
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads
SFC /scannow
System Files - SFC Command
Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored.

speedfan speedfan.sys Sun Sep 24 09:26:48 2006 
netr28x  netr28x.sys  Wed Feb 25 22:02:09 2009 
Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 
aiijthsc aiijthsc.SYS Sat Mar 21 10:48:32 2009

Scan with your Anti Virus

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
Remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.

 

[Ermandfa]

hmm I have gotten the newest nvidia drivers. I hope this fixes the issue. Thanks.

 

[richc46]

Give it a try, if it does not repost.
There are many other steps, especially the remove of SPTD, do them all.