USB problem

Neil wrote:
Hi,

Error is still persisting.

Tried booting with Linux live CD and had no problems, with memory stick

Disabled DEP settings & BSOD changed error message to 0x000000e.
Regarding BIOS, if I disable USB 2.0 then the problems appears to go away.
Can bot with memory stick or insert memory stick while PC is running with no
problems.
Not checked the same with printer yet.

"Paul" wrote:

Neil wrote:
Thanks for all your replies.
Yes the printer does have a card reader, so there could be a connection with
the memory stick.
Tried your last suggestions regarding device manager & SFC with stil no
change, plugging in memory stick caused an uncontrolled shutdown.

Powering up PC with memory stick directly attached startup fails and PC
reboots.
Did notice BSOD flash when startup failed, so changed startup setting to not
restart on errors.
BSOD now gave error details :- atempt made to execute nonexecutable memory.

0x000000FC (0xF79F38E8, 0x07928963, 0xF79F3848, 0x00000001)

Did a quick web search on 0x000000FC and found reference to SP3 & DEP
settings.
Checked for SP3 install, but date was well before problems started.
Chenged DEP setting & still no change.

Motherboard is Asus M2V-MXSE
CPU is AMD 4200+ dual core
Ram is 1GB with 256 mb Nvidia graphics.

Hope this info helps, look forward to fearing from you again soon.

Neil

There is no help on decoding the parameters of 0x000000FC here.
It would have helped, if the routine attempting the access was
identified.

http://aumha.org/a/stop.htm

I found one web page, which recommended changing a BIOS setting
for USB. PDF page 63 (2-21) here shows the options.

http://dlcdnet.asus.com/pub/ASUS/mb/..._m2v-mx_se.zip

(This page had something to do with SP3.)
http://www.icamd.org/windows/dell.html

You could try disabling legacy support. But I don't know what
other settings there would help. Are your USB settings currently
all at the default values, or have some been changed ?

There are web pages, that cover some of the BIOS settings. For
example, the Port64/60 emulation is described here.

http://www.techarp.com/showFreeBOG.a...ng=0&bogno=343

Perhaps someone else recognizes the 0x000000FC symptom ?

Paul


The funny thing is, I have the same Southbridge as you do :-)
The Southbridge is where the motherboard USB ports are handled.
I have a VT8237S on the motherboard I'm typing this on. I've run
a Canon inkjet printer, a couple USB sticks, a webcam, and
there were no USB related issues. Or DEP, or crashing.

Since this isn't your personal machine, I suppose there are limits
are to how far you can go on debugging. If it was me at this
point, and my Linux testing was showing no problems, but WinXP
would not play nice, I might connect my spare drive,
do a clean install of WinXP, and do some testing there.
I would disconnect the original drive, during the installation,
but after the first full reboot is finished, I'd then be
able to connect up the old drive again. Then, try the USB
memory stick first, before any USB printer software.

It could be that the USB printer software has done something.
If the behavior "goes south", after the printer software is
added to the fresh install, that might hint at the problem.
(When I do a fresh install, I disconnect from the net, and
avoid activation. I try to make sure I have all the software
I need for testing, stored on disk. That way, I'm not constantly
re-activating with Microsoft watching.)

Could the DEP thing be malware ? Otherwise, why would the
system be attempting to execute data space, instead of sticking
to memory areas marked as holding code.

http://en.wikipedia.org/wiki/Data_Execution_Prevention

Have you ever looked through the setupapi.log file ? Is there
anything strange recorded in there ? Sometimes, there are
multiple files by that name, as the system may change the name
and start a fresh one, when it gets too big. When a new USB device
is plugged in, you might see a fresh entry at the end of the file.

I'm guessing this is yours ?

http://vip.asus.com/forum/view.aspx?...Language=en-us

Paul

Thanks again.
Changed DEP as there were suggestions regarding service packs causing BSOD's.

CHanged BIOS settings to disable USB 2 And memory sticks work OK.
Completely uninstalled printer drivers and all related software and passed
it back o it's rightfull owner to reinstall printer.
Considering the PC only has printer, webcam or webcam etc attached then
maybe USB 1 should suffice.

