Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Physical memory Dump


  • Please log in to reply

#31
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
I tried to download the Who crashed it but when I got to the analyze part it said I didn't have the right debugging software from Microsoft. It gave me the option to download it, so I did and then at the end it said because I was in safemode the installer wouldn't work. So, ultimately it appears I can't run the analyzer. Any suggestions?
  • 0

Advertisements


#32
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
Windows XP is set by default to reboot your computer when it hits a critical error.
For most users I suppose this is a good thing, as no one likes to see the BSOD
But in this case, we actually WANT to see the BSOD because it contains some useful
information in diagnosing the problem.
In order to force your computer to show you the BSOD, need to tell it to stop auto restarting
on critical errors.

Right-click...My Computer... and then click ...Properties...
Click the ..Advanced tab... Under Startup and Recovery.. click ..Settings...
to open the Startup and Recovery dialog box....
Clear the ..Automatically restart.. check box, and click OK the necessary number of times...

Restart your computer for the settings to take effect....

also use the add/remove programs in the control panel to remove avg...its one a lot of the errors...we can reinstall it after we get you going again...

we need to tell Windows that Windows Installer is a “safe” service. click start... and run..type in
REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer” /VE /T REG_SZ /D “Service” net start msiserver press enter...
Long... but it’ll list the Windows Installer Service as legitimate for Safe Mode. You can actually do this trick for any service, but don’t overdo it: Safe Mode is supposed to be minimal to make sure Windows can start....
then you should be able to install whocrashed...
DUH... :) I forgot ...WhoCrashed will install the debuger if its not already on your system when it installs itself...try downloading WhoCrashed to the misbehaving system while your connected internet in safe mode with networking..and then run it..it will go get the debugger...

Edited by happyrock, 02 February 2009 - 04:59 PM.

  • 0

#33
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
Ok, the automatically restart box was NOT checked when I went to change it. JUST FYI. . The system froze up when I was trying to uninstall AVG. So, Im going to try and start it again in safemode with networking and do that. And then try to install Who crashed. Also, I think I said it incorrectly before about installing Whocrashed. It said that the degugging may be an incorrect version and so my only option was to try and install it. I will try your sugesstions though and see how this comes out. THanks!!
  • 0

#34
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
I got the same error again. When I did the run command it didn't do anything after I hit enter. Also, just to make sure I entered it all correctly. Does it matter if those are caps or lower case.



This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not normally installed and is not redistributable, we suggest you select the download option from below. Then the right package will be downloaded to a temporary folder and the required files will be extracted from the package automatically. You only need to do this once. In case you do have WinDbg available on your computer, make sure it is the right version for your computers architecture, then you can select the option to locate WinDbg yourself.

It gave me again the option to install from microsft or locate it myself (which I didn't know if/where it was on the computer)
  • 0

#35
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
Ok, with your help I'm feeling slightly geekish :) . I successfully unistalled AVG and that enabled me to load windows normally, which allowed me to get Whocrashed using the installer. Just FYI, I copied your instructions onthe run reg add option (before I restarted after uninstalling AVG) and I still couldn't download it. SEE previous notes. ANyway, here we are! YEAH. So, now what?

Oh and when windows loaded it gave me a RUNDLL error. THe same as I mentioned before.


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 1/19/2009 3:14:50 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8056E35F, 0xF79066CC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 1/12/2009 2:10:44 AM your computer crashed
This was likely caused by the following module: toside.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xF8A40005, 0xEEC5FCB0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\toside.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Toshiba PCI IDE Controller
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 1/2/2009 4:04:11 AM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xEE470030, 0x0, 0xF8AF2959, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\mssync20.sys



On Fri 1/2/2009 3:25:18 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xF8A50000, 0x0, 0xF8A50000, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Fri 1/2/2009 2:32:30 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xF8AC0000, 0x0, 0xF8AC0000, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Thu 1/1/2009 7:37:19 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81D14C1F, 0xF89FBC2C, 0xF89FB928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 1/1/2009 5:50:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81D2AC1F, 0xF7A43C2C, 0xF7A43928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 12/29/2008 11:40:25 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81D29C1F, 0xF79A8C2C, 0xF79A8928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 12/22/2008 3:42:24 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81ED4C1F, 0xF81FBC2C, 0xF81FB928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 9/8/2008 5:02:02 PM your computer crashed
This was likely caused by the following module: ialmdd5.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF09D455, 0xEF1869DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology



On Sat 9/6/2008 6:02:53 PM your computer crashed
This was likely caused by the following module: ialmdd5.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF09D455, 0xEDE2F9DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology



On Sat 9/6/2008 2:13:33 AM your computer crashed
This was likely caused by the following module: ialmdd5.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF09D455, 0xEE1799DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology



On Sun 4/20/2008 2:27:10 PM your computer crashed
This was likely caused by the following module: drvmcdb.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x805809A6, 0xEF868994, 0xEF868690)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on drvmcdb.sys





