Hi,
appears to have an XP pro issue with one of our networked workstations.
Not sure if this is a hardware issue or a virus.
I am receiving:
Error code 1000008e, parameter1 c0000005, parameter2 89dee107, parameter3 a7dbd8dc, parameter4 00000000.
And is causing the PC to reboot itself
Virus software has been updated and didn't detect any issues.
Ran Memory and disk checks still detecting no issues.
Does anyone know how we can decipher this error code?
Winbdg tool is this able to help? no expert with this though.
Cheers
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_
(Click to consult the online MSDN article.)
A kernel mode program generated an exception which the error handler didnt catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).
from auhma.org
I would check into the drivers try running in safe mode see if the problem still occurs if not then you can narrow it down some.
If you get Dumps, then the Windows Debugger is usually adequate to read the crash dumps...Takes a little practice though....
WinDbg
http://www.microsoft.com/w
Use the Microsoft Symbol Server to obtain debug symbol files
http://support.microsoft.c
(so you dont need the full symbol packages for each OS, and SP....)
Some of the most basic commands....
!process
!thread
lmnt
!analyze -v
kb
Should be enough to get you started....Use the built in help feature of WinDbg, its a great resource...
Or, a more automated tool......
The Offline Crash Diagnostic tool for Windows XP is available
http://support.microsoft.c
Business Accounts
Answer for Membership
by: dmwynnePosted on 2009-03-08 at 19:41:54ID: 23832734
What are you running for antivirus? Are there any updates for it?
Run sfc /scannow to check system files.
Anything more detailed in the event logs as to what exactly is causing it.