Two recent BSoDs

[DFChicken]

I've just recently received two blue screens, one of which was titled DRIVER_IRQL_NOT_LESS_OR_EQUAL, while the other one did not have a title. Here's the technical information...

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Problem signature:
Problem Event Name: APPCRASH
Application Name: Rtvscan.exe
Application Version: 10.2.0.298
Application Timestamp: 4580ab9c
Fault Module Name: StackHash_a34a
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00000000
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: a34a
Additional Information 2: c9c5f4fd744690d388ab9d5b3eb051a7
Additional Information 3: bf4a
Additional Information 4: f1ea91ae32511d63575c3b59717fed46


------------------------------------------------------------------------------


And here is the blue screen without a title at the top...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80001A5A5D8
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini061209-02.dmp
C:\Users\heshaam\AppData\Local\Temp\WER-44039-0.sysdata.xml
C:\Users\heshaam\AppData\Local\Temp\WER12F3.tmp.version.txt




Any help on why I'm getting these blue screens is greatly appreciated. Thank you in advance! :D

 

[Crispy2007]

I would install Service Pack 2 for starters, For the DRIVER_IRQL_NOT_LESS_OR_EQUAL, make sure that your display driver is up to date (Non beta drivers), and for the 0x1E: KMODE_EXCEPTION_NOT_HANDLED, Here is sone info that will help you: Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

 

[usasma]

The RTVSCAN.EXE is a component of Norton protection programs - which can easily cause these sorts of errors.

Ensure that you're able to reinstall your Norton - or obtain another antivirus program.
Uninstall the Norton using this free utility: Download and run the Norton Removal Tool
Reboot the system and install the antivirus.
If you choose another antivirus (I don't recommend Internet Security applications), then ensure that Windows Defender is working and that the Windows Firewall is also working (this isn't necessary with Internet Security applications that are being installed).

Please post back with your results. If this doesn't fix it, there's other stuff that we can do to analyze the crash dumps.

 

[DFChicken]

This is kind of embarrassing, I have Symantec AntiVirus v10.2 but I'm not sure which Norton Removal Tool to download. I'm guessing 2008 however I might be wrong. Any ideas?

 

[DFChicken]

Alright I've removed Norton completely and reinstalled it. I've also went ahead and installed Vista x64 Service Pack 2.

Now about the blue screens. I didn't used to get them too often, usually about one BSoD every day or two. I'll let you know if I get another one, but I'm still open to any other suggestions anyone may as to what I can do to prevent these blue screens.

 

[Crispy2007]

Download Memtest86+ - Advanced Memory Diagnostic Tool and run it.

 

[usasma]

FWIW - the amount of information on the site is daunting, but it revolves around saving your Norton subscription. The Removal Tool is the same for all Norton/Symantec versions that I've used it on.

 

[DFChicken]

I ran the memory test for 17 hours straight. After that I hit escape to reboot because I guess the test was designed to run forever. But during the test at the red bottom section of the screen there was a list of things that had either passed or failed I suppose. I'm not sure what they meant however...

 

[Crispy2007]

If something failed it means that your ram will most likely be the cause off the BSOD.

 

[usasma]

Yep, if you got "red stuff" in MemTest, it's most likely that your RAM is bad.

Unplug the system from the wall (and remove the battery if it's a laptop).
Ground yourself on the metal of the case (to keep static discharge from corrupting your RAM even more).

If there's only one RAM stick, try it in each of the slots and run MemTest on each of the slots.
If there's more than one stick, try them all in one slot and run MemTest on each of them. If all are bad, try the next slot, etc If any are good, then try the good one in each slot and run MemTest on them.

 

[DFChicken]

Okay, so I have two sticks of RAM. I'll test one stick at a time and try it in each of the four slots. My only question is that can I quit the test as soon as something red comes up at the bottom of the screen?

 

[usasma]

Yep, red is bad in MemTest, so stop it as soon as anything red comes up.

This leads us to a discussion about RAM errors. Some people believe that a few errors won't hurt anything and that Windows will compensate for them. I (and others) disagree with this because there's no telling where the error will pop up and how significant it will be. If it's non-essential data, then there's no problem - but if it's a critical process that's loaded there, the system will crash.

 

[DFChicken]

Alright, I'll go ahead and test it all now and get back to you. If worst comes to worst, I can simply return the memory to the manufacturer and get new ones. (I just bought this memory a few months ago by the way).

 

[DFChicken]

This is interesting...
I tested each stick of RAM by itself in DIMM Slot 0 and then DIMM Slot 1 (those are the two slots I use for the memory). At the end of each test it showed that the memory had no errors and told me to hit escape to reboot. Then I put the two sticks of RAM together like I had when I ran the original test and it also came up with no errors. How is that possible when the first time I ran the test it showed several errors with the memory?


EDIT: by the way I didn't bother testing DIMM Slot 2 or DIMM Slot 3 because I don't use those slots anyways.

 

[Crispy2007]

It can depend on what slot you putt it into.

 

[usasma]

A memory test is a software test that sends signals through the paths that memory must take. Anything wrong with the paths can cause an error. The most common issues are either bad RAM stick(s) or bad slots - but there are many other things that can cause this (and aren't so easy to figure out).

I've recently read that MemTest also tests CPU cache and video RAM - but the depth of the explanation is outside of my abilities.

So, we've gotta look at the differences between the first MemTest and the last MemTest. Presumably the sticks were in the same positions, so that seems to rule them out as the cause.

Was the case closed when you ran the first test and open when you ran the last test? If so, this could be an overheating problem. Were there any other differences? While you're in the case, carefully check to see if the CPU and video card fans are running. I recently found (at work) a situation where the video card was overheating and crashing the system - I did this by touching the components inside the case (after unplugging it) and burning my finger on the video card!

I'd suggest putting the RAM back in, closing the case and running MemTest overnight (or until it fails). Then open the case, let it cool down for an hour or two, then run MemTest overnight again (or until it fails). If it still fails, then try it with a house fan pointing at the RAM and run MemTest overnight again (or until it fails).

 

[DFChicken]

That's interesting, and I think you're right about the over-heating. When I ran the initial RAM test that failed, my case was closed completely. But when I ran the rest of the tests which all passed, my case wasn't completely closed. I had only laid down the cover on top of the computer so that it was slightly cracked open.

In addition, I've known my computer to overheat in the past when I have it closed. I've seen the CPU temp reach as high as 65-69 degrees Celsius (but that's when I'm playing games or doing something that uses much resources).

Anyways I'll take your advice and try again, thanks.

 

[DFChicken]

Well it seems you are correct usasma. I closed my case, ran the test, and got the same errors as I received during the initial test. Then I turned it off, opened the case, and let it cool down a little. I did the test once again with the case open and let the test run until it told me that no errors were found and that I could restart my computer.

I sometimes did suspect that my computer was blue-screening due to over-heating but I was never sure. Do you think this proves it?

 

[usasma]

I'm wary of stating a yes/no answer here - but the evidence stands for itself... Cover on, it fails memtest, cover off, it doesn't.

Do you have any way of posting a picture of the inside of the case (or several) so we can see where the fans are? Are you sure that all the fans are working? Does the case have a good, unobstructed airflow pattern? Can you see any dust bunnies between the RAM sticks? Are they very close together? Is there a place where you can mount a fan to blow on them permanently?

 

[DFChicken]

Today I've installed a special fan that covers the sticks of RAM and blows air on to them to keep them cool. I'm going to try to run the memtest with my cover on with this new fan blowing and see what happens.

Also I'll try to get you some pictures of my computer. Just to let you know, it's a little small and cramped. The airflow is probably minimal but I've checked all the fans to see if they work (and they do). I don't have any fans on the side of my computer and the fans that I have in the back only blow air out of the computer. Anyway I'll get you a picture as soon as possible.