Tech Support > Microsoft Windows > Performance/Maintainence > BSOD 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)
BSOD 0X0000007B (0XF7946528, 0XC0000034, 0X00000000, 0X00000000)
Posted by BSOD on November 21st, 2007


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...&bt nG=Search

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

thanks.


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

Posted by Leonard Grey on November 21st, 2007


STOP 0x7B: INACCESSIBLE_BOOT_DEVICE
http://www.aumha.org/a/stop.php#0x7b

---
Leonard Grey
Errare humanum est

BSOD wrote:

Posted by Leonard Grey on November 21st, 2007


STOP 0x7B: INACCESSIBLE_BOOT_DEVICE
http://www.aumha.org/a/stop.php#0x7b

---
Leonard Grey
Errare humanum est

BSOD wrote:

Posted by BSOD on November 21st, 2007


I did not install any new devices or new hard drives. Also that is an
obvious answer that doesn't help me a bit. I can google too, and I've seen
all there was to see on the MSDN site.

Since this particular BSOD can mean many things, the key here is the second
hex number: 0XF7946528

Anyone? Anything?

Maybe Bill Gates cares to reply?



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


"Leonard Grey" wrote:

Posted by BSOD on November 21st, 2007


I did not install any new devices or new hard drives. Also that is an
obvious answer that doesn't help me a bit. I can google too, and I've seen
all there was to see on the MSDN site.

Since this particular BSOD can mean many things, the key here is the second
hex number: 0XF7946528

Anyone? Anything?

Maybe Bill Gates cares to reply?



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


"Leonard Grey" wrote:

Posted by Gerry on November 21st, 2007


What is the hard drive make and model? Have you tried testing with the
drive manufacturers test utility?

Can you read the drive when installed as a slave drive in another
computer?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

BSOD wrote:


Posted by Gerry on November 21st, 2007


What is the hard drive make and model? Have you tried testing with the
drive manufacturers test utility?

Can you read the drive when installed as a slave drive in another
computer?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

BSOD wrote:


Posted by Jim on November 22nd, 2007



"BSOD" <BSOD@discussions.microsoft.com> wrote in message
news59231F5-7CA9-4647-9D60-0AF784931268@microsoft.com...
it is in non paged pool, the virtual address and the physical address may be
identical.
Jim



Posted by Jim on November 22nd, 2007



"BSOD" <BSOD@discussions.microsoft.com> wrote in message
news59231F5-7CA9-4647-9D60-0AF784931268@microsoft.com...
it is in non paged pool, the virtual address and the physical address may be
identical.
Jim



Posted by Script on November 22nd, 2007


So the relevant question (to me) is, how would one read the instruction at
the address listed?

"Jim" wrote:

Posted by Script on November 22nd, 2007


So the relevant question (to me) is, how would one read the instruction at
the address listed?

"Jim" wrote:

Posted by Jim on November 23rd, 2007



"Script" <Script@discussions.microsoft.com> wrote in message
news:F33A7F43-90F1-4E3E-A278-50A0235A6BB0@microsoft.com...
experience than I have to accomplish this task.

And, it may be that the specific instruction did not cause a problem. Quite
a few processors only report the general area of a problem (i. e. the
address is only close to the problem).

Jim



Posted by Jim on November 23rd, 2007



"Script" <Script@discussions.microsoft.com> wrote in message
news:F33A7F43-90F1-4E3E-A278-50A0235A6BB0@microsoft.com...
experience than I have to accomplish this task.

And, it may be that the specific instruction did not cause a problem. Quite
a few processors only report the general area of a problem (i. e. the
address is only close to the problem).

Jim



Posted by Script on November 23rd, 2007


Thanks for your help, and candor.

"Jim" wrote:

Posted by Script on November 23rd, 2007


Thanks for your help, and candor.

"Jim" wrote:

Posted by BSOD on November 23rd, 2007



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


"Jim" wrote:

Since it crashes at the beginning of the boot process it's very unlikely
that a debugger can be started to see what's going on.

Anyway, I got more info on how the BSOD happened. It went this way: RealVNC
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.

Weird eh?

Anyway this box had Windows XP running on it for the last 3 and a half years
and iit'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.

Thanks.


Posted by BSOD on November 23rd, 2007



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


"Jim" wrote:

Since it crashes at the beginning of the boot process it's very unlikely
that a debugger can be started to see what's going on.

Anyway, I got more info on how the BSOD happened. It went this way: RealVNC
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.

Weird eh?

Anyway this box had Windows XP running on it for the last 3 and a half years
and iit'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.

Thanks.