-
February 15th, 2005, 02:27 AM
#1
usb devices cause crash
hi,
i have just installed service pack 2 on my winxp machines, and whenever an external usb device is plugged in (memory stick, external HDD, camera etc), the machine shows the dreaded blue screen and starts to 'dump physical memory'. does this mean i need to upgrade drivers for the motherboard (which is DFIPM12-Tc/TL)? and how do i locate these drivers on the net not in russian??
thanks for your help
anne
-
February 15th, 2005, 07:42 AM
#2
Intel Mod
Hi Anne,
Up-to-date drivers are a good place to start, although I can't answer for SP2 compatability.
DFI's global english download site is here:
http://www.dfi.com.tw/index_us_noflash.jsp?SITE=US
and PM12-TC & TL are listed in the Model dropdown, to source Via 4-in-1 pack and USB2.0 driver.
Good luck, post back if you have any further trouble.
-
February 17th, 2005, 12:43 AM
#3
dear platypus,
thanks for that. i have installed the chipset drivers from there. no change. uninstalled the USB hubs and controllers, and installed the USB drivers from the dfi site as you suggested, no change. then uninstalled them again and let windows detect them, no change.
are we looking here at a dead end. will i have to take sp2 off these machines for the usb to work, or are there other avenues??
-
February 17th, 2005, 07:59 AM
#4
Intel Mod
Well Anne, we mightn't really be at a dead end, but my limited experience fault-finding XP could mean someone else may have to help you more.
Just to double check, is this correct, the USB worked OK on these systems, then immediately on installation of SP2, all began to blue screen?
In this instance, since the common factor seems likely to be the DFI board, it could well be a hardware incompatability. If so reverting back from SP2 is a work-around, but if you need SP2, doesn't help a lot...
One thing I notice is that the most recent BIOS for this board is quite old (2 years old in fact), and may be immature in some aspects required by the updates in SP2. However, if the BIOS in your systems is even older than Feb 2003, it could still be worth trying an update to the later BIOS. I would expect it would be best to uninstall SP2 before doing such an update, then install SP2 again. Perhaps other members may have run into such a situation before.
Also, do you have a record of any error messages given at the blue screen? This can help a lot in identifying the cause of problems.
-
February 18th, 2005, 10:14 AM
#5
my PCs now work - but i fear it may be precarious.
i think you are right about the immature BIOS, but i did upgrade to a 3.3.03 one that i found.
also, the machines have symantec ghost console client on them, and there is a problem acknowledged in the symantec knowledge base with usb drivers on machines with ghost 8x console client on them, and a fix that i have used.
a certain sequence of BIOS upgrade, new BIOSchipset drivers, updated motherboard USB drivers, uninstall all USB listings from devmgt, do the symantec fix, turn off and on again after a few seconds gives us a working system when windows finds them again.
i'm over it, hopefully we won't hear of it again - rolling back sp2 and doing a new image will take a bit of time if it has to happen.
thanks for your assistance, fingers crossed.........
-
February 18th, 2005, 11:15 PM
#6
Registered User
Originally Posted by anne
the machines have symantec ghost console client on them, and there is a problem acknowledged in the symantec knowledge base with usb drivers on machines with ghost 8x console client on them, and a fix that i have used.
Where did you get that info from symantec and is there a patch. I have the same problem at work when anyone tries to use a USB device like a memory stick or digital camera. It has to be plugged in before the computer boots otherwise BSOD here we come.
I found these but no answers.
http://www.techsupportforum.com/comp...c/22413-1.html
http://www.pcbanter.net/archive/inde...en-XP-SP2.html
Last edited by BOB IROC; February 18th, 2005 at 11:38 PM.
-
February 19th, 2005, 05:37 PM
#7
Check out this old thread,
http://forums.windrivers.com/showthread.php?t=50713
in my post, I had trouble with the Ghost client too, but surely your not using the old ghost 6.5 are you? Is so grab a demo of 8.0 and see if you have the same trouble.
-
February 19th, 2005, 07:40 PM
#8
Registered User
Originally Posted by GHSTECH
No I am using the new ghost 8.0 Client and ghost 8.0 Enterprise.
-
February 20th, 2005, 05:30 PM
#9
bob,
sorry for the delay - i wanted to test the fix thoroughly. because i needed to update BIOS and drivers etc, i can't vouch for how much of my solution is to do with the ghost issue, but if you google ghmon.sys you will find that many people are dealing with it, and several give the link to the symantec knowledge base entry, which is
http://service1.symantec.com/SUPPORT/ghost.nsf/
d87bb6ce0bde286d88256d6a00452701/46596fbcc1df097c80256ed100392df7?
OpenDocument&src=bar_sch_nam
one discussionwhich you'll find through google notes (which symantec doesn't) that you need to have rebooted and logged in again to an account for the fix to work.........
interested to follow your progress
anne
-
February 21st, 2005, 12:05 PM
#10
Registered User
Thanks
Thanks Anne I will try that. I have googled my fingers to death and found lots of posts about the problem, but nothing with any ideas on how to fix it without removing the ghost client.
-
February 21st, 2005, 04:32 PM
#11
dear bob,
sorry to hear that. i included the link to the symantec knowledge base so you could go straight to the fix, which is easy when you get to it....basically drilling through the symantec enterprise tech support, you can go to document id 2004071411243425, or browse the knowledge base for ghmon.sys which is all you need as it is the little modified file that will do the trick.....
the instructions in the knowledge base doc are as follows:
Computer reboots after attaching a USB flash drive
Situation: When you attach, or plug-in, a USB flash drive to a computer that has the Ghost Client installed, the computer reboots. You may also see a blue screen error message that states "Stop 0x00000035 NO_MORE_IRP_STACK_LOCATIONS."
Solution: This problem is caused by a flaw in the GhMon.sys file. A new version of the file is available, and can be downloaded by clicking the following attachment.
To replace the file on your computer
1. Rename the original GhMon.sys file in the \WINDOWS\system32\drivers folder to GhMon.old.
2. Copy the new version of the file to the same folder.
3. Create an image of the model computer with the GhMon.sys file included, then apply the new image to other computers.
so, it's straightforward, but i do agree with you that symantec have very much buried it....good luck
anne
-
February 22nd, 2005, 08:18 AM
#12
Registered User
So far so Good. I have tried the fix on a few machines and all is well. I wonder if I could just push this file out using Ghost Console. Hmmmm. That would be cool because some machines I do not want to clone if I don't have too and I really don't want to go do them manually. I will have to try that.
Similar Threads
-
By Chimaera_Trev in forum Windows XP
Replies: 4
Last Post: October 9th, 2007, 10:31 PM
-
By Chimaera_Trev in forum USB/Firewire
Replies: 5
Last Post: March 13th, 2006, 12:05 PM
-
By vespo in forum USB/Firewire
Replies: 0
Last Post: January 13th, 2005, 02:07 PM
-
By jarvismcnikid in forum USB/Firewire
Replies: 5
Last Post: October 10th, 2004, 01:04 AM
-
By crazyzoop84 in forum USB/Firewire
Replies: 12
Last Post: April 15th, 2004, 06:09 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks