Windows XP crashing consistently
I have recently done a complete overhaul on my system. I got a Soyo P4vte with an intel 3 GHZ Proc,got a new 256 MB radeon 9800 Pro,a new memorex 16x double layer internal dvd writer and then also have an audigy MP3 board.
I have recently done a complete overhaul on my system. I got a Soyo P4vte with an intel 3 GHZ Proc,got a new 256 MB radeon 9800 Pro,a new memorex 16x double layer internal dvd writer and then also have an audigy MP3 board.
Since then i have crashing problems every couple of hours on my pc. The processor shows 40 degrees Celcius, and the case is 33.5. I've tried to fix it by completely dumping everything before all the upgrades. I upgraded the bios, did fresh install all the way to SP2 on XP updated the drivers on the motherboard,videocard, soundboard and even flashed the DVD burner. I am also running norton system works 2002 but is completely updated with all recent patches and definitions. It doesnt seem to be a certain application crashing it.
When it crashes I get the following codes and error messages on the crash saying that it appears to be a driver conflict and Microsoft has nothing further.
BCCode : 1000008e BCP1 : C0000005 BCP2 : 8054BA39 BCP3 :B8167818 BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
and the dump locations on it were the following...
C:\DOCUME~1\Justin\LOCALS~1\Temp\WERcfa8.dir00\Mini011705-02.dmp
C:\DOCUME~1\Justin\LOCALS~1\Temp\WERcfa8.dir00\sysdata.xml
I have no clue what is causing this does anybody know what i can do, or from experience what may be causing this? Any help is greatly appreciated since i am at my troubleshooting expertise limits. Thanks in advance.
Since then i have crashing problems every couple of hours on my pc. The processor shows 40 degrees Celcius, and the case is 33.5. I've tried to fix it by completely dumping everything before all the upgrades. I upgraded the bios, did fresh install all the way to SP2 on XP updated the drivers on the motherboard,videocard, soundboard and even flashed the DVD burner. I am also running norton system works 2002 but is completely updated with all recent patches and definitions. It doesnt seem to be a certain application crashing it.
When it crashes I get the following codes and error messages on the crash saying that it appears to be a driver conflict and Microsoft has nothing further.
BCCode : 1000008e BCP1 : C0000005 BCP2 : 8054BA39 BCP3 :B8167818 BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
and the dump locations on it were the following...
C:\DOCUME~1\Justin\LOCALS~1\Temp\WERcfa8.dir00\Mini011705-02.dmp
C:\DOCUME~1\Justin\LOCALS~1\Temp\WERcfa8.dir00\sysdata.xml
I have no clue what is causing this does anybody know what i can do, or from experience what may be causing this? Any help is greatly appreciated since i am at my troubleshooting expertise limits. Thanks in advance.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
This may be RAM issue.
Quote:STOP 0x0000008e
CAUSE
This behavior may occur if one of the following conditions is true:
• One or more of the random access memory (RAM) modules that are installed on your computer are faulty.
• The RAM configuration is incompatible with Windows XP.
Download memtest86
or prime95 and test your memory for errors.
Or:
If you have more than one memory module, leave only one in place and remove others, start your system and see if you got any errors. Repeat this for other memory modules.
This should 'eliminate' faulty ram, if you got one.
Quote:STOP 0x0000008e
CAUSE
This behavior may occur if one of the following conditions is true:
• One or more of the random access memory (RAM) modules that are installed on your computer are faulty.
• The RAM configuration is incompatible with Windows XP.
Download memtest86
or prime95 and test your memory for errors.
Or:
If you have more than one memory module, leave only one in place and remove others, start your system and see if you got any errors. Repeat this for other memory modules.
This should 'eliminate' faulty ram, if you got one.
thanks I will give it a try one thing i did not mention was i got new kingston DDR400 2 sticks of 512 MB RAM. I am going to test now.
I've replaced the RAM with new sticks from Kingston I asked them to extensively test now and still happening in the event log I am showing the following system error does anyone have any idea what these codes tell me. I tried using dumpcheck but it didnt give me a fault address.
I am still getting the following error
Error 1003
Error code 1000008e, parameter1 c0000005, parameter2 bf801166, parameter3 f71b6a48, parameter4 00000000.
I will try changing out the PSU next, again thank you.
I am still getting the following error
Error 1003
Error code 1000008e, parameter1 c0000005, parameter2 bf801166, parameter3 f71b6a48, parameter4 00000000.
I will try changing out the PSU next, again thank you.
Changing the psu didn't work, does anyone have any other ideas? Again, thanks for helping me through these troubling times
Error code 1000008e = "KERNEL_MODE_EXCEPTION_NOT_HANDLED_M"
Most of newsgroup comments about this stop error point to faulty hardware or drivers. The hardware varies from modems, video cards, USB device to memory or sound cards.
Sometimes it proves to be hardware that it is not compatible with Windows XP.
It could be your video adapter.
Update its drivers.
Make sure it is propely plugged in the bus(PCI/AGP).
Try another, eg. borrow from friend.
Run "chkdsk /p /r" via Recovery Console.
Check your CPU temperatures.
Update your motherboard drivers.
Disabling memory caching of the BIOS might also resolve the error.
Update your BIOS.
Click Start->Run and execute "verifier".
Click Next, Next and let it scan your system for "non-signed"/"unsigned" drivers (I have finnish language XP, so I cannot say what that is in english ). In the list you will see all unsigned drivers, try up[censored] those.
Most of newsgroup comments about this stop error point to faulty hardware or drivers. The hardware varies from modems, video cards, USB device to memory or sound cards.
Sometimes it proves to be hardware that it is not compatible with Windows XP.
It could be your video adapter.
Update its drivers.
Make sure it is propely plugged in the bus(PCI/AGP).
Try another, eg. borrow from friend.
Run "chkdsk /p /r" via Recovery Console.
Check your CPU temperatures.
Update your motherboard drivers.
Disabling memory caching of the BIOS might also resolve the error.
Update your BIOS.
Click Start->Run and execute "verifier".
Click Next, Next and let it scan your system for "non-signed"/"unsigned" drivers (I have finnish language XP, so I cannot say what that is in english ). In the list you will see all unsigned drivers, try up[censored] those.
More often than not, this error is telling you that there is a memory conflict sometimes from bad Ram, sometimes from video ram, sometimes with the conflict between system ram and the video, and sometimes from drivers wanting particular memory addresses already held by another process.
Since you have replaced the Ram, you could try just one stick to see if the problem is between the motherboard's support of two sticks.
I don't know of any compatibility problems between 9800pro and that motherboard.
Personally, my primary suspect is the Norton System Works. It is a Swiss Army knife and while it does a lot, you are often better off using the right tool rather than something that is useful when there is nothing better to use. Norton's stuff is peculiar and it is not above substituting its own .dll's for those of Microsoft's. The XP system is supposed to track where programs are stashing their functions, but System Works is duplicating this and it may be falsely masking what the system is reporting.
In any case, since you don't seem to mind tearing this thing apart, start from scratch and clean install XP with just the hardware bare essentials. Do not put the Norton's back on until you have run the machine through its paces and it doesn't reboot on you. If it does continue to give you errors, make sure that you have the proper timing on the memory. Remove all the ATI drivers and run it as a standard VGA for a while or you could put in a different video card to see if you still get the random reboots. Unfortunately, this is one of those problems were who have to eliminate one peripheral after another until you are left with just the motherboard as the last suspect.
Since you have replaced the Ram, you could try just one stick to see if the problem is between the motherboard's support of two sticks.
I don't know of any compatibility problems between 9800pro and that motherboard.
Personally, my primary suspect is the Norton System Works. It is a Swiss Army knife and while it does a lot, you are often better off using the right tool rather than something that is useful when there is nothing better to use. Norton's stuff is peculiar and it is not above substituting its own .dll's for those of Microsoft's. The XP system is supposed to track where programs are stashing their functions, but System Works is duplicating this and it may be falsely masking what the system is reporting.
In any case, since you don't seem to mind tearing this thing apart, start from scratch and clean install XP with just the hardware bare essentials. Do not put the Norton's back on until you have run the machine through its paces and it doesn't reboot on you. If it does continue to give you errors, make sure that you have the proper timing on the memory. Remove all the ATI drivers and run it as a standard VGA for a while or you could put in a different video card to see if you still get the random reboots. Unfortunately, this is one of those problems were who have to eliminate one peripheral after another until you are left with just the motherboard as the last suspect.
I think I will start by taking off system works, does anyone have a good antivirus replacement that is stable and i can use while i test this? IE. is there one that offers a trial that any of you know of?
Also I have tried replacing the sticks 1 at a time and still get the same problem.
Drivers are all updated, to include the bios and firmware on my dvd recorder, checked again today, all updates for window are done. i also tried running another driver on the 9800 today from tech net, the 1.9 version of the ATI, and still got no change.
Once again I appreciate everyone's help
Also I have tried replacing the sticks 1 at a time and still get the same problem.
Drivers are all updated, to include the bios and firmware on my dvd recorder, checked again today, all updates for window are done. i also tried running another driver on the 9800 today from tech net, the 1.9 version of the ATI, and still got no change.
Once again I appreciate everyone's help
Two free anti-virus programs are Anti-Vir: http://www.free-av.com/index.htm or AVG: http://www.grisoft.com/us/us_index.php
avast! Home Edition.
* Outlook/Exchange.
* IM.
* EMail(SMTP/POP3/IMAP4).
* Background.
* Network Shield (IDS).
* P2P.
* Outlook/Exchange.
* IM.
* EMail(SMTP/POP3/IMAP4).
* Background.
* Network Shield (IDS).
* P2P.
my computer just did the same thing yours did viking,only i didn't get one of those messages. i tried the old-fashon way of getting rid of viruses...taking the "slave" and my pops took out the virus somehow.i dunno how!LOL!after that we installed all of the free programs that we could get for blocking viruses and slapped them on the computer.(took more than an hour)but now i get an AVG virus blocker popup every 5 minutes or so,saying it found a trojan horse virus.i just put it in the vult.safest computer in this house!hope this works for you!
by the way, did you know you could do
[marquee]this?[/marquee]
just do: <marquee>whatever you want</marquee> ...only with these: []
bye!http://www.alexmason.net
by the way, did you know you could do
[marquee]this?[/marquee]
just do: <marquee>whatever you want</marquee> ...only with these: []
bye!http://www.alexmason.net
The PSU I got was ultra X connect 500 watt psu. I have checked the temps, they aren't very high, all drivers are update, right now I have removed norton and have installed AVG. I will try that if no good, will start taking off video drivers and replacing video cards. Thanks everybody, will let you know as i go!
Back again.. It is still restarting spurratically... is that a word?
Here is what I have done since the last test. I tried to determine if it is a heat issue, doubt it, CPU was reading 33.5 Celcius last time it restarted. and some times it will run for quite a while with it at 42 Celcius.
Changed the video card back to an Nvidia Geforce 128 M, updated drivers and it still restarted within 2 hours.
Tried running it in VGA mode... no luck
Turned off Bios Memory caching... no luck
Tried dropping all ATI drivers and using only Windows drivers, a standard... no luck
As I mentioned before, changed to AVG, which i do like by the way!... no luck
I do have a few unverified drivers, but they are all the latest updates according to vendor sites....
Once again any new ideas guys, I'm just minutes from using the BFH on this thing.Appreciate all your help, right now it is a battle of wills and i am losing!
Here is what I have done since the last test. I tried to determine if it is a heat issue, doubt it, CPU was reading 33.5 Celcius last time it restarted. and some times it will run for quite a while with it at 42 Celcius.
Changed the video card back to an Nvidia Geforce 128 M, updated drivers and it still restarted within 2 hours.
Tried running it in VGA mode... no luck
Turned off Bios Memory caching... no luck
Tried dropping all ATI drivers and using only Windows drivers, a standard... no luck
As I mentioned before, changed to AVG, which i do like by the way!... no luck
I do have a few unverified drivers, but they are all the latest updates according to vendor sites....
Once again any new ideas guys, I'm just minutes from using the BFH on this thing.Appreciate all your help, right now it is a battle of wills and i am losing!
Does anyone know of any shareware diagnostic tools, i've narrowed it down to MB or processor now so I am wanting to know how to check this
Originally posted by vikings976:
Quote:Does anyone know of any shareware diagnostic tools, i've narrowed it down to MB or processor now so I am wanting to know how to check this
Boot into the BIOS and let it sit. If it reboots while in BIOS then it is most likely your mother board.
Quote:Does anyone know of any shareware diagnostic tools, i've narrowed it down to MB or processor now so I am wanting to know how to check this
Boot into the BIOS and let it sit. If it reboots while in BIOS then it is most likely your mother board.
i know it's a late answer, but i just ran into the same problem on the same MOBO and figured out what is causing it. i'm posting the answer so other folks like me who went googling for someone with a similar problem can find the answer.
when you did a complete overhaul, you changed the CPU from a non-hyperthreading CPU to one that uses hyperthreading. even though the bios will discover this, and allow you to enable hyperthreading AND XP will recognize this and show as 2 CPUs in the hardware manager, you will get random crashes. could be after 2 minutes of light usage, could be after 2 hours of gaming - completely random. worst part is if you try to reinstall XP with the notion that maybe the old files and registry entries for the uniprocessor HAL and now XP will not allow you to copy certain files necessary for the installation.
change back to your old CPU. XP will not crash and you can now load the latest BIOS that 'should' solve the crashing problem. if you are in limbo, you can now reinstall XP without those file copy errors, then try to update the BIOS and maybe the hyperthreading CPU will work.
when you did a complete overhaul, you changed the CPU from a non-hyperthreading CPU to one that uses hyperthreading. even though the bios will discover this, and allow you to enable hyperthreading AND XP will recognize this and show as 2 CPUs in the hardware manager, you will get random crashes. could be after 2 minutes of light usage, could be after 2 hours of gaming - completely random. worst part is if you try to reinstall XP with the notion that maybe the old files and registry entries for the uniprocessor HAL and now XP will not allow you to copy certain files necessary for the installation.
change back to your old CPU. XP will not crash and you can now load the latest BIOS that 'should' solve the crashing problem. if you are in limbo, you can now reinstall XP without those file copy errors, then try to update the BIOS and maybe the hyperthreading CPU will work.
