Blue Screen Hell

[Fraser Shortt]

Within the past month or two, I've begun experiencing blue screens at
shutdown... virtually every time.

IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)

I've tested the RAM with Microsoft Windows Memory Diagnostic and memtest86.
No issues.

The hardware hasn't changed in over a year.
- Gigabyte EP45T-EXTREME F4
- Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
- Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
- 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black SATAII
- SAPPHIRE RADEON HD4870 512MB DDR5

I've rebuilt my system countless times and ultimately the error returns.

I've re-installed Windows XP Pro with SP2 and SP3.

The most recent build attempt, I installed Windows XP Pro SP2, drivers, SP3,
all Windows Updates, McAfee VirusScan Enterprise 8.5i, Office 2007 Ultimate
then SP2. When the system prompted for restart, the blue screen reappeared.

I can't figure this out. I've read about issues with Microsoft's Memory
Manager with XP SP2. What could possibly be causing these blue screens?

Any help would be greatly, GREATLY appreciated!

Thanks in advance,
FS

[Paul]

Fraser Shortt wrote:
> Within the past month or two, I've begun experiencing blue screens at
> shutdown... virtually every time.
>
> IRQL_NOT_LESS_OR_EQUAL
>
> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>
> I've tested the RAM with Microsoft Windows Memory Diagnostic and memtest86.
> No issues.
>
> The hardware hasn't changed in over a year.
> - Gigabyte EP45T-EXTREME F4
> - Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
> - Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
> - 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black SATAII
> - SAPPHIRE RADEON HD4870 512MB DDR5
>
> I've rebuilt my system countless times and ultimately the error returns.
>
> I've re-installed Windows XP Pro with SP2 and SP3.
>
> The most recent build attempt, I installed Windows XP Pro SP2, drivers, SP3,
> all Windows Updates, McAfee VirusScan Enterprise 8.5i, Office 2007 Ultimate
> then SP2. When the system prompted for restart, the blue screen reappeared.
>
> I can't figure this out. I've read about issues with Microsoft's Memory
> Manager with XP SP2. What could possibly be causing these blue screens?
>
> Any help would be greatly, GREATLY appreciated!
>
> Thanks in advance,
> FS
>

There is an example in this article, where a routine name is mentioned.

http://support.microsoft.com/?kbid=314063

[Paul]

Paul wrote:
> Fraser Shortt wrote:
>> Within the past month or two, I've begun experiencing blue screens at
>> shutdown... virtually every time.
>>
>> IRQL_NOT_LESS_OR_EQUAL
>>
>> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>>
>> I've tested the RAM with Microsoft Windows Memory Diagnostic and
>> memtest86. No issues.
>>
>> The hardware hasn't changed in over a year.
>> - Gigabyte EP45T-EXTREME F4
>> - Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
>> - Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
>> - 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black SATAII
>> - SAPPHIRE RADEON HD4870 512MB DDR5
>>
>> I've rebuilt my system countless times and ultimately the error returns.
>>
>> I've re-installed Windows XP Pro with SP2 and SP3.
>>
>> The most recent build attempt, I installed Windows XP Pro SP2,
>> drivers, SP3, all Windows Updates, McAfee VirusScan Enterprise 8.5i,
>> Office 2007 Ultimate then SP2. When the system prompted for restart,
>> the blue screen reappeared.
>>
>> I can't figure this out. I've read about issues with Microsoft's
>> Memory Manager with XP SP2. What could possibly be causing these blue
>> screens?
>>
>> Any help would be greatly, GREATLY appreciated!
>>
>> Thanks in advance,
>> FS
>
> There is an example in this article, where a routine name is mentioned.
>
> http://support.microsoft.com/?kbid=314063

Sorry, didn't finish that before Thunderbird decided to send it.

This is the example in the KB article.

STOP 0x0000000A (0xBFD14AAC, 0x000000FF, 0x00000000, 0x8000F67C)
IRQL_NOT_LESS_OR_EQUAL
***Address 8000f67c has base at 80001000 - hal.dll

If you had the routine name in the error message, that might
be more useful than the rest of the numbers. I don't know
of a way to probe my system, to map a number like "0x8000F67C"
to a piece of code.

Paul

[William R. Walsh]

Hi!

> IRQL_NOT_LESS_OR_EQUAL
> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)

This is not overly indicative of a memory problem. Instead it indicates a
driver that is doing something it should not.

