XP Image network access - blue screen

[Jeb]

Hello all,

I am attempting to resolve the situation where our XPe
Image, when installed with PC Anywhere, will crash when it
accesses the network in around 7% of tests.

Our test is to access "My Network Places" and a couple of
hosts in Explorer. The crash happens as soon as you view
the network.

The blue screen has the following information:
STOP 0x00000027 (0xBAAD00A3, 0xF995BAF4, 0xF995B7F4,
0xF00175F4)
Its source is rdbss.sys.

Can anyone assist with either of the following questions?

1. Are we likely to be missing a component(s)? If so,
which, or how do we find out?

2. Has anyone else had problems with this bluescreen, or
PC Anywhere?


Thank you in advance,

Jeb.

 

[Brad Combs]

Jeb,

To rule out the component theory I would download the vampire.slx that Heidi
Linda put on www.xpefiles.com and build an image with it. If it works with
that then you know your missing a component somewhere and you can back track
from there. HTH,

Brad Combs
Imago Technologies

 

[Jeb]

Thanks for the suggestion, I'll give it a shot soon.

Jeb.

 

[Doug Hoeffel]

I have seen the following network-related BSOD's:

DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen w/ Stop Code 0xD1 in tcpip.sys
RDR_FILE_SYSTEM Blue Screen with Stop Code 0x27 in rdbss.sys
Stop Code 0xBE in netbios.sys (ATTEMPTED_WRITE_TO_READONLY_MEMORY)

I don't think this was related to pcAnywhere though. I also use V10.5 with
the V10.5.1 patch. Set the pcAnywhwere service to manual start and see if
the BSOD still occurs.

In my case, I think it was due to adding certain components to my OS image.
Basically, I never saw any of these problems until I added certain
components and hotfixes. Have you recently added components/hotfixes to
your image?

Let me know since I backed out certain components but I haven't been able to
add them back 1 by 1 to see exactly which one causes the problems.

.... Doug

 

[Jeb]

We have only seen the RDR_FILE_SYSTEM BSOD regularly, plus
one IRQL_NOT_LESS_OR_EQUAL (location not specified?).

As for the image, I can't really say whether components
were "added". The image was considered "stable" for some
time until the problem appeared so I really don't know.

No hotfixes have been applied to our tests, and I usually
re-image before another test, so nothing carries over
between tests. The target designer is at SP1, though.

Do you have any records of which components you backed out
to stop these errors? I may find time to test such things -
once I can get back on our test rig

Thanks for your input,

Jeb.

 

[Jeb]

Yes, I did a stop 0x0A, however our images do not use EWF.

Thanks for the list, I'll compare it against our image
soon.

Jeb.