System crashes

Archived from groups: microsoft.public.windowsxp.general (More info?)

I have a new (self built) pc, which has so far been a long and complex
project. Having finally got a clean start using windows xp home, I started
to load software.

All went well until installing the online game, World of Warcraft. The
install went as normal, but when downloading the patches, the pc would crash
after a few minutes. On rebooting the message returned from microsoft when
using the error reporting tool, was that there was an unknown driver device
problem. I then went to the web site for each hardware vendor and downloaded
the latest driver.

Here things have gone from bad to worse. On booting the pc in normal mode I
have a choice of doing two things, nothing or something. Do something
immediately crashes the pc. Do nothing and the pc will crash at some point
in the next couple of minutes.

After reading a response to a similar problem, I've turned off the automatic
reboot and can now see the blue error message screen.
*** Stop: 0x000000FC (0xB83C48C4, 0x39E3E163, 0xB83C4800, 0x00000001)
which is apparently an attempt to execute a non-executable memory.

I've looked up this message, which says:
This problem occurs if all the following conditions are true:
• The system includes a legacy hardware DVD decoder that requires the
Mpegport.sys driver.
• You installed the 32-bit version of Windows XP SP2 on a computer that
supports hardware-enforced data execution prevention (DEP).

The solution includes disabling the Mpegport.sys driver, however, there is
no such driver on the machine.

Any other ideas?

Archived from groups: microsoft.public.windowsxp.general (More info?)

Thanks for your reply.

Taking things one at a time.

The built was a long and complex project because, if I knew as much as I
thought I knew, I'd realise I don't know as much as I think I know.

Couldn't get windows to load properly, which on getting someone else to do
it, turned out to be driver issues (two) around SATA drives in a striping
raid, or so I am told.

Specs:
Abit Fatal1ty AN8-SLi
AMD FX-55
BFG 7800 GTX
1 gb Corsair expert (2 x 512mb) twin
Antec Neo PSU
2 x 74gb WD SATA Raptor (striping raid)
Samsung 913N LCD Monitor
NEC DV 5800A
Thermaltake Tsunami Dream Case

The WOW issue may be a red herring. Thinking about it, patching from the
blizzard server was the first action, other than loading software. Reading
the WOW troubleshooting section, they point to an incompatible driver when
the patching continually fails and/or the pc crashes. Any action will now
immediately crash the pc.

>1. Test the RAM with Memtest86+ from www.memtest.org.

- can this be done in safe mode, this is the only way I can get the pc to
stay operational?
>
> 2. Make sure all your hardware is healthy and that you have the latest
> drivers for everything - chipset, audio, video, etc. If things worked
> well with drivers and then you updated and stuff failed, roll back to
> the drivers that worked. Only get drivers from the device mftr.'s
> website - never from Windows Update.

- hardware all was all ok initially. yes, I updated drivers from the
manufacturers sites. can you perform rollback from safe mode?
>
> 3. Make sure your power supply is adequate for the hardware you've got
> in your machine.

- I believe its ok, 480watt
>
> 4. Make sure there is proper airflow in the case.

- same problem even with case side off. however, main case fans linked to
a regulator via PSU and haven't seen them running yet. CPU fan goes like
buggery.
>
> 5. Make sure you didn't use old ribbon cables.

- all new.
>
> 6. Make sure your system requirements meet WOW's.

- Yes, this machine is an upgrade from my current pc, which runs WOW fine.






"Malke" wrote:

> William wrote:
>
> > I have a new (self built) pc, which has so far been a long and complex
> > project. Having finally got a clean start using windows xp home, I
> > started to load software.
> >
> > All went well until installing the online game, World of Warcraft.
> > The install went as normal, but when downloading the patches, the pc
> > would crash
> > after a few minutes. On rebooting the message returned from microsoft
> > when using the error reporting tool, was that there was an unknown
> > driver device
> > problem. I then went to the web site for each hardware vendor and
> > downloaded the latest driver.
> >
> > Here things have gone from bad to worse. On booting the pc in normal
> > mode I
> > have a choice of doing two things, nothing or something. Do something
> > immediately crashes the pc. Do nothing and the pc will crash at some
> > point in the next couple of minutes.
> >
> > After reading a response to a similar problem, I've turned off the
> > automatic reboot and can now see the blue error message screen.
> > *** Stop: 0x000000FC (0xB83C48C4, 0x39E3E163, 0xB83C4800, 0x00000001)
> > which is apparently an attempt to execute a non-executable memory.
> >
> > I've looked up this message, which says:
> > This problem occurs if all the following conditions are true:
> > • The system includes a legacy hardware DVD decoder that requires the
> > Mpegport.sys driver.
> > • You installed the 32-bit version of Windows XP SP2 on a computer
> > that supports hardware-enforced data execution prevention (DEP).
> >
> > The solution includes disabling the Mpegport.sys driver, however,
> > there is no such driver on the machine.
> >
>
> Since we don't know anything about the hardware you used or why building
> the computer was a "long and complex project" (usually building a
> computer takes just a few hours) it is hard to give you specifics. When
> WOW first came out, it required disabling basically everything except
> crucial system processes. It has since been patched. I can't remember
> if you need to patch it yourself or if the game gets automatically
> patched when you connect to Blizzard's servers. Always make sure any
> game you are playing is patched to the current level. That said, test
> these things:
>
> 1. Test the RAM with Memtest86+ from www.memtest.org.
>
> 2. Make sure all your hardware is healthy and that you have the latest
> drivers for everything - chipset, audio, video, etc. If things worked
> well with drivers and then you updated and stuff failed, roll back to
> the drivers that worked. Only get drivers from the device mftr.'s
> website - never from Windows Update.
>
> 3. Make sure your power supply is adequate for the hardware you've got
> in your machine.
>
> 4. Make sure there is proper airflow in the case.
>
> 5. Make sure you didn't use old ribbon cables.
>
> 6. Make sure your system requirements meet WOW's.
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>