Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on Mup.sys


  • Please log in to reply
10 replies to this topic

#1 elomont

elomont

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:04:11 AM

Posted 21 August 2009 - 05:39 PM

I will recap what I was doing when it first occurred......

The last thing I did was a Windows Update. There was about 14 updates. Restarted to a BSOD. It reads variations of 0x000000fc, f, b as the errors. Safe boot with any option (networking, plain old safe boot, etc) leads to BSOD. It hangs on MUP.sys any way I try to start. No new hardware has been added. Just Windows Updates.

Here's another tidbit of info. If I disconnect the USB keyboard and mouse and boot, it will make it the Windows Logon screen where you can select from different users. However, since both the keyboard and mouse are unplugged you can get no further. When you plug in either the keyboard or mouse you instantly get the infamous BSOD again. Maybe that info will help one of you..........

I have since removed the drive and attached it to my desktop and am using it as a slave. I can access everything that is on the drive. So, I guess my question is how do I circumvent the Mup.sys file? Can I rename it with a good version and just rename the old so that it is not recognized on startup? I have my own personal Windows Pro CD, can I copy any files from there onto her drive to correct the problem?

Another idea.......Can I delete the Windows Updates from that hard drive while I have it as a slave? I'm thinking not, but you guys can confirm. If so, I would need the steps. Remember, the drive won't boot, but I do have access to all the files.

I'm editing here and adding some more info........I have also tried Recovery Console which leads me to a screen which reads that it does not detect a drive after I press R for recovery. It reads the same if I try to do a "repair". Just in case any of you were going to suggest that route.

Any ideas? Thank you in advance. Ask any questions you need to I will try to answer them.

She is running Windows Media Center and chkdsk finds no errors.

Edited by elomont, 21 August 2009 - 05:59 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,754 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:11 AM

Posted 21 August 2009 - 06:54 PM

<<I can access everything that is on the drive.>>

<< I have also tried Recovery Console which leads me to a screen which reads that it does not detect a drive after I press R for recovery. It reads the same if I try to do a "repair". Just in case any of you were going to suggest that route.>> The Recovery Console ought to see the Media Center drive as a second drive with a Windows install.

Those seem a bit incompatible to me. Did you try running chkdsk /r on the troublesome drive you claim to be able to access?

<<I have my own personal Windows Pro CD, can I copy any files from there onto her drive to correct the problem?>>

Sure...if you know what files and what problem.

What I would have done...is use the XP Pro CD to run the Recovery Console on her system, no problem with that. Even though Media Center is supposed to be a modified version of XP Pro, I would not try a repair install of either using the other's CD.

Funny...I've seen no mention of a Media Center disk or recovery/restore CDs.

Please post exact error messages, rather than cliffnotes versions...the details matter.

Louis

#3 elomont

elomont
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:04:11 AM

Posted 23 August 2009 - 08:22 PM

To anyone new reading this I have copied and pasted the previous persons questions and then followed them with my answers.................

I can access everything that is on that drive......means I've removed the drive from the original computer and installed it as a slave on my desktop. It is listed as my F: drive. I still cannot boot from it, but I can get "into" it meaning I can read files, folders, etc.

I have also tried Recovery Console which leads me to a screen which reads that it does not detect a drive after I press R for recovery. It reads the same if I try to do a "repair". Just in case any of you were going to suggest that route.>> The Recovery Console ought to see the Media Center drive as a second drive with a Windows install..............The Recovery Console does not recognize the drive as being installed even though the drive IS recognized it in BIOS. Strange I know.

I have my own personal Windows Pro CD, can I copy any files from there onto her drive to correct the problem?............I do not know which files are causing the problems. Hence, my post.

What I would have done...is use the XP Pro CD to run the Recovery Console on her system, no problem with that. Even though Media Center is supposed to be a modified version of XP Pro, I would not try a repair install of either using the other's CD.............As stated above when booted from the XP Pro CD the hard drive is not detected after either R or a fresh install is selected.

Funny...I've seen no mention of a Media Center disk or recovery/restore CDs........I will ask, but I'm sure she does NOT have either.

Please post exact error messages, rather than cliffnotes versions...the details matter..............the errors messages vary, but here is a short list......

0x0000007e, 0x000000fc, 0xc0000005, 0xf7a238ea, 0xf7a237f4, 0xf7a234f0, 0xf7a1b8ea, 0xf7a1b744, 0xf7a1b4f0, 0xf79d98e8, 0x0743c963, 0x79d9848, 0x00000001..........if you need more let me know.


