Recurring IRQL not less or equal BSOD's

[jtmzac]

Hi,
I have been having the aforementioned BSOD's for a few months now and have simply put up with them since they were only happening twice a day.
I have finally decided to try and fix them so I came here.
I had always thought that the ATI drivers were always the problem (or at least part of it) since I used to have a lot of trouble even updating them and I used to get BSOD's during heavy gpu load (rift on max settings with crossfire on).
My computer has since started crashing on the desktop sometimes so I'm not sure what it is.

I had a look at the perfmon report and noticed an issue with logmein. I have no idea why it's there as I uninstalled it quite some time ago?
I do have anti-virus installed (Kaspersky internet security).
The UAC being off is self-explanatory.
The perfmon report also says that WWAN autoconfig was stopped abnormally. I don't know if it is caused by the changes I made to the registry to kill processes faster due to an abnormally long shutdown time I had?

I have done things like give myself ownership of all the files on the entire computer so I can add/change stuff in the windows folder and it is possible (but very unlikely) that I may have affected something. I also made an attempt to manually remove ATI driver registry entries at one point due to problems.

The crash dump might be a mess of several dumps (which should all be the same anyway) but it's all I have at the moment. I will move the current dumps out of the folder and re-run the software next time it crashes.

That’s everything I can think of to add at the moment. If you need any more info please ask.

 

[zigzag3143]

You have a driver from 2005 that is a HUGE cause of BSOD's in win 7 called RTCORE64.SYS, it is the msi afterburner driver (used in overclocking). It needs at least to be updated and if it cant it needs to be removed.

After addressing that we can look at the obvious video problems.


Other old drivers needing updating

WinRing0x64.sys    7/26/2008 9:29:37 AM                               
000.fcl    9/26/2008 9:11:22 AM              
LGPBTDD.sys    7/1/2009 2:47:52 PM

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
http://www.carrona.org/dvrref.php

 

[jtmzac]

right, I have uninstalled msi afterburner since I was only using it to monitor gpu stats which I can do in ccc anyway.

For WinRing0x64.sys I have updated to the latest version of realtemp.

For 000.fcl I have updated to the latest version of powerdvd10.

For LGPBTDD.sys I have updated to the latest version of Logitech gaming software.

I have no way to affect when the computer will crash so now I just have go on using the pc like normal and see if it crashes.

Time to have some fun updating to ccc 12-4. :sarc:

Just a quick question since I'm interested. It seems that the age of a driver seems to affect it's likeliness of causing problems, is this just due to un-optimisation for the current windows 7 build? or is it more because it was made for xp/vista?

 

[zigzag3143]

right, I have uninstalled msi afterburner since I was only using it to monitor gpu stats which I can do in ccc anyway.

For WinRing0x64.sys I have updated to the latest version of realtemp.

For 000.fcl I have updated to the latest version of powerdvd10.

For LGPBTDD.sys I have updated to the latest version of Logitech gaming software.

I have no way to affect when the computer will crash so now I just have go on using the pc like normal and see if it crashes.

Time to have some fun updating to ccc 12-4. :sarc:

Just a quick question since I'm interested. It seems that the age of a driver seems to affect it's likeliness of causing problems, is this just due to un-optimisation for the current windows 7 build? or is it more because it was made for xp/vista?

Great question.

Windows 7 (like any new OS) handles things a bit differently than its predecessor so since the drivers are how the device talks to the CPU they need to compensate for those changes so the correct information gets to the CPU.

Older drivers (prior to win 7s release) cant and they loose something in "the translation"

One way to compensate for this (if there are no new drivers) is to install the older driver in compatibility mode. That "translates" the information in both directions.

To install an older driver in win 7 you need to install it in compatibility mode.


To install in compatibility mode right click the installer, go to properties, then compatibility. Choose the appropriate OS


http://www.sevenforums.com/tutorials/316-compatibility-mode.html?ltr=C