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

corrupt drivers causing rebooting loop

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 6 posts
Hi, does anybody know of any XP driver files that can cause this rebooting loop to occur??

The machine reboots just after the logo screen and before the login screen.

Running safe mode, loads of files 'run' down the screen and when it gets to mup.sys the screen goes blank and the reboot begins. I have tried disabling mup.sys using the recovery console, but the reboot starts after the file:- kmxndis.sys, which was the next file, before mup.sys.

Any ideas, please????

Edited by Fenor, 09 April 2007 - 03:22 PM.

  • 0




    motto - Just get-er-done

  • Technician
  • 4,345 posts
Are you using the tiny firewall on your computer? You might read this if you are.


Its still part of the Ndis sys file that is causing your problem.

The NDIS library (Network Driver Interface Specification) is contained in
ndis.sys. It is a collection of routines that applications can invoke to
perform network-related operations. Ndis.sys is an integral part of the
kernel and it must match other kernel components to work properly. Perhaps
the update you installed requires a particular version of NDIS you do not
have, or the update replaced some of the system components used by ndis.sys.

You didn't say which service pack you have installed (if any). The latest
released service pack is 1a. Service pack 2 should be out soon. You could
look at the version number of your ndis.sys (...\system32\drivers) and make
sure it matches ntoskrnl.exe and hal.dll (both in ...\system32). These two
components are used by ndis.sys. I would also highly recommend you check
with Windows Update for possible missing updates. If everything looks good
but it still crashes, you might try running a repair install. Doing that
should give you a matching set of system components; however, in some
instances it could make things worse. Backup any important data before you
attempt a repair.

A BSOD means ndis.sys tried to access memory that was swapped out
to disk. You probably need to set the computer so it does not restart to find what the BSOD says.


  • 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