I'd suggest leaving VirusScan out of the system for a while. If you
installed things in the order listed, it seems like a reasonable bet to
suspect it of causing problems. It may also be a good idea to install it
*after* you have set up all your other programs.

Also, be sure to get the latest drivers *direct from the chipset maker* when
you setting up your hardware. That goes for all your hardware--video,
chipset, audio, networking, etc.

On the hardware side, are you SURE that all your fans and heatsinks are
doing their thing? Have you tried swapping out some parts, like the video
card? How about your power supply? Is it honestly specified or were its
makers a bit...optimistic...regarding its capabilities? You may need a
voltmeter to find out if the supply is failing under load.

http://greyghost.mooo.com/psuthoughts/

William

[Gerry]

Fraser

What appears on the line under next line?
0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)

You may find the degree of diffulty for my next suggestion too much You
can use a Kernel Debugger to examine the 0x0000000A: IRQL Dump Report.
If you succeed in running the debugger post a copy of the Report and
obtain a stack trace.

Install Debugging Tools for Windows 32-bit Version
http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793589.aspx

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did not
have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
too high. (A kernel-mode process can access only other processes that
have an IRQL lower than, or equal to, its own.)
Source: http://aumha.org/a/stop.htm

You receive a "Stop 0x0000000A" error message in Windows XP
http://support.microsoft.com/kb/314063/

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Fraser Shortt wrote:
> Within the past month or two, I've begun experiencing blue screens at
> shutdown... virtually every time.
>
> IRQL_NOT_LESS_OR_EQUAL
>
> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>
> I've tested the RAM with Microsoft Windows Memory Diagnostic and
> memtest86. No issues.
>
> The hardware hasn't changed in over a year.
> - Gigabyte EP45T-EXTREME F4
> - Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
> - Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
> - 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black
> SATAII - SAPPHIRE RADEON HD4870 512MB DDR5
>
> I've rebuilt my system countless times and ultimately the error
> returns.
> I've re-installed Windows XP Pro with SP2 and SP3.
>
> The most recent build attempt, I installed Windows XP Pro SP2,
> drivers, SP3, all Windows Updates, McAfee VirusScan Enterprise 8.5i,
> Office 2007 Ultimate then SP2. When the system prompted for restart,
> the blue screen reappeared.
> I can't figure this out. I've read about issues with Microsoft's
> Memory Manager with XP SP2. What could possibly be causing these
> blue screens?
> Any help would be greatly, GREATLY appreciated!
>
> Thanks in advance,
> FS

[Fraser Shortt]

"Paul" > wrote in message
...
> Paul wrote:
>> Fraser Shortt wrote:
>>> Within the past month or two, I've begun experiencing blue screens at
>>> shutdown... virtually every time.
>>>
>>> IRQL_NOT_LESS_OR_EQUAL
>>>
>>> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>>>
>>> I've tested the RAM with Microsoft Windows Memory Diagnostic and
>>> memtest86. No issues.
>>>
>>> The hardware hasn't changed in over a year.
>>> - Gigabyte EP45T-EXTREME F4
>>> - Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
>>> - Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
>>> - 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black
>>> SATAII
>>> - SAPPHIRE RADEON HD4870 512MB DDR5
>>>
>>> I've rebuilt my system countless times and ultimately the error returns.
>>>
>>> I've re-installed Windows XP Pro with SP2 and SP3.
>>>
>>> The most recent build attempt, I installed Windows XP Pro SP2, drivers,
>>> SP3, all Windows Updates, McAfee VirusScan Enterprise 8.5i, Office 2007
>>> Ultimate then SP2. When the system prompted for restart, the blue
>>> screen reappeared.
>>>
>>> I can't figure this out. I've read about issues with Microsoft's Memory
>>> Manager with XP SP2. What could possibly be causing these blue screens?
>>>
>>> Any help would be greatly, GREATLY appreciated!
>>>
>>> Thanks in advance,
>>> FS
>>
>> There is an example in this article, where a routine name is mentioned.
>>
>> http://support.microsoft.com/?kbid=314063
>
> Sorry, didn't finish that before Thunderbird decided to send it.
>
> This is the example in the KB article.
>
> STOP 0x0000000A (0xBFD14AAC, 0x000000FF, 0x00000000, 0x8000F67C)
> IRQL_NOT_LESS_OR_EQUAL
> ***Address 8000f67c has base at 80001000 - hal.dll
>
> If you had the routine name in the error message, that might
> be more useful than the rest of the numbers. I don't know
> of a way to probe my system, to map a number like "0x8000F67C"
> to a piece of code.
>
> Paul

Hi Paul,

Thanks for responding.

Unfortunately, that's the problem. Nothing is listed. Just the following:

IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)

Actually, the more common memory reference is:

STOP: 0x0000000A (0xBAD0B204, 0x00000002, 0x00000001, 0x806E6A16)

There is no more information provided.

FS

[Fraser Shortt]

"William R. Walsh" >
wrote in message news:tZR8m.195063$DP1.194234@attbi_s22...
> Hi!
>
>> IRQL_NOT_LESS_OR_EQUAL
>> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>
> This is not overly indicative of a memory problem. Instead it indicates a
> driver that is doing something it should not.
>
> I'd suggest leaving VirusScan out of the system for a while. If you
> installed things in the order listed, it seems like a reasonable bet to
> suspect it of causing problems. It may also be a good idea to install it
> *after* you have set up all your other programs.
>
> Also, be sure to get the latest drivers *direct from the chipset maker*
> when you setting up your hardware. That goes for all your hardware--video,
> chipset, audio, networking, etc.
>
> On the hardware side, are you SURE that all your fans and heatsinks are
> doing their thing? Have you tried swapping out some parts, like the video
> card? How about your power supply? Is it honestly specified or were its
> makers a bit...optimistic...regarding its capabilities? You may need a
> voltmeter to find out if the supply is failing under load.
>
> http://greyghost.mooo.com/psuthoughts/
>
> William


Hi William,

Thanks for responding.

The issue didn't reappear this most reason rebuild until I installed Office
2007 SP2.

I've had McAfee VirusScan Enterprise on my system for years without issue,
but stranger things have happened.

I have downloaded the latest drivers from Gigabyte and ATI, but there has
been no improvement.

Honestly, no hardware has changed in a year. The only thing I've updated
within the last few months has been the usual Microsoft Updates and the ATI
video driver. Otherwise, everything is stock from a year ago.

FS

[Fraser Shortt]

Hi Gerry,

Thanks for responding.

Nothing appears under the STOP message. This is the crazy part. The
message is so unbelievably vague.

I've installed the debugging tools and forgive my noobishness, but how do I
configure it for the dump report?

Thanks in advance,
FS


"Gerry" > wrote in message
...
> Fraser
>
> What appears on the line under next line?
> 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>
> You may find the degree of diffulty for my next suggestion too much You
> can use a Kernel Debugger to examine the 0x0000000A: IRQL Dump Report.
> If you succeed in running the debugger post a copy of the Report and
> obtain a stack trace.
>
> Install Debugging Tools for Windows 32-bit Version
> http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx
>
> Background information on Stop Error message
> http://msdn2.microsoft.com/en-us/library/ms793589.aspx
>
> 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
> Typically due to a bad driver, or faulty or incompatible hardware or
> software. Use the General Troubleshooting of STOP Messages checklist
> above. Technically, this error condition means that a kernel-mode
> process or driver tried to access a memory location to which it did not
> have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
> too high. (A kernel-mode process can access only other processes that
> have an IRQL lower than, or equal to, its own.)
> Source: http://aumha.org/a/stop.htm
>
> You receive a "Stop 0x0000000A" error message in Windows XP
> http://support.microsoft.com/kb/314063/
>
> --
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> Fraser Shortt wrote:
>> Within the past month or two, I've begun experiencing blue screens at
>> shutdown... virtually every time.
>>
>> IRQL_NOT_LESS_OR_EQUAL
>>
>> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>>
>> I've tested the RAM with Microsoft Windows Memory Diagnostic and
>> memtest86. No issues.
>>
>> The hardware hasn't changed in over a year.
>> - Gigabyte EP45T-EXTREME F4
>> - Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
>> - Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
>> - 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black
>> SATAII - SAPPHIRE RADEON HD4870 512MB DDR5
>>
>> I've rebuilt my system countless times and ultimately the error
>> returns.
>> I've re-installed Windows XP Pro with SP2 and SP3.
>>
>> The most recent build attempt, I installed Windows XP Pro SP2,
>> drivers, SP3, all Windows Updates, McAfee VirusScan Enterprise 8.5i,
>> Office 2007 Ultimate then SP2. When the system prompted for restart,
>> the blue screen reappeared.
>> I can't figure this out. I've read about issues with Microsoft's
>> Memory Manager with XP SP2. What could possibly be causing these
>> blue screens?
>> Any help would be greatly, GREATLY appreciated!
>>
>> Thanks in advance,
>> FS
>