I have some logs (VETlog.txt) which may help in pinpointing what is wrong. I also could be talking out of my rear, but I will post one here. This log is dated the same day when I started having the BSOD problem......
[/b]
OS Date: 08/20/09
OS Time: 10:37:32
Process Id: 1256
Process File: C:\Program Files\America Online 9.0\waol.exe
Command line: "C:\Program Files\America Online 9.0\waol.exe" -f"Internet Explorer;iexplore.exe;0" -s
Thread Id: 704(0x2c0)
Module handle: 0x14800000
Module File: C:\Program Files\Viewpoint\Viewpoint Experience Technology\AxMetaStream_0305000D.dll
Module version: MTS: 3,5,0,13; Dll: 3.5.0.13

Processor Intel Pentium Family 15 Model 6 Stepping 4 (2 Processor(s))
OS 344158752 Build 2600 Service Pack 2
Normal Boot
1 Monitor(s) Primary resolution is 1280 x 1024

EXCEPTION_ACCESS_VIOLATION: The thread attempted to read from or write to a virtual address for which it does not have the appropriate access.

Stack:
AOLUserShell.dll! 0x20c00000 + 0x15031()
AOLUserShell.dll! 0x20c00000 + 0x487b5()
AOLUserShell.dll! 0x20c00000 + 0x391f0()
AOLUserShell.dll! 0x20c00000 + 0x377bc()
AOLUserShell.dll! 0x20c00000 + 0x126d9()
AxMetaStream_0305000D.dll! 0x14800000 + 0x1278()
AxMetaStream_0305000D.dll! 0x14800000 + 0xe1b3()
AxMetaStream_0305000D.dll! 0x14800000 + 0xe065()
AxMetaStream_0305000D.dll! 0x14800000 + 0xeb4b()
AxMetaStream_0305000D.dll! 0x14800000 + 0x4aa4()
OLEAUT32.dll! 0x77120000 + 0x16390()
AxMetaStream_0305000D.dll! 0x14800000 + 0x4fe1()
VBScript.dll! 0x73300000 + 0x15a26()
VBScript.dll! 0x73300000 + 0x159a4()
VBScript.dll! 0x73300000 + 0x4dd3()
VBScript.dll! 0x73300000 + 0x523d()
VBScript.dll! 0x73300000 + 0x21b5()
VBScript.dll! 0x73300000 + 0x508c()
VBScript.dll! 0x73300000 + 0x21b5()
VBScript.dll! 0x73300000 + 0x3e91()
VBScript.dll! 0x73300000 + 0xbcb1()
VBScript.dll! 0x73300000 + 0xd5c4()
VBScript.dll! 0x73300000 + 0xd40a()
actvx.rct! 0x6a100000 + 0x91a1()
actvx.rct! 0x6a100000 + 0x1b1a()
actvx.rct! 0x6a100000 + 0x74c9()
supersub.dll! 0x60580000 + 0x5535()
supersub.dll! 0x60580000 + 0x5752()
supersub.dll! 0x60580000 + 0x12f70()
supersub.dll! 0x60580000 + 0x13734()
supersub.dll! 0x60580000 + 0x13cc2()
supersub.dll! 0x60580000 + 0x13e7a()
supersub.dll! 0x60580000 + 0x14c64()
supersub.dll! 0x60580000 + 0x5535()
supersub.dll! 0x60580000 + 0x5752()
supersub.dll! 0x60580000 + 0x12f70()
supersub.dll! 0x60580000 + 0x13734()
supersub.dll! 0x60580000 + 0x13cc2()
supersub.dll! 0x60580000 + 0x1415c()
supersub.dll! 0x60580000 + 0x1437c()
supersub.dll! 0x60580000 + 0x14424()
Stop displaying stack!!

Additional parameters:
0x1
0x3d088889

Registers context:
EDI: 0x76756964
ESI: 0x3d088889
EBX: 0x2c0
EDX: 0x8
ECX: 0x0
EAX: 0x0
EBP: 0x13dd38
EIP: 0x20c15031
ESP: 0x13dbe4