On Fri 3/9/2007 2:07:20 AM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xEE9C7000, 0x1, 0xF8AE64CD, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\mssync20.sys



On Wed 1/17/2007 8:39:07 PM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xEE0C0030, 0x0, 0xF8AE8959, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\mssync20.sys



On Tue 11/14/2006 4:07:15 PM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xF8AD0000, 0x0, 0xF8ADE50C, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\mssync20.sys



On Mon 7/10/2006 9:11:39 PM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xF8A70000, 0x0, 0xF8A7250C, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\mssync20.sys




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

17 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Edited by realapp, 02 February 2009 - 06:17 PM.

  • 0

#36
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
edit double post

Edited by happyrock, 02 February 2009 - 07:10 PM.

  • 0

#37
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
funny ....the newest crash is on the 19th of dec...one of the old ones is malware related...so you may want to take a romp thru the malware forum...
run who crashed again...post the report again and then run chkdsk /r...

Running chkdsk on your Windows XP or 2000 system can repair minor Windows problems

There are several different methods that can be used to run chkdsk

Click the Start button then... Run
In the Run window's Open box... type in ... cmd
Click OK and an MS-DOS-style black screen will appear in a new window
Run chkdsk by typing in chkdsk /r press enter
note the single space before the /
a message will appear that says...chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? <y/n>"
Type y (for "yes") and then press ...ENTER...
A message will appear that will say...This volume will be checked the next time the system restarts
Type exit and then press ...enter...

While chkdsk is running, you will see a light blue window with a dark blue band at the top and bottom. Chkdsk will display the specific stage it is checking as well as the percentage of completion of the stage. You cannot do anything else on your computer while chkdsk is running. When chkdsk is finished, it will automatically reboot your computer.
NOTE this can take a long time to complete..it may even appear to hang or get stuck at a certain % for a couple of hours...then complete
it may even back up and go over the same area...this is normal...let it run...there are 5 stages
DO NOT TURN OFF YOUR COMPUTER WHILE RUNNING CHKDSK or you can have severe problems...

Edited by happyrock, 02 February 2009 - 07:12 PM.

  • 0

#38
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
I reinstalled some new antivirus suggested from this site and ran SuperAntispware, etc and it did remove some malware.

As suggested, I reran Whocrashed and here are the results. I will run the chkdisk as suggested. Thanks!



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Tue 2/3/2009 1:20:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xF7A40000, 0x0, 0xF7A40000, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 1/19/2009 3:14:50 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8056E35F, 0xF79066CC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 1/12/2009 2:10:44 AM your computer crashed
This was likely caused by the following module: toside.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xF8A40005, 0xEEC5FCB0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\toside.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Toshiba PCI IDE Controller
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 1/2/2009 4:04:11 AM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xEE470030, 0x0, 0xF8AF2959, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on mssync20.sys





