Random BSOD, IRQL_NOT_LESS_OR_EQUAL and MEMORY_MANAGEMENT

Report file is corrupt. Try uploading again.

Re-uploaded the file. That should work now :)

Lohita said:

Hi All,

I've been having problems with my PC randomly BSODing. Before this my PC used to randomly get stuck and I would have to restart it. I also recently noticed that it gave me a bad CMOS error recently.

A couple of details on the machine:

Basic Hardware Specs:

• Processor: AMD Phenom II X4 955 Black Edition @ 3.2 GHz
• Motherboard: MSI 790GX-G65 (Flashed to latest Bios)
• RAM: 8 GB DDR3 @ 1333 MHz
• Graphics Card: MSI R6970 Lightning 2 GB
• Monitor: Samsung 2233SWPLUS 21.5" LCD
• HDD: Samsung Spinpoint F3 1 TB
• Optical Drive: HP DVD Writer
• Sound: Onboard
• Network Card: D-Link DWA-510 Wireless-G PCI WLAN card
• Mouse: Cyborg R.A.T. 7
• PSU: Corsair TX-750 750 W
• Other peripherals: Hot swap bay, card reader, 1200 VA UPS, 4-port USB hub

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64 Ultimate
- the original installed OS on the system? Windows 7 x64 Ultimate
- an OEM or full retail version? OEM
- What is the age of system (hardware)? Mostly bought in December 2009, with some parts bought more recently
- What is the age of OS installation (have you re-installed the OS?) Installed in December 2009 and been running the same installation since then

I had recently (About 3 weeks ago) overclocked my machine so that it was running at 3.8 GHz, and all RAM was running at 1600 MHz at 9-9-9-24, but since the BSODs started it's back to stock clocks on both.

Any help in finding a solution to fix the problems with the BSOD would be really appreciated.

Thanks in advance!

Couple of issues immediately apparent

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


Old drivers

Code:

tap0901.sys    1/21/2009 11:55:45 AM        fffff880`04400000    fffff880`0440d000        0x0000d000    0x49775391                    
cpuz132_x64.sys    3/26/2009 6:17:23 PM        fffff880`08ab4000    fffff880`08abc000        0x00008000    0x49cc0d03                    
RTKVHD64.sys    3/30/2009 4:15:46 AM        fffff880`06e10000    fffff880`06fb9000        0x001a9000    0x49d08dc2                    
AmdLLD64.sys    4/22/2009 2:32:17 PM        fffff880`058ad000    fffff880`058c0000        0x00013000    0x49ef70c1

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 try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Sure, will try that for now, thanks.

Lohita said:

Sure, will try that for now, thanks.

Good luck

I have uninstalled Daemon Tools (Including the SPTD driver using the software you mentioned) as well as CPU-Z and will re-install the latest version of CPU-Z a bit later. I will also be updating the Realtek driver.

I have not however been able to find an uninstaller for tap0901.sys. Is there another way to get rid of this driver?

Additionally, as indicated at http://www.w7forums.com/bsod-happening-often-t6292.html, I will be renaming AmdLLD64.sys to AmdLLD64.sys.bak.

Any other recommendations?

I have also been having a problem where my machine gets stuck. I've noticed this happens generally when I'm doing something graphically intense, e.g. playing a game. Not sure why this happens either. I just upgraded to the latest drivers as well and I still have the same issues.