XP PRO 32bit SP2, AMD FX53, 2 gigs of RAM, Non dual booting

Anyone have any clue why my box died?

Before you say viruses or bad HD, know that my computer is clean and the HD
is in fine shape. Only windows is busted.


Any clue as to what 0XF7946528 means? Seems to be a common problem as seen
in this google:

http://www.google.com/search?hl=en&c...28&btnG=Search

but nobody knows what it means not even ms it seems.

thanks.


--
BSOD Stop: 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)

Have you been through the 7B errors here http://www.aumha.org/a/stop.php?

Have you tried starting in safe mode and looking at Event Viewer?


"BSOD" wrote:

> XP PRO 32bit SP2, AMD FX53, 2 gigs of RAM, Non dual booting
>
> Anyone have any clue why my box died?
>
> Before you say viruses or bad HD, know that my computer is clean and the HD
> is in fine shape. Only windows is busted.
>
>
> Any clue as to what 0XF7946528 means? Seems to be a common problem as seen
> in this google:
>
> http://www.google.com/search?hl=en&c...28&btnG=Search
>
> but nobody knows what it means not even ms it seems.
>
> thanks.
>
>
> --
> BSOD Stop: 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)
>

>XP PRO 32bit SP2, AMD FX53, 2 gigs of RAM, Non dual booting
>
>Anyone have any clue why my box died?
>
>Before you say viruses or bad HD, know that my computer is clean and the HD
>is in fine shape. Only windows is busted.
>
>
>Any clue as to what 0XF7946528 means? Seems to be a common problem as seen
>in this google:
>
>http://www.google.com/search?hl=en&c...28&btnG=Search
>
>but nobody knows what it means not even ms it seems.
>
>thanks.

Well, the following article details what the 0X0000007B portion of the
BSOD means so it's a boot problem for sure:
http://support.microsoft.com/kb/324103

When did this start happening? What motherboard and BIOS do you
currently have? How about the SATA drivers? XP fully patched up to
November?

One thing you might want to try first is to boot off your XP CD to
recovery console and do a FIXBOOT and FIXMBR command at the prompt.
I'm not sure how far along the boot process you're getting, if at all,
before BSOD or if it's right at OS boot. More details.

- Thee Chicago Wolf

"BSOD" <(E-Mail Removed)> wrote in message
news:0828F72C-FFA6-4EBF-AB92-(E-Mail Removed)...
> XP PRO 32bit SP2, AMD FX53, 2 gigs of RAM, Non dual booting
>
> Anyone have any clue why my box died?
>
> Before you say viruses or bad HD, know that my computer is clean and the
> HD
> is in fine shape. Only windows is busted.
>
>
> Any clue as to what 0XF7946528 means? Seems to be a common problem as seen
> in this google:
>
> http://www.google.com/search?hl=en&c...28&btnG=Search
>
> but nobody knows what it means not even ms it seems.
>
> thanks.
>
>
> --
> BSOD Stop: 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)


0XF7946528 is a virtual address in non paged pool. A program (usually a
driver) is malfunctioning.

Jim

May be that something here will give you some direction to pursue:

http://msdn2.microsoft.com/en-gb/library/ms795508.aspx

"BSOD" wrote:

> XP PRO 32bit SP2, AMD FX53, 2 gigs of RAM, Non dual booting
>
> Anyone have any clue why my box died?
>
> Before you say viruses or bad HD, know that my computer is clean and the HD
> is in fine shape. Only windows is busted.
>
>
> Any clue as to what 0XF7946528 means? Seems to be a common problem as seen
> in this google:
>
> http://www.google.com/search?hl=en&c...28&btnG=Search
>
> but nobody knows what it means not even ms it seems.
>
> thanks.
>
>
> --
> BSOD Stop: 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)
>

--
BSOD Stop: 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)


"Thee Chicago Wolf" wrote:

> >XP PRO 32bit SP2, AMD FX53, 2 gigs of RAM, Non dual booting
> >
> >Anyone have any clue why my box died?
> >
> >Before you say viruses or bad HD, know that my computer is clean and the HD
> >is in fine shape. Only windows is busted.
> >
> >
> >Any clue as to what 0XF7946528 means? Seems to be a common problem as seen
> >in this google:
> >
> >http://www.google.com/search?hl=en&c...28&btnG=Search
> >
> >but nobody knows what it means not even ms it seems.
> >
> >thanks.
>
> Well, the following article details what the 0X0000007B portion of the
> BSOD means so it's a boot problem for sure:
> http://support.microsoft.com/kb/324103
>
> When did this start happening? What motherboard and BIOS do you
> currently have? How about the SATA drivers? XP fully patched up to
> November?
>
> One thing you might want to try first is to boot off your XP CD to
> recovery console and do a FIXBOOT and FIXMBR command at the prompt.
> I'm not sure how far along the boot process you're getting, if at all,
> before BSOD or if it's right at OS boot. More details.
>
> - Thee Chicago Wolf
>

I have used recovery console before posting here. Also I have removed the
drive and checked it in another box. The drive is a 160GB Western Digital
with 2 partitions on it running on the secondary IDE bus as master. I have
removed all the other hard drives as well as all of the non essential add-ons.

Here is how it went down: RealVNC Enterprise was installed which seems to
have installed a display adapter called vncmirror.sys under GUID
{4D36E968-E325-11CE-BFC1-08002BE10318} and for some
reason the install hanged. After a hard reboot it it booted with a 800x600 4
bitplane display and vncmirror.sys was showing in device manager as a display
adapter. The vncmirror.sys was disabled and the computer rebooted. Same 4
bitplane display, after which the driver was uninstalled! Windows didn't
boot again.

Anyway this box had Windows XP running on it for the last 3 and a half years
and it's kind of a record.

Knowing this how do I go about fixing the registry? I searched for the sys
file and that driver is no longer on the system.