Anybody read this code?
I friend of mine has a home built computer. Lately he has nothing but problems with it. So, he did a reformat/reinstall of XP. Ran good for a couple of days. Then today he reboots and get a blue screen. The text says something about a problem detected, and Windows is shutting down to protect itself. If this is the first time it has occured,try starting Windows normally, if not, then go into safe mode. (But I have forgotten what it said to do in safe mode-sorry). He tried rebooting several times, and this pages shows up at different times on the reboot, but always shows.
At the bottom of the page is this code:
STOP: 0X0000007E 0X0000005 0XF870E9C3 0XF8A3ICOO OXF8A31900
Can anybody read this code, or maybe a link to where it can be deciphered?
Thanks;
Dragstk
At the bottom of the page is this code:
STOP: 0X0000007E 0X0000005 0XF870E9C3 0XF8A3ICOO OXF8A31900
Can anybody read this code, or maybe a link to where it can be deciphered?
Thanks;
Dragstk
0
Comments
See if friend can replicate, this time write down the file name, and tell frined about MemTest86 and have him\her run that also.
This seems to happen more with upgrades than totally clean installs, though-- so is this clean install or an upgrade to get XP starting with aprevious version of Widnows on HD already????
Other than RAM, the 20 pages of google hits discussed it being caused by:
Keyboard drivers, for USB keyboards
mouse drivers, for USB mice
DVD drivers and underlying windows stuff when upgrading
RAM failures were the most prevalent (aka common) thing, any chance a RAM stick worked loose when box was coming back from a LAN party or anything like that???
BAD RAM can cause all kinds of wierd stop errors, so I'm gonna preempt Prime's thunder since I got here first and do the memtest86 chant first.... Run memtest86, run it many times, run it in all tests mode, let it run overnight. No errors by morning, it is not RAM and could be even a bad hub for USB, bad cable to DVD drive, USB device with bad cable, that kind of thing.
Google could not find the exact error with memory address, and the file name it yelled about was not given to you by your friend or got forgotten-- so I am gonna do the "having file name helps a real HUGE lot with 7E stops, too many dang possibilities without it, sorry," thing also. yuo do NOT want to know how many hits I got off of Google, they were against media devices, external hubs, one printer, several USB keyboards, etc....
Sorry, tried.
This is a clean install of XP. I will get a hold of my friend, see what file is the issue. I'll get him a copy of Memtest.
The computer has not been moved, but that doesn't rule out something being loose.
I'll use what you have told me, get more info and report back.
Thanks again;
Dragstk
http://www.winnetmag.com/Article/ArticleID/26804/26804.html related to usbhub.sys error and manifests after adding a new USB device when USB bandwidth consumption exceeds the 100-percent maximum that the USB 2.0 update or XP Service Pack 1 (SP1) allow.
Hope that helps...Good luck.
Danke (oops, thanks, been hanging out on the SuSE newsgroup, have to switch languages again) for getting back at me with more info, but in this case I had trouble even synopsizing them for you.
try this when you get the file name:
stop: +0x0000007E -upgrade +filename
- says exclude from results what follows as one word
+ says I want the first thing AND this in every result you give me
Boolean searching on Google, neato.
+ forces boolean ANDing, - forces an inverse NOR'd exclude, default is an OR'd inclusive result
It seems more info is needed from my friend, as to what is happening. But I did pass along the links you sent, so hopefully they will help.
Thank you for your efforts.
John, I'll try the additions to the file name , tomorrow when I see my friend.
Dragstk