Random BSOD, errors IRQL not less or equal/KMODE exception not handled

Hi all,
the last month has been a real nightmare: I started getting BSODs practically out of the blue and it's happening more and more often.
I can't recall installing anything particular at the time (I use the PC mostly to work and navigate the web), and I haven't changed any piece of hardware, lately.
I keep the drivers up to date and use Windows Update regularly, use Avira as antivirus software (which has never given me problems), regularly scan the system for viruses/malware (using both Avira and Anti-Malware - one at a time, of course) and defragging the drives when necessary.
In the last few days I ran RAm tests for a few hours but no errors were detected...

I can't think of any other info you might want, attached you'll find all the data required by the BSOD posting instructions...

Thanks in advance for your help.
ALex

And here's the .zip file

Problematic Software:

Code:

Start Menu\Programs\Device Doctor Pro	Public:Start Menu\Programs\Device Doctor Pro	Public
Start Menu\Programs\Driver Detective	Public:Start Menu\Programs\Driver Detective	Public

• We do not recommend automated driver update software. It often finds drivers for devices similar to but not exactly the same as the hardware actually on the system. This can lead to conflicts and blue screen crashes. If you need help finding driver updates for a certain device, please start a thread in Drivers - Windows 7 Forums instead of using software. Driver updates are not always necessary and some updates can actually decrease system stability rather than increase it, so it is usually better not to update unless a device or its driver is causing problems with the system. If it ain't broke, don't fix it.

The following drivers need to be updated:

Code:

ahcix64.sys Fri Aug 29 19:50:57 2008 (48B8A781)
ahcix64s.sys Wed Jul 1 01:05:27 2009 (4A4B0AB7)

ahcix64.sys
ahcix64s.sys

The drivers should be updated from your motherboard support site or directly from AMD: AMD Chipset Drivers -> AMD Raid Drivers


Crashes indicate possible hardware issues, but they may actually be related to the RAID controller drivers being out of date. Test to see if the system is stable after doing the above first. Test by doing your normal routine for twice as long as it typically takes to get a crash.

If you get more crashes, run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Hi writhziden,
thank you for your answer. I've downloaded and installed the RAID drivers and will get back to you after doing as you suggested. During installation (I always choose "Custom") I noticed that the installation program listed the RAID drivers as already up to date - it did install them anyway (it dismounted and re-mounted the disks, so I guess it did).

As for system temperature, I already keep it in check: it's usually between 43 and 52 Celsius degrees. I noticed it raises when the browser (Chrome) is on a site using flash (and the system often crashes while playing a Flash game).
The GPU temperature, on the other hand, is steady at 67 Celsius degrees.

As for the drivers-checking software, you're obviously right but I do not let it automate driver installation: I use it (Driver Detective, I used Device Doctor just twice and never started it again) to see if the drivers are up to date and then personally choose what to install (which doesn't mean I can't be wrong, of course).

Thanks again, I'll get back to you.
ALex

Glad to see you do not let the driver update software do the updating for you.

As to the temperatures, the tests are not just to check temperatures but to check that the hardware is working properly. The temperature monitoring is to make sure those stress tests do not overheat components because the tests can cause your system to get a little hotter than normal use does. It is a good idea to monitor the temperatures just to be safe.

You may have already known that was what I meant, but I wanted to make sure.


In addition to the tests, we should make sure your RAM is compatible with your system:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

I imagined you'd want to stress test the system, but please make sure for at least two reasons: a) English is not my mother language b) I can always learn something new.
I thought I was an above-average user, until I ran into this issue and suddenly had no clue, whatsoever.

Ran FurMark for about 30 mins (the only time I could spare from work) - 15 "free", 15 doing the benchmark (got a score of 1235): nothing happened, apart from the GPU temp reaching 97° C (GPU vent running at 52%).

Adding CPU-Z to the to-do list...

Brief update: ran VMT for one hour seven minutes (1 pass, didn't have more time) with no problems e no errors detected. Hopefully I'll be able to run the tests longer during the w-e.

Alright, let us know how the VMT pans out when you have a chance to run it longer. This weekend is fine for me. :)

Had VMT running for 3 hours and 10 minutes, before getting a BSOD.
After re-booting the PC, I noticed I received an e-mail, a few seconds before the PC crashed.
Attaching the dump...
G'nite :)