Recently I've been getting frequent "STOP 0x0000008E (0xC0000005, 0x8054A51A, ... , 0x000000000)" errors. The code in the "..." differs from each time, but the rest of it remains the same.
These first appeared when I was 'Counter-Strike' a few months back, but only ever happens when I play that game, so I stopped. I was error free for a few months, until a few days back. I was playing a different game and this error message caught me by suprise. Ever since then I have been getting these messages regardless of whether I'm playing games, or just browsing site/watching movies. The time of the crash would differ from hours to windows just starting up.
I downloaded and ran "rustbfix.exe" and nothing was found.
I downloaded memtest86 BUT I don't have a floppy disk drive to run it with :S. Is there anyway I can run this without using a floppy?
Hi everybody, I'm experiencing a "STOP: 0x0000007E (0xC0000005 etc. problem. My system was new in April (running Vista Premium Home Edition) and has operated pretty well..........till yesterday. I was playing music from the computer, went outside to talk with a friend, came back in and the system was rebooting. And that's all it has done since then.
I can't boot into safe mode, nor can I boot from the Vista cd...any suggestions? I have a nagging fear that the drive with the operating system on it may have filled. Could that cause this sort of problem? Please, any assistance would be appreciated.
If you have more than 1 stick of RAM, you could try taking out a stick at a time and starting up your system.
As you can see a few posts back I had this bluescreen problem too.
I fixed it by deciding to randomly remove 1 of the 2 sticks of RAM I had and I haven't had this problem since, so in my case it was my RAM issue.
Yours might be different, but it is worth a try.
I also got a system stop, but it was no 8e code:
0x000000f4(0x00000003,0x896b1d84,0x805di3b6)
After that, my VGA driver was gone and I did re-install it.
Sofar it is running again for an hour, but I am uncertain if this was an incidental stop or a permanent problem.
I have an asus en8600gts graphics card, working on a Geforce 8600gts driver.
My monitor is a brandnew syncmaster206bw.
Can it be caused by a rootkit attack on my graphic card?
Hi I have a BIG problem that is URGENT basically I have followed your instructions troll except for the bit when you need to boot it from a CD. The problem is on a laptop with no floppy or CD drive. PLEASE HELP! how can I boot it without a cd drive can I do it on a USB Memory stick? this has been bugging me the whole day have spent soo much time on it I would be so appreciative. Thanks
greetings i also have a problem with my pc.. i tried memtest.. i tried the rootkit.. still i cant find the solution to my problem.. here's the code
0x0000008e (0xc0000005, 0x816b3079,0xf58e6b74,0x00000000)
i cant find it on the web.. can anyone please help me
I'm very glad I found this site and read the original post by troll. Thanks to icrontic and troll for nice work. I joined today to share my fix for the BSOD. The 0x0000008E was most prevalent with a mix of others as well. One of the other messages had a reference to something for AOHELL. I went into device manager and it was indeed flagged so I removed it, but still no luck and the dreaded BSOD messages kept coming. I was having non-stop BSOD messages and even could not always boot in safe mode. I followed the advice of troll and found that my pc had good memory, no virus, and I still was getting the BSOD. I run avg, avg anti-rootkit, adware, spybot, threatfire, etc., and did use spyware doctor too. I first removed spyware doctor which was problematic on my machine. Still I got BSOD messages. I went to Dell and MS websites followed all of the procedures and nothing. I checked all of my drivers with a download from Dell and all was found to be fine. So I decided to go into msconfig from the run menu and then the startup tab. I unchecked both ctfmon and hkcmd. No more BSOD on restarts and it has been a week now with only one BSOD since. This may not be the fix for everyone, but it may help a few. The right thing to do would have been to only uncheck one at a time, but my patience was thin and I know both were not required. Good luck to all. As a new member I hope my first post is useful.
Glad you found my post useful, and good to hear that you got your problem fixed...
For others reading this thread, there are MANY MANY things that can cause the 0x8E BSOD as you can see by following my problem he didn't have the root kit or virus that I found, for him it was ctfmon & khcmd...
I've never seen "khcmd", hkcmd if it's possibly a typo is used for intel onboard graphics.
The only link I've found for khcmd is here http://www.xunt.org/f/khcmd.exe.html and they says it's a virus... and that would possibly explain your bluescreen.
Thanks for posting your experience and fix for what was causing your BSOD. :thumbup
I am having big problems with my laptop, I beg you ...
This blue screen comes up, and it restarts itself. Says that maybe BIOS should be updated, or you have excessive memory usage.
Through Safe Mode I cleaned my disks, and now there is more than half free space on my laptop, but still problem does occur. I turned off BIOS driver, but ... no effect ..
It's gettin worse, now when I start Windows, it says that I have to activate Windows, and while I am waiting for my Windows to be activated, RESTART process again ..
so now I can't use Windows normally, only Safe Mode without Networking ..
please ...
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited December 2007
kzvip, does the problem give you the error code 0xC0000005~ ?
A blue screen with STOP: 0x0000008E is a "bugcheck" code indicating that Windows detected a fatal error and cannot continue. There are numerous reasons for this condition but usually boils down to a failing piece of hardware, a misbehaving device driver, or malware.
Without any more information, you should try to test your RAM with Memtest86 from http://www.memtest86.com/
Download and create a bootable CD from a reliable computer and test your laptop for a few hours. As frustrating as this may seem, this is about the same as posting "my car won't start" in a forum and expecting a magic answer.
Start with Memtest and the folks around here will be sure to help.
I am getting a random BSOD 0x8E and I have posted my problem on another thread, however, perhaps it would be best placed here. This is what I have done so far:
Scanned with trend micro, bitdefender, avast, spybot s&d, plus more and all have come up empty for viruses.
Second, I unticked hksmd.exe in msconfig, and am thinking this is the problem as per what I have read.
Also, I ran memtest for 4 hours and there were no memory errors found.
I would like to follow troll's directions to find the possible rustock rootkit problem, but I don't have XP, I am running Vista.
Gateway support told me I have hexdoor and they can't help me, so I don't know how I can have hexdoor and no scanner will find it. I tried finding hexdoor and other malware by using a M$ mallware removal tool and also a rootkit scanner, plus all anti-virus scanner mentioned above, all coming up with nothing.
So, what else could I do to see why I am getting the BSOD for0x8E? Thanks in advance.<!-- / message -->
What you need to do is load the crashdump into the debugger and see what device driver is causing the problem. If you analyze enough of these and they are in the same driver, you've found the problem If you get random crashes all over the place, it will be a bit harder to figure out.
You need to make sure Vista is configured to generate the minidumps. I don't have Vista so someone else can chime in. If you look in the folder and they are there, you've got quite a bit to play with already.
That's about as simple as I can make it. Good luck.
I am a bit lost with this program you suggessted. I am opening the .dmp files with the program. Here is what I am getting for all the files. I am not sure if this output is what you were after for me to discover. Let me know.
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini122807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
Debug session time: Fri Dec 28 08:48:49.056 2007 (GMT-5)
System Uptime: 0 days 0:05:42.681
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 820818a3, acdff7ac, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : win32k.sys ( win32k+111919 )
Followup: MachineOwner
If they are all pointing to win32k.sys, I'd suspect a graphics issue since this is the kernel mode driver for the Windows GDI. One thing that you could do, as painful as it is, is to uninstall the graphics driver and let Vista use a default driver to see if it goes away.
You mean to uninstall the display adapter driver or video card driver, right?
If I do, What will happen? Will I get horrible resolution? I updated my display adapter driver the other day to the latest version, not sure if that is helping. Knock on wood, I haven't had the BSOD today.
Try updating your graphics card drivers. Probably an ATI, Intel, or Nvidia right? Make sure you are running the latest from the manufacturer. Without all of the debugging symbols loaded, it is hard to tell. What is happening is that it is blowing up on a memory operation 'REPNE SCAS'.
I have Intel and I just installed the new driver yesterday and am still getting the crashes.
To be exact, I have Mobile Intel 965 Express Chipset Family
I just noticed that I can't even rollback my driver to the previous version.
I just crashed again so I am at a loss. Seems to be happening while I am accessing IE7 through roboform, but I could have sworn I crashed while navigating my Yahoo! email account a few times too. I am pretty certain I get crashes only when online browsing or accessing pages.
I ran many virus scanners, anti-rootkit scans, all that stuff and no virus or rootkit malware.
I let memtest run for 4 hours and no error.
I think the driver is the issue, but don't know where to go from here. I guess just do what you say and uninstall my driver and have vista run with the default. This is just a big headache. Any more advice would be appreciated.
More ram won't fix the issue. Try running the Vista default graphics driver only and see if that gets you anywhere. Beyond that it is going to be tough to debug. If you are running more than one virus scanner at the same time you can run into this type of trouble as well. Ultimately, you will need to uninstall anything that installs a device driver, one at a time, until the issue goes away to narrow it down.
It will (try to) record what was going on when your computer crashed and save it to a text file. By studying the file you'll at least get a list of likely suspects as to what caused the crash.
From Microsoft:
The file created should appear in the root of the drive where Windows is installed. As for being "easy to read and understand", it may be, but it might just look like gibberish unless you know what you're looking for. You can attach a copy of the dump file here and we'll have a look.
You could also try right-clicking My Computer, then go to Properties>>Advanced>>Startup and Recovery Settings, then uncheck Automatically Restart.
It will produce a BSOD with an error code. Let us know what it is and we'll try and help.
I have this problem and have followed your advice. I have some dump files from when I get the STOP: 0x0000008E error. However they are .dmp files and are complete gibberish in notepad & wordpad. I'd really like to post my dump file to see if you guys see anything in there but I don't know how at this point. Please help. These errors are killing me & its a new computer!
I have this problem and have followed your advice. I have some dump files from when I get the STOP: 0x0000008E error. However they are .dmp files and are complete gibberish in notepad & wordpad. I'd really like to post my dump file to see if you guys see anything in there but I don't know how at this point. Please help. These errors are killing me & its a new computer!
Comments
Recently I've been getting frequent "STOP 0x0000008E (0xC0000005, 0x8054A51A, ... , 0x000000000)" errors. The code in the "..." differs from each time, but the rest of it remains the same.
These first appeared when I was 'Counter-Strike' a few months back, but only ever happens when I play that game, so I stopped. I was error free for a few months, until a few days back. I was playing a different game and this error message caught me by suprise. Ever since then I have been getting these messages regardless of whether I'm playing games, or just browsing site/watching movies. The time of the crash would differ from hours to windows just starting up.
I downloaded and ran "rustbfix.exe" and nothing was found.
I downloaded memtest86 BUT I don't have a floppy disk drive to run it with :S. Is there anyway I can run this without using a floppy?
Thanks ~ saphyre
http://www.memtest86.com/
I can't boot into safe mode, nor can I boot from the Vista cd...any suggestions? I have a nagging fear that the drive with the operating system on it may have filled. Could that cause this sort of problem? Please, any assistance would be appreciated.
As you can see a few posts back I had this bluescreen problem too.
I fixed it by deciding to randomly remove 1 of the 2 sticks of RAM I had and I haven't had this problem since, so in my case it was my RAM issue.
Yours might be different, but it is worth a try.
0x000000f4(0x00000003,0x896b1d84,0x805di3b6)
After that, my VGA driver was gone and I did re-install it.
Sofar it is running again for an hour, but I am uncertain if this was an incidental stop or a permanent problem.
I have an asus en8600gts graphics card, working on a Geforce 8600gts driver.
My monitor is a brandnew syncmaster206bw.
Can it be caused by a rootkit attack on my graphic card?
0x0000008e (0xc0000005, 0x816b3079,0xf58e6b74,0x00000000)
i cant find it on the web.. can anyone please help me
:bigggrin:
im going out of my mind trying to fix this thing. =(
this is what my blue screen of death says...
0x0000008E (0xC0000005, 0x802C8C5F, 0xBADOFA1C, 0x00000000)
i really need help with this one.
Glad you found my post useful, and good to hear that you got your problem fixed...
For others reading this thread, there are MANY MANY things that can cause the 0x8E BSOD as you can see by following my problem he didn't have the root kit or virus that I found, for him it was ctfmon & khcmd...
I've never seen "khcmd", hkcmd if it's possibly a typo is used for intel onboard graphics.
The only link I've found for khcmd is here http://www.xunt.org/f/khcmd.exe.html and they says it's a virus... and that would possibly explain your bluescreen.
Thanks for posting your experience and fix for what was causing your BSOD. :thumbup
I am having big problems with my laptop, I beg you ...
This blue screen comes up, and it restarts itself. Says that maybe BIOS should be updated, or you have excessive memory usage.
Through Safe Mode I cleaned my disks, and now there is more than half free space on my laptop, but still problem does occur. I turned off BIOS driver, but ... no effect ..
It's gettin worse, now when I start Windows, it says that I have to activate Windows, and while I am waiting for my Windows to be activated,
RESTART process again ..
so now I can't use Windows normally, only Safe Mode without Networking ..
please ...
no,
0x0000008E
A blue screen with STOP: 0x0000008E is a "bugcheck" code indicating that Windows detected a fatal error and cannot continue. There are numerous reasons for this condition but usually boils down to a failing piece of hardware, a misbehaving device driver, or malware.
Without any more information, you should try to test your RAM with Memtest86 from http://www.memtest86.com/
Download and create a bootable CD from a reliable computer and test your laptop for a few hours. As frustrating as this may seem, this is about the same as posting "my car won't start" in a forum and expecting a magic answer.
Start with Memtest and the folks around here will be sure to help.
Scanned with trend micro, bitdefender, avast, spybot s&d, plus more and all have come up empty for viruses.
Second, I unticked hksmd.exe in msconfig, and am thinking this is the problem as per what I have read.
Also, I ran memtest for 4 hours and there were no memory errors found.
I would like to follow troll's directions to find the possible rustock rootkit problem, but I don't have XP, I am running Vista.
Gateway support told me I have hexdoor and they can't help me, so I don't know how I can have hexdoor and no scanner will find it. I tried finding hexdoor and other malware by using a M$ mallware removal tool and also a rootkit scanner, plus all anti-virus scanner mentioned above, all coming up with nothing.
So, what else could I do to see why I am getting the BSOD for0x8E? Thanks in advance.<!-- / message -->
Get and install the debugging tools for windows from the link below:
http://www.microsoft.com/whdc/devtools/debugging/whatsnew.mspx
What you need to do is load the crashdump into the debugger and see what device driver is causing the problem. If you analyze enough of these and they are in the same driver, you've found the problem If you get random crashes all over the place, it will be a bit harder to figure out.
Microsofts Knowledge Base article detailing what is below. Read it to get a feel for what you need to do.
http://support.microsoft.com/kb/315263
The crashdumps are usually located in 'C:\Windows\Minidump' and will have a .dmp extension.
To load the crashdump in the debugger use the following command line:
You need to make sure Vista is configured to generate the minidumps. I don't have Vista so someone else can chime in. If you look in the folder and they are there, you've got quite a bit to play with already.
That's about as simple as I can make it. Good luck.
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini122807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
Debug session time: Fri Dec 28 08:48:49.056 2007 (GMT-5)
System Uptime: 0 days 0:05:42.681
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 820818a3, acdff7ac, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : win32k.sys ( win32k+111919 )
Followup: MachineOwner
In windbg, type
!analyze -v
FAULTING_MODULE: 82000000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 46d4d163
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt+818a3
820818a3 f266af repne scas word ptr es:[edi]
TRAP_FRAME: acdff7ac -- (.trap 0xffffffffacdff7ac)
ErrCode = 00000000
eax=00000000 ebx=fee64fd8 ecx=ffffffec edx=acdff880 esi=fee539c8 edi=fee65000
eip=820818a3 esp=acdff820 ebp=acdff890 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt+0x818a3:
820818a3 f266af repne scas word ptr es:[edi] es:0023:fee65000=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from a0711919 to 820818a3
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
acdff890 a0711919 0101012a 000000a2 00000001 nt+0x818a3
acdff978 a0710ea0 0101012a 00000013 00000001 win32k+0x111919
acdffa28 a0669f72 00000000 0110007d acdffa70 win32k+0x110ea0
acdffa98 a066a75e a2010c6c fee63fb0 00f0f0f0 win32k+0x69f72
acdffb04 a0634e4f a2010c6c 0000003e fee04bc8 win32k+0x6a75e
acdffba4 a06d9d0a fee54bb0 00000318 a2010c6c win32k+0x34e4f
acdffbe4 a06d9d9d fee54bb0 00000318 a2010c6c win32k+0xd9d0a
acdffc0c a0642602 fee54bb0 00000318 a2010c6c win32k+0xd9d9d
acdffc54 a06db3ae 00000001 00000000 0000000e win32k+0x42602
acdffcb4 a06dd0f2 fee54bb0 00000317 a2010c6c win32k+0xdb3ae
acdffccc a06dda06 fee54bb0 00000317 a2010c6c win32k+0xdd0f2
acdffce8 a06dcf3e fee54bb0 00000317 a2010c6c win32k+0xdda06
acdffd20 8208caaa 000504f2 00000317 a2010c6c win32k+0xdcf3e
acdffd44 77af0f34 badb0d00 0012f948 ac00fd64 nt+0x8caaa
acdffd48 badb0d00 0012f948 ac00fd64 8208caaa 0x77af0f34
acdffd4c 0012f948 ac00fd64 8208caaa 00000000 0xbadb0d00
acdffd50 ac00fd64 8208caaa 00000000 00000000 0x12f948
acdffd54 8208caaa 00000000 00000000 05defe5c 0xac00fd64
acdffd58 00000000 00000000 05defe5c 77af0f34 nt+0x8caaa
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+111919
a0711919 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k+111919
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
If I do, What will happen? Will I get horrible resolution? I updated my display adapter driver the other day to the latest version, not sure if that is helping. Knock on wood, I haven't had the BSOD today.
Try updating your graphics card drivers. Probably an ATI, Intel, or Nvidia right? Make sure you are running the latest from the manufacturer. Without all of the debugging symbols loaded, it is hard to tell. What is happening is that it is blowing up on a memory operation 'REPNE SCAS'.
To be exact, I have Mobile Intel 965 Express Chipset Family
I just noticed that I can't even rollback my driver to the previous version.
I just crashed again so I am at a loss. Seems to be happening while I am accessing IE7 through roboform, but I could have sworn I crashed while navigating my Yahoo! email account a few times too. I am pretty certain I get crashes only when online browsing or accessing pages.
I ran many virus scanners, anti-rootkit scans, all that stuff and no virus or rootkit malware.
I let memtest run for 4 hours and no error.
I think the driver is the issue, but don't know where to go from here. I guess just do what you say and uninstall my driver and have vista run with the default. This is just a big headache. Any more advice would be appreciated.
I have this problem and have followed your advice. I have some dump files from when I get the STOP: 0x0000008E error. However they are .dmp files and are complete gibberish in notepad & wordpad. I'd really like to post my dump file to see if you guys see anything in there but I don't know how at this point. Please help. These errors are killing me & its a new computer!
Thanks!
Here is my dump file.