If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailable..
hi and thanks for your help.
after runniong malwarebytes and not finding any malware, i shut down for the evening. the next morning, i restarted only to end up with a generic host 32 window pop up. but by desktop came up and all looked fine. i clicked on a folder and a word doc appeared, but then everything froze. after some time it was apparent that nothing was going to happen, so i shut down. since then the system has been in a constant cycle of rebooting. i have also made mulitiple attempts to get into any safe mode option, but the computer still reboots. i have learned that there are some viruses that cause this problem, but i have also learned that this could mean the drive has also gone bad. i run xp, sp3, 64bit. what are my options and can i ever get into my hd again to extract data? the o/s i run is an oem, so there is no recovery console or repair available as an option. |
Ads |
#2
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailable..
oh - and i meant to also add that in the safe mode options, i did cancel the
reboot to get the bsod window that indicated the following stop error: 0×0000007E (0xc0000005, ox852dc194, 0xf79ef7B0, 0xF7ef4ac). as for the generic host error: i have gotten this window a few times before, but once i x'ed it out, it never came back - and plus it never caused the problem i am having now (the constant rebooting cycle). so maybe this is 2 different issues happening by chance at the same time. (sorry for the previous misspellings...) |
#3
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailable..
one more note of possibly useful info:
upon start up the PCI device listing shows no bus, device function, vendor/device or class number on the ACPI controller (the last device indicated). also 10 options in the win advanced options menu result in a system reboot - the remaining 2 are the options of either a reboot or return to o/s options. when i choose an option, the screen fills with a list of drivers being loaded and the last one that shows before the system reboots is: mutli(0)disk(0)rdisk(0)partition(1)/WINDOWS/system32/drivers/Mup.sys hope this helps more. |
#4
|
|||
|
|||
Rebooting cycle that is endless and any safe mode isunavailable..
On Feb 8, 5:32*pm, kipg wrote:
one more note of possibly useful info: upon start up the PCI device listing shows no bus, device function, vendor/device or class number on the ACPI controller (the last device indicated). also 10 options in the win advanced options menu result in a system reboot - the remaining 2 are the options of either a reboot or return to o/s options. when i choose an option, the screen fills with a list of drivers being loaded and the last one that shows before the system reboots is: mutli(0)disk(0)rdisk(0)partition(1)/WINDOWS/system32/drivers/Mup.sys hope this helps more. I don't know about 64bit, but in 32bit, when the last thing you see is mup.sys, the next driver is usually the culprit, but you can't always tell what it is (easily). In my 32bit experiences, a hang or reboot on mup.sys is either a USB or NIC driver, so unhook any external USB devices, unplug any NIC cards you added and try again. Start with as few devices as possible. Replace them one at a time rebooting after each until you find the one that makes the system reboot or hang. I'm going with a USB or wireless mouse! |
#5
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailable..
=?Utf-8?B?a2lwZw==?= wrote
in : [problem description SNIPped] If nothing else solves the problem, you can always put the drive in another machine and using that machine's functional OS transfer your data to wherever - first running a suitable set of AV/malware scans on your drive FROM THE BOOTING DRIVE/OS to see what the hell is (or is not) going on with your HD. It could be your MB, a driver problem, or one of dozens of other things. Of course you will either need to use an external enclosure or the "other" computer will have to have a case large enough to put your HD into, or at least enough cable length and space to plug in your drive and put it somewhere stable. It is not necessary to actually INSTALL it inside the machine, just make sure not to knock it off whatever it's on while you're working with it. OR when it's just sitting there. (I wasn't aware there is no recovery/repair in OEM versions. IMO it's still MUCH better to have an OEM disc than a "hidden recovery partition" full of ads and other crap. Oh well. You are better off doing an image of a perfectly set up C partition anyway and forgetting about "restores". Keep all your data on other partitions.) -- The arrows are faster than rodents! - t. |
#6
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailab
thanks j, hoping that it would be that simple, i reviewed my usb devices and there were only two: my keyboard and ta da.... a wireless mouse. but unplugging the mouse did not change anything.... and as for the keyboard, i kinda need that. so maybe it is not the usb devices, but something else... and yes, i have 32bit, not 64. my bad. "Jose" wrote: On Feb 8, 5:32 pm, kipg wrote: one more note of possibly useful info: upon start up the PCI device listing shows no bus, device function, vendor/device or class number on the ACPI controller (the last device indicated). also 10 options in the win advanced options menu result in a system reboot - the remaining 2 are the options of either a reboot or return to o/s options. when i choose an option, the screen fills with a list of drivers being loaded and the last one that shows before the system reboots is: mutli(0)disk(0)rdisk(0)partition(1)/WINDOWS/system32/drivers/Mup.sys hope this helps more. I don't know about 64bit, but in 32bit, when the last thing you see is mup.sys, the next driver is usually the culprit, but you can't always tell what it is (easily). In my 32bit experiences, a hang or reboot on mup.sys is either a USB or NIC driver, so unhook any external USB devices, unplug any NIC cards you added and try again. Start with as few devices as possible. Replace them one at a time rebooting after each until you find the one that makes the system reboot or hang. I'm going with a USB or wireless mouse! . |
#7
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailab
yes my default position was to do a transfer in the event that i could not
access my drive data any other way. but i would like to get my current drive up and running again. i did a diagnostic on my current drive (western digital) and it found no physical errors, so the plot thickens. any other ideas regarding a solution? *** i learned the hard way that an oem o/s has no recovery/repair option. because of this, i would rather delete the crap in a hidden partition, than not have the option of recovery/repair. this whole affair has been frustrating and stupid. thanks for your ideas. |
#8
|
|||
|
|||
Rebooting cycle that is endless and any safe mode is unavailab
=?Utf-8?B?a2lwZw==?= wrote
in : yes my default position was to do a transfer in the event that i could not access my drive data any other way. but i would like to get my current drive up and running again. i did a diagnostic on my current drive (western digital) and it found no physical errors, so the plot thickens. any other ideas regarding a solution? I don't know if this will be of much use, but you could try reinstalling Windows. SUPPOSEDLY Windows will just reinstall the OS parts (in XP, spread all over the damn partition) but leave your data alone - although probably not your settings. In actual practice this may or may not work this way or may end in disaster, so I would definitely make a backup of everything important - but to do so you'd have to do the transfers first. If that's too much hassle (and I would say it is, especially given the low chances of success at the end) you could do the transfer and then reformat and partition the drive and you would probably find it working OK since it checks out OK physically. The problem is somewhere in the OS/programs setup, and it could be just about anything. Jose seems the most knowledgeable person here and if his suggestions didn't help, I don't know if there's much you can do... i learned the hard way that an oem o/s has no recovery/repair option. because of this, i would rather delete the crap in a hidden partition, than not have the option of recovery/repair. this whole affair has been frustrating and stupid. I know what you mean. I have been through computer experiences that I would REALLY like to forget. REALLY. thanks for your ideas. I wish I could be more helpful. -- The arrows are faster than rodents! - t. |
Thread Tools | |
Display Modes | |
|
|