Ranga,
Sounds like a driver is at fault in your configuration. It maybe a device
driver specific to your hardware. It is possible that the problem is exposed
only in a RAMDisk boot. Try the same steps to prepare an image for a
different device. Try increasing the RAM. Let me know if the problem still
repros
--
Thanks,
- Saad, MS
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ranga" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi all,
>
> Any suggestions for this.
>
> Please help me.
>
> (E-Mail Removed) (Ranga) wrote in message
news:<(E-Mail Removed)>...
> > Hello all,
> >
> > I have a Via C3 Motherboard. For this, I Created a Firmware to boot
> > from a Remote Location.
> >
> > For this, FBA process got completed. After that I created a SDI image
> > and booted it from a Remote Location.
> >
> > After loading, (with the message splashing "Loading RAMDISK Image"),
> > the Login UI did not come up. Instead of that, the following error
> > message came up,
>
> -------------------------------------------------------------------------
> >
> > A problem has been detected and windows has been shut down to
> > prevent
> > damage to your computer
> >
> > A Kernel thread terminated while holding a Mutex.
> >
> > If this is the first time, you've seen this stop error screen,
> > restart
> > your computer. If this screen appears again, follow these steps:
> >
> > Check to make sure, any new hardware or software is properly
> > installed. If this is a new installation, ask your hardware or
> > software Manufacturer for any windows updates you might need.
> >
> > If problems continue, disable or remove any newly installed
> > hardware
> > or software. Disable BIOS Memory option such as caching or
> > shadowing. If
> > you need to use safe mode to remove or disable components,
> > restart your
> > computer, press f8 to select advanced startup options, and then
> > select safe mode.
> >
> > Technical Information:
> >
> > *** STOP: 0x 4000 008A (0x85D7 8860,0x85DB 7448,0x0000
> > 0000,0x0000 0000)
> > -------------------------------------------------------------------
> >
> >
> > The Remote Boot Image just terminated after this.
> >
> > Now, the Ran the Firmware from the IDE based Compact Flash. The
> > firmware works without any problems.
> >
> > I could find the problem only with the Remote boot based solution but
> > not in the Compact Flash based solution.
> >
> > Please help me regarding this.
> >
> > with regards,
> > Ranga.