[Anna]

> Fraser Shortt wrote:
>> Within the past month or two, I've begun experiencing blue screens at
>> shutdown... virtually every time.
>>
>> IRQL_NOT_LESS_OR_EQUAL
>>
>> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>>
>> I've tested the RAM with Microsoft Windows Memory Diagnostic and
>> memtest86. No issues.
>>
>> The hardware hasn't changed in over a year.
>> - Gigabyte EP45T-EXTREME F4
>> - Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
>> - Kingston KHX11000D3LLK2/4G HyperX 2x2GB DDR3 1375Mhz CL-7 non ECC
>> - 3 x Western Digital WD1001FALS 1TB 32MB 7200rpm Caviar Black SATAII
>> - SAPPHIRE RADEON HD4870 512MB DDR5
>>
>> I've rebuilt my system countless times and ultimately the error returns.
>>
>> I've re-installed Windows XP Pro with SP2 and SP3.
>>
>> The most recent build attempt, I installed Windows XP Pro SP2, drivers,
>> SP3, all Windows Updates, McAfee VirusScan Enterprise 8.5i, Office 2007
>> Ultimate then SP2. When the system prompted for restart, the blue screen
>> reappeared.
>>
>> I can't figure this out. I've read about issues with Microsoft's Memory
>> Manager with XP SP2. What could possibly be causing these blue screens?
>>
>> Any help would be greatly, GREATLY appreciated!
>>
>> Thanks in advance,
>> FS

> Hi Paul,
>
> Thanks for responding.
>
> Unfortunately, that's the problem. Nothing is listed. Just the
> following:
>
> IRQL_NOT_LESS_OR_EQUAL
>
> STOP: 0x0000000A (0xBAD0B1CC, 0x00000002, 0x00000001, 0x806E6A16)
>
> Actually, the more common memory reference is:
>
> STOP: 0x0000000A (0xBAD0B204, 0x00000002, 0x00000001, 0x806E6A16)
>
> There is no more information provided.

> Hi William,
>
> Thanks for responding.
>
> The issue didn't reappear this most reason rebuild until I installed
> Office 2007 SP2.
>
> I've had McAfee VirusScan Enterprise on my system for years without issue,
> but stranger things have happened.
>
> I have downloaded the latest drivers from Gigabyte and ATI, but there has
> been no improvement.
>
> Honestly, no hardware has changed in a year. The only thing I've updated
> within the last few months has been the usual Microsoft Updates and the
> ATI video driver. Otherwise, everything is stock from a year ago.

> Hi Gerry,
>
> Thanks for responding.
>
> Nothing appears under the STOP message. This is the crazy part. The
> message is so unbelievably vague.
>
> I've installed the debugging tools and forgive my noobishness, but how do
> I configure it for the dump report?
>
> Thanks in advance,
> FS


Fraser...
Since you state that the problem you describe didn't "reappear" until you
installed Office 2007 SP2, we'll assume that if you now uninstall that
program the problem still remains, right? So that (apparently) your problem
has nothing to do with that program install.

I'm assuming that you're working with a non-RAID configuration.

Just to determine that a corrupted OS may be the source of the problem, have
you considered or actually undertaken a Repair install of the OS? I assume
you're reasonably familiar with the process. If you do decide to do so, work
only with your boot drive, uninstalling the other two HDDs. (I take it you
ordinarily work with three (3) SATA HDDs, yes?)

It is possible, of course, that the problem is hardware-related. But first I
would suggest a Repair install of the OS to determine if a corrupted OS is
the source of the problem. Before doing so I would suggest that if you use a
disk-cloning or disk-imaging program, you clone/image the contents of your
boot HDD to another HDD or at the least ensure that any important files on
the boot drive have been copied over to some other media.

If it appears the problem is hardware-related I would have some other
suggestions for you should you be interested.
Anna

[LCD[_6_]]

When nothing helps. You have an option to replace your motherboard
and/or power supply unit.