Blue Screen

  • Thread starter Thread starter GardenStone
  • Start date Start date
G

GardenStone

Hello,

Just found and joined this newsgroup.... Hello all.
Of course there's a specific reason I searched for
an appropriate group.
This is the problem:
Using REGEDIT and export the registry works about one
minut, then I get the well-knowm blue screen, telling:

A problem has detected and windows has been shut down
to precent damage to your computer.
PAGE_FAULT_IN_NONPAGED_AREA

And below:
Technical information:
***STOP: 0x00000050 (0xE1A95000,0x00000000,0x80572A2C,0x00000001)

The same problem occurs when usning the applications
Registry Booster, Regcleaner 4.3. and Advanced Windows
Care. Astounishingly prgrams like Ahsampoo Winoptimizer
3 Platinium and TuneUp Utilities 2006 are running normally
when the clean the registry.
Not only exporting/saving the registry ins't possible,
often scanning for orphaned filesreferences gives the
same blue screen.
But I can export one string from the Reg.

I started in Safe Mode, same problems.

Strange is, that the system.log didn't dump specific info
about the forced shutdown, all though at Properties-Advanced
-startup and recovery the logging is checked.

Checked some dll files that could cause blue screens,
they're all there.

Any good tips here to solve this problem?

I'm running XP Pro, SP2 at a P4, 2,60 Mhz, 1024 MB RAM,
about 20 Gigabyte applications are registered in the reg.
 
This problem may occur if the computer is infected with a variant of the
Sdbot virus.
If you have MS Antispyware removal, run that. If that doesn't cure it, try
an online scan with TrendMicro, or Panda.
 
l> This problem may occur if the computer is infected with a
l> variant of the Sdbot virus.
l> If you have MS Antispyware removal, run that.

That was the first thing I thought of myself. :-)
Unfortunately, it isn't that easy.

All though I've running F-Secure permanently which has
a virus- and adware shield, I've done a deep system check
at the first time the Blue Screem problem appeared.
Nether F-Secure, nor Windows Defender (from Microsoft),
and AdAware Pro didn't find any problem.



 
there could be another explanation, faulty hardware, etc, but it seems
unlikely since it seems to happen only when you are running diagnostic type
programs, which indicates an intrusion.
Maybe an online scan from TrendMicro, Panda, or Edwido, 'though F-Secure
should have caught it, maybe try F-Secure in safe mode.

See if regedit will stay open in safe mode.
If it does, you could see if the infected exe's are there, then try the
manual removal.
 
Back
Top