Opposite safemode symptom

[spirocore]

Hi
Ive restored a slow xp 'media center edition' machine to what seems to be
normal operation. Several infections were found with malwarebytes and I also ran chkdsk. The machine was also set back to an earlier restore point. The problem is (and was) it still wont boot in to safe mode. Windows seems to start up fine in normal mode now, but I get stop error 0x0000007B in safe mode. Is this a symptom of a problem or did i miss something? (I was trying to avoid a repair install)
Thanks

 

[stduc]

In the absence of more info I suspect a boot sector virus or rootkit. See this article

http://support.microsoft.com/kb/324103

for more info.

Run MalwareByte's Anti-Malware, GMER, RootRepeal and maybe ComboFix and see what happens?

Maybe post in the Virus/Spyware discussion forum for more specific advice?

 

[linney]

Any clues in these?

WinXP Pro won't boot into safe mode
thread779-1020730

Blue Screen 0x0000007E ONLY in Safe Mode
thread779-1581486

 

[goombawaho]

I would say it's more likely related to something starting up that is causing this. I've seen where machines with Norton would NOT start in safe mode but would in normal mode.

Best bet is to turn off startup items (in regular mode) one by one and try a boot into safe mode after each change. You'll get to the bottom of it that way.

Autoruns or Msconfig can be used.

 

[vacunita]

I tend to agree with stduc.
Also could be one of the default drivers Windows need for safe mode is having issues, possibly corrupted.

Have you tried running sfc /scannow from the command prompt, either the recovery console or from Windows normally?




----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Behind the Web, Tips and Tricks for Web Development.

http://behindtheweb.blogspot.com/

 

[goombawaho]

It could be either startup item or malware. I'm going to bet that it's a startup item, because in my experience, malware is more likely to LET you boot in Safe Mode and NOT in regular mode.

$5 pretend bet.

Smart idea to START with the malware detection and then move on to my suggestion IF machine is clean.

I agree exactly with StDuc's advice on determining whether it's a virus. We are anxiously awaiting your results.

 

[BadBigBen]

every BSOD 0x0000007B error that I ever came across, was due to driver issues, e.g. AHCI mode set for SATA drives that lacked the corresponding registry settings, or where just plain missing the AHCI drivers (I know this is not the case as it does boot into NORMAL mode)...

my suggestion, along with all the others, would be to see if it is a SATA drive, firstly then to see if the BIOS setting for the SATA devices is set to AHCI, if so set it to IDE or LEGACY (this will let XP see the SATA drives as IDE drives, thus not needing SATA drivers)... now if the PC in question has only IDE drives, then disregard the these instructions...

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[satrow]

STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE
Usual causes: Hard drive, File system, Boot sequence errors, Device driver, Virus infection (in particular check the MBR) =

http://www.carrona.org/bsodindx.html#0x0000007B

 

[stduc]

It seems logical to me for a virus to prevent starting in safemode in order to protect itself.

I have always found the easiest and most reliable way to fix a system is to remove the boot drive and scan it using another machine. Alternatively boot from a CDROM or USB device that contains antimalware software.

 

[goombawaho]

Bet, bet, bet. Double down. We have two competing theories and it's getting exciting in here.

Let me rephrase the above to reflect what it really says:
STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE usual causes of blue screen: every possible cause. Spin the roulette wheel.

Blue screens can be anything and they are tough to analyze at times.

I want to take one step back and throw this out there in terms of revised order of troubleshooting, just to tell you what I would do. Since hardware always trumps software problems -
1. Memory Test
2. Hard Drive Test
3. Malware Testing (per StDuc's earlier post + add TDSSKiller)
4. Startup item analysis and elimination (per my post)

 

[stduc]

Seconded - good plan there goombawaho

 

[spirocore]

Thanks very much for the suggestions.the machine is operating normally after reconfiguring some things and disabling norton 360 but still, blue screens in safe modes 'w command prompt',etc (vga mode is ok)
It may be a driver problem related to one of the many 'sharing' applications loaded on the system or maybe something Norton has caused.
the few quirks and the overall sluggishness have been corrected. I noticed many more maleware infections when i was able to run mbam from the machine itself (c as opposed to slaving the drive.
Since there's five bucks riding on it, Ill continue with the troubleshooting methods suggested -also want to make sure it isnt virus related.
This tech forum is the best with the most well informed posters. thanks again