Just had a message to say that printer installed OK and memory sticks were
working, so he was happy with that.

"Paul" wrote:

Neil wrote:
Hi,

Error is still persisting.

Tried booting with Linux live CD and had no problems, with memory stick

Disabled DEP settings & BSOD changed error message to 0x000000e.
Regarding BIOS, if I disable USB 2.0 then the problems appears to go away.
Can bot with memory stick or insert memory stick while PC is running with no
problems.
Not checked the same with printer yet.

"Paul" wrote:

Neil wrote:
Thanks for all your replies.
Yes the printer does have a card reader, so there could be a connection with
the memory stick.
Tried your last suggestions regarding device manager & SFC with stil no
change, plugging in memory stick caused an uncontrolled shutdown.

Powering up PC with memory stick directly attached startup fails and PC
reboots.
Did notice BSOD flash when startup failed, so changed startup setting to not
restart on errors.
BSOD now gave error details :- atempt made to execute nonexecutable memory.

0x000000FC (0xF79F38E8, 0x07928963, 0xF79F3848, 0x00000001)

Did a quick web search on 0x000000FC and found reference to SP3 & DEP
settings.
Checked for SP3 install, but date was well before problems started.
Chenged DEP setting & still no change.

Motherboard is Asus M2V-MXSE
CPU is AMD 4200+ dual core
Ram is 1GB with 256 mb Nvidia graphics.

Hope this info helps, look forward to fearing from you again soon.

Neil

There is no help on decoding the parameters of 0x000000FC here.
It would have helped, if the routine attempting the access was
identified.

http://aumha.org/a/stop.htm

I found one web page, which recommended changing a BIOS setting
for USB. PDF page 63 (2-21) here shows the options.

http://dlcdnet.asus.com/pub/ASUS/mb/..._m2v-mx_se.zip

(This page had something to do with SP3.)
http://www.icamd.org/windows/dell.html

You could try disabling legacy support. But I don't know what
other settings there would help. Are your USB settings currently
all at the default values, or have some been changed ?

There are web pages, that cover some of the BIOS settings. For
example, the Port64/60 emulation is described here.

http://www.techarp.com/showFreeBOG.a...ng=0&bogno=343

Perhaps someone else recognizes the 0x000000FC symptom ?

Paul


The funny thing is, I have the same Southbridge as you do :-)
The Southbridge is where the motherboard USB ports are handled.
I have a VT8237S on the motherboard I'm typing this on. I've run
a Canon inkjet printer, a couple USB sticks, a webcam, and
there were no USB related issues. Or DEP, or crashing.

Since this isn't your personal machine, I suppose there are limits
are to how far you can go on debugging. If it was me at this
point, and my Linux testing was showing no problems, but WinXP
would not play nice, I might connect my spare drive,
do a clean install of WinXP, and do some testing there.
I would disconnect the original drive, during the installation,
but after the first full reboot is finished, I'd then be
able to connect up the old drive again. Then, try the USB
memory stick first, before any USB printer software.

It could be that the USB printer software has done something.
If the behavior "goes south", after the printer software is
added to the fresh install, that might hint at the problem.
(When I do a fresh install, I disconnect from the net, and
avoid activation. I try to make sure I have all the software
I need for testing, stored on disk. That way, I'm not constantly
re-activating with Microsoft watching.)

Could the DEP thing be malware ? Otherwise, why would the
system be attempting to execute data space, instead of sticking
to memory areas marked as holding code.

http://en.wikipedia.org/wiki/Data_Execution_Prevention

Have you ever looked through the setupapi.log file ? Is there
anything strange recorded in there ? Sometimes, there are
multiple files by that name, as the system may change the name
and start a fresh one, when it gets too big. When a new USB device
is plugged in, you might see a fresh entry at the end of the file.

I'm guessing this is yours ?

http://vip.asus.com/forum/view.aspx?...Language=en-us

Paul

Thanks again.
Changed DEP as there were suggestions regarding service packs causing BSOD's.

