Solved RecEnv.exe Application Error

[Kaktussoft]

you can also put faulty memory in another slot, to prove memory is faulty and not the slot

 

[ConMac]

Even with New RAM - Startup Fails

I swapped out the failed RAM for the Corsair 2 x 4GB (DDR3-1866 PC3-15000). I used Memtest86+ v.4.20 for 2+ hours and 2+ passes, and the new RAM passed with no errors. My system still won't boot into Windows 7 64-bit (dual booting with XP on HD #2). I've tried the System Repair Disk and the System OS DVD, and under System Recovery Options for both, it lists the OS as "(recovered)". When I try to do a Startup Repair, it tells me "Startup Repair could not detect a problem."

Should I assume at this point that I have a Registry issue and use the
Startup Repair Infinite Loop Recovery?

How to Recover from an Infinitely Looping Startup Repair Loop without Reinstalling Windows
Published by Dzomlija
01-22-2011

:sarc: Thanks again.

P.S. XP is booting normally and is stable.

 

[Kaktussoft]

I've tried the System Repair Disk and the System OS DVD, and under System Recovery Options for both, it lists the OS as "(recovered)". that's quite normal, because he has fixed it before. You can rename the description so remove the "recovered" text later. But not important now.

winxp runs fine... nice
It's not an infinite loop!! Startup just thinks it's a good installation with everything intact.

Try to boot into win7 safe mode. Tell me exactly what happens

 

[Kaktussoft]

perform frorm recovery environment->"command prompt"
diskpart
list vol
exit

now you know drive letters

chkdsk/f c:
chkdsk/f d:
chkdsk/f e:
chkdsk/f g:

so chkdsk for all partitions. any errors? repaired?

 

[ConMac]

Thanks again for the input. I'll do as you suggested and report back.

I forgot to mention; when I did the Memtest86+ test of the new sticks I noticed the following on the screen:

"Slot 0 4096 MB PC3-10600 - Corsair CMZ8GX3M2A1866C9 *XMP*
Slot 1 4096 MB PC3-10600 - Corsair CMZ8GX3M2A1866C9 *XMP*"

Also at the top of this screen it listed under settings:

"RAM: 933 MHz (DDR3-1866/CAS:9-10-9-27/Dual Channel)"

Shouldn't that line above, "PC3-10600", have said "PC3-15000" for my 8 GB (2x 4GB) DDR3 SDRAM 1866 (PC3 15000)? Or does it matter?

 

[ConMac]

Still No Luck...

I could not boot into Safe Mode (or Safe Mode with Networking or with Command Prompt). In Advanced Boot Options for: "(recovered)" - in Windows Error Recovery, I chose Startup Repair. The message said that "Startup Repair Cannot Repair Automatically."

I then went into the Recovery Environment, and under System Recovery Options for "Operating System: (recovered) on (D Windows 7" I selected Command Prompt and the following volumes were there:

Vol Label Size Status
0 G: DVD-ROM
1 C: Windows XP NTFS Partition 146GB Healthy
2 E: Windows XP NTFS Partition 785GB Healthy
3 D: Windows 7 NTFS Partition 146GB Healthy
4 F: Windows 7 NTFS Partition 785GB Healthy

I ran chkdsk/f for Volumes 1-4. The results were all the same: "Windows has checked the file system and found no problems." It also listed 0 files in bad sectors for all of them.

When I ran Startup Repair in the Recovery Environment I got the message: "Startup Repair could not detect a problem."

What else is there to test?

 

[Kaktussoft]

Thanks again for the input. I'll do as you suggested and report back.

I forgot to mention; when I did the Memtest86+ test of the new sticks I noticed the following on the screen:

"Slot 0 4096 MB PC3-10600 - Corsair CMZ8GX3M2A1866C9 *XMP*
Slot 1 4096 MB PC3-10600 - Corsair CMZ8GX3M2A1866C9 *XMP*"

Also at the top of this screen it listed under settings:

"RAM: 933 MHz (DDR3-1866/CAS:9-10-9-27/Dual Channel)"

Shouldn't that line above, "PC3-10600", have said "PC3-15000" for my 8 GB (2x 4GB) DDR3 SDRAM 1866 (PC3 15000)? Or does it matter?

Not sure. But memtest86 says it's working fine.

 

[Kaktussoft]

• disks are good
• memory is good
• "startup repair" thinks win7 is good.... but that's not true of course

Please explain what's situatio now? I mean you startup. then you select win7 and press enter. what exactly happens then?

Select win7 and press F8. now select safe mode and press enter. What happens exactly?

 

[ConMac]

When I select Windows 7 I get a screen that says that Windows failed to start with two options: Fix Startup (Recommended) or Start Windows Normally. When I select Fix Startup, it tells me that "Startup Repair Cannot Repair Automatically." When I select Start Windows Normally, it comes back to the Windows failed to start screen.

When I press F8 to enter Safe Mode, it doesn't work. The system attempts to boot (it sounds like more than once), and then it comes back to the screen that says Windows failed to start.

Could the MBR be corrupted?
If yes, should I use "bootrec /fixmbr" and "bootrec /fixboot" from the Windows RE Comand Prompt?

 

[Kaktussoft]

"Startup Repair Cannot Repair Automatically."??
You told before "startup repair" thinks Windows 7 is good.... but that's not true of course ".

but now you say "Startup Repair Cannot Repair Automatically."!!
Anyway if it says so... there are some things you can click there something like "view diagnostic details". What's in there? status 0x0 means success

 

[ConMac]

Error Code 0 x 490

Let me better explain my situation, because I am getting different messages now:

