Blue Screen

[TheGreatAndMerciless]

Windows XP Pro w/SP3. Shortly after Windows fully boots I am getting the blue screen that reads:

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

INVALID_PROCESS_ATTACH_ATTEMPT

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

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you may need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select advances startup options, and then select safe mode.

Technical information:

***STOP: 0X00000005 (0X8695E020, 0X86FCA830, 0X00000001, 0X00000000)"

Two seconds after this blue screen appears, the computer reboots and keeps repeating this cycle. I know what is written on the blue screen because I used my camera to photograph it.

It is not a memory problem as the computer contains four 1GB memory modules and I have removed them and inserted memory from another computer with the same blue screen repetition.

However, I am certain that it is a hardware rather than a software problem. This is a certainty because I have several backups on other hard drives. Each hard drive boots fully and then shows the blue screen briefly and then reboots to do the same thing over and over again.

The computer was running perfectly and suddenly began this blue screen error problem. No new hardware or software has been recently added. The four backups are from four to fourteen days old.

If anyone can offer a clue as to the culprit or a way to identify the offending item, I will be most grateful.

 

[Zen216]

I see this on microsoft site

Error Message:
STOP: 0x00000005 (parameter, parameter, parameter, parameter) INVALID_PROCESS_ATTACH_ATTEMPT

Explanation:
This is a Windows 2000 Executive character-mode STOP message. It indicates a problem with an owned mutex or a mutex with a process already attached.

User Action:
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

have you installed any new hardware,,, or was it a sp3 install that killed the computer?

 

[Zen216]

this might help as well,

http://www.windowsbbs.com/showthread.php?t=58720

 

[wolluf]

If no new hardware/software & you've tried known good memory, points to a failure of another hardware item - likely the motherboard/processor! But can you swap out other items (if you have any graphics, sound, network cards etc, disconnect non-vital ones, and replace vital with known good. Try another PSU. Try another keyboard & mouse. Disconnect optical drives). If all makes no difference, does point to mobo - might be worth clearing the cmos and reloading fail-safe defaults.

PS. Could also try a clean install on another drive if one available - to see if that fails or not and if it does, might get some more clues. If it doesn't, then sounds like something has corrupted the system registry hive on your current installation. In which case a repair reinstall might fix it - or restoring a previous registry file set as per my post in this thread -

http://www.tek-tips.com/viewthread.cfm?qid=1451418&page=1

Good luck!

 

[BadBigBen]

You receive the Stop error "Stop 0x05 (INVALID_PROCESS_ATTACH_ATTEMPT)" in Windows XP Service Pack 2 or Windows Server 2003

This problem occurs because a coding error in the Http.sys file causes stack corruption. This problem occurs if the following conditions are true:
• TDI filter drivers are installed on your computer. TDI filter drivers are typically installed by antivirus or firewall programs.
• The installed TDI filter drivers return STATUS_PENDING to the TDI_SET_EVENT_HANDLER I/O request, so that the call is processed as an asyncronous APC.
A coding error in the Http.sys file may cause stack corruption when the TDI filter driver finishes processing the TDI_SET_EVENT_HANDLER I/O request asynchronously on a different thread. The stack for the original thread is overwritten when the I/O request is processed. This causes the Stop error message.

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

and it talks about Firewalls and AntiViral software and SP2, so if they updated lately to a newer version it could be the cause...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[TheGreatAndMerciless]

PROBLEM SOLVED

Thanks to all of you for your efforts to assist me with my dilemma. I solved the problem by dismantling the computer's hardware and then putting it all back together. I also unplugged and reattached all wires. I have no idea which item was causing the problem as I did everything in the same operation rather than piecemeal. Whatever it was, the computer is again functioning as it did prior to experiencing this glitch.

 

[BadBigBen]

Glad you got it running...

probably a bad contact there somewhere, and the OS could not address the hardware correctly...


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."