System Services Exception stop error 0x0000003B

R

RoseW

WinXp Pro 64 on new machine as of Oct 9/08 dual processor and up to date
with patches.
The machine was idle with no software running and I was away from the
machine.When I returned the monitor had this stop error message referencing
0x0000003B
0x00000000C0000005
0xFFFFF80001293CE1
0XFFFFFADFDC04150
0X0000000000000000
Beginning dump of physical memory.

This System services exception list suggested checking into recently
installed software,hardware and disabling the bios memory options such as
caching, shadowing.
I had just installed mouse drivers for A4tech battery free mouse downloaded
from the a4tech.com site which were specific for 64 bit.
Previous to that the event manager listed an error that memory wasn't being
released. I found an UPHive file for Xp 64 and it stopped that error in the
event manager since Oct.28

Machine restarted okay and I uninstalled the mouse software. This required a
restart. The Stop Error screen appeared again.
Restarting again just produced the same stop error screen. I have stopped
using that new machine at this point and expect to take it into the shop
tomorrow.

Searching for this 0x0000003B stop error produced a lot of references to
Servers and Vista but I couldn't find anything specific to Xp Pro 64 bit
Another search brought up the vdtw30.dll (video file) and a possibility with
the Realtek sound files.

Is this sufficient information to present to the original builder of the
machine?

Rose
 
R

RoseW

| Rose
|
| Background information on Stop Error message
| http://msdn.microsoft.com/en-us/library/ms793232.aspx
| Hope this helps.
|
| Gerry
| ~~~~
| FCA
| Stourport, England
| Enquire, plan and execute
| ~~~~~~~~~~~~~~~~~~~

I did make use of that library and many other searches and there were not
definitive lines of attack. In fact, my computer repair person just used a
restore point and he didn't know off hand why or what of the System services
exception message. I had him check out the video configuration since there
was a log file referencing skins not being found in the ATI folder. He did
say XpPro 64 bit was closely related to the server status therefore the few
suggestions to deal with this particular stop error could have been
relevant. He couldn't find anything connected however so its a mystery and
the restore point to before the 2 software installations worked. I conclude
that I'm not going to worry about the warning message in the Event log that
memory wasn't released at shut down since it seems to be connected to a
registry backup. The UPHIVE cleanup for xppro 64 did stop that message.
I stood beside him as he did the restore so now I know that the F button for
safe mode can be pushed from the outset and not wait until the flashing bar
when Windows starts up. I had named specific restore points before I
installed these latest softwares so it was really a no-brainer. I am more
prepared for any future 'surprise' such as this white on blue screen <grin>.
The key word is 'Maintain RESTORE points before any changes! <grin>
Thanks for responding.
Rose



|
| RoseW wrote:
| > WinXp Pro 64 on new machine as of Oct 9/08 dual processor and up to
| > date with patches.
| > The machine was idle with no software running and I was away from the
| > machine.When I returned the monitor had this stop error message
| > referencing 0x0000003B
| > 0x00000000C0000005
| > 0xFFFFF80001293CE1
| > 0XFFFFFADFDC04150
| > 0X0000000000000000
| > Beginning dump of physical memory.
| >
| > This System services exception list suggested checking into recently
| > installed software,hardware and disabling the bios memory options
| > such as caching, shadowing.
| > I had just installed mouse drivers for A4tech battery free mouse
| > downloaded from the a4tech.com site which were specific for 64 bit.
| > Previous to that the event manager listed an error that memory wasn't
| > being released. I found an UPHive file for Xp 64 and it stopped that
| > error in the event manager since Oct.28
| >
| > Machine restarted okay and I uninstalled the mouse software. This
| > required a restart. The Stop Error screen appeared again.
| > Restarting again just produced the same stop error screen. I have
| > stopped using that new machine at this point and expect to take it
| > into the shop tomorrow.
| >
| > Searching for this 0x0000003B stop error produced a lot of references
| > to Servers and Vista but I couldn't find anything specific to Xp Pro
| > 64 bit Another search brought up the vdtw30.dll (video file) and a
| > possibility with the Realtek sound files.
| >
| > Is this sufficient information to present to the original builder of
| > the machine?
| >
| > Rose
|
|
 
G

Gerry

Rose

Glad your problem is sorted.

Computer repair businesses often use different techniques to home
computer users. Many computer problems are hardware related and often by
swapping components the problem can be identified and fixed. A home user
usually does not have the spare components to use.

Your Stop Error report was not a common one and your system is system is
64 bit. These are outside my normal experience. I merely posted
information on where I would start, the Error message.

--



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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top