• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows error, lockup, reboot.

bluemax

Diamond Member
I have two systems, a Dell that had an 80GB HDD and a 160GB "data" disk; and a second system I just built. I wanted to use that 160GB disk in my main setup and dump the Dell, so I did the following:

I used SYSPREP to shut down the Dell system and to prepare disk for "transport".

I then used Arcronis TrueImage to clone the SATA hard drives. (I'll worry about the stupid extra Dell partitions later.)

When I returned both hard drives to their respective systems, both give me the same error when starting Windows (the logo comes up, then🙂
msoobe.exe error - unknown exception (0x06d007e) occurred in application at location 0x7c812a5b. [close window]

System is not fully installed. Please run setup again.


🙁

Okay, so on my 160GB drive, I try an experiment - I used my Windows XP original disk and tried to do a repair. It appeared to work, up until the setup portion was complete and it was time to boot for the first time. It just reboots after the first blip of logo - in safe mode too. Good thing I can always duplcate the image from the first hard drive again, I haven't changed it yet.

Which one will be easier to repair, and how should I go about it? I don't have a working computer at home until I ZAP the Dell back to factory settings and wipe the hard drive in the process.


I'd rally rather not have to reinstall my software all over again due to a fresh Winstall. 🙁

Thanks in advance for all your expert advice! 😉
 
Originally posted by: acole1
do a chkdsk

clear the boot sector

google the msoobe.exe error

um. thanks, I suppose. Not really useful tips there, especially since Google didn't find a real solution to this error, which other people have had but with different results.

Man am I glad I left IT.... I've wasted almost a week's evenings on this stupid black box.

I just wiped it and put in Windows from scratch - now I have to find all my fracking discs and reload all my other software too.

Next time, I'm justy gonna' buy a mac. 20+ years of PC must come to an end.
 
Originally posted by: bluemax
Originally posted by: acole1
do a chkdsk

clear the boot sector

google the msoobe.exe error

um. thanks, I suppose. Not really useful tips there, especially since Google didn't find a real solution to this error, which other people have had but with different results.

Man am I glad I left IT.... I've wasted almost a week's evenings on this stupid black box.

I just wiped it and put in Windows from scratch - now I have to find all my fracking discs and reload all my other software too.

Next time, I'm justy gonna' buy a mac. 20+ years of PC must come to an end.

Yes you will be much better off see mac is the purfekt link 😉
 
Cute. 🙂 Funny video!

No, no OS is perfect.

Not every presentation can go off without a hitch. Remember the big game developers' conference in Santa Clara to show off DirectX? *BSOD* All the game developers threw the gift goodies (Gak & frisbees) at all the MS execs, having them dive under their computers for cover. 😀

OTOH, for reasons that pertain to ME, the move to Apple has been considered for a couple years now. With every Windows crash, unrecoverable error and OS reinstall, I want the move even more.

NOONE should have to reinstall the OS just to make it run smooth again!
 
Apparently this issue is caused by the installation of windows media player 11 in most cases.... Link

I have spent the last 2 hours troubleshooting it and I am extremely pissed off 🙂
 
Back
Top