Re: Blue Screen Hell

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




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


.



Relevant Pages

  • Re: Service Pack 2
    ... Should have edited the output to stop at the hardware. ... I do not see anything there preventing you from running SP2. ... After you have the latest hardware drivers, ... BEFORE you install. ...
    (microsoft.public.windowsupdate)
  • Re: Crashes and the Blue Screen of Death!
    ... but the most common cause is hardware failure. ... The most common cause of this is hardware memory corruption. ... are listed on the Windows 2000 Hardware Compatibility List. ... recommended that all users install them as they become available. ...
    (microsoft.public.win2000.general)
  • Re: Blue Screen
    ... If the bluescreens would have occured after ... You really do have to exchange hardware (right ... Infact when you install ... > these bluescreen issues by reading the bluescreens and analysing the memory ...
    (microsoft.public.windowsxp.general)
  • Re: Blue Screen/shut down
    ... failed memory hardware. ... applications, drivers, or system services. ... >>You have to install drivers in order for hardware to ...
    (microsoft.public.windowsxp.newusers)
  • Re: !!!Do not load SP2!!!
    ... Microsoft should not put out service packs (and hypoe them as being next to ... tries to load on a DOT4 port, but the install can't find the printer. ... >> SP2 that caused the original problem. ... >> hardware supported and everything was fine until I installed SP2. ...
    (microsoft.public.windowsxp.general)