CHanged BIOS settings to disable USB 2 And memory sticks work OK.
Completely uninstalled printer drivers and all related software and passed
it back o it's rightfull owner to reinstall printer.
Considering the PC only has printer, webcam or webcam etc attached then
maybe USB 1 should suffice.

Just had a message to say that printer installed OK and memory sticks were
working, so he was happy with that.

"Paul" wrote:

Neil wrote:
Hi,

Error is still persisting.

Tried booting with Linux live CD and had no problems, with memory stick

Disabled DEP settings & BSOD changed error message to 0x000000e.
Regarding BIOS, if I disable USB 2.0 then the problems appears to go away.
Can bot with memory stick or insert memory stick while PC is running with no
problems.
Not checked the same with printer yet.

"Paul" wrote:

Neil wrote:
Thanks for all your replies.
Yes the printer does have a card reader, so there could be a connection with
the memory stick.
Tried your last suggestions regarding device manager & SFC with stil no
change, plugging in memory stick caused an uncontrolled shutdown.

Powering up PC with memory stick directly attached startup fails and PC
reboots.
Did notice BSOD flash when startup failed, so changed startup setting to not
restart on errors.
BSOD now gave error details :- atempt made to execute nonexecutable memory.

0x000000FC (0xF79F38E8, 0x07928963, 0xF79F3848, 0x00000001)

Did a quick web search on 0x000000FC and found reference to SP3 & DEP
settings.
Checked for SP3 install, but date was well before problems started.
Chenged DEP setting & still no change.

Motherboard is Asus M2V-MXSE
CPU is AMD 4200+ dual core
Ram is 1GB with 256 mb Nvidia graphics.

Hope this info helps, look forward to fearing from you again soon.

Neil

There is no help on decoding the parameters of 0x000000FC here.
It would have helped, if the routine attempting the access was
identified.

http://aumha.org/a/stop.htm

I found one web page, which recommended changing a BIOS setting
for USB. PDF page 63 (2-21) here shows the options.

http://dlcdnet.asus.com/pub/ASUS/mb/..._m2v-mx_se.zip

(This page had something to do with SP3.)
http://www.icamd.org/windows/dell.html

You could try disabling legacy support. But I don't know what
other settings there would help. Are your USB settings currently
all at the default values, or have some been changed ?

There are web pages, that cover some of the BIOS settings. For
example, the Port64/60 emulation is described here.

http://www.techarp.com/showFreeBOG.a...ng=0&bogno=343

Perhaps someone else recognizes the 0x000000FC symptom ?

Paul


The funny thing is, I have the same Southbridge as you do :-)
The Southbridge is where the motherboard USB ports are handled.
I have a VT8237S on the motherboard I'm typing this on. I've run
a Canon inkjet printer, a couple USB sticks, a webcam, and
there were no USB related issues. Or DEP, or crashing.

Since this isn't your personal machine, I suppose there are limits
are to how far you can go on debugging. If it was me at this
point, and my Linux testing was showing no problems, but WinXP
would not play nice, I might connect my spare drive,
do a clean install of WinXP, and do some testing there.
I would disconnect the original drive, during the installation,
but after the first full reboot is finished, I'd then be
able to connect up the old drive again. Then, try the USB
memory stick first, before any USB printer software.

It could be that the USB printer software has done something.
If the behavior "goes south", after the printer software is
added to the fresh install, that might hint at the problem.
(When I do a fresh install, I disconnect from the net, and
avoid activation. I try to make sure I have all the software
I need for testing, stored on disk. That way, I'm not constantly
re-activating with Microsoft watching.)

Could the DEP thing be malware ? Otherwise, why would the
system be attempting to execute data space, instead of sticking
to memory areas marked as holding code.

http://en.wikipedia.org/wiki/Data_Execution_Prevention

Have you ever looked through the setupapi.log file ? Is there
anything strange recorded in there ? Sometimes, there are
multiple files by that name, as the system may change the name
and start a fresh one, when it gets too big. When a new USB device
is plugged in, you might see a fresh entry at the end of the file.

I'm guessing this is yours ?

http://vip.asus.com/forum/view.aspx?...Language=en-us

Paul