RE: STOP 0x0000007F (0x00000008, 0x80042000, 0x00000000, 0x00000000) e

[Guest]

Thier is a hotfix for that but its for 0x0000007E Might be the same,its
#900485

 

[Guest]

Hi Andrew,

Thanks for youyr reply. But 7e is for timing issue, I am sure mine is not a
timing issue, I suspect it is a memory issue. At first I thought it is a
software issue, so I reformated and reinstalled Windows, but again I got that
error message. I want to know how I can make sure which hardware is failing.

Regards,
Mehdi.

 

[mikeyhsd]

search Google or MS KB.

use the

0x0000007F

part for searching



(e-mail address removed)



Hi Andrew,

Thanks for youyr reply. But 7e is for timing issue, I am sure mine is not a
timing issue, I suspect it is a memory issue. At first I thought it is a
software issue, so I reformated and reinstalled Windows, but again I got that
error message. I want to know how I can make sure which hardware is failing.

Regards,
Mehdi.

 

[John John]

Well, there is an article about Server 2003 and Windows 2000 with the
exact same error message and they say it needs a hotfix, but no mention
of Windows XP being affected by the problem. For your information the
article is here: http://support.microsoft.com/kb/891722/ I don't
recommend that you try to obtain the fix but the information is there
for you. If you try to get the fix and tell then that you are running
Windows XP they might tell you to take a hike and charge your credit
card for pestering them! Maybe it does affect Windows XP but it could
be that they have received no reports of the error on XP so they haven't
included it in the article.

Other than that you can sift through these:

http://search.microsoft.com/results.aspx?q=STOP+0x0000007F&l=1&mkt=en-US&FORM=QBME1
http://search.microsoft.com/results.aspx?q=0x0000007F+(0x00000008,&l=1&mkt=en-US&FORM=QBME1

John

 

[John John]

Your problem is different. You have an 0x7e error and the original
poster has an 0x7f error, not the same thing. You should not tack your
post on to other posters threads (called highjacking), especially not if
your problem is different. It will only confuse everybody as helpers
will be trying to post answers for two different problems and everyone
will become confused and lost in the ensuing mess. Start a new message
thread with your error message clearly identified in the subject line
and someone will help you. Your chances of obtaining accurate help will
be better if you start a new discussion thread, some of the helpers
reading will see this thread as being looked after already and may
simply skip over your post. If they see a new post and see that you are
all by your lonesome self they will stop to offer help ;-)

John

PS: Look here for possible answers to your problem:
http://search.microsoft.com/results.aspx?q=STOP:+0x0000007E+pci.sys&l=1&mkt=en-US&FORM=QBME1

 

[Ron Martell]

Thier is a hotfix for that but its for 0x0000007E Might be the same,its
#900485

Andrew, please go away. Far, far away where there is no Internet
access so you will no longer be able to pollute these newsgroups with
your inane useless blathering.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Sorry John John I can't read. I thought it was the same thing. I tried all
the items on that link already and no luck. Thanx for the help anyway.