Unsolved

This post is more than 5 years old

59 Posts

14059

September 22nd, 2005 16:00

Annoying Windows STOP error, possible bad device driver 0xC0000005...

I recently reinstalled Windows XP Home edition on my Dell Inspiron 1100. Twice in two days I have had windows pop up the blue screen with this stop error code:
 
stop error 0x0000008e, 0xc0000005, 0x8057a7aa, 0xf00bdbe0, 0x000000
 
It states it a bad driver, but how do I figure out which one it is? The only peripheral or device I use with the laptop is a Linksys wireless card. I don't have a hard disk partition with Diagnostics on it, so can someone recommend what is going on? I recently upgraded to SP2, which I never had problems with before I did the clean install. I've read online that this might be a bad graphics driver, but don't have a sure way of narrowing it down...
 
Thanks,
AC

4 Operator

 • 

20.1K Posts

September 22nd, 2005 18:00

Check the Hardware Device Manager in System Properties, Hardware tab. Shortcut: Windows Key + Pause break key.

59 Posts

September 22nd, 2005 19:00

All devices seem to be working properly, according to the Device Manager

59 Posts

September 22nd, 2005 21:00

After I reboot, Internet Explorer goes straight to microsoft.com and informs me this is driver related, but won't give any specifics besides all those error 0x00000 numbers. Will try to see the drivers loading at startup. Thanks for the tips

59 Posts

September 22nd, 2005 21:00

Ok, I tried the restart option to see the drivers loading. I don't know if this means anything, but the last driver on the list is something called Mup.sys  and the screen stays there for a while, not scrolling after that last driver, then a moment later the system boots up. Is "Mup.sys" microsoft update possibly? Never heard of it...

2.7K Posts

September 22nd, 2005 21:00

Hi,
 
The following will disable the Windows XP splash screen (logo) at startup, and show the list of drivers loading at startup.  You should be able to see which one has a problem loading
 
Click Start, Run and type MSCONFIG
Click the Boot.ini tab
Under Operating Systems section, select the appropriate entry and then enable the /SOS switch in the Boot Options section below
Click OK and close MSCONFIG utility.
 
Reboot and check it
 
The corresponding entry in the Boot.ini file is automatically added. Example given below:
 
multi(0)disk(0)rdisk(0)partition(5)\WINDOWS="XP Professional" /noexecute=optin /fastdetect
becomes
multi(0)disk(0)rdisk(0)partition(5)\WINDOWS="XP Professional" /noexecute=optin /fastdetect /sos
 
The /sos parameter displays the names of the drivers as they load during the boot process.
 
To return to normal startup just disable it again in msconfig
 
Does it actually tell you it is a driver error, as that Stop message can be bad RAM too?

2.7K Posts

September 22nd, 2005 22:00

Should you blame mup.sys?
It just happens that it is the last line put on the screen in safe mode before the GUI starts
It might not be the problem at all.
If it is mup.sys there are a lot of causes and solutions ranging from disabling all USB devices to RAM problems.
 
Here is a long discussion about it covering 2 years of people posting solutions
 
Have a look here for some more help in identifying it
Control Panel / Performance and Maintenance / Admin Tools / Event Viewer / System.
Look for "Red" errors. Double click on error.

59 Posts

September 23rd, 2005 00:00

I reinstalled all my Inspiron drivers in the order as suggested in the Reinstall Guide on Dell's support site. The wireless card driver was the last to install.

2 Intern

 • 

2.4K Posts

September 24th, 2005 15:00

Editorial:

I think you might have missed something on the install, perhaps the monitor's inf or a required BIOS/firmware update. Your system has numerous upgrades. You will have to talk to Dell as to exactly what you have to install on your system. That said, a few suggestions for you to try.

1.Run these 2 commands from Start|Run:

dxdiag and msinfo32 (look especially for conflicts in the second command result)

2. Run your AV program.
 
3. Bet these errors really jumped in when you installed SP2; do you have 2 firewalls running (eg NIS) ? If so, disable one. 
 
4. See if this Dell dload tells you anything.
 
 
5. Run AdAware. If the program finds objects then they might have corrupted the SP2 install. If that's the case (not likely) you might want to uninstall SP2  and run AdAware AND Spybot before you re-install SP2.
 
6. Q. When you go to the Windows update site-after the scan- does it offer a graphics driver in the optional updaate section ?
 
Sorry, this was the Dell dload that I meant to post.
 

Message Edited by maxd on 09-24-2005 05:46 PM

3 Posts

September 27th, 2005 06:00

I too have experience the same problem. I would boot up my machine and it would spontaneously crash core dump to the blue screen of death, then reboot several times a day randomly. I finally realized that if I turned off my wireless radio (disabling my wireless connection) it would be stable the entire day.

After several months I found the following to solve my problem, I'm guessing you have wireless on your machine as well.

Microsoft XP SP2 installs a Data Execution Prevention (DEP) function that messes up the NIC adapter driver. You can edit the boot.ini to DISABLE DEP by setting "/NoExecute=AlwaysOff" (mine originally had "/NoExecute=Optin").

Goto My Computer, right-click and select Properties>Advanced Tab>Settings (Startup and Recovery)>Edit
This will bring you to the boot.ini file. You might want to make a backup copy and place it on your desktop. Where you see "/NoExecute=", make sure it is changed to "AlwaysOff"

-r

59 Posts

September 27th, 2005 07:00

Hi,
 
Thanks for this tip. I will definitely try it. Yes, I do believe it's my Linksys card. SP2 probably messed its driver up. How do you backup boot.ini? 

3 Posts

September 27th, 2005 15:00

I just cut-n-pasted the text from the boot.ini into notepad, then save.

I figured if something goes wrong, I could cut-n-paste back to the boot.ini

-r
No Events found!

Top