driver_irql_not_less_or_equal (Dumps Attatched)

OverhaulNetwork · 07 Jul 2010

I have been getting BSOD's lately and am unsure of what exactly is causing them. Obviously I need to get this issue resolved.

this is the first PC I have built myself, I was thinking it was hardware related as i have already RMA'd RAM because windows only would see 7.99GB usable out of the 12GB I had installed. I am forced to run my 1600MHz RAM at 1468MHz aas anything higher makes my system unable to boot

I have run memtest86+ for 12 hours with no issues, so I had ruled the RAM out...

I hope that someone can help me get the the bottom of my problems. My PC is overclocked from 2.67GHz to 3.67GHz and it was my first overclock so I am not sure if it done 100% correct. It runs prime95 stable for 12 hours (i turn off after that long) with a decent CPU temp so i called it a stable OC, maybe I am wrong.

Anyway here are my dump files. Thanks in advance for the help

usasma · 07 Jul 2010

Does the system have BSOD's if you stop overclocking?
That's the "test" to see if the overclock is to blame. Once the system is stable without an overclock, then you can overclock and any problems can be attributed to the overclock (and this tells you if your overclock is stable or not).

Also, an overclocked system doesn't behave as a non-overclocked system does. So any errors are immediately suspect. Are they the correct errors, or are they a result of a failed/failing overclock?

In this case you have a brand new system. And the number of different BSOD errors indicates either a hardware or a compatibility issue.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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 try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

Code:

adfs.SYS     Thu Jun 26 16:52:37 2008 - Adobe Filter driver - http://www.carrona.org/dvrref.html#adfs.SYS
MarvinBus64.sys Fri Sep 23 17:17:03 2005 - likely a part of Pinnacle Studio's Marvin Bus - http://www.carrona.org/dvrref.html#MarvinBus64.sys
PxHlpa64.sys Mon Dec 10 18:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) - http://www.carrona.org/dvrref.html#PxHlpa64.sys

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul  7 16:15:18.723 2010 (UTC - 4:00)
System Uptime: 0 days 1:29:05.956
BugCheck D1, {fffffa8040de26c0, 2, 0, fffff880100eefca}
*** 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+9ffca )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul  7 14:45:11.555 2010 (UTC - 4:00)
System Uptime: 0 days 13:39:35.789
BugCheck A, {fffffa7f9d9d6252, 2, 0, fffff80002cd7e8b}
Probably caused by : memory_corruption
BUGCHECK_STR:  0xA
PROCESS_NAME:  VidBlaster.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 30 04:30:31.998 2010 (UTC - 4:00)
System Uptime: 0 days 12:51:39.517
BugCheck 24, {1904fb, fffff88006e6d7d8, fffff88006e6d040, fffff80002fc68f1}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReadMftRecord+b2 )
PROCESS_NAME:  rundll32.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 14:01:52.665 2010 (UTC - 4:00)
System Uptime: 1 days 14:35:39.009
BugCheck 4E, {2, 163216, 35ffff, 5}
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : eamon.sys ( eamon+69d1 )
BUGCHECK_STR:  0x4E_2
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 22:43:53.293 2010 (UTC - 4:00)
System Uptime: 0 days 23:34:32.608
BugCheck 50, {ffffffefd0900000, 0, fffff80002cda710, 5}
Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+590 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  ekrn.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 01:28:00.736 2010 (UTC - 4:00)
System Uptime: 0 days 19:54:16.423
BugCheck 3B, {c0000005, fffff960000c74c3, fffff8800a9b21d0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware ( win32k+c74c3 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  VidBlaster.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