It's a Kernal mode error - http://aumha.org/a/stop.php#0x8e
However, as to what causes it, I have no clue without more information. Best way is since you can go into Windows, install the Windows Debugger: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Once installed, you need to put in the symbol path to get it to read the file properly. Click on file, Symbol Path, and past the following line in:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
After that, click on file, and open crash dump. In the window after that, to into the file name section:
C:\Windows\Minidump
Hit enter and it should show the contents of the folder. Double clicking them will cause it to scan the file. When it is done, click on or type:
!analyze -v
Post the log here. To view more than one to see if they are all the same, go to Debug -> Stop Debug, then back to File -> Open Crash Dump.
I am only guessing,could it be memory problem like insufficient amount or faulty chips?
That's the problem, you're only guessing at this point. By analyzing the log, you will get a more direct result and be able to focus on what could be the cause. Yes, this error can commonly be a hardware fault, but that doesn't mean it's the only fault there is. It could be a bad piece of software. Or the fault log might even point directly at what hardware it is.
If you want to randomly swap parts and play "plug and pray", it could get rather costly. Save yourself money, time and trouble. Get a couple logs together and I'd be more than happy to read them (along with the rest of the community) to see what we can get from them.
Thanks,I appreciate your help.The only thing is that I am not at all computer savy and not sure that I would be able to follow your instructions and not mess-up something in the process.
Pawk
319 Posts
0
February 21st, 2008 20:00
However, as to what causes it, I have no clue without more information. Best way is since you can go into Windows, install the Windows Debugger: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Once installed, you need to put in the symbol path to get it to read the file properly. Click on file, Symbol Path, and past the following line in:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
After that, click on file, and open crash dump. In the window after that, to into the file name section:
C:\Windows\Minidump
Hit enter and it should show the contents of the folder. Double clicking them will cause it to scan the file. When it is done, click on or type:
!analyze -v
Post the log here. To view more than one to see if they are all the same, go to Debug -> Stop Debug, then back to File -> Open Crash Dump.
george_c 40
233 Posts
0
February 21st, 2008 21:00
I am only guessing,could it be memory problem like insufficient amount or faulty chips?
Maxlore
34 Posts
0
February 22nd, 2008 08:00
Pawk is right...
Just go through the same and avoid other kind of experimentations...
Pawk
319 Posts
0
February 22nd, 2008 13:00
If you want to randomly swap parts and play "plug and pray", it could get rather costly. Save yourself money, time and trouble. Get a couple logs together and I'd be more than happy to read them (along with the rest of the community) to see what we can get from them.
george_c 40
233 Posts
0
February 22nd, 2008 14:00
Thanks,I appreciate your help.The only thing is that I am not at all computer savy and not sure that I would be able to follow your instructions and not mess-up something in the process.