AxMetaStream_0305000D.dll 3.5.0.13
ComponentMgr.dll 3.5.0.28
ZoomView.dll 3.2.2.26
WaveletReader.dll 3.6.0.59
VMPVideo2.dll 3.4.0.67
VMPVideo.dll 3.2.2.26
VMPSpeech.dll 3.2.2.26
VMPExtras.dll 3.0.7.36
VMPAudio.dll 3.2.2.26
VMgr.dll 1.0.0.43
VectorView.dll 3.2.2.26
SWFView.dll 3.6.0.59
SreeDMMX.dll 3.4.0.67
ServiceComponent.dll 3.2.2.26
SceneComponent.dll 3.5.0.28
ObjectMovie.dll 3.2.2.26
MTS3Reader.dll 3.6.0.59
LensFlares.dll 3.2.2.26
JpegReader.dll 3.6.0.59
GifReader.dll 3.2.2.26
DataTracking.dll 3.0.8.201
Cursors.dll 3.4.0.67
AOLUserShell.dll 3.2.2.26
AOLShell.dll 3.0.11.26
AOLArt.dll 3.0.7.36

Where: DoCommandInternal

One parting question.......Since I can access cmd while it is installed in my desktop as a slave can I run any commands on it besides chkdsk, which I have already done, to correct the problem?

Some other particulars about the machine in question.......

Dell XPS 200
Windows Media Center Edition 2005
Intel Pentium D

Edited by elomont, 23 August 2009 - 08:24 PM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,754 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:11 AM

Posted 24 August 2009 - 05:41 AM

FWIW: The BIOS will generally recognize any drive that is properly connected. My Computer/Explorer will reflect any drive that is properly connected and which is properly partitioned with either NTFS or a FAT file system.

FWIW: The Recovery Console is applicable for all versions of XP. If the RC does not recognize a Windows installation...my guess is that it's one of two things. Either the file structure of that partition is damaged...or the partition/drive itself has physical problems. In either instance, the most important thing is to remove any valued data files...to a safer location.

STOP errors occur with regularity in XP/Windows. The www.aumha.org website has (IMO) the most complete yet concise guide to interpreting/troubleshooting STOP errors. You can visit it, if you like and verify the data that is summarized below. Where I make any reference to General Troubleshooting checklist, the following steps are referenced:

General Troubleshooting of STOP Messages
If you can’t find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.

1. Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.

2. If you’ve recently added new hardware, remove it and retest.

3. Run hardware diagnostics supplied by the manufacturer.

4. Make sure device drivers and system BIOS are up-to-date. However, if you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.

5. Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.

6. Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn’t, then pay particular attention to the non-HCL hardware in your troubleshooting.

7. Check for viruses.

8. Investigate recently added software.

9. Examine (and try disabling) BIOS memory options such as caching or shadowing.

Concise summary of STOP errror messages noted in your post:

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
No generic explanation, specific data for specific situation at http://support.microsoft.com/kb/886348 AND http://windowsitpro.com/article/articleid/...ute_memory.html

0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
Generally, use the General Troubleshooting of STOP Messages checklist above to troubleshoot this problem.

http://www.tek-tips.com/viewthread.cfm?qid...3434&page=1 contains data on cited STOP error 0x00000001.

Additional info: Most STOP error messages indicate the possibility of memory problems, because it is in the memory that most of the errors I've seen first come to light. This doesn't necessarily mean that the memory is good or not good...it merely indicates the scene of the accident/crime (not the cause).

Viewpoint Experience Technology seems to be something that is bundled with AOL, as well as some type of multimedia plugin. http://www.google.com/search?hl=en&q=+...mp;oq=&aqi=

From the data that you posted, I'd say that VET seems to be responsible for at least one of the STOP errors.

<<Since I can access cmd while it is installed in my desktop as a slave can I run any commands on it besides chkdsk, which I have already done, to correct the problem?>>

As previously suggested, running chkdsk /r on that drive...would be my first step. The Recovery Console is not the only method for running this command, once a user is able to either boot the partition or access files on it from another system.

From your desktop: Start/Run...type chkdsk F: /r (with exact spacing depicted here) and hit Enter. You may get an error message, in which case you should post it here.

Louis

#5 elomont

elomont
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:04:11 AM

Posted 07 September 2009 - 10:26 AM

I'm finally remembering to post the solution that worked for me......

It was very simple. I ended up asking the woman if she had the original OS disk that came with the computer when she bought it. Surprisingly, she actually did have it. I ended up putting it in, running a repair of the OS (not recovery) and it corrected whatever problems were wrong.

What I did learn was that my own personal OS disk (XP Pro) could not be used to correct her computer which was running XP Media Center Version 2005. When I did use mine, the repair function would not even detect her current OS. However, when I put her original disk in her OS was detected and I was able to run the repair function.

If anything is not clear in my description of the solution I found, please ask. Maybe I can clarify a bit more.

Hopefully this will help someone else.