On Fri 1/2/2009 3:25:18 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xF8A50000, 0x0, 0xF8A50000, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Fri 1/2/2009 2:32:30 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xF8AC0000, 0x0, 0xF8AC0000, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Thu 1/1/2009 7:37:19 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81D14C1F, 0xF89FBC2C, 0xF89FB928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 1/1/2009 5:50:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81D2AC1F, 0xF7A43C2C, 0xF7A43928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 12/29/2008 11:40:25 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81D29C1F, 0xF79A8C2C, 0xF79A8928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 12/22/2008 3:42:24 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x81ED4C1F, 0xF81FBC2C, 0xF81FB928)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 9/8/2008 5:02:02 PM your computer crashed
This was likely caused by the following module: ialmdd5.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF09D455, 0xEF1869DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology



On Sat 9/6/2008 6:02:53 PM your computer crashed
This was likely caused by the following module: ialmdd5.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF09D455, 0xEDE2F9DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology



On Sat 9/6/2008 2:13:33 AM your computer crashed
This was likely caused by the following module: ialmdd5.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF09D455, 0xEE1799DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology



On Sun 4/20/2008 2:27:10 PM your computer crashed
This was likely caused by the following module: drvmcdb.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x805809A6, 0xEF868994, 0xEF868690)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on drvmcdb.sys





On Fri 3/9/2007 2:07:20 AM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xEE9C7000, 0x1, 0xF8AE64CD, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on mssync20.sys





On Wed 1/17/2007 8:39:07 PM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xEE0C0030, 0x0, 0xF8AE8959, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on mssync20.sys





On Tue 11/14/2006 4:07:15 PM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xF8AD0000, 0x0, 0xF8ADE50C, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on mssync20.sys





On Mon 7/10/2006 9:11:39 PM your computer crashed
This was likely caused by the following module: mssync20.sys
Bugcheck code: 0x10000050 (0xF8A70000, 0x0, 0xF8A7250C, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on mssync20.sys






--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

18 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#39
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
go back to the malware forum and post a new topic...
tell them I sent you there so they could guide you in running a rootkit detector...
how is your computer running now.....
as for the ntoskrnl.exe error
we may have to do a repair on xp but if we do you will have to reinstall all the patches all over again..so lets hold off on that for now

Edited by happyrock, 03 February 2009 - 09:25 AM.

  • 0

#40
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
Ok, I'll do that and what do you think of this Rundll error? Should I be posting this elsewhere as well? I have not a clue what it is. Thanks for all of your help. I truly appreciate it!

Computer is running better. So far I have not had to shut it down and with the exception of this rundll errror that pops up as soon as the desktop come up, it starts ok as well.

Edited by realapp, 03 February 2009 - 09:18 AM.

  • 0

Advertisements


#41
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
what comes after rundll ...Error loading what

Edited by happyrock, 03 February 2009 - 09:31 AM.

  • 0

#42
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
Error loading c:/Windows/System 32/mnyuuxqo.dll

Also, I forgot to tell you in the last post that I tried running the chkdisk the way you intructed and it didn't do anything at all. When the msdos screen came up it said:

c: documents and settings:

I typed in what you said after that and it did nothing. No blue bars as you said at top or bottom screen, just nothing.
  • 0

#43
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
check the spelling on that error again...be sure your coping it exactly..
try this...
click on my computer...then right click your C drive...then properties...then the tools tab...
then in the error checking section...click on check now...put ticks in both boxes...then start.....
a message will pop up telling you it can't do it now... blah blah blah...and would you like it to run the next time you restart windows....click yes and reboot your computer

Edited by happyrock, 03 February 2009 - 10:17 AM.

  • 0

#44
realapp

realapp

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 338 posts
I did as you instructed and on the reboot it did a chkdisk thing before loading. Also, the error is exactly as I said in previous post. I checked it 3 times to make sure. It just says after that" the specified module could not be found".

I posted in the malware forum and they have instructed me to do a rootkit test. So I am running that on the problem computer now. Thanks.
  • 0

#45
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
mention the mnyuuxqo.dll error...I can't find anything on that at all
hijackthis may be able clear it up what ever is pointing at the missing .dll..
did chkdsk find and fix any problems...

Edited by happyrock, 03 February 2009 - 12:52 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP