Blue screen of death

[scott77]

Hi, I keep getting blue screens on my desktop. They seem to occur at 3am every time they occur. I have updated all drivers and I have run memtest 86 for 5 passes and there were no errors reported. Anyway here are the error codes:
Stop:
0x0000000A (0x3c74C09B, 0x0000001C, 0x00000000, 0x804F4276)

I want to know how to figure out which piece of hardware or software is causing the problem.

Thanks in advance.

[ronallandottk]

Unfortunately, I'm not really familiar with all of the stop error codes, but the 0x0000001C code is more or less a dead giveaway that the problem is a device driver of some sort.

Other than the error codes, what error message did the blue screen display?

Could you describe your PC configuration, what you were doing when the error first manifested itself, and any recent drivers you updated? Have you had the PC for some time, or is it a new build/new PC?

BSODs are quite cryptic, but using a process of elimination, it isn't really that difficult (though tedious) to pinpoint the cause.

[scott77]

Hi, it usually says IRQL_NOT_LESS_OR_EQUAL but next time it does it I will check to see if there is anything else. It has a P5K/EPU Asus mobo, HD3000 series graphics card, I can't remember the exact model. Intel E8200, 2x 1gb 800 mhz DDR2 ram. It also has a PCI card which is for a surveillance system. It has been blue screening pretty much since I built it which was about 6months ago. I'm pretty sure the drivers for the PCI card I mentioned are causing the problem, but I want to be sure. I don't really want to go disabling them, because as with most cases the blue screens are unpredictable.

I know that you can use the error code to get the address of the driver and therefore identify it, do you know how to do this?

Thanks.

[ronallandottk]

If the BSOD occurs again, read the third part of the screen, after the STOP message and the "If this is the first time..."

The third part usually provides a memory location, a date stamp (both in hex) and a filename, maybe a DLL, an EXE, or a SYS file which may have triggered the BSOD.

Can you cause the BSOD on command? Or is it purely random?

In my experience, the most common cause for BSODs with the STOP message you've stated is actually faulty RAM. In a nutshell, a driver is loaded at a high memory location on bootup, and when the OS accesses the driver and the address can't be accessed, this screws up the system with a BSOD with a "DRIVER_IRQL_NOT_LESS_OR_EQUAL." error message.

It may appear to be a driver problem...but actually it's the RAM.

This can usually be verified by removing one of your sticks of RAM, and observing the system if it still BSODs. If it does, replace the stick with your other stick of RAM and see if it happens again.

Drivers are loaded from the top of the available memory addresses downwards, so testing both sticks one at a time can usually identify the faulty stick of RAM.

Your RAM may have passed MemTest, but that doesn't necessarily mean that it's not a RAM problem. I have a MSI motherboard that always crashes/BSODs when I use generic RAM (the generic RAM isn't defective, works well in another PC with a different brand of motherboard), I was able to eliminate the crashes by using branded RAM (Kingston, in my case). It's possible your motherboard just doesn't like the RAM you're using. It's not unheard of for some motherboards to be unstable with some brands of memory.

Additionally, are your RAM sticks identical? Your board is running in dual-channel mode, and dissimilar memory sticks may cause problems as well.

You could also check if a BIOS update is available for your board. An updated BIOS could solve the problem.

Lastly, since you've mentioned the crashes occurring at around 3 AM, it may be worth exploring if your PC is overheating, especially if it's been one for long periods of time and it isn't well ventilated or situated in a hot room. Excessive heat can easily be responsible for a BSOD as well.

If the PCI surveillance card is bothering you, try uninstalling its drivers and pull out the card from the PC and see if it still BSODs.

I'm sorry if I can't be more specific. PC configurations are quite varied, and there is no sure fire solution for a BSOD, except trial and error.

[scott77]

Hi, yes the BSOD is completely random. Sorry I forgot to mention, I'm using GSkill RAM. I run 2x 2GB 800mhz GSkill sticks in my other comp which has an Asus Maximus Formula mobo, and I've never had a problem. However I do realise even though they are both Asus mobos they may not like the same RAM so I will check this out. Both sticks are identical. Also updating the BIOS would probably be a last resort. I'm also pretty certain it isn't overheating, the case has 2 huge cooling fans in it to cope with being on 24/7 also everything is at stock clocks. Also it never happens during the day which is way warmer than at 3am and it seems to do it at precisely 3am so that sort of rules it out.

Thanks for the help so far, I'll try running with 1 stick tomorrow.

Thanks again, you help is highly appreciated.

[ronallandottk]

Here's one more thing you can check.

Since you've mentioned that it almost always happens precisely at 3 AM, do you have any program running that is set to do something at 3 AM?

Possibilities include antivirus programs which may be set to automatically update and/or scan your disks at that time. Disk utilities such as disk scanners or defragmenters could also be set for that time.

Are your Windows updates set to download/install at a particular time? It may be possible that your PC may be set to download updates automatically and it may be downloading an update - perhaps a driver update - that doesn't work well with your PC, causing it to BSOD?

The 3 AM thing is a bit curious...it seems to indicate that a rogue application running at that time is crashing your PC.

[scott77]

I checked all of those possibilities out earlier, except for the automatic updates one which I've just checked and it is set to download updates at 3am. Hopefully this is the problem and not some annoying coincidence. I've disabled updates and I'll post back and let you know the outcome. Thanks.

[wendybell]

I need help with a "blue screen of death" problem.
My first error message that I got said:


"We apologize for the inconvenience but Windows did not start successfully. A recent hardware or software change might have caused this.



If your computer stopped responding, restarted unexpectedly, or was automatically shut down to protect your files and folders, choose last know good configuration to revert to the most recent settings that worked.



If a previous startup attempt was interrupted due to a power failure or because the power or restart button was pressed, or if you aren't sure what caused the problem, choose starts windows normally



Safe mode

safe mode with networking

Safe mode with command prompt



Last known Good configuration (your most recent settings that worked)



Start windows normally"



When I try either Last known good configuration or start windows normally, I get the following message:



"A problem has been detected and windows has been shut down to prevent damage to your computer.



If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Disable or uninstall any anti-virus, disk defragmentation or back up utilities. Check your hard drive configuration, and check for any updated drivers. Run CHKDSK/F to check for hard drive corruptions and then restart your computer.



Technical information:

Stop: 0x00000024 (0x00190203, 0x8A834300, 0xC0000102, 0x00000000)


Now I get something that says:

A problem has been detected and windows has been shut down to prevent damage to your computer.

Disable or uninstall any anti-virus, disc defragmentation or backup utilities. Check your hard drive configuration and check for any updated drivers; run CHKDSK/F to check for hard drive corruption and then restart your computer.

Stop 0x00000024 (0x00190203, x8A7FFEF0, 0xC0000102, 0x00000000

[ronallandottk]

Can you describe your hardware's specs?

Is it an old PC or is it newly built?

What was the last thing the PC was doing before it BSOD'd?

Did the BSOD display any particular error message?

Off the bat I'd say the cause is faulty memory, but it's to early to give a 100% answer. Try going here:

http://www.geekswhoknow.com/articles/stop-0x0000000A-0x000000A-irql_not_less_or_equal.htm

Awaiting further details.

[wendybell]

I forgot to put the specs when I first posted my request...sorry. I am not sure what exactly you might need. It is a Dell computer, XPS 400, with Pentium D Processor 820 with Dual Core Technology (2.8 GHz, 800FSB) We bought it in April 2006.
I don't know what was happening on it before it came up with those messages, it is my 13 year old son's computer. He plays all kinds of those war games on it. He just told me one day that his computer "wasn't working anymore"! It has been down for a number of months, kind of not high on my list of priorities to fix, but he keeps bugging me to get it working again...any help would be much appreciated!