Edited by elomont, 07 September 2009 - 10:50 AM.


#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,754 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:11 AM

Posted 07 September 2009 - 12:26 PM

Your solution makes sense...feedback appreciated...happy computing :thumbsup:.

Louis

#7 joseibarra

joseibarra

  • Members
  • 1,187 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:04:11 AM

Posted 07 September 2009 - 01:17 PM

Another mup.sys suspicion, but I am getting quite convinced it is not mup.sys at all (it just looks like it), but what comes after that is the problem.

I have not seen one in a long time, but it sure would be nice to know more about that BSOD to try to narrow it down to one component.

Since elomont says that the system booted okay without keyboard and mouse, that convinces me more that what comes after mup.sys is related to those devices (probably USB elomont?). I would pull the mouse first. This is going to factor into my "hung on mup.sys" troubleshooting, does it hang with no KB/M, etc. I don't know what to do if you say yes, but maybe can figure it out.

What loads next depends but if you could figure it out, it might be easier to understand and fix for folks that don't have an installation CD for a Repair. Sure beats the heck out of a reinstall if it is just one file or driver or something...

A Repair might fix it, but that does a lot of things!

I read it is possible to bypass mup.sys in Safe Mode to determine the next item and focus the investigation there. Haven't tried it yet and don't know how to inflict this problem on myself. Then I could make a troubleshooting copy/paste.

I'm going to read through the BC for mup.sys problems and look for more patterns.

Where is a hung on mup.sys system when I need one!

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#8 elomont

elomont
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:04:11 AM

Posted 07 September 2009 - 01:43 PM

To tell you the truth Jose running the repair function using her original OS disk corrected the problem and she did not lose any of her data so that is good enough for me. She already has the computer back and she is good to go.

I'm no professional by any means, but I'm slowly gaining experience and have come to realize that sometimes computers are just squirrelly and will do weird things sometimes. As long as I learn something from fixing them and the person can use the computer afterwards without losing too much or any data is my goal.

The computer would load without the KB or M attached, but then when it got to the selection of the user names screen you were out of luck because you did not have either attached and therefore could not select a user. When you did plug in the USB KB or M it would instantly give you a BSOD.

I understand where you are coming from with wanting to know exactly what the problem is and what you need to do to correct the problem, but I'm under the impression that it may not be the same fix every time for every computer. Follow me? Someone else with more experience may be able to give you a more comforting response. LOL.

All I know is that it is fixed and she is back up and running for free.

#9 joseibarra

joseibarra

  • Members
  • 1,187 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:04:11 AM

Posted 07 September 2009 - 03:39 PM

That is a good thing.

I have just become personally annoyed with this mup.sys thing - another poster has it, but only in Safe Mode. Things I can't figure out bother me.

I am trying to zero in on something other than a hit and miss method to figuring it out, and your clues are most helpful.

I am leaning heavily toward something with the mouse and USB port as step 1:

1. Unplug the mouse, does it work now.

I am just not sure what to do next! The other poster has a laptop with external USB KB&M and I don't know what happened yet when he tried unplugging and just using the built in touchpad. I think it would work, and I know what loads next after mup.sys on his, but just don't know what to do about it yet. A BSOD complicates it more, but there must be clues there.

I am not saying a Repair is necessarily hit or miss, but I would like to know the problem in more detail (wish I had it right here) for folks that don't have that option :thumbsup:

Happy trails!

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#10 hamluis

hamluis

    Moderator


  • Moderator
  • 55,754 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:11 AM

Posted 07 September 2009 - 04:03 PM

Well...any attempted repair install IS hit-or-miss, it's the last safe (relatively safe) thing that can be tried...before a clean install.

But a repair install won't handle either malware or hardeware problems.

It was probably a corrrupt/damaged file. My system has over 1 million files on it, I would lose any sleep trying to understand how 1 of them could become damaged and then malperform :thumbsup:.

Sometimes a scattergun is what is needed :flowers:.

Louis

#11 joseibarra

joseibarra

  • Members
  • 1,187 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:04:11 AM

Posted 07 September 2009 - 08:58 PM

Well, I'll tell you! I'm having a good time and learning a lot!

I figured out enough stuff along the way to reduce my "boot time" down to 122 seconds from 208 seconds with just a little understanding and couple tweaks that are not kooky or cutting any corners at all.

A whole 86 seconds I didn't know I was even missing. I'm screamin' man! :thumbsup: Like I boot all the time, right?

I know - mileage is variable... :flowers:

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users