On startup, it fails to boot into Windows 7. I get Windows Error Recovery with 2 options: Launch Startup Repair (recommended) and Start Windows Normally

When I choose Launch Setup Repair, it says it cannot repair this computer automatically. The Problem Details are:

Problem Even Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 21200566
Problem Signatuer 05: AutoFailover
Problem Signature 06: 19
Problem Signature 07: BadPatch
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

I hit Finish, then it shuts down.

Then I boot into the system DVD, and selected Repair your computer, which gives me the System Recovery Options:

I selected Startup Repair, and every test was completed successfully with a 0 x 0, except one, and it said:

Root cause found:
A patch is preventing the system from starting
Repair action: System files integrity check and repair
Result: Failed. Error code = 0 x 490

The odd thing is, when I repeat this test, this same error code appears, but later on it also says:
Root cause found:
Startup repair has tried several times but still cannot determine the cause of the problem

I tried "bootrec /fixmbr" and "bootrec /fixboot" and got "The operation completed successfully messages" for both, but they didn't work.

I ran sfc from the command prompt and got the message: "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

I also tried "bootsect /nt60 SYS /mbr" and got the message: "Successfully updated NTFS filesystem bootcode. Successfully updated disk bootcode."

I also ran"bootrec /scanos" and "bootrec /rebuildbcd" from the command prompt and got the message: "Total identified Windows installations: 0"

Could this be my problem? That even though Windows 7 is listed above as "(recovered)", and you said previously that this not a big deal, that it could just be renamed later; that maybe Windows 7 is just corrupted beyond repair? I'm hoping that's not the case.

I really do appreciate your assistance with this.

 

[Kaktussoft]

sfc cannot be run from recovery environment. At least not that way. You're doing the SFC command to the windows recovery environment itself.

bootsect and bootrec commands are not needed now. bootsector and mbr are fine.

Why did you rebuild bcd?

It still says badpatch now (so it did rebuild succesfully?)

Problem Signature 07: BadPatch

 

[Kaktussoft]

Repair action: System files integrity check and repair
Result: Failed. Error code = 0 x 490

this is actually the saem as an offline SFC

A patch is preventing the system from starting... some patch has to be uninstalled.

In recovery environment (preferable from DVD) you can enter "system restore". Assume the following

12-jan last restore point
10-jan 12:15 another restore point
10-jan 11:59 another restore point

restore restore point 10-jan 12:15, because you did boot successfully afterwards and ceated 12 jan restore point. So go back to restore point prior to last successful boot.

Post results

 

[ConMac]

Restore Points Erased

The restore points I mentioned earlier have now been erased by this issue. I did a system backup two weeks ago using EaseUS Todo backup. I will have to do a reinstall, and then restore the system backup I did two weeks ago - if that's my last option.

Also, why do you think the MBR and bootsector are fine?

I rebuilt the BCD and used the bootsect and bootrec because I saw those as possible solutions to the 0 x 490 error code issue in this Forum.

I came across an option for correcting my inability to boot into Safe Mode from another Windows 7 forum: typing "rename d:\windows\system32\drivers\classpnp,sys classpnp.old" in the Windows 7 RE command prompt. But that didn't work. ( D: is where the Windows 7 partition is.)

Do you have any suggestions regarding fixing my inability to boot into Safe Mode? At least from there I could try clean booting and attempt to identify the specific problem.

Thanks again, cheers!

 

[Kaktussoft]

I came across an option for correcting my inability to boot into Safe Mode from another Windows 7 forum: typing "rename d:\windows\system32\drivers\classpnp,sys classpnp.old" in the Windows 7 RE command prompt=> most people talk about classpnp.sys errors. But that isn't he problem at all!! classpnp.sys is just the last driver loaded as on all machines. After that it freezes... so the problem is AFTER loading drivers.

your system is booting so MBR sees active partition. MBR is just a jump to load and run bootsector of partition flagged "active". That bootsector runs bootmgr and that file rads the bootmenu \boot\bcd

All work fine beacuse you are in windows!!! There is a problem within windows!!

 

[Kaktussoft]

"system backup" 2 weeks ago? How did you made that? Did you backup all partitions?

 

[ConMac]

your system is booting so MBR sees active partition. MBR is just a jump to load and run bootsector of partition flagged "active". That bootsector runs bootmgr and that file rads the bootmenu \boot\bcd

All work fine beacuse you are in windows!!! There is a problem within windows!![/QUOTE]

Let me explain better: I can boot into XP (where I currently am writing this). Windows 7 does not boot. Are you saying that because I can use the Boot Manager to boot into XP, you consider that as booting into Windows 7?

All is not fine because I can't boot into Windows 7, not even Safe Mode. Do you have any suggestions on how to boot into Safe Mode, or is Windows 7 just too corrupted to bother?

 

[ConMac]

System Backup

"system backup" 2 weeks ago? How did you made that? Did you backup all partitions?

I did a system backup using EaseUS Todo Backup Free 4.0 to an external HD. I do not have any system backups using Windows 7 to an external HD. If I have to do a fresh install, and then restore this system image, will this mess up my ability to dual boot? Will my Boot Manager remain as it is now?

 

[Kaktussoft]

please post screenshot of disk management with all fields visible. Bootmenu will be the same or will be easy reapairable.

What partitions did you backup 2 weeks ago? Best thing to do is a restore. Because due to the memory problems the disk is somewhat corrupt!

 

[Kaktussoft]

You can access the win7 partition from within winxp. Please save important documents from that partition prior to doing a partition restore.

Do you have a bootable CD with EaseUS ToDo Backup, so you can restore? If not install EaseUS on winxp and restore from there.