Hi
Further to my recent enquiry to which lurkswithin responded, I have been able to capture the stop code: 0x0000008E (0xC0000005, 0x8058E764, 0xAFA40CAC, 0x00000000).
Your assistance would be much appreciated.
Regards

Roger

There is a current rootkit (a virus of a sort) that is basically undetectable at this time creating this exact problem. It started sometime after opening an attachment from email or AIM and it hides itself very effectively from applications looking for it!

Rustock rootkit v 1.2
Z:\NewProjects\spambot\new\driver\objfre\i386\driv er.pdb

Look for this file in windows mini dump logs.

To configure startup and recovery options to use the small memory dump file, follow these steps.

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump (64k).
The file created should appear in the root of the drive where Windows is installed.

Symantic has a way to maunually remove it follow the directions :

Backdoor.Rustock.B Removal - Removing Help | Symantec

Good Luck!

Many thanks for your assistance, Lurkswithin.
I am not sure what mini dump logs are but will look for them!
You refer to "Symantec has a way to manually remove it" - what if I am not covered by Symantec? My anti-virus application is Avira.
Regards

Roger

The manual removal instructions are for anyone's use in removing the application. Just click the symantic link and it will take you to the correct page with the instructions for removal. If you do not feel comfortable in dealing with removing scripting then you will either need to find someone to help or rely on a repair shop or resort to formatting and reinstalling your operating system....might be best anyway as sometimes the removal of this type of application is next to impossible.

Hi Lurkswithin
Many thanks for your assistance.
Regards

Roger

I have an Acer Aspire 4720z laptop. I tried to upgrade to SP2 for Vista then on reboot after upgrade I got the BSOD. My client wants XP Pro, so I do a clean install, by deleting the partitions and creating a new, formatted C: drive. After setup loads files and reboots back into setup I get this Error 0x0000007e (0xc0000005, 0x806084a7, 0xf78a6364, 0xf78a6060). With nothing else referred to except the same old could be a driver for new hardware, which it isn't....I think.
Any help anyone might have would be incredibly helpful!!!!